cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to allocate media volume

ashokb
Level 3
Hi Team,

I have the new volume A000XX and already having the entry in EMM database. While firing the backup it's throwing the below error.

Please help me out from this problem.

10/05/2009 20:01:57 - current media A00025 complete, requesting next media Any
10/05/2009 20:03:03 - granted resource  A00026
10/05/2009 20:03:03 - granted resource  "...................................."
10/05/2009 20:03:03 - granted resource  "..................................."                                        
10/05/2009 20:03:05 - mounting A00026
10/05/2009 20:04:14 - Error bptm (pid=19303) incorrect media found in drive index 0, expected A00026, found A00024,FREEZING A00026
10/05/2009 20:04:14 - mounted A00026; mount time: 0:01:09
10/05/2009 20:04:14 - current media A00026 complete, requesting next media Any
10/05/2009 20:05:22 - Error ndmpagent (pid=19302) NDMP backup failed, path = /vo                                              l/vol1/
10/05/2009 20:05:22 - end writing; write time: 4:03:46
unable to allocate new media for backup, storage unit has none available (96)


Thanks in advance.

Regards,
Ashok
7 REPLIES 7

Andy_Welburn
Level 6
you've got an incorrectly labelled tape. More likely a drive config issue.

To start with check the following T/N on how to use robtest to identify misconfigured drives:

Steps to verify device configuration using robtest.

Andy_Welburn
Level 6
that someone has physically replaced tapes in the library without inventorying the robot. Excerpt from T/N DOCUMENTATION: How to troubleshoot frozen media on UNIX and Windows

"...
This can occur under the following circumstances:
  • If NetBackup requests a media ID to be mounted in a drive and the media ID physically recorded on the tape is different than that NetBackup media ID, media will freeze. This can happen if the robot needs to be inventoried, if barcodes have been physically changed on the media, or if the media was previously written to by another NetBackup installation with different barcode rules.
  • The drives in the robot are not configured in order within NetBackup, or are configured with the wrong tape paths. Configuration of drives using the correct Robot Drive Number is important to the proper mounting and utilization of media. The Robot Drive Number, commonly set based on co-relation of the drive serial number with drive serial number information from the robotic library, should be determined and validated before the device configuration is considered complete.
..."

& another one for you to look through: GENERAL ERROR: Tapes are being frozen due to "<16> write_backup: incorrect media found in drive inde...

There are more out there (!!! ;) ). try the Knowledge Base or This Technote contains a table for NetBackup's Status Codes, with links to potential resolutions for...

Nicolai
Moderator
Moderator
Partner    VIP   
For the issue:  Error bptm (pid=19303) incorrect media found in drive index 0, expected A00026, found A00024,FREEZING A00026
Run a robot inventory - It seems media have been mixed around. The optical label and the magnetic label should match.

Second: unable to allocate new media for backup, storage unit has none available (96)
You are out of free media. Add some more, but check you have a scratch pool created. Media assigned to a volume pool will remain in the pool - even if they are free unless a scratch pool is created. Media unassigned will then return to the scratch pool and become available to other volume pools.

See the Veritas NetBackup Administrator’s Guide, Volume I page 543 regarding description of a scratch pool.

and the Veritas NetBackup Administrator’s Guide, Volume II page 96 has some examples of scratch pool usage.

Nicolai
Moderator
Moderator
Partner    VIP   
What a speed Andy has ......

Andy_Welburn
Level 6
:D

Nicolai
Moderator
Moderator
Partner    VIP   
TIMEZONE="Europe/Copenhagen"

So what timezone are you in - GMT ?

I am getting curious !

Andy_Welburn
Level 6
Currently BST (i.e. GMT +1) but will be back to GMT at end of month.