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

VMware linux file restore failing with status 2800

Created: 05 Nov 2013 | 13 comments

Hi Experts,

I am trying to restore the files from VM linux machine to my solaris server, but it's getting aborted with the status 2800 (Standard restore policy error).

Could you please someone provide me the workaround to resolve it

Please find the below logs

 

11/05/2013 09:28:48 - Info bpdm (pid=3255) started
11/05/2013 09:28:48 - started process bpdm (pid=3255)
11/05/2013 09:28:48 - Info bpdm (pid=3255) reading backup image
11/05/2013 09:28:49 - Info bpdm (pid=3255) requesting nbjm for media
11/05/2013 09:28:49 - Info bpdm (pid=3255) using 30 data buffers
11/05/2013 09:28:49 - Info bpdm (pid=3255) spawning a child process
11/05/2013 09:28:49 - Info bpbrm (pid=3255) child pid: 3278
11/05/2013 09:28:58 - begin reading
11/05/2013 09:29:02 - end reading; read time: 0:00:04
11/05/2013 09:29:03 - Info bpdm (pid=3255) completed reading backup image
11/05/2013 09:29:03 - Info bpdm (pid=3255) EXITING with status 0
11/05/2013 09:29:03 - Info bnymffnb1-app (pid=3255) StorageServer=PureDisk:bnymffnb1-app; Report=PDDO Stats for (bnymffnb1-app): read: 144431 KB, CR received: 150457 KB, CR received over FC: 0 KB, dedup: 0.0%
11/05/2013 09:29:04 - Info bpbrm (pid=3296) bnymffnb1 is the host to restore to
11/05/2013 09:29:04 - Info bpbrm (pid=3296) reading file list from client
11/05/2013 09:29:04 - connecting
11/05/2013 09:29:04 - Info bpbrm (pid=3296) starting bptm
11/05/2013 09:29:04 - Info tar (pid=10288) Restore started
11/05/2013 09:29:04 - connected; connect time: 0:00:00
11/05/2013 09:29:04 - Info bpbrm (pid=3296) bptm pid: 3297
11/05/2013 09:29:04 - Info bptm (pid=3297) start
11/05/2013 09:29:05 - started process bptm (pid=3297)
11/05/2013 09:29:05 - Info bpdm (pid=3297) reading backup image
11/05/2013 09:29:05 - Info bptm (pid=3297) using 30 data buffers
11/05/2013 09:29:05 - Info bptm (pid=3297) spawning a child process
11/05/2013 09:29:05 - Info bptm (pid=3297) child pid: 3298
11/05/2013 09:29:06 - begin reading
11/05/2013 09:29:07 - Info bptm (pid=3297) waited for empty buffer 0 times, delayed 0 times
11/05/2013 09:29:07 - end reading; read time: 0:00:01
11/05/2013 09:29:07 - Info tar (pid=10288) done. status: 183
11/05/2013 09:29:08 - Info bptm (pid=3297) completed reading backup image
11/05/2013 09:29:08 - Info bptm (pid=3297) EXITING with status 0 <----------
11/05/2013 09:29:08 - Info bnymffnb1-app (pid=3297) StorageServer=PureDisk:bnymffnb1-app; Report=PDDO Stats for (bnymffnb1-app): read: 11567 KB, CR received: 20092 KB, CR received over FC: 0 KB, dedup: 0.0%
11/05/2013 09:29:08 - Info tar (pid=10288) done. status: 183: tar received an invalid archive
11/05/2013 09:29:08 - Error bpbrm (pid=3296) client restore EXIT STATUS 183: tar received an invalid archive
11/05/2013 09:29:28 - begin Restore
11/05/2013 09:29:29 - restoring from image VM-ASPENTPRD01_1383385836
11/05/2013 09:29:29 - requesting resource @aaaab
11/05/2013 09:29:30 - Info bprd (pid=10209) Restoring from copy 1 of image created Sat Nov 02 05:50:36 2013
11/05/2013 09:29:30 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bnymffnb1-app;Path=PureDiskVolume;StorageServer=bnymffnb1-app;MediaServer=bnymffnb1-app
11/05/2013 09:29:50 - requesting resource @aaaab
11/05/2013 09:29:50 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bnymffnb1-app;Path=PureDiskVolume;StorageServer=bnymffnb1-app;MediaServer=bnymffnb1-app
11/05/2013 09:29:56 - restored from image VM-ASPENTPRD01_1383385836; restore time: 0:00:27
11/05/2013 09:29:56 - end Restore; elapsed time 0:00:28
Standard policy restore error  (2800)
 
 
 
Regards,
Mohamed Musthak

 

 

Operating Systems:

Comments 13 CommentsJump to latest comment

RamNagalla's picture

let us know some more details about your attempt..

what is the netbackup version on your Solaris system?

did you try restoring the file to another server...?  if not.. i would suggest you to do that also... 

does the backup image is encrypted?

mohamedmusthaq's picture

Hi Nagalla,

Thanks for your response, I'm trying to restore the files from Linux VM to solaris box (Master server)

It's 7.5.0.4.

Backup image is not encrypted.

 

 

Regards,
Mohamed Musthak.

Mark_Solutions's picture

Lots of possible reasons - it may be the path used (especially as these are different O/S's) or it could be corrupted files held within the backup image

Create a tar log folder on the client you are restoring to and lets see what the log says as a first step

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

Will Restore's picture

Article URL http://www.symantec.com/docs/HOWTO91546

 

NetBackup status code: 2800

Message: Standard policy restore error

Explanation: Some or all of the restore operation files failed. When performing a snapshot client restore, you may have selected a different path from the path in the policy's Backup Selections list.

For example, vol6 is mounted on /mnt/vol6 and vol7 is mounted on /mnt/vol7. These mount points are specified in the backup selection. If you select only the parent directory (/mnt), the restore fails with status code 2800.

Will Restore -- where there is a Will there is a way

RamNagalla's picture

hi,

would suggest you to try rest restore to another destination.. if its a tar issue on the destination it will confirms that..

mohamedmusthaq's picture

I'm able to restore from Linux VM to phsical linux servers, but i again i tried restoring from Linum VM - Linux VM but failed, please check the below logs

 

 1/06/2013 11:03:44 - Info bpdm (pid=13620) started

11/06/2013 11:03:44 - started process bpdm (pid=13620)
11/06/2013 11:03:44 - Info bpdm (pid=13620) reading backup image
11/06/2013 11:03:45 - Info bpdm (pid=13620) requesting nbjm for media
11/06/2013 11:03:45 - Info bpdm (pid=13620) using 30 data buffers
11/06/2013 11:03:45 - Info bpdm (pid=13620) spawning a child process
11/06/2013 11:03:45 - Info bpbrm (pid=13620) child pid: 13656
11/06/2013 11:03:47 - begin reading
11/06/2013 11:03:55 - end reading; read time: 0:00:08
11/06/2013 11:03:55 - Info bpdm (pid=13620) completed reading backup image
11/06/2013 11:03:55 - Info bpdm (pid=13620) EXITING with status 0
11/06/2013 11:03:55 - Info bnymffnb1-app (pid=13620) StorageServer=PureDisk:bnymffnb1-app; Report=PDDO Stats for (bnymffnb1-app): read: 221116 KB, CR received: 227820 KB, CR received over FC: 0 KB, dedup: 0.0%
11/06/2013 11:03:58 - Error bpbrm (pid=13694) bpcd on VM-ASPENTUAT02 exited with status 48: client hostname could not be found
11/06/2013 11:03:58 - Info tar (pid=0) done. status: 48: client hostname could not be found
11/06/2013 11:03:58 - Error bpbrm (pid=13694) client restore EXIT STATUS 48: client hostname could not be found
11/06/2013 11:04:24 - begin Restore
11/06/2013 11:04:25 - restoring from image VM-ASPENTUAT01_1383397158
11/06/2013 11:04:25 - Info bprd (pid=22654) Restoring from copy 1 of image created Sat Nov 02 08:59:18 2013
11/06/2013 11:04:25 - requesting resource @aaaab
11/06/2013 11:04:25 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bnymffnb1-app;Path=PureDiskVolume;StorageServer=bnymffnb1-app;MediaServer=bnymffnb1-app
11/06/2013 11:04:43 - requesting resource @aaaab
11/06/2013 11:04:43 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_bnymffnb1-app;Path=PureDiskVolume;StorageServer=bnymffnb1-app;MediaServer=bnymffnb1-app
11/06/2013 11:16:44 - restored from image VM-ASPENTUAT01_1383397158; restore time: 0:12:19
11/06/2013 11:16:44 - end Restore; elapsed time 0:12:20
Standard policy restore error  (2800)
 
mohamedmusthaq's picture

Host entries are fine & daily/full  backups are running fine

Will Restore's picture

this is a different problem

VM-ASPENTUAT02 exited with status 48: client hostname could not be found

 

Media server being used for the restore cannot resolve the name and IP address of the restore client.

See this technote:  http://www.symantec.com/business/support/index?pag...

 

Will Restore -- where there is a Will there is a way

RamNagalla's picture

Correct...

in your first restore to the servers... seems there is a issue with the Solaris desitnation ( Tar error) that is the reason your restore got failed.. and successfull when you change the destination

2nd restore to Phyiscal Linux server is succesfull because that is working fine

3rd restore to Linux VM is Failied due to host name resolution error

Info tar (pid=0) done. status: 48: client hostname could not be found

that destination client name that you are using by the netbackup is not resoling its name, so make sure the name is avaliable in DNS or /etc/hosts and resolved in both forward lookup and reverse lookup and then try the restore..

 

mohamedmusthaq's picture

Hi Nagalla,

Restoring single files is fine now,

I'm trying to restore the vmdk files, but its aborting with status 2820

 

11/08/2013 10:05:11 - begin Restore
11/08/2013 10:05:14 - restoring from image VM-XXXXXXXXX_1383408467
11/08/2013 10:05:14 - Info bprd (pid=13817) Restoring from copy 1 of image created Sat Nov 02 12:07:47 2013
11/08/2013 10:05:14 - requesting resource @aaaab
11/08/2013 10:05:14 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_XXXXXXX-app;Path=PureDiskVolume;StorageServer=XXXXXXX-app;MediaServer=XXXXXXX-app
11/08/2013 10:05:19 - Info bpdm (pid=21416) started
11/08/2013 10:05:19 - started process bpdm (pid=21416)
11/08/2013 10:05:19 - Info bpdm (pid=21416) reading backup image
11/08/2013 10:05:19 - Info bpdm (pid=21416) requesting nbjm for media
11/08/2013 10:05:19 - Info bpdm (pid=21416) using 30 data buffers
11/08/2013 10:05:19 - Info bpdm (pid=21416) spawning a child process
11/08/2013 10:05:19 - Info bpbrm (pid=21416) child pid: 21435
11/08/2013 10:05:25 - begin reading
11/08/2013 10:05:26 - end reading; read time: 0:00:01
11/08/2013 10:05:26 - Info bpdm (pid=21416) completed reading backup image
11/08/2013 10:05:26 - Info bpdm (pid=21416) EXITING with status 0
11/08/2013 10:05:27 - Info XXXXXXX-app (pid=21416) StorageServer=PureDisk:XXXXXXX-app; Report=PDDO Stats for (XXXXXXX-app): read: 12433 KB, CR received: 17646 KB, CR received over FC: 0 KB, dedup: 0.0%
11/08/2013 10:10:02 - requesting resource @aaaab
11/08/2013 10:10:03 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_XXXXXXX-app;Path=PureDiskVolume;StorageServer=XXXXXXX-app;MediaServer=XXXXXXX-app
11/08/2013 10:10:04 - Info bpbrm (pid=21607) XXXXXXX-app is the host to restore to
11/08/2013 10:10:04 - Info bpbrm (pid=21607) reading file list from client
11/08/2013 10:10:04 - connecting
11/08/2013 10:10:04 - Info bpbrm (pid=21607) starting bptm
11/08/2013 10:10:05 - Info tar (pid=21614) Restore started
11/08/2013 10:10:05 - connected; connect time: 0:00:00
11/08/2013 10:10:05 - Info bpbrm (pid=21607) bptm pid: 21616
11/08/2013 10:10:05 - Info bptm (pid=21616) start
11/08/2013 10:10:06 - started process bptm (pid=21616)
11/08/2013 10:10:06 - Info bpdm (pid=21616) reading backup image
11/08/2013 10:10:06 - Info bptm (pid=21616) using 30 data buffers
11/08/2013 10:10:06 - Info bptm (pid=21616) spawning a child process
11/08/2013 10:10:06 - Info bptm (pid=21616) child pid: 21617
11/08/2013 10:10:07 - begin reading
11/08/2013 10:11:16 - Error bpbrm (pid=21607) from client bnymwdnb1-app: ERR - Virtual machine restore file write failed
11/08/2013 10:11:16 - Info tar (pid=21614) done. status 14
11/08/2013 10:11:16 - Error bptm (pid=21617) cannot write data to socket, Connection reset by peer
11/08/2013 10:11:16 - Info bptm (pid=21616) EXITING with status 24 <----------
11/08/2013 10:11:16 - Info tar (pid=21614) done. status: 14
11/08/2013 10:11:17 - Info XXXXXXX-app (pid=21616) StorageServer=PureDisk:XXXXXXX-app; Report=PDDO Stats for (XXXXXXX-app): read: 2037905 KB, CR received: 2043766 KB, CR received over FC: 0 KB, dedup: 0.0%
11/08/2013 10:11:17 - Info tar (pid=21614) done. status: 24: socket write failed
11/08/2013 10:11:17 - Error bpbrm (pid=21607) client restore EXIT STATUS 24: socket write failed
11/08/2013 10:12:48 - restored from image VM-XXXXXXX_1383408467; restore time: 0:07:34
11/08/2013 10:12:48 - end Restore; elapsed time 0:07:37
NBU VMware policy restore error  (2820)
 
RamNagalla's picture

what is the transport method that you are using...?

if you are using does port 902 is listion state between the media server and ESXi host

please enable the bpvmutil log in the backup host and try the restore..

once restore got failed.. attached the bpvmtuil log into this post..

bpvmutil log would be in the location 

Installpath/NetBackup\logs\bpVMutil\ of the backup host.