Highlighted

VM Restore from netbackup

Hi team, do we have any step by step document of Virtual machine(Netbackup client) restore . -restore to original VM - restore to another datastore Client OS type is windows and linux Or any suggested method of VM restore The backup is using VMware policy method. Nbu version 7.6.0.3 Master server is windows 2012
3 Solutions

Accepted Solutions
Highlighted
Accepted Solution!

Symantec NetBackup 7.6 for

Symantec NetBackup 7.6 for VMware Administrator's Guide

http://www.symantec.com/docs/DOC6461

Chapter 10 & 11

Page 146 - Restore to orginal location

Page 150 - Restore to alternate location

View solution in original post

Highlighted
Accepted Solution!

I am wondering if you

I am wondering if you actually went through the sections of the manual that Nicolai referred you to?

If you did, you would've seen the following on p.148:

Remove network interfaces
Removes any network interfaces from the restored virtual machine.
Select this option if:
      ■ The network connections on the destination virtual machine have changed since the backup was                  made.
     ■ Or if the original virtual machine still exists and a duplicate may cause conflicts.

View solution in original post

Highlighted
Accepted Solution!

The one thing that may be an

The one thing that may be an issue with SAN restore is with write permission on SAN disk.

See this post: https://www-secure.symantec.com/connect/forums/netbackup-7505-and-vmware-san-transport#comment-88958... 

There are also scenarios where LAN based restore is better than SAN - this is documented in the NBU for VMware Admin Guide.

Logs needed on backup host: tar
Media server: bptm and bpbrm

*** EDIT ***

Found this in NBU for VMware Guide:

For the SAN transport mode and a restore host on Windows 2008R2, the restore
fails if the datastore’s lun is offline. The detailed status log contains messages
similar to the following:
5/22/2013 4:10:12 AM - Info tar32(pid=5832) done. status: 24:
socket write failed
5/22/2013 4:10:12 AM - Error bpbrm(pid=5792) client restore EXIT STATUS 24:
socket write failed
Make sure the status of the SAN disk on the restore host is online (not offline).
Disk status can be checked or changed using the Windows diskpart.exe utility
or the Disk Management utility (diskmgmt.msc). When the disk status reads
online, retry the restore.
■ A restore by means of the SAN transport mode may be slow in other
circumstances. The following VMware article provides details:
Best practices when using SAN transport for backup and restore

View solution in original post

12 Replies
Highlighted
Accepted Solution!

Symantec NetBackup 7.6 for

Symantec NetBackup 7.6 for VMware Administrator's Guide

http://www.symantec.com/docs/DOC6461

Chapter 10 & 11

Page 146 - Restore to orginal location

Page 150 - Restore to alternate location

View solution in original post

Highlighted

Thank u Nicolai... I wanted

Thank u Nicolai... I wanted to do a test restore. The client machine is healthy. So Is it necessary to shutdown the original VM before restoring to original or different location (to avoid hostname and IP conflict) ?
Highlighted

No - but I usually don't

No - but I usually don't power on the cloned VM and disable the NIC to avoid conflicts.

Ensure you don't allow overwrite files.

Highlighted

I believe if the original VM

I believe if the original VM is still powered on and you want to overwrite the VM, it will automatically be powered off once you have initiated the restore.

As Nicolai has mentioned, if you're restoring a copy of an existing VM then there is a tickbox in the restore wizard for removing the NIC - which is what I use as I personally like to power on the VM and ensure it boots as part of the test restore. If you power on the restored VM with a network connection then it could have an impact due to hostname / IP conflict as you mentioned, depending on your setup.

Highlighted
Accepted Solution!

I am wondering if you

I am wondering if you actually went through the sections of the manual that Nicolai referred you to?

If you did, you would've seen the following on p.148:

Remove network interfaces
Removes any network interfaces from the restored virtual machine.
Select this option if:
      ■ The network connections on the destination virtual machine have changed since the backup was                  made.
     ■ Or if the original virtual machine still exists and a duplicate may cause conflicts.

View solution in original post

Highlighted

hi Team,  I got below error

hi Team, 

I got below error when I used SAN transport mode for VM restore .

VMware policy restore error(2820)

When I used NBD trasnport mode , restore completed sucessfully.

for backup of this VM, I am using SAN trasnport mode.

 

Highlighted

Hi Brits, For VM restoration

Hi Brits,

For VM restoration it is required to access ESXi & related (Destination) storage from Master server by NBD or SAN.

May be one of ESXi or storage device unable to communicated with master server

And NBD restored was success because of both are availble from network.

Check the SAN connectivity and test restoration from SAN.

 

Regards,

Yogesh Patil

 

Highlighted

Please always post ALL text

Please always post ALL text in Details tab of the failed job - not just the error.
You can see that this is a very generic error.

Have you created log folders (as per Troubleshooting chapter in NBU for VMware Guide)?
Depending on what we see in job details, we will know which logs are needed.

Highlighted

6/8/2015 6:02:53 PM - begin

6/8/2015 6:02:53 PM - begin Restore

6/8/2015 6:02:54 PM - restoring image <CLIENT SERVER>_1433588459

6/8/2015 6:02:54 PM - requesting resource @aaaad

6/8/2015 6:02:54 PM - granted resource MediaID=@aaaad;DiskVolume=PureDiskVolume;DiskPool=DiskPool_2;Path=PureDiskVolume;StorageServer=<Media Server>;MediaServer=<Media Server>

6/8/2015 6:02:54 PM - Info bprd(pid=2468) Restoring from copy 1 of image created 06/06/15 20:00:59 from policy VM_Win_Servers_1

6/8/2015 6:02:55 PM - Info bprd.sfr(pid=2468) Restoring to vCenter server <vCenter Server>, ESX host <ESX Server>, Datacenter //<DC NAME>, Folder /<DC NAME>/vm/Core Infra, Display Name <CLIENT SERVER>_Restored, Resource Pool/vApp /<DC NAME>/host/pathname_InfraCore/Resources, Datastore/Datastore Cluster <datastore name>

6/8/2015 6:02:56 PM - Info bpdm(pid=1608) started           

6/8/2015 6:02:56 PM - started process bpdm (1608)

6/8/2015 6:02:56 PM - Info bpdm(pid=1608) reading backup image         

6/8/2015 6:02:56 PM - Info bpdm(pid=1608) requesting nbjm for media        

6/8/2015 6:02:56 PM - Info bpdm(pid=1608) using 30 data buffers        

6/8/2015 6:02:56 PM - Info bpdm(pid=1608) spawning a child process        

6/8/2015 6:02:56 PM - Info bpbrm(pid=1608) child pid: 6512         

6/8/2015 6:02:56 PM - Info bpdm(pid=6512) started           

6/8/2015 6:02:56 PM - started process bpdm (6512)

6/8/2015 6:02:57 PM - begin reading

6/8/2015 6:02:58 PM - end reading; read time: 0:00:01

6/8/2015 6:02:58 PM - Info bpdm(pid=1608) completed reading backup image        

6/8/2015 6:02:58 PM - Info bpdm(pid=1608) EXITING with status 0        

6/8/2015 6:03:23 PM - requesting resource @aaaad

6/8/2015 6:03:23 PM - granted resource MediaID=@aaaad;DiskVolume=PureDiskVolume;DiskPool=DiskPool_2;Path=PureDiskVolume;StorageServer=<Media Server>;MediaServer=<Media Server>

6/8/2015 6:03:24 PM - Info bpbrm(pid=7004) <Media Server> is the host to restore to     

6/8/2015 6:03:24 PM - Info bpbrm(pid=7004) reading file list for client       

6/8/2015 6:03:25 PM - connecting

6/8/2015 6:03:25 PM - Info bpbrm(pid=7004) starting bptm           

6/8/2015 6:03:34 PM - Info tar32(pid=4536) Restore started          

6/8/2015 6:03:34 PM - connected; connect time: 0:00:09

6/8/2015 6:03:34 PM - Info bptm(pid=5172) start           

6/8/2015 6:03:34 PM - started process bptm (5172)

6/8/2015 6:03:35 PM - Info bptm(pid=5172) reading backup image         

6/8/2015 6:03:35 PM - Info bptm(pid=5172) using 30 data buffers        

6/8/2015 6:03:35 PM - Info bptm(pid=5172) spawning a child process        

6/8/2015 6:03:35 PM - Info bptm(pid=5172) child pid: 5256         

6/8/2015 6:03:35 PM - Info bptm(pid=5256) start           

6/8/2015 6:03:35 PM - started process bptm (5256)

6/8/2015 6:03:36 PM - begin reading

6/8/2015 6:04:10 PM - Info tar32(pid=4536) INF - Transport Type = san      

6/8/2015 6:04:10 PM - Error bptm(pid=5256) cannot write data to socket, 10053      

6/8/2015 6:04:10 PM - Info bptm(pid=5172) EXITING with status 24 <----------       

6/8/2015 6:04:10 PM - Info <Media Server>(pid=5172) StorageServer=PureDisk:<Media Server>; Report=PDDO Stats for (<Media Server>): read: 14472 KB, CR received: 27493 KB, CR received over FC: 0 KB, dedup: 0.0%

6/8/2015 6:04:11 PM - Info tar32(pid=4536) done. status: 24: socket write failed      

6/8/2015 6:04:11 PM - Error bpbrm(pid=7004) client restore EXIT STATUS 24: socket write failed    

6/8/2015 6:05:20 PM - restored image <CLIENT SERVER>_1433588459 - (the restore failed to recover the requested files(5)); restore time 0:02:26

6/8/2015 6:05:20 PM - end Restore; elapsed time: 0:02:27

VMware policy restore error(2820)

Highlighted

Thank you Yogeh foir

Thank you Yogeh foir suggestion.

SAN connectivity is proper as the backups are running fine.

before restore , there is an option of "run pre-recovery check". This check was sucessful when i have selected SAN transport mode. I think it checks the proper connectivity also  ?

Highlighted
Accepted Solution!

The one thing that may be an

The one thing that may be an issue with SAN restore is with write permission on SAN disk.

See this post: https://www-secure.symantec.com/connect/forums/netbackup-7505-and-vmware-san-transport#comment-88958... 

There are also scenarios where LAN based restore is better than SAN - this is documented in the NBU for VMware Admin Guide.

Logs needed on backup host: tar
Media server: bptm and bpbrm

*** EDIT ***

Found this in NBU for VMware Guide:

For the SAN transport mode and a restore host on Windows 2008R2, the restore
fails if the datastore’s lun is offline. The detailed status log contains messages
similar to the following:
5/22/2013 4:10:12 AM - Info tar32(pid=5832) done. status: 24:
socket write failed
5/22/2013 4:10:12 AM - Error bpbrm(pid=5792) client restore EXIT STATUS 24:
socket write failed
Make sure the status of the SAN disk on the restore host is online (not offline).
Disk status can be checked or changed using the Windows diskpart.exe utility
or the Disk Management utility (diskmgmt.msc). When the disk status reads
online, retry the restore.
■ A restore by means of the SAN transport mode may be slow in other
circumstances. The following VMware article provides details:
Best practices when using SAN transport for backup and restore

View solution in original post

Highlighted

Thank you Marianne. Now VM

Thank you Marianne. Now VM restore concept is more clear to me.

my datastore LUN's are offline which are presented on media server. This could be a solid reason of failed restore. 

Next time i will try SAN transport mode after making the disks online & will check the restore speed.

many thanks again for clearing the doubts.