Veritas NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Adding NetBackup credentials for VMware
- Validating VMware virtualization server certificates in NetBackup
- Configure NetBackup policies for VMware
- VMware backup options
- Exclude Disks tab
- Configure a VMware Intelligent Policy
- Reduce the size of backups
- Back up virtual machines
- Use Accelerator to back up virtual machines
- Restore virtual machines
- Restoring the full VMware virtual machine
- Virtual Machine Recovery dialog boxes (restore to original location)
- Virtual Machine Recovery dialogs boxes (restore to alternate location)
- Restoring VMware virtual machine disks by using Backup, Archive, and Restore
- Restoring VMware virtual machine disks by using NetBackup commands
- Restoring individual VMware virtual machine files
- Browse and search virtual machines for restore
- Restore virtual machines with Instant Recovery
- Use NetBackup for vCloud Director
- Virtual machine recovery dialog boxes for vCloud Director
- Best practices and more information
- Troubleshooting
- Appendix A. NetBackup commands to back up and restore virtual machines
- Using NetBackup commands to create a VMware policy
- Appendix B. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- About configuring services for NFS on Windows 2008 and 2008 R2 (NetBackup for VMware)
- Appendix C. The Reuse VM selection query results option
- Appendix D. Backup of VMware raw devices (RDM)
Restoring individual files with Instant Recovery for VMware while the current virtual machine is running
You can use instant recovery to restore files individually from a virtual machine backup. You can restore the virtual machine from its backup image and mount it on a private network (such as a sandbox). This approach avoids the potential for network conflicts with the virtual machine in your production environment. Another virtual machine on a public network can be used as an intermediary, to copy the files from the virtual machine on the private network.
Note:
This procedure lets you restore files into a running VM. You do not need to shut down the current virtual machine in your production environment before you start this procedure.
Before you start this procedure, you need an intermediary virtual machine that has a network connection to the public network or production network. In this procedure you connect the intermediary to the private network where the restored virtual machine is to be mounted.
At the end of the procedure, you can copy files from the restored virtual machine to the intermediary virtual machine. Then the virtual machines on the public network can access the files on the intermediary.
To restore individual files using instant recovery
- Use vSphere Client to log on to the vCenter server.
You must use a logon that allows access to the files that you want to recover.
- Create a vSphere standard switch.
This switch is for access to the ESX host from the sandbox or private network where the VM is to be activated from its backup.
Note:
The switch is for internal communication within the ESX host only.
For example, in vSphere Client 5:
Select the ESX host for communication between the restored virtual machine and the intermediary virtual machine.
On the Configuration tab, in the Hardware pane, click Networking.
Click Add Networking.
Select Virtual Machine as the connection type.
Select Create a vSphere standard switch.
For Port Group Properties, Network Label, enter a name for the internal switch (such as NB or NetBackup).
Click Finish.
- On the intermediary virtual machine, add a network card (NIC) to be connected to the vSphere standard switch.
Use this connection to retrieve files from the restored virtual machine that is to be mounted on the private network.
Note:
This intermediary virtual machine must already have a network connection to the public network or production network.
For example, in vSphere Client 5:
Select the intermediary virtual machine.
On the Summary tab, click Edit Settings.
Click Add.
Select Ethernet Adapter.
For the Network label, select the private network that is created in step 2.
Click Finish.
- If the intermediary's guest OS does not automatically assign an IP address for the private network after step 3, note: You must manually configure the IP address, default gateway, and subnet mask.
The intermediary should now be connected to both the public network and to the private network where the virtual machine is to be restored.
- Use the nbrestorevm command to restore the virtual machine.
nbrestorevm -vmw -ir_activate -C virtual_machine -temp_location temporary_datastore -R rename_file_path -vmsn
-vmsn specifies that no network is enabled for the virtual machine when it is activated from the backup image. Without the -vmsn option, network conflicts with the production virtual machine may occur.
The file that is designated by -R rename_file_path specifies a different display name or location for the restored virtual machine. You must change the virtual machine name or location to avoid conflicts with the current virtual machine in production. For example, to rename the virtual machine, the rename file can consist of the following entry (ending with a carriage return):
change vmname to acme_vm5
Note:
The words
change vmname to
are literals, followed by the actual name to change to (such asacme_vm5
).See Instant Recovery options on the nbrestorevm command.
For other nbrestorevm options, see the man page or the NetBackup Commands Reference Guide.
- Add a network card (NIC) to the restored virtual machine and connect the NIC to the vSphere standard switch from step 2.
- Turn on the restored virtual machine.
- If the guest OS does not automatically assign an IP address for the private network, configure the IP address, default gateway, and subnet mask.
- Set up file sharing (such as through FTP, NFS, or CIFS) between the restored virtual machine and the intermediary virtual machine.
Then copy the files from the restored virtual machine to the intermediary virtual machine. The current virtual machine in production can access the files.
- If you do not want to keep the restored virtual machine, enter the following:
nbrestorevm - ir_listvm
In the -ir_listvm output, find the VM Instant Recovery ID for the restored virtual machine.
To remove the restored virtual machine:
nbrestorevm - ir_deactivate instant recovery ID
where instant recovery ID is the virtual machine's numeric identifier from the -ir_listvm output.