vmoprcmd
hi all,
This is the output of my vmoprcmd -d command:
PENDING REQUESTS
<NONE>
DRIVE STATUS
Drv Type Control User Label RecMID ExtMID Ready Wr.Enbl. ReqId
0 hcart3 TLD No K00451 Yes Yes 0
1 hcart3 TLD No K00450 Yes Yes 0
2 hcart3 TLD Yes K00090 K00090 Yes Yes 0
3 hcart3 TLD No K00358 K00457 Yes Yes 0
4 hcart3 TLD - No - 0
5 hcart3 TLD - No - 0
6 hcart3 TLD - No - 0
7 hcart3 TLD - No - 0
ADDITIONAL DRIVE STATUS
Drv DriveName Shared Assigned Comment
0 KCL7001-LTO3-1 Yes bu7.kan.ironmou
1 KCL7001-LTO3-2 Yes bu7.kan.ironmou
2 KCL7001-LTO3-3 Yes bu7.kan.ironmou
3 KCL7001-LTO3-4 Yes bu7.kan.ironmou
4 HP.ULTRIUM3-SCSI.008 No -
5 HP.ULTRIUM3-SCSI.009 No -
6 HP.ULTRIUM3-SCSI.010 No -
7 HP.ULTRIUM3-SCSI.011 No -
-bash-3.2$
1. the 2 tapes k00451 and k00450 says its unlabled and backups are happening fine. What does this mean. would i get a gud backup? do i have to relabel and run the backup?
2. 3 hcart3 TLD No K00358 K00457 Yes Yes 0 : the recmid and extmid are different. what could be the reason? and also the its unlabel?
3. is there a way to see all the unlabel tapes?
Comments
Some technical info: The
Some technical info:
The External Media ID (ExtMID) is usually written on an external label which is attached to the outside of the media cartridge. It is used to identify the media before it is inserted into the drive, but is not recorded internally on the media itself.
The Recorded Media ID (RecMID) is an internal label recorded at the beginning of the media. This should be the same as the media ID that is recorded in the volume database. If they do not match when the media gets mounted into the drive and the RecMID is read, the bptm process will freeze the media.
(In answer to Q2. You could end up with frozen media. You need to fix the mismatch. I would freeze the tape anyway and await expiration. Then properly label the tape using bplabel command or the GUI under Media Management branch)
A media with a RecMID is called a labeled volume. Unlabeled volumes do not have a RecMID. When a request for an unlabeled volume takes place, without specifying the RecMID, the ExtMID is referenced by default (even if the ExtMID is not actually recorded on the volume). This is because the system assumes the RecMID and ExtMID labels are the same unless otherwise specified.
(Q3. Issue command vmquery -W -a | awk {print $1, $4) to check for unlabelled tapes.
The first column is the RecMID which is the Media ID written in the volume database.)
References to look at:
http://seer.entsupport.symantec.com/docs/311622.htm
http://seer.entsupport.symantec.com/docs/275000.htm
http://seer.entsupport.symantec.com/docs/245195.htm
Tip: Get overview/document your NBU environment. Run 'nbsu' and review the output.
• If this provides help, please vote or mark appropriate solution.
in addition to Stuart's
in addition to Stuart's comments:
I've seen this happening when there's device mapping mismatch.
At some point in time, multiple jobs were kicked off at the same time. New tapes, K00358 and K00457 were requested and mounted in 2 different drives. Because the device mapping was wrong, the internal labels got mixed up.
Restores will be difficult, if not impossible.
You need to 1st of all verify device mapping, then fix internal labels.
If there are images on these tapes, you will need to perform a manual mount. NBU avrd will only recognize the internal label. Duplicate the images that belong to internal label to a different volume pool. Then expire all images belonging to this media id.
Unfreeze media if frozen, then re-label (use media GUI). De-select the tick-box to verify internal label.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
I agree
What Marianne has said happened to us following installation of a replacement tape library.
We did not pay enough attention to the config of the 4 drives. When we subsequently labelled all the new tapes, they were loaded ok in all 4 drives, but at least 2 were mapped incorrectly & therefore recorded media & external media ids did not match. This caused no end of issues for the next few days until the config was corrected & the tapes re-labelled!!
If you do re-label the tapes, ensure the tick-box is deselected for label verification as stated by Marianne. If not either the labelling job fails or apparently "succeeds" but does not actually re-label!
Regards Andy
"It's not too late to panic ..."
Would you like to reply?
Login or Register to post your comment.