STATUS CODE 96: Unable to use media for backups in a robotic library after a successful upgrade to NetBackup 6.0, due to media not expiring properly. The bpexpdate command fails with "Requested media id was not found in the EMM database".

Problem

STATUS CODE 96: Unable to use media for backups in a robotic library after a successful upgrade to NetBackup 6.0, due to media not expiring properly. The bpexpdate command fails with "Requested media id was not found in the EMM database".

Error Message

status 96: unable to allocate new media for backup, storage unit has none available;

Requested media id was not found in the EMM database

Solution

Overview:
After an upgrade from NetBackup 5.x to NetBackup 6.0, the nbpushdata command must be run in order to migrate the contents of the 5.x database files to the Enterprise Media Manager (EMM) Server.  If an assigned volume existed before the upgrade without a corresponding mediaDB entry on the media server that last wrote to the media, then the new EMM server will not contain a complete media record.  This will result in an assigned volume that cannot be used for backups and will never expire.  This is also known as an inconsistent media.  If this happens with multiple media id's, jobs can fail with Status 96 due to no media being available for the backup.

Note: This document applies only to the Status Code 96 being received due to information about the media being inconsistent in the database.  Please follow the In-depth TechNote on Status 96 in the Related Documents section below, for general procedures on addressing the Status 96 error.


Troubleshooting:
In order to use media again that have this issue, they must be expired.  However, for the reasons mentioned above, the media will not expire on their own and manually expiring them with the bpexpdate command will fail.  If an assigned media is not being mounted for backups and it is suspected that it has an inconsistency, the procedure listed below may be followed.


Log Files:  N/A


Resolution:
The procedure for analyzing and eliminating inconsistencies for a media is as follows.  This example uses "A00001" as an example media id:

1. Use nbemmcmd to list the media server record for the media id.  If the Media Server: hostname appears as NONE, yet there is a value for Time Assigned:, this indicates an incomplete EMM media record.  In the output below, "A00001" is assigned, but has no associated media server.   If there is a media server name listed, do not proceed with these steps, as the record is consistent.

nbemmcmd
UNIX: /usr/openv/netbackup/bin/admincmd/

Windows: <Install_dir>\NetBackup\bin\admincmd

Command syntax example and output:
nbemmcmd -listmedia -mediaid A00001

NBEMMCMD, Version:6.0(20050906)
=====================================================
Media GUID:      a5ea9a7a-8d50-13f4-8018-cef85f775cf7
Media ID:        A00001
Partner:         -
Media Type:      HCART
..
Barcode:         A00001
Partner Barcode: --------
Media Server:    NONE
Created:         04/27/2005 16:20
Time Assigned:   05/04/2005 04:20
.. .. ..
=====================================================
Command completed successfully.


2. Determine if the media ID exists in the merge table.  If the media ID appears in this listing, then a different issue exists, do not proceed further.  Contact Symantec Enterprise Technical Support for assistance with getting this media ID out of the merge table.  The following example shows no media id's in the merge table:

nbemmcmd
UNIX: /usr/openv/netbackup/bin/admincmd/

Windows: <Install_dir>\NetBackup\bin\admincmd

Command syntax example and output:
nbemmcmd -listmedia -mergetable

The following number of records were found:0
Command completed successfully.


3. From the same path, type "bpimmedia -mediaid A00001" to determine if there are any images on this piece of media.  If there are no images, then no output will be displayed.  If there are images, an IMAGE line and FRAG line will appear for each valid image on the media ID.


4. As long as the media ID does not appear in the merge table, the bptm command can be used to build a complete media record for the affected media ID.  Then, the volume can then be unassigned and expired.  This will require the Media ID of the affected media, as well as the density and the Volume pool number.   The following example is from a Solaris 9 server with a media id of A00001, a density of HCART, that resides in Volume Pool 1 (NetBackup).

bptm
UNIX: /usr/openv/netbackup/bin

Windows: <Install_dir>\NetBackup\bin

Command syntax example:
bptm -makedbentry -m A00001 -den hcart -poolnum 1


5.  Once this command completes, run the "nbemmcmd -listmedia -mediaid A00001" command again from Step 1.  There should now be a valid Media server: hostname.   Also, it is important to note that the media is now frozen, with an expiration of "infinity".


6. If no images were found in step 3, the tape can now be expired with the bpexpdate command.  

bpexpdate
UNIX: /usr/openv/netbackup/bin/admincmd

Windows: <Install_dir>\NetBackup\bin\admincmd

Command syntax example and output:
bpexpdate -m A00001 -d 0  

Are you SURE you want to delete A00001 y/n (n)? y

Now that the media is expired, it can be used for backups again and will be overwritten.  If there are images found on the media from step 3 that need to be preserved, the media can be left alone and expired later, but will not be used for backups until it is manually expired with bpexpdate, as it is now frozen with an expiration of "infinity".  

If it is desired to retain data on any media that has been expired, an import should be performed immediately to prevent an overwrite.  For more information on importing expired media, see the System Administrator's Guide, referenced below, in the Related Documents section.



Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)