unable to allocate new media for backup, storage unit has none available
Updated: 21 May 2010 | 12 comments
This issue has been solved. See solution.
Hi All,
I have configured the NFS backup policy on sunday ,Apart from this none of the backups are running in this time,I have 2 drives tape library,both the drives are free on that time.
Also I have kept some tapes in the scratch pool,Even though I have got this error.
I wanted know why this error came or suggest me what & all needs to check avoid this type of errors.
Thanks in advance.
discussion Filed Under:
Comments
Hi
Make a practice to run inventory on the tapes before you run the actual Job .
If this response answers your concern, please mark it as a "solution"
There are several things you will need to check:
For starters lets look at:
1) Is your scratch pool actually defined as a scratch pool (not just by name)? (vmpool -list_scratch)
2) Are the tapes in the scratch pool of the correct density for the backup in question? (eg HCART/HCART3 or whatever)
3) Are the tapes in the scratch pool available (not frozen, suspended or physically expired)? (nbemmcmd -listmedia -mediaid <media_id> )
Regards Andy
"It's not too late to panic ..."
Checked erlier
I have checked erlier itself I didn't get any issues in this,is there any chances of drive issues.
Don't think so.
If there were drive issues they would probably show as down & you would tend to get 196 errors - the backups would Q until the backup window closed. This is a media allocation issue - there are no available tapes left in the volume pool in question & NB can't find any suitable tapes in scratch.
***Edit**
Have you had a look thru' the guides Stuart & Marianne have referenced or the link to 96 error codes from the URL I provided?
You may need to provide us with output from some of the commands to see if we can isolate any issues.
Regards Andy
"It's not too late to panic ..."
In-depth Troubleshooting Guide for Status 96
Consult this troubleshooting guide.
In-depth Troubleshooting Guide for Exit Status Code 96 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0
http://seer.entsupport.symantec.com/docs/278555.htm
Further help from the GUI:
Also you can troubleshoot status codes information in the Admin Console GUI
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
Also:
look at the following for status code 96:
This Technote contains a table for NetBackup's Status Codes, with links to potential resolutions for each.
Regards Andy
"It's not too late to panic ..."
In-depth Troubleshooting Guide for Exit Status Code 96
Have a look at this doc:
http://seer.entsupport.symantec.com/docs/276881.htm
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
Thanks for the info,
Let me trouble shoot as per the DOC.
Done,
It's working now.Tape was frozen which is there in the policy,also I have not run the invetory from log time since tapes are already been used which there in scratch pool.
Good.
If you haven't done so already (altho' you probably have), give the tape a look over to see if it's damaged at all (dislodged tape-leader maybe). If happy that it looks ok then you can use the bpmedia command to unfreeze it or the GUI. Keep an eye out for it freezing again, as if it keeps doing so it will probably need disposing of.
Regards Andy
"It's not too late to panic ..."
Ok Andy,
Thanks a lot....
Additional info:
may be of interest (!):
DOCUMENTATION: How Veritas NetBackup 6.x (tm) determines if a tape should be frozen or the status of a tape drive should be changed to down, and how to change this behavior
DOCUMENTATION: How to troubleshoot frozen media on UNIX and Windows
Regards Andy
"It's not too late to panic ..."
Would you like to reply?
Login or Register to post your comment.