Re: [Veritas-bu] Media ID not UNIQUE in DataBase (34)
Another option is to just print your own barcode labels. I use GNU barcode to generate the labels, as described here: http://community.spiceworks.com/how_to/show/36086-creating-your-own-lto-labels It says "LTO" but I'm 99% sure that DLT uses the same labeling. I ended up with the following command. The command is all one line, but i've commented each line here: barcode -i LABELNAMEFILE -o POSTSCRIPTOUTPUTFILE.PS # encoding #39 is a barcode standard -e 39 # inches -u in # geometry width x height +/- xmargin +/- ymargin (size of each label) -g 2.5x0.625 # table geometry columns x lines + leftmargin + bottommargin -rightmargin -topmargin -t 1x15+.25+0.5-4.35-0.5 # margin between cells in the table -m .1 # page size -p 8x11 # no checksum character, for codes which allow it (such as #39) -c The list of label text needs to be the LABELNAMEFILE, just one per line like this: 01L4 02L4 ...etc The label size i chose is a bit too small. 2.75x0.625 or maybe even 3x0.625 would be better. Looks like the original link used 3x0.625. I know I made it smaller on purpose, so experiment with plain paper and check the size before you print a bunch of labels. It doesn't like blank lines in the LABELNAME file. I print on full-sheet sticky labels and cut them up. The link above shows a particular label that works, but i was in a hurry and this is what I had. jtwemlow October 10, 2013 9:41 AM Hi, whilst the barcodes are 8 characters long, NetBackup uses just 6 characters as its media ID. So tape GJW998L4 has a media id of W998L4 and tape LXW998L4 will also have the media id of W998L4. When you inventory a robot, via the advanced options you can create Media ID generation rules. You should define that barcodes are 8 characters, and that you will use the first 6 characters from the left hand side, e.g GJW998L4 would have id GJW998 and LXW998L4 would have LXW998 which would be unique.The problem with implemeting a rule after media has been used if that the media id is also written to the tape, if you implement the rule the media id read from the library will not match what is on the tape. So you need to be careful just implementing rules on the fly.There are TECH docs on the Symantec website that detail changing the lable on media.Hope this helps (hope this makes sence).Cheers James+--|This was sent by jtwem...@sch-group.net via Backup Central.|Forward SPAM to ab...@backupcentral.com.+--___Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Dan PrittsICPSR Computing Network ServicesUniversity of Michigan+1 (734)615-7362 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Media ID not UNIQUE in DataBase (34)
The barcode and mediaID are entirely separate entities. Even though your barcodes are different, NetBackup automatically generates the same mediaID for both media (GJW998L4 and LXW998L4 both look like W998L4 to NetBackup). I suggest you create a mediaID generation rule for 8 character barcodes with 1:2:3:4:5:6. This will create new mediaIDs for the LX media, but still recognize the GJ media when you put it in the library. -Jonathan From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Simon Weaver Sent: Thursday, June 13, 2013 10:12 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Media ID not UNIQUE in DataBase (34) All I really need some help or advice here, as I am struggling to understand the issue. We have no specific barcode rules setup, just using DEFAULT For 4 years, we have been running trouble free, ordering tapes and labels. This week, we received an error loading blank tapes. NetBackup reports that the Media ID is not unique in the Database (34). Checking the Barcode's they are different. The current one in the library and known to NetBackup is W998L4 and the actual Barcode is GJW998L4. But the tapes I am trying to import into the library have the same Media ID W998L4, yet the Barcode is LXW998L4. The problem is, majority of the tapes in the library are W9xxL4 and the pack of labels is the same! Has anyone seen this before? I searched the Web, found some technotes, but these tapes are brand new, never been in any other environment, and the labels are also brand new unique. Appreciate any helpful advise. Simon ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
Have you checked how the library reads the barcode labels? Have you checked your barcode rules? I had this problem: a) If I have barcode rules in place setup to read only the first 6 characters of the barcode label. Netbackup media manager shows 2 columns the barcode label with 6 characters and the other with the extended (L1 ,L2 etc.) b) If the tape library is setup to send extended barcode labels 6+ characters or standard make sure that the library barcode labels matches Netbackups media list. run vmcheckxxx -rt tld -rn 0 -rh your media server -list look at the Barcode column to see what the library send to Netbackup. __ Efrain Vargas From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 10:34 PM To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] media ID not unique in database (34) I don't' suppose its possible to right click on the media with the issue and change their locations to stand alone? I looked for a similar command line counterpart but vmchange dosen't seem to be up to the task. -Jonathan From: Randy Samora [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 10:11 PM To: Martin, Jonathan; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) That happens a lot to me as well and you're right, I run inventory again and I'm okay. But this time it's being stubborn. I've printed out a report and I'll just pull the tapes that were manually put in there and inventory them through the mail slots. I know there has to be a way to resync but I need scratch tapes now for tonight's backups but if anyone knows the answer, there's a trip to Hawaii in it for you, all expenses paid except flight, hotel, meals and drinks. How's that for incentive? From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 21:02: VIRUS ALERT! To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) Sometimes I have this issue if I move tapes that are in the library. For example Barcode 123456 is in slot 1 then I move it to slot 2 while changing media. The next time I inventory NBU complains that that media is already in the robot in slot1. In most cases running a 2nd inventory immediately following this clears up the issue. -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 6:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 09:33: VIRUS ALERT! ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
THAT'S what I was looking for; thanks Mark!! From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2008 17:16: VIRUS ALERT! To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) Do you have duplicate tape numbers? Barcode numbers? Most common reason. Otherwise, pull all the offending tapes, let your library update it's inventory, and then sync netbackup against it using the GUI or: vmupdate -rn robnum -rt robtype -rh robhost -use_barcode_rules then inject the tapes again and allow the library to inventory reupdate netbackup's inventory. -M From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 4:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 17:07: VIRUS ALERT! ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
Do you have duplicate tape numbers? Barcode numbers? Most common reason. Otherwise, pull all the offending tapes, let your library update it's inventory, and then sync netbackup against it using the GUI or: vmupdate -rn robnum -rt robtype -rh robhost -use_barcode_rules then inject the tapes again and allow the library to inventory reupdate netbackup's inventory. -M From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 4:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
And for the geezers out there (like me) that's VMUPDATE -RN not M. I tried M so many times that I cussed out one co-worker who happened to be the guy who drives our car pool so if any of you know anyone in the area that might give me a ride . . . From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, September 18, 2008 17:16: VIRUS ALERT! To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) Do you have duplicate tape numbers? Barcode numbers? Most common reason. Otherwise, pull all the offending tapes, let your library update it's inventory, and then sync netbackup against it using the GUI or: vmupdate -rn robnum -rt robtype -rh robhost -use_barcode_rules then inject the tapes again and allow the library to inventory reupdate netbackup's inventory. -M From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 4:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 17:07: VIRUS ALERT! ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
If the tapes are not assigned, delete them then rerun the inventory. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: 17 September 2008 23:57 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
They are assigned and I'm going through and expiring them and then deleting them. I was hoping for a quicker way. From: Patrick [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 18:25: VIRUS ALERT! To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) If the tapes are not assigned, delete them then rerun the inventory. Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. [EMAIL PROTECTED] From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: 17 September 2008 23:57 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 09:33: VIRUS ALERT! ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
On Wed, Sep 17, 2008 at 06:28:37PM -0500, Randy Samora wrote: They are assigned and I'm going through and expiring them and then deleting them. I was hoping for a quicker way. These are *new* tapes? Why would you need to expire them? They shouldn't have any data. You didn't get a batch of tapes with duplicate barcodes did you? -- Darren ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
Sometimes I have this issue if I move tapes that are in the library. For example Barcode 123456 is in slot 1 then I move it to slot 2 while changing media. The next time I inventory NBU complains that that media is already in the robot in slot1. In most cases running a 2nd inventory immediately following this clears up the issue. -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 6:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
That happens a lot to me as well and you're right, I run inventory again and I'm okay. But this time it's being stubborn. I've printed out a report and I'll just pull the tapes that were manually put in there and inventory them through the mail slots. I know there has to be a way to resync but I need scratch tapes now for tonight's backups but if anyone knows the answer, there's a trip to Hawaii in it for you, all expenses paid except flight, hotel, meals and drinks. How's that for incentive? From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 21:02: VIRUS ALERT! To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) Sometimes I have this issue if I move tapes that are in the library. For example Barcode 123456 is in slot 1 then I move it to slot 2 while changing media. The next time I inventory NBU complains that that media is already in the robot in slot1. In most cases running a 2nd inventory immediately following this clears up the issue. -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 6:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 09:33: VIRUS ALERT! ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] media ID not unique in database (34)
I don't' suppose its possible to right click on the media with the issue and change their locations to stand alone? I looked for a similar command line counterpart but vmchange dosen't seem to be up to the task. -Jonathan From: Randy Samora [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 10:11 PM To: Martin, Jonathan; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) That happens a lot to me as well and you're right, I run inventory again and I'm okay. But this time it's being stubborn. I've printed out a report and I'll just pull the tapes that were manually put in there and inventory them through the mail slots. I know there has to be a way to resync but I need scratch tapes now for tonight's backups but if anyone knows the answer, there's a trip to Hawaii in it for you, all expenses paid except flight, hotel, meals and drinks. How's that for incentive? From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 21:02: VIRUS ALERT! To: Randy Samora; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] media ID not unique in database (34) Sometimes I have this issue if I move tapes that are in the library. For example Barcode 123456 is in slot 1 then I move it to slot 2 while changing media. The next time I inventory NBU complains that that media is already in the robot in slot1. In most cases running a 2nd inventory immediately following this clears up the issue. -Jonathan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent: Wednesday, September 17, 2008 6:57 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] media ID not unique in database (34) My tape dude didn't want to inventory new tapes into the library 54 at a time so he opened the door and inserted 200 tapes. When I try to run an inventory now, I get media ID not unique in database (34).If I run a comparison, the robot inventory shows the new tapes but the Volume Configuration does not and so I see a Mismatch - Yes. But if I try to update the volume configuration, that's when I get the Status 34. I've rebooted the library but the library already knows what's in the library. How do I get NetBackup updated? This is a Windows environment running NBU 6.0 MP5. Thanks Randy No virus found in this incoming message. Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus Database: 270.6.21/1676 - Release Date: 9/17/2008 09:33: VIRUS ALERT! ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
