Veritas NetBackup™ for Hyper-V Administrator's Guide

Last Published:
Product(s): NetBackup (8.2, 8.1.2, 8.1.1)
  1. Introduction
    1.  
      About Hyper-V
    2.  
      NetBackup for Hyper-V environment
    3.  
      Hyper-V terminology related to backup
    4.  
      Basic phases in a NetBackup backup of a Hyper-V virtual machine
    5.  
      NetBackup administrator tasks for Hyper-V
    6.  
      Quick reference for troubleshooting
  2. Notes and prerequisites
    1.  
      NetBackup for Hyper-V prerequisites
    2.  
      NetBackup for Hyper-V notes and restrictions
    3.  
      NetBackup character restrictions for Hyper-V virtual machine display names
    4.  
      NetBackup character restrictions for vhd or vhdx names and the VM path when the Enable file recovery from VM backup option is used
    5.  
      Notes on Linux virtual machines
  3. Configure NetBackup communication with Hyper-V
    1.  
      Changing the NetBackup Legacy Network Service logon (vnetd.exe) to the domain user account
    2.  
      Setting global limits on the use of Hyper-V resources
  4. Configure NetBackup policies for Hyper-V
    1.  
      Creating a Hyper-V policy from the Policy Configuration Wizard
    2.  
      Creating a Hyper-V policy from the NetBackup Policies utility
    3.  
      Limit jobs per policy on the Attributes tab (for Hyper-V)
    4.  
      Virtual machine host names and display names should be unique if VMs are selected manually in the policy
    5. Backup options on the Hyper-V tab
      1.  
        Optimization options (Hyper-V)
      2.  
        Primary VM identifier option (Hyper-V)
      3.  
        Enable offline backup of non-VSS VMs (Hyper-V with VSS)
      4.  
        Cluster shared volumes timeout (Hyper-V with VSS)
    6. Hyper-V - Advanced Attributes
      1.  
        Provider Type configuration parameter (VSS)
      2.  
        Snapshot Attribute configuration parameter (VSS)
      3.  
        Virtual disk selection parameter (WMI)
      4.  
        Existing snapshot handling parameter (WMI)
      5.  
        Consistency level parameter (WMI)
      6.  
        About the exclude disk options for virtual disk selection
      7.  
        Virtual disk selection options: an example to avoid
      8.  
        Restoring data from the backups that excluded the boot disk or data disks
    7. Browse for Hyper-V virtual machines
      1.  
        About cached names for virtual machine backup
    8.  
      Prerequisites for alternate client backup of a virtual machine (VSS)
    9.  
      Configuring alternate client backup of virtual machines
    10.  
      Requirements for a NetBackup client inside the virtual machine
  5. Configure Hyper-V Intelligent Policies
    1.  
      About Hyper-V Intelligent Policy (automatic selection of virtual machines for backup)
    2.  
      The basics of a NetBackup query rule
    3.  
      Important notes on Hyper-V Intelligent Policy
    4.  
      NetBackup requirements for Hyper-V Intelligent Policy
    5.  
      Setting up Hyper-V Intelligent Policy: Task overview
    6.  
      Options for selecting Hyper-V virtual machines
    7.  
      Creating a Hyper-V policy for automatic virtual machine selection
    8.  
      Editing a query in Basic Mode
    9.  
      Using the Query Builder in Advanced Mode
    10.  
      AND vs. OR in queries
    11.  
      Examples for the NetBackup Query Builder
    12.  
      The IsSet operator in queries
    13.  
      About selecting virtual machines by means of multiple policies
    14.  
      Order of operations in queries (precedence rules)
    15.  
      Parentheses in compound queries
    16.  
      Query rules for virtual machine Notes that contain a newline character
    17.  
      Query Builder field reference
    18.  
      Test Query screen for Hyper-V
    19.  
      Test Query: Failed virtual machines
    20.  
      Effect of Primary VM identifier parameter on Selection column in Test Query results
    21.  
      Effect of Primary VM identifier parameter on VM Name column in Test query results
    22.  
      Restoring a VM that was backed up with a Hyper-V Intelligent Policy and that has a pass-through disk
  6. NetBackup Hyper-V for SCVMM
    1.  
      About backup of virtual machines in an SCVMM environment
    2.  
      Notes on NetBackup for Hyper-V with SCVMM
    3.  
      Creating a query to back up VMs in a localized SCVMM environment
  7. Windows Server failover cluster support
    1.  
      About virtual machines on Windows 2008, 2012, and 2016 failover clusters
    2.  
      Notes on CSV backup and restore
    3.  
      Creating a policy for virtual machines in a cluster
    4.  
      Location of the restored virtual machine in a cluster
    5. Virtual machine maintenance after a restore
      1.  
        Removal of cluster resources during restore
    6.  
      Hyper-V restore may fail if the VM was created on a CSV and the CSV is a reparse point on the destination drive
  8. Back up and restore Hyper-V
    1.  
      Backing up Hyper-V virtual machines
    2.  
      WMI backup method: State of the virtual machine before and after restore
    3.  
      Notes on individual file restore
    4.  
      Notes on full virtual machine restore
    5.  
      About restoring individual files
    6.  
      Restoring individual files to a host that has a NetBackup client
    7.  
      Restore Marked Files dialog for restore of individual files
    8. Restoring individual files to a shared location on the virtual machine
      1.  
        Setting up NetBackup Client Service for restore to a shared location on the virtual machine
    9.  
      Restoring the full Hyper-V virtual machine
    10.  
      Restore Marked Files dialog for restore of the Hyper-V virtual machine
    11.  
      About restoring common files
    12.  
      The BAR interface may list Hyper-V snapshot files when you browse to restore Hyper-V VM files
  9. Use Accelerator to back up Hyper-V
    1.  
      About the NetBackup Accelerator for virtual machines
    2.  
      Accelerator: full vs. incremental schedules
    3.  
      How the NetBackup Accelerator works with virtual machines
    4.  
      Accelerator notes and requirements for virtual machines
    5.  
      Accelerator forced rescan for virtual machines (schedule attribute)
    6.  
      Accelerator requires the OptimizedImage attribute
    7.  
      Accelerator backups and the NetBackup catalog
    8.  
      Accelerator messages in the backup job details log
    9.  
      NetBackup logs for Accelerator with virtual machines
    10.  
      About reporting the amount of Accelerator backup data that was transferred over the network
    11.  
      Replacing the Accelerator image size with the network-transferred data in NetBackup command output
  10. Best practices and more information
    1.  
      Best practices
  11. Troubleshooting
    1. NetBackup logs for Hyper-V and how to create them
      1.  
        Enabling VxFI logging
      2.  
        Configuring VxMS and vhd logging
      3.  
        Format of the VxMS core.log and provider.log file names
    2. Errors during policy creation
      1.  
        NetBackup policy validation failed
    3. NetBackup status codes related to Hyper-V
      1.  
        Snapshot error encountered (status code 156)
    4.  
      Backup job hangs for multiple virtual machines
    5.  
      Viewing or resizing Windows NTFS shadow storage
    6.  
      The Hyper-V integration component is not installed
    7.  
      LDM volumes and status code 1
    8.  
      Hyper-V snapshots (avhd or avhdx files) and status code 1
    9.  
      Unable to log in to the NetBackup Administration Console
    10.  
      When backing up the virtual machines that reside on the same CSV, Windows warning 1584 can be ignored
    11.  
      Problems with alternate client backup
    12.  
      Restored virtual machine fails to start
    13.  
      Problem with a restart of a restored virtual machine: Why did the computer shut down unexpectedly?
    14.  
      Problems with restore of individual files
    15.  
      Problems with restore of the full virtual machine
    16.  
      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
    17.  
      Increasing the WMI create disk time-out value
    18.  
      Linux VMs and persistent device naming
  12. Appendix A. VSS backup method: Hyper-V online and offline backups
    1.  
      About Hyper-V online and offline backups for VSS
    2.  
      Conditions that determine online vs. offline backup for VSS
    3.  
      Additional notes on offline backups with VSS
    4.  
      Hyper-V 2012 R2 virtual machines may be in the Off state when restored
  13. Appendix B. Hyper-V pass-through disks
    1.  
      About Hyper-V pass-through disks with NetBackup
    2.  
      Configurations for backing up pass-through disks
    3.  
      Requirements for backing up Hyper-V pass-through disks
    4.  
      Restrictions for Hyper-V pass-through disks
    5.  
      Configuring a local snapshot backup of Hyper-V pass-through disks
    6.  
      About alternate client backup of pass-through disks
    7.  
      Configuring an alternate client backup of Hyper-V pass-through disks
    8.  
      Important note on VSS and disk arrays
  14. Appendix C. NetBackup commands to back up and restore Hyper-V virtual machines
    1.  
      Using NetBackup commands to create a Hyper-V policy
    2.  
      Using NetBackup commands to create a Hyper-V Intelligent Policy
    3.  
      The bpplinfo options for Hyper-V policies
    4.  
      bpplinclude options for modifying query rules in Hyper-V policies
    5. Examples of nbrestorevm for restoring VMs to Hyper-V
      1.  
        Hyper-V examples of restore to original location
      2.  
        Hyper-V examples of restore to alternate locations
    6.  
      The nbrestorevm -R rename file for Hyper-V
    7.  
      Notes on troubleshooting the nbrestorevm command for Hyper-V
    8.  
      Logs for troubleshooting the nbrestorevm command

Problems with restore of the full virtual machine

Restores of a full Hyper-V virtual machine may fail in the following cases.

The "Overwrite virtual machine" option was not selected and vhd or vhdx file(s) for the virtual machine still exist on the destination.

The vhd or vhdx file(s) from the backup are not restored. You must select Overwrite virtual machine for the restore, or remove the current virtual machine and vhd or vhdx files from the destination server before you start the restore. If you remove the virtual machine but leave one or more vhd or vhdx files at the destination, the vhd or vhdx files from the backup are not restored.

The virtual machine restore job fails but the virtual machine is nonetheless registered in the Hyper-V server.

The Hyper-V-VMMS writes the following warnings in the events log:

Event ID: 10127, sample event log message:

Unable to repair the network configuration for virtual machine'Virtual Machine
Display Name'. The virtual machine may not have the same network connectivity as 
it did when the backup was taken. Inspect the network settings and modify them 
as necessary. (Virtual machine ID 0AD8DFCC-BDC0-4818-B6DF-7A1BA0A735BF)

Event ID: 10104, sample event log message:

One or more errors occurred while restoring the virtual machine from backup. 
The virtual machine might not have registered or it might not start. (Virtual 
machine ID "0AD8DFCC-BDC0-4718-B6DF-7A3BA2A735BF ")

The Hyper-V writer encountered a Network configuration error. The restored virtual machine can be started after you change the Network Adaptor configuration in the virtual machine settings.

The virtual machine is highly available (HA), but the node that owns the virtual machine is not the restore server. (The node that owns the virtual machine is not the node that performs the restore.)

The tar log contains a message similar to the following:

VssNode::doRestore: Current owner of VM .[<VM name> {<VM guid>}] is 
[<current owner>] not this [<restore server>], To perform this restore either move 
VM to this host [<restore server>] or Delete VM from Cluster, or perform redirected 
restore at current owner.

Note the following explanations:

  • For a restore to the original location: When the backup took place, the virtual machine was not HA, but now the virtual machine is HA. However, the node that owns the virtual machine is not the node from which the virtual machine was backed up.

  • For a redirected restore: The virtual machine is HA but the node that owns the virtual machine is not the restore server (the node that performs the restore).

    See the recommended actions in the tar log message.

A redirected restore of a volume-GUID-based virtual machine fails if the virtual machine was backed up from a previous redirected restore.

Note: In a redirected restore, the virtual machine is restored to a different location on the original Hyper-V server or to a different Hyper-V server. It is not restored to its original location on the original server.

A virtual machine may be configured on a Windows volume GUID. The following is an example of a Windows volume GUID:

\\?\Volume{1a2b74b1-1b2a-11df-8c23-0023acfc9192}\

If you perform a redirected restore of a volume-GUID-based virtual machine and you back up the restored virtual machine, note: An attempt to do a redirected restore from the backup may fail. For example, consider a virtual machine that is configured on the following volume GUID:

\\?\Volume{1a2b74b1-1b2a-11df-8c23-0023acfc9192}\

The virtual machine is then restored to a different volume GUID, such as:

\\?\Volume{2a3b70a1-3b1a-11df-8c23-0023acfc9192}\

If the restored virtual machine is backed up and you do a redirected restore from the backup, the restore may fail.

To avoid this problem in a redirected restore, restore the virtual machine to a subdirectory of the volume GUID, such as to the following:

\\?\Volume{1a3b70a1-3b1a-11df-8c23-0023acfc9192}\REDIR_subdirectory\
NetBackup cannot perform a redirected restore of a virtual machine to a Hyper-V 2008 R2 server if the virtual machine contains a compressed vhd or vhdx file.

The NetBackup job Detailed Status tab contains a message similar to the following:

12/11/2009 17:35:58 - started process bpdm (pid=2912) 
...
the restore failed to recover the requested files  (5)
12/11/2009 17:47:06 - Error bpbrm (pid=1348) client restore EXIT STATUS 185: tar
did not find all the files to be restored

A message similar to the following appears in the eventvwr.msc file:

Failed to update the configuration with the new location of virtual hard disk 
'F:\REDIR_VM\f\ADD_VHD\IDE_1_DISK.vhd' for virtual machine 
'<virtual_machine_name>': The requested operation could not be 
completed due to a virtual disk system limitation.  Virtual disks are only 
supported on NTFS volumes and must be both uncompressed and unencrypted. 
(0xC03A001A). Remove the disk from the virtual machine and then attach the disk 
from the new location. (Virtual machine ID <virtual_machine_ID.)

This issue is due to a Microsoft limitation. See the following Microsoft link for more information:

http://technet.microsoft.com/en-us/library/dd440865.aspx

Restore of a Windows 2016 Hyper-V VM to an SMB 3.0 file share may complete with only partial success.

If sufficient permissions are not set on the destination file share, the restore completes with status 1, "The requested operation was partially successful." Messages similar to the following appear in the NetBackup job details log:

Unable to set VHD/VHDX metadata which includes alternate data streams
and permissions. If VM does not boot, check the permissions of the
VM's virtual disk files.

Note:

The VM's files are restored, but NetBackup was unable to restore the owner of the vhd or vhdx file(s).

For a fully successful restore, do the following:

  • Add permissions to the share and to the underlying file system where the data resides. The permissions must give Full Control to the Hyper-V server and to the Hyper-V cluster.

  • On the Hyper-V server to which the VM is to be restored: Make sure that the NetBackup Client Service is running as Domain\Administrator and not as the LocalSystem user account.

When these changes are complete, rerun the restore. The restore job should return status 0, "the requested operation was successfully completed."