Veritas-bu

[Veritas-bu] Netbackup not seeing correct Barcode Label

2007-04-02 14:06:34
Subject: [Veritas-bu] Netbackup not seeing correct Barcode Label
From: Brandon.Zermeno at Pulte.com (Brandon Zermeno)
Date: Mon, 2 Apr 2007 11:06:34 -0700
I have 2 of the PX502's and I found it was just easier to create barcode
rules to force it to read the first 6 characters from the left. Under
media ID generation I have the barcode length of 8 and the rule is
1:2:3:4:5:6  That way it leave off the L3 on the end.

 

 

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
Sponsler, Michael
Sent: Tuesday, March 27, 2007 3:10 PM
To: Jones, Courtenay; Veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Netbackup not seeing correct Barcode Label

 

Yup.  Rebooted the jukebox (PX510), and rebooted the master server just
for good measure.  No barcode rules or media id generation rules.

 

I'm pretty dumbfounded.

 

Doing a search for 00Q100 on my PX510 web admin console (for both
barcode and media id) gives me nada.  Searching for Q10000 tells me
where the tape is.

 

--

Mike

 

 

 

________________________________

From: Jones, Courtenay [mailto:courtenay.jones at StockSupply.com] 
Sent: Tuesday, March 27, 2007 5:49 PM
To: Sponsler, Michael; Veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Netbackup not seeing correct Barcode Label

Have you checked your barcode rules to make sure no one has made any
changes?

 

Regards,

 

-cj

Courtenay Jones

UNIX Systems Engineer, Raleigh Technology Centre

 

 

________________________________

From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
Sponsler, Michael
Sent: Tuesday, March 27, 2007 5:27 PM
To: Veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Netbackup not seeing correct Barcode Label

Netbackup 6.0, MP4.
Master server Solaris 10 connected to a PX510 SDLT600 via a fibre SAN.
Media
servers on san, connected to PX510 via shared storage: Suse Enterprise
Linux
(two servers).

The problem:
The physical labels on the tapes are Q10000 -> Q10014.  The PX510 sees
the
tapes correctly, such as Q10000 (verified by the PX510 web admin
console).
 When a vmcheckxxx or vmupdate is run on the robot, the tapes come in as
"Barcode" 10Q100 -> 14Q100.  Thus, the generated Media ID is also 10Q100
-> 14Q100.  When a backup job goes to run, and say it requests tape
10Q100
it will return an error 98, media resource request failed.

The PX510 responds to Netbackup saying "10Q100" does not exist.  The
PX510
sees the tapes as Q10000 -> Q10014.  No Media ID generation rules or
barcode
rules are in place.  The robot and drive definitions were deleted, and
recreated.
 I recreated them on the master server only, on one of the media servers
only, and I also tried changing the robot number from 53 to 56.  The
PX510
/ Netbackup setup had run, and reported tape barcodes correctly before
hand.
 The problem just "appeared" one day.  I was getting error 96's, assumed
someone did a tape change (I am the netbackup admin of a netbackup
network
that exists in the UK, and I am in the US) and ran in inventory update.
The tapes changed from Q10000 to 00Q100, etc...

Any ideas? 

 

-- 
Mike Sponsler 
Northrop Grumman 
Michael.Sponsler at ngc.com
 
CONFIDENTIALITY NOTICE:  This email may contain confidential and privileged 
material for the sole use of the intended recipient(s).  Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately by 
email and delete the message and any file attachments from your computer.  
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20070402/1abf1411/attachment.html

<Prev in Thread] Current Thread [Next in Thread>