Veritas NetBackup™ for Hyper-V Administrator's Guide
- Introduction
- Notes and prerequisites
- NetBackup for Hyper-V prerequisites
- NetBackup for Hyper-V notes and restrictions
- NetBackup character restrictions for Hyper-V virtual machine display names
- NetBackup character restrictions for vhd or vhdx names and the VM path when the Enable file recovery from VM backup option is used
- Notes on Linux virtual machines
- Configure NetBackup communication with Hyper-V
- Configure NetBackup policies for Hyper-V
- Creating a Hyper-V policy from the Policy Configuration Wizard
- Creating a Hyper-V policy from the NetBackup Policies utility
- Limit jobs per policy on the Attributes tab (for Hyper-V)
- Virtual machine host names and display names should be unique if VMs are selected manually in the policy
- Backup options on the Hyper-V tab
- Hyper-V - Advanced Attributes
- Provider Type configuration parameter (VSS)
- Snapshot Attribute configuration parameter (VSS)
- Virtual disk selection parameter (WMI)
- Existing snapshot handling parameter (WMI)
- Consistency level parameter (WMI)
- About the exclude disk options for virtual disk selection
- Virtual disk selection options: an example to avoid
- Restoring data from the backups that excluded the boot disk or data disks
- Browse for Hyper-V virtual machines
- Prerequisites for alternate client backup of a virtual machine (VSS)
- Configuring alternate client backup of virtual machines
- Requirements for a NetBackup client inside the virtual machine
- Configure Hyper-V Intelligent Policies
- About Hyper-V Intelligent Policy (automatic selection of virtual machines for backup)
- The basics of a NetBackup query rule
- Important notes on Hyper-V Intelligent Policy
- NetBackup requirements for Hyper-V Intelligent Policy
- Setting up Hyper-V Intelligent Policy: Task overview
- Options for selecting Hyper-V virtual machines
- Creating a Hyper-V policy for automatic virtual machine selection
- Editing a query in Basic Mode
- Using the Query Builder in Advanced Mode
- AND vs. OR in queries
- Examples for the NetBackup Query Builder
- The IsSet operator in queries
- About selecting virtual machines by means of multiple policies
- Order of operations in queries (precedence rules)
- Parentheses in compound queries
- Query rules for virtual machine Notes that contain a newline character
- Query Builder field reference
- Test Query screen for Hyper-V
- Test Query: Failed virtual machines
- Effect of Primary VM identifier parameter on Selection column in Test Query results
- Effect of Primary VM identifier parameter on VM Name column in Test query results
- Restoring a VM that was backed up with a Hyper-V Intelligent Policy and that has a pass-through disk
- NetBackup Hyper-V for SCVMM
- Windows Server failover cluster support
- About virtual machines on Windows 2008, 2012, and 2016 failover clusters
- Notes on CSV backup and restore
- Creating a policy for virtual machines in a cluster
- Location of the restored virtual machine in a cluster
- Virtual machine maintenance after a restore
- Hyper-V restore may fail if the VM was created on a CSV and the CSV is a reparse point on the destination drive
- Back up and restore Hyper-V
- Backing up Hyper-V virtual machines
- WMI backup method: State of the virtual machine before and after restore
- Notes on individual file restore
- Notes on full virtual machine restore
- About restoring individual files
- Restoring individual files to a host that has a NetBackup client
- Restore Marked Files dialog for restore of individual files
- Restoring individual files to a shared location on the virtual machine
- Restoring the full Hyper-V virtual machine
- Restore Marked Files dialog for restore of the Hyper-V virtual machine
- About restoring common files
- The BAR interface may list Hyper-V snapshot files when you browse to restore Hyper-V VM files
- Use Accelerator to back up Hyper-V
- About the NetBackup Accelerator for virtual machines
- Accelerator: full vs. incremental schedules
- How the NetBackup Accelerator works with virtual machines
- Accelerator notes and requirements for virtual machines
- Accelerator forced rescan for virtual machines (schedule attribute)
- Accelerator requires the OptimizedImage attribute
- Accelerator backups and the NetBackup catalog
- Accelerator messages in the backup job details log
- NetBackup logs for Accelerator with virtual machines
- About reporting the amount of Accelerator backup data that was transferred over the network
- Replacing the Accelerator image size with the network-transferred data in NetBackup command output
- Best practices and more information
- Troubleshooting
- NetBackup logs for Hyper-V and how to create them
- Errors during policy creation
- NetBackup status codes related to Hyper-V
- Backup job hangs for multiple virtual machines
- Viewing or resizing Windows NTFS shadow storage
- The Hyper-V integration component is not installed
- LDM volumes and status code 1
- Hyper-V snapshots (avhd or avhdx files) and status code 1
- Unable to log in to the NetBackup Administration Console
- When backing up the virtual machines that reside on the same CSV, Windows warning 1584 can be ignored
- Problems with alternate client backup
- Restored virtual machine fails to start
- Problem with a restart of a restored virtual machine: Why did the computer shut down unexpectedly?
- Problems with restore of individual files
- Problems with restore of the full virtual machine
- Unable to change virtual disk settings for a VM after restore if the VM had user checkpoints during a backup that used the WMI method
- Increasing the WMI create disk time-out value
- Linux VMs and persistent device naming
- Appendix A. VSS backup method: Hyper-V online and offline backups
- Appendix B. Hyper-V pass-through disks
- About Hyper-V pass-through disks with NetBackup
- Configurations for backing up pass-through disks
- Requirements for backing up Hyper-V pass-through disks
- Restrictions for Hyper-V pass-through disks
- Configuring a local snapshot backup of Hyper-V pass-through disks
- About alternate client backup of pass-through disks
- Configuring an alternate client backup of Hyper-V pass-through disks
- Important note on VSS and disk arrays
- Appendix C. NetBackup commands to back up and restore Hyper-V virtual machines
- Using NetBackup commands to create a Hyper-V policy
- Using NetBackup commands to create a Hyper-V Intelligent Policy
- The bpplinfo options for Hyper-V policies
- bpplinclude options for modifying query rules in Hyper-V policies
- Examples of nbrestorevm for restoring VMs to Hyper-V
- The nbrestorevm -R rename file for Hyper-V
- Notes on troubleshooting the nbrestorevm command for Hyper-V
- Logs for troubleshooting the nbrestorevm command
Notes on full virtual machine restore
Note the following:
A backup of the full virtual machine can be restored only to Windows Server with the Hyper-V role enabled.
By default, the NetBackup client on the Hyper-V server does not have Windows Administrator privileges. You can restore a full virtual machine from the NetBackup server. You cannot restore a full virtual machine from a NetBackup client that does not have Administrator privileges.
For the virtual machines that are configured in a volume GUID with a differencing disk in another volume GUID, redirected restores are not supported.
When you restore the virtual machine to its original location with the option, note: The same virtual machine on the Hyper-V server is automatically turned off and deleted before the restore. The vhd or vhdx files of the virtual machine on the Hyper-V server are overwritten by the vhd or vhdx files from the backup image. If any new vhd or vhdx files were created after the backup, those files are not removed.
When you restore the virtual machine to a different location on the original Hyper-V server or to a different server, note: The same virtual machine (if it exists) on the Hyper-V server is automatically turned off and deleted before the restore if you choose the option. The
.vhdor.vhdxfiles of the deleted virtual machine, however, are not deleted. You must delete those files.When you restore the virtual machine to a Hyper-V server that has a virtual machine of the same GUID, you must select the option. Otherwise, the restore fails.
If you restore a virtual machine without the option, note: You must remove the current virtual machine and its vhd or vhdx files from the destination server before you start the restore. If you remove the virtual machine but leave one or more of its virtual disk files on the destination server, the virtual disk files from the backup are not restored.
(This item is a limitation in VSS and the Hyper-V writer, not in NetBackup.) If the virtual machine contains Hyper-V snapshot files (avhd or avhdx files), NetBackup cannot restore the virtual machine to a different location or to a different Hyper-V server.
Note the following:
This issue has been fixed in Windows Server 2008 R2 (restore server).
This restriction does not apply in either of the following cases: When you restore the virtual machine to its original location on the original Hyper-V server, or when you restore to a staging location.
(This item is a limitation in VSS, not in NetBackup.) Immediately after a full virtual machine is restored, the virtual machine volume may be larger than it was when the virtual machine was backed up. The increase is normal: After the restore, snapshot-related cache files remain on the volume. After about 20 minutes, the cache files are automatically removed and the volume returns to its original size
Note: A new backup of the restored virtual machine could fail if the virtual machine volume contains insufficient space to create a snapshot for the backup. According to Microsoft, this situation should not occur as long as the virtual machine volume has at least 10 to 15% free space.
In the following case a race condition may result:
You attempt to do a full restore of two virtual machines at the same time.
The two virtual machines also share a virtual hard disk (vhd or vhdx file) that both restore jobs have selected to restore.
The two jobs may simultaneously attempt to access the same vhd or vhdx file, but only one job gains access to the file. The other job is denied access, and that job may fail with error code 185.
If you restore a virtual machine to a different Hyper-V server, the original Hyper-V server and the target server must have the same number of network adapters (NICs). You must configure the network adapter(s) for the restored virtual machine on the target server.
A restore of a virtual machine to an alternate location fails if any of its virtual disks has an ampersand (&) in its path. As a workaround, restore the virtual machine to its original location, or restore to a staging location and register the virtual machine manually.