Keep alive are packets that are sent on idle connection to ensure the
connection is still active / valid. If the keep alive fails its often
because the connection itself has been severed (broken TCP connection) This
can also happen if the target machine is working on something and does not
have time to answer a keep alive request. See the following Qarticle from MS
concerning keepalives (and other topics)

http://support.microsoft.com/kb/120642/en-us

Hope that helps
Steve


On 8/16/06, Sixbury, Dan <dsixbury at hrblock.com> wrote:
>
>  ALL:
> I just received an odd message during a backup.  I saw multiple errors
> that read
>
> Error bpbrm (pid-14867) could not write KEEPALIVE to COMM_SOCK
>
> The backup was just one file system, not a ton of data, and a 7 year
> retention.  We are running the Enterprise 5.1 MP4 of Netbackup on Unix.
> The backup said that it completed with a status 0.  I just checked and it
> looks like 0 files backed up.  Any ideas on what causes the keepalive on
> comm_sock errors and how to fix?
>
> Dan
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060817/41662f59/attachment.html