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_01C3E449.9DBB7BE2
Content-Type: text/plain
Doing the sychnronize global device DB on the media servers did not stop the
status 50 aborts.
Pauk
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of MacKinnon,
G.
R. (Gregory)
Sent: Wednesday, January 21, 2004 12:00 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] status code 50
Griese, Paul wrote:
>
> NBU 4.5 MP3 on Solaris Master, Solaris 8, Ultra-4, running about 370
> active policies; catalog DB is about 64 GB and hasn't been compressed
> lately. We have many Solaris, NT and VMS clients. A bunch of the
> clients are on a SAN. We save about 4.5 to 5.2 TB a day and we use 4
> L700 robots.
>
> Everything was running great. We went 34 days with uninterrupted
> Netbackup service at the end of the year - a record for us - we did
> not have to do any Netbackup bounces. Now everything has gone to heck.
> We can't go two days without many jobs dying with status code 50,
> always in the early morning hours, and it usually happens
> every morning. Rarely do we have a day free of these status 50 aborted
> jobs. After a few days of this, things deteriorate to the point where
> jobs just hang, can not be killed, and we wind-up having to bounce
> Netbackup. We have tried rescheduling jobs so that there are not so
> many running between midnight and 6AM, but it doesn't seem to help. We
> are actually more busy after 6AM but we don't get this rash of code
> 50s after 6AM. We have added a few more active policies in the past
> month, but we have also purged some data off of some other clients
> which has made their backup jobs run for a shorter period of time.
>
> Veritas has been little help. They have told us three different
> things: 1). Try running two Masters; 2). move your Master to a more
> powerful SUN box; 3). install MP5. They seem to imply that we have
> overloaded our SUN box Master, but the uptime and top commands don't
> show excessive load on CPU or memory.
>
> We are going to try installing MP5. The release notes mention error
> code 50, but it relates to "queued vault job receives a status 50"
> which is not exactly our problem. We run Vault in the afternoon
> and they do not have the status 50 problem. The problem resides with
> our nornal backups, not Vault.
>
> So, has anybody had an experience like this? Did MP5 help? Is an
> Ultra-4 not powerful enough for our environment?
>
>
> Paul Griese
> System Management
> 713-331-6454
>
>
> ______________________________________________________________________
> _______
>
>
> (c) 2003 TeleCheck International, Inc. THIS DOCUMENT, AND ANY ATTACHED
> INFORMATION: 1) IS PROPRIETARY, PRIVILEGED AND CONFIDENTIAL PROPERTY
> OF TELECHECK UNDER APPLICABLE LAW, AND 2) IS INTENDED EXCLUSIVELY FOR
> INTERNAL USE BY TELECHECK EMPLOYEES AND INTENDED RECIPIENTS WITH A
> LEGITIMATE TELECHECK BUSINESS NEED THEREFORE. ITS REPRODUCTION,
> DISSEMINATION, DISTRIBUTION AND/OR DISCLOSURE, EXCEPT TO SUCH
> TELECHECK EMPLOYEES AND INTENDED RECIPIENTS, IS STRICTLY PROHIBITED .
> IF YOU ARE NOT SUCH A TELECHECK EMPLOYEE OR INTENDED RECIPIENT, OR THE
> EMPLOYEE OR AGENT RESPONSIBLE FOR DELIVERING THIS MESSAGE TO THE
> INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REPRODUCTION,
> DISSEMINATION, DISTRIBUTION AND/OR DISCLOSURE OF THIS DOCUMENT, OR ANY
> ATTACHMENTS, IS STRICTLY PROHIBITED.
>
Are you using SSO with more than 1 media server having access to the tape
drives? If so you might have to do a Synchronize Global Device Database on
the media servers. Don't know why it happens, but that seems to fix our '50'
problem.
Gregg
--
=================================================================
Gregg MacKinnon Ford Motor Co.
gmackinn AT ford DOT com 2101 Village Rd.
Technical Computing Section Rm 1116, MD 1076
(313) 594-3716 pager 7958343 Dearborn Michigan, 48124
==================================================================
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
____________________________________________________________________________
_
(c) 2003 TeleCheck International, Inc. THIS DOCUMENT, AND ANY ATTACHED
INFORMATION: 1) IS PROPRIETARY, PRIVILEGED AND CONFIDENTIAL PROPERTY OF
TELECHECK UNDER APPLICABLE LAW, AND 2) IS INTENDED EXCLUSIVELY FOR INTERNAL
USE BY TELECHECK EMPLOYEES AND INTENDED RECIPIENTS WITH A LEGITIMATE
TELECHECK BUSINESS NEED THEREFORE. ITS REPRODUCTION, DISSEMINATION,
DISTRIBUTION AND/OR DISCLOSURE, EXCEPT TO SUCH TELECHECK EMPLOYEES AND
INTENDED RECIPIENTS, IS STRICTLY PROHIBITED . IF YOU ARE NOT SUCH A
TELECHECK EMPLOYEE OR INTENDED RECIPIENT, OR THE EMPLOYEE OR AGENT
RESPONSIBLE FOR DELIVERING THIS MESSAGE TO THE INTENDED RECIPIENT, YOU ARE
HEREBY NOTIFIED THAT ANY REPRODUCTION, DISSEMINATION, DISTRIBUTION AND/OR
DISCLOSURE OF THIS DOCUMENT, OR ANY ATTACHMENTS, IS STRICTLY PROHIBITED.
------_=_NextPart_001_01C3E449.9DBB7BE2
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.2657.73">
<TITLE>RE: [Veritas-bu] status code 50</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Doing the sychnronize global device DB on the media =
servers did not stop the status 50 aborts.</FONT>
</P>
<P><FONT SIZE=3D2>Pauk</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: veritas-bu-admin AT mailman.eng.auburn DOT edu [<A =
HREF=3D"mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu">mailto:veritas-b=
u-admin AT mailman.eng.auburn DOT edu</A>] On Behalf Of MacKinnon, G. R. =
(Gregory)</FONT></P>
<P><FONT SIZE=3D2>Sent: Wednesday, January 21, 2004 12:00 PM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Veritas-bu] status code 50</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Griese, Paul wrote:</FONT>
</P>
<P><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> NBU 4.5 MP3 on Solaris Master, Solaris 8, =
Ultra-4, running about 370</FONT>
<BR><FONT SIZE=3D2>> active policies; catalog DB is about 64 GB and =
hasn't been compressed </FONT>
<BR><FONT SIZE=3D2>> lately. We have many Solaris, NT and VMS =
clients. A bunch of the </FONT>
<BR><FONT SIZE=3D2>> clients are on a SAN. We save about 4.5 to 5.2 =
TB a day and we use 4 </FONT>
<BR><FONT SIZE=3D2>> L700 robots.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Everything was running great. We went 34 days =
with uninterrupted</FONT>
<BR><FONT SIZE=3D2>> Netbackup service at the end of the year - a =
record for us - we did </FONT>
<BR><FONT SIZE=3D2>> not have to do any Netbackup bounces. Now =
everything has gone to heck. </FONT>
<BR><FONT SIZE=3D2>> We can't go two days without many jobs dying =
with status code 50, </FONT>
<BR><FONT SIZE=3D2>> always in the early morning hours, and it =
usually happens </FONT>
<BR><FONT SIZE=3D2>> every morning. Rarely do we have a day free of =
these status 50 aborted </FONT>
<BR><FONT SIZE=3D2>> jobs. After a few days of this, things =
deteriorate to the point where </FONT>
<BR><FONT SIZE=3D2>> jobs just hang, can not be killed, and we =
wind-up having to bounce </FONT>
<BR><FONT SIZE=3D2>> Netbackup. We have tried rescheduling =
jobs so that there are not so </FONT>
<BR><FONT SIZE=3D2>> many running between midnight and 6AM, but it =
doesn't seem to help. We </FONT>
<BR><FONT SIZE=3D2>> are actually more busy after 6AM but we don't =
get this rash of code </FONT>
<BR><FONT SIZE=3D2>> 50s after 6AM. We have added a few more active =
policies in the past </FONT>
<BR><FONT SIZE=3D2>> month, but we have also purged some data off of =
some other clients </FONT>
<BR><FONT SIZE=3D2>> which has made their backup jobs run for a =
shorter period of time. </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Veritas has been little help. They have told us =
three different</FONT>
<BR><FONT SIZE=3D2>> things: 1). Try running two Masters; 2). move =
your Master to a more </FONT>
<BR><FONT SIZE=3D2>> powerful SUN box; 3). install MP5. They seem to =
imply that we have </FONT>
<BR><FONT SIZE=3D2>> overloaded our SUN box Master, but the uptime =
and top commands don't </FONT>
<BR><FONT SIZE=3D2>> show excessive load on CPU or memory.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> We are going to try installing MP5. The release =
notes mention error</FONT>
<BR><FONT SIZE=3D2>> code 50, but it relates to "queued vault =
job receives a status 50" </FONT>
<BR><FONT SIZE=3D2>> which is not exactly our problem. We run Vault =
in the afternoon </FONT>
<BR><FONT SIZE=3D2>> and they do not have the status 50 problem. The =
problem resides with </FONT>
<BR><FONT SIZE=3D2>> our nornal backups, not Vault.</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> So, has anybody had an experience like this? =
Did MP5 help? Is an</FONT>
<BR><FONT SIZE=3D2>> Ultra-4 not powerful enough for our =
environment?</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Paul Griese</FONT>
<BR><FONT SIZE=3D2>> System Management</FONT>
<BR><FONT SIZE=3D2>> 713-331-6454</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> =
______________________________________________________________________</=
FONT>
<BR><FONT SIZE=3D2>> _______</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> (c) 2003 TeleCheck International, Inc. THIS =
DOCUMENT, AND ANY ATTACHED</FONT>
<BR><FONT SIZE=3D2>> INFORMATION: 1) IS PROPRIETARY, PRIVILEGED AND =
CONFIDENTIAL PROPERTY </FONT>
<BR><FONT SIZE=3D2>> OF TELECHECK UNDER APPLICABLE LAW, AND 2) IS =
INTENDED EXCLUSIVELY FOR </FONT>
<BR><FONT SIZE=3D2>> INTERNAL USE BY TELECHECK EMPLOYEES AND =
INTENDED RECIPIENTS WITH A </FONT>
<BR><FONT SIZE=3D2>> LEGITIMATE TELECHECK BUSINESS NEED THEREFORE. =
ITS REPRODUCTION, </FONT>
<BR><FONT SIZE=3D2>> DISSEMINATION, DISTRIBUTION AND/OR DISCLOSURE, =
EXCEPT TO SUCH </FONT>
<BR><FONT SIZE=3D2>> TELECHECK EMPLOYEES AND INTENDED RECIPIENTS, IS =
STRICTLY PROHIBITED . </FONT>
<BR><FONT SIZE=3D2>> IF YOU ARE NOT SUCH A TELECHECK EMPLOYEE OR =
INTENDED RECIPIENT, OR THE </FONT>
<BR><FONT SIZE=3D2>> EMPLOYEE OR AGENT RESPONSIBLE FOR DELIVERING =
THIS MESSAGE TO THE </FONT>
<BR><FONT SIZE=3D2>> INTENDED RECIPIENT, YOU ARE HEREBY NOTIFIED =
THAT ANY REPRODUCTION, </FONT>
<BR><FONT SIZE=3D2>> DISSEMINATION, DISTRIBUTION AND/OR DISCLOSURE =
OF THIS DOCUMENT, OR ANY </FONT>
<BR><FONT SIZE=3D2>> ATTACHMENTS, IS STRICTLY PROHIBITED.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>Are you using SSO with more than 1 media server =
having access to the tape drives? If so you might have to do a =
Synchronize Global Device Database on the media servers. Don't know why =
it happens, but that seems to fix our '50' problem.</FONT></P>
<P><FONT SIZE=3D2>Gregg</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D</FONT>
<BR><FONT SIZE=3D2>Gregg MacKinnon =
=
=
Ford Motor Co.</FONT>
<BR><FONT =
SIZE=3D2>gmackinn AT ford DOT com =
=
2101 Village Rd. </FONT>
<BR><FONT SIZE=3D2>Technical Computing Section =
Rm 1116, MD =
1076 </FONT>
<BR><FONT SIZE=3D2>(313) 594-3716 pager 7958343 =
Dearborn Michigan, =
48124</FONT>
<BR><FONT =
SIZE=3D2>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D &nb=
sp; =
=
=
=
=
</FONT></P>
<BR>
<P><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Veritas-bu maillist - =
Veritas-bu AT mailman.eng.auburn DOT edu <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>
<BR><FONT =
SIZE=3D2>_______________________________________________________________=
______________</FONT>
</P>
<P><FONT SIZE=3D2>(c) 2003 TeleCheck International, Inc. THIS DOCUMENT, =
AND ANY ATTACHED INFORMATION: 1) IS PROPRIETARY, PRIVILEGED AND =
CONFIDENTIAL PROPERTY OF TELECHECK UNDER APPLICABLE LAW, AND 2) =
IS INTENDED EXCLUSIVELY FOR INTERNAL USE BY TELECHECK EMPLOYEES AND =
INTENDED RECIPIENTS WITH A LEGITIMATE TELECHECK BUSINESS NEED =
THEREFORE. ITS REPRODUCTION, DISSEMINATION, DISTRIBUTION =
AND/OR DISCLOSURE, EXCEPT TO SUCH TELECHECK EMPLOYEES AND =
INTENDED RECIPIENTS, IS STRICTLY PROHIBITED . IF YOU ARE =
NOT SUCH A TELECHECK EMPLOYEE OR INTENDED RECIPIENT, OR THE EMPLOYEE OR =
AGENT RESPONSIBLE FOR DELIVERING THIS MESSAGE TO THE INTENDED =
RECIPIENT, YOU ARE HEREBY NOTIFIED THAT ANY REPRODUCTION, =
DISSEMINATION, DISTRIBUTION AND/OR DISCLOSURE OF THIS DOCUMENT, OR ANY =
ATTACHMENTS, IS STRICTLY PROHIBITED.</FONT></P>
<BR>
<BR>
</BODY>
</HTML>
------_=_NextPart_001_01C3E449.9DBB7BE2--
|
