We have our SP server configured to run 6 migration processes. There are 8 tape drives.
What generally happens is that the migration from disk to tape starts with 6 processes, but then gradually loses processes to preemption from backups or restores which need a tape drive.
After while it ends up with only about 2 processes, and eventually only 1.
There is a lot of data to migrate (the disk pool is 17TB), and once it's down to 1 or 2 processes, the migration takes a very long time to complete(24 hours or more), and it often doesn't keep up with the data coming into the disk pool.
Is there some way of forcing a migration to either re-spawn processes as tape drives become available, or automatically exit and restart, once it gets down to only 1 or 2 processes?
What generally happens is that the migration from disk to tape starts with 6 processes, but then gradually loses processes to preemption from backups or restores which need a tape drive.
After while it ends up with only about 2 processes, and eventually only 1.
There is a lot of data to migrate (the disk pool is 17TB), and once it's down to 1 or 2 processes, the migration takes a very long time to complete(24 hours or more), and it often doesn't keep up with the data coming into the disk pool.
Is there some way of forcing a migration to either re-spawn processes as tape drives become available, or automatically exit and restart, once it gets down to only 1 or 2 processes?