Veritas NetBackup™ for Hyper-V Administrator's Guide
- Notes and prerequisites
- Configure NetBackup communication with Hyper-V
- Configure NetBackup policies for Hyper-V
- Backup options on the Hyper-V tab
- Hyper-V - Advanced Attributes
- Browse for Hyper-V virtual machines
- Configure Hyper-V Intelligent Policies
- NetBackup Hyper-V for SCVMM
- Windows Server failover cluster support
- Virtual machine maintenance after a restore
- Back up and restore Hyper-V
- Restoring individual files to a shared location on the virtual machine
- Use Accelerator to back up Hyper-V
- Best practices and more information
- NetBackup logs for Hyper-V and how to create them
- Errors during policy creation
- NetBackup status codes related to Hyper-V
- Appendix A. VSS backup method: Hyper-V online and offline backups
- Appendix B. Hyper-V pass-through disks
- Appendix C. NetBackup commands to back up and restore Hyper-V virtual machines
- Examples of nbrestorevm for restoring VMs to Hyper-V
Notes on NetBackup for Hyper-V with SCVMM
Note the following about NetBackup for Hyper-V with SCVMM:
Requires SCVMM 2012 R2 or later.
For a list of supported versions of SCVMM, see the appropriate version of the NetBackup Software Compatibility List available from the following location:
NetBackup client software must be installed on the SCVMM server and on each Hyper-V server.
Certain kinds of VMs are excluded from the backup list when the NetBackup Hyper-V policy runs:
Hyper-V VMs that are marked for deletion.
Hyper-V VM templates.
Hyper-V VMs that are stored on an SCVMM library server.
Any VMs that do not reside on a Hyper-V server, such as VMware VMs.
SCVMM can manage non-Hyper-V VMs. NetBackup for Hyper-V does not back up these VMs. To back up VMware VMs for example, use NetBackup for VMware.
The Test Query dialog lists these types of VMs as Excluded, with a message that explains the reason for the exclusion. (The option is available on the policy Clients tab.)
Changes that are made through Hyper-V Manager on individual Hyper-V hosts or clusters can take up to 24 hours to be reflected in SCVMM. This delay is due to the Microsoft SCVMM refresh cycle. In an SCVMM environment, Microsoft recommends making VM configuration changes through SCVMM (not through the Hyper-V Manager on individual hosts or clusters). Changes that are made through the SCVMM Console are reflected immediately in SCVMM.
In an SCVMM environment, the VM GUID is referred to as the VM ID.
If the SCVMM environment includes multiple VMs that have the same VM ID, each SCVMM refresh cycle reports only one of the VMs. Any other VM with the same VM ID is not visible. The NetBackup policy can back up only the VM that is currently reported or visible. Any other VM that has the same VM ID is not visible and is not backed up.
To make sure that NetBackup can discover and back up all VMs, avoid duplicate VM IDs in the SCVMM environment.
To back up VMs in an SCVMM environment, the NetBackup policy must use queries to select the VMs automatically (Hyper-V Intelligent Policy). If the query includes localized (non-English) values, the policy may not be able to select and back up the VMs.