05-21-2015 02:41 AM
Hi Experts
I am trying to perform a VM instant recovery but failing with error code 5
Backup server is Windows 2008. Nbu 7.6.0.4
Media server/Backup host : Symnatec Appliance 5230. 2.6.0.4
I am restoring the vm using below command but the job is failing without completeing teh task
As instant recovey does not support linux backup host(appliance), i am putting master server(win) with -vmproxy
nbrestorevm -vmw -ir_activate -C TESTBACKUP03 -temp_location XXXX -R C:\vmrestore -vmproxy masterserver -vmpo
C:\vmrestore contains change vmname to TESTBACKUP03_New
Logs below
5/21/2015 1:28:50 PM - begin
5/21/2015 1:28:50 PM - Info bprd(pid=7324) Waiting for Instant Recovery job to end
5/21/2015 1:28:50 PM - Info bprd(pid=7324) Starting to export a backup image on the media server appliance
5/21/2015 1:28:52 PM - Info bprd(pid=7324) Backup image has been successfully exported on the media server appliance
5/21/2015 1:29:01 PM - Info bprd(pid=7324) Backup image has been successfully mounted on the server esxhost
5/21/2015 1:29:01 PM - Info bprd(pid=7324) Starting to activate a virtual machine on the server esxhost
5/21/2015 1:30:08 PM - Error bprd(pid=7324) Failed to activate a virtual machine on the server esxhost
5/21/2015 1:30:08 PM - Info bprd(pid=7324) Starting to unmount a backup image on the server esxhost
the restore failed to recover the requested files(5)
05-21-2015 03:00 AM
Hi Ajith,
Is your restore host a windows machine??
Because Instant Recovery for VMware requires restore host (NetBackup client) to be Windows.
Check the below tech note:
https://support.symantec.com/en_US/article.HOWTO92127.html
Thanks.
05-21-2015 03:12 AM
Check the vsphere/esx event log for the reason the VM cannot be activated
Check the bpVMutil log(s) on the master and media server
There seems to missing vcenter in the command, -vmserver if memory serves
05-21-2015 04:15 AM
Yes, the restore host is windows and it is the master server itself.
i tried with -vmserver option but no luck. bpvmutil log attached from backup server
07-24-2015 02:24 AM
This could be related to timeout period . Check the last 15-20 lines of logs. It has failed with 41