Forum Discussion

Pratique's avatar
Pratique
Level 4
14 years ago

Restore : Exit status 54

Hi,

I am trying to do a restore from a Unix client formclust4.ndeu-dc1-core.cscehub.com, but it is showing these logs in the Detailed Status tab:

Apr 2, 2011 1:35:50 AM - begin Restore
Apr 2, 2011 1:55:52 AM - media needed: EH0620
Apr 2, 2011 1:55:52 AM - media needed: EH0750
Apr 2, 2011 1:55:52 AM - media needed: EH1335
Apr 2, 2011 1:55:52 AM - media needed: EH1547
Apr 2, 2011 1:55:52 AM - media needed: EH1120
Apr 2, 2011 1:55:52 AM - media needed: X00437
Apr 2, 2011 1:55:52 AM - media needed: X00239
Apr 2, 2011 1:55:52 AM - media needed: EH1628
Apr 2, 2011 1:55:52 AM - media needed: EH1277
Apr 2, 2011 1:55:52 AM - restoring from image formclust4.ndeu-dc1-core.cscehub.com_1299325833
Apr 2, 2011 2:15:51 AM - Error bpbrm (pid=19161) timed out trying to connect to formclust4.ndeu-dc1-core.cscehub.com
Apr 2, 2011 2:15:51 AM - Error bpbrm (pid=19161) client restore EXIT STATUS 54: timed out connecting to client
Apr 2, 2011 2:57:53 AM - restored from image formclust4.ndeu-dc1-core.cscehub.com_1299325833; restore time: 1:02:01
Apr 2, 2011 2:57:53 AM - restoring from image formclust4.ndeu-dc1-core.cscehub.com_1300927561
Apr 2, 2011 3:17:52 AM - Error bpbrm (pid=26624) timed out trying to connect to formclust4.ndeu-dc1-core.cscehub.com
Apr 2, 2011 3:17:53 AM - Error bpbrm (pid=26624) client restore EXIT STATUS 54: timed out connecting to client
Apr 2, 2011 3:59:54 AM - restored from image formclust4.ndeu-dc1-core.cscehub.com_1300927561; restore time: 1:02:01
Apr 2, 2011 3:59:54 AM - restoring from image formclust4.ndeu-dc1-core.cscehub.com_1301086141
 

The restore is still in active state though, it has not failed.

Insight on Networking:

The master server is not able to ping and telnet the client server, though the media can. The communication from the client is working fine. We tried restarting inted services, but no luck. Please help me out on this very critical restore.

  • What is the reason for master not being able to ping the client?  DNS or routing problem on your network? have you asked your network admins to investigate?

    OS version on client? NBU version? Firewall between client and master and/or media server?

    Is master the media server as well?

    If 'ping' problem is resolved, check all of the following.

    Is vnetd and bpcd on client LISTENING?

    Do you have bpcd log on client? If not, create log dir and do following test from master and media server:

    bptestbpcd -client <client-name>

    Please post output of command as well as client's bpcd log.

5 Replies

  • What is the reason for master not being able to ping the client?  DNS or routing problem on your network? have you asked your network admins to investigate?

    OS version on client? NBU version? Firewall between client and master and/or media server?

    Is master the media server as well?

    If 'ping' problem is resolved, check all of the following.

    Is vnetd and bpcd on client LISTENING?

    Do you have bpcd log on client? If not, create log dir and do following test from master and media server:

    bptestbpcd -client <client-name>

    Please post output of command as well as client's bpcd log.

  • There was network issue on the LAN to the master to client, which was rectified by the concerned team. The communication between master and client servers went up and the restore was then completed.

  • So the right solution is the one who Marianne gave you. Don't you think so? 

    ... "have you asked your network admins to investigate?"...

  • As Marianne said

     

    OS version on client? NBU version? Firewall between client and master and/or media server?

     
     
    This means that the connectivity may have problem. Could be between Master and Media or  Master and Client or etc.