Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.
Backup and Recovery Community Blog

unable to allocate new media for backup, storage unit has none available(96)

Created: 03 Nov 2010 • 2 comments
Zahid.Haseeb's picture
0 0 Votes
Login to vote

Environment

NBU Server = 7

OS of NBU = win2003R2

Client = win2003

SQL = 2000 

 

Problem

I was trying to take SQL backup but failed instantly which the below Activity Monitor error.

 

Activity Monitor

11/3/2010 11:37:02 AM - requesting resource tpsbkp-4mm
11/3/2010 11:37:02 AM - requesting resource tpsbkp.NBU_CLIENT.MAXJOBS.tpsbdc
11/3/2010 11:37:02 AM - requesting resource tpsbkp.NBU_POLICY.MAXJOBS.PVCSTrackr
11/3/2010 11:37:02 AM - Error nbjm(pid=2032) NBU status: 96, EMM status: No media is available   
unable to allocate new media for backup, storage unit has none available(96) 

 

Resolution

Actually i wanted to take the backup of MS SQL with an infinity 9 retention level. i set the retention level to 9 in the schedule which i created but did not select retention level to 9 in the Default-Application-Backup schedule. Just i selected retention level 9 in the Default-Application-Backup schedule and the problem resolved.

 

Helpful link

https://www-secure.symantec.com/connect/forums/media-still-available-backup-sql-server-not-initiating

 

Comments 2 CommentsJump to latest comment

Zahid.Haseeb's picture

Update:

 

By default Veritas Netbackup does not allow backups with different retention levels to use the same media.If you want to allow , Do select the below highlighted box.

 

This property allows NetBackup to mix retention levels on tape volumes. It applies to media in both robotic drives and nonrobotic drives. The default is that the check box is clear and each volume can contain backups of only a single retention level.

Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb

zahidhaseeb.wordpress.com

-1
Login to vote
JMatishuk's picture

This fixed my issue which is great, but it was never checked off before and we never had an issue until this last quarterly.  Strange.

0
Login to vote