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

Restore issue

Created: 04 Jun 2013 | 4 comments

While initiating the restore of C drive from client side I am getting below error. Please suggest. Its a FULL system state recovery & System state . volume shadow components have not yet initiated.. Getting error on C drive..

06/04/2013 09:07:42 - begin Restore

06/04/2013 09:07:53 - number of images required: 1

06/04/2013 09:07:53 - media needed: HS0498

06/04/2013 09:08:27 - restoring from image usnbsq5606c-brn_1368267204

06/04/2013 09:08:32 - Info bpbrm (pid=4247) DR-SPLRSRVDBA is the host to restore to

06/04/2013 09:08:33 - Info bpbrm (pid=4247) telling media manager to start restore on client

06/04/2013 09:08:33 - requesting resource HS0498

06/04/2013 09:08:33 - Error nbjm (pid=18155) NBU status: 2075, EMM status: Fibre Transport resources are not available

06/04/2013 09:08:33 - Error nbjm (pid=18155) NBU status: 2075, EMM status: Fibre Transport resources are not available

06/04/2013 09:08:36 - Error bptm (pid=4252) listen() error on data socket, File exists

06/04/2013 09:08:37 - Error bptm (pid=4252) The following files/folders were not restored:

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/AutoBoot.cmd

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/BOOTSECT.BAK

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/Custom-W2k8.cmd

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/Custom2-W2k8.cmd

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/PostInstall.cmd

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/R2.cmd

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/R2.vbs

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/hpomFSthreshold_W_do_not_delete.txt

06/04/2013 09:08:37 - Error bptm (pid=4252) UTF - /C/hpomFSthreshold_do_not_delete.txt

06/04/2013 09:08:37 - Error bptm (pid=4252) more than 10 files were not restored, remaining ones are shown in the progress log.

06/04/2013 09:10:04 - Info bptm (pid=4252) EXITING with status 41 <----------

06/04/2013 09:10:04 - Info bpbrm (pid=4247) got ERROR 41 from media manager

06/04/2013 09:10:04 - restored from image usnbsq5606c-brn_1368267204; restore time: 0:01:37

06/04/2013 09:10:04 - Warning bprd (pid=4182) Restore must be resumed prior to first image expiration on Tue Jun 25 05:13:24 2013

06/04/2013 09:10:05 - end Restore; elapsed time 0:02:23

Failed to get status code information (2826)

Operating Systems:

Comments 4 CommentsJump to latest comment

Marianne's picture

You did not mention if this is W2003 or W2008 restore?

See these 2 TN's:

W2008: http://www.symantec.com/docs/TECH87810

W2003: http://www.symantec.com/docs/TECH56473

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

NB_maximus's picture

I've seen the Technote, my concern is that if you see the initial lines in the log it says

06/04/2013 09:08:27 - restoring from image usnbsq5606c-brn_1368267204

06/04/2013 09:08:32 - Info bpbrm (pid=4247) DR-SPLRSRVDBA is the host to restore to

06/04/2013 09:08:33 - Info bpbrm (pid=4247) telling media manager to start restore on client

Earlier the disaster recovery hostname was DR-SPLRSRVDBA but as we had to do a client side recovery we changed the host name to that of production one (IP different) & also changed the registry to reflect usnbsq5606c-brn.

This is how the images were visible from the client BAR GUI & as the destination client option was greyed out with usnbsq5606c-brn we had to rename the server too.

I dont know why DR-SPLRSRVDBA is coming into picture even after removing it from masters host file & deleting it as client.

Ankit Maheshwari's picture

Do check host entries.

bpclntcmd -clear_host_cache

i think bprdreq -rereadconfig cn be helpful..

Ankit Maheshwari

Marianne's picture

Something in your config is telling NBU to restore to DR-SPLRSRVDBA.

We need to see bprd log on the master.

If the log folder does not exist, create it and restart NBU.
Retry the restore, then kill it when Activity Monitor gets to:
DR-SPLRSRVDBA is the host to restore to.

Copy bprd log to bprd.txt and post as File attachment.

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