12-06-2014 05:24 AM
Hello Experts,
I had a policy which i fired last night. It has 1 month retention as other policies from last 1 day its still in queue
with the "awaiting resource xxx-hcart3-robot-tld-0 - No drives are available" message every time..
1:- I cancelled it and again fired it same is happening.
2:- Made the priority to 99999 but to no avail.
3:- Changed the storage unit :(
4:- If i fire other backup policy thats go to active state in a jiffy.
Pls suggest how to troubleshoot.
Server is on 7.6 Windows and these are solaris flat files backup.
Thanks,
Solved! Go to Solution.
12-06-2014 10:39 AM
If the pool and/or retention is different it will queue.
If new jobs have same retention and pool as the jobs already busy, it will be added to same drives/tapes.
NBU will give priority to jobs that do not need tape change, regardless of policy priority.
Also see explanation in this post: https://www-secure.symantec.com/connect/forums/start-high-priority-backup-job-front-other-queued-job...
There is also a TN that explains this.
Understanding the Job Priority setting
http://www.symantec.com/docs/HOWTO105692
Extract:
The following scenarios present situations in which a request with a lower priority
may receive resources before a request with a higher priority:
■ A higher priority job needs to unload the media in a drive because the retention
level (or the media pool) of the loaded media is not what the job requires. A
lower priority job can use the media that is already loaded in the drive. To
maximize drive utilization, the Resource Broker gives the loaded media and
drive pair to the job with the lower priority.
12-06-2014 06:11 AM
12-06-2014 06:11 AM
12-06-2014 07:06 AM
Yes
12-06-2014 10:39 AM
If the pool and/or retention is different it will queue.
If new jobs have same retention and pool as the jobs already busy, it will be added to same drives/tapes.
NBU will give priority to jobs that do not need tape change, regardless of policy priority.
Also see explanation in this post: https://www-secure.symantec.com/connect/forums/start-high-priority-backup-job-front-other-queued-job...
There is also a TN that explains this.
Understanding the Job Priority setting
http://www.symantec.com/docs/HOWTO105692
Extract:
The following scenarios present situations in which a request with a lower priority
may receive resources before a request with a higher priority:
■ A higher priority job needs to unload the media in a drive because the retention
level (or the media pool) of the loaded media is not what the job requires. A
lower priority job can use the media that is already loaded in the drive. To
maximize drive utilization, the Resource Broker gives the loaded media and
drive pair to the job with the lower priority.
12-07-2014 03:50 AM
What happens if you set the policy start time to 5 minutes before the other policies ?
Netbackup has a algorithm that weights tape mount/dismount higher than a jobs with higher priority. Its quite normal to see other lower priority jobs take over a streams on a tape drive because those jobs fit the needed retention and volume pool