This is a multi-part message in MIME format.
------=_NextPart_000_0048_01C30512.B0B0E8C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Keath,
I hit this same problem with ADIC and IBM libraries. The unfortunate =
reality is that
barcode format and reporting is not specified by the SCSI standards docs =
- it's=20
up to individual hardware and software vendors to make their own =
interpretations.
Some libraries are configurable, so check the docs for your STK or ask =
your
support channel.
You can read the gory details at http://www.t11.org/index.htm.
Another downside occurs for people using different media densities in =
the same
library, eg Ultrium 1 and 2, where the L1 and L2 suffixes are supposed =
to help
software work out which media can go in which drive. So why does NBU =
base
its barcode rules on prefixes ? ;-)
D
#
----- Original Message -----=20
From: Marx, Keath=20
To: 'veritas-bu AT mailman.eng.auburn DOT edu'=20
Sent: Thursday, April 17, 2003 3:17 PM
Subject: [Veritas-bu] Barcode labels different!
Okay,
I just traded my Dell Powervault 128t to our test lab for a =
Storagetek L40. I have one big problem. The 128t could read all 8 =
digits of the barcode. I used barcode rules to specify using the first =
6 digits. The L40 seems to only be able to read the first 6 digits =
(this is why I used the rules with the 128t. I thought this would give =
me cross compatibility) Unfortunately, now the system sees the barcode =
NN1234L1 as NN1234. The rules keep the tape ID correct but Netbackup =
tries to add them as new tapes since the barcode does not match exactly. =
I can deal with that problem from the aspect of new tapes but what can =
I do about all the tapes I already have data on?
The only thing I have come up with that would work fairly well is to =
expire ALL of my tapes then import them all (ack!)
Thanks
This message, including files attached to it, may contain confidential =
information that is intended only for the use of the ADDRESSEE(S) named =
above. If you are not an intended recipient, you are hereby notified =
that any dissemination or copying of the information contained in this =
message, or the taking of any action in reliance upon the information, =
is strictly prohibited. If you have received this message in error, =
please notify the sender immediately and delete the message from your =
system. Thank you.=20
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 10/04/2003
------=_NextPart_000_0048_01C30512.B0B0E8C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR>
<STYLE>@font-face {
font-family: Comic Sans MS;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.emailstyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
SPAN.EmailStyle18 {
FONT-FAMILY: Arial
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US vLink=3Dpurple link=3Dblue bgColor=3D#ffffff>
<DIV>
<DIV><FONT face=3DArial size=3D2>Keath,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>I hit this same problem with ADIC and =
IBM=20
libraries. The unfortunate reality is that</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>barcode format and reporting is not =
specified by=20
the SCSI standards docs - it's </FONT></DIV>
<DIV><FONT face=3DArial size=3D2>up </FONT><FONT face=3DArial =
size=3D2>to individual=20
hardware and software vendors to make their own =
interpretations.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Some libraries are configurable, so =
check the docs=20
for your STK or ask your</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>support channel.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>You can read the gory details at <A=20
href=3D"http://www.t11.org/index.htm";>http://www.t11.org/index.htm</A>.</=
FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Another downside occurs for people =
using different=20
media densities in the same</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>library, eg Ultrium 1 and 2, where the =
L1 and L2=20
suffixes are supposed to help</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>software work out which media can go in =
which=20
drive. So why does NBU base</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>its barcode rules on prefixes ? =
;-)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>D</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>#</FONT></DIV></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3DKeath.Marx AT Anthem DOT com =
href=3D"mailto:Keath.Marx AT Anthem DOT com">Marx,=20
Keath</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
title=3Dveritas-bu AT mailman.eng.auburn DOT edu=20
=
href=3D"mailto:'veritas-bu AT mailman.eng.auburn DOT
edu'">'[email protected]=
ng.auburn.edu'</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, April 17, 2003 =
3:17=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Veritas-bu] Barcode =
labels=20
different!</DIV>
<DIV><BR></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Okay,</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> I just traded my =
Dell=20
Powervault 128t to our test lab for a Storagetek L40. I have one =
big=20
problem. The 128t could read all 8 digits of the barcode. I used =
barcode=20
rules to specify using the first 6 digits. The L40 seems to only =
be able=20
to read the first 6 digits (this is why I used the rules with the =
128t. =20
I thought this would give me cross compatibility) Unfortunately, =
now the=20
system sees the barcode NN1234L1 as NN1234. The rules keep the =
tape ID=20
correct but Netbackup tries to add them as new tapes since the barcode =
does=20
not match exactly. I can deal with that problem from the aspect =
of new=20
tapes but what can I do about all the tapes I already have data=20
on?</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">The only thing I have =
come up with=20
that would work fairly well is to expire ALL of my tapes then import =
them all=20
(ack!)</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">Thanks</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><FONT face=3D"Comic =
Sans MS"=20
size=3D1><SPAN style=3D"FONT-SIZE: 7.5pt; FONT-FAMILY: 'Comic Sans =
MS'">This=20
message, including files attached to it, may contain confidential =
information=20
that is intended only for the use of the ADDRESSEE(S) named above. If =
you are=20
not an intended recipient, you are hereby notified that any =
dissemination or=20
copying of the information contained in this message, or the taking of =
any=20
action in reliance upon the information, is strictly prohibited. If =
you have=20
received this message in error, please notify the sender immediately =
and=20
delete the message from your system. Thank you.</SPAN></FONT><FONT =
face=3DArial=20
size=3D2><SPAN style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial"> =
</SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"></SPAN></FONT> </P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 12pt"><BR>---<BR>Outgoing mail is certified Virus=20
Free.<BR>Checked by AVG anti-virus system (<A=20
=
href=3D"http://www.grisoft.com";>http://www.grisoft.com</A>).<BR>Version: =
6.0.471=20
/ Virus Database: 269 - Release Date:=20
10/04/2003</SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_000_0048_01C30512.B0B0E8C0--
|
