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
Accelerator notes and requirements for virtual machines
Note the following about Accelerator for virtual machines:
Accelerator for Hyper-V is available for virtual machines on Hyper-V Server 2016 and later. In a Hyper-V policy, click the policy's Hyper-V tab and select . Then select and .
Accelerator for virtual machines uses Hyper-V resilient change tracking (RCT) to identify the changes that were made within a virtual machine.
After the first Accelerator backup: If you create a checkpoint on the VM (or delete a checkpoint), the next backup from that policy is a full backup. That is, the backup processing for the second backup is not limited to changed blocks: Under Accelerator Optimization in the NetBackup Activity Monitor, the optimization rate is 0%.
If you create another checkpoint and run a third Accelerator backup: The optimization rate may increase, depending on the amount of data that is captured in the checkpoint (the size of the checkpoint file). The smaller the checkpoint file, the higher the rate of optimization in the third backup.
Similarly, if a checkpoint is deleted after the second backup, the optimization rate in the next backup depends on the size of the virtual disk that was affected by the checkpoint deletion.
Supports the disk storage units that have the following storage destinations:
Cloud storage. Storage that a supported cloud storage vendor provides.
NetBackup Media Server Deduplication Pool. In addition to NetBackup media servers, NetBackup 5200 series appliances support Media Server Deduplication Pool storage.
Qualified third-party OpenStorage devices.
To verify that your storage unit supports Accelerator, refer to the NetBackup hardware compatibility list for the currently supported OST vendors:
Veritas recommends that you not enable Expire after copy retention for any storage units that are used with storage lifecycle policies (SLP) in combination with Accelerator. The Expire after copy retention can cause images to expire while the backup runs. To synthesize a new full backup, the SLP backup needs the previous backup image. If the previous image expires during the backup, the backup fails.
Update the NetBackup device mapping files if needed.
The NetBackup device mapping files contain all storage device types that NetBackup can use. To add support for the new devices or upgraded devices that support Accelerator, download the current device mapping files from the Veritas support site.
See the NetBackup Administrator's Guide Volume I for information on the device mapping files and how to download them.
Storage unit groups are supported only if the storage unit selection in the group is Failover.
Supports the full backups and incremental backups. Every Accelerator backup (from a full schedule or incremental schedule) results in a complete image of the virtual machine.
You can use incremental backups (cumulative or differential) as follows: To reduce the file-mapping overhead and to reduce the number of files that are recorded in the NetBackup catalog. Cumulative backups may involve more file-mapping because they do not use the random indexing method to determine which files have changed. In some cases, differential backups may be faster than cumulative backups.
If a backup of the virtual machine does not exist, NetBackup performs a full backup. This initial backup occurs at the speed of a normal (non-accelerated) full backup. Subsequent Accelerator backups of the virtual machine use resilient change tracking (RCT) to accelerate the backup.
If the storage unit that is associated with the policy cannot be validated when you create the policy, note: The storage unit is validated later when the backup job begins. If Accelerator does not support the storage unit, the backup fails. In the bpbrm log, a message appears that is similar to one of the following:
Storage server %s, type %s, doesn't support image include.
Storage server type %s, doesn't support accelerator backup.
Accelerator requires the storage to have the
OptimizedImageattribute enabled.