This is a multipart message in MIME format.
--=_alternative 0046826385256E78_=
Content-Type: text/plain; charset="us-ascii"
Yes.
I am also currently working on this issue. In my case I am trying to back
up from a Tru64 client connected
to a Cisco switch then to a firewall then to the main switch on our LAN.
In my case, when I initate a backup,
the tape is mounted and positioned, as soon as the "Begin Writing" message
appears in the activity
monitor detail, the job aborts with a "40" error. Sometimes it will run
when Veritas tries it the second time.
However, in only about 1 in 10 tries, will the backup run OK.
I believe there is an incompatibliity between the NIC card in the client
and the Cisco 2950 switch.
I have set everything to 100FDX NO autonegotiate, and various
combinations. The system administrators
are checking the exact model of the NIC cards in the clients. At the same
time I can run backups sucessfully
from another Tru64 system with no problems. The issue is still not
resolved. We are using FTP to move the
files to another system to be backed up.
If anyone else has any ideas on this one, let me know.
=============================
Carl Stehman
PHI Services Company
202-331-6619
Pager 301-765-2703
ckstehman AT pepco DOT com
"Vassileff, Glen" <VassiG AT australia.stortek DOT com>
Sent by: veritas-bu-admin AT mailman.eng.auburn DOT edu
04/15/2004 07:41 PM
To: "'veritas-bu AT mailman.eng.auburn DOT edu'" <veritas-bu AT
mailman.eng.auburn DOT edu>
cc:
Subject: [Veritas-bu] bpbkar copy_to_shm error
Has anyone came across the following error message:
13:56:19 [5201] <16> bpbkar copy_to_shm: ERR - bpbkar exiting because
backup
is aborting
13:56:19 [5201] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 40:
network connection broken
13:56:19 [5201] <4> bpbkar Exit: INF - EXIT STATUS 40: network connection
broken
Backups constantly failing on different files with the same error message.
Wonder if it is something to do with shared memory allocation.
Regards,
Glen
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
--=_alternative 0046826385256E78_=
Content-Type: text/html; charset="us-ascii"
<br><font size=2 face="sans-serif">Yes.</font>
<br>
<br><font size=2 face="sans-serif">I am also currently working on this issue.
In my case I am trying to back up from a Tru64 client connected</font>
<br><font size=2 face="sans-serif">to a Cisco switch then to a firewall
then to the main switch on our LAN. In my case, when I initate a
backup,</font>
<br><font size=2 face="sans-serif">the tape is mounted and positioned, as soon
as the "Begin Writing" message appears in the activity</font>
<br><font size=2 face="sans-serif">monitor detail, the job aborts with a
"40" error. Sometimes it will run when Veritas tries it the
second time.</font>
<br><font size=2 face="sans-serif">However, in only about 1 in 10 tries, will
the backup run OK.</font>
<br>
<br><font size=2 face="sans-serif">I believe there is an incompatibliity
between the NIC card in the client and the Cisco 2950 switch.</font>
<br><font size=2 face="sans-serif">I have set everything to 100FDX NO
autonegotiate, and various combinations. The system administrators</font>
<br><font size=2 face="sans-serif">are checking the exact model of the NIC
cards in the clients. At the same time I can run backups
sucessfully</font>
<br><font size=2 face="sans-serif">from another Tru64 system with no problems.
The issue is still not resolved. We are using FTP to move the</font>
<br><font size=2 face="sans-serif">files to another system to be backed
up.</font>
<br>
<br><font size=2 face="sans-serif">If anyone else has any ideas on this one,
let me know.</font>
<br><font size=2 face="sans-serif"><br>
=============================<br>
Carl Stehman<br>
PHI Services Company<br>
202-331-6619<br>
Pager 301-765-2703<br>
ckstehman AT pepco DOT com</font>
<br>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td>
<td><font size=1 face="sans-serif"><b>"Vassileff, Glen" <VassiG AT
australia.stortek DOT com></b></font>
<br><font size=1 face="sans-serif">Sent by: veritas-bu-admin AT
mailman.eng.auburn DOT edu</font>
<p><font size=1 face="sans-serif">04/15/2004 07:41 PM</font>
<br>
<td><font size=1 face="Arial"> </font>
<br><font size=1 face="sans-serif"> To:
"'veritas-bu AT mailman.eng.auburn DOT edu'"
<veritas-bu AT mailman.eng.auburn DOT edu></font>
<br><font size=1 face="sans-serif"> cc:
</font>
<br><font size=1 face="sans-serif"> Subject:
[Veritas-bu] bpbkar copy_to_shm error</font></table>
<br>
<br>
<br><font size=2 face="Courier New"><br>
Has anyone came across the following error message:<br>
<br>
13:56:19 [5201] <16> bpbkar copy_to_shm: ERR - bpbkar exiting because
backup<br>
is aborting<br>
13:56:19 [5201] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 40:<br>
network connection broken<br>
13:56:19 [5201] <4> bpbkar Exit: INF - EXIT STATUS 40: network
connection<br>
broken<br>
<br>
Backups constantly failing on different files with the same error message.<br>
Wonder if it is something to do with shared memory allocation.<br>
<br>
Regards,<br>
<br>
Glen<br>
_______________________________________________<br>
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu<br>
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu<br>
</font>
<br>
<br>
<br>
--=_alternative 0046826385256E78_=--
|
