Netbackup-VMware

Symantec NetBackup ™ forVMware Administrator'sGuide

UNIX, Windows, and Linux

Release 7.0

20654026

Symantec NetBackup™ for VMware GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version 7.0.

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 RSA Data Security, Inc. MD5 Message-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 License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto 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.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,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 TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR 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 and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 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 and Documentation by the U.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. The Technical 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, the Technical Support group works with Product Engineeringand 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’s Maintenance Programs, you can visit our Website at the following URL:

www.symantec.com/techsupp/

Contacting Technical SupportCustomers with a current maintenance agreement may 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 on which the problem occurred, 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 your Symantec product requires registration or a license key, 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 to maximize 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.

Symantec Early Warning Solutions

These services remove the burden of managing and monitoring security devicesand events, ensuring rapid response to real threats.

Managed Security Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About NetBackup for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11The features of NetBackup for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

New in this release ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Full virtual machine backup vs file-level backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13NetBackup for VMware: vStorage vs VCB .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Minimum levels for vStorage support ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13When is VCB required? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Why is VCB not being used? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14NetBackup for VMware environment .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

NetBackup for VMware components ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Environment diagrams .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15NetBackup for VMware license requirement ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

NetBackup for VMware configuration tasks: overview .... . . . . . . . . . . . . . . . . . . . . . 17VMware tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17NetBackup tasks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

About VMware storage optimization .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Terminology .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 2 Notes and prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Notes and restrictions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Further notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Deleting a vSphere Client snapshot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Setting the Changed Block Tracking option in vSphere Client ... . . . . . . . . . . . . 25Notes on the hotadd transfer type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Creating a helper virtual machine for hotadd transfer ... . . . . . . . . . . . . . . . . . . . . . . 28

Chapter 3 Configure NetBackup for VMware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Adding the VMware backup host to NetBackup configuration .... . . . . . . . . . . . 30Adding NetBackup credentials for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Changing the host name of a VMware server in NetBackup .... . . . . . . . . . . . . . . 32

Contents

Incremental backups must be based on timestamps .... . . . . . . . . . . . . . . . . . . . . . . . 33Configuring a VMware policy from the Policies node .... . . . . . . . . . . . . . . . . . . . . . . 33Configuration parameters for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Client name selection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Virtual machine backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Transfer type .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Virtual machine quiesce ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Exclude unused and deleted blocks ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Existing snapshot handling .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Monolithic export (VCB only) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Snapshot mount point (VCB only) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Browse for VMware Virtual Machines screen .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Configuring a VMware policy from the Snapshot Policy Configuration

wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45About incremental backups of virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Volume Manager volumes in the virtual machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Backup options compared .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Reducing the size of backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47About block-level backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Recovery options: vStorage vs VCB .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Recovery options with VMware vStorage .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Recovery options with VMware VCB .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 4 Back up VMware virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Backing up virtual machines ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Further information on NetBackup policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Chapter 5 Restore VMware virtual machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

VMware restore procedures: overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Restore of selected files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Restore of the virtual machine from vStorage backups .... . . . . . . . . . . . . . . 56Restore of the virtual machine from VCB backups .... . . . . . . . . . . . . . . . . . . . . 56

Restore notes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56If the recovery host is not at the same NetBackup release level

as the backup host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Restoring individual folders and files ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Setting up NetBackup Client Service for restore to a shared virtual

machine drive ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Restoring the full VMware virtual machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Restore Marked Files dialog box (VMware) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Virtual Machine Recovery dialog boxes (restore to original

location) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Contents8

Virtual Machine Recovery dialogs boxes (restore to alternatelocation) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 6 Best practices and more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Best practices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75For VCB backups .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76VMware with deduplication .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

More information on VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Further assistance with NetBackup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Support information on NetBackup for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 7 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

NetBackup logging for VMware .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Other logs for troubleshooting .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

VMware environment—important! .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Changing the browsing timeout for virtual machine discovery .... . . . . . . . . . 82Changing timeout and logging values for vSphere .... . . . . . . . . . . . . . . . . . . . . . . . . . . 82Notes and tips ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Backup and restore problems .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Credentials for VMware server are not valid ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84NetBackup cannot obtain the volume ID of a drive ... . . . . . . . . . . . . . . . . . . . . 84Other backup failures ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Restore fails when you restore individual files to a virtual

machine that has NetBackup client software .... . . . . . . . . . . . . . . . . . . . . . 87Backup or restore job hangs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Mount point missing on a restored Windows virtual

machine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Problems with transfer types ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89NetBackup catalog information for virtual machine backups

made on 6.5.4 or lower may prevent browsing the importedimages for restore ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Restore fails with NetBackup status code 5 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Restore of selected files fails with NetBackup status code

227 .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Invalid client error when you restore selected files using

NetBackup BAR interface installed on the virtualmachine .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

VMware virtual machine does not reboot after restore ... . . . . . . . . . . . . . . . 91

9Contents

Appendix A Backup of VMware raw devices (RDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

About VMware raw device mapping (RDM) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93NetBackup support details for RDMs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Configurations for backing up RDMs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94About alternate client backup of RDMs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Requirements for alternate client backup of RDMs .... . . . . . . . . . . . . . . . . . . . . . . . . 95Configuring alternate client backup of RDMs .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Appendix B File-level backup of Windows virtual machines . . . . . . . . . . . . 99

About file-level backup of Windows virtual machines ... . . . . . . . . . . . . . . . . . . . . . . 99Configuration tasks for file-level backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100File-level backup options .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101What can be restored from a file-level backup? .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Configuring a policy for Windows file-level backup .... . . . . . . . . . . . . . . . . . . . . . . . 102

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Contents10

Introduction

This chapter includes the following topics:

■ About NetBackup for VMware

■ New in this release

■ Full virtual machine backup vs file-level backup

■ NetBackup for VMware: vStorage vs VCB

■ Minimum levels for vStorage support

■ When is VCB required?

■ Why is VCB not being used?

■ NetBackup for VMware environment

■ NetBackup for VMware configuration tasks: overview

■ About VMware storage optimization

■ Terminology

About NetBackup for VMwareNetBackup for VMware provides backup and restore of the VMware virtualmachines that run on VMware ESX servers. NetBackup for VMware takes advantageof VMware vStorage APIs for Data Protection. The backup process is off-loadedfrom the ESX server to a VMware backup host.

The features of NetBackup for VMwareNetBackup for VMware does the following:

1Chapter

■ Performs off-host backup of virtual machines (NetBackup client software isnot required on the virtual machine). Off-host backup reduces the backupprocessing load on the VMware ESX server.

■ Automatically creates quiesced snapshots using VSS (Windows only).

■ Uses snapshot technology to keep virtual machines 100% available to users.

■ Supports VMware vSphere as well as older VMware environments.

■ Performs full and incremental backup, including block-level incrementals.

■ Backs up and restores selected files (Windows only) or the full virtual machine.

■ Can restore selected files from a backup of a full Windows virtual machine.

■ Backs up the virtual machines even when they are turned off.

New in this releaseThe following items are new in this 7.0 release:

■ NetBackup supports VMware vSphere with vStorage APIs for Data Protection.VMware Consolidated Backup (VCB) is still supported but not required in mostcases. vStorage eliminates the need to make a VCB copy of a virtual machinesnapshot on the VMware backup host. Instead, NetBackup backs up thesnapshot directly from the ESX server.See “NetBackup for VMware: vStorage vs VCB” on page 13.

■ NetBackup can back up certain pre-vSphere environments (such as ESX 3.x)without requiring VCB.

■ NetBackup can perform file-level and block-level incremental backups ofvirtual machines (cumulative and differential).

■ NetBackup can perform full and incremental backups by means of the samesnapshot backup option.

■ NetBackup can create virtual machine backups that are storage optimized(unused space on the virtual machine is not backed up).

■ NetBackup can back up virtual machines by their host name, VMware displayname, or UUID.

■ New virtual machine recovery dialogs make it easier to recover the virtualmachine to the original location or to an alternate location.

IntroductionNew in this release

12

Full virtual machine backup vs file-level backupWhen configured as described in this guide, NetBackup backs up the entire virtualmachine as a set of virtual disk files. The backup includes all data files as well asoperating system files and VMware virtual disk files. From the backup, you canrecover the guest OS and the entire virtual machine. Depending on the optionchosen in the backup policy, you can also recover individual files from the samebackup (Windows virtual machines only).

For Windows, NetBackup also supports file-level backup (backup of selected files).File-level backup requires VCB. For more information on file-level backup ofWindows virtual machines, see the appendix titled "File-level backup of Windowsvirtual machines."

NetBackup for VMware: vStorage vs VCBNetBackup 6.5.x for VMware relied upon VMware Consolidated Backup technology(VCB) to make off-host backups of virtual machines. VCB software was installedon the VMware backup host (called the backup proxy server). For backups of theentire virtual machine, all files were copied from the VMware datastore and writtento disk on the backup host.

NetBackup 7.0 now uses VMware vStorage APIs for Data Protection. vStorageAPIs enable a variety of data protection features for more efficient use of storagecapacity and faster backups. NetBackup can use vStorage to back up the latestvSphere environments and earlier VMware environments.

Note that NetBackup 7.0 can back up vSphere environments using VCB. VMwareintends to discontinue VCB in a future release, however, and recommends the useof vStorage APIs.

Minimum levels for vStorage supportTo use VMware vStorage, NetBackup requires the following minimum levels ofVMware servers: ESX 3.5, or VirtualCenter 2.5. NetBackup can use vStorage witholder ESX servers (such as 3.0.2) if they are behind a VirtualCenter at version 2.5or later.

When is VCB required?NetBackup can protect most VMware environments by means of VMware's newervStorage APIs, without using VCB.

VCB is required in the following cases:

13IntroductionFull virtual machine backup vs file-level backup

■ For backups of selected files instead of the entire virtual machine, if aNetBackup client is not installed on the virtual machine.

■ For incremental backups that use the virtual machine backup option calledFull backup with file level incremental.

■ For the following older VMware environments:

■ ESX servers older than 3.5 if no VirtualCenter server is present.

■ For VirtualCenter servers older than 2.5.

Why is VCB not being used?When possible, NetBackup automatically uses vStorage instead of VCB, even whenbacking up certain VMware environments that are older than vSphere. If the ESXserver is at least 3.5, or the VirtualCenter is at least 2.5, NetBackup uses vStorage.Even if installed, VCB is not used in these environments.

NetBackup uses VCB for VMware environments that are older than ESX 3.5 orVirtualCenter 2.5. It also uses VCB if the policy is configured for Windows file-levelbackups. See the appendix titled "File-level backup of Windows virtual machines."

NetBackup for VMware environmentThis section describes the NetBackup for VMware environment.

NetBackup for VMware componentsNetBackup for VMware uses the following components.

Backup hostNetBackup for VMware uses a special Windows server that is called a backup host(formerly called the VMware backup proxy server). The backup host is a NetBackupclient that performs backups on behalf of the virtual machines. The backup hostcan also be configured as a NetBackup master or media server.

The backup host is the only host on which NetBackup client software is installed.No NetBackup client software is required on the VMware virtual machines.

Note that the backup host is referred to as the recovery host when it performs arestore.

IntroductionWhy is VCB not being used?

14

Virtual machineVirtual machines provide complete guest operating systems on virtualizedhardware. In a NetBackup policy, a virtual machine is configured as a NetBackupclient, even though NetBackup client software is not installed on the virtualmachine.

ESX serverThe VMware ESX server presents a virtualized hardware environment to multiplevirtual machines; each virtual machine runs an independent operating system.Users can run applications in the virtualized OS as if the OS was installed in itsown physical machine.

vCenter ServerThe VMware vCenter Server (or VirtualCenter server) coordinates multiple ESXservers and workloads. It can migrate virtual machines from one ESX server toanother. It also provides the ability to back up the virtual machines that are turnedoff.

The vCenter Server is optional in the NetBackup for VMware environment.

Converter serverFor backups that were made with VCB, the VMware Converter server assists infull virtual machine restores to the ESX server. The Converter must be installedon the same host as the VMware backup host.

VMware NetBackup Integration Module (VNIM) not required!The VMware NetBackup Integration Module (VNIM) is not required for NetBackupfor VMware. Conflicts can occur between NetBackup for VMware policies and anyolder script-based policies that use VNIM.

See “Notes and tips” on page 83.

Environment diagramsFigure 1-1 shows the hardware components for NetBackup for VMware.

15IntroductionNetBackup for VMware environment

Figure 1-1 NetBackup for VMware: backup environment

NetBackupmaster server

LAN / WAN

VMware ESX serverwith virtual machines

VMware backup hostacting as both NetBackupmedia server and client

SAN

NetBackupstorage unit(disk or tape)

VMware virtual disk files(datastore) must be available to

VMware backup host

Figure 1-2 shows a NetBackup for VMware environment with a VMwareVirtualCenter that manages multiple ESX servers.

Figure 1-2 VMware VirtualCenter that manages multiple ESX servers

VMwareVirtualCenter

NetBackupmaster server

LAN / WAN

VMware ESXservers

VMware backup host VMware virtual disk files(datastore)

SAN

NetBackupstorage unit(disk or tape)

Overview of the backup processThe following tables describe the phases in the NetBackup backup process.

Table 1-1 NetBackup backup process with vStorage

DescriptionPhase

The NetBackup master server initiates the backup.Phase 1

The NetBackup client on the VMware backup host initiates a VMwaresnapshot on the virtual machine.

Phase 2

Windows only: VSS synchronizes the file system on the virtual machine.Phase 3

The VMware server creates a snapshot on the virtual disk datastore.Phase 4

IntroductionNetBackup for VMware environment

16

Table 1-1 NetBackup backup process with vStorage (continued)

DescriptionPhase

The NetBackup client reads the snapshot from the datastores and writesthe data to the NetBackup storage unit.

Phase 5

Table 1-2 NetBackup backup process with VCB

DescriptionPhase

The NetBackup master server initiates the backup.Phase 1

The NetBackup client on the VMware backup host initiates a VMwaresnapshot on the virtual machine.

Phase 2

Windows only: VSS synchronizes the file system on the virtual machine.Phase 3

The VMware server creates a snapshot on the virtual disk datastore.Phase 4

The VMware backup host does one of the following:

■ For full virtual machine backup, it copies the files from the VMwaredatastore and writes them to disk on the backup host.

■ For file-level backup, it mounts individual disk volumes from theVMware datastore.

Phase 5

The NetBackup client reads the data from the backup host and writes thedata to the NetBackup storage unit.

Phase 6

NetBackup for VMware license requirementNetBackup for VMware requires the NetBackup Enterprise Client license.

NetBackup for VMware configuration tasks: overviewThis section describes configuration tasks for VMware and for NetBackup.

VMware tasksThe VMware components including ESX servers and virtual machines must beset up before you configure NetBackup.

Table 1-3 briefly describes these VMware-specific tasks; further assistance withthese tasks may be found in your VMware documentation.

17IntroductionNetBackup for VMware configuration tasks: overview

Table 1-3 VMware tasks

TasksSequence

Set up disk storage on Fibre Channel or iSCSI. The VMware backuphost must be able to access the disk storage.

Phase 1

Install the VMware ESX server and virtual machines.Phase 2

Install VMware Tools on the virtual machines that you plan to backup.

Phase 3

Optional: install a vCenter (or VirtualCenter) server.Phase 4

For recovery of VCB backups: Install the VMware Converter server onthe VMware restore host.

The VMware Converter server is not required for vStorage.

Phase 5

For older versions of VMware only: Install a supported version of VCBon the VMware backup host.

See “When is VCB required?” on page 13.

For further information on supported guest operating systems andVMware components and versions, refer to the following Symantectech note: http://entsupport.symantec.com/docs/312604

Symantec recommends that the NetBackup media server and theVMware backup host be installed on the same host.

Phase 6

Notes:

■ Ensure that the hardware and the SAN are configured properly. The VMwaredatastore where the target virtual machine files exist must be accessible tothe VMware backup host.With vStorage, and with VCB version 1.1 and ESX server 3.5, note: A SANconnection between the backup host and the datastore is optional if you usethe NBD transfer type or NBDSSL transfer type.

■ VMware has specific hardware and configuration requirements. VMware SANrequirements can be found in the appropriate VMware SAN Configurationguide.

NetBackup tasksTable 1-4 lists the NetBackup configuration tasks that are described later in thischapter and in other NetBackup documentation, as indicated.

IntroductionNetBackup for VMware configuration tasks: overview

18

Table 1-4 NetBackup tasks

TasksSequence

Install the NetBackup 7.0 master server and media server.

See the NetBackup 7.0 Installation Guide.

Symantec recommends that the NetBackup media server and theVMware backup host be installed on the same host.

Phase 1

Install the NetBackup 7.0 Enterprise Client license on the masterserver, and install NetBackup client 7.0 software on the VMwarebackup host.

Phase 2

Add the VMware backup host to your NetBackup configuration.

See “Adding the VMware backup host to NetBackup configuration”on page 30.

Phase 3

Set NetBackup access credentials for the VMware vCenter orVirtualCenter (if any), or for VMware ESX servers.

See “Adding NetBackup credentials for VMware” on page 30.

Phase 4

Configure incremental backups for VMware.

See “Incremental backups must be based on timestamps ”on page 33.

Phase 5

Create a NetBackup policy for VMware.

See “Configuring a VMware policy from the Policies node”on page 33.

Phase 6

Perform a backup or restore.

See “Backing up virtual machines” on page 51.

See “VMware restore procedures: overview” on page 55.

Phase 7

Recheck the configuration.

See “Best practices” on page 75.

See “Backup and restore problems” on page 84.

Phase 8

About VMware storage optimizationVMware’s vStorage technology can track block-level changes in the virtualmachine. Block-level change tracking allows NetBackup to skip unused(unallocated) regions on the virtual disk during the backup. The result is a smallerbackup image (storage optimized).

19IntroductionAbout VMware storage optimization

You can enable storage optimization in either of the following ways:

■ Select Perform block level incremental backup in the NetBackup policy.NetBackup uses storage optimization when it backs up the virtual machinesthat are listed in the policy.For Perform block level incremental backup, the VMware virtual machineversion must be vmx-07 or later.Note: It may be necessary to delete an existing snapshot before you start thebackup.See “Deleting a vSphere Client snapshot” on page 25.

■ Or, if you intend to use the snapshot feature of vSphere Client before you starta NetBackup backup of the virtual machine: Set the vSphere Client “ctkEnabled”option to “true” before you use vSphere Client to create the snapshot.See “Setting the Changed Block Tracking option in vSphere Client” on page 25.

TerminologyTable 1-5 lists the terminology that is used in NetBackup for VMware. For furtherexplanations of VMware terminology, refer to your VMware documentation.

Table 1-5 NetBackup for VMware common terms

DefinitionTerm

In NetBackup for VMware, the datastore is a disk that containsthe virtual machines files.

datastore

An operating system that runs on a virtual machine.guest OS

A software virtualization layer that lets different operatingsystems run simultaneously on the same physical machine.

hypervisor

A virtual disk that cannot be captured with a snapshot. Anindependent disk can be configured as either persistent ortemporary.

Note: NetBackup for VMware cannot back up the data on anindependent disk. The backup appears to succeed, but the backupimage contains no data for the independent disk.

independent disk

Allows a virtual machine to directly access physical disks (on FibreChannel or iSCSI). By means of RDM, disk LUNs appear to be filesin a VMFS volume.

Note that disks in RDM mode cannot be backed up with VMwareVCB (on a backup host). NetBackup client software must beinstalled in the virtual machine.

Raw device mapping(RDM)

IntroductionTerminology

20

Table 1-5 NetBackup for VMware common terms (continued)

DefinitionTerm

Flushes the OS buffers (Windows only) before VMware snapshotsare initiated. The sync driver is installed by means of VMwareTools.

sync driver

See VMware Consolidated Backup.VCB

An execution environment that the hypervisor creates for thecomputer hardware. The resulting virtualized environment allowsdifferent operating systems to run simultaneously on the samephysical machine.

virtual machine

In a VMware ESX server, one or more vmdk files make up the diskimage or virtual drive in a virtual machine. The.vmdk files containthe operating system, applications, and data in the virtualmachine.

vmdk file

An off-host backup server in a NetBackup for VMwareenvironment. The VMware backup host performs backups onbehalf of virtual machines.

The backup host is referred to as the recovery host during restore.

VMwarebackup/recovery host

An off-host backup application programming interface (API)created by VMware. Designed to off load backups from the ESXserver.

VMware ConsolidatedBackup

Installed inside each VMware virtual machine. Enhances thevirtual machine performance and adds backup-relatedfunctionality.

VMware Tools

VMware vStorage APIs for Data Protection enable data protectionfeatures for more efficient use of storage capacity. NetBackup canuse vStorage to back up the latest vSphere environments as wellas to back up earlier VMware environments.

vStorage

21IntroductionTerminology

IntroductionTerminology

22

Notes and prerequisites


■ Prerequisites

■ Notes and restrictions

■ Deleting a vSphere Client snapshot

■ Setting the Changed Block Tracking option in vSphere Client

■ Notes on the hotadd transfer type

■ Creating a helper virtual machine for hotadd transfer

PrerequisitesThe following prerequisites apply to NetBackup for VMware:

■ The VMware backup host must run Windows 2003 or 2008. (For VCB onWindows 2008, VCB 1.5 is required.) The supported hardware types are thesame as for any NetBackup Windows client. For further information onsupported guest operating systems and VMware components and versions,refer to the following Symantec tech note:http://entsupport.symantec.com/docs/312604

■ To use the hotadd transfer type for backup or restore, the VMware backup orrestore host is installed in a virtual machine.For ESX 3.5 and earlier: You must set up a shadow virtual machine that hasthe same name as the backup host but with the (VCB-HELPER) suffix.

See “Creating a helper virtual machine for hotadd transfer” on page 28.See “Notes on the hotadd transfer type” on page 27.

2Chapter

Notes and restrictionsNote the following about NetBackup for VMware:

■ NetBackup for VMware does not work with the VMware NetBackup IntegrationModule (VNIM). Conflicts can occur between NetBackup for VMware policiesand any older script-based policies that use VNIM.See “Notes and tips” on page 83.

■ NetBackup for VMware does not support the NetBackup Instant Recoveryfeature.

■ If a Windows virtual machine includes Veritas Storage Foundation volumes,only the Full VM backup option and the Perform block level incrementalbackup option (BLIB) are supported.

■ For backups using VCB, NetBackup for VMware supports USB drives as thesnapshot mount point (for staging) on a VMware backup host. The USB drivemust be formatted with the NTFS file system.

■ NetBackup for VMware does not support the Mapped full VM backup optionfor virtual machines that contain encrypted drives. For backups of virtualmachines that have encrypted drives, use the Full VM backup option.

■ For Windows virtual machine backups using VCB, the snapshot mount pointon the backup host must be a local drive, not network mounted. Do not setcompression or encryption on the mount point.

■ To restore individual NTFS encrypted files, you must install a NetBackup clienton the virtual machine.See “Best practices” on page 75.

■ For UNIX and Linux virtual machines, single file restore is not supported.

■ Storage optimization cannot be used if a snapshot exists on the virtual machinewhen VMware Changed Block Tracking is turned on.See “Setting the Changed Block Tracking option in vSphere Client” on page 25.See “About VMware storage optimization” on page 19.

■ For any non-VCB virtual machine backup that NetBackup 7.0 for VMwaremade, the NBDSSL transport method is not supported during the restore. Notethat VMware's current vStorage VDDK API does not support the NBDSSLtransport method during restore.

■ If the policy's Client name selection option is set to VM hostname, note:NetBackup cannot select a VMware virtual machine for backup if it cannotobtain an IP address for the virtual machine.

■ If the restore host is on Windows Server 2008 and you use the SAN transfertype for the restore, the SAN luns must be online.

Notes and prerequisitesNotes and restrictions

24

See “Restore fails with NetBackup status code 5” on page 90.

Further notesAdditional information is available in the following:

■ For up-to-date information on supported VMware components, guest operatingsystems, and file systems, see the following Symantec tech note:http://entsupport.symantec.com/docs/312604The tech note contains information on NetBackup support for VMware vSphere.

■ For notes and limitations about NetBackup for VMware in this 7.0 release, seethe NetBackup Release Notes.

Deleting a vSphere Client snapshotFor a storage optimized backup, you must delete any vSphere Client snapshot andre-initiate the NetBackup backup if both of the following are true:

■ A vSphere Client snapshot of the virtual machine already exists before thebackup starts.

■ The vSphere Client Changed Block Tracking (ctkEnabled) option was notenabled before the vSphere snapshot was created.

Background information is available on storage optimized backups:

See “About VMware storage optimization” on page 19.

To delete a vSphere Client snapshot

1 In the vSphere Client interface, right-click on the virtual machine and selectSnapshot > Snapshot Manager.

2 Select the snapshot and click Delete.

Setting theChangedBlock Tracking option in vSphereClient

If you use vSphere Client to create a snapshot before the VMware changed blocktracking option is enabled, NetBackup cannot use storage optimization for thatvirtual machine. You must do the following on the virtual machine before usingvSphere Client to take a snapshot.

Note that NetBackup does not require that you use the Snapshot feature in vSphereClient. NetBackup automatically creates a snapshot when a NetBackup backupjob starts.

25Notes and prerequisitesDeleting a vSphere Client snapshot

To enable Changed Block Tracking for the virtual machine

1 In vSphere Client, power off the virtual machine.

2 Select the virtual machine, then click Edit settings.

3 Obtain the hard drive controller and disk numbers (scsi and ide) for eachvirtual drive on the virtual machine.

To find the controller and disk numbers, do the following:

■ Click the Hardware tab.

■ Click on each hard disk. Its scsi or ide controller and disk numbers appearunder Virtual Device Node, in the form SCSI(X.X) or IDE(X.X). Make anote of each.

4 Click the Options tab. Under Advanced, General, click ConfigurationParameters.

5 On the Configuration Parameters screen, click Add Row.

6 Enter ctkEnabled in the Name column and enter true for the Value.

7 For each virtual drive on the virtual machine, enter a Name in the formscsiX:X.ctkEnabled or ideX:X.ctkEnabled, where X:X represents thecontroller and disk number of each disk as found on the Hardware tab.

For example: scsi0:0.ctkEnabled for the first disk and scsi0:1.ctkEnabled

for the second disk. (The numbers for your disks may be different.)

8 Enter true for the Value of each disk entry.

Notes and prerequisitesSetting the Changed Block Tracking option in vSphere Client

26

9 Click OK.

10 Power on the virtual machine.

Now you can use vSphere Client to take a snapshot of the virtual machine.NetBackup can apply vStorage optimization (changed block tracking) to futurebackups of the virtual machine.

Notes on the hotadd transfer typeNetBackup supports several transfer types for sending snapshot data betweenthe VMware datastore and the VMware backup host during a backup or restore.One of those transfer types (hotadd) is used when the VMware backup host isinstalled in a virtual machine.

Note the following about the hotadd transfer type:

■ For a backup or restore, the hotadd transfer type does not support the .vmdkfiles that are larger than 1 TB. If the .vmdk file is larger than 1 TB, the filecannot be mounted.

■ The VMware backup host must be installed in a virtual machine.

■ For ESX versions 3.5 and earlier: You must configure a shadow (helper) virtualmachine before the backup starts. The helper virtual machine must have atleast as many SCSI controllers as exist on the virtual machine that you wantto back up.The helper virtual machine is used internally by the VMware VDDK to attachthe disks temporarily during hotadd backup or restore.A helper virtual machine is not required for backups of ESX 4.0 virtualmachines. For all other configurations, whether you use VCB or vStorage, ahelper virtual machine is required.See “Creating a helper virtual machine for hotadd transfer” on page 28.

■ NetBackup does not support IDE disks on the virtual machine or on the backuphost.

■ On the virtual machine to back up, no two disks should have the same name.(Identical names can occur if the disks reside on different datastores.)

■ The ESX server (where the backup-host virtual machine resides) must haveaccess to the datastore of the virtual machines that you want to back up.

■ The datastore for the backup-host virtual machine must have some free spacebefore the hotadd backup begins. Otherwise, the backup may fail.

■ For additional hotadd information, see the following VMware VDDK ReleaseNotes:http://www.vmware.com/support/developer/vddk/VDDK-1.1-Relnotes.html

27Notes and prerequisitesNotes on the hotadd transfer type

Creating a helper virtualmachine for hotadd transferThis procedure applies only to ESX versions 3.5 (and earlier) with use of the hotaddtransfer type.

To create a helper virtual machine for hotadd backup or restore

1 Create a virtual machine.

You do not need to assign any drives to the virtual machine.

2 Give the helper virtual machine the same VMware display name as the virtualmachine where the backup host is installed. Add the (VCB-HELPER) suffix tothe name.

For example, if the virtual machine that contains the backup host is calledbu_host_VM, the name of the helper virtual machine must be the following:

bu_host_VM(VCB-HELPER)

Note that the complete name including the suffix must not exceed 32characters.

3 For more information on helper virtual machines, see the following VMwaredocument:

VMware Virtual Machine Backup Guide (Update 2 and later for ESX Server3.5, ESX Server 3i version 3.5, VirtualCenter 2.5).

Notes and prerequisitesCreating a helper virtual machine for hotadd transfer

28

Configure NetBackup forVMware


■ Adding the VMware backup host to NetBackup configuration

■ Adding NetBackup credentials for VMware

■ Changing the host name of a VMware server in NetBackup

■ Incremental backups must be based on timestamps

■ Configuring a VMware policy from the Policies node

■ Configuration parameters for VMware

■ Browse for VMware Virtual Machines screen

■ Configuring a VMware policy from the Snapshot Policy Configuration wizard

■ About incremental backups of virtual machines

■ Volume Manager volumes in the virtual machine

■ Backup options compared

■ Reducing the size of backups

■ About block-level backup

■ Recovery options: vStorage vs VCB

3Chapter

Adding the VMware backup host to NetBackupconfiguration

You must add the VMware backup host to your NetBackup configuration. In theNetBackup Administration Console, do the following.

To add the VMware backup host

1 Click HostProperties>MasterServer> and double click NetBackupmasterserver > VMware backup hosts.

2 Click Add.

3 Enter the fully qualified domain name of the VMware backup host, and clickAdd.

4 When you are finished adding backup hosts, click Close.

5 Click Apply and then OK.

Adding NetBackup credentials for VMwareThe NetBackup server requires logon credentials to access the VMware ESX serversor the VMware VirtualCenter. In the NetBackup Administration Console, do thefollowing.

To add NetBackup credentials

1 Click Media and Device Management > Credentials > Virtual MachineServers.

2 Click Actions > New > New Virtual Machine Server and enter the fullyqualified domain name of the virtual machine server (VirtualCenter or ESXserver).

3 In the Credentials pane of the Virtual Machine Server dialog, enter thefollowing:

Virtual machine server type

Select the type of virtual machine:

■ VMware VirtualCenter serverFor a vCenter server (or VirtualCenter server) that manages multipleVMware ESX servers.Note: If you have a vCenter server, do not enter logon credentials forindividual ESX servers. NetBackup uses the credentials for the vCenteronly.

■ VMware ESX server

Configure NetBackup for VMwareAdding the VMware backup host to NetBackup configuration

30

For ESX servers where there is no vCenter server (or VirtualCenter). Usethis dialog box to enter credentials for each ESX server.

■ VMware restore ESX serverFor an ESX server to which NetBackup can restore virtual machinesdirectly, bypassing the vCenter server. This option is intended for restoresthat use the SAN transfer type.Restoring a virtual machine through the vCenter server (instead of directlyto an ESX server) may result in a slower restore over the SAN.

User name

Enter the user name for the virtual machine server. Note that spaces in usernames are not allowed.

Password

Enter the password (and confirm it) for the virtual machine server.

Validate Credentials

Select this box to have the credentials verified. When you click OK, NetBackupverifies that the credentials you have entered are currently valid for thevirtual machine server. An invalid entry that you enter during this sessionis deleted from the dialog.

If your VMware backup host is running a version of NetBackup that is earlierthan 6.5.4, the credentials cannot be validated. An error message is displayed.You must verify that the credentials you entered are correct for the VMwareserver. If the credentials are correct, you can ignore the error message.

Connect using port number

This option applies only to backups that use VCB.

Unless the port number was changed on the VMware server, no portspecification is required if you use VCB 1.1 or later. If the Connectusingportnumber box is checked, deselect it. VCB determines the port.

If you use a version of VCB that is older than 1.1, click the Connectusingportnumber box and use the default port 902.

Note: If you select port 902 and use an ESX server 3.5 or later, the VMwarebackup host is unable to communicate with the VirtualCenter or ESX servers.The attempt to back up the virtual machines fails. The credentials validationalso fails if you selected Validate Credentials.

31Configure NetBackup for VMwareAdding NetBackup credentials for VMware

4 Click OK.

5 If your site has multiple ESX servers but no vCenter server, use the VirtualMachine Server dialog to enter credentials for each ESX server.

Changing the host name of a VMware server inNetBackup

Use the following procedure if you need to change a VMware server's host nameas it is stored in NetBackup.

Example reasons for changing the VMware server name are the following:

■ If you used a simple host name for the server when you added its NetBackupcredentials, and need to replace that host name with the fully qualified hostname.

■ If two hosts currently resolve to the same IP address, and one of them mustbe renamed and assigned a new IP address.

To change the host name of a VMware host in NetBackup

1 Remove the current credentials that were entered for the VMware host.

Do the following:

■ In the NetBackup Administration Console, click on Media and DeviceManagement > Credentials > Virtual Machine Servers.

■ Right-click on the credentials definition for the VMware server and selectDelete (or press the Delete key).

2 Remove the VMware host from the NetBackup EMM database.

Enter the following command:

nbemmcmd -deletehost -machinename VMware_server_name

-machinetype virtual_machine

3 In the NetBackup Administration Console, re-enter NetBackup's credentialsfor the VMware server.


Make sure to enter the correct host name for the VMware server.

Configure NetBackup for VMwareChanging the host name of a VMware server in NetBackup

32

Incremental backups must be based on timestampsIncremental backups of virtual machines must be based on timestamps, not onarchive bit. You must configure the NetBackup client on the VMware backup hostas described in this section.

To configure the client on the VMware backup host for incremental backups

1 Start the NetBackup Backup, Archive, and Restore interface from theNetBackup client that is installed on the VMware backup host.

2 Click File > NetBackup Client Properties.

3 On the General tab, make sure Perform incrementals based on archive bitis clear (unchecked).

Configuring a VMware policy from the Policies nodeYou can create a policy (full or incremental) to back up the virtual machine ineither of two ways:

■ Use the Policies node of the NetBackup Administration Console (described inthis topic).

■ Use the Snapshot Policy Configuration wizard.See “Configuring a VMware policy from the Snapshot Policy Configurationwizard” on page 45.

To configure a policy for backup of individual files, see the appendix titled"File-level backup of Windows virtual machines."

To configure a policy to back up the virtual machine

1 In the NetBackup Administration Console, click Policies and select Actions> New > New Policy.

2 Select the FlashBackup-Windows policy type.

The FlashBackup-Windows policy type is recommended for mostenvironments. Use it to back up individual drives (Windows), or to back upthe entire virtual machine (any supported virtual machine).

Note the following about the FlashBackup-Windows policy type:

■ Increases the backup speed as compared to standard file-order backupmethods, if the virtual machine is heavily populated with small files.

■ Can create a backup from which you can restore selected files or the fullvirtual machine.

33Configure NetBackup for VMwareIncremental backups must be based on timestamps

For UNIX and Linux virtual machines, FlashBackup-Windows is the onlysupported policy type.

For more information on the FlashBackup-Windows policy type and virtualmachine backups, see the following:

See “Backup options compared” on page 46.

3 Select a policy storage unit or storage unit group.

Storage unit groups are described in the NetBackup Administrator’s Guide,Volume I.

4 Note that the FlashBackup-Windows policy type automatically selects Performsnapshot backups.

The following is the Snapshot Client pane on the lower left of the policyattributes tab:

Make sure that CollectdisasterrecoveryinformationforBareMetalRestoreis not selected.

5 Select Perform off-host backup.

6 From the pull-down list for the Use field, select VMware backup host.

7 In the Machine field, specify the name of the VMware backup host.

If the VMware backup host does not appear in the Machine pull-down list,make sure that it was added to the Host Properties setting.

See “Adding the VMware backup host to NetBackup configuration” on page 30.

You may have to close and reopen the policy for the added VMware backuphost to appear in the list.

Configure NetBackup for VMwareConfiguring a VMware policy from the Policies node

34

8 For block-level backups of the virtual machine, select Perform block levelincremental backups.

This option reduces the backup size. To enable this option, you must firstselect Perform off-host backup and VMware backup host.

See “About block-level backup” on page 48.

9 Click Options.

The following is the upper half of the Snapshot Options dialog box(Configuration Parameters). The lower portion (Snapshot Resources) is notused.

See “Configuration parameters for VMware” on page 37.

10 To save these settings, click OK and then Apply.

11 Use the Schedules tab to define a schedule.

On the attributes tab, you can select Full backup, Differential IncrementalBackup, or Cumulative Incremental Backup.

Incremental backups require one of the following configurations:

■ On the policy attributes tab, select Perform block level incrementalbackups. Requires ESX server 4.0 and virtual machine at vmx-07 or later.

■ Or select the Mapped full VM backup or Full backup with file levelincremental option for the Virtualmachinebackup type on the SnapshotOptions dialog.

35Configure NetBackup for VMwareConfiguring a VMware policy from the Policies node

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

You can type the host name in the EntertheVMwarehostname field, or clickBrowse and select virtual machine.

See “Browse for VMware Virtual Machines screen” on page 42.

Note: In the NetBackup Java Administration Console, the Install Softwareoption is for installing NetBackup client software on trusting UNIX clients.This option does not apply to virtual machines.

13 Use the Backup Selections tab to specify the virtual machine or virtualmachine drives to back up.

Click New. You can make entries manually, or click on the pull-down (UNIX)or hand icon (Windows) to select from available directives.

For VMware snapshot backup, the System_State directive (Windows 2000)and the ShadowCopy Componentsdirective (Windows 2003) are not supported.

Enter either of the following and then click Add (on UNIX) or press Enter(Windows):

■ Individual drive letters.Enter the drive letter as follows (for example):

\\.\E:

The drive must be designated exactly as shown (E:\ is not correct).

■ ALL_LOCAL_DRIVES

The ALL_LOCAL_DRIVES directive backs up all local drives on the virtualmachines that are selected on the Clients tab. This entry is the only onesupported for UNIX and Linux virtual machines.Note the kinds of files that are included in an ALL_LOCAL_DRIVES backup:

Configure NetBackup for VMwareConfiguring a VMware policy from the Policies node

36

The ALL_LOCAL_DRIVES directive backs up all data fileson the virtual machines.

ALL_LOCAL_DRIVES also backs up the following, if thesnapshot option is Full VM backup, Mapped full VM backup,or Full backup with file level incremental:

■ Windows System State files

■ Windows OS partitions that contain the Windowssystem files (usually C:)

■ VMware virtual disk files


Note: If you chose Full VM backup or Mapped Full VMbackup for the Virtual Machine Backup parameter,ALL_LOCAL_DRIVES is the only entry allowed for backupselections.

FlashBackup-Windowspolicy

To back up individual files or folders instead of a drive, you must configurea file-level backup. See the appendix titled "File-level backup of Windowsvirtual machines." Note that VCB is required.

14 If you click Apply or OK on the policy Attributes tab, a validation processchecks the policy and reports any errors. If you click Close, no validation isperformed.

Configuration parameters for VMwareThe following parameters apply to the VMware snapshot method:

Client name selectionSpecifies the type of name by which NetBackup recognizes a virtual machine.

The network hostname for the virtual machine.VM hostname

The name of the virtual machine as it appears in the VMwareinterface.

VMware display name

The unique ID assigned to the virtual machine when thevirtual machine was created.

VMware UUID

If you create a policy and then change the ClientNameSelection value, note: Youmay have to delete the virtual machine selections that were made on the Clientstab and re-enter them. Otherwise, NetBackup may no longer be able to identifythe virtual machines to back up.

37Configure NetBackup for VMwareConfiguration parameters for VMware

For example, if you change the Client Name Selection from VM hostname to VMdisplay name, and the display names of the virtual machines are different fromthe host names, the host names in the Clients tab cannot be used and the virtualmachines are not backed up. You must delete the host name entries on the Clientstab and browse the network to select the virtual machines by display name.

Note: When creating virtual machines, use the same name for both host nameand display name. If the Client Name Selection is changed, the existing entrieson the Clients tab still work.

Virtual machine backup

Backs up either of the following:

■ Individual folders and files, individual drives, or all local drives,with the MS-Windows policy type.

■ Individual drives or all local drives, with theFlashBackup-Windows policy type.

FilelevelsnapshotusingVCB cannot be used to back up Windowssystem files or VMware virtual disk files.

FilelevelsnapshotusingVCB requires VCB on the VMware backuphost.

See “About file-level backup of Windows virtual machines”on page 99.

File level snapshotusing VCB

Backs up the entire virtual machine. This option works with theFlashBackup-Windows policy type only. Individual files cannotbe restored from this backup.

Full VM backup

Backs up the entire virtual machine. This option works with theFlashBackup-Windows policy type only. Two kinds of restore arepossible from a mapped full backup: restore of the entire virtualmachine or of individual folders and files.

To perform a VMware backup to a deduplication storage unit,select the Mapped full VM backup option. This option providesthe best deduplication rates. Use of the Full VM backup optionresults in a lower rate of deduplication.

A tabular presentation of these parameters is available.


Mapped full VMbackup

Configure NetBackup for VMwareConfiguration parameters for VMware

38

A combination of MappedfullVMbackup andFilelevelsnapshotusing VCB. Backs up the entire virtual machine for full backups,and backs up individual files, folders, or drives for incrementalbackups. This option works with the FlashBackup-Windows policytype only.

Note: This option is primarily intended for NetBackup 6.5.xsystems that are upgraded to 7.0. When making backups with a7.0 system, you should use the Full VM backup or Mapped fullVM backup option instead, with an incremental schedule.

Full backup with filelevel incremental

Transfer typeIf you use VCB for the backup, these options require ESX server 3.5 or later andVCB 1.1 or later.

The transfer types determine how the snapshot data is sent from the VMwaredatastore to the VMware backup host. The appropriate option depends in part onthe type of network that connects the VMware datastore to the VMware backuphost.

For unencrypted transfer over Fibre Channel (SAN) or iSCSI.This value is the default.

san

For unencrypted transfer over a local network that uses theNetwork Block Device (NBD) driver protocol. This type oftransfer is usually slower than Fibre Channel.

nbd

For encrypted transfer (SSL) over a local network that usesthe Network Block Device (NBD) driver protocol. This typeof transfer is usually slower than Fibre Channel.

nbdssl

Provides transfer flexibility if the VMware datastore isavailable on both a SAN and a local network. NetBackupattempts an unencrypted transfer over Fibre Channel (SAN)or iSCSI. If that fails, it transfers the snapshot data usingthe Network Block Device (NBD) driver protocol over thelocal network.

try san then nbd

Provides transfer flexibility if the VMware datastore isavailable on both a SAN and a local network. NetBackupattempts an unencrypted transfer over Fibre Channel (SAN)or iSCSI. If that fails, it transfers the snapshot data with SSLencryption using the Network Block Device (NBD) driverprotocol over the local network.

try san then nbdssl


Lets you run the VMware backup host in a virtual machine.This feature requires ESX 3.5 Update2 or later.

For instructions on this transport mode and on installingthe backup host in a VMware virtual machine, refer to yourVMware documentation.

hotadd

Tries all possible transfer types and uses the first type thatsucceeds.

For vSphere systems, this option can automatically switchtransfer type for each .vmdk file, as needed. It selectswhichever type is appropriate, depending on the networkconnection that can be used to access the .vmdk file.

try all types

Virtual machine quiesce

Note: This option applies only to Windows virtual machines (such as Windows2003 and XP or later). It does not apply to older Windows systems or to UNIX orLinux.

By default, this option is enabled. In the great majority of cases, you should acceptthe default.

I/O on the virtual machine is quiesced before NetBackup creates the snapshot.Without quiescing file activity, data consistency in the snapshot cannot beguaranteed. If not consistent, the backed up data may be of little or no value.

If this option is disabled, the snapshot is created without quiescing I/O on thevirtual machine. In this case, you must perform your own checks for dataconsistency in the backup data.

Caution: Symantec does not recommend that you disable quiesce. In most cases,this option should be enabled.

Exclude unused and deleted blocksThis option reduces the size of the backup image by excluding any unused ordeleted blocks within the file system on the virtual machine.

Note the following:

■ This option applies only to backups of an entire virtual machine (it does notapply to backups that specify individual files only).

■ This option supports the Windows NTFS file system only.

Configure NetBackup for VMwareConfiguration parameters for VMware

40

■ This option uses proprietary mapping technology to identify vacant sectors(allocated but empty) within the file system. If the virtual disk contains rawspace, that raw space is included in the backup.

Existing snapshot handling

Note: This option applies only to backups that use VMware vStorage. It does notapply to backups that use VMware VCB.

After it creates a snapshot, NetBackup usually deletes the snapshot when thebackup has succeeded. If snapshots are not automatically deleted (whether createdby NetBackup or not), the performance of the virtual machine may eventually beaffected.

Note also that the existence of undeleted snapshots can cause restore failures dueto lack of disk space. If the virtual machine was configured on multiple datastoresand a leftover snapshot existed on the virtual machine when it was backed up,NetBackup tries to restore all .vmdk files to the snapshot datastore. As a result,the datastore may not have enough space for the .vmdk files, and the restore fails.(For a successful restore, you can restore the virtual machine to an alternatelocation. Use the Storage Destination dialog in the Virtual Machine Recoverydialogs to select a datastore for the .vmdk files.)

The Existingsnapshothandling parameter specifies what action NetBackup takeswhen a snapshot is discovered before creating a new snapshot for the backup.

NetBackup ignores any existing virtual machine snapshots(including snapshots previously created by NetBackup) andproceeds with snapshot creation and the backup.

Ignore

If any snapshot exists on the virtual machine, NetBackup abortsthe job for that virtual machine only.

Abort

If a virtual machine snapshot exists that a NetBackup vStorageor VCB backup previously created: NetBackup removes the oldsnapshot, creates an updated snapshot, and proceeds with thevirtual machine backup.

Remove NBU

Monolithic export (VCB only)This option applies only to backups that use VCB.


When NetBackup backs up a virtual machine, it copies the virtual machine .vmdkfiles from the VMware datastore to the VMware backup host. Note that NetBackupcan copy a large vmdk file to the VMware backup host as 2GB files instead of asa larger file. Sending a large vmdk file in smaller (2GB) units can improve transferspeed.

The default is Disabled: the vmdk file is transferred to the VMware backup hostin 2GB chunks.

Enabled means that the vmdk file is transferred to the VMware backup host as asingle file, regardless of how large the vmdk file is. In some cases, transferring avery large vmdk file may result in a slower transfer speed.

Snapshot mount point (VCB only)Specifies a folder on the VMware backup host. This option applies only to backupsthat use VMware VCB on the backup host.

An example mount point is:

G:\mnt

If the folder does not exist on the VMware backup host, NetBackup creates it.

This folder is used in one of two ways, depending on the parameter value that youchoose:

■ For file-level backups (File level snapshot using VCB), the VMware backup hostmounts snapshots of individual virtual disk volumes in this folder. Thesesnapshots are links to the virtual datastore. No virtual machine data is copiedto this folder.

■ For full virtual machine backups (Full VM backup or Mapped full VM backup),the VMware backup host creates a snapshot of the entire virtual machine inthis folder. This snapshot contains copies of all virtual disk files on the virtualdatastore that constitute a point-in-time image of the entire virtual machine.Enough space must be available in this folder to contain the snapshot.For Windows virtual machines, the mount point must be a local drive, notnetwork mounted. Also, do not set compression or encryption on the mountpoint.See “Other backup failures” on page 85.

Browse for VMware Virtual Machines screenUse this screen to select a vCenter server (VirtualCenter), ESX server, or individualvirtual machines.

Configure NetBackup for VMwareBrowse for VMware Virtual Machines screen

42

■ Enter the VM hostnameEnter the name of a virtual machine. The format of the name depends on yoursystem. It may be the fully qualified name or another name, depending onyour network configuration and how the name is defined in the guest OS. IfNetBackup cannot find the name you enter, policy validation fails.To enter a host name, make sure that Browse and select Virtual Machines isnot selected.

■ Browse and select Virtual MachineClick this option to discover ESX servers (shown in the left pane). You canselect virtual machines from a list (in the right pane).The virtual machine names that are listed may be derived from a cache file.Use of the cache file is faster than rediscovering the machines on the networkif your site has a large number of virtual machines.If NetBackup cannot obtain the IP address of the virtual machine, the hostname and IP address are displayed as NONE.

■ Last UpdateTo update the cache file and re-display virtual machines, click the refresh iconto the right of the Last Update field. This field shows the date and time of themost recent cache file that contains the names of virtual machines.

For NetBackup to access the virtual machines, the following are required:

■ For older virtual machines, VMware VCB must be installed on the VMwarebackup host.

■ The NetBackup master server must have credentials for the VMwareVirtualCenter or ESX server(s).See “Adding NetBackup credentials for VMware” on page 30.

43Configure NetBackup for VMwareBrowse for VMware Virtual Machines screen

■ The browsing timeout value must not be set too low.See “Changing the browsing timeout for virtual machine discovery”on page 82.

■ VM Host Name, Display Name, UUID, etc.When you select an ESX server in the left pane, new columns displayinformation about the virtual machines. You can change the settings andarrangement of these columns by right clicking on any of the column headers.The columns are the following:

The host name of the virtual machine.VM Host Name

The display name of the virtual machine.Display Name

The UUID of the virtual machine.UUID

The IP address of the virtual machine.IP Address

The guest OS system as defined when the virtual machinewas created.

OS

The datastore where the virtual machine configurationfiles are stored.

Data Store

The power on/off status of the virtual machine when itwas last discovered.

Power

Shows whether the virtual machine has a physical disk inraw device mapping mode (RDM) or has an independentdrive.

RDM Status

The VMware release version of the virtual machine(vmx-04 or vmx-07).

Platform

The time and date at which the virtual machine's UUIDwas initially discovered and cached.

Discovered Timestamp

Shows whether the virtual machine supports the VMwareChanged Block Tracking feature (for BLIB). Changed BlockTracking requires ESX server 4.0 and a virtual machineat vmx-07 or later.

Change Tracking Support

The ESX server in which the virtual machine resides (alsoappears in the left pane).

ESX Host

The datacenter that contains the virtual machine (alsoappears in the left pane).

Data Center

Configure NetBackup for VMwareBrowse for VMware Virtual Machines screen

44

The vCenter server that manages the ESX server (alsoappears in the left pane).

Virtual Center Name

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

Configuring aVMwarepolicy fromtheSnapshotPolicyConfiguration wizard

Use the following procedure.

To create a backup policy by means of the Snapshot Policy Configuration wizard

1 In the NetBackup Administration Console (on the NetBackup master server),click on the name of the master server.

2 Click Create a Snapshot Backup Policy.

3 Click Next.

4 On the Select Client screen, enter a name for the policy.

5 For Virtual Machine Type, select VMware.

6 Enter the name of the VMware backup host.

7 Follow the remaining screens in the wizard.

The wizard creates the policy according to your selections.

About incremental backups of virtual machinesNetBackup 7.0 provides a flexible approach to incremental backups, as follows:

■ For vStorage, NetBackup enables full virtual machine and file-levelincrementals in the same backup.

■ For VCB, NetBackup enables file-level incrementals.

Note the following about incremental backups of virtual machines:

45Configure NetBackup for VMwareConfiguring a VMware policy from the Snapshot Policy Configuration wizard

■ Incremental backups must be based on timestamps.See “Incremental backups must be based on timestamps ” on page 33.

■ With VCB, the only backup option that supports incrementals is Full backupwithfilelevel incremental. BLIB is not available. Operating system files cannotbe restored from the incremental backups that use this option.

■ Better support for incremental is available when you use BLIB (Performblocklevel incremental backups). BLIB requires ESX 4.0 and virtual machines atvmx-07 or later.

To configure incremental backup of a virtual machine, choose one of these options:

■ For VCB-based backups (older VMware environments): In the NetBackup policy,select the FlashBackup-Windows policy type and the Full backup with filelevel incremental option (on the Snapshot Client Options dialog).See “NetBackup for VMware: vStorage vs VCB” on page 13.

■ For vStorage backups: In the NetBackup policy, select theFlashBackup-Windows policy type and the Full VM backup or Mapped fullVM backup option on the Snapshot Client Options dialog. In the schedule,select either Differential Incremental Backup or Cumulative IncrementalBackup.More information is available about these backup options.See “Recovery options: vStorage vs VCB” on page 48.

Volume Manager volumes in the virtual machineTo back up a virtual machine that contains Veritas Storage Foundation VolumeManager volumes, use the Full VM backup option. Make sure that the Excludeunused and deleted blocks option is disabled.

Note: Restore of selected files from a backup of the full virtual machine is notsupported if the virtual machine contains Storage Foundation Volume Managervolumes.

See “Notes and restrictions” on page 24.

Backup options comparedTable 3-1 describes the backup options for FlashBackup-Windows policies.

Configure NetBackup for VMwareVolume Manager volumes in the virtual machine

46

Table 3-1 Backup options for FlashBackup-Windows policies

What can be restoredWhat is backed upVirtual MachineBackupparameter

Backup Selectionsentry

Individual folders and files, orentire drive (not includingoperating system or VMwarevirtual disk files)

Individual drives as raw devices.File level snapshotusing VCB

Individual drives

For example: \\.\E:

Individual folders and files, orentire drives (not includingoperating system or VMwarevirtual disk files)

All individual drives in virtualmachine as raw devices.


ALL_LOCAL_DRIVES

directive

Entire virtual machine onlyVMware virtual disk files. Backupis "raw partition" type.

Full VM backupALL_LOCAL_DRIVES

directive

Entire virtual machine orindividual folders and files

VMware virtual disk files. Backupis "raw partition" type.

Mapped full VMbackup

ALL_LOCAL_DRIVES

directive

Note that backup type Full backup with file level incremental is a combinationof Mapped full VM backup and File level snapshot using VCB. VMware VCBsoftware must be installed on the VMware backup host.

Reducing the size of backupsNetBackup provides several options for reducing the size of the backup image, asfollows:

■ Perform block level incremental backups (on policy attributes tab)Referred to as BLIB. Reduces the size of incremental backups by trackingblock-level changes. Only the blocks that have changed since the last full orincremental are included in an incremental backup. Applies to cumulative andto differential backups. This option applies only to ESX 4.0 virtual machinesat version vmx-07 or later.

■ Exclude unused and deleted blocks (on Snapshot Options dialog from policyattributes tab)Reduces the size of a full backup by excluding any unused or deleted sectorswithin the file system on the virtual machine.This option applies to full backups only and is not related to BLIB. Excludeunused and deleted blocks uses proprietary mapping technology to identifyvacant sectors (allocated but empty) within the file system. If the virtual diskcontains raw space, the raw space is included in the backup. To exclude raw

47Configure NetBackup for VMwareReducing the size of backups

space from the backup, select Perform block level incremental backups onthe policy attributes tab.

About block-level backupNetBackup supports block-level backups of the virtual machine. For block-levelbackups, NetBackup uses VMware's Changed Block Tracking feature to reducethe backup size. Since this option works at the block level (not at the file level), itapplies only to backups of the entire virtual machine. It cannot be used when thepolicy backup selections list specifies individual files.

This option reduces the size of full backups as well as the size of incrementalbackups, as follows.

Table 3-2 Block-level backup of the virtual machine: full vs incrementalschedule

Optimization that is used in backupType of backup

Backs up only the blocks that are currently used(allocated) in the virtual machine. Unallocated blocksare not included in the backup.

Backup of entire virtual machine,with full schedule

Backs up only the blocks that have changed since thelast backup. Blocks that have not changed are notincluded in the backup.

Backup of entire virtual machine,with incremental schedule

Note the following about block level incremental backups:

■ Can be used only with ESX 4.0 virtual machines at version vmx-07 or later.

■ Can be used only with the FlashBackup-Windows policy type.

■ Not available in VCB-based backups.

Recovery options: vStorage vs VCBThis section compares the NetBackup restore options available with vStorage vsVCB.

Recovery options with VMware vStorageThe following table describes the recovery features that are available when youuse vStorage. The first two columns (Virtual machine backup and Schedule) arebackup options; the other columns describe the recovery options.

Configure NetBackup for VMwareAbout block-level backup

48

These features require the FlashBackup-Windows policy type.

Table 3-3 Recovery features with vStorage

CommentsCanrecoverfiles

Canrecovervirtualmachine

ScheduleVirtualmachinebackup

NoYesFullFull VMbackup

Requires BLIB.NoYesIncrementalFull VMbackup

YesYesFullMapped fullVM backup

For full virtual machinerecovery, BLIB is required.

YesYesIncrementalMapped fullVM backup

NetBackup uses vStorage.YesYesFullFull backupwith file levelincremental

Requires VCB.YesNoIncrementalFull backupwith file levelincremental

Recovery options with VMware VCBThe following table describes the recovery features that are available when youuse VCB. Note that BLIB cannot be used with VCB.

Because it pertains only to Windows file-level backups, the File level snapshotusing VCB backup option is not included in this table.

See “About file-level backup of Windows virtual machines” on page 99.

Table 3-4 Recovery features with VCB (note: BLIB is not supported)

Comments (BLIB is notsupported)

Canrecoverfiles


ScheduleVirtualmachinebackup type

For VCB-based backups, the FullVM backup option does notsupport incrementals.

NoYesFullFull VMbackup

49Configure NetBackup for VMwareRecovery options: vStorage vs VCB

Table 3-4 Recovery features with VCB (note: BLIB is not supported) (continued)

Comments (BLIB is notsupported)

Canrecoverfiles


ScheduleVirtualmachinebackup type

Incremental backup is notavailable with VCB and Full VMbackup. Use Full backup withfile level incremental instead.

N/AN/AIncrementalFull VMbackup

YesYesFullMapped fullVM backup

Incremental backup is notavailable with VCB and MappedfullVMbackup. Use Fullbackupwith file level incrementalinstead.

N/AN/AIncrementalMapped fullVM backup

This backup option providessupport for NetBackup 6.5.xsystems that are upgraded to 7.0.

YesYesFullFull backupwith file levelincremental

Performs file-level incrementalbackup only.

This backup option providessupport for NetBackup 6.5.xsystems that are upgraded to 7.0.

YesNoIncrementalFull backupwith file levelincremental

Configure NetBackup for VMwareRecovery options: vStorage vs VCB

50

Back up VMware virtualmachines


■ Backing up virtual machines

■ Further information on NetBackup policies

Backing up virtual machinesVirtual machine backups initiate from a NetBackup policy. You can start thebackup manually from a policy, or have it run automatically according to a schedulethat is defined in the policy.

To create the policy, you can use the Policies node of the NetBackupAdministration Console, or the Snapshot Policy Configuration wizard.

See “Configuring a VMware policy from the Policies node” on page 33.

See “Configuring a VMware policy from the Snapshot Policy Configuration wizard”on page 45.

4Chapter

To back up a virtual machine manually from an existing policy

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

The Manual Backup dialog appears.

Back up VMware virtual machinesBacking up virtual machines

52

2 Select the type of schedule for the backup.

3 Select the clients (virtual machines) to back up.

4 Click OK to start the backup.

5 To see the job progress, click Activity Monitor in the NetBackupAdministration Console.

It may take a few moments for the job to appear in the Activity Monitor. Donot start another backup if a job does not immediately appear. If the job doesnot show up after a few moments, close and restart the NetBackupAdministration Console.

Note that your VMware backup request launches more than one job. The firstjob automatically creates and deletes snapshots. This job has a dash (-) in theSchedule column. The second job backs up the virtual machine files from thesnapshot.

Further information on NetBackup policiesFor further information on policies and backup schedules, see the "Creating backuppolicies" chapter of the NetBackup Administrator's Guide, Volume I.

53Back up VMware virtual machinesFurther information on NetBackup policies

Back up VMware virtual machinesFurther information on NetBackup policies

54

Restore VMware virtualmachines


■ VMware restore procedures: overview

■ Restore notes

■ Restoring individual folders and files

■ Setting up NetBackup Client Service for restore to a shared virtual machinedrive

■ Restoring the full VMware virtual machine

VMware restore procedures: overviewThe following sections describe the VMware restore procedures.

Restore of selected filesThe following restore procedures are supported:

■ One-stage process

Restore selected files to the virtual machine by restoring to the recovery host.The virtual machine drives that are the destination for the restore must beconfigured in one of the following ways:

■ The virtual machine drives must be shared through the guest operatingsystem on the virtual machine.See “Setting up NetBackup Client Service for restore to a shared virtualmachine drive” on page 60.

5Chapter

■ NetBackup client software must be installed on the VMware virtual machine.

■ Two-stage process

■ Restore selected files from the VMware recovery host to a NetBackupWindows client (not to the virtual machine).See the NetBackup Backup, Archive, and Restore Getting Started Guide onhow to restore to different locations.

■ Then manually copy the restored files to the Windows virtual machine.(NetBackup does not perform this step.)

Restore of the virtual machine from vStorage backupsTo restore a virtual machine from a backup that was made with vStorage, use theVirtual Machine Recovery dialogs in the NetBackup Backup, Archive, and Restoreinterface.

See “Restoring the full VMware virtual machine” on page 61.

Restore of the virtual machine from VCB backupsTo restore a virtual machine from a backup that was made with VCB, restore allvirtual machine files to the VMware recovery host. The recovery host is used asa staging machine. You must use this approach if the backup was made byNetBackup 6.5.x.

After you restore the virtual machine files to the VMware recovery host, do oneof the following:

■ Use VMware automated restoreNetBackup integrates with VMware vCenter Converter to restore the virtualmachine to a designated ESX server. The virtual machine files are then removedfrom the staging machine.Certain compatibility issues exist between newer and older versions of VMwareESX server and VMware Converter. Refer to the following Symantec tech notefor more information:http://entsupport.symantec.com/docs/312604

■ Use the VMware Converter application to restore the virtual machine fromthe staging machine to the virtual machine server.

Restore notesBefore you begin the restore, note the following:

Restore VMware virtual machinesRestore notes

56

■ Unless a NetBackup client is installed on the virtual machine, restores mustbe performed from the NetBackup master server.

■ To restore files to the original virtual machine location, the destination mustbe specified as the virtual machine's host name (not display name or UUID).

■ For the SAN transfer type, the job may be slow when you restore to a vCenterServer. For greater speed, designate an ESX server as the destination for therestore.Note that you can set up an ESX server to be used for restores. You can addNetBackup restore credentials specifically for that ESX server, by means ofthe VMware restore ESX server server type.See “Adding NetBackup credentials for VMware” on page 30.

■ If the attempt to restore a full virtual machine fails while using the SANtransport type, try the NBD transport type instead.

■ If the virtual machine was backed up by its display name or UUID, and thedisplay name is not the same as its host name, you must specify the correctdestination client for the restore. Use the Specify NetBackup Machines andPolicy Type dialog in the NetBackup Backup, Archive, and Restore interface.See “Invalid client error when you restore selected files using NetBackup BARinterface installed on the virtual machine” on page 91.

■ For the VMware files that were encrypted on the virtual machine usingWindows NTFS encryption, you must install a NetBackup client on the virtualmachine.

■ For a virtual machine that is running a Linux guest operating system: Whenyou restore a virtual machine (to its original location or different location),the ESX server assigns the virtual machine a new (virtual) MAC address. Afteryou restart the virtual machine, you may have to configure its MAC address.For instance, the original MAC address of the virtual machine may be in aconfiguration file that has to be updated.Refer to your VMware documentation for more details.

■ When restoring large files, make sure that no snapshots are active on thedestination virtual machine. Otherwise, the files are restored to the VMwareconfiguration datastore, which may be too small to contain the files you wantto restore. In that case, the restore fails.The configuration datastore (sometimes called the VMX directory) containsthe configuration files that describe the virtual machine, such as .vmx files.Note that active snapshots of vmdk files are also stored on the configurationdatastore.

■ If you cancel the virtual machine restore before it completes, thenot-fully-restored virtual machine remains at the target location. NetBackup

57Restore VMware virtual machinesRestore notes

does not delete the incomplete virtual machine when the restore job is canceled.You must manually remove the incomplete virtual machine.

If the recovery host is not at the same NetBackup release level as thebackup host

Note the following about mixed-level backups and restores:

■ To restore from a NetBackup 7.0 backupTo restore a virtual machine from a backup that a NetBackup 7.0 backup hostperformed, a NetBackup 7.0 recovery host is required. You cannot use aNetBackup 6.5.x recovery host to restore a virtual machine that was backedup by a NetBackup 7.0 backup host.

■ To restore from a NetBackup 6.5.x backupTo restore a virtual machine (or selected files) from a backup that a NetBackup6.5.x backup host performed, the VMware Converter must be installed on theNetBackup recovery host. The recovery host can run NetBackup 6.5.x or 7.0.A staging area is required.

Restoring individual folders and filesIf the VMware backup was made with either of the following, you can restoreindividual files:

■ An MS-Windows policy.

■ A FlashBackup-Windows policy with a Virtual Machine Backup parameterset to File levelsnapshotusingVCB, MappedfullVMbackup, or Fullbackupwith file level incremental.

To restore individual folders or files

1 In the NetBackup Backup, Archive, and Restore interface, specify the sourceclient and destination client and the type of policy:

For UNIX systems, on the Restore Files tab, click the Restore icon:

For Windows systems, click Files>SpecifyNetBackupMachinesandPolicyType.

2 Specify the following:

Restore VMware virtual machinesRestoring individual folders and files

58

The NetBackup master server that directed the backup.Server to use forbackupandrestores

The VMware virtual machine that was backed up.

Note: If the policy identified the virtual machine by its VMwaredisplay name or UUID (not by host name), specify that displayname or UUID.

Source client forrestores

Specify one of the following:

■ The VMware virtual machine that was originally backedup, if NetBackup client software has been installed on thevirtual machine.

If the policy identified the virtual machine by its VMwaredisplay name or UUID (not by its host name), specify thehost name of the destination machine. Do not specify theVMware display name or UUID.

■ The VMware recovery host.

Note: The NetBackup Client Service must be logged on asAdministrator.

See “Setting up NetBackup Client Service for restore to a sharedvirtual machine drive” on page 60.

Destination clientfor restores

The type of policy that made the backup, either MS-Windowsor FlashBackup-Windows.

Policy type forrestores

3 Select the type of restore, as follows:

■ For UNIX systems, on the Restore Files tab, select Normal Backups.

■ For Windows systems, click Files > Select Files and Folders to Restore >from Normal Backup

4 For UNIX systems enter the Browse directory that contains the folders orfiles to restore.

5 Click the files you want to restore.

6 Start the restore, as follows:

■ On UNIX systems: Click Restore.

■ On Windows systems: Click Actions > Restore....

7 For Windows systems, if NetBackup client software is not installed on thevirtual machine, select one of the following:

■ Restore everything to a different location

59Restore VMware virtual machinesRestoring individual folders and files

■ Restore individual folders and files to different locationsDestinations must be entered as UNC path names that refer to shareddrives on the virtual machine.

For example, to restore the file E:\folder1\file1 on virtual machine vm1,enter the following destination:

\\vm1\e$\folder1\file1

The NetBackup Client Service must be logged on under an account that hasAdministrator privileges.

See “Setting up NetBackup Client Service for restore to a shared virtualmachine drive” on page 60.

Setting up NetBackup Client Service for restore to ashared virtual machine drive

To restore individual files to a Windows virtual machine that has a shared drive,note: the NetBackup Client Service must be logged on under an account that hasAdministrator privileges (not as the Local System account). An account withAdministrator privileges lets NetBackup write to the directories on the virtualmachine to which 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 VMware recovery host, double-click theNetBackup Client Service.

2 Check the Log On tab: if the service is not logged on under an account thathas Administrator privileges, stop the service.

3 Change the logon to the Administrator account, or to an account that hasAdministrator privileges.

The account must have Administrator privileges in the domain in which boththe virtual machine and the VMware backup host reside.

4 Restart the service.

5 Retry the restore.

Restore VMware virtual machinesSetting up NetBackup Client Service for restore to a shared virtual machine drive

60

Restoring the full VMware virtual machineIf the VMware backup was made with both of the following, you can restore theentire virtual machine:

■ A FlashBackup-Windows policy.

■ The Virtual Machine Backup parameter was set to any of the following:

■ Full VM backup

■ Mapped full VM backup

■ Full backupwith file level incremental, and the policy schedule was a fullbackup type.

More detail is available on restore options.See “Recovery options: vStorage vs VCB” on page 48.

To restore the full virtual machine

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

2 Specify the source client and destination client and type of policy:

For UNIX systems, on the Restore Files tab, click the restore icon.

For Windows systems: Click Files>SpecifyNetBackupMachinesandPolicyType.

3 Specify the following:

The NetBackup master server that directed the backupServer to use forbackupandrestores

The VMware virtual machine that was backed upSource client forrestores

The VMware recovery hostDestination clientfor restores

FlashBackup-WindowsPolicy type forrestores

4 Select the type of restore:

For UNIX systems, on the Restore Files tab, select Restore type > VirtualMachine Backups.

For Windows systems, click the down arrow on the Select forRestore option.Select RestorefromVirtualMachineBackup. A restore window displays thebackups available for restore.

61Restore VMware virtual machinesRestoring the full VMware virtual machine

5 Select the virtual machine backup to restore.

For UNIX systems, do the following:

■ On the RestoreFiles tab, specify the Startdate and Enddate within whichto search for the backup. Click either of the calendar options.

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

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

For Windows systems, in the NetBackupHistory pane, click on the VMwarebackup. Then click on the item that is displayed under AllFolders. You cannotselect individual files. You must select the entire virtual machine.

Restore VMware virtual machinesRestoring the full VMware virtual machine

62

6 Select restore options.

For UNIX systems, click Restore.

For Windows systems, click Actions > Restore.

The type of dialog that appears next depends on how NetBackup performedthe backup (by means of VCB or vStorage).

See “ Restore Marked Files dialog box (VMware)” on page 63.

See “ Virtual Machine Recovery dialog boxes (restore to original location)”on page 66.

See “Virtual Machine Recovery dialogs boxes (restore to alternate location)”on page 69.

Restore Marked Files dialog box (VMware)If NetBackup used VMware VCB to back up the virtual machine, the RestoreMarked Files dialog appears when you click Restore.


The Restore Options are as follows:

■ Restore all virtual machine files to a virtual machine server automaticallyusing VMware ConverterRestores all virtual machine files to the staging machine that you specify onthis dialog box. NetBackup then issues a VMware-provided script to restorethe virtual machine to the virtual machine server you specify. After the restoreis complete, the restored virtual machine is powered off. The virtual machinefiles are then removed from the staging machine.If the virtual machine display name already exists on the Virtual machineserver, the restore fails.Note the following options:


64

Retains the UUID of the original virtual machine (note that theUUID is a globally unique identifier). The virtual machine isrestored with the same UUID that it had before the restore. Thisoption requires that the previous virtual machine (the one thatwas backed up) has been deleted, so that the UUID is free.

Note: If the UUID exists, the restore fails.

The default (no identify restore) makes sure that the displayname of the new virtual machine (created by the restore) doesnot already exist. The virtual machine that the restore createsis given a new UUID.

Perform identityrestore to restoreUUID (UniversalUnique Identifier)

Verifies that the virtual machine that the restore creates doesnot have the same IP address as the virtual machine that wasbacked up. The network information is deleted at the time ofthe restore.

The default is to retain the IP information. Use the default if:

■ You have already deleted the virtual machine that was backedup

■ And you want the virtual machine created by the restore tokeep the same IP information as the original machine.

Strip networkinformation fromthe virtual machinethat has beenrestored

Does not restore hardware backing information from the originalimage. Default settings are substituted.

Remove backinginformation fordevices likeDVD/CD-ROMdrives, serial orparallel ports

■ Restore all virtual machine files to the staging machineRestores all virtual machine files to the staging machine. NetBackup does notrestore the files to the virtual machine server. If you are not restoring to theoriginal location, you can use the VMware Converter application to restorethe entire virtual machine from the staging machine to the Virtual machineserver.See your VMware documentation.

The Restore Destination Choices are as follows:

■ Virtual machine serverBy default, this field shows the server that was stored in the backup imageinformation. You can use that server as the restore destination, or enter adifferent virtual machine server as the destination.

■ Staging machine for restoration


Select or enter the VMware recovery host to which the VMware files aretemporarily restored. If you chose RestoreallvirtualmachinefilestoavirtualmachineserverautomaticallyusingVMwareConverter, the files are restoredto the Virtual machine server and deleted from this staging server.The default is the backup host that was used for the backup. The name of thatbackup host is stored in the backup image information. On this dialog box, thepull-down list for staging machines includes the VMware backup hosts thatare defined in existing NetBackup policies.Restore staging locationEnter a Windows file path on the staging machine to which the virtual machinefiles are temporarily restored. The default is the VMware backup host mountpoint that was stored in the backup image information.

The Override default priority options are the following:

■ Override default priorityPlace a check mark in this box to override the default priority.

■ Job prioritySet the priority.

Virtual Machine Recovery dialog boxes (restore to original location)If NetBackup used VMware vStorage to back up the virtual machine, the VirtualMachine Recovery dialog boxes appear when you start the restore.

Recovery Destination dialog boxSelect the type of destination for the recovery: the original location or alternatelocation.

■ Original settings of the virtual machine when it was backed upShows the configuration of the virtual machine at the time of the backup.When you restore the virtual machine to its original location, theseconfiguration settings are used and cannot be changed.

■ Recover virtual machine toSelect Original location or Alternate location.

Recovery Options dialog boxSelect the recovery host, transfer type, and other options, as follows:

■ Destination settings of the virtual machine to be recoveredShows the configuration of the virtual machine at the time of backup. Thesesettings are applied to the virtual machine when it is restored.


66

■ NetBackup Recovery HostThe host that performs the recovery. The default is the first host in the list ofbackup hosts that NetBackup has credentials to access.It is usually best to select the host that performed the backup. Selecting adifferent host as the recovery host could result in a slow restore or a failedrestore, depending on the selected transfer type. For example, if the host thatperformed the backup used a SAN connection to access the datastore, but thehost you select as recovery host does not have SAN access to the datastore,the restore fails if you select the san transfer type.

■ Transfer TypeDetermines how the restore data is sent from the VMware recovery host tothe VMware datastore. The appropriate option depends in part on the type ofnetwork that connects the VMware datastore to the VMware recovery host.The default type is the one that was used for the backup.

For unencrypted transfer over Fibre Channel (SAN) or iSCSI.san

For unencrypted transfer over a local network that uses theNetwork Block Device (NBD) driver protocol. This type oftransfer is usually slower than Fibre Channel.

nbd

Provides transfer flexibility if the VMware datastore isavailable on both a SAN and a local network. NetBackupattempts an unencrypted transfer over Fibre Channel (SAN)or iSCSI. If that fails, it transfers the snapshot data usingthe Network Block Device (NBD) driver protocol over thelocal network.

Try san then nbd

Requires that the VMware recovery host is in a virtualmachine. This feature requires ESX 3.5 Update2 or later.

For instructions on this transport mode and on installingthe recovery host in a VMware virtual machine, refer to yourVMware documentation.

hotadd

Provides the most transfer flexibility. NetBackup tries eachtransfer type and uses the first type that succeeds.

Try all types

■ Overwrite the existing virtual machineIf a virtual machine with the same UUID or display name exists at thedestination, that virtual machine must be deleted before the restore begins.Otherwise, the restore fails. Select this option to have the virtual machinedeleted.

■ Restore UUID


Retains the UUID of the original virtual machine (note that the UUID is aglobally unique identifier). The virtual machine is restored with the same UUIDthat it had before the restore.This option requires that the virtual machine has been deleted on thedestination server, so that the UUID is free. Otherwise, you must selectOverwrite the existing virtual machine.

Note the following:

■ If a virtual machine with the same display name but with a different UUIDexists at the target restore location, the restore fails. You must either deletethe existing virtual machine and then run the restore, or keep the existingmachine and abandon the attempt to restore.

■ If a virtual machine with a different display name but with the same UUIDexists at the target restore location: You must either delete the existingvirtual machine and run the restore, or select RestoreUUID and Overwritethe existing virtual machine. In the latter case, NetBackup deletes theexisting virtual machine and restores the original virtual machine.

■ In general, if the attempt to restore the virtual machine to its originallocation results in a conflict with an existing virtual machine, and you donot want to keep the existing virtual machine, you can do one of thefollowing: Either remove the existing virtual machine, or log into the ESXserver and remove the directory where the virtual machine resides.

■ Remove network interfacesRemoves any network interfaces from the restored virtual machine. Selectthis option if the network connections on the destination machine have changedsince the backup was made.

■ Power on virtual machine after recoverySelect this option to have the recovered virtual machine automatically poweredon when the recovery is complete.

■ Override default job priorityPlace a check mark in this box to override the default priority.

■ Job PrioritySet the priority.

Perform Recovery dialog boxReview the settings that will be applied to the restored virtual machine.

■ Recovery settingsLists several settings that are used for the recovery.

■ Run Pre-Recovery Check


68

Click this option to verify credentials, available space on the datastore, andother important requirements.

■ Start RecoveryStarts the recovery of the virtual machine.

Virtual Machine Recovery dialogs boxes (restore to alternate location)If NetBackup used vStorage to back up the virtual machine, the Virtual MachineRecovery dialog boxes appear when you start the restore.

Recovery Destination dialog box (restore to alternate location)■ Original settings of the virtual machine when it was backed up

Shows the configuration of the virtual machine at the time of the backup.When restoring to an alternate location (not to the original location), you canchange these settings after you click Next.

■ Recover virtual machine toSelect Alternate location.

Recovery Options dialog box (restore to alternate location)This dialog initially displays the original virtual machine settings that wererecorded in the NetBackup catalog when the virtual machine was backed up. Beforeaccepting any default values, you may have to verify that the original hosts orservers are still available.

This dialog contains the following fields:

■ NetBackup Recovery HostThe recovery host transfers the virtual machine files to the VMware destinationthat is specified in other fields on this dialog. The default for the recovery hostis the original backup host that backed up the virtual machine.

Consider the following when selecting a recovery host:

■ To use the original VMware backup host for the recovery, verify that thebackup host still exists. The original backup host may have been removedor reconfigured after the backup occurred.

■ The current processing load on the host that you want to use may be afactor. The recovery host undergoes significant I/O activity when it restoresa virtual machine.

■ The network connection between the recovery host and the destinationdatastore may limit the type and speed of data transmission. For example,


to use the SAN transfer type, the recovery host must have access to theappropriate luns in the datastore.

■ vCenter ServerSpecifies the vCenter server for the restored virtual machine. To use theoriginal vCenter Server (the default), verify that the original vCenter serverstill exists.To use an older VirtualCenter Server, make sure that it is compatible with thevirtual machine you want to restore. Note that a vmx-07 virtual machine canbe restored only to a vSphere 4.0 server.To restore directly to an ESX server, select None. None is available only ifNetBackup credentials have been configured for at least one ESX server.See “Adding NetBackup credentials for VMware” on page 30.

■ ESX ServerSpecifies the ESX server for the restored virtual machine. To use the originalESX server (the default), verify that the original ESX server still exists.Click the Search option to browse for a different ESX server.See “Select ESX server dialog box (restore to alternate location)” on page 71.

■ DatacenterShows the VMware datacenter containing the selected ESX server.

■ FolderThis option applies only when you restore through a vCenter server. Thisoption is disabled when you restore directly to an ESX server.By default, this field shows the folder that contained the virtual machine whenthe virtual machine was backed up. If you select a different ESX server to whichto restore the virtual machine, this field changes to None. You must then clickBrowse to select a folder within the datacenter for the restored virtual machine.See “Select Folder dialog box (restore to alternate location)” on page 72.

■ Display NameSpecifies the VMware display name for the restored virtual machine. Thedefault is the display name that the virtual machine had when it was backedup.The display name must be unique for the vCenter Server where the virtualmachine is restored.

Note: If a virtual machine with this display name already exists at this location(or at the original location), you are prompted to click Overwrite the existingvirtual machine. You cannot restore the virtual machine if the result will betwo virtual machines with the same display name on the same vCenter server.


70

■ Resource PoolUse this option to have the restored virtual machine assigned to a resourcepool. Resource pools manage the host's CPU and memory.

■ DatastoreSpecifies the VMware configuration datastore where the virtual machineconfiguration files are stored.The configuration datastore (sometimes called the VMX directory) containsthe configuration files that describe the virtual machine, such as .vmx files.Active snapshots of vmdk files are also stored on the configuration datastore.

■ Transfer TypeDetermines how the data is sent from the VMware recovery host to the VMwaredatastore. The appropriate type depends on the type of connection betweenthe NetBackup recovery host and the VMware datastore.More information is available about these options.See “Recovery Options dialog box” on page 66.

■ Overwrite the existing virtual machineSelect this option to overwrite an existing virtual machine (at the restoredestination or the original location) that has the same display name or UUIDof the virtual machine to be restored.If a virtual machine with the same display name or UUID exists at thedestination vCenter, that virtual machine must be deleted before the restorebegins.

Select ESX server dialog box (restore to alternate location)You can enter the name of the ESX server, or drill down in the list to select aserver.

■ Specify ESX serverEnter the fully qualified name of the ESX server in this field.

■ SearchClick Search to display a list of available ESX servers that are on the vCenterserver. Drill into the list and place a check mark beside an ESX server.

Note: Some older ESX servers may not support the version of the virtualmachine that you want to restore. Verify that the ESX server is compatiblewith the virtual machine.


Select Folder dialog box (restore to alternate location)This dialog shows the folders that exist on the datacenter that is shown in theDatacenter field.

Pick a folder from the list of available folders. The restored virtual machine isplaced in this folder.

If two datacenters of the same name exist in the vCenter server, all folders for theidentically named datacenters are displayed. After you select a folder and clickOK, verify that the Folder path shown on the Recovery Options dialog indicatesa folder on the datacenter that contains the destination ESX server. If the selectedfolder is on the wrong datacenter, the restore fails.

Storage Destination dialog box (restore to alternate location)Select the datastores where the .vmdk files are to be restored.

■ Source VMDK File NameShows the names of the virtual machine .vmdk files that were backed up.

■ DatastoreShows the VMware datastore where the .vmdk files are restored. Click in thisfield for a pull-down to select another datastore available to the ESX server.

■ Datastore StatusIndicates whether the datastore has enough space to contain the selected.vmdk file.

The datastore has enough space to contain the selected.vmdk file of the virtual machine that you restore.

OK

The datastore does not have enough space to contain theselected .vmdk file of the virtual machine that you restore.

Insufficient space

Network Connections and other options dialog box (restore toalternate location)■ Select/unselect all network names

This box selects or unselects all the networks that are listed under NetworkNames. If a network is selected, the restored virtual machine is automaticallyconnected to that network.Place a check mark in this box if you want to select all network connectionsfor the restored virtual machine.


72

■ Network NamesSelect particular networks that you want the restored virtual machine to beconnected to.Note: When the virtual machine is backed up, its network connections arerecorded in the NetBackup catalog.

For the restore, NetBackup determines what networks currently exist, andlists network names as follows:

■ If a network that was recorded in the backup catalog for the virtual machinestill exists, it is listed on this screen and automatically selected.

■ If a network is available that was not listed in the NetBackup catalog, it islisted on this screen but not selected.

■ If a network was recorded in the backup catalog but is not currentlyavailable, it is not listed.

■ Power on virtual machine after recoveryTurns on the virtual machine after it is restored.

■ Override default job priorityPlace a check mark in this box to override the default priority.

■ Job PrioritySet the priority.

Perform Recovery dialog box (restore to alternate location)■ Recovery settings

Lists the settings that are used for the recovery.

■ Run Pre-Recovery CheckVerifies credentials, determines whether the datastore has available space,and reviews other important requirements. You must run this check at leastonce. You can proceed with the restore even if the check fails.

■ Start RecoveryStarts the recovery of the virtual machine.



74

Best practices and moreinformation


■ Best practices

■ More information on VMware

■ Further assistance with NetBackup

■ Support information on NetBackup for VMware

Best practicesThe following are best practices for VMware:

■ For a more efficient backup, the NetBackup media server and the VMwarebackup host should be installed on the same host.

■ When creating virtual machines, use the same name for both host name anddisplay name. If the policy's Client Name Selection is changed, the existingentries on the policy Clients tab still work.

■ VMware recommends that you run no more than four simultaneous backupsof virtual machines that reside on the same datastore.

■ Successful VMware snapshots depend on the following:

■ The amount of I/O that occurs on the virtual machine datastore. Backupsshould be scheduled when relatively little I/O activity is expected. Reducingthe number of simultaneous backups can also help. (Use the Limit jobsperpolicy attribute in the NetBackup policy.)

6Chapter

■ The design of the I/O substructure that is associated with each virtualmachine datastore. For correct I/O design and implementation, consultyour VMware documentation.

■ Include in a single NetBackup policy those virtual machines that use the samedatastore. This practice lets you control the amount of backup-related I/O thatoccurs per datastore, to limit the backup effect on the target virtual machines.

■ NetBackup supports multiple backup hosts. When a single backup host issaturated with a backup process, another backup host can be added to increasebackup throughput.

■ Upgrade to the latest version of VMware vSphere or Virtual Infrastructure.

■ See the Symantec white paper titled NetBackup for VMware Best PracticesGuide.

For VCB backupsWhen backing up virtual machines with VCB, note the following regarding thesnapshot mount point on the VMware backup host (formerly called backup proxy):

■ On the backup host, the file system that contains the snapshot mount pointundergoes extensive I/O during full virtual machine backup. For this reason,the file system should reside on a high performance device.

■ On the backup host, the file system that contains the snapshot mount pointshould be reserved for snapshots only. It should also be on a dedicated SCSIor Fibre Channel bus.

■ The file system that contains the snapshot mount point should be routinelydefragmented. A heavily fragmented file system can adversely affect backupperformance.

■ To increase backup throughput on the backup host, define multiple snapshotmount points. Each mount point should be created on a disk that is connectedon its own disk bus (such as SCSI or IDE). Thus, I/O activity that one policycreates can be isolated from I/O activity that other policies create.

VMware with deduplicationFor a VMware backup to a deduplication storage unit, select the Mapped fullVMbackup option for the Virtualmachinebackup parameter on the VMware snapshotmethod. This option provides the best deduplication rates. Use of the Full VMbackup option results in a lower rate of deduplication.

More information is available about VMware configuration parameters.


Best practices and more informationBest practices

76

More information on VMwareVMware Inc. provides an extensive set of manuals on VMware products.

http://www.vmware.com/support/pubs/

Further assistance with NetBackupFor assistance with Snapshot Client configuration, refer to the NetBackup 7.0Snapshot Client Administrator's Guide. The guide contains installation andconfiguration instructions on Snapshot Client.

For a list of all supported combinations of platforms and snapshot methods, seethe NetBackup 7.x Snapshot Client Compatibility document:

http://entsupport.symantec.com/docs/337052

Support information on NetBackup for VMwareUp-to-date information on NetBackup support in a virtual environment is availablein the following tech note:

Support for NetBackup in a virtual environment


This tech note provides a wide range of support information, such as a list ofsupported guest operating systems, file systems, and required VMwarecomponents.

77Best practices and more informationMore information on VMware

Best practices and more informationSupport information on NetBackup for VMware

78

Troubleshooting


■ NetBackup logging for VMware

■ VMware environment—important!

■ Changing the browsing timeout for virtual machine discovery

■ Changing timeout and logging values for vSphere

■ Notes and tips

■ Backup and restore problems

NetBackup logging for VMwareFor log messages about VMware backup or restore, see the following NetBackuplog folders.

Table 7-1 NetBackup logs that pertain to VMware backup and restore

Resides onContainsmessageson

Log folder

NetBackup master ormedia server

Backup and restoreinstall_path\NetBackup\logs\bpbrm

NetBackup mediaserver

Backup and restoreinstall_path\NetBackup\logs\bptm

VMware backup hostSnapshot creationand backup

install_path\NetBackup\logs\bpfis

VMware backup hostSnapshot creationand backup

install_path\NetBackup\logs\bpcd

7Chapter

Table 7-1 NetBackup logs that pertain to VMware backup and restore(continued)

Resides onContainsmessageson

Log folder

VMware backup hostBackupinstall_path\NetBackup\logs\bpbkar

NetBackup masterserver

Restoreinstall_path\NetBackup\logs\bprd

VMware recoveryhost

Restoreinstall_path\NetBackup\logs\tar

VMware backup orrecovery host

Policy configurationand on restore

install_path\NetBackup\logs\bpVMutil

The client where theBackup, Archive, andRestore interface isrunning.

Restoreinstall_path\NetBackup\logs\bpVMreq

VMware backup hostPolicy 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 backup host:

Windows:

install_path\NetBackup\logs\mklogdir.bat

UNIX (on master or media servers):

/opt/openv/netbackup/logs/mklogdir

More detail is available on snapshot logs and logging levels.

See the NetBackup 7.0 Snapshot Client Administrator’s Guide.

A broader discussion of NetBackup logging is available.

See the NetBackup Troubleshooting Guide.

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

TroubleshootingNetBackup logging for VMware

80

Table 7-2 Other logs for VMware

Resides onContains messages onLog folder

VMware backup host

See “Enabling VxMS logging”on page 81.

Note: The use of VxMSlogging can reduce theperformance of the backuphost.

File mapping during backup\Program Files\CommonFiles\VERITAS\VxMS\Logs

Enabling VxMS loggingVxMS logging may require significant resources on the VMware backup host.

To enable VxMS logging

1 On the Windows desktop of the backup host, click Start > Run and enterregedit.

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.

4 Change the Logging DWORD value.

For example: Useful logging levels (in decimal) are 3400 for low and 7400 forhigh.

VMware environment—important!Unsupported equipment can cause many problems. Ensure that your VMwareenvironment (including ESX servers, SAN devices, and backup host) conforms toall requirements and recommendations that are spelled out by VMware. Forinstance, if VMware does not support your HBAs, device drivers, or guest operatingsystems, NetBackup cannot work.

For support details, see VMware documentation at the VMware support site (forexample, the VMware compatibility guides).

81TroubleshootingVMware environment—important!

Changing the browsing timeout for virtual machinediscovery

In the NetBackup Administration Console on Windows, you can adjust the timeavailable for browsing for virtual machines in the NetBackup policy.

To change the browsing timeout value

1 In the NetBackup Administration Console on Windows, click on the Policiesnode.

2 From the main menu, click View > Options, then click the Policies tab.

3 Adjust the VMware connect timeout value.

4 Click OK.

Changing timeout and logging values for vSphereThe following are vSphere registry keys and their default values for varioustimeouts.

Table 7-3 Registry keys and defaults for vSphere timeouts

Default value (in seconds)DWORD registry key name

900jobtimeout

900poweroptimeout

900snapshottimeout

180registertimeout

180renametimeout

180browsetimeout

300connecttimeout

The registry key and default for the vSphere API logging level are the following.

Table 7-4 Registry key and default for vSphere API logging level

Default valueDWORD registry key name

0 (no logging)vmcloglevel

TroubleshootingChanging the browsing timeout for virtual machine discovery

82

To change vSphere timeouts and logging values

1 On the Windows desktop of the backup host, click Start > Run and enterregedit.

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

3 Go to HKEY_LOCAL_MACHINE > SOFTWARE > VERITAS > NETBACKUP> CURRENTVERSION > CONFIG and create a key called BACKUP.

4 To change a timeout value, create a new DWORD under BACKUP, using theappropriate registry name (such as jobtimeout or poweroptimeout).

Enter a value for the timeout.

5 To change the level of vSphere API logging, create a new DWORD calledvmcloglevel and enter the new logging value.

The allowed values are 0 through 6, where 0 is no logging and 6 is the highestlogging level.

Notes and tipsNote the following:

■ For incremental backups, make sure the VMware backup host is correctlyconfigured. Otherwise, NetBackup performs only full backups.See “Incremental backups must be based on timestamps ” on page 33.

■ You cannot restore Windows operating system files from a file-level backupof a virtual machine. You can restore standard data files only. A restore of theoperating system requires a full virtual machine backup.

■ Make sure the VMware Tools are installed on each virtual machine. Otherwise,communication problems and other problems can result.

■ You cannot restore individual VMware files onto the virtual machine itself,except under certain conditions.See “VMware restore procedures: overview” on page 55.

■ (For VCB backups only.) For the Full VM backup, Mapped full VM backup, orFull backup with file level incremental options: Backups are not supported ifthe snapshot staging area in the VMware backup host has compression orencryption enabled.See “Other backup failures” on page 85.

■ For VMware environments that require VCB: Make sure that you have thelatest VCB version on the VMware backup host.See “When is VCB required?” on page 13.

83TroubleshootingNotes and tips

■ NetBackup for VMware does not work with the VMware NetBackup IntegrationModule (VNIM).

Note the following:

■ If VNIM is installed, do not configure a NetBackup for VMware policy (withthe VMware snapshot method) to call any scripts that use VNIM. Such apolicy results in a backup that fails.

■ Do not run any NetBackup for VMware policy at the same time as ascript-based policy that calls VNIM. If the two policies require access tothe same virtual machine, a conflict may result and the backup may fail.

Backup and restore problemsThis section describes the backup and restore problems that may occur withNetBackup for VMware.

Credentials for VMware server are not validA number of possible problems can prevent NetBackup from gaining access tothe ESX server or VirtualCenter. NetBackup’s AddVirtualMachineServer dialoghas a Validate Credentials box that directs NetBackup to verify the credentialswhen you click OK. If the credentials do not pass validation, a pop-up messageappears.

Problems can result for a variety of reasons, including the following:

■ An incorrect virtual machine server name. Make sure that the server name isentered correctly.More information is available about changing the server name that is storedin NetBackup.See “Changing the host name of a VMware server in NetBackup” on page 32.

■ An invalid user name or password. Make sure that a valid user name andpassword were entered correctly.

■ VCB only: An incorrect port number. Make sure that the port number is correct,or you can uncheck the Connect using port number box. In most cases, noport specification is required. For VCB backups, VCB software determines theport.

NetBackup cannot obtain the volume ID of a driveNetBackup may not be able to obtain the volume ID of a drive that is listed in thepolicy’s backup selections. In that case, none of the drives that are listed in the

TroubleshootingBackup and restore problems

84

policy for the client are backed up. The backup fails with NetBackup status code156.

Try one of the following:

■ Use the ALL_LOCAL_DRIVES directive instead of listing individual drives.

■ A drive letter that is specified in the policy’s backup selections list may beincorrect, or the drive may be down. Update the client’s include list (Exceptionsto exclude list), and fix or remove the drive entry in the backup selections list.

Other backup failuresOther backup failures can occur for several reasons:

■ You cannot run more than one backup per virtual machine at a time. If youstart a second backup of the same virtual machine while the first backup isactive, the second job fails with a status 156.

■ VCB only: If the VMware backup host has insufficient space in which to mounta snapshot of the virtual machine, the backup fails with status 156.The bpfis log on the VMware backup host may contain a message such as thefollowing:

13:35:37.859 [5536.1276] <2> onlfi_vfms_logf: [2007-09-21

13:35:34.578 'vcbMounter' 2204 error] Error: Failed to export

the disk: There is not enough space on the disk

Free up additional space on the backup host and rerun the backup.

■ If the VMware backup host cannot access the VMware datastore by means ofthe transfer type that was selected for the job, the backup fails.Select a different transfer type and retry the backup.

The final status code for the failure depends on whether the backup uses VCBor vStorage, as follows.

■ For VCB backups: The backup fails with status 156 and the bpfis log on thebackup host may contain messages such as the following:

12:23:29.998 [3892.3332] <2> onlfi_vfms_logf: [2008-05-07

12:23:26.279 'App' 3668 trivia] Attempting to open

LVID:46a9ed36-ca235c12-1236-00001a1a24e4/46a9ed35-aa804fd4-6b99

-00001a1a24e4/1.

12:23:29.998 [3892.3332] <2> onlfi_vfms_logf: [2008-05-07

12:23:26.279 'App' 3668 error] No path to device

LVID:46a9ed36-ca235c12-1236-00001a1a24e4/46a9ed35-aa804fd4-6b99

-00001a1a24e4/1 found.

85TroubleshootingBackup and restore problems

■ For vStorage backups: The backup fails with status 6 and the job detailedstatus log on the backup host may contain messages such as the following:

12/4/2009 1:12:34 PM - Error bpbrm(pid=21376) from

client moneevm4_clone: ERR - Error opening the snapshot

disks using given transport mode: Status 23.

12/4/2009 1:12:39 PM - Error bpbrm(pid=21376) could not

send server status message

12/4/2009 1:12:40 PM - end writing; write time: 00:00:28

the backup failed to back up the requested files(6)

■ NetBackup cannot find the host name or VMware display name of a virtualmachine that is listed in the backup policy. The detailed status log may includethe following error message:

Critical bpbrm (pid=<pid number>) from client <client name>:

FTL - snapshot creation failed, status 156.)

If the virtual machines do not have static IP addresses, you may have toconfigure NetBackup to identify virtual machines by their VMware displaynames or UUIDs. Examples of the environments that do not use static IPaddresses are clusters, and the networks that assign IP addresses dynamically.Note that NetBackup may have been configured to identify virtual machinesby their VMware display names. In that case, make sure that the display namesare unique and that they do not contain spaces or special characters.See “Client name selection” on page 37.

■ For versions of VCB earlier than 1.5: A disk was mounted on a virtual machinebut the disk is assigned to the virtual machine in raw mode (RDM). As a result,the attempt to create a snapshot of the virtual machine fails.The bpfis log on the backup host may contain a message such as the following:

12:46:27.175 [2636.5628] <2> onlfi_vfms_logf: [2007-10-17

12:46:27.019 'App'

1976 verbose] Fault Msg: "Virtual machine is configured to use a

device that prevents the snapshot operation: Device '' is a raw

disk, which is not supported."

For VCB 1.5 and for vStorage, the RDM is ignored (not backed up) and anyindependent disk is recreated but empty.See “Configurations for backing up RDMs” on page 94.

■ For the Full VM backup, Mapped full VM backup, or Full backup with file levelincremental options: Backups are not supported if the snapshot staging areain the VMware backup host has compression or encryption enabled.


86

■ For the Full VM backup, Mapped full VM backup, or Full backup with file levelincremental options: Backups are not supported if the snapshot mount pointon the VMware backup host has compression or encryption enabled. For thebackup, the VMware backup host copies the space-optimized VMware virtualmachine images to its snapshot mount point. The Windows NTFS file systemthat is allocated for the snapshot mount point should not have the Compressionor Encryption attribute set. If either attribute is set, backups succeed but singlefile restores cannot be performed from the backups.

■ The attempt to create a VMware snapshot of the virtual machine exceeds theVMware timeout of 10 secondsIf the attempt to create a snapshot of the virtual machine exceeds the VMwaretimeout of 10 seconds, the snapshot fails with NetBackup status 156. Thistimeout may occur if the virtual machine is configured with a large numberof volumes. Note that the timeout may be encountered even if the Virtualmachine quiesce option was disabled.

Do one of the following:

■ Reduce the number of volumes within the virtual machine.

■ Install a NetBackup client on the virtual machine and select another backupmethod for the policy (not the VMware snapshot method).

Restore fails when you restore individual files to a virtual machine thathas NetBackup client software

When you restore individual files to a virtual machine that has a NetBackup client,make sure that a firewall does not interfere with the restore. If a firewall stopsthe restore, turn off the firewall and retry the restore.

Backup or restore job hangsNetBackup may have exceeded the maximum number of allowed VMware NFCconnections to the ESX server when it used the transfer types nbd or nbdssl. Notethat NetBackup uses one NFC connection per virtual disk on the ESX or ESXiserver.

If NetBackup is configured to access the ESX server directly (not through a vCenteror VirtualCenter server), the maximum number of allowed connections is smaller.The following are the maximum connections as set by VMware:


Table 7-5 VMware NFC connection limits

Maximum NFCconnections allowed

Type of access to the ESXserver

ESX version

9Directly to ESX serverESX 3.5

27Through vCenterESX 3.5

9Directly to ESX serverESX 4

27Through vCenterESX 4

11Directly to ESX serverESXi 4

23Through vCenterESXi 4

Try a different transport type (such as SAN or hotadd). If a different transporttype is not available and NetBackup accesses the ESX servers directly, set upaccess through a vCenter (or VirtualCenter) server. Use of a server increases themaximum number of allowed connections. For example, a limit of 27 means thatNetBackup can back up or restore a virtual machine that has up to 27 disks, if theESX server is behind a vCenter server.

Note that the connection limits are per-host (that is, per vCenter or ESX server).

For example, assume the following environment:

■ An ESX 4.0 server with three virtual machines.

■ Each virtual machine has ten virtual disks.

■ The virtual machines are behind a vCenter 4.0 server.

For a simultaneous backup of the three virtual machines, NetBackup requires 30NFC connections. With a limit of 27 NFC connections per vCenter server, any ofthe three backup jobs may hang.

These limits are described in the VMware Virtual Disk API Programming Guide:

http://www.vmware.com/support/developer/vddk/vddk11_api_programming.pdf

Mount point missing on a restored Windows virtual machineA Windows virtual machine may fail to write its mount point configuration todisk (the mount point configuration remains in RAM). In that case, the mountpoint information cannot be backed up. When the virtual machine is restored,the data from the mounted volume is restored, but the mount point is absent fromthe restored virtual machine.


88

Reassign the mount point on the restored virtual machine. To make sure themount point is correctly configured, restart the virtual machine.

Problems with transfer typesThis topic describes problems that may arise with the following transfer types:

■ san

■ nbd

■ nbdssl

■ try san then nbd

■ try san then nbdssl

■ hotadd

■ try all types

More information is available on these types.

See “Transfer type” on page 39.

Note the following potential issues:

■ During a backup, VMware creates mount directories in the C:\Windows\Tempfolder. After the backup, VMware automatically removes the mount directories.In some cases, such as when the backup uses the hotadd transfer type,NetBackup may be unable to remove the mount directories.In that case, you must manually remove the mount directories from the \Tempfolder. The folder name contains a string such as VMware-System.

■ If a datastore is out of space when you attempt to delete snapshots, VMwarecreates a snapshot named Consolidate Helper. You must manually delete thissnapshot before the next backup. For more information, see the followingVMware knowledge base article about deleting the Consolidate Helper snapshot:http://kb.vmware.com/kb/1003302

■ Taken together, the virtual machine and the alternate client virtual machinemay contain too many disks. If the total is too great for the alternate client'sSCSI controllers to handle, a backup or restore using hotadd fails with status6. The following message appears in the job detailed status log:

ERR - Error opening the snapshot disks using

given transport mode: Status 23.

Add more SCSI controllers to the alternate client virtual machine.


NetBackup catalog information for virtual machine backups made on6.5.4 or lower may prevent browsing the imported images for restore

If you import a NetBackup 6.5.4 or lower virtual machine backup image to aNetBackup 7.0 system, the catalog header file (non .f file) of the imported imagemay have the wrong value for VM_TYPE. The value of the imported image maybe incorrectly reported as 0 even for type 1 (Full VM) and type 2 (Mapped full VM)backups. As a result, you cannot use the Backup, Archive, and Restore interfaceto browse and restore the virtual machine image.

You must change the VM_TYPE value in the header file of the imported image tocorrect this problem. For backups that were made with the Full VM backup option,set VM_TYPE to 1. For backups that were made with the Mapped full VM backupoption, set VM_TYPE to 2.

For instructions, see the following tech note:

http://seer.entsupport.symantec.com/docs/308841.htm

Restore fails with NetBackup status code 5A virtual machine restore may fail in the following cases:

■ If an .ISO file was presented to a virtual machine as a virtual CD or DVD at thetime of backup, the ISO file must be available on the destination host for therestore. If the ISO file is not available on the host where you restore the virtualmachine, the restore fails. Note that the Virtual Infrastructure interface onthe VirtualCenter may include the following message:

Invalid configuration for Device '1'

■ The VMware restore host is on Windows Server 2008 but the SAN luns areoffline.The detailed status log in the NetBackup Activity Monitor includes the messageVirtual machine restore: file write failed.

If the restore host is on Windows Server 2008 and you use the SAN transfertype, you must manually change the SAN luns to be online.

■ For vStorage restores: If the restore host cannot access the VMware datastoreby means of the transfer type that was selected for the job, the restore fails.The job detailed status log on the VMware restore host may contain messagessuch as the following:

3:26:43 INF - Beginning read-blockmap on server luebeck

of client moneevm4, reading file h:\dstu\moneevm4_1259284475_C1_F1.

13:27:21 (19400.001) INF - TAR STARTED


90

13:27:23 (19400.001) INF - Beginning restore from server luebeck

to client luebeck.

13:27:36 (19400.001) FTL - Virtual machine restore: VxMS initialization

failed

13:27:37 (19400.001) FTL - Virtual machine restore: file create failed

13:28:42 (19400.001) INF - TAR EXITING WITH STATUS = 5

13:28:42 (19400.001) INF - TAR RESTORED 0 OF 1 FILES SUCCESSFULLY

13:28:42 (19400.001) INF - TAR KEPT 0 EXISTING FILES

13:28:42 (19400.001) INF - TAR PARTIALLY RESTORED 0 FILES

13:29:54 (19400.xxx) INF - Status = the restore failed to recover

the requested files.

Select a different transfer type and retry the restore.

Restore of selected files fails with NetBackup status code 227To restore selected files (not the entire virtual machine) to the original location,you must specify the host name of the virtual machine. Do not specify the displayname or UUID as the destination. If you specify the display name or UUID asdestination, the restore fails.

Invalid client error when you restore selected files using NetBackupBAR interface installed on the virtual machine

If the virtual machine was backed up by its display name or UUID, and the displayname is not the same as its host name, note: you cannot restore selected files bymeans of the Backup, Archive, and Restore (BAR) interface if the interface isinstalled on the virtual machine itself. The files can be restored if BAR is installedon the master server or media server. In this case, BAR must not be installed onthe virtual machine that you want to restore to.

To restore files, note that the Destination client for restores field in the BARinterface must have a valid host name or IP address.

VMware virtual machine does not reboot after restoreThe virtual machine may have had SCSI and IDE drives at the time of backup andthe guest OS resided on a SCSI drive. In that case, the virtual machine whenrestored may attempt to boot from the IDE drive. The boot attempt fails with themessage "Operating system not found." This problem occurs when NetBackupuses the VMware vStorage APIs.

VMware has identified this problem and will address it in a future release.


As a workaround, you can reconfigure the BIOS on the virtual machine to bootfrom the correct SCSI device.


92

Backup of VMware rawdevices (RDM)

This appendix includes the following topics:

■ About VMware raw device mapping (RDM)

■ NetBackup support details for RDMs

■ Configurations for backing up RDMs

■ About alternate client backup of RDMs

■ Requirements for alternate client backup of RDMs

■ Configuring alternate client backup of RDMs

About VMware raw device mapping (RDM)VMware raw device mapping mode (RDM) allows a virtual machine to directlyaccess physical disks. With raw device mapping, a VMware virtual machine canuse large storage devices such as disk arrays. Access to the data on an RDM diskis faster than to a fully virtualized disk (vmdk file). An RDM disk can be locallyattached to the ESX server or configured on a Fibre Channel SAN.

NetBackup supports the disk arrays that are configured on a virtual machine asRDMs.

Note: NetBackup cannot back up the RDM by means of a VMware backup host.

AAppendix

NetBackup support details for RDMsFor notes and restrictions on NetBackup support for VMware RDM (such as therequired version of VCB), see the following Symantec tech note:

Support for NetBackup in a virtual environment


Configurations for backing up RDMsYou can use either of the following NetBackup configurations to back up diskarrays as RDMs:

■ Without Snapshot Client: Install a NetBackup client on the virtual machine.You can configure NetBackup to back up the virtual machine and any RDMsas if the client was installed on a physical host. Without Snapshot Clientsoftware on the virtual machine, the features of Snapshot Client are notavailable. (This configuration is not discussed in this NetBackup for VMwareguide.)

■ With Snapshot Client: Install a NetBackup client and Snapshot Client softwareon the virtual machine. Configure an alternate client backup.

About alternate client backup of RDMsBackup of an RDM requires the alternate client off-host backup method that isprovided by NetBackup Snapshot Client.

Alternate client backup of an RDM consists of the following:

■ The RDM disk array contains the data to be backed up. Another host containingNetBackup client software and Snapshot Client software must have access tothe disk array. This host is the alternate client. (In this configuration, thevirtual machine is called the primary client.)

■ A snapshot of the data is created on the disk array and is mounted on thealternate client. The alternate client creates a backup image from the snapshot,using original path names, and streams the image to the NetBackup mediaserver.

■ The alternate client handles the backup I/O processing; the backup has littleor no effect on the virtual machine. The media server reads the snapshot datafrom the alternate client and writes the data to storage.

■ The virtual machine and alternate client must be running the same operatingsystem, volume manager, and file system. For each of these I/O system

Backup of VMware raw devices (RDM)NetBackup support details for RDMs

94

components, the alternate client must be at the same level as the primaryclient, or higher level.For complete requirements on alternate client backup, refer to the Policyconfiguration chapter of theNetBackupSnapshotClientAdministrator'sGuide.

Requirements for alternate client backup of RDMsTo use Snapshot Client to back up an RDM, note the following:

■ RDM devices must be configured in physical compatibility mode. You selectthis mode when you create the RDM. Physical compatibility mode is notconfigured in NetBackup.For an introduction to RDM, refer to your VMware documentation. For example,see the following VMware document:ESX Server 3 Configuration Guide

■ NetBackup may require certain OS and array configuration, depending on theguest OS and the array. For details, see the disk arrays chapter of theNetBackupSnapshot Client Administrator's Guide.

■ NetBackup client software must be installed on the virtual machine.

■ The requirements for the NetBackup for VMware feature (a backup host andthe VMware snapshot method) do not apply to backups of RDM disk arrays.To back up RDM disk arrays, you must configure a Snapshot Client alternateclient backup.

Configuring alternate client backup of RDMsThe following procedure highlights key points in creating an alternate clientbackup of a disk array that is configured as an RDM. For broader details on diskarray configuration, refer to theNetBackupSnapshotClientAdministrator'sGuide.

95Backup of VMware raw devices (RDM)Requirements for alternate client backup of RDMs

To create an alternate client policy for a disk array that is configured as an RDM

1 Select a policy type that is appropriate for the OS of the virtual machine andfor the type of data to back up.

Refer to the Policy configuration chapter of the NetBackup Snapshot ClientAdministrator's Guide.

2 On the policy Attributes tab in the Administration Console, click Performsnapshot backups and Perform off-host backup.

The following is a detail from the Attributes tab.

3 Select Alternate Client from the Use pull-down. In the Machine field, enterthe name of the host that is configured as an off-host backup machine (thealternate client).

Do not select VMware backup host.

4 Click Options.

5 Select a snapshot method.

The VMware method does not apply to alternate client backup and is notavailable in the list.

Select a snapshot method that is appropriate for the volume or array. Forexample:

■ The HP_EVA_Snapclone method or other EVA method for an HP EVAarray.

■ The EMC_CLARiiON_Snapview_Clone or other CLARiiON method for anEMC CLARiiON array.

Backup of VMware raw devices (RDM)Configuring alternate client backup of RDMs

96

■ FlashSnap.For FlashSnap, the following must be installed: VxVM 3.2 or later forUNIX, VxVM 4.0 or later for Linux and AIX, or VxVM 3.1 or later forWindows. Also, volumes must be configured over the primary host’s disks.The VxVM FlashSnap license must also be installed.

■ VSS (for Windows guest operating systems only).

The array may require additional OS and NetBackup configuration asdescribed in the disk arrays chapter of the NetBackup Snapshot ClientAdministrator's Guide. The same guide contains more details on snapshotmethods.

6 If required by an array snapshot method that you selected in the previousstep, specify the Snapshot Resources.

7 In the policy’s Clients list, select the virtual machine on which the array isconfigured as an RDM.

8 In the policy’s Backup Selections list, specify the disk that you want to backup, or the files or volumes that reside on the disk.

97Backup of VMware raw devices (RDM)Configuring alternate client backup of RDMs

Backup of VMware raw devices (RDM)Configuring alternate client backup of RDMs

98

File-level backup ofWindows virtual machines

This appendix includes the following topics:

■ About file-level backup of Windows virtual machines

■ Configuration tasks for file-level backup

■ File-level backup options

■ What can be restored from a file-level backup?

■ Configuring a policy for Windows file-level backup

About file-level backup ofWindows virtual machinesIf you use VMware VCB, you can back up selected Windows files instead of theentire virtual machine. This appendix describes how to configure such a backup.

In most cases, it may be better to schedule full and incremental backups of theentire virtual machine with the NetBackup MappedfullVMbackup option. Froma mapped virtual machine backup, you can restore the virtual machine or selectedfiles. To set up such a policy, see the "Configure NetBackup for VMware" chapterin this guide.

To back up selected files from a Windows virtual machine, you can use either ofthese approaches:

■ Install the NetBackup client software in the virtual machine. NetBackupconducts the backup as though the client is installed in an ordinary physicalhost. Most features that NetBackup supports on physical hosts are alsosupported when the client is installed on the virtual machine. (Thisconfiguration is not described in this appendix or in this guide.)

BAppendix

For further support details on this configuration, see "General NetBackupsupport in a virtual environment" in the Symantec tech note titled Supportfor NetBackup in a virtual environment:http://entsupport.symantec.com/docs/312604

■ Set up a backup host that includes VCB and a NetBackup client. This appendixdescribes how to configure this kind of backup.

Note:The file-level backup capability described in this appendix requires VMwareVCB. VCB has been replaced by VMware vStorage APIs for Data Protection. Notethat VMware intends to phase out support for VCB.

Configuration tasks for file-level backupThe following table summarizes the tasks for setting up file-level backup.

Table B-1 Configuration tasks for file-level backup

TasksSequence

Install VMware components.

See “VMware tasks” on page 17.

Phase 1

Install the NetBackup 7.0 master server and media server.

See the NetBackup 7.0 Installation Guide.

Symantec recommends that the NetBackup media server and the VMwarebackup host be installed on the same host.

Phase 2

Install the NetBackup 7.0 Enterprise Client license on the master server,and install NetBackup client 7.0 software on the VMware backup host.

Phase 3

Add the VMware backup host to your NetBackup configuration.

See “Adding the VMware backup host to NetBackup configuration”on page 30.

Phase 4

Set NetBackup access credentials for the VMware vCenter or VirtualCenter(if any), or for VMware ESX servers.


Phase 5

Configure incremental backups for VMware.

See “Incremental backups must be based on timestamps ” on page 33.

Phase 6

File-level backup of Windows virtual machinesConfiguration tasks for file-level backup

100

Table B-1 Configuration tasks for file-level backup (continued)

TasksSequence

Create a NetBackup policy.

See “Configuring a policy for Windows file-level backup” on page 102.

Phase 7

File-level backup optionsTable B-2 describes the backup and recovery options for file-level backup.

Table B-2 Backup options for file-level backups (MS-Windows policies)

What can be restoredWhat is backed upVirtual machinebackupparameter

Backup Selectionsentry

Individual folders and filesSpecified folders and files only,excluding Windows system files


Individual folders andfiles

Individual folders and filesAll data files and folders inspecified drives, excludingWindows system files


Individual drives

For example: E:\

Individual folders and filesAll data files and folders on alllocal virtual machine drives,excluding Windows system files


ALL_LOCAL_DRIVES

directive

What can be restored from a file-level backup?You can use file-level backup to back up ordinary files and folders on the virtualmachine. The backed up files and folders can be individually restored.

Important note: File-level backup does not support restore of the following:

■ The VMware virtual disk files that define the virtual machine.

■ Windows system protected files (System State).

■ Windows system directories such as the following:

C:\WINDOWS\system

C:\WINDOWS\system32

■ Windows system database files (such as RSM Database and Terminal ServicesDatabase)

101File-level backup of Windows virtual machinesFile-level backup options

To back up the virtual disk files and operating system files, use theFlashBackup-Windows policy type and the Full VM backup or Mapped full VMbackup options as described in another chapter of this guide.


Configuring a policy for Windows file-level backupUse the following procedure to make file-based backups of Windows drives, folders,or files. Requires VCB software on the VMware backup host.

To configure a policy for file-level backup

1 In the NetBackup Administration console, create a new policy.

2 For the policy type, select MS-Windows.

3 Select a policy storage unit or storage unit group.

4 Select Perform snapshot backups.

5 Select Perform off-host backup.

6 From the pull-down list for the Use field, select VMware backup host.

7 In the Machine field, specify the name of the VMware backup host.

If the backup host does not appear in the Machine pull-down list, make surethat it was added to the Host Properties setting.

See “Adding the VMware backup host to NetBackup configuration” on page 30.

You may have to close and reopen the policy for the VMware backup host toappear in the list.

8 Click Options.

Select the following:

■ For the Virtual machine backup option, select File level snapshot usingVCB.

■ For the Snapshot mount point (VCB only) option, specify a folder on theVMware backup host. For example:G:\mnt

The VMware backup host mounts snapshots of individual virtual diskvolumes in this folder. The snapshots are links to the virtual machinedatastore. No virtual machine data is copied to this folder.

More information is available about the other configuration parameters.


File-level backup of Windows virtual machinesConfiguring a policy for Windows file-level backup

102

9 To save these settings, click OK and then Apply.

10 Use the Schedules tab to define a schedule.

Both full and incremental backups are supported.

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

You can type the host name in the EntertheVMwarehostname field, or clickBrowse and select virtual machines.

See “Browse for VMware Virtual Machines screen” on page 42.

12 Use the Backup Selections tab to specify the files to back up.

Click New. You can make entries manually, or click on the pull-down (UNIX)or hand icon (Windows) to select from available directives.

For VMware snapshot backup, the System_State directive (Windows 2000)and the ShadowCopy Componentsdirective (Windows 2003) are not supported.

Enter any of the following and then click Add (on UNIX) or press Enter(Windows):

■ Individual folders and files.

■ Individual drive letters.Enter the drive letter as follows (for example):

E:\

The drive letter must not be a network (shared) drive: It must specify adrive on the virtual machine.

■ The ALL_LOCAL_DRIVES directive.

This directive backs up the data files on all local drives on the virtualmachines that are selected on the Clients tab.

File-level backup as described in this procedure cannot back up the following:

■ Windows System State

■ Windows system files (such as on C:)

■ VMware virtual disk files

A procedure is available for backing up these files.


13 If you click Apply or OK on the policy Attributes tab, a validation processchecks the policy and reports any errors.

If you click Close, no validation is performed.

103File-level backup of Windows virtual machinesConfiguring a policy for Windows file-level backup

File-level backup of Windows virtual machinesConfiguring a policy for Windows file-level backup

104

Symbols156 (status code) 85227 (status code) 915 (status code) 906 (status code) 86, 89

AALL_LOCAL_DRIVES 36, 85alternate client backup

configure for RDM 95of RDM 94

alternate location for restore 69archive bit 33

Bbackup

environment diagrams 15file-level 99host 14

adding to configuration 30how to enter in policy 34

how to configure 33how to perform 51job hangs 87off-host

configuration 34options compared 46process overview 16reduce size of 47throughput 76troubleshooting 84

Backup Selections list 36Bare Metal Restore 34best practices 75BIOS

reconfigure for booting 91BLIB 19, 35, 46–48block level incremental backup. See BLIBblocks

exclude unused and deleted 40

browse virtual machines 42browsing timeout 82

Ccache file

for browsing virtual machines 43catalog header file

wrong value for VM_TYPE 90catalog information in 6.5.x 90change VMware hostname in NetBackup 32Changed Block Tracking 19, 48

how to enable 25client

installed in virtual machine 99Client name selection option 37code 156 error 85code 227 error 91code 5 error 90code 6 error 86, 89configuration datastore 57configuration steps 17Consolidate-Helper snapshot 89Converter

VMware 15credentials

adding for VMware 30troubleshooting 84

ctkEnabled 25Cumulative Incremental Backup 35

Ddatacenter

for restore 70datastore

out of space 89deduplication 76Differential Incremental Backup 35disable virtual machine quiesce 40Discovered Timestamp 44disk array

configured as RDM 95

Index

display name 37, 44drives

and reboot failure 91

EEMM database

remove VM host name from NetBackup 32encrypted drives 24encryption of snapshot data transfer 39Enterprise Client license 17environment

diagrams 15importance to performance 81

equipment 81ESX server 15, 30Exclude unused and deleted blocks option 40Existing snapshot handling option 41

FFile level snapshot using VCB 38, 99file-level backup

about 99configuration tasks 100policy for 102

files list. See Backup Selections listFlashBackup-Windows policy 33, 46Full backup with file level incremental 39Full VM backup 38

Hheader file

VM_TYPE value 90helper virtual machine

for hotadd transfer type 28host name 37, 44

changing in NetBackup 32host properties

for VMware 30hotadd transfer type 40, 67, 89

notes on 27hypervisor 20

Iimported image

trouble restoring 90incremental backup

about 45requirements 35

incremental backup (continued)timestamp setting 33

independent disk 20, 44, 86individual file backup 99Install Software option 36Instant Recovery not supported 24invalid client 91ISO file 90

Jjob hangs 87

LLast Update 43license requirements 17logging

how to create folders for 80VMware 79vSphere 82VxMS 81

Mmanual backup 51Mapped full VM backup 38Monolithic export option 41mount point

for snapshot (VCB) 42missing 88snapshot 76VMware 37

Nnbd 39nbdssl 39nbemmcmd 32Network Block Device (NBD) transfer 39Network Block Device (NBD) transfer with SSL 39Network Connections dialog 72NFC connections 87NTFS file system

for USB drives 24

Ooff-host backup 34optimized storage 19overview

configuration steps 17

Index106

overview (continued)of backup process 16restore procedure 55

overwrite virtual machine 67

PPerform block level incremental backup 19, 35Perform Recovery dialog 73Perform snapshot backups option 34policy

for file-level backup 102for full virtual machine backup 33types 33wizard for creating 45

port number 31, 84prerequisites 23

Qquiesce virtual machine 40

RRDM 20, 86

about 93alternate client backup of 94–95configurations supported 94

reboot failure 91Recovery Destination dialog 66recovery host 14, 67recovery options 48–49

vStorage vs VCB 48Recovery Options dialog 66, 69recovery wizard. See restore from vStorage backuprelease level

using mixed levels 58remove VMware host name from NetBackup EMM

database 32restore

and catalog information 90from VCB backup 63from vStorage backup 66individual files 58job hangs 87notes on 56procedure overview 55virtual machine 61

Restore Marked Files dialog 63run a backup 51

SSAN luns 90SAN transfer type 39SCSI drives

and reboot failure 91scsiX:X.ctkEnabled 25Select ESX server dialog 71Select Folder dialog 72server name

changing in NetBackup 32size of backups 47snapshot

how to enable Changed Block Tracking 25mount point 42, 76removing leftover 41vSphere Client

how to delete 25Snapshot Policy Configuration wizard 45SSL encryption of snapshot data 39start a backup 51status code 156 85status code 227 91status code 5 90status code 6 86, 89Storage Destination dialog 72storage optimization 19, 24

enable Changed Block Tracking 25how to delete snapshot for 25

Tterminology 20timeout

browsing 82timeouts

vSphere 82timestamps

for incrementals 33transfer types 39

and hung job 87for restore 67hotadd 27problems with 89

troubleshootingtips 83

UUSB drives

as the snapshot mount point 24

107Index

UUID 37, 44

Vvalidate

credentials 30VCB 13, 21, 46

and file-level backup 99port number 31recovery options 49restore from backup 56, 63snapshot mount point 42when required 13why not used 14

VCB-HELPER suffix 28vCenter Converter 56vCenter server 15Virtual machine quiesce option 40Virtual Machine recovery wizard

restore to alternate location 69virtual machines

backup options 38browsing 42configure backup policy for 33how to back up 51restore procedures 55

VirtualCenter server 15VM_TYPE value in header file 90vmdk file 21

transferring to backup host 41VMware

and Linux 34backup environment 14–15backup host 30, 34backups 51configuration overview 17Converter 15credentials 30ESX server 15, 30host properties 30introduction 11logging 79main features 11policy configuration 33

file-level backup only 102required components 14snapshot mount point 37terminology 20troubleshooting 79

VMware NetBackup Integration Module (VNIM) 15

VMware Tools 21VMX directory 57vmx-07 35VNIM 15, 84volume ID of drive

troubleshooting 85Volume Manager volumes 46vSphere Client

enable Changed Block Tracking 25vSphere Client snapshot

how to delete 25vStorage 13, 21, 46

minimum VMware levels required 13recovery options 48restore from backup made by 66

VxMS logging 81

Wwizard

to create backup policy 45to recover virtual machine 66

Index108

Netbackup-VMware

Documents

storage unit

proprietary

globally unique

static ip

identify vacant

increase backup

mount point

commercial