Veritas-bu

[Veritas-bu] all netbackup jobs failed

2004-08-17 11:50:11
Subject: [Veritas-bu] all netbackup jobs failed
From: Mark.Donaldson AT cexp DOT com (Mark.Donaldson AT cexp DOT com)
Date: Tue, 17 Aug 2004 09:50:11 -0600
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_01C48471.C4B6954C
Content-Type: text/plain;
        charset="iso-8859-1"

So, I just bumped into this problem on one of my master servers and
remembered this thread.   A solution, however, is not within.

I found a bpbackupdb command that had been "running" for the past 10 days
(yeah, yeah, I've been busy - whatever...).  

Simply killing it (and it required a "-9" ie: "die, dammit, die") was all
that I had to do.

-M

(resent after the original message was pended for being oversized)

-----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 Coco, Samuel
(Cont, ARL/CISD)
Sent: Tuesday, August 10, 2004 5:14 AM
To: Laura.Duffy AT iibbank DOT ie; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] all netbackup jobs failed


Laura,

    We experienced the same results once while on 4.5 FP3.  However, ours
occurred because someone (not me) to cancel a DB(catalog) backup in
progress.  When it refused to quit cleanly - subsequent attempts failed with
the 125 error call.


Thank you,


Samuel J. Coco, STG
Functional Area Manager, ARL
Sr UNIX Administrator
BELL      301 394-1151 DSN 290
CELL (B) 240 398-7121 / (H)443 496-1623
Email  scoco AT arl.army DOT mil
-----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
Laura.Duffy AT iibbank DOT ie
Sent: Tuesday, August 10, 2004 5:01 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] all netbackup jobs failed


Hi,
 
We just recently upgraded from netbackup 3.4 to 4.5.  Our backups have been
running great every night apart from last night.  Nothing ran.
In the Activity Monitor Window there was 3 DB Backup Jobs - 2 had failed
with status 125.
 
125 means:
 
another NB database backup is already in progress
Only one NetBackup catalog backup may be active at any given time.
 
One was Active.
 
The Catalog Backup was set to run after each session of scheduled, user and
manual backups.  I have changed this today to run now only after scheduled
backups.
 
In the bpsched log file it repeats the following message over & over again.
 
log_client_queued: empty-main bpsched is busy
 
Has anyone else had this problem before.  Would it have happened because the
catalog backup was set to run too often?
I would appreciate any information anyone has.
 
Kind Regards,
 
 
Laura Duffy
IT Dept
IIB Homeloans / IIB Bank
2 Hume Street
Dublin 2
 
Direct telephone no.   00-353-1-6035556
Nearest fax    6628966
Email    laura.duffy AT iibbank DOT ie
Web www.iibbank.ie / www.iibhomeloans.ie 
 

------_=_NextPart_001_01C48471.C4B6954C
Content-Type: text/html;
        charset="iso-8859-1"
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=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2657.73">
<TITLE>RE: [Veritas-bu] all netbackup jobs failed</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>So, I just bumped into this problem on one of my =
master servers and remembered this thread.&nbsp;&nbsp; A solution, =
however, is not within.</FONT></P>

<P><FONT SIZE=3D2>I found a bpbackupdb command that had been =
&quot;running&quot; for the past 10 days (yeah, yeah, I've been busy - =
whatever...).&nbsp; </FONT>
</P>

<P><FONT SIZE=3D2>Simply killing it (and it required a &quot;-9&quot; =
ie: &quot;die, dammit, die&quot;) was all that I had to do.</FONT>
</P>

<P><FONT SIZE=3D2>-M</FONT>
</P>

<P><FONT SIZE=3D2>(resent after the original message was pended for =
being oversized)</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 Coco, Samuel (Cont, =
ARL/CISD)</FONT></P>

<P><FONT SIZE=3D2>Sent: Tuesday, August 10, 2004 5:14 AM</FONT>
<BR><FONT SIZE=3D2>To: Laura.Duffy AT iibbank DOT ie; =
veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Veritas-bu] all netbackup jobs =
failed</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Laura,</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; We experienced the same results =
once while on 4.5 FP3.&nbsp; However, ours occurred because someone =
(not me) to cancel a DB(catalog) backup in progress.&nbsp; When it =
refused to quit cleanly - subsequent attempts failed with the 125 error =
call.</FONT></P>
<BR>

<P><FONT SIZE=3D2>Thank you,</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Samuel J. Coco, STG</FONT>
<BR><FONT SIZE=3D2>Functional Area Manager, ARL</FONT>
<BR><FONT SIZE=3D2>Sr UNIX Administrator</FONT>
<BR><FONT SIZE=3D2>BELL&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 301 394-1151 DSN =
290</FONT>
<BR><FONT SIZE=3D2>CELL (B) 240 398-7121 / (H)443 496-1623</FONT>
<BR><FONT SIZE=3D2>Email&nbsp; scoco AT arl.army DOT mil</FONT>
<BR><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 =
Laura.Duffy AT iibbank DOT ie</FONT></P>

<P><FONT SIZE=3D2>Sent: Tuesday, August 10, 2004 5:01 AM</FONT>
<BR><FONT SIZE=3D2>To: veritas-bu AT mailman.eng.auburn DOT edu</FONT>
<BR><FONT SIZE=3D2>Subject: [Veritas-bu] all netbackup jobs =
failed</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Hi,</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>We just recently upgraded from netbackup 3.4 to =
4.5.&nbsp; Our backups have been running great every night apart from =
last night.&nbsp; Nothing ran.</FONT></P>

<P><FONT SIZE=3D2>In the Activity Monitor Window there was 3 DB Backup =
Jobs - 2 had failed with status 125.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>125 means:</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>another NB database backup is already in =
progress</FONT>
<BR><FONT SIZE=3D2>Only one NetBackup catalog backup may be active at =
any given time.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>One was Active.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>The Catalog Backup was set to run after each session =
of scheduled, user and manual backups.&nbsp; I have changed this today =
to run now only after scheduled backups.</FONT></P>

<P><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>In the bpsched log file it repeats the following =
message over &amp; over again.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>log_client_queued: empty-main bpsched is busy</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Has anyone else had this problem before.&nbsp; Would =
it have happened because the catalog backup was set to run too =
often?</FONT>
<BR><FONT SIZE=3D2>I would appreciate any information anyone =
has.</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Kind Regards,</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Laura Duffy</FONT>
<BR><FONT SIZE=3D2>IT Dept</FONT>
<BR><FONT SIZE=3D2>IIB Homeloans / IIB Bank</FONT>
<BR><FONT SIZE=3D2>2 Hume Street</FONT>
<BR><FONT SIZE=3D2>Dublin 2</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>Direct telephone no.&nbsp;&nbsp; =
00-353-1-6035556</FONT>
<BR><FONT SIZE=3D2>Nearest fax&nbsp;&nbsp;&nbsp; 6628966</FONT>
<BR><FONT SIZE=3D2>Email&nbsp;&nbsp;&nbsp; =
laura.duffy AT iibbank DOT ie</FONT>
<BR><FONT SIZE=3D2>Web www.iibbank.ie / www.iibhomeloans.ie </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C48471.C4B6954C--

<Prev in Thread] Current Thread [Next in Thread>