11-08-2011 04:31 AM
Hi All,
We are running on NBU 6.5 on windows with 1 master and 2 media servers. Recently we introduced a new library and decommissioned the old one, while we are trying to restore from old tapes it doesn't do it. The media id in the database is 5623L3 but while doing the inventory it shows something like AV5623L3. After a bit search we were able to restore the data using below TN but had to wait overnight for the manual intervention to remove and insert the tapes. Is there any way we can restore the data without removing the tape from the library once inventory is done?
http://www.symantec.com/docs/TECH69855
We did delete the tape and then moved it but that did no help and after all the tried we had to remove the media physically from the robot,
We also tried the vmphyinv command but it says the media id already exist in the database.
Can someone please answer the above 2 questions so future restores can be done smoothly.
Thanks
Solved! Go to Solution.
11-08-2011 10:05 AM
Oh dear... Did not realize you started using the media with the 'new' 1st 6 char barcodes....
If we look at the examples in your opening post:
AV5623L3 will be in the NBU database as 5623L3.
Inventory on new robot would add it as AV5623.
For now, keep assigned media ending in L3 out of the robot. Delete expired/unassigned media so that you can put it in the robot to be overwritten. BUT- you will have to re-label these tapes to overwrite the internal label. (Right-click, label, de-select verify label.)
To restore from 5623L3, allow inventory to add the tape as AV5623. Record the slot number and volume group.
Delete AV5623.
Find 5623L3 in the Media GUI, right-click and select Move. Specify the slot number and volume group recorded above.
Eject after the restore has completed.
11-08-2011 04:52 AM
yes you can restore data from old tapes but
now you need configure barcode labels with new tape library as it was priviously ....
NOTE -- you can configure barcode labels on Netbackup level & tape library level as well.
Below URL will help you for the same
https://www-secure.symantec.com/connect/forums/netbackup-barcode-length
https://www-secure.symantec.com/connect/forums/barcode-media-problem
https://www-secure.symantec.com/connect/forums/barcode-rulesmedia-id-generation-question
11-08-2011 04:55 AM
You need to consider introducing a barcode rule to remove the first two characters of your media from being presented to NetBackup. It only stores 6 chars. You can determine which 6 via Advanced Options in Inventory Robot dialog.
/usr/openv/volmgr/bin/vmrule -listall
The above command will also show you the rules already set ON the master... there was the previous caveat that some rules were set via the Admin Console and only stored there ie on that client (persons computer.)
The Volume II of the Admin Guide will detail how to set a rule(s)
11-08-2011 05:06 AM
Please help us to understand how media id is stored since new robot was attached?
You mentioned "AV5623L3", but as previously mentioned, NBU will only store 6 characters.
Please run this command and post the first couple of lines:
vmquery -bx -rn <robot-number>
Then run the command for all media and post a number of media-id's that shows robot type as NONE:
vmquery -bx -a
11-08-2011 05:06 AM
Thanks Stuart and Yogesh but we already had the barcode set on the new library 1 month backup and can't change it now else it will not work for the new ones.
C:\Program Files\VERITAS\Volmgr\bin>vmrule -listall
===========================================================
rule number: 0
barcode tag: JJ
media type: HCART3
pool name: Scratch_Pool
max mounts: 0
description: --
===========================================================
I would like to know if we can restore from the old tapes that were written from old library without removing and inserting again once inventory is done as per the TN above? Is there any way around doing the same thing without removing the tapes from the library once invetory is done.
11-08-2011 05:47 AM
It seems that the 1st 6 characters are now stored and previously it used to be the last 6, right?
We need to see how the robot reads/presents the media.
Please run the following from cmd, and post a couple of lines:
vmcheckxxx -rn 2 -rt TLD
Check 'Barcode' column - 6 or 8 characters?
If 6, you need to check robot setting to present 8 characters instead of 6.
NBU will store the last 6 by default (as with previous robot).
11-08-2011 06:15 AM
Yes that is what it looks like, you mean to say I should change something from the library side
Robot Contents Volume Configuration
Slot Tape Barcode Media ID Barcode Mismatch Detected
==== ==== ============= ======== ============= =================
1 No
2 Yes JJD643 JJD643 JJD643
3 No
4 No
5 No
6 Yes JJD621 JJD621 JJD621
7 No
8 Yes JJD629 JJD629 JJD629
9 Yes JJD641 JJD641 JJD641
11-08-2011 06:26 AM
Correct - the library is configured to report 6 chars only.
Look in your robot documentation how to do that or ask the hardware vendor.
If you post your robot make and model, one of our list members will surely be able to point you in the right direction.
11-08-2011 06:33 AM
You are right in the library Barcode Label Length Reported To Host is 6, after making it to 8 do I have to reboot the library or recycle the services for NBU. Also what about the tapes that are written for past 1 month with media id showing first 6 characters, will I be able to restore from those or need to make some changes ?
11-08-2011 07:30 AM
Hey Marianne,
changed Barcode Label Length Reported To Host 8 saved the settings in the library configuration and ran the inventory and it prompted to update the volume configuration for the tapes in the library and wow it shows the last 6 characters now but I didn't update the volume configuration and cancelled it as i haveto take the approval.
Could you please suggest what will happen to the tapes that were written with first 6 characters, will I be able to restore or have to change the configuration ?
Also if my architect doesn't allow me to change the setting to make it last 6 character how should i go about restore.
thanks for ur help.
11-08-2011 07:33 AM
Hi Marianne,
My apologies it is indeed 6 characters and shows XX5623 whereas in the database it is 5623L3
C:\Program Files\VERITAS\Volmgr\bin>vmquery -bx -rn 2
media media robot robot robot side/ volume optical # mounts/
last assigned pool
ID type type # slot face group partner cleanings
mount time time
--------------------------------------------------------------------------------
-------------------------------------------
JJD551 HCART3 TLD 2 22 - 000_00002_ - 5 1
0/13/2011 23:32 10/10/2011 22:55 Vault_Monthly
vmquery -bx -a output
XX5623 HCART3 TLD 2 21 - 000_00002_ - 0 00/00/0000 00:00 --- --- NetBackup
P180L3 HCART3 NONE - - - --- - 3 03/09/2010 23:47 --- --- Scratch_Pool
11-08-2011 10:05 AM
Oh dear... Did not realize you started using the media with the 'new' 1st 6 char barcodes....
If we look at the examples in your opening post:
AV5623L3 will be in the NBU database as 5623L3.
Inventory on new robot would add it as AV5623.
For now, keep assigned media ending in L3 out of the robot. Delete expired/unassigned media so that you can put it in the robot to be overwritten. BUT- you will have to re-label these tapes to overwrite the internal label. (Right-click, label, de-select verify label.)
To restore from 5623L3, allow inventory to add the tape as AV5623. Record the slot number and volume group.
Delete AV5623.
Find 5623L3 in the Media GUI, right-click and select Move. Specify the slot number and volume group recorded above.
Eject after the restore has completed.
11-10-2011 09:47 PM
Hey Marianne,
I did as suggested and it shows now 5623L3 in there but while doing the restore it generates the pending action stating media misplaced. Also when I try to inventory the library it tries to update the volume configuration with AV5623. It seems its not detecting the media in the library once we deleted it and moved it and that is the reason it comes up in the inventory to update the volume configuration.
11-11-2011 03:44 AM
If you do an inventory it WILL add/update the media id as AV5623.
The manual update process that I've described above should work to allow you to restore. I have personally assisted customers in this way on more than one occation.
Please do me a favour - please post output of the following commands:
vmquery -m AV5623
vmquery -m 5623L3
11-15-2011 02:28 PM
Here is the output:
C:\Program Files\VERITAS\Volmgr\bin>vmquery -m NV5623
===================================================================
media ID: NV5623
media type: 1/2" cartridge tape 3 (24)
barcode: NV5623
media description: Added by Media Manager
volume pool: NetBackup (1)
robot type: TLD - Tape Library DLT (8)
robot number: 2
robot slot: 21
robot control host: delba0003
volume group: 000_00002_TLD
vault name: ---
vault sent date: ---
vault return date: ---
vault slot: ---
vault session id: ---
vault container id: -
created: 11/11/2011 5:51:20 PM
assigned: ---
last mounted: ---
first mount: ---
expiration date: ---
number of mounts: 0
max mounts allowed: ---
===================================================================
C:\Program Files\VERITAS\Volmgr\bin>vmquery -m 5623L3
===================================================================
media ID: 5623L3
media type: 1/2" cartridge tape 3 (24)
barcode: NV5623L3
media description: Added by Media Manager
volume pool: Vault_Monthly (11)
robot type: NONE - Not Robotic (0)
volume group: ---
vault name: ---
vault sent date: ---
vault return date: ---
vault slot: ---
vault session id: ---
vault container id: -
created: 7/19/2007 4:08:48 PM
assigned: 4/2/2011 8:00:17 PM
last mounted: 11/1/2011 8:21:45 PM
first mount: 7/19/2007 4:14:16 PM
expiration date: ---
number of mounts: 18
max mounts allowed: ---
status: 0x0
===================================================================
11-15-2011 08:58 PM
Can we try again what I suggested above?
Delete AV5623.
Right-click on 5623L3 and select Move. Select robot 2 (robot control host delba0003), slot 21, volume group 000_00002_TLD.
Start the restore.
Eject after the restore has completed.
PLEASE do not perform an inventory while this tape is in the robot. It will once again move 5623L3 to Non-robotic and add AV5623.
11-18-2011 01:22 PM
Hi Marianne,
I tried it exactly the way you suggested but still it shows the same thing:
11/19/2011 2:45:56 AM - connecting
11/19/2011 2:46:03 AM - started process bptm (1476)
11/19/2011 2:46:03 AM - mounting 5623L3
11/19/2011 2:46:04 AM - connected; connect time: 00:00:08
11/19/2011 2:46:08 AM - Error bptm(pid=1476) error requesting media, TpErrno = Robot operation failed
11/19/2011 2:46:46 AM - begin Restore
11/19/2011 2:46:48 AM - 1 images required
11/19/2011 2:46:48 AM - media 5623L3 required
11/19/2011 2:46:53 AM - restoring image XXXXX_1301668201
11/19/2011 2:46:59 AM - requesting resource 5623L3
11/19/2011 2:46:59 AM - granted resource 5623L3
11/19/2011 2:46:59 AM - granted resource HPMSL4048_D1
11/19/2011 2:47:09 AM - current media 5623L3 complete, requesting next resource HPMSL4048_D1:Vault_Monthly:5623L3
11/19/2011 2:47:17 AM - awaiting resource HPMSL4048_D1:Vault_Monthly:5623L3 A pending request has been generated for this resource request.
Operator action may be required. Pending Action: Misplaced tape.,
Media ID: 5623L3, Barcode: NV5623L3, Density: hcart3, Access Mode: Read,
Action Drive Name: N/A, Action Media Server: N/A, Robot Number: 2, Robot Type: TLD,
Volume Group: 000_00002_TLD, Action Acs: N/A, Action Lsm: N/A
11-18-2011 10:54 PM
Please check bptm log on the media server for the reason for this error: "Error bptm(pid=1476) error requesting media, TpErrno = Robot operation failed "
VERBOSE entry in vm.conf of media server will also help to see what exactly happened at Media Manager level during mount request (NBU needs to be restarted to enable VERBOSE logging). These logs will be written to Windows Event Viewer Application log. If Unix, to syslog.
Seems you are going to battle like this with each and every restore that you need to perform from the old media.
Two suggestions: Log a call with Support and request a Webex session to see if the support can 'see' something that we don't.
Otherwise, use this problem as motivation to purchase/rent a standalone tape drive to accommodate restores from old media.
11-19-2011 03:12 PM
Hi
Looking at your output your old library reported all 8 digits of the barcode but it looks like you new one only reports 6
You may be able to change a setting on the library to report all of the 8 digits (some libraries call it short barcode setting)
If not then you are stuck with it and the only real way around it is to change the barcode record in the database when you come to do restores (you will also need to delete all expired media and then next time you put it in the library label it using bplabel from the command line so that you re-write the header on the tape with the new media id.
For now, and for your restore try the following, firstly you need to delete NV5623 and then run:
program files\veritas\volmgr\bin\vmchange -h <emmservername> -barcode NV5623 -m 5623L3
This changes NetBackup so that it now knows that media id 5623L3 has a barcode of NV5623
Your restore should then work
You obviously have some sorting out to do with all of the other tapes if your new library wont go back to using long barcodes
Hope this helps
12-08-2011 08:17 AM
Hi Mark_Solutions,
Thanks for the reply but that didn't work as per my initial thread.
Thanks Marianne for the great help though it is still not resolved but the information you provided was great. Right now whenever we get the restore request we change the robot to select the last 6 chracter and run the inventory and then restore works.
Regards