Instant recovery failed .
Hello all,
I am facing an issue during the recovery of vm .
we are able to run the successfully backup . As backup steps are mentioned in below link
http://www.virtualdennis.com/netbackup-7-configuration-for-vmware-vstorage-backups/
After complete the backup , I was deleted the VM.
Now, try to take the instant recovery but on activity monitor I am getting socket opened failed(21).
But on run the instant recovery cmd :
C:\Program Files\Veritas\NetBackup\bin>nbrestorevm -vmw -ir_activate -C vm1 -temp_location datastore2 -S WIN-CLAIJS5TQ8F -vmpo
Restore image time = 06/25/14 11:54:50
VM restore request returned with status = 0
But vm is not recovered.
HELP ! HELP ! HELP ! HELP !
also go though the Requirements for Instant Recovery for VMware" from Netbackup 7.6 Vmware admin gudie page number 169 and make sure you have met all those requirements
http://www.symantec.com/business/support/index?page=content&id=DOC6461
Requirements for Instant Recovery for VMware
For virtual machine instant recovery, your environment must meet the following
requirements:
■ The virtual machine to restore must have been backed up from a VMware policy.
■ The target ESX server for the restore must be at vSphere 5.0 or later.
■ The restore host (NetBackup client) must be on Windows. The backup host that
made the backup can be Windows or Linux.
■ For a restore host that is separate from the NetBackup master server or media
server: You must add the restore host to the list of servers that can access the
master server. For example: If a NetBackup appliance was the backup host that
made the backup, the restore host must run on a separate Windows host.
Restore virtual machines with Instant Recovery 169
Performance recommendations for Instant Recovery for VMware
In the NetBackup Administration Console, click Host Properties > Master
Servers, double-click the NetBackup master server, and click Servers. On the
Additional Servers tab, click Add to add the restore host.
See “Allowing other servers or clients to restore virtual machines” on page 258.
■ If the backup host was Linux, you must use the -vmproxy option on the
nbrestorevm command to specify a Windows restore host. The nbrestorevm
command is explained in the following topics:
See “Instant Recovery options on the nbrestorevm command” on page 172.
See “Restoring a virtual machine with Instant Recovery for VMware” on page 177.
■ The NFS Client service must be enabled on the ESXi host.
■ The Services for Network File System (NFS) must be installed on the Windows
media server and restore host.
See “About configuring services for NFS on Windows 2012 (NetBackup for
VMware)” on page 260.
See “About configuring services for NFS on Windows 2008 and 2008 R2
(NetBackup for VMware)” on page 267.
See “About configuring Services for Network File System (NFS) on the Windows
2003 R2 SP2 NetBackup media server and NetBackup clients (NetBackup for
VMware)” on page 275.
The NetBackup media server platform must support Granular Recovery
Technology. See the NetBackup Enterprise Server and Server 7.x OS Software
Compatibility List:
http://www.symantec.com/docs/TECH76648
■ The Client for NFS service may have to be restarted on the NetBackup restore
host.
See “Restarting the Client for NFS service on the restore host” on page 172.
■ The media server must use IPv4 (IPv6 is not supported).
Note: If the media server is registered with IPv6 but is configured for both IPv4
and IPv6, use the following workaround:
On the ESX server add an entry to the /etc/hosts file, to remap the media
server host name to its IPv4 address. For example:
10.84.65.60 mserver7.acme.com
Where 10.84.65.60 is the IPv4 address of the media server mserver7.
■ NetBackup requires login credentials for the vCenter server and the restore
host.
See “Adding NetBackup credentials for VMware” on page 42.
