Veritas-bu

[Veritas-bu] CONTINUE BACKUP message(66)

2003-03-20 11:41:37
Subject: [Veritas-bu] CONTINUE BACKUP message(66)
From: scott.kendall AT abbott DOT com (scott.kendall AT abbott DOT com)
Date: Thu, 20 Mar 2003 10:41:37 -0600
This is a multipart message in MIME format.
--=_alternative 005BB0C386256CEF_=
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

When using a bpstart=5Fnotify script to shutdown the database, if the scrip=
t=20
takes too long you will get this error.

Important Note *** it will also leave a hung bpstart process in the=20
process list... at least I have seen this on Windows clients every time=20
this error happens.  Until you kill this process (or reboot the client),=20
future backups will just skip over using the bpstart script and finish=20
with a completed successfully status... but without shutting down the db,=20
these are useless backups.***

To keep from getting the timeout, look at the backup start notify timeout=20
and backup end notify timeout values on all media servers.  Be aware that=20
when you extend these timeouts, you have to also extend the client read=20
timeout on the clients to at least the same value.


- Scott





"Amine AIT-KHALED" <aaitkhaled AT suez DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
03/20/2003 06:20 AM

=20
        To:     veritas-bu AT mailman.eng.auburn DOT edu
        cc:=20
        Subject:        [Veritas-bu] CONTINUE BACKUP message(66)


Hi all,
I have a problem with a backup oracle server
Here's the log result
20/03/2003 03:20:24 - connecting
20/03/2003 03:20:25 - connected; connect time: 000:00:01
20/03/2003 03:20:25 - mounting 000524
20/03/2003 03:25:22 - mounted; mount time: 000:04:57
20/03/2003 03:25:22 - positioning to file 80
20/03/2003 03:27:12 - positioned; position time: 000:01:50
20/03/2003 03:27:12 - begin writing
20/03/2003 03:27:19 - end writing; write time: 000:00:07
client backup failed to receive the CONTINUE BACKUP message(66)

Status 66

Cordialement.

Amine A=EFt-Khaled
Administrateur R=E9seau et Syst=E8me
Tel: 01 40 06 16 70



=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu



--=_alternative 005BB0C386256CEF_=
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable


<br><font size=3D2 face=3D"Arial">When using a bpstart=5Fnotify script to s=
hutdown the database, if the script takes too long you will get this error.=
</font>
<br>
<br><font size=3D2 face=3D"Arial">Important Note *** it will also leave a h=
ung bpstart process in the process list... at least I have seen this on Win=
dows clients every time this error happens. &nbsp;Until you kill this proce=
ss (or reboot the client), future backups will just skip over using the bps=
tart script and finish with a completed successfully status... but without =
shutting down the db, these are useless backups.***</font>
<br>
<br><font size=3D2 face=3D"Arial">To keep from getting the timeout, look at=
 the backup start notify timeout and backup end notify timeout values on al=
l media servers. &nbsp;Be aware that when you extend these timeouts, you ha=
ve to also extend the client read timeout on the clients to at least the sa=
me value.</font>
<br>
<br>
<br><font size=3D2 face=3D"Arial">- Scott</font>
<br>
<br>
<br>
<br>
<table width=3D100%>
<tr valign=3Dtop>
<td>
<td><font size=3D1 face=3D"sans-serif"><b>&quot;Amine AIT-KHALED&quot; &lt;=
aaitkhaled AT suez DOT com&gt;</b></font>
<br><font size=3D1 face=3D"sans-serif">Sent by: veritas-bu-admin AT mailman DOT 
en=
g.auburn.edu</font>
<p><font size=3D1 face=3D"sans-serif">03/20/2003 06:20 AM</font>
<br>
<td><font size=3D1 face=3D"Arial">&nbsp; &nbsp; &nbsp; &nbsp; </font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; To: &nbs=
p; &nbsp; &nbsp; &nbsp;veritas-bu AT mailman.eng.auburn DOT edu</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; cc: &nbs=
p; &nbsp; &nbsp; &nbsp;</font>
<br><font size=3D1 face=3D"sans-serif">&nbsp; &nbsp; &nbsp; &nbsp; Subject:=
 &nbsp; &nbsp; &nbsp; &nbsp;[Veritas-bu] CONTINUE BACKUP message(66)</font>=
</table>
<br>
<br>
<br><font size=3D2 face=3D"Courier New">Hi all,<br>
I have a problem with a backup oracle server<br>
Here's the log result<br>
20/03/2003 03:20:24 - connecting<br>
20/03/2003 03:20:25 - connected; connect time: 000:00:01<br>
20/03/2003 03:20:25 - mounting 000524<br>
20/03/2003 03:25:22 - mounted; mount time: 000:04:57<br>
20/03/2003 03:25:22 - positioning to file 80<br>
20/03/2003 03:27:12 - positioned; position time: 000:01:50<br>
20/03/2003 03:27:12 - begin writing<br>
20/03/2003 03:27:19 - end writing; write time: 000:00:07<br>
client backup failed to receive the CONTINUE BACKUP message(66)<br>
<br>
Status 66<br>
<br>
Cordialement.<br>
<br>
Amine A=EFt-Khaled<br>
Administrateur R=E9seau et Syst=E8me<br>
Tel: 01 40 06 16 70<br>
<br>
<br>
<br>
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=
=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F<br>
Veritas-bu maillist &nbsp;- &nbsp;Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
--=_alternative 005BB0C386256CEF_=--

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