This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C3AE7C.1483460D
Content-Type: text/plain;
charset="iso-8859-1"
Christopher,
I had simular problems with a ATL P7000 library with 5 IBM LTO1 drives.
These drives are shared by the master server and 9 other mediaservers.
I had several discussions with Veritas engineers and they said that the
order in which the drives are seen by the OS doesn' t realy matter for
Netbackup. When the device manager is started, the drive information is
taken from the registry and Netbackup takes care of this. Of course the OS
must seen all the drives.
You can check your configuration with the tpconfig -d and tpautoconf -show
command. On every server you have to check that the Netbackup drivenames
maps always to the drive with the same Serial Number and that the tapepaths
are consistent.
The drive path \\.\Tapex <file://\\.\Tapex> is only a pointer and it doesn'
t realy matter if they are in numerical order.
Example on one of the servers of my installation:
Output tpconfig -d:
Index DriveName DeviceName Type Shared Status
***** ********* ********** **** ****** ******
0 IBMULTRIUM-TD10 \\.\Tape4 <file://\\.\Tape4> hcart Yes
UP
TLD(0) Definition DRIVE=1
1 IBMULTRIUM-TD11 \\.\Tape0 <file://\\.\Tape0> hcart Yes
UP
TLD(0) Definition DRIVE=2
2 IBMULTRIUM-TD12 \\.\Tape1 <file://\\.\Tape1> hcart Yes
UP
TLD(0) Definition DRIVE=3
3 IBMULTRIUM-TD13 \\.\Tape2 <file://\\.\Tape2> hcart Yes
UP
TLD(0) Definition DRIVE=4
4 IBMULTRIUM-TD14 \\.\Tape3 <file://\\.\Tape3> hcart Yes
UP
TLD(0) Definition DRIVE=5
Output tpautoconf -show:
ATL P7000 64380513.11 5 0 0 0
Drive 1: "6811132782" IBM ULTRIUM-TD1 25D4 5 0 0 2 "Tape4"
Drive 2: "6811132755" IBM ULTRIUM-TD1 25D4 5 0 1 0 "Tape0"
Drive 3: "6811132786" IBM ULTRIUM-TD1 25D4 5 0 1 1 "Tape1"
Drive 4: "6811123976" IBM ULTRIUM-TD1 25D4 5 0 2 0 "Tape2"
Drive 5: "1010202786" IBM ULTRIUM-TD1 25D4 5 0 2 1 "Tape3"
When a server was rebooted, in most of the cases I had problems with drives
going down during backup sessions.
I assume that when a server is rebooted, the NetBackup services are started
to early, before the drives are correctly seen by the OS.
I discussed this with Veritas and they advised me to start the Netbackup
services after the drives are correctly configured. Because this is not so
easy in a windows environment, I decided to change the startup of the
services from automatically to manual and start the NetBackup services by a
script about 5 minutes after the server has been booted.
Since then I do not have problems with drives going down and I hope they are
gone for ever.
If for one or another reason, you loose drives and have to do a rescan,
always stop and start the device manager in order to take up the proper
device information.
Regards
Robert
-----Original Message-----
From: Bair, Christopher [mailto:cbair AT freemarkets DOT com]
Sent: dinsdag 18 november 2003 19:18
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Drive problem
I have a Compaq ESL9000 which is connected through a Compaq Network storage
Router M2402 which houses 8 SDLT 160/320 drives. The problem I am seeing is
this. When the OS finds these drives (win2k sp4), it is finding them out of
order. That is, the LUN's are not ordered the same as they are in the
storage router or library. What this does is causes the software (netbackup
datacenter 4.5 MP3) to see the drives out of order. This in turn is causing
the drives to go down periodically with the following in the error logs:
Fatal open error on COMPAQSDLT3204 (device 4, \\.\Tape6): The system cannot
find the file specified. DOWN'ing it
As of last week, I had 6 drives in the library, and the system did not have
this problem. Adding the additional drives is causing this strange behavior,
and I was hoping that someone might be able to offer some help.
------_=_NextPart_001_01C3AE7C.1483460D
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40"; xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2800.1106" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:[email protected]" rel=3DFile-List><!--[if gte =
mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:EnvelopeVis/>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {
font-family: MS Shell Dlg;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; =
mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; =
}
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: =
personal-compose; mso-style-noshow: yes; mso-ansi-font-size: 10.0pt; =
mso-bidi-font-size: 10.0pt; mso-ascii-font-family: Arial; =
mso-hansi-font-family: Arial; mso-bidi-font-family: Arial
}
SPAN.SpellE {
mso-style-name: ""; mso-spl-e: yes
}
SPAN.GramE {
mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Christopher,</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>I had=20
simular problems with a ATL P7000 library with 5 IBM LTO1 drives. These =
drives=20
are shared by the master server and 9 other =
mediaservers.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>I had=20
several discussions with Veritas engineers and they said that the order =
in which=20
the drives are seen by the OS doesn' t realy matter for Netbackup. When =
the=20
device manager is started, the drive information is taken from the =
registry and=20
Netbackup takes care of this. Of course the OS must seen all the=20
drives.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>You=20
can check your configuration with the tpconfig -d and tpautoconf -show =
command.=20
On every server you have to check that the Netbackup drivenames maps =
always to=20
the drive with the same Serial Number and that the tapepaths are =
consistent.=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>The=20
drive path <A href=3D"file://\\.\Tapex">\\.\Tapex</A> is only a pointer =
and it=20
doesn' t realy matter if they are in numerical =
order.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2> </FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Example on one of the servers of my =
installation:</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2> Output tpconfig -d:</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2> =20
Index=20
DriveName &nb=
sp; =20
DeviceName Type Shared =
Status<BR>*****=20
********* &nb=
sp; =20
********** **** ****** =
******<BR> =20
0 =20
IBMULTRIUM-TD10 &nb=
sp; <A=20
href=3D"file://\\.\Tape4">\\.\Tape4</A> =
hcart =20
Yes UP<BR> TLD(0) =
Definition DRIVE=3D1=20
<BR> 1 =20
IBMULTRIUM-TD11 &nb=
sp; <A=20
href=3D"file://\\.\Tape0">\\.\Tape0</A> =
hcart =20
Yes UP<BR> TLD(0) =
Definition DRIVE=3D2=20
<BR> 2 =20
IBMULTRIUM-TD12 &nb=
sp; <A=20
href=3D"file://\\.\Tape1">\\.\Tape1</A> =
hcart =20
Yes UP<BR> TLD(0) =
Definition DRIVE=3D3=20
<BR> 3 =20
IBMULTRIUM-TD13 &nb=
sp; <A=20
href=3D"file://\\.\Tape2">\\.\Tape2</A> =
hcart =20
Yes UP<BR> TLD(0) =
Definition DRIVE=3D4=20
<BR> 4 =20
IBMULTRIUM-TD14 &nb=
sp; <A=20
href=3D"file://\\.\Tape3">\\.\Tape3</A> =
hcart =20
Yes UP<BR> TLD(0) =
Definition DRIVE=3D5=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>Output=20
tpautoconf -show: </FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2><BR>ATL P7000 =
64380513.11 5 0 0=20
0 <BR> Drive 1: "6811132782"=20
IBM ULTRIUM-TD1 25D4 5 =
0 0 2=20
"Tape4"<BR> Drive 2: "6811132755"=20
IBM ULTRIUM-TD1 25D4 5 =
0 1 0=20
"Tape0"<BR> Drive 3: "6811132786"=20
IBM ULTRIUM-TD1 25D4 5 =
0 1 1=20
"Tape1"<BR> Drive 4: "6811123976"=20
IBM ULTRIUM-TD1 25D4 5 =
0 2 0=20
"Tape2"<BR> Drive 5: "1010202786"=20
IBM ULTRIUM-TD1 25D4 5 =
0 2 1=20
"Tape3"<BR></FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2> </FONT></SPAN><SPAN class=3D725561308-19112003><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>When a=20
server was rebooted, in most of the cases I had problems with drives =
going down=20
during backup sessions. </FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
assume that when a server is rebooted, the NetBackup services are =
started to=20
early, before the drives are correctly seen by the =
OS.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
discussed this with Veritas and they advised me to start the Netbackup =
services=20
after the drives are correctly configured. Because this is not so easy =
in a=20
windows environment, I decided to change the startup of the services =
from=20
automatically to manual and</FONT></SPAN><SPAN =
class=3D725561308-19112003><FONT=20
face=3DArial color=3D#0000ff size=3D2> start the NetBackup services by =
a script about=20
5 minutes after the server has been booted.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>Since=20
then I do not have problems with drives going down and I hope they are =
gone for=20
ever.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff size=3D2>If for=20
one or another reason, you loose drives and have to do a rescan, always =
stop and=20
start the device manager in order to take up the proper device=20
information.</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Regards</FONT></SPAN></DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN> </DIV>
<DIV><SPAN class=3D725561308-19112003><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>Robert</DIV>
<DIV><BR></DIV></FONT></SPAN>
<BLOCKQUOTE dir=3Dltr style=3D"MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
size=3D2>-----Original Message-----<BR><B>From:</B> Bair, Christopher =
[mailto:cbair AT freemarkets DOT com]<BR><B>Sent:</B> dinsdag 18 november =
2003=20
19:18<BR><B>To:</B> =
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B>=20
[Veritas-bu] Drive problem<BR><BR></FONT></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">I have a Compaq ESL9000 =
which is=20
connected through <SPAN class=3DGramE>a Compaq</SPAN> Network storage =
Router=20
M2402 which houses 8 SDLT 160/320 drives. The problem I am seeing is =
this.=20
When the OS finds these drives (win2k sp4), it is finding them out of =
order.=20
That is, the <SPAN class=3DSpellE>LUN's</SPAN> are not ordered the =
same as they=20
are in the storage router or library. What this does is causes the =
software=20
(<SPAN class=3DSpellE>netbackup</SPAN> datacenter 4.5 MP3) to see the =
drives out=20
of order. This in turn is causing the drives to go down periodically =
with the=20
following in the error logs:<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: =
Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"MS Shell Dlg" size=3D1><SPAN=20
style=3D"FONT-SIZE: 8.5pt; FONT-FAMILY: 'MS Shell Dlg'">Fatal open =
error on=20
COMPAQSDLT3204 (device 4, \\.\Tape6): The system cannot find the file =
specified.<SPAN style=3D"mso-spacerun: yes"> </SPAN><SPAN=20
class=3DSpellE>DOWN'ing</SPAN> it<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3D"MS Shell Dlg" size=3D1><SPAN=20
style=3D"FONT-SIZE: 8.5pt; FONT-FAMILY: 'MS Shell =
Dlg'"><o:p> </o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial">As of last week, I had =
6 drives in=20
the library, and the system did not have this problem. Adding the =
additional=20
drives is causing this strange behavior, and I was hoping that =
someone might=20
be able to offer some=20
help.<o:p></o:p></SPAN></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C3AE7C.1483460D--
|
