Hi Ryan,
Move Backup will respect the concurrent task limits set on source/target repository, so if there are concerns about the workload on the repository you can set the concurrent task limit lower on the source OR target repository, and Backup Move will honor the restrictions.
As for is it faster to go sequentially, depends on the storage itself -- a lot of storage can easily support quite a number of streams with stable performance for each stream, so it will largely depend on the environment.
Are you seeing issues where Backup Move is non-performant compared to backups/restores?
Move Backup will respect the concurrent task limits set on source/target repository, so if there are concerns about the workload on the repository you can set the concurrent task limit lower on the source OR target repository, and Backup Move will honor the restrictions.
As for is it faster to go sequentially, depends on the storage itself -- a lot of storage can easily support quite a number of streams with stable performance for each stream, so it will largely depend on the environment.
Are you seeing issues where Backup Move is non-performant compared to backups/restores?
Statistics: Posted by david.domask — Apr 30, 2025 7:52 am