Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Status 58 trying to restore imported image

Created: 16 Apr 2013 • Updated: 22 Apr 2013 | 7 comments
imashu's picture
This issue has been solved. See solution.

*** Moved to new discussion from https://www-secure.symantec.com/connect/forums/unable-see-images-after-1st-2nd-phase-import-completed-restores-frm-lto3-tapes  ***

Hello Marianne,

I am able to see the images now but now while running the restores we are getting the below error;

 

04/16/2013 18:04:31 - begin Restore
04/16/2013 18:09:33 - media needed: BLS476
04/16/2013 18:09:33 - restoring from image bze1ub03_1365912125
04/16/2013 18:09:33 - Info bprd (pid=9110) Restoring from copy 1 of image created Sun Apr 14 05:02:05 2013
04/16/2013 18:14:34 - Info bpbrm (pid=10495) connect failed STATUS (18) CONNECT_FAILED
04/16/2013 18:14:34 - Info bpbrm (pid=10495)  status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO 10.25.208.52 10.25.208.52 bpcd VIA pbx
04/16/2013 18:14:34 - Info bpbrm (pid=10495)  status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO 10.25.208.52 10.25.208.52 bpcd VIA vnetd
04/16/2013 18:14:34 - Info bpbrm (pid=10495)  status: FAILED, (44) CONNECT_TIMEOUT; system: (115) Operation now in progress; FROM 0.0.0.0 TO 10.25.208.52 10.25.208.52 bpcd
04/16/2013 18:14:34 - Error bpbrm (pid=10495) cannot connect to 10.25.208.52, Operation now in progress (115)
04/16/2013 18:14:34 - Info tar (pid=0) done. status: 58: can't connect to client
04/16/2013 18:14:34 - Error bpbrm (pid=10495) client restore EXIT STATUS 58: can't connect to client
04/16/2013 18:14:34 - restored from image bze1ub03_1365912125; restore time: 0:05:01
04/16/2013 18:14:34 - Warning bprd (pid=9110) Restore must be resumed prior to first image expiration on Sun 16 Jun 2013 12:50:46 PM BST
04/16/2013 18:14:34 - end Restore; elapsed time 0:10:03
Standard policy restore error  (2800)

 

Could you please suggest!!

 

Operating Systems:
Discussion Filed Under:

Comments 7 CommentsJump to latest comment

Marianne's picture

Where are you trying to restore to?

Different client or source client?

Can you use the same media server to backup the destination client?

Firstly check forward and reverse name lookup between media server and destination client (both directions).

Check network connectivity - ping using hostnames in both directions as a start.

Check that PBX (port 1556) and vnetd (port 13724) are open between server and client (bi-directional).

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

SOLUTION
smurphy's picture

Also check the Status 58 troubleshooting TechNote:

 

http://www.symantec.com/business/support/index?page=content&id=TECH68832

Steve Murphy
NetBackup Technical Support
_________________________________
http://go.symantec.com/nb

Jaykullar's picture

Server to client does not need PBX communication, only Server to Server?

Marianne's picture

As from 7.0.1, PBX is installed along with normal client binaries and NBU server will first try to connect to PBX on client.  If that fails, server will attempt vnetd.

First noticed here: https://www-secure.symantec.com/connect/forums/701-clients-making-calls-1556-pbx 
then we discovered this TN: http://www.symantec.com/docs/TECH136791

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Jaykullar's picture

Interesting, so when configuring firewalls can we just use PBX and not vnetd?

revaroo's picture

Yes. PBX takes care of the rest.

imashu's picture

This is resolved now as when i re-installed the netbackup client software and applied patch 7.5.0.5, restarted the client, checked the Host properties and it worked.