03-24-2016 10:21 AM
I know I'm probably missing something rudimentary, but here's my situation:
I created a policy to backup some directories on a single server concurrently. So my backup selection looks like this:
NEW_STREAM
/backup/folder1
NEW_STREAM
/backup/folder2
NEW_STREAM
/backup/folder3
NEW_STREAM
/backup/folder4
etc... for a total of 10 streams.
The policy schedule has "Media Multiplexing" set to 6, and the storage unit has multiplexing enabled, with a max of 8 streams per drive.
When I run the job, I get 10 backup jobs each writing to a different tape drive, pretty much consuming all the drives. I would expect the jobs to stream to 2 drives.
What am I missing? The environment is 7.6.
Thanks
Solved! Go to Solution.
03-24-2016 10:49 AM
Create another storage unit, pointing to the same device definition, but limit this new storage unit to two concurrent write drives, and then change the required policy schedule(s) to use this new storage unit.
03-24-2016 10:49 AM
Create another storage unit, pointing to the same device definition, but limit this new storage unit to two concurrent write drives, and then change the required policy schedule(s) to use this new storage unit.
03-24-2016 11:56 AM
Thanks! It's been a while since I had to deal with tape backups outside of an SLP.
03-24-2016 01:32 PM
03-24-2016 01:53 PM
Yeah, my guess is that there is possibly a retention level clash... if other jobs from other policies wouldn't multi-plex in to the original config that created multiple jobs spread across many drives.
04-12-2016 07:02 AM
The issue was what SDO commented on.
The policy I created had a different retention than my other policies (this was a one-time backup for migration purposes). So when I kicked it off, it took all the drives and my regular jobs had no resources available. I created an STU with a max of 2 drives and that remediated the issue.