cancel
Showing results for 
Search instead for 
Did you mean: 

Restore fails with Standard policy restore error (2800)

ngarart
Level 3

My restore is failing with Standard policy restore error  (2800)

nbe version = 7.7.2

master = sles 12 sp1

media server sles 12 sp 1

client = Oracle Linux Server release 6.7

but i can restore the files to my master server without any problem.

 

here is the detail

12/07/2016 16:12:09 - begin Restore
12/07/2016 16:12:09 - Info bprd (pid=31996) Found (19248479) files in (1) images for Restore Job ID 1345444.xxx
12/07/2016 16:12:10 - restoring from image MP2ELVM001_1480813695
12/07/2016 16:12:10 - requesting resource @aaaaj
12/07/2016 16:12:10 - granted resource  MediaID=@aaaaj;DiskVolume=_PhysicalLSU;DiskPool=DXiMWP14;Path=_PhysicalLSU;StorageServer=DXiMWP14_172.17.40.73;MediaServer=mp2ls230
12/07/2016 16:12:11 - Info bprd (pid=31996) Searched (   32910) files of (19248479) files for Restore Job ID 1345444.xxx
12/07/2016 16:12:11 - Info bprd (pid=31996) Restoring from copy 1 of image created Sun Dec  4 03:08:15 2016 from policy ESKOMMWP_EXALOGIC_LINUX_FS
12/07/2016 16:12:13 - restored from image MP2ELVM001_1480813695; restore time: 0:00:03
12/07/2016 16:12:13 - Warning bprd (pid=31996) Restore must be resumed prior to first image expiration on Sun 01 Jan 2017 03:08:15 AM SAST
12/07/2016 16:12:13 - end Restore; elapsed time 0:00:04
12/07/2016 16:14:44 - Info bpbrm (pid=30773) MP2ELVM001 is the host to restore to
12/07/2016 16:14:44 - Info bpbrm (pid=30773) reading file list for client
12/07/2016 16:14:45 - connecting
12/07/2016 16:14:45 - Info bpbrm (pid=30773) starting bptm
12/07/2016 16:14:45 - Error bpbrm (pid=30773) client MP2ELVM001 didn't start
12/07/2016 16:14:45 - Info tar (pid=0) done. status: 49: client did not start
12/07/2016 16:14:45 - Error bpbrm (pid=30773) client restore EXIT STATUS 49: client did not start
Standard policy restore error  (2800)

 

3 REPLIES 3

RiaanBadenhorst
Moderator
Moderator
Partner    VIP    Accredited Certified

Hi,

 

Client is facing an issue "Status 49". Please enable the tar log on the client to see what is going on. 

I found this note of interest as well https://www.veritas.com/support/en_US/article.TECH32332

Is the NBU client running on the server that is being restored? Or is it crashing? Or ports blocked?

Deb_Wilmot
Level 6
Employee Accredited Certified

In addition to the tar log, it might be good to enable the bpcd log file.  Commands are forked by bpcd on clients; that log should give you information about :

  1.  The receipt of the tar command from the media server.

  2.  Information about the forking of the tar processes.

   3.  Hopefully will tell you why the fork of the tar process failed to initiate.

Deb