Veritas NetBackup™ for VMware Administrator's Guide
- Required tasks: overview
- Notes and prerequisites
- Configure NetBackup communication with VMware
- Adding NetBackup credentials for VMware
- 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
- 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)
NetBackup for VMware best practices
For a more efficient backup, the NetBackup media server and the VMware backup host should be installed on the same host.
When creating virtual machines, use the same name for both host name and display name. If the policy's Clients tab still work.option is changed, the existing entries on the policy
VMware recommends that you run no more than four simultaneous backups of virtual machines that reside on the same datastore.
Successful VMware snapshots depend on the following:
The amount of I/O that occurs on the virtual machine datastore. Backups should be scheduled when relatively little I/O activity is expected. Reducing the number of simultaneous backups can also help.
Limit access to the datastore per policy: Use theattribute in the NetBackup policy.
Limit access to the datastore globally (across all policies): Use the Host Properties Resource Limit screen.
The design of the I/O substructure that is associated with each virtual machine datastore. For correct I/O design and implementation, consult your VMware documentation.
Make sure that the VMware backup host has enough memory to handle the number of simultaneous backups that occur.
Include in a single NetBackup policy those virtual machines that use the same datastore. This practice lets you control the amount of backup-related I/O that occurs per datastore, to limit the backup effect on the target virtual machines.
NetBackup supports multiple backup hosts. When a single backup host is saturated with a backup process, another backup host can be added to increase backup throughput.
If a VM's disks are accessible to multiple ESX hosts, the disks can be accessed for backup or restore through any of the ESX hosts. The ESX host may or may not be the ESX host where the virtual machine is running or registered. All of the following must be accessible to each other and should have DNS configured:
The vCenter server.
All ESX hosts under the vCenter that have access to the VM's vmdk files.
The backup host.
Upgrade to the latest version of VMware vSphere or Virtual Infrastructure.