This is a multi-part message in MIME format.
------_=_NextPart_001_01C5B876.D8CA27CE
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Yea I made a mistake about the disk staging. I was working on 2 problems
and said in my message here that I was using disk staging for ndmp. I am
not. They are direct attached like you say. Sorry. I will try the other
steps to see if there is any issues.
Thanks,
Greg
_____ =20
From: Kevin Smallwood [mailto:kevin73 AT phoenixpyre DOT net]=20
Sent: Tuesday, September 13, 2005 10:38 AM
To: Hindle, Greg; veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] 99 errors
NDMP by design cannot use disk staging. How do you have this configured?
NDMP based backups have direct attached drives connected to the NAS
device. Status 99 is a "NDMP Halt" error - it is a very generic error -
so its difficult to determine what is causing it. Since you say it just
started happening today, check the NDMP logs on the master as well as on
the NAS device (if that logging is turned on). Also use set_ndmp_attr
-verify on the master to determine if those NAS devices are properly
authenticating with the master. It could also be a batch of bad media
causing media write time outs, but since this is NDMP and not a standard
backup, its showing a Status 99 rather than a 14 or 84.
-----Original Message-----
From: Hindle, Greg [mailto:Greg.Hindle AT constellation DOT com]
Sent: Tuesday, September 13, 2005 08:36 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] 99 errors
=09
=09
NBU 5.0 mp3 on Solaris. Need your help again. I am getting 99
errors on allot of things today. Usually we get one or two a week but
today I have more. The 99 errors deal with NDMP and some of these
reference a tape and that tapes gets frozen but I have a few that go to
disk staging and do not use tape. I know that 99 basically says that
path does not exist to be backed up. But could there be another reason
why this happens? What should I be looking at other then the obvious
(looking for the path that is to be backed up).=20
Thanks!=20
Greg=20
=20
=20
>>> The information contained in this e-mail transmission is
privileged and/or
confidential intended solely for the exclusive use of the
individual addressee.
If you are not the intended addressee you are hereby notified
that any
retention, disclosure or other use is strictly prohibited. If
you have received
this notification in error, please immediately contact the
sender and delete
the material. CEG-IP2
------_=_NextPart_001_01C5B876.D8CA27CE
Content-Type: text/html;
charset="us-ascii"
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=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2180" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D996401415-13092005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Yea I made a mistake about the disk =
staging. I was=20
working on 2 problems and said in my message here that I was using disk =
staging=20
for ndmp. I am not. They are direct attached like you say. Sorry. =
I will=20
try the other steps to see if there is any issues.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D996401415-13092005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Thanks,</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D996401415-13092005><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Greg</FONT></SPAN></DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> Kevin Smallwood=20
[mailto:kevin73 AT phoenixpyre DOT net] <BR><B>Sent:</B> Tuesday, September 13,
=
2005=20
10:38 AM<BR><B>To:</B> Hindle, Greg;=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> Re: [Veritas-bu] 99
=
errors<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>NDMP by design cannot use disk staging. How do you have this =
configured?=20
NDMP based backups have direct attached drives connected to the NAS =
device.=20
Status 99 is a "NDMP Halt" error - it is a very generic error - so its =
difficult=20
to determine what is causing it. Since you say it just started happening =
today,=20
check the NDMP logs on the master as well as on the NAS device (if that =
logging=20
is turned on). Also use set_ndmp_attr -verify on the master to determine =
if=20
those NAS devices are properly authenticating with the master. It could =
also be=20
a batch of bad media causing media write time outs, but since this is =
NDMP and=20
not a standard backup, its showing a Status 99 rather than a 14 or=20
84.<BR><BR><BR></DIV>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: rgb(0,0,255) =
2px solid; MARGIN-RIGHT: 0px"><FONT=20
face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B> =
Hindle, Greg=20
[mailto:Greg.Hindle AT constellation DOT com]<BR><B>Sent:</B> Tuesday, =
September 13,=20
2005 08:36 AM<BR><B>To:</B>=20
veritas-bu AT mailman.eng.auburn DOT edu<BR><B>Subject:</B> [Veritas-bu] 99=20
errors<BR><BR></FONT><!-- Converted from text/rtf format -->
<P><FONT face=3DArial size=3D2>NBU 5.0 mp3 on Solaris. Need your help =
again. I am=20
getting 99 errors on allot of things today. Usually we get one or two =
a week=20
but today I have more. The 99 errors deal with NDMP and some of these=20
reference a tape and that tapes gets frozen but I have a few that go =
to disk=20
staging and do not use tape. I know that 99 basically says that path =
does not=20
exist to be backed up. But could there be another reason why this =
happens?=20
What should I be looking at other then the obvious (looking for the =
path that=20
is to be backed up). </FONT></P>
<P><FONT face=3DArial> Thanks!</FONT> <BR><FONT face=3DArial=20
size=3D2>Greg</FONT> <BR><FONT face=3DArial> </FONT> <BR><FONT=20
face=3DArial> </FONT> </P><PRE>>>> The information =
contained in this e-mail transmission is privileged and/or
confidential intended solely for the exclusive use of the individual =
addressee.
If you are not the intended addressee you are hereby notified that any
retention, disclosure or other use is strictly prohibited. If you have =
received
this notification in error, please immediately contact the sender and =
delete
the material. CEG-IP2
</PRE></BLOCKQUOTE></BODY></HTML>
------_=_NextPart_001_01C5B876.D8CA27CE--
|
