06-24-2014 09:34 PM
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 !
Solved! Go to Solution.
06-24-2014 10:05 PM
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.
06-24-2014 10:00 PM
the link that you have provided is for Netbackup 7.0 or 7.1 but not the 7.5 or later sice its using the Policiy type as FlashBackup-Windows.
in 7.5 policy type for VM backup is Vmware.
tell us the more about your setup
1) what is the netbackup version( since you are using nbrestorevm command it should be 7.6)
2) what is the Vcenter version
3) what is the Backup host(unix or windows)
what els did you consider and setup that you did other than in the link that you provided..
06-24-2014 10:05 PM
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.
06-24-2014 10:24 PM
Hello Nagalla,
I am using netbackup 7.6
V center version is 5.1
Backup host is windows (W2K8 R2)
NETBACKUP and vcenter are installed on same machine.
06-24-2014 11:58 PM
how about the recommendation that i posted in below post.. have you gone though that and make sure that everything is followed..
06-25-2014 12:11 AM
06-25-2014 01:33 AM
what about the NFS services...?
06-25-2014 01:44 AM
06-25-2014 01:47 AM
06-25-2014 01:57 AM
Rashi,
everthing is avaliable in the guide that i have provided in the above link
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.
06-25-2014 02:29 AM
06-25-2014 03:08 AM
I am not able get procedure to set the NFS services on ESXi host
you need to get your VMware guys to get it done and working..
06-29-2014 11:18 PM
Hello all,
Anyone help me !!
I am continusoly getting the same error.
06-30-2014 12:26 AM
so did you fix the NFS issue on ESXi host?
08-02-2014 02:57 AM
Hi rashi.jain:
I have same problem,Your problem is solved ?what reason?
08-02-2014 07:39 AM
simply login using vsphere and connect to esxi where NFS services are to be enabled
modify the security policy in vSphere Client. Click Configuration > Security Profile > Properties, select NFS Client and click OK.
Note : Ensure that the ports 111 and 2049 are also open on the NFS server.
Whitelist NBU vmware backup host IP to esxi and vcenter so there are no issues during NFS mount and dismount.
On Backup host (Win2k8 R2)
Configure NFS services
Note: Before you configure NFS on the media server or restore host, look for the ONC/RPC Portmapper service. If it exists, stop it and disable it. Otherwise, the configuration of NFS Services for Windows fails.
On the media server do the following:
■ Stop and disable the ONC/RPC Portmapper service.
■ Use the Windows Server Manager to enable NFS.
See “Enabling Services for Network File System (NFS) on Windows 2008 or 2008 R2 (NetBackup for VMware)” on page 268.
■ Stop the Server for NFS service.
See “Disabling the Server for NFS (NetBackup for VMware)” on page 272.
■ Stop the Client for NFS service.
See “Disabling the Client for NFS on the media server (NetBackup for VMware)” on page 273.
Note: If the media server is also a restore host, do not disable the Client for NFS.
■ Configure the portmap service to start automatically at server restart. Enter the following
from the command prompt: (Run CMD as an Administrator)
sc config portmap start= auto
This command should return the status [SC] ChangeServiceConfig SUCCESS.
If in case you needed NFS services to be restarted without server reboot try below
To restart the Client for NFS service without a server restart
◆ From the Windows command prompt, run the following commands:
net stop nfsclnt
net stop nfsrdr
net start nfsrdr
net start nfsclnt
The Client for NFS service should restart without a restart of the server
Also create following log directory on backup host (to get logs to troubleshoot in case any issue arises)
nbfsd - on backup host
tar - on backup host
bpVMutil - on backuphost
bpVMreq - on host where BAR gui is used for recovery
Do not increase verbose logging for now.. initial logging gives ample information to troubleshoot issue at basic levels.
Let us know if above helps you to get recovery complete
12-07-2016 03:29 AM
Hello All,
ESX should have a VM Kernel as NIC configured with an IP address assigned to it for NFS to work.
I am using a Win 2012 R2 as Media server **bleep** recovery host and was unable to find below Portmapper Service, while starting from command line returned:
Q: Which host do I need to start this service, Media Server, recovery host ?
c:\Program Files\Veritas\NetBackup\bin>sc config portmap start= auto
[SC] OpenService FAILED 1060:
The specified service does not exist as an installed service.
■ Configure the portmap service to start automatically at server restart. Enter the following
from the command prompt: (Run CMD as an Administrator)
sc config portmap start= auto
This command should return the status [SC] ChangeServiceConfig SUCCESS.
12-07-2016 04:18 AM
Please post in your thread over here:
https://vox.veritas.com/t5/NetBackup/VMware-Instant-Recovery-failure/m-p/822297
This particular discussion has been marked as SOLVED.