NetBackup™ for VMware Administrator's Guide
- Introduction
- Required tasks: overview
- Configuring RBAC roles for VMware administrators
- Notes and prerequisites
- VMware vSphere privileges
- Managing VMware servers
- About VMware discovery
- Add VMware servers
- Change resource limits for VMware resource types
- Configuring backup policies for VMware
- Backup options on the VMware tab
- Exclude disks tab
- Configuring a VMware Intelligent Policy
- About the Reuse VM selection query results option
- Use Accelerator to back up virtual machines
- Configuring protection plans for VMware
- Malware scan
- Instant access
- Instant rollback
- Continuous data protection
- Backing up virtual machines
- VM recovery
- VMware agentless restore
- Restoring Individual files and folders from VMware backups
- Using NetBackup to back up Cloud Director environments
- Recover VMware Cloud Director virtual machines
- Restore virtual machines with Instant Recovery
- Protecting VMs using hardware snapshots and replication
- Best practices and more information
- Troubleshooting VMware operations
- NetBackup logging for VMware
- Snapshot error encountered (status code 156)
- Appendix A. Configuring services for NFS on Windows
- About configuring services for NFS on Windows 2012 or 2016 (NetBackup for VMware)
- Appendix B. Backups of VMware raw devices (RDM)
Notes on the hotadd transport mode
NetBackup supports several transport modes for sending snapshot data between the VMware datastore and the VMware backup host during a backup or restore. One of those transport modes (hotadd) is used when the VMware backup host is installed in a virtual machine.
Note the following about the hotadd transport mode:
The VMware backup host must be installed in a virtual machine.
The following is a VMware requirement: The virtual machine to back up (or restore) and the virtual machine that contains the hotadd backup host must reside in the same VMware data center. The same VMware requirement applies to virtual machine restore: The virtual machine to restore and the virtual machine that contains the hotadd restore host must reside in the same VMware datacenter.
For hotadd backup, it is recommended at least one hotadd backup host for each datacenter.
NetBackup does not support IDE disks on the virtual machine.
On the virtual machine to back up, no two disks should have the same name. (Identical names can occur if the disks reside on different datastores.)
The ESX server (where the backup-host virtual machine resides) must have access to the datastore of the virtual machines that you want to back up.
The datastore for the backup-host virtual machine must have some free space before the hotadd backup begins. Otherwise, the backup may fail.
Locking timeouts in the VMware VDDK may cause simultaneous hotadd backups from the same VMware backup host to fail.
See Simultaneous hotadd backups (from the same VMware backup host) fail with status 13.
For a list of VMware restrictions on the hotadd transport mode, refer to VMware's documentation.