Some reasons I've seen so far (not that I necessarily endorse all the 
suggestions - I'm just repeating them):

1.  Improper network settings: duplex and speed should be forced to match 
switch settings on fast Ethernet connections.
2.  Virus software.  It may interfere with backups; turn it off for the 
duration of the backups.
3.  Improper timeouts.  Increase the client read and client connect timeouts.
4.  OTM configuration issues.  Turn off OTM and see if the problem continues to 
occur.

I'd like to add one of my own to be considered:

5.  Backups of the master server being taken while other backups are running.  
(Our guess: file locks and/or OTM prevent the image files from being updated, 
resulting in a failure on the master server seen as a network drop from the 
client.  We recently moved the backups for the backup servers [master and 
media] to a quiet time.)

-Michael


-----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 Day,
Michael
Sent: Friday, August 09, 2002 1:46 PM
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] could not write KEEPALIVE to COMM_SOCK


Anyone have any info on the following error I keep on seeing in my 'Problem
with backups' reports?  "could not write KEEPALIVE to COMM_SOCK".  I'm
seeing bundles and bundles of these errors and its on many of my NT servers.
I'm also getting many error 14's and 41's but my backups are completing with
multiple retries due to network related problems.

Michael H. Day
QRS Systems Engineer