β11-15-2013 02:49 AM
Hello,
I would like to submit a problem I meet with one of my masters (Solaris 7.5.0.6)
in this domain there is one master (Solaris 7.5.0.6) and one media server (Windows 2K8 7.5.0.6)
My problem is that the tapes used by the media server are always shown with a DBBACKUP status in the available_media script output
After checking the available_media in detail first, it appears that if a tape is not found in bpmedialist -mlist -l output, available_media will display a DBBACKUP status for this particular tape
here is an example of the error with a specific tape B08121 I have
master:/root# available_media | grep B08121
B08121 HCART3 TLD 0 94 - - - DBBACKUP
master:/root# bpmedialist -mlist -l | grep B08121
master:/root#
master:/root# bpmedialist -mlist -l -h mediaserver | grep B08121
B08121 *NULL* 1 20 1383930105 1384451940 1388080740 0 967744941 54 54 3 5 0 512 1024 0 15121157 0 0 0 0 0 0 0 0
master:/root# bpmedialist -ev B08121
requested media id is not assigned to this host in the EMM database
master:/root# bpmedialist -ev B08121 -h mediaserver
Server Host = mediaserver
id rl images allocated last updated density kbytes restores
vimages expiration last read <------- STATUS ------->
On Hold
--------------------------------------------------------------------------------
B08121 3 54 11/08/2013 18:01 11/14/2013 18:59 hcart3 967744941 0
MPX 12/26/2013 18:59 N/A
0
master:/root# nbemmcmd -listmedia -mediaid B08121
NBEMMCMD, Version: 7.5.0.6
====================================================================
Media GUID: 01894a58-8bb0-11e0-8000-e92b37c63adb
Media ID: B08121
Partner: -
Media Type: HCART3
Volume Group: 000_00000_TLD
Application: Netbackup
Media Flags: 1
Description: Added by Media Manager
Barcode: B08121
Partner Barcode: --------
Last Write Host: mediaserver
Created: 05/31/2011 16:01
Time Assigned: 11/08/2013 18:01
First Mount: 07/12/2011 20:52
Last Mount: 11/14/2013 19:04
Volume Expiration: -
Data Expiration: 12/26/2013 18:59
Last Written: 11/14/2013 18:59
Last Read: -
Robot Type: TLD
Robot Control Host: master
Robot Number: 0
Slot: 94
Side/Face: -
Cleanings Remaining: -
Number of Mounts: 92
Maximum Mounts Allowed: 0
Media Status: MPX
Kilobytes: 967744941
Images: 54
Valid Images: 54
Retention Period: 3
Number of Restores: 0
Optical Header Size Bytes: 1024
Optical Sector Size Bytes: 0
Optical Partition Size Bytes: 0
Last Header Offset: 15121157
Adamm Guid: 00000000-0000-0000-0000-000000000000
Rsm Guid: 00000000-0000-0000-0000-000000000000
Origin Host: NONE
Master Host: master
Server Group: NO_SHARING_GROUP
Upgrade Conflicts Flag:
Pool Number: 5
Volume Pool: Production
Previous Pool Name: SCRATCH
Vault Flags: -
Vault Container: -
Vault Name: -
Vault Slot: -
Session ID: -
Date Vaulted: -
Return Date: -
Media on Hold: 0
====================================================================
Command completed successfully.
I had a look at the technote TECH6059, but it is not relevant, the correction is already in place
Is there any workaround to get these tapes taken into account by the available_media script during bpmedialist -mlist -l on the master?
Solved! Go to Solution.
β12-03-2013 04:41 AM
Just for your information, available_media is listed in the goodies directory and thus is not an officially supported command. You will not see it listed in the NetBackup Commands Guide.
β11-15-2013 05:11 AM
Did you try to remove the media from emm?
Usage: vmdelete [-h <EMM_server> | <volume_database_host>]
[-m <media_id> | -v <volume_group>]
β11-15-2013 05:34 AM
Thank you for you reply
No I didn't, and it does not work
master:/root# vmdelete -h maser -m B08121
cannot delete assigned volume (92)
This is normal, the tape contains data written by the media server that expire next 26th of December.
I can see the tape has active through the nbemmcmd, the EMM is aware then I guess
the problem is with the available_media script, it uses the command: bpmedialist -mlist -l
and the tapes used by the media server are not listed with this command.
I have updated available_media script to run below command instead and it works fine:
bpmedialist -mlist -l -h master -h mediaserver
master:/root# available_media | grep B08121
B08121 HCART3 TLD 0 94 - 3 967744941 ACTIVE/MPX
But this is just a workaround, and I would like to understand the root cause of the problem
β11-20-2013 08:18 AM
Typically a volume will be flagged as dbbackup when available_media cannot get an accurate status. A default, so to speak.
This has been seen when the owning media server or Last Write Host cannot be contacted or had been decommissioned incorrectly. Worst-case scenario is mediadb corruption in EMM.
It might be worth your while to run the NBCC utility and create a Support case to have the results analyzed and potentially a NBCCR repair run. Check out:
http://www.symantec.com/docs/TECH67840
β11-20-2013 08:50 AM
looking into admin and bpdbm logs might give some hint
enable the admin and bpdbm logs with Verobse 5 and run the command
bpmedialist -ev B08121
then look into the logs for some hint
β12-03-2013 02:18 AM
Hi, thank you
Sorry for my late reply, I will follow your instructions and keep you posted
β12-03-2013 04:41 AM
Just for your information, available_media is listed in the goodies directory and thus is not an officially supported command. You will not see it listed in the NetBackup Commands Guide.
β12-03-2013 06:24 AM
Hi Revaroo, I agree availble_media script is just an addon tool (very useful by the way)
My concern was more with the bpmedialist command in general (why the -h is mandatory in certain case)
I ran a NBCC but it gave me no error, and nothing wrong found in the admin nor bpdbm logs
This is not a blocking point I have updated the availble_media script and it works fine for me in this case
Thank you all for your support