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
- 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)
- Configure an 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
- Edit or remove 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
- 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 Hyper-V files to a host that has a NetBackup client
- Restore options for restore of Hyper-V individual files (NetBackup web UI)
- Restoring individual Hyper-V files to a shared location on the virtual machine
- Restoring the full Hyper-V virtual machine
- Restore Options
- 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
- 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
- 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
- Notes on Hyper-V policy attributes when you use the NetBackup commands
- The bpplinfo options for 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
Problems with restore of individual files
When you restore individual files (not the entire virtual machine), the restore may fail in certain cases. The following table describes the problems and recommended actions for the restore of individual files.
Table: Problems with restore of individual files
Cause of the problem | Description and recommended action |
|---|---|
Files are selected from multiple drives (volumes) on the virtual machine. | For example: The original virtual machine had two drives (C:\ and D:\), and files from each drive are selected in the same restore operation. Messages similar to the following appear in the job progress log: 13:26:05 (86.001) (86.001) INF - Skipping to next file header... 13:26:05 (86.001) (86.001) INF - TAR EXITING WITH STATUS = 0 13:26:05 (86.001) (86.001) INF - TAR RESTORED 11368 OF 11463 FILES SUCCESSFULLY 13:26:05 (86.001) (86.001) INF - TAR KEPT 0 EXISTING FILES 13:26:05 (86.001) (86.001) INF - TAR PARTIALLY RESTORED 0 FILES 13:26:15 (86.001) Status of restore from image created 7/21/2008 2:55:05 PM = the requested operation was partially successful Select files from a single drive at a time. Selecting files from multiple drives is not supported. |
You have attempted to restore the files into a mapped drive on the virtual machine. The restore fails with NetBackup status code 185. | Restore the files by means of a shared location on the virtual machine (with a UNC path) rather than by means of a mapped drive. See Restoring individual Hyper-V files to a shared location on the virtual machine. |
The snapshot contains invalid inodes. | Windows Hyper-V provides no mechanism for quiescing file system activity on Linux virtual machines. As a result, invalid inodes may be present in the snapshot. A backup that was made with the option may have file-mapping failures if the virtual machine experiences heavy I/O. The failures are reported in the NetBackup Administration Console in this form: ERR - Unable to read metadata for index: 379023, VFM error = 6. Note that the backup succeeds, but any files with metadata errors cannot be restored individually. For the backups that enable individual restore of all files, schedule the backup when the I/O activity is lower. If metadata errors persist, shut down the virtual machine during the backup. |