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
Consistency level parameter (WMI)
Application Consistent Then Crash Consistent
NetBackup makes two attempts to quiesce I/O on the virtual machine for an application-consistent snapshot. If both attempts fail to create an application-consistent snapshot, NetBackup creates a crash-consistent snapshot and proceeds with the backup. (See the other two options for a description of application consistent and crash consistent.)
This setting is the default. I/O on the virtual machine is quiesced before NetBackup creates the snapshot. Without quiescing file activity, data consistency in the snapshot cannot be guaranteed. If not consistent, the backed-up data may be of little or no value.
If the virtual machine is in the saved state or the paused state, it cannot be quiesced and the backup job fails. You must use one of the other Consistency level options.
Note these prerequisites for theoption:
The latest version of Hyper-V integration services must be installed and running inside the VM.
The Hyper-V integration services must be enabled in the VM settings.
The snapshot is created without quiescing I/O on the virtual machine. In this case, you must perform your own analysis for data consistency in the backed-up data.
In most cases, Veritas does not recommend Crash Consistent. With this setting, NetBackup cannot guarantee that all required data has been flushed to disk when the snapshot occurs. The data that is captured in the snapshot may be incomplete.