Netbackup for Hyper-V Guide

Veritas NetBackup™ forHyper-V Guide

UNIX, Windows, and Linux

Release 6.5.4

Veritas NetBackup™ for Hyper-V GuideThe software described in this book is furnished under a license agreement andmay be usedonly in accordance with the terms of the agreement.

Documentation version 6.5.4.

Legal NoticeCopyright © 2009 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo and NetBackup are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.

Portions of this software are derived from the RSAData Security, Inc. MD5Message-DigestAlgorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The LicenseAgreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see theThird Party LegalNoticeAppendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THEDOCUMENTATIONISPROVIDED"ASIS"ANDALLEXPRESSORIMPLIEDCONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBELEGALLYINVALID.SYMANTECCORPORATIONSHALLNOTBELIABLEFORINCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software andDocumentation are deemed to be commercial computer softwareas defined in FAR12.212 and subject to restricted rights as defined in FARSection 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software andDocumentation by theU.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. TheTechnical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, theTechnical Support groupworkswithProductEngineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s maintenance offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and Web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrade protection

■ Global support that is available 24 hours a day, 7 days a week

■ Advanced features, including Account Management Services

For information about Symantec’sMaintenance Programs, you can visit ourWebsite at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomerswith a currentmaintenance agreementmay access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer onwhich theproblemoccurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level

■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system



■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf yourSymantecproduct requires registrationor a licensekey, access our technicalsupport Web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with the following types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and maintenance contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Maintenance agreement resourcesIf you want to contact Symantec regarding an existing maintenance agreement,please contact the maintenance agreement administration team for your regionas follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you tomaximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

These solutions provide early warning of cyber attacks, comprehensive threatanalysis, and countermeasures to prevent attacks before they occur.

SymantecEarlyWarningSolutions

These services remove the burdenofmanaging andmonitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trustedpartners. SymantecConsultingServices offer a varietyof prepackaged and customizable options that include assessment, design,implementation,monitoring, andmanagement capabilities. Each is focused onestablishing andmaintaining the integrity and availability of your IT resources.

Consulting Services

Educational Services provide a full array of technical training, securityeducation, security certification, and awareness communication programs.

Educational Services

To access more information about Enterprise services, please visit our Web siteat the following URL:

www.symantec.com

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

About Hyper-V .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9NetBackup for Hyper-V environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Basic phases in a NetBackup backup of a Hyper-V virtual

machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Hyper-V terminology related to backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12NetBackup administrator tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Quick reference for troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Prerequisites and other notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Use of fully qualified names for virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Restrictions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Chapter 3 Create a backup policy for Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring a Hyper-V policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Chapter 4 Back up and restore Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Backing up Hyper-V virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Restore notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Notes on individual file restore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Notes on full virtual machine restore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

About restoring individual files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Restoring individual files to a host that has a NetBackup client ... . . . . . . . . . 29Restoring individual files to a shared location on the virtual

machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Setting up NetBackup Client Service for restore to a shared

location on the virtual machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Restoring the full virtual machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33About restoring common files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Contents

Chapter 5 Best practices and more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Best practices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41More information on NetBackup and Hyper-V .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Chapter 6 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

NetBackup logs and how to create them .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Other logs for troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Enabling VxMS and vhd logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Enabling VxFI logging .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

NetBackup policy validation failed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46NetBackup status codes related to Hyper-V .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Snapshot error encountered (status code 156) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Backup job hangs for multiple virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Windows NTFS shadow storage has insufficient space for

snapshots ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Storage unit characteristics mismatched to request (status code

154) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51The Hyper-V integration component is missing or not properly

installed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52NTFS shadow storage is configured on a different volume .... . . . . . . . . . . . . . . . 52The backup job is partially successful (status code 1) ... . . . . . . . . . . . . . . . . . . . . . . . 54Restored virtual machine fails to start ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Problems when restoring individual files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Problems when restoring the full virtual machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . 55Problem when starting a restored virtual machine: "Why did the

computer shut down unexpectedly?” . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Appendix A Hyper-V online and offline backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

About Hyper-V online and offline backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57When online vs offline backup is performed .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Additional notes on offline backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Contents8

Introduction

This chapter includes the following topics:

■ About Hyper-V

■ NetBackup for Hyper-V environment

■ Basic phases in a NetBackup backup of a Hyper-V virtual machine

■ Hyper-V terminology related to backup

■ NetBackup administrator tasks

■ Quick reference for troubleshooting

About Hyper-VNetBackup forHyper-V provides snapshot-based backup of virtualmachines thatrun on Windows 2008 Hyper-V servers.

The principal features of NetBackup for Hyper-V are the following:

■ Uses snapshot technology to keep virtual machines 100% available to users.Creates quiesced snapshots using Volume Shadow Copy Service (VSS).

■ Performs full backups of the virtual machine, including Hyper-V commonfiles.

■ Can restore individual files in the virtual machine or the full virtual machine.

■ Can restore to the original virtual machine, to other locations on the Hyper-Vserver, or to a different Hyper-V server or other host.

NetBackup for Hyper-V environmentThis section introduces the components of NetBackup for Hyper-V.

1Chapter

Table 1-1 describes the components that are required to back up and restore aHyper-V virtual machine.

Table 1-1 Components required for NetBackup for Hyper-V

Description and requirementsComponent

Creates backup policies and starts backups and restores. TheNetBackup master server must be at 6.5.4 or later. It mustinclude the NetBackup Enterprise Client license.

NetBackup master server

Reads andwrites backupdata andmanagesNetBackup storagemedia. The NetBackup media server must be at 6.5.4 or later.The NetBackup media server can be installed on the Hyper-Vserver or on a different host.

For a more efficient backup, install the NetBackup mediaserver on the same host as the Hyper-V server.

NetBackup media server

Processes backup and restore requests. A NetBackup 6.5.4client must exist on each Hyper-V server.

Note: The client need not be installed on any virtualmachine,except as an option for one of the individual file restoremethods.

See “About restoring individual files” on page 28.

NetBackup client

A Windows hypervisor-based virtualization system, forcreating the virtualized operating systems that run inWindows Server 2008 on an x64-based computer.

Additional hardware requirements may apply. Refer to yourMicrosoft Hyper-V documentation.

Hyper-V server

Provides integration between the Hyper-V server and thevirtual machines.

Note: The Hyper-V backup integration service must beenabled.

For installation instructions, refer to Microsoft Hyper-Vdocumentation.

Hyper-V integrationservices (integrationcomponents)

Figure 1-1 shows the NetBackup for Hyper-V environment.

IntroductionNetBackup for Hyper-V environment

10

Figure 1-1 NetBackup for Hyper-V backup environment

NetBackup 6.5.4master server

NetBackup 6.5.4 mediaserver with externalstorage (tape or disk).

Windows 2008 Hyper-V server withvirtual machines. Each Hyper-V serverneeds one NetBackup 6.5.4 client.

LAN / WAN

Basic phases in a NetBackup backup of a Hyper-Vvirtual machine

Table 1-2 describes the phases of the NetBackup for Hyper-V backup process.

Table 1-2 Phases of NetBackup for Hyper-V backup

DescriptionPhase

The NetBackup master server initiates the backup.Phase 1

The NetBackup client on the Hyper-V server initiates a snapshot.Phase 2

TheVSSHyper-Vwriter quiesces the virtualmachine and creates the snapshoton the host volume. If theHyper-Vwriter cannot quiesce the virtualmachine,the virtualmachine is placed in the Saved state before creation of the snapshot.

Phase 3

TheNetBackup client reads the data from the snapshot of the virtualmachineand transfers the data to the media server. The media server writes the datato the NetBackup storage unit.

Phase 4

If the virtual machine was placed in the Saved state, Hyper-V returns thevirtual machine to its original state.

Phase 5

11IntroductionBasic phases in a NetBackup backup of a Hyper-V virtual machine

Hyper-V terminology related to backupTable 1-3 Hyper-V terminology related to backup

DescriptionTerm

A snapshot file that was created by Windows Server 2008 Hyper-V,for point-in-time recovery of the virtual machine.

This snapshot and recovery mechanism is entirely separate from theone used by NetBackup for Hyper-V. NetBackup creates its ownsnapshots when it backs up virtual machines. NetBackup does notcreate Hyper-V .avhd files.

.avhd file

A virtual disk ( .vhd file) that contains files that are required by morethan one virtual machine. Instead of copies of the same .vhd fileexisting at multiple places, a single .vhd file (the parent) is shared bymultiple virtual machines.

See “About restoring common files” on page 38.

Common .vhd files

The differencing disk is in a child relationship to the parent disk (seecommon .vhd files). The parent and child virtual disks may be on thesame physical drive or on different physical drives. This mechanismenables common files to be shared across virtual machines.

Differencing disk

A file in a Windows 2008 Hyper-V installation that contains thevirtualized contents of a hard disk. A .vhd file can contain an entirevirtual operating system and its programs. Hyper-V supports severalkinds of .vhd files, such as fixed, dynamic, and differencing.

Refer to yourMicrosoftHyper-v documentation formore information.

.vhd file

NetBackupbacks up these files as part of a full virtualmachine backup.

The .bin and .vsv files are visible only when the virtual machine isrunning.

virtual machineconfiguration files(.xml, .bin, .vsv)

A globally unique identifier of the virtual machine.virtual machineGUID

NetBackup administrator tasksThe following are the tasks for the NetBackup administrator:

■ Install the NetBackup 6.5.4 master server and media server.See the NetBackup 6.5 Installation Guide.Symantec recommends that the NetBackup media server and the Hyper-Vserver be installed on the same host.

IntroductionHyper-V terminology related to backup

12

■ Install theNetBackup 6.5.4 Enterprise Client license on themaster server, andinstall Snapshot Client 6.5.4 software on the Hyper-V server. Only oneNetBackup client is required on eachHyper-V server. As an option for restore,a client may be installed on a virtual machine.For Snapshot Client installation instructions, see the Installation chapter ofthe NetBackup Snapshot Client Administrator’s Guide.For Windows, NetBackup Snapshot Client software is automatically installedwith the core NetBackup server and client product.

■ Read the notes on NetBackup for Hyper-V.See “Notes” on page 17.See “Restore notes” on page 26.

■ Read the best practices.See “Best practices” on page 41.

■ Create a NetBackup Snapshot Client policy for Hyper-V.See “Configuring a Hyper-V policy” on page 19.

■ Run a Hyper-V backup.See “Backing up Hyper-V virtual machines” on page 25.

■ Perform a restore.See “About restoring individual files” on page 28.See “Restoring the full virtual machine” on page 33.

■ Troubleshoot your configuration.See the Troubleshooting chapter.

Quick reference for troubleshootingConsult the following topics for troubleshooting tips and pointers:

■ See “NetBackup status codes related to Hyper-V” on page 47.

■ See “NetBackup logs and how to create them” on page 44.

13IntroductionQuick reference for troubleshooting

IntroductionQuick reference for troubleshooting

14

Prerequisites and othernotes


■ Prerequisites

■ Use of fully qualified names for virtual machines

■ Notes

■ Restrictions

PrerequisitesThe following prerequisites apply to NetBackup for Hyper-V:

■ The NetBackup master server, media server, and client must be at NetBackupversion 6.5.4 or later.

■ Apply the following hot fixes on the Hyper-V server.

■ http://support.microsoft.com/kb/959962An update for Windows Server 2008-based computers to address issueswith backing up and restoring Hyper-V virtual machines.

■ http://support.microsoft.com/default.aspx/kb/956697An update for an unsuccessful virtual machine restore. The unsuccessfulrestore causes an invalid link to the virtual machine configuration XMLfile that was created at the following:%SystemDrive%\ProgramData\Microsoft\Windows\Hyper-V\VirtualMachines

■ http://support.microsoft.com/KB/959978

2Chapter

An update for the VSS hardware provider snapshot for Hyper-V, to avoida Hyper-V writer crash during backup.

■ Check with Microsoft to see if additional hot fixes have been released.

■ Before starting a backupof a virtualmachine, verify that theNetBackupmasterserver and media server can communicate with the Hyper-V server.

■ For backups, NetBackup uses the fully qualified host name of the virtualmachine, if that name is available. If a fully qualified name is not available,NetBackup uses the virtual machine name as it appears in the Hyper-VManager. In this case, the name that appears on the Hyper-V Manager mustbe the same as the fully qualified host name of the virtual machine.See “Use of fully qualified names for virtual machines” on page 16.

■ To restore files to a shared location on the virtual machine, note: virtualmachinesmust be in the same domain as theNetBackup client andmaster andmedia server.

■ On a virtualmachine,Windows shadow storage for a volume (such as C:) mustbe on the same volume. For instance, if the virtual machine has multiplevolumes, and the shadow storage for the C: volume is on D:, the backup fails.See “ NTFS shadow storage is configured on a different volume” on page 52.Windows shadow storage is required whenever theWindows Volume ShadowCopy Service (VSS) creates point-in-time snapshots.

Use of fully qualified names for virtual machinesFor backups, NetBackupuses the fully qualified host nameof the virtualmachine,if that name is available. If a fully qualified name is not available, NetBackup usesthe virtual machine name as it appears in the Hyper-V Manager. The Hyper-Vdisplay name of the virtual machine must be the same as the fully qualified hostname. Otherwise, see the following notes.

The NetBackup policy maintains a cache file of virtual machine names. You canselect a virtual machine name from the list in the cache file, rather than waitingto rediscover the machines on the network. This approach can save time if yoursite has a large number of virtual machines.

Discrepancies may exist in the list of virtual machine names. On the Clients tabof the NetBackup policy Attributes dialog, click the refresh icon to the right ofthe Last Update field to update the list of virtual machines.

See “Configuring a Hyper-V policy” on page 19.

Note the following:

Prerequisites and other notesUse of fully qualified names for virtual machines

16

■ If you create a policy and later change the display name of the virtualmachinein theHyper-VManager, thenewnamemaynot beused for backups.NetBackupcontinues to use the fully qualified host name: thename is obtained fromeitherthe cached list of names or from a new virtual machine that is turned on.

■ If a recently created virtual machine is turned off during its first backup,NetBackup cannot obtain a fully qualified name for thatmachine. In this case,NetBackup backs up the virtual machine with the name that appears in theHyper-V Manager. When the virtual machine is turned on, the NetBackupcache file is updated to use the fully qualified host name to identify the virtualmachine. Policies that refer to the Hyper-V display name rather than to thefully qualified name will be unable to locate the virtual machine. You mustupdate the client list in such policies to refer to the fully qualified name. (TheHyper-V display name of the virtual machine should be the same as the fullyqualified host name.)

NotesNote the following:

■ If a virtual machine is Paused when the backup starts, the virtual machine isplaced in the Saved state after the backup completes.

■ For VSS with disk arrays:To use a hardware array snapshot, make sure that the hardware array's VSSprovider supports snapshots that involve theHyper-Vwriter. Check the releasenotes of the array vendor or VSS provider.

■ More information about NetBackup for Hyper-V support is available in thefollowing Symantec tech note:http://entsupport.symantec.com/docs/312604

RestrictionsNote the following:

■ NetBackup for Hyper-V does not yet support incremental backups of virtualmachines. Only full backup schedules are currently supported.

■ NetBackup for Hyper-V does not yet support the NetBackup Instant Recoveryfeature.

■ NetBackup for Hyper-V does not yet support off-host backup of virtualmachines.

17Prerequisites and other notesNotes

■ (The following is due to a Microsoft limitation.) NetBackup for Hyper-V doesnot support backup of pass through or iSCSI diskswhile backing up the virtualmachine. Pass through or iSCSI disks are skipped when the virtual machineis backed up.

■ (The following is due to a Microsoft limitation.) NetBackup for Hyper-V doesnot support backup of encrypted .vhd files.

■ (The following is due to aMicrosoft limitation.) For virtualmachines that havea FAT or FAT32 file system,NetBackup supports onlyHyper-V offline backup.See “About Hyper-V online and offline backups” on page 57.

Prerequisites and other notesRestrictions

18

Create a backup policy forHyper-V


■ Configuring a Hyper-V policy

Configuring a Hyper-V policyBefore you configure a policy, make sure that the Hyper-V server is online.NetBackup must be able to communicate with the Hyper-V server.

Use the followingprocedure to create a policy forHyper-Vvirtualmachine backup.

3Chapter

To configure a policy for Hyper-V

1 Start the NetBackup Administration Console as follows:

On UNIX, enter: /usr/openv/netbackup/bin/jnbSA &

On Windows, click Start > Programs > Veritas NetBackup > NetBackupAdministration Console.

2 Click on Policies and click Actions > New to create a new policy, or select apolicy to edit.

Create a backup policy for Hyper-VConfiguring a Hyper-V policy

20

3 Select FlashBackup-Windows as the policy type.

The FlashBackup-Windows policy type automatically selects Performsnapshot backups.

4 Select a policy storage unit or storage unit group (or Any Available).

5 Select Hyper-V.

6 In the Hyper-V server name field, enter the name of the Hyper-V server.

7 Click Snapshot Options.

The following is the upper half of the Snapshot Client Options dialog:

8 Select the Virtual Machine Backup option:

Backs up the entire virtual machine.

You can restore the entire virtual machine from this backup.Individual files in the virtual machine cannot be restored fromthis backup.

1-FullVM

Backs up the entire virtual machine. This option is the default.

Two kinds of restores are possible: restore of the entire virtualmachine, or restore of individual folders and files.

2-Mapped FullVM

21Create a backup policy for Hyper-VConfiguring a Hyper-V policy

9 Select the Provider Type:

This attribute determines the type of VSS snapshot provider that creates thesnapshot.

Attempts to select the available provider in this order: hardware,then software, then system.

0-auto

Uses the Microsoft system provider, for a block-level copy on writesnapshot.

Unlike option 3, the Microsoft system provider does not require anyadditional hardware.

1-system

Not certified in this release.2-software

Uses the hardware provider for a disk array. A hardware providermanages the VSS snapshot at the hardware level by working with ahardware storage adapter or controller.

For example, if you want to back up an EMC CLARiiON or HP EVAarray by means of the array’s snapshot provider, select 3-hardware.Depending on your array and on the snapshot attribute you select,certain preconfiguration of the array may be required.

See the appropriate topic for your disk array in the NetBackupSnapshot Client Administrator's Guide.

3-hardware

10 Select the Snapshot Attribute:

This attribute determines the type of VSS snapshot to be created.

Uses the default snapshot type of the VSS provider.0-unspecified

Uses a copy-on-write type of snapshot. For example, to back up anEMC CLARiiON array with an EMC CLARiiON SnapView Snapshot,select 1-differential.

1-differential

Uses a clone snapshot or mirror snapshot. For example, to back upanHP EVA array with anHP EVA Snapclone snapshot, select 2-plex.

2-plex

11 To save these settings, click OK.

12 Use the Schedules tab to define a schedule.

Currently, NetBackup for Hyper-V supports full backups only (notincremental).


22

13 On the Clients tab, click New to specify virtual machines to back up.

14 You can do the following:

■ Enter the name of a virtual machine. The format of the name depends onyour system. It may be the fully qualified name or another name,depending on your network configuration and how the name is definedin the guest OS. If NetBackup cannot find the name you enter, policyvalidation fails.If it is checked, uncheck the Browse Virtual Machines box.

■ To discover virtual servers on the network and select virtual machinesfrom a list, check the Browse Virtual Machines box.You can use the Find field to locate a virtual machine in the list.

■ The virtual machine names that are listed may be derived from a cachefile. Use of the cache file is faster than rediscovering themachines on thenetwork if your site has a large number of virtual machines. If the virtualmachine is turned off, but it was turned on when the cache file was lastcreated, its name is displayed in the list.If the display name of the virtual machine was recently changed in theHyper-V Manager, note: the virtual machine name that was used for thebackupdoes not change.NetBackupuses the fully qualifiedmachinenameif that name is available.See “Use of fully qualified names for virtual machines” on page 16.

23Create a backup policy for Hyper-VConfiguring a Hyper-V policy

■ To update the cache file and re-display virtualmachines, click the refreshicon to the right of the Last Update field. This field shows the date andtime of the most recent cache file that contains the names of virtualmachines.

15 Click OK.

The virtual machines you selected are listed in the Clients tab.

16 On the Backup Selections tab, select ALL_LOCAL_DRIVES.ALL_LOCAL_DRIVES is the only backup selection that is supported forHyper-V virtual machines. NetBackup backs up all local drives on the virtualmachines that are selected on the Clients tab.


24

Back up and restoreHyper-V


■ Backing up Hyper-V virtual machines

■ Restore notes

■ About restoring individual files

■ Restoring individual files to a host that has a NetBackup client

■ Restoring individual files to a shared location on the virtual machine

■ Restoring the full virtual machine

■ About restoring common files

Backing up Hyper-V virtual machinesYou can initiate a Hyper-V virtual machine backup in the same manner as anyNetBackup backup.

Note: NetBackup for Hyper-V does not support user backups: only manual orscheduled backups are allowed.

To back up a virtual machine manually

1 Click on the Policies node in the NetBackup Administration Console, selectthe policy, and click Actions > Manual Backup.

2 For further instructions, see the Backup, Archive, and Restore online Helpor the NetBackup Backup, Archive, and Restore Getting Started Guide.

4Chapter

Restore notesThis topic describes important points on restore.

Notes on individual file restoreNote the following:

■ If you are running antivirus protectiononHyper-Vvirtualmachines, SymantecrecommendsSymantec Endpoint Protection 11.0MaintenanceRelease 4 (build11.0.4000) or later. Restores of virtual machine files complete faster if thevirtual machine is running this version as opposed to an earlier version ofEndpoint Protection.

■ To restore an individual file that is larger than approximately 2 GB, restorethe file to a host that has a NetBackup client. NetBackup for Hyper-V does notcurrently support restores of large files by means of a shared location on thevirtualmachine. This file size restriction does not apply to restore of an entirevirtual machine.See “Restoring individual files to a host that has a NetBackup client ”on page 29.

■ Fromabackup image thatwasmadewith the 2-MappedFullVMbackupoption:if you select individual files to restore, the selected files must have originallyresided on the same virtual machine volume. If some of the selected filesresided onone volumeandother files resided on adifferent volume, the restorefails.

■ Files that use NTFS-file system features cannot retain those features if youattempt to restore the files to a FAT or FAT32 file system.

Note the following:

■ Files thatwere compressedunderNTFSare restored as uncompressed filesin a FAT or FAT32 file system.

■ Files thatwere encryptedunderNTFS cannot be restored to a FATor FAT32file system.

■ Files that had NTFS-based security attributes are restored without thoseattributes in a FAT or FAT32 file system.

■ The restore failswithNetBackup status 5when the files that have alternatedata streams are restored to a FAT or FAT32 file system.

Notes on full virtual machine restoreNote the following:

Back up and restore Hyper-VRestore notes

26

■ A backup of the full virtual machine can be restored only to a Windows server2008 with the Hyper-V role enabled.

■ Bydefault, theNetBackup client on theHyper-V server does not haveWindowsAdministrator privileges. You can restore a full virtual machine from theNetBackup server. You cannot restore a full virtualmachine fromaNetBackupclient that does not have Administrator privileges.

■ Whenyou restore the virtualmachine to its original locationwith theOverwritevirtualmachine option, note: the same virtualmachine on theHyper-V serveris automatically turned off and deleted before the restore. The .vhd files of thevirtual machine on the Hyper-V server are overwritten by the .vhd files fromthe backup image. If any new .vhd files were created after the backup, thosefiles are not removed.

■ When you restore the virtual machine to a different location on the originalHyper-V server or to a different server, note: the same virtual machine (if itexists) on the Hyper-V server is automatically turned off and deleted beforethe restore if you choose the Overwrite virtual machine option. The .vhd filesof the deleted virtualmachine, however, are not deleted. Youmust delete those.vhd files.

■ When you restore the virtual machine to a Hyper-V server that has a virtualmachine of the same GUID, you must select the Overwrite virtual machineoption. Otherwise, the restore fails.

■ If you restore a virtualmachinewithout theOverwrite virtualmachine option,note: you must remove the current virtual machine and its .vhd files from thedestination server before you start the restore. If you remove the virtualmachine but leave one or more of its .vhd files on the destination server, the.vhd files from the backup are not restored.

■ (This item is a limitation in VSS and the Hyper-V writer, not in NetBackup.) Ifthe virtual machine contains Hyper-V snapshot files (.avhd files), NetBackupcannot restore the virtual machine to a different location or to a differentHyper-V server. This restriction does not apply when you restore the virtualmachine to its original location on the original Hyper-V server or when yourestore to a staging location.Note that NetBackup does not create Hyper-V snapshot files (.avhd).

■ (This item is a limitation in VSS and the Hyper-V writer, not in NetBackup.)Immediately after a full virtualmachine is restored, the virtualmachine volumemaybe larger than itwaswhen thevirtualmachinewasbackedup.The increaseis normal: after the restore, snapshot-related cache files remain on the volume.After about 20 minutes, the cache files are automatically removed and thevolume returns to its original size

27Back up and restore Hyper-VRestore notes

Note: a new backup of the restored virtual machine could fail if the virtualmachinevolumecontains insufficient space to create a snapshot for thebackup.According to Microsoft, this situation should not occur as long as the virtualmachine volume has at least 10 to 15% free space.

■ If you attempt to do a full restore of two virtual machines at the same time,and the two machines share a virtual hard disk (.vhd file) that both restorejobs have selected to restore, a race condition may result. The two jobs maysimultaneously attempt to access the same .vhd file, but only one job gainsaccess to the file. The other job is denied access, and that job may fail witherror code 185.See “NetBackup status codes related to Hyper-V” on page 47.

■ If you restore a virtualmachine to a differentHyper-V server, note: the originalHyper-V server and the target server must have the same number of networkadapters (NICs). You must configure the network adapter(s) for the restoredvirtual machine on the target server.See “ Restored virtual machine fails to start” on page 54.

About restoring individual filesIf the Hyper-V backup was made with the "2-Mapped FullVM" backup option,note: you can restore individual files and folders that existed on that virtualmachine at the time of the backup.

If the Hyper-V Virtual Machine Backup option for the backup was 1-FullVM, youcan restore the entire virtual machine only. A different procedure is required torestore the entire virtual machine.

See “Restoring the full virtual machine” on page 33.

More information is available on the Hyper-V backup options.

See “Configuring a Hyper-V policy” on page 19.

You can set up a configuration to restore individual files in any of the followingways:

■ Install a NetBackup client on another computer. Create a share on the virtualmachine to allow that computer to access the virtual machine. (The virtualmachine does not require a NetBackup client.) Specify the UNC path as thedestination for the restore. More information is available on this option:See “Restoring individual files to a shared location on the virtual machine”on page 31.See “Setting up NetBackup Client Service for restore to a shared location onthe virtual machine” on page 32.

Back up and restore Hyper-VAbout restoring individual files

28

■ Install a NetBackup client on the virtual machine where you want to restorethe files. Restore the files to the virtual machine in the same manner asrestoring to any NetBackup client.See “Restoring individual files to a host that has a NetBackup client ”on page 29.

■ Install a NetBackup client on another computer. Restore the files to thatcomputer and then copy the files to the virtual machine.To restore encrypted files, you must install a NetBackup client on the virtualmachine and restore the files directly to the virtual machine.See “Restoring individual files to a host that has a NetBackup client ”on page 29.

You can use theNetBackupBackup, Archive, andRestore interface to restore filesand folders from NetBackup for Hyper-V backups.

Important notes on Hyper-V restore are also available.

See “Restore notes” on page 26.

Restoring individual files to a host that has aNetBackup client

Use the following procedure.

29Back up and restore Hyper-VRestoring individual files to a host that has a NetBackup client

To restore individual files to a host that has NetBackup client

1 Start the NetBackup Backup, Archive, and Restore interface on a NetBackupclient.

2 Click Files > Specify NetBackup Machines and Policy Type.

Select the following.

The NetBackup master server that performed theHyper-V backup.

Server to use for backupsand restores

The Hyper-V virtual machine that was backed up.Source client for restores(or virtual client forbackups)

A physical host or a virtual machine. The host or virtualmachine must contain a NetBackup client.

You must use a different procedure to restore the filesto a virtual machine that does not have a NetBackupclient.

See “Restoring individual files to a shared location onthe virtual machine” on page 31.

Destination client forrestores

FlashBackup-Windows.Policy type for restores

3 Under Actions > Select Restore Type, select Normal Backups.

4 In the All folders pane, select the files to restore.

5 Click Actions > Restore.

6 Make your selections on the Restore Marked Files dialog.

Note the following:

■ Restore everything to its original locationSelect this option to restore the files to their original paths or folders onthe destination client. If the original volume at the time of backup (suchas E:\) does not exist on the destination client for this restore, the restorefails.

■ Restore everything to a different locationSelect this option to restore the files to a different path or folder on thedestination client. Specify the folder in the Destination: field.If the original volume at the time of backup (such as E:\) does not exist onthe destination client for this restore, the restore fails.Use a different procedure to restore the files to a virtual machine thatdoes not have a NetBackup client:

Back up and restore Hyper-VRestoring individual files to a host that has a NetBackup client

30

See “Restoring individual files to a shared location on the virtualmachine”on page 31.

■ Restore individual folders and files to different locationsSelect this option to restore files to particular locations. Each item youselected to restore appears in the Source column. Double-click on an itemto enter or browse for a restore destination.

7 Click Start Restore.

Restoring individual files to a shared location on thevirtual machine

You can restore virtual machine files to a Hyper-V virtual machine that does nothave a NetBackup client installed on it.

To restore individual files to a virtual machine that is not a NetBackup client

1 Install a NetBackup client on a physical host.

The host must be in the same domain as the virtual machine that you wantto restore the files to. This host can be aHyper-V server or another computer.

2 Create a share to allow the host that contains the NetBackup client to accessthe virtual machine. The share must allow write access.

For example: \\virtual_machine1\share_folder

In this example, virtual_machine1 is the ultimate destination for the restoredfiles. The host with the NetBackup client acts as a conduit for the restore.

3 Start theNetBackupBackup,Archive, andRestore interface on theNetBackupclient.

31Back up and restore Hyper-VRestoring individual files to a shared location on the virtual machine

4 Click Files > Specify NetBackup Machines and Policy Type.


The NetBackup master server that performed theHyper-V backup.

Server to use for backupsand restores

The Hyper-V virtual machine that was backed up.Source client for restores(or virtual client forbackups)

Select the host that has theNetBackup client. The virtualmachine to which youwant to restoremust have a sharefor this host.

Do not specify the virtual machine in this field.


FlashBackup-Windows.Policy type for restores

5 Under Actions > Select Restore Type, select Normal Backups.

6 In the All folders pane, select the files to restore.

7 Click Actions > Restore.

8 On the Restore Marked Files dialog, click Restore everything to a differentlocation.

In theDestination: field, specify theUNCpathname that refers to the shareddrive or folder on the destination virtual machine.

For example, to restore files to E:\folder1 on virtual_machine1, enter thefollowing:

\\virtual_machine1\share_folder\

NetBackup restores the files to the shared location on the virtual machine.

9 You may have to change the logon for the NetBackup Client Service.

See “Setting up NetBackup Client Service for restore to a shared location onthe virtual machine” on page 32.

Setting up NetBackup Client Service for restore to a shared locationon the virtual machine

To restore individual files to a Windows virtual machine that has a shared drive,the “NetBackup Client Service” must be logged on as the domain Administratoraccount. Itmust not be logged on as the Local Systemaccount. TheAdministrator

Back up and restore Hyper-VRestoring individual files to a shared location on the virtual machine

32

account allows NetBackup to write to the directories on the virtual machine towhich the data is restored.

If you try to restore files while the NetBackup Client Service is logged on as theLocal System account, the restore fails.

To log on the NetBackup Client Service as Administrator

1 In Windows Services on the host that has a share to the virtual machine,double-click the NetBackup Client Service.

2 Check the Log On tab: if the service is not logged on as Administrator, stopthe service.

3 Change the logon to the Administrator account, in the domain in which boththe virtual machine and the host that has a share reside.

4 Restart the service.

5 Retry the restore.

Restoring the full virtual machineYou can restore the entire virtual machine to the original Hyper-V server or to adifferent Hyper-V server.

For important notes on restoring the full virtual machine, see the following:

See “Notes on full virtual machine restore” on page 26.

33Back up and restore Hyper-VRestoring the full virtual machine

To restore the entire Hyper-V virtual machine

1 Start the NetBackup Backup, Archive, and Restore interface.

2 Specify the source client, destination client, and type of policy.

Windows:

Click Files > Specify NetBackup Machines and Policy Type.

UNIX:

On the RestoreFiles tab, click the hand icon that is in the upper right corner.


The NetBackup master server that performed the Hyper-Vbackup.

Server to use forbackups and restores

The Hyper-V virtual machine that was backed up.Source client forrestores (or virtualclient for backups)

This field is ignored when you restore an entire virtualmachine.

A later step in this procedure explains how to restore to adifferent Hyper-V server.


FlashBackup-Windows.Policy type forrestores

3 Select the type of restore:

Windows:

Click the downarrownext to theSelectforRestore option and selectRestorefrom Virtual Machine Backup. A restore window displays the backupsavailable for restore.

UNIX:

On the Restore Files tab, select Restore type > Virtual Machine Backups.

4 Select the backup of the virtual machine that you want to restore.

Windows:

In the NetBackup History pane, click on the Hyper-V backup, then click onthe item that is displayed underAllFolders. Youmust select the entire virtualmachine.

UNIX:

Back up and restore Hyper-VRestoring the full virtual machine

34

■ On theRestoreFiles tab, specify the Start date andEnddatewithinwhichto search for the backup.

■ Specify root (/) in the Browse directory field and press Enter.

■ Click on the root folder that is displayed under Directory Structure.

5 Open the Restore Marked Files dialog.

Windows: Click Actions > Restore.

UNIX: Click Restore.

6 Select from the following options on the Restore Marked Files dialog box.

Shows the Hyper-V hostname and GUID (Globally UniqueIdentifier) of the virtual machine that was backed up. Usethis value to verify that this backup represents the virtualmachine that you want to restore. The GUID is a uniquestring for a virtual machine in addition to the hostname.

Hyper-V virtualmachine GUID

Restore Options

Restores the virtualmachine to its original location on theoriginal Hyper-V server.

Restore to Hyper-Vserver

Restores the virtual machine to a different location on theoriginal Hyper-V server, or restores it to a differentHyper-V server.

Restore to differentlocations on same /different Hyper-Vserver

Restores the virtual machine files to the staging locationon the server that you specify under Hyper-V server andRestoreeverythingtodifferentdirectory. Use this optionif:

■ You do not want to restore an entire virtual machine

■ YoudonotwantNetBackup to start the virtualmachineafter the restore

For instance, you can use this option to add restored filesas a .vhd volume to a virtual machine other than the onefrom which they were backed up.

Restore to staginglocation


If you selected Restore to Hyper-V server or Restore todifferent locations on same / different Hyper-V server,note the following:

■ If a virtual machine with the same GUID exits on thedestination server, that virtual machine is removedalong with its configuration and snapshot files. Anyexisting .vhd files for the virtual machine on thedestination server are overwritten. The virtualmachinethat you selected to restore is restored from the backup.

■ If theOverwritevirtualmachine option is not selectedand a virtual machine with the same GUID exists onthe destination server: the restore failswithNetBackupstatus code 5.

■ If theOverwritevirtualmachine option is not selectedand .vhd file(s) for the virtualmachine still exist on thedestination: the .vhd file(s) from the backup are notrestored.

See “Problemswhen restoring the full virtualmachine”on page 55.

If you selected Restore to staging location, note thefollowing:

■ If the .vhd file youwant to restore already exists on thedestination server in the location specified for therestore, that file on the destination server isoverwritten.

■ If the Overwrite existing files option is not selectedand any file you want to restore already exists in thelocation specified for the restore, the file is notoverwritten. Anyother files that are selected for restoreare restored. The restore is reported as a partial success.

Overwrite virtualmachine

(If you selected Restoreto staging location, thisoption is Overwriteexisting files)

Restore Destinations

If you selected Restore to Hyper-V server (to restore tothe original location), note: the restore destination is thenameof theHyper-Vserver fromwhich thevirtualmachinewas backed up. In this case, the destination cannot bechanged.

For the other restore options (restore to adifferent location,or restore to staging location), specify the destinationHyper-V server for the restore.

Hyper-V server

Back up and restore Hyper-VRestoring the full virtual machine

36

Lists the Hyper-V virtual machine files as they existedwhen the virtual machine was backed up. By default, alllisted files are selected for restore.

If you do not want the restore to replace certain files onthe current virtual machine on the destination server,uncheck those files. Leave a check mark next to the filesthat you want to restore. The files that are not checked inare not restored. Note that virtual machine configurationfiles (.xml, .vsv, and .bin files) and .avhd files are notde-selectable in restores other than staging restores.

Caution:Replacing common fileswith earlier versions canbe problematic for the virtual machines that rely on thecommon files. If you do notwant to overwrite the commonfiles on theHyper-V server, uncheck the common files thatyou do not want to restore.

See “About restoring common files” on page 38.

Note the following about the listed files:

■ If you do not select any .vhd files, NetBackup tries tofind them in their original location. If they are missingat the original location, the restore fails. If a parent .vhdfile was in E:\myVhds\ on the original machine and isnot selected during restore, NetBackup looks for theparent .vhd file in E:\myVhds\ on the target machine.If the file does not exist, the restore fails.

■ For Restore toHyper-Vserver or Restore todifferentlocationsonsame/differentHyper-Vserver, you canuncheck any .vhd files in this list. All other files arepre-checked and cannot be unchecked.

■ For Restore to staging location, you can uncheck anyfiles in the list.

■ Configuration files (such as xml, bin, vsv, and snapshotfiles) are always restored when you restore the fullvirtual machine.

List of backed up files(Source)

This field is disabled if you selected Restore to Hyper-Vserver.

For restore to a different location or to staging location,enter the path on the server or other machine that youspecifiedunderHyper-VserverorStagingmachinename.NetBackup creates the appropriate subdirectories.

Restore everything todifferent directory


Displays the directories on the destination server inwhichthe Hyper-V files are to be restored. You must specify adestination path in the Restore everything to differentdirectory field.

View Paths

Determines the restore job's priority for restore resources.A higher priority means that NetBackup assigns the firstavailable drive to the first restore job with the highestpriority. Enter a number (maximum 99999). The defaultfor all restore jobs is 0, the lowest priority possible. Anyrestore job with a priority greater than zero has priorityover the default setting.

Override default jobpriority

7 Click Start Restore.

When the restore is complete, the restored virtual machine is placed in theSaved or Off state. The state after restore depends on its state at the time ofthe backup and the type of Hyper-V backup that occurred.

See “About Hyper-V online and offline backups” on page 57.

About restoring common filesYou can save disk space by creating aHyper-V virtual hard disk that contains filesthat are required by a number of virtual machines. Instead of copies of the same.vhd file existing at multiple places, a single .vhd file (the parent) is shared bymultiple virtual machines. That virtual disk (the parent .vhd file) can be accessedby two ormore virtualmachines (each called a child). The parent .vhd file is calleda common file, because more than one virtual machine uses it.

The files unique to each virtual machine are maintained on differencing virtualdisks. These virtual disks are in a child relationship to the parent disk. The parentand child virtual disksmay be on the same physical drive or on different physicaldrives.

For example, the base version ofWindowsXP can be installed as a read-only imageon a virtual hard disk (parent). Two or more virtual machines can run the sameXP system files from the base image on the parent virtual hard disk. Applicationsthat are unique to a virtualmachine are not included in the common files. Insteadthey are on the .vhd files that are specific to the virtual machine.

Caution: Use care when restoring common files. If you restore an earlier versionof the common files (overwriting the current version), the virtual machines thatrely on those files may experience problems.

Back up and restore Hyper-VAbout restoring common files

38

When restoring common files, note the following:

■ Before you restore common files, make sure the virtual machines that use thecommon files are in the Off or Saved state. Otherwise, a virtual machine mayhave a lock on the common files and the restore fails with NetBackup statuscode 5.

■ Tokeep the common files that are currently on the server, uncheck the common.vhd files on the RestoreMarked Files dialog under List of backed up files. Thefiles on the destination Hyper-V server that are not selected in the RestoreMarked Files dialog are not replaced by the restore.

■ To overwrite the existing common files, check all the .vhd files from the Listof backed up files. However, if the common files are in use on the destinationserver, the restore fails. For the restore to succeed, the virtual machines thatuse the common files must be in the Off or Saved state.

■ To restore common files without overwriting any common files that exist onthe destination server: specify a different location on theRestoreMarked Filesdialog under Restore everything to different directory.

39Back up and restore Hyper-VAbout restoring common files

Back up and restore Hyper-VAbout restoring common files

40

Best practices and moreinformation


■ Best practices

■ More information on NetBackup and Hyper-V

Best practicesSymantec recommends the following:

■ For a more efficient backup, the NetBackup media server should be installedon the same host as theHyper-V server. In this configuration, the backup datacan be sent to storage without traveling over the network.

More information on NetBackup and Hyper-VSee the following:

■ For details on NetBackup support for Hyper-V, see the following Symantectech note:Support for NetBackup in a virtual environmenthttp://entsupport.symantec.com/docs/312604

■ A wide variety of information is available at Microsoft TechNet.For example, refer to the Hyper-V Getting Started Guide:http://technet.microsoft.com/en-us/library/cc732470.aspx

5Chapter

Best practices and more informationMore information on NetBackup and Hyper-V

42

Troubleshooting


■ NetBackup logs and how to create them

■ Other logs for troubleshooting

■ NetBackup policy validation failed

■ NetBackup status codes related to Hyper-V

■ Snapshot error encountered (status code 156)

■ Backup job hangs for multiple virtual machines

■ Windows NTFS shadow storage has insufficient space for snapshots

■ Storage unit characteristics mismatched to request (status code 154)

■ The Hyper-V integration component is missing or not properly installed

■ NTFS shadow storage is configured on a different volume

■ The backup job is partially successful (status code 1)

■ Restored virtual machine fails to start

■ Problems when restoring individual files

■ Problems when restoring the full virtual machine

■ Problem when starting a restored virtual machine: "Why did the computershut down unexpectedly?”

6Chapter

NetBackup logs and how to create themFor logmessages aboutNetBackup forHyper-Vbackupor restore, see the followingNetBackup log folders.

Table 6-1 NetBackup logs that pertain to Hyper-V backup and restore

Resides onContains messageson

Log folder

NetBackup master ormedia server

Backup and restoreinstall_path\NetBackup\logs\bpbrm

NetBackupmediaserverBackup and restoreinstall_path\NetBackup\logs\bptm

NetBackup client on theHyper-V server

Snapshot creation andbackup

install_path\NetBackup\logs\bpcd


Snapshot creation andbackup

install_path\NetBackup\logs\bpfis


Backupinstall_path\NetBackup\logs\bpbkar

NetBackup masterserver

Restoreinstall_path\NetBackup\logs\bprd


Restoreinstall_path\NetBackup\logs\tar


Policy configurationand on restore

install_path\NetBackup\logs\bpVMutil


Policy configurationinstall_path\NetBackup\logs\nbproxy

Note: These log folders must already exist in order for logging to occur. If thesefolders do not exist, create them.

To create the log folders, run the following command on the NetBackup serversand on the Hyper-V server:

Windows:

install_path\NetBackup\logs\mklogdir.bat

UNIX (on master or media servers):

/opt/openv/netbackup/logs/mklogdir

TroubleshootingNetBackup logs and how to create them

44

Formore detail on snapshot-related logs, logging levels, and the required folders,see the NetBackup 6.5 Snapshot Client Administrator’s Guide.

A broader discussion of NetBackup logging is available in the NetBackupTroubleshooting Guide.

Other logs for troubleshootingThe following logs may also contain valuable information.

Table 6-2 Other logs

Resides onContains messages onLog folder


See “EnablingVxMSandvhdlogging” on page 45.

File mapping during backupand VxMS APIs.

This folder also contains avhd log, which describes theformat of the virtualmachine's .vhd files.NetBackup support can usethe vhd log to reproduce acustomer's virtual machineenvironment fortroubleshooting purposes.

\Program Files\CommonFiles\VERITAS\VxMS\Logs


See “Enabling VxFI logging”on page 46.

Snapshot creation and VSSAPIs.

\Program Files\CommonFiles\SymantecShared\VxFI\4\logs\

Enabling VxMS and vhd loggingTo enable VxMS and vhd logging

1 On the Windows desktop of the Hyper-V server where the NetBackup clientis installed, click Start > Run and enter regedit.

2 To be on the safe side, make a backup of the current registry (File > Export).

3 Go to HKEY_LOCAL_MACHINE > SOFTWARE > VERITAS > VxMS.

45TroubleshootingOther logs for troubleshooting

4 Change the Logging DWORD value to 0x7580.

5 For vhd logging: in the same location (HKEY_LOCAL_MACHINE>SOFTWARE> VERITAS > VxMS), create a new DWORD called VHDLog.

To enable vhd logging, set the value of VHDLog to 0x01.

To disable vhd logging, set the value of VHDLog to 0x00.

Thenameof the vhd log isvhd_vm.txt. Only onevhd_vm.txt log file is created;new log entries are written to the existing log file.

Enabling VxFI loggingBy default, VxFI logging occurs at the error level. You can increase the loggingverbosity by changing the log configuration file for the appropriate provider.

Use the following procedure.

To enable VxFI logging

1 On the Windows desktop of the Hyper-V server where the NetBackup clientis installed, go to the following location:

\Program Files\Common Files\Symantec Shared\VxFI\4\ConfigFiles\

This folder contains a configuration file for each provider, such as vss.confand emcclariionfi.conf. These files are generated after a successful loadof VxFI providers, usually during NetBackup policy validation.

2 Edit the .conf file for the appropriate provider, as follows:

Change the TRACELEVEL entry to the following:

"TRACELEVEL"=dword:00000006

The default TRACELEVEL value is 00000001.

Note that VSS and WMI provider logs are relevant to Hyper-V.

NetBackup policy validation failedNetBackup policy validation may fail in the following cases:

■ No host name entry for the virtual machine exists in the DNS server, or in theWindows hosts file on the Hyper-V server(Windows\System32\drivers\etc\hosts).Create a virtual machine name entry in either the DNS server or in the hostsfile of the Hyper-V server.

■ A firewall is enabled and no port entry exists for the master server.

TroubleshootingNetBackup policy validation failed

46

Add a port entry for the NetBackup master server.See the NetBackup Administrator's Guide.

NetBackup status codes related to Hyper-VThis topic provides assistance for NetBackup status codes.

Table 6-3 NetBackup status codes related to Hyper-V

Explanation and recommended actionNetBackup status code

A problem may have occurred with a virtual disk that isconfigured for Logical Disk Manager (LDM) volumes.

See “The backup job is partially successful (status code 1)”on page 54.

1, the requested operationwas partially successful

The problem may be one of the following:

■ In a full virtual machine restore, the Overwrite virtualmachine optionwasnot selected: a virtualmachinewiththe same GUID exists on the destination server. If avirtual machine with the same GUID exists on thedestination server, you must select Overwrite virtualmachine.

■ In a restore of individual files by means of a sharedlocation on the destination virtualmachine, one ormoreof the files is larger than 2 GB. Restore such files to avirtual machine that has a NetBackup client. (This issuedoes not apply to restores of the full virtual machine.)

■ In a restore of common files, the virtual machines thatuse the common files were in the Running or Pausedstate. The virtual machines that use the common filesmust be in the Off or Saved state. Otherwise, a virtualmachine may have a lock on the common files.

5, the restore failed torecover the requested files

The Windows shadow storage for the volume may haveinsufficient space to hold all required snapshots. A largershadow storage area may be required.

See “WindowsNTFS shadow storage has insufficient spacefor snapshots” on page 51.

42, network read failed

Verify that the NetBackup master server can communicatewith the virtual machine.

48, clienthostnamecouldnotbe found.

47TroubleshootingNetBackup status codes related to Hyper-V

Table 6-3 NetBackup status codes related to Hyper-V (continued)

Explanation and recommended actionNetBackup status code

The NetBackup storage unit is on a media server that isrunning an earlier version of NetBackup (pre-6.5.4). InstallNetBackup 6.5.4 on themedia server and rerun the backup.

See “Storage unit characteristics mismatched to request(status code 154)” on page 51.

154, storage unitcharacteristics mismatchedto request

See “Snapshot error encountered (status code 156)”on page 48.

156, snapshot errorencountered

If you attempt to do a full restore of two virtual machinesat the same time, and the twomachines share a virtual harddisk (.vhd file) that contains a file that both restore jobshave selected to restore, a race condition may result. Thetwo jobs may simultaneously attempt to access the samefile, but only one job gains access to the file. The other jobis denied access, and that job may fail with status code 185.

After the first restore job successfully completes, retry thesecond job.

185, tar did not find all thefiles to be restored

Snapshot error encountered (status code 156)This topic describes Hyper-V issues that relate to status code 156.

TroubleshootingSnapshot error encountered (status code 156)

48

Table 6-4 Possible causes of status code 156

Description and recommended actionCauses of status code156

Indicates a mismatch between the virtual machine names thatare specified on the Clients tab of the NetBackup policy and theactual names on the Hyper-V server. Check the actual namesas listed in the Hyper-V Manager on the Hyper-V server.

Recommended action:

Note the following:

■ In the NetBackup policy, the virtual machines must bespecified as fully qualified names.

■ In theNetBackuppolicy, the virtualmachinenamemayhavebeen entered incorrectly.

If you browsed for the virtual machines on the Clients taband selected names from the list, the list may be out of date.(The list is derived from a cache file.) Refresh the list byclicking on the icon next to the Last Update field.

The virtual machinename is incorrectlyspecified in theNetBackup policy.

Volumes on the virtual machine do not have enough free spacefor the snapshot. Microsoft recommends that at least 10% ofthe virtual machine volume is available for the snapshot.

Recommended action: create more space on the volume.

Volumes on the virtualmachine are almost full.

The Hyper-V integration component is not properly installedin the virtual machine .

Recommended action:

See “The Hyper-V integration component is missing or notproperly installed” on page 52.

TheHyper-V integrationcomponent is missing.

For a Windows NTFS file system, Windows shadow storage fora volume (such as C:) must be configured on the same volume.

Recommended action:

See “NTFS shadowstorage is configured onadifferent volume”on page 52.

Windows NTFS shadowstorage is configured ona different volume.

49TroubleshootingSnapshot error encountered (status code 156)

Table 6-4 Possible causes of status code 156 (continued)

Description and recommended actionCauses of status code156

The following application error event may be written to thevirtual machine during backup:

Event Type: ErrorEvent Source: VSSEvent Category: NoneEvent ID: 12302Date: 1/8/2009Time: 1:36:21 AMUser: N/AComputer: ARTICTALEVM8

Description:

Volume Shadow Copy Service error: An internalinconsistency was detected in trying to contactshadow copy service writers. Please check to seethat the Event Service and Volume Shadow Copy Serviceare operating properly.For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

Recommended action:

Run the vssadmin list writer command.

If no writer is listed in the output and a similar error is logged,refer to the following to resolve this issue:

http://support.microsoft.com/kb/940184

The VSS framework inthe virtual machine isnot working properly

Backup job hangs for multiple virtual machinesIf theNetBackupbackuppolicy specifiesmultiple virtualmachines, and the storageunit "Maximum concurrent jobs" option is set to 2 ormore, the backupmay hang.If youhave Symantec Endpoint Protection installed on yourHyper-V server,makesure it is at version 11.0MaintenanceRelease 4 (build 11.0.4000) or later. Backupsof multiple virtual machines with multiple concurrent jobs may experience thisbackup problem with earlier versions of Symantec Endpoint Protection.

TroubleshootingBackup job hangs for multiple virtual machines

50

WindowsNTFS shadowstoragehas insufficient spacefor snapshots

For backups that are made with the "1-system" Provider Type (for a block-levelcopy-on-write snapshot), Windows shadow storage for a volume on a Hyper-Vhost must have enough space to hold all required snapshots. If too little space isavailable, the backup fails with status code 42, "network read failed." In this case,a larger shadow storage area is required. Refer to Microsoft documentation forrecommendations on shadow storage size. For example, refer to the following:

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

If additional space is not available for shadow storage, reschedule backups so theydo not occur at the same time.

To view or resize shadow storage

1 To list the current shadow storage settings, run the following on the virtualmachine:

vssadmin list shadowstorage

2 To resize shadow storage, run the following:

vssadmin resize shadowstorage

Refer to your Microsoft Windows documentation for more details.

Storage unit characteristics mismatched to request(status code 154)

If the NetBackup storage unit is on a media server that is running a pre-6.5.4version of NetBackup, the backup fails with status 154. Messages similar to thefollowing appear in the Detailed Status log:

11/21/2008 5:36:44 PM - requesting resource STU_MED

11/21/2008 5:36:44 PM - requesting resource lin04-

x86.NBU_CLIENT.MAXJOBS.hyper_win_5.veritas.com

11/21/2008 5:36:44 PM - requesting resource lin04-

x86.NBU_POLICY.MAXJOBS.MAPPED_VM

11/21/2008 5:36:46 PM - Error nbjm(pid=4224) NBU status: 154, EMM status:

Storage unit is not compatible

storage unit characteristics mismatched to request(154)

Install NetBackup 6.5.4 on the media server and rerun the backup.

51TroubleshootingWindows NTFS shadow storage has insufficient space for snapshots

Note: For NetBackup for Hyper-V, master server, media server, and client mustall be at 6.5.4.

TheHyper-V integration component ismissing or notproperly installed

Make sure the proper version of the Hyper-V virtual machine integrationcomponent is installed on the virtualmachine. The integration component shouldbe at version 6.0.6001.18016 or later. It should also be the same version asdrive_letter\Windows\System32\vmms.exe on the Hyper-V server. Otherwise,the backup fails with status code 156.

To determine the integrated component version, right-click on the following fileon the virtual machine and click Properties > Details:

drive_letter\Windows\System32\vmicsvc.exe

This file is the integration service running in the virtual machine.

NTFS shadow storage is configured on a differentvolume

For a Windows NTFS file system, Windows shadow storage for a volume must beon the same volume. If the virtualmachine hasmultiple volumes, and the shadowstorage for the C: volume is on the D: volume, the backup fails with NetBackupstatus 156. An error message similar to the following appears in the Windowsevent logs for Hyper-V VMMS:

An unhandled exception was encountered while processing a VSS writer

event callback. The VSS writer infrastructure is in an unstable

state. The writer hosting process must be restarted in order to

resume VSS functionality.

Windows event logs for VMMS can be located on the Server Manager consoleunder the following:

Diagnostics > Event Viewer > Applications and Services Logs > Microsoft >Windows > Hyper-V-VMMS > Admin

Do the following and re-run the backup.

TroubleshootingThe Hyper-V integration component is missing or not properly installed

52

To configure volume shadow storage on the same volume

1 On the virtualmachine, enter the followingWindows command to determinewhether shadow storage exists on a different volume:

C:\Program Files\Veritas\NetBackup\bin vssadmin list shadowstorage

Example output:

Shadow Copy Storage association

For volume: (C:)\\?\Volume{8235bcc3-bf95-11dc-b45c-806e6f6e

2463}\

Shadow Copy Storage volume: (E:)\\?\Volume{2e0436fc-5b7b-

12dd-a2d3-dbf4f361c0

Used Shadow Copy Storage space: 0 B

Allocated Shadow Copy Storage space: 0 B

Maximum Shadow Copy Storage space: UNBOUNDED

In this example, the shadow storage for the C: volume is configured on theE: volume.

2 If shadowstorage for avolume is configuredonadifferent volume, reconfigurethe shadow storage to the same volume.

To reconfigure the shadow storage for C: to be on C:, enter the following:

vssadmin add shadowstorage /For=C: /On=C:

3 To verify that the VSS functionality is re-enabled, enter the following on theHyper-V server.

vssadmin list writers

The output should list "Microsoft Hyper-V VSS Writer" as the writer name.For example:

Writer name: 'Microsoft Hyper-V VSS Writer'

Writer Id: {66371cd4-6ded-4f4b-6f17-fd23f8ddc2dc}

Writer Instance Id: {e3282564-3ed4-4579-af5e-d452bf543004}

State: [1] Stable

Last error: No error

4 If the vssadmin list writers commanddoes not list an entry for “MicrosoftHyper-VVSSWriter," restart the vmms service. To do so, enter the followingcommands on the Hyper-V server:

net stop vmms

net start vmms

53TroubleshootingNTFS shadow storage is configured on a different volume

The backup job is partially successful (status code 1)If a virtual disk has been configured for Logical Disk Manager (LDM) volumes,and theNetBackuppolicy specifies the "2-Mapped FullVM" option, note: in certaincases a backup of the virtual machine may not complete. The NetBackup job mayissue status 1, "the requested operation was partially successful." This error canoccur if the controller type of the .vhd disk was SCSI when the disk was initiallyformatted but the controller type was later changed to IDE (or vice versa).

In this case, the NetBackup progress log may contain the following message:

ERR - Unable to retrieve volumes from virtual machine, error = 1

You must restore the controller type of the .vhd disk to the controller typeoriginally assigned before the LDM volume was created. Then retry the backup.

Restored virtual machine fails to startThe following issues may prevent a restored virtual machine from starting:

■ If you restore a virtualmachine to a differentHyper-V server, and the originalHyper-V server and the target server do not have the samenumber of networkadapters (NICs), note: you must configure the network adapter(s) for therestored virtual machine on the target server. Otherwise, the attempt to startthe restored virtual machine fails and a message similar to the followingappears:

Microsoft Synthetic Ethernet Port (Instance ID {C549AG45-5925-49C0-

ADD2-218E70A4A1EA}): Failed to power on with Error 'The system

cannot find the path specified.' (0x80070003). (Virtual machine

5412BD43-DC85-31CB-A488-1B29CE2C57C8)

■ When a virtualmachine is restored to a different Hyper-V server, the locationof a virtual CD or DVD drive may prevent the machine from restarting.

The problem occurs in the following case:

■ Theoriginal virtualmachinehad aCD ISO image that is attached to a virtualCD or DVD drive.

■ On theHyper-V serverwhere the virtualmachinewas restored, the CD ISOimage is not present at the same path as it was on the original Hyper-Vhost during backup.For example: the virtual machine originally had E:\cd1.iso attached to itsvirtual DVDdrive, but E:\cd1.iso does not exist on the target Hyper-V host,

TroubleshootingThe backup job is partially successful (status code 1)

54

or it exists at a different location, such as F:\cd1.iso. In either case, therestored virtual machine does not turn on.

To solve the attached CD/DVD problem

1 In the Hyper-V Manager, click on the restored virtual machine.

2 Click Settings.

3 Under the appropriate IDE Controller, click DVD drive.

4 In the Media pane, specify the correct location of the CD, or select None.

Problems when restoring individual filesWhen you restore individual files (not the entire virtual machine), the restoremay fail in the following cases:

■ Files are selected from multiple drives (volumes) on the virtual machine.For example: the original virtual machine had two drives (C:\ and D:\), andfiles from each drive are selected in the same restore operation. Messagessimilar 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.

■ You have attempted to restore the files into a mapped drive on the virtualmachine. The restore fails with NetBackup status code 185.Do the restore by means of a shared location on the virtual machine (with aUNC path) rather than by means of a mapped drive.See “Restoring individual files to a shared location on the virtual machine”on page 31.

Problems when restoring the full virtual machineRestores of a full virtual machine may fail in the following cases:

55TroubleshootingProblems when restoring individual files

■ You try to restore the full virtual machine to a location other than its originallocation. The virtual machine contains a Hyper-V snapshot (.avhd files) thatexisted during the backup. The restore fails with status code 5, and the jobprogress log contains a message similar to following:

Redirected restore not supported for Hyper-V snapshots (.avhd files).

Restores of virtual machines that contain Hyper-V snapshots (.avhd files) canbe directed only to the original location. As an alternative, you can restore thefiles to a staging location.

■ If the Overwrite virtual machine option was not selected and .vhd file(s) forthe virtual machine still exist on the destination: the .vhd file(s) from thebackup are not restored. You must select Overwrite virtual machine for therestore, or remove the current virtual machine and its .vhd files from thedestination server before you start the restore. If you remove the virtualmachine but leave one or more of its .vhd files on the destination server, the.vhd files from the backup are not restored.

Problem when starting a restored virtual machine:"Why did the computer shut down unexpectedly?”

An unexpected shutdown message is displayed when a restored Windows virtualmachine is started.

When you start a restored virtual machine, the system may display the message“Why did the computer shut down unexpectedly?” It may prompt you to enter aproblem ID. This message and prompt occur if the virtual machine was in theRunning state when the backup was initiated.

When a Windows system starts up, a bit is set indicating that the system did notshut down gracefully. If the system is shut down gracefully, the bit is cleared.However, when an online backup of a running virtual machine is performed, theunexpected shutdown bit remains set in the backed up image. When the restoredvirtual machine is started, the bit is detected and the unexpected shutdownmessage is displayed.

TroubleshootingProblem when starting a restored virtual machine: "Why did the computer shut down unexpectedly?”

56

Hyper-V online and offlinebackups

This appendix includes the following topics:

■ About Hyper-V online and offline backups

About Hyper-V online and offline backupsA Hyper-V virtual machine can be in any of the following states: Running, Saved,Paused, or Off.

In addition,Microsoft provides the following two types ofHyper-Vvirtualmachinebackups:

A virtual machine that is in the Running state is briefly quiesced for thebackup. User access during the backup continues without interruption.

Online

A virtual machine that is in the Running or Paused state is renderedtemporarily inactive. It is returned to its original state before the backupcompletes. User access during the backup is interrupted.

Offline

Note: Type of backup (online or offline) is a Microsoft designation and is notconfigured in NetBackup.

Table A-1 shows the possible combinations of virtual machine state and the typeof backup.

AAppendix

Table A-1 State of virtual machine before and after restore

State after restoreType of backupState at the time of backup

OffOnlineRunning

SavedOfflineRunning

SavedOfflineSaved

SavedOfflinePaused

OffOfflineOff

When online vs offline backup is performedAHyper-V online backup canbe performedwithnodowntimeon a running virtualmachine when all of the following conditions are met:

■ TheHyper-V integration services are installed and theVSS integration serviceis enabled.

■ All disks that are used by the virtual machine are configured within the guestoperating system as NTFS-formatted basic disks. If the virtual machine usesdynamic disks or the FAT or FAT32 file system, an online backup cannot beperformed.Note that "dynamic" disks are not a type of virtual hard disk (vhd format).Dynamic disks and basic disks are disk types defined by Microsoft for certainWindows operating systems.

■ Each virtual machine volumemust specify itself as the storage location for itsshadowcopies. For example, the shadowcopy storage for C:must be configuredon C:, the shadow copy storage for D: must be on D:, and so forth.

If these conditions arenotmet, the backup is performedoffline. Anoffline backupresults in some downtime on the virtual machine. If the virtual machine is in theRunning or Paused state, it is put in a Saved state as part of the offline backup.After the backup is completed, the virtualmachine is returned to its original state.

Additional notes on offline backupsWhen an offline backup is performed on a virtualmachine that is currently in theRunning state, note: the virtualmachine briefly enters the Saved state during thebackup and then returns to its original state.

For a virtual machine that is in the Running state at the start of the backup, thetype of backup is offline in the following circumstances:

Hyper-V online and offline backupsAbout Hyper-V online and offline backups

58

■ The VSS integration component of Hyper-V is not running in the virtualmachine.The VSS integration component is part of the Hyper-V integration servicesthat are installed in the virtual machine.

■ The virtual machine is running an operating system that does not supportWindows Volume Shadow Copy Service (VSS).

■ The storage configuration of the virtual machine is not compliant.

Any of the following can result in a non-compliant storage configuration:

■ The shadow storage for any volume in the virtual machine is explicitly setto be in a different volume.See “NTFS shadow storage is configured on a different volume” onpage 52.

■ The virtual machine has one or more disks that are configured as dynamicdisks in the operating system. Note that dynamic disks are not a type ofvirtual hard disk. Dynamic disks and basic disks are disk types defined byMicrosoft for certain Windows operating systems.

■ The virtualmachinehas volumes that donot supportVolumeShadowCopyService (VSS).If the virtual machine has a non-NTFS formatted volume (such as FAT orFAT32), the virtualmachine is placed in the Saved state during the backup.

59Hyper-V online and offline backupsAbout Hyper-V online and offline backups

Hyper-V online and offline backupsAbout Hyper-V online and offline backups

60

Documents

Netbackup for Hyper-V Guide