08-07-2016 07:22 PM
08-07-2016 07:43 PM
Restores always take priority in the job list. As soon as a drive is available it will start. If you need something immediatly i suggest pausing or stopping a job using the drive that you can easily rerun later.
08-07-2016 11:55 PM
08-08-2016 01:04 AM - edited 08-11-2016 08:13 AM
Decrease "concurrent write drives" in storager unit properties with one for the required storage unit.
Concurrent write dries does not apply to restores, this trick works well.
Once restore is done you can increment the concurent write drives again
08-08-2016 02:13 AM
Yes, this is the best practice to avoid situations like this.
08-08-2016 10:57 AM
All these have some value - I would suggest going to your pools and lowering the number of partially full tapes.
Once that is limited, as soon as one backup needs a tape, it will pause.
You should not limit the drives, instead limit the max partially full tapes to one less than your backup drives.
This also works if you want to force backups from one volume pool to another if you have multiple pools as targets.