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)
- Appendix C. The Reuse VM selection query results option
- Appendix D. Backup of VMware raw devices (RDM)
Errors for backups of virtual machines on Virtual Volumes (VVols)
When troubleshooting backups of virtual machines on VVols, note the following:
Each snapshot job creates a vSphere snapshot of the virtual machine.
To investigate snapshot failures, check the storage array's VASA provider logs as well as the vSphere error messages. (VASA is vSphere API for Storage Awareness.)
Table: Errors for backups of virtual machines on VVols
Error message or cause |
Explanation and recommended action |
---|---|
vSphere snapshot creation fails for a backup of a VM on VVol. |
Ensure that you have the required snapshot license from the array vendor. Licensing requirements for vSphere snapshots vary from one type of VVol storage to another, depending on the array vendor. Each snapshot job creates a vSphere snapshot of the virtual machine. |
There is insufficient space in VVol storage. Space requirements vary from one array vendor to another. Consult the storage array documentation. |