I am having repeated failures when attempting to run a *full* backup on a DP client residing within a backup specification which contains numerous other DP clients. All of the other DP clients residing in that backup specification successfully complete their backup runs. Only that one client is failing its full backup and I would point out that the client fails only when running its weekly *full* backup. It successfully completes its daily *incremental* backups during every run attempt.


The client is running Red Hat (I think) see below:

[root@jambox3 lbin]# uname -a
Linux jambox3.rsn.hp.com 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:30:39 EST 2005 i686 i686 i386 GNU/Linux
You have new mail in /var/spool/mail/root
[root@jambox3 lbin]#

The client is running DP 6.0

Here was the error message from the first run:

[Critical] From: BDA-NET@jambox3.rsn.hp.com "jambox3.rsn.hp.com [/]" Time: 7/6/2010 8:34:26 AM [b]IPC failure reading NET message (IPC Read Error System error: [110] Connection timed out[/b]
) => aborting.

Immediately after the first run failed, I enabled the "Reconnect broken connections" option, thinking that the original IPC Read error message was possibly induced by network problems.

I then restarted the failed backup. It too, failed, but it did give 4 successive "Reconnect succeeded, resuming operation" messages over a 2 hour period of time before it failed due to reaching its inactivity timeout of 7200 seconds.

Does anybody have any idea how to troubleshoot this problem and/or what might actually be causing it? I suspect that the problem is specific to the DP client and not necessarily network related because it is the only client that is failing its full backup.

Any and all replies are greatly appreciated. Thanks in advance!

Rob Sandifer
When you created Drives for whatever silo/tape library you use, you need to to ensure it's setup to talk to your backup segment. If it's not, you get this error.
Sorry, you do not have permission to post/reply in this forum.