01-31-2011 02:28 AM
Netbackup 7.0.1
Windows 2003
So I have three tapes in the same volume pool which are used to backup several servers over a weekend. I've setup two SQL policies, one starts a half an hour earlier than the other and is a higher priority (2). I need to make sure this one completes, its got all the production SQL servers, the other one isn't so important but still needs to run.
The problem is the second (less important job) kicks off, appears to take priority, stopping the other one, and once it completes the important SQL job fails its remaining jobs with status 96 errors.
My first thought was all the tapes are full. So I checked the size. Two of them are full (including the tapes that Important SQL job was using) and the third tape only has 28GBs in use.
So my question is, how do I figure out why Netbackup is not utilising this tape and deciding to fail all remaining jobs instead?
Any help greatly appreciated
Thanks
Solved! Go to Solution.
01-31-2011 06:30 AM
Correct, the Application Backup schedule determines the actual retention level of the backup image.
Changing the schedule will apply to future backups and not backups already written.
If you want to update the images/media written with infinity retention, you can do that using the 'bpexdate -recalculate' command.
01-31-2011 04:18 AM
01-31-2011 05:11 AM
Hi,
Take a look at the following technote which explains how Netbackup Selects media for backup.
http://www.symantec.com/business/support/index?page=content&id=TECH7354&key=15172&actp=LIST
Hopefully this will answer your question.
01-31-2011 05:40 AM
Thanks, I forgot to mention that all Policies are set with a retention of 5 weeks, but I went over this again and noticed that the associated application backup was set to Infinity, which could have caused some confusion. So I've set that to 5 weeks aswell to make sure all retentions match.
Im hoping thats what it was. Thanks for the link, I'll have a proper read through this now.
01-31-2011 06:30 AM
Correct, the Application Backup schedule determines the actual retention level of the backup image.
Changing the schedule will apply to future backups and not backups already written.
If you want to update the images/media written with infinity retention, you can do that using the 'bpexdate -recalculate' command.
04-04-2011 11:07 PM
See the below BLOG for your reference. Hope it will help you:
04-05-2011 04:34 AM
@pjtee - Please let us know if you managed to resolve this problem?