-
-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Enhancement Request] Bulk move support from $source_volume to $target_volume #83
Comments
A lot of work has gone into this script to make sure that extra folders, symlinks and settings are moved and edited to suit the new volume location. I added an "all" menu option for backing up and restoring. Adding an 'all' menu option for moving would be easy enough to add. You're the 2nd person in 2 weeks that have asked for it. |
Yeah clearly a lot has! I started with an app I didn't care about getting hosed and it worked perfectly, scaled up from that and eventually moved everything. To confirm-- we're good to delete the volume after the move right? No data tendrils should be left (understanding some apps need you to move the db, like drive sync) |
I recommend checking your apps still work as expected, without the old volume, before deleting the old volume:
Assuming all your apps are okay:
Of course all of the above assumes that there is only 1 volume on those drives. |
I'm the third one. I upgraded from Synology DS220j (2 bay) to DS923+ (4 bay) and want to migrate everything from ext4 to btrfs, so I created a new btrfs volume with 2 new drives and I have to move everything there from the old ext4 volume. I'll do it one by one now. Beside your project there is only one solution: backup, reinstall/reconfigure, and restore everything, which not optimal if I have 2 working disk and 2 new disk in a 4 bay NAS to make the transition. Thank you for your work. |
+1 for moving all packages from one to another volume. |
+1 also please when you have time this would be fantastic |
Another +1 for a move all |
Reading the docs, it seems like you've done some dependency mapping to ensure things are re-linked properly (haven't looked at the scripts though, just assuming).
In any case, since this tool has methods in place to move applications safely and re-link deps, I think it would be a great enhancement to be able to bulk-move applications, where all applications from /$source_volume are moved to /$target_volume in one go.
ex:
The text was updated successfully, but these errors were encountered: