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_01C2BB37.CDB2AEB0
Content-Type: text/plain
Are you using persistent binding on the tape drive addresses? Is it
possible your fabric reinitialized & readdressed your drives creating a
drive address to drive index problem?
-M
-----Original Message-----
From: Greenberg, Katherine A [mailto:GreenbergKA AT aetna DOT com]
Sent: Monday, January 13, 2003 11:59 AM
To: 'Quarantine'; Auburn_list (E-mail)
Subject: RE: [Veritas-bu] Drives down NBU 4.5 MP2
I need to clarify a few things....
1) Everything was working fine until this morning.
2) Nothing changed in the environment this morning.
3) SSO Tape drives in NetBackup 4.5 do not act the same way they did in 3.4.
If a drive goes down on one server, unless another server is having specific
issues with THAT drive, it will not get down'ed there as well.
4) I've Up'ped the drives about 15 times today, run a test backup
specifically using the Master's STU and the drives go right back down again.
Thanks for the thoughts so far :) Keep 'em coming!
~Kate :)
-----Original Message-----
From: Quarantine [mailto:Quarantine AT GSCCCA DOT ORG]
Sent: Monday, January 13, 2003 1:54 PM
To: Greenberg, Katherine A; Auburn_list (E-mail)
Subject: RE: [Veritas-bu] Drives down NBU 4.5 MP2
I've been seeing a similar problem. I have 4 FC drives (STK9840) and 3
servers (Win2K with NBU 4.5 MP2). Intermittantly, I'll see between 1 and 4
drives down for specific servers. The problem occurs for all servers, and
other servers are able to write to the down drive. For example, I may see
drive 1 down on server 1, drive 3 down on server 2 and drive 2 down on
server 3. I haven't been able to figure out a pattern yet. I can up the
drives on the individual servers, and things work fine until the next time
NetBackup decides to down the drives. Oddly enough, the problem has cleared
up over the past few weeks without my doing anything of which I'm aware.
Matt
-----Original Message-----
From: Greenberg, Katherine A [mailto:GreenbergKA AT aetna DOT com]
Sent: Monday, January 13, 2003 1:33 PM
To: Auburn_list (E-mail)
Subject: [Veritas-bu] Drives down NBU 4.5 MP2
Hey all,
I'm wondering if anyone has ever seen this before....
I have a library with 8 fibre (SAN) attached tape drives (IBM 3590E1A). The
drives are fine and working and using robtest I can load and unload them. mt
commands come back and say, yeah! there's a tape in there. However, when I
try to run backups, the drives get DOWN'ED with a messages in
/var/adm/messages of "Unable to Open Drive". And it's not only ONE drive,
it just goes down the Index list, attempts a mount, fails and downs the
drive.
Now the above would give me pause if this were happening on ALL the servers
in the environment. however, this is only happening on the Master. So, for
all intents and purposes, backups are completing successfully b/c there are
other boxes clients can use to back them up. The only thing that is
consistently failing are catalog backups...
Any thoughts, help, etc. are appreciated.
Regards!
Kate
Katherine Greenberg
Systems Engineer
Mid-Range Storage Management
Aetna, Inc.
bensonka AT aetna DOT com
860.636.6724
This e-mail, including attachments, is intended for the exclusive use of the
person or entity to which it is addressed and may contain confidential or
privileged information. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified that
any dissemination, distribution or copying of this e-mail is prohibited. If
you think that you have received this e-mail in error, please advise the
sender by reply e-mail of the error and then delete this e-mail immediately.
Thank you. Aetna
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This e-mail, including attachments, is intended for the exclusive use of the
person or entity to which it is addressed and may contain confidential or
privileged information. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified that
any dissemination, distribution or copying of this e-mail is prohibited. If
you think that you have received this e-mail in error, please advise the
sender by reply e-mail of the error and then delete this e-mail immediately.
Thank you. Aetna
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
------_=_NextPart_001_01C2BB37.CDB2AEB0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DUS-ASCII">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Veritas-bu] Drives down NBU 4.5 MP2</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Are you using persistent binding on the tape drive =
addresses? Is it possible your fabric reinitialized & =
readdressed your drives creating a drive address to drive index =
problem?</FONT></P>
<P><FONT SIZE=3D2>-M</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Greenberg, Katherine A [<A =
HREF=3D"mailto:GreenbergKA AT aetna DOT com">mailto:GreenbergKA AT aetna DOT
com</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 13, 2003 11:59 AM</FONT>
<BR><FONT SIZE=3D2>To: 'Quarantine'; Auburn_list (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Drives down NBU 4.5 =
MP2</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I need to clarify a few things....</FONT>
</P>
<P><FONT SIZE=3D2>1) Everything was working fine until this =
morning.</FONT>
<BR><FONT SIZE=3D2>2) Nothing changed in the environment this =
morning.</FONT>
<BR><FONT SIZE=3D2>3) SSO Tape drives in NetBackup 4.5 do not act the =
same way they did in 3.4.</FONT>
<BR><FONT SIZE=3D2>If a drive goes down on one server, unless another =
server is having specific</FONT>
<BR><FONT SIZE=3D2>issues with THAT drive, it will not get down'ed =
there as well.</FONT>
<BR><FONT SIZE=3D2>4) I've Up'ped the drives about 15 times today, run =
a test backup</FONT>
<BR><FONT SIZE=3D2>specifically using the Master's STU and the drives =
go right back down again.</FONT>
</P>
<P><FONT SIZE=3D2>Thanks for the thoughts so far :) Keep 'em =
coming!</FONT>
</P>
<P><FONT SIZE=3D2>~Kate :)</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Quarantine [<A =
HREF=3D"mailto:Quarantine AT GSCCCA DOT ORG">mailto:Quarantine AT GSCCCA DOT
ORG</A>]<=
/FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 13, 2003 1:54 PM</FONT>
<BR><FONT SIZE=3D2>To: Greenberg, Katherine A; Auburn_list =
(E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] Drives down NBU 4.5 =
MP2</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>I've been seeing a similar problem. I have 4 FC =
drives (STK9840) and 3</FONT>
<BR><FONT SIZE=3D2>servers (Win2K with NBU 4.5 MP2). =
Intermittantly, I'll see between 1 and 4</FONT>
<BR><FONT SIZE=3D2>drives down for specific servers. The problem =
occurs for all servers, and</FONT>
<BR><FONT SIZE=3D2>other servers are able to write to the down =
drive. For example, I may see</FONT>
<BR><FONT SIZE=3D2>drive 1 down on server 1, drive 3 down on server 2 =
and drive 2 down on</FONT>
<BR><FONT SIZE=3D2>server 3. I haven't been able to figure out a =
pattern yet. I can up the</FONT>
<BR><FONT SIZE=3D2>drives on the individual servers, and things work =
fine until the next time</FONT>
<BR><FONT SIZE=3D2>NetBackup decides to down the drives. Oddly =
enough, the problem has cleared</FONT>
<BR><FONT SIZE=3D2>up over the past few weeks without my doing anything =
of which I'm aware.</FONT>
</P>
<P><FONT SIZE=3D2>Matt</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Greenberg, Katherine A [<A =
HREF=3D"mailto:GreenbergKA AT aetna DOT com">mailto:GreenbergKA AT aetna DOT
com</A>] =
</FONT>
<BR><FONT SIZE=3D2>Sent: Monday, January 13, 2003 1:33 PM</FONT>
<BR><FONT SIZE=3D2>To: Auburn_list (E-mail)</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] Drives down NBU 4.5 MP2</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Hey all,</FONT>
</P>
<P><FONT SIZE=3D2>I'm wondering if anyone has ever seen this =
before....</FONT>
</P>
<P><FONT SIZE=3D2>I have a library with 8 fibre (SAN) attached tape =
drives (IBM 3590E1A). The</FONT>
<BR><FONT SIZE=3D2>drives are fine and working and using robtest I can =
load and unload them. mt</FONT>
<BR><FONT SIZE=3D2>commands come back and say, yeah! there's a tape in =
there. However, when I</FONT>
<BR><FONT SIZE=3D2>try to run backups, the drives get DOWN'ED with a =
messages in</FONT>
<BR><FONT SIZE=3D2>/var/adm/messages of "Unable to Open =
Drive". And it's not only ONE drive,</FONT>
<BR><FONT SIZE=3D2>it just goes down the Index list, attempts a mount, =
fails and downs the</FONT>
<BR><FONT SIZE=3D2>drive.</FONT>
</P>
<P><FONT SIZE=3D2>Now the above would give me pause if this were =
happening on ALL the servers</FONT>
<BR><FONT SIZE=3D2>in the environment. however, this is only happening =
on the Master. So, for</FONT>
<BR><FONT SIZE=3D2>all intents and purposes, backups are completing =
successfully b/c there are</FONT>
<BR><FONT SIZE=3D2>other boxes clients can use to back them up. The =
only thing that is</FONT>
<BR><FONT SIZE=3D2>consistently failing are catalog backups...</FONT>
</P>
<P><FONT SIZE=3D2>Any thoughts, help, etc. are appreciated.</FONT>
</P>
<P><FONT SIZE=3D2>Regards!</FONT>
<BR><FONT SIZE=3D2>Kate</FONT>
</P>
<P><FONT SIZE=3D2>Katherine Greenberg</FONT>
<BR><FONT SIZE=3D2>Systems Engineer</FONT>
<BR><FONT SIZE=3D2>Mid-Range Storage Management</FONT>
<BR><FONT SIZE=3D2>Aetna, Inc.</FONT>
<BR><FONT SIZE=3D2>bensonka AT aetna DOT com</FONT>
<BR><FONT SIZE=3D2>860.636.6724</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>This e-mail, including attachments, is intended for =
the exclusive use of the</FONT>
<BR><FONT SIZE=3D2>person or entity to which it is addressed and may =
contain confidential or</FONT>
<BR><FONT SIZE=3D2>privileged information. If the reader of this =
e-mail is not the intended</FONT>
<BR><FONT SIZE=3D2>recipient or his or her authorized agent, the reader =
is hereby notified that</FONT>
<BR><FONT SIZE=3D2>any dissemination, distribution or copying of this =
e-mail is prohibited. If</FONT>
<BR><FONT SIZE=3D2>you think that you have received this e-mail in =
error, please advise the</FONT>
<BR><FONT SIZE=3D2>sender by reply e-mail of the error and then delete =
this e-mail immediately.</FONT>
<BR><FONT SIZE=3D2>Thank you. Aetna</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
<P><FONT SIZE=3D2>This e-mail, including attachments, is intended for =
the exclusive use of the</FONT>
<BR><FONT SIZE=3D2>person or entity to which it is addressed and may =
contain confidential or</FONT>
<BR><FONT SIZE=3D2>privileged information. If the reader of this =
e-mail is not the intended</FONT>
<BR><FONT SIZE=3D2>recipient or his or her authorized agent, the reader =
is hereby notified that</FONT>
<BR><FONT SIZE=3D2>any dissemination, distribution or copying of this =
e-mail is prohibited. If</FONT>
<BR><FONT SIZE=3D2>you think that you have received this e-mail in =
error, please advise the</FONT>
<BR><FONT SIZE=3D2>sender by reply e-mail of the error and then delete =
this e-mail immediately.</FONT>
<BR><FONT SIZE=3D2>Thank you. Aetna</FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu"; =
TARGET=3D"_blank">http://mailman.eng.auburn.edu/mailman/listinfo/veritas=
-bu</A></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C2BB37.CDB2AEB0--
|
