[Veritas-bu] error code 50 (client process aborted)

This is a multi-part message in MIME format.

------_=_NextPart_001_01C4155D.997434F6
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello!

Last week I have upgraded our server from 4.5 FP3 to FP6, and from then =
on I get error code 50 (client process aborted) from several backups =
every night after 10 minutes of execution. After the error code 50 has =
occurred the backup is requeued and the backup is run again. Too bad the =
client process is actually aborted, but I can live with that. It is =
probably that we are starting too many backups at the same time or =
something like that...

The problem is that the backup with error code 50 is left in the =
activity log. Because of this we have to manually search through the =
activity log so we won't miss any failing backups. We can no longer =
trust hosts marked with red. This never happened with FP3...

Could someone explain why these backups with error code 50 occurs and =
wht they are left in the activity log? Has someone been able to fix some =
kind of a work-around?

Regards
/jonas bl=E5berg



Jonas Bl=E5berg
  Mandator Infrastructure
  Kruthusgatan 17,6
  S-411 04 G=F6teborg
jonas.blaberg AT mandator DOT com
office: +46-(0)31-739 84 54
mobile: +46-(0)709-95 00 68



------_=_NextPart_001_01C4155D.997434F6
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 =
6.5.6944.0">
<TITLE>error code 50 (client process aborted)</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">Hello!</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Last week I have upgraded our server =
from 4.5 FP3 to FP6, and from then on I get error code 50 (client =
process aborted) from several backups every night after 10 minutes of =
execution. After the error code 50 has occurred the backup is requeued =
and the backup is run again. Too bad the client process is actually =
aborted, but I can live with that. It is probably that we are starting =
too many backups at the same time or something like that...</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">The problem is that the backup with =
error code 50 is left in the activity log. Because of this we have to =
manually search through the activity log so we won't miss any failing =
backups. We can no longer trust hosts marked with red. This never =
happened with FP3...</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Could someone explain why these backups =
with error code 50 occurs and wht they are left in the activity log? Has =
someone been able to fix some kind of a work-around?</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">/jonas bl=E5berg</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">Jonas Bl=E5berg</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; Mandator Infrastructure</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; Kruthusgatan 17,6</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">&nbsp; S-411 04 G=F6teborg</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">jonas.blaberg AT mandator DOT com</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">office: +46-(0)31-739 84 54</FONT>

<BR><FONT SIZE=3D2 FACE=3D"Arial">mobile: +46-(0)709-95 00 68</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C4155D.997434F6--