EMC NetWorker Module for Microsoft Applications. Administration Guide. Release 2.3 P/N REV A02

Transcription

1 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide P/N REV A02 EMC Corporation Corporate Headquarters: Hopkinton, MA

2 Copyright EMC Corporation. All rights reserved. Published May, 2011 EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date regulatory document for your product line, go to the Document/Whitepaper Library on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. 2 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

3 Contents Preface Chapter 1 Overview About NetWorker Module for Microsoft Applications NMM support Supported and unsupported NetWorker features in NMM Windows operating system support NMM can coexist with NetWorker Module for Microsoft Exchange NMM can coexist with NetWorker Module for Microsoft SQL server Supported configurations Simple LAN-based configuration LAN-based configuration with a proxy client LAN-free configuration LAN-free dedicated storage node configuration The VSS snapshot creation process Providers Writers supported by NMM Dynamic volume support Providers and backup performance NMM client snapshot policies Preconfigured snapshot policies Rollover a snapshot Types of NMM client snapshot backups Serverless backup Nonpersistent rollover backup Instant backup with or without rollover Types of NMM client recoveries Conventional recovery Instant recovery Rollback recovery Full and granular backup and recovery for applications Directed recovery The NMM client interface Recover view Snapshot Management view Monitor view NMM client graphical user interface Opening the software and connecting to a NetWorker server Selecting an item for recovery EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 3

4 Contents Searching for an item Specifying a recovery browse time Selecting a backup version for recovery Viewing the volumes required for a recovery Performing a snapshot rollover Performing a rollback recovery Deleting a snapshot Chapter 2 Chapter 3 Chapter 4 Configuring a Scheduled Backup Backup configuration roadmap Name resolution Best practices and considerations for backing up application data Configuration tasks Configure a backup pool for snapshot operations Configure snapshot policies Configure a backup schedule Configure a backup group Configure a client resource Configure privileges Configure a proxy client Backing up a clustered NMM client Moving a NMM client to another NetWorker server NetWorker Client Management Specifying a remote client for directed recovery Connecting to a NetWorker server Specifying a recovery browse time Specifying ranges for service and connection ports Specifying a password Deduplication Backup and Recovery with Avamar Data deduplication with Avamar Avamar integration in NMM Supported and unsupported applications, features, and configurations Supported applications and configurations Unsupported applications, features, and configurations Related documentation about Avamar server and NetWorker server Additional NetWorker server deduplication operation information Avamar and NetWorker server configuration Configure the Avamar and the NetWorker server to receive deduplication data and process backups Set the DNS resolution for NetWorker deduplication node and NMM.. 76 Deduplication backups requirements for NetWorker server Backup levels and schedules for deduplication clients Retention policies Backup configuration notes Configuring a client resource for deduplication backup Querying deduplication save sets by using mminfo Recovering deduplicated data Deleting deduplication save sets EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

5 Contents Chapter 5 Deduplication Backup and Recovery with Data Domain Data deduplication with Data Domain Data Domain integration in NMM Supported applications, features, and configurations Data Domain deduplication support Data Domain Boost on NMM support Related documentation about Data Domain and NetWorker server Data Domain and NetWorker configuration Configuring client resource for Data Domain Boost backups Recovering deduplicated data Chapter 6 Multihomed setup for backup and recovery Overview Basic requirements for setting up a multihomed environment Generic requirements for setting up a multihomed environment for NMM backups Requirements for multihomed NMM client's network configuration Requirements for multihomed NetWorker server's network configuration.. 94 Requirements for network configuration on NetWorker storage node Configuring NMM client resources in a multihomed environment Chapter 7 Windows System Backup and Recovery Overview Access privileges for backup and recovery Performing system backups Specifying system save sets for backup NMM system data commands Configuring system backups Performing a recovery Recovery considerations System recovery in Windows server 2008 and Windows server System Recovery Options Summary Recovery options Recovering file system snapshots that have not been rolled over Booting the NMM host in Directory Service Restore mode Performing an authoritative recovery of NTDS or FRS data Performing a directed recovery with NMM Recovering the Windows system configuration to an earlier state Restoring BOOT/BCD data in Windows 2008 R Performing Windows print queues backup and recovery Performing Windows DFS-R granular backup and recovery Pre and post command support precmd.bat script postcmd.bat script nsrsnapvsssavepnpc file Performing disaster recovery for Windows 2003 and Windows 2003 R Perform a disaster recovery operation when the NMM client is not on a domain controller Perform a disaster recovery operation when the NMM client is on a domain controller Performing disaster recovery for Windows 2008 and Windows 2008 R EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 5

6 Contents Chapter 8 Microsoft Windows Cluster Backup and Recovery Windows server cluster backup and recovery Cluster support in NMM client Compatibility with previous Windows cluster backups Components used by NMM for Windows Cluster backup and recovery 131 Windows Cluster application information variable settings Performing Windows server cluster backups Cluster failover and backups Performing Windows server cluster recovery Performing Windows server 2003 clustered client disaster recovery Perform disaster recovery of a cluster client Cluster recovery environment variable settings Perform disaster recovery from a legacy VSS backup Perform a disaster recovery of a clustered client from a legacy non-vss backup Monitoring a recovery Glossary Index 6 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

7 Figures Title Page 1 Simple LAN-based configuration LAN-based configuration with a proxy client LAN-free configuration LAN-free configuration with a dedicated storage node VSS backup process NMM client main page Exclusion representation of recover items Snapshot Management view Monitor view Selected and partially selected items Snapshots and snapshot save sets Deduplication backup attribute Sample network topology of NetWorker multihomed backup Local client on the taskbar next to client Configuration Options dialog box Select Viewable Clients dialog box NMM client menu list EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 7

8 Figures 8 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

9 Tables Title Page 1 Currently supported writers Support for disaster and granular backup and recovery Pull and push support Backup tasks Best practices and considerations for application backups Conventional backup settings Hardware instant snapshot policy Hardware instant snapshot with rollover policy Considerations for NMM client backup schedules Save set syntax Special characters and their URL-encoded values Application information variable settings Configuration requirements for a proxy client Additional steps and considerations for backing up a clustered client resource Backup and recovery schedule comparison Configuration details for Data Domain and NetWorker Access privileges needed for backup and recovery NMM system data commands Tasks for scheduling a backup for VSS writers Windows Cluster application information variable settings Steps and considerations for backing up a clustered client resource EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 9

10 Tables 10 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

11 Preface As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative. Note: This document was accurate as of the time of publication. However, as information is added, new versions of this document may be released to the EMC Powerlink website. Check the EMC Powerlink website to ensure that you are using the latest version of this document. Purpose This guide contains information common to all the Microsoft applications, like SQL, SharePoint, Exchange, Active Directory, Hyper-V, and Data Protection Manager, that can be backed up and recovered by using EMC NetWorker Module for Microsoft Applications. IMPORTANT Ensure to download a copy of the EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide from the EMC Powerlink website to use along with this guide. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide contains information specific to an application, and must be referred to when backing up and recovering an application. Audience This guide is part of the EMC NetWorker Module for Microsoft Applications documentation set, and is intended for use by system administrators during the setup and maintenance of the product. Readers should be familiar with the following technologies used in backup and recovery: EMC NetWorker software EMC NetWorker snapshot management Microsoft Volume Shadow Copy Service (VSS) technology Storage subsystems, such as EMC CLARiiON or Symmetrix, if used EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 11

12 Preface Related documentation Conventions used in this document The following EMC publications provide additional information: EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide EMC NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups Release 2.3 Technical Notes EMC NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups Release 2.3 Technical Notes EMC NetWorker Licensing Guide EMC NetWorker Data Domain Deduplication Devices 7.6 SP1 Integration Guide EMC Information Protection Software Compatibility Guide EMC Solutions Enabler Symmetrix CLI Version 6.3 Quick Reference EMC NetWorker Release 7.6 SP1 documentation EMC NetWorker Release 7.6 SP2 documentation EMC uses the following conventions for special notices: Note: A note presents information that is important, but not hazard-related. IMPORTANT An important notice contains information essential to software or hardware operation. Typographical conventions EMC uses the following type style conventions in this document. Normal Used in running (nonprocedural) text for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications Bold Used in running (nonprocedural) text for: Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for: Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus) What user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for: Full titles of publications referenced in text Emphasis (for example a new term) Variables 12 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

13 Preface Courier Used for: System output, such as an error message or script URLs, complete paths, filenames, prompts, and syntax when shown outside of running text Courier bold Used for: Specific user input (such as commands) Courier italic Used in procedures for: Variables on command line User input variables < > Angle brackets enclose parameter or variable values supplied by the user [ ] Square brackets enclose optional values Vertical bar indicates alternate selections - the bar means or { } Braces indicate content that you must specify (that is, x or y or z)... Ellipses indicate nonessential information omitted from the example Where to get help EMC support, product, and licensing information can be obtained as follows. Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at: Technical support For technical support, go to Powerlink and choose Support. On the Support page, you will see several options, including one for making a service request. Note that to open a service request, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to: [email protected] If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject that you are addressing. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 13

14 Preface 14 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

15 1 Overview This chapter includes the following topics: About NetWorker Module for Microsoft Applications Supported configurations The VSS snapshot creation process NMM client snapshot policies Rollover a snapshot Types of NMM client snapshot backups Types of NMM client recoveries Full and granular backup and recovery for applications Directed recovery The NMM client interface NMM client graphical user interface Overview 15

16 Overview About NetWorker Module for Microsoft Applications The EMC NetWorker Module for Microsoft Applications (NMM) works with Microsoft Volume Shadow Copy Service (VSS) technology to provide snapshot backup and recovery services for file systems, Microsoft applications, and Windows system data. The NMM client allows for the creation of point-in-time snapshot data. A snapshot can be retained on storage volumes for quick access. You can also perform a rollover of a snapshot to a traditional backup medium, such as a tape, file type device, advanced file type device, or Data Domain device. Data can be recovered either from a snapshot or from the backup media. This section provides information on: NMM support on page 16 Supported and unsupported NetWorker features in NMM on page 18 Windows operating system support on page 18 NMM can coexist with NetWorker Module for Microsoft Exchange on page 19 NMM can coexist with NetWorker Module for Microsoft SQL server on page 19 NMM support NMM provides the following support: Support for the following configurations: Simple LAN-based configuration on page 19 LAN-based configuration with a proxy client on page 21 LAN-free configuration on page 22 LAN-free dedicated storage node configuration on page 23 Support for several types of backup, depending on the types available for the given application or operating system: Serverless backup on page 31 Nonpersistent rollover backup on page 32 Instant backup with or without rollover on page 32 Support for several types of recovery, depending on the types available for the given application or operating system: Conventional recovery on page 32 Instant recovery on page 33 Rollback recovery on page 33 Deduplication support for most of the Microsoft applications and Windows operating systems that are supported by NMM: For the NetWorker server, NetWorker 7.5 SP3 or 7.6 SP1 is required. For the EMC Avamar server hardware, Avamar Axiom 4.0 SP2 or later is required. For the Data Domain server: Data Domain Appliance with Data Domain operating system version supported by NetWorker client installed on NMM 2.3 client. 16 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

17 Overview Data Domain operating system 4.8 or later for Data Domain-Boost functionality. NetWorker 7.6 SP1 for Data Domain-Boost functionality. Microsoft application support: Exchange server 2010 Exchange server 2007 Exchange server 2003 SQL server 2008 R2 SQL server 2008 SQL server 2005 Office SharePoint server 2010 Office SharePoint server 2007 SharePoint Portal server 2003 Windows SharePoint Services 3.0 Windows SharePoint Services 2.0 Windows SharePoint Foundation 2010 System Center Data Protection Manager 2007 Windows server 2008 and Windows server 2008 R2 with Hyper-V Microsoft release-to-manufacturing (RTM) release of Hyper-V, which is available only for the x64 edition of Windows server 2008 RTM. The initial Windows server 2008 RTM provided a beta or release candidate (RC) inversion of Hyper-V. If you are using one of these pre-rtm versions of Hyper-V, or did not order Hyper-V with your Windows server 2008 RTM license, you must download the Hyper-V RTM update from Microsoft. Windows server 2008 Service Pack 2 and its updates Windows server 2008, server Core Installation, with Hyper-V Windows volumes and system components Windows Cluster support Active Directory Application Mode (ADAM) Active Directory Note: Application support often requires a minimum specific service-pack level. The service-pack levels frequently change. The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about which service packs are required for each application. Support for system providers: Microsoft System Provider for use with supported disks, independent of its hardware arrangement, or whether or not the disk, is a part of a hardware array. This includes directly connected disks such as SATA or SCSI and storage arrays, for example, where a hardware provider does not exist or has not been installed. However, the Microsoft System Provider will not take advantage of any features that a storage array can provide including any built-in snapshot capabilities. About NetWorker Module for Microsoft Applications 17

18 Overview Note: The Microsoft System Provider is part of the operating system. The cache sizes and locations are managed in the Disk Management applet. With EMC VSS Provider: EMC Symmetrix, Symmetrix V-MAX, and Symmetrix DMX arrays EMC CLARiiON arrays Note: When EMC VSS hardware providers are used with VMware ESX 3.5 or ESX 4.0 and Windows guest operating system in NMM clients, set the environment variable VICLIENT_DISABLE_CACHE=1 to disable Virtual Infrastructure Client (VI Client) cache in the NMM clients. EMC Celerra arrays with Celerra VSS Provider Dell EqualLogic PS Series arrays with Dell EqualLogic Integration ToolKit IBM Storage System DS8000 IBM Storage System DS6000 The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about hardware array versions supported and NMM compatibility. Supported and unsupported NetWorker features in NMM The following NetWorker features are supported: Internationalization (I18N) NetWorker cloning and staging to create and manage additional copies of save sets. This NMM support requires NetWorker 7.5 SP3 or 7.6 SP1. Dedicated storage node for LAN-free backups Avamar and Data Domain support for data deduplication Mulithomed environment backup and recovery The following NetWorker features are not supported: Localization (L10N) Manual (adhoc) backups Windows operating system support NMM client supports the following versions of Microsoft Windows and Microsoft Windows-related features: Windows server 2008 R2 (x64) Standard, Enterprise, DataCenter Editions Windows server 2008 SP2 (x86, x64) Standard, Enterprise, DataCenter Editions Windows server 2003 R2 (x86, x64) Standard, Enterprise, DataCenter Editions Windows server 2003 (x86, x64) Standard, Enterprise, DataCenter Editions Windows storage server 2003 Windows storage server 2003 R2 System state recovery, file servers, and operating system roles including Active Directory, DHCP, and Terminal Services 18 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

19 Overview GUID Partition Table disks: No disk size limit on Windows environments with CLARiiON storage (EMC SnapView clone, SnapView snap, and EMC SAN Copy technologies only) Disk size limit of less than 2 TB on Windows environments with Symmetrix storage Note: Windows IA64 editions is not supported. The following Windows features are not supported: BitLocker encryption VSS Hardware Provider based proxy backup of Windows dynamic disks. Single Instance Storage (SIS) NMM can coexist with NetWorker Module for Microsoft Exchange NetWorker Module for Microsoft Exchange (NME) 5.1 SP1 or later and NMM 2.3 can coexist on a server. While NMM can be used to perform database backups by using VSS, NME can be used to perform granular backups, which means individual mailbox and public folder item-level backups. However, make sure not to use both NMM and NME to back up the Exchange database. If NMM is used for backups, NME promotes an incremental database backup to full backup. Note: NME does not support Microsoft Exchange NMM can coexist with NetWorker Module for Microsoft SQL server NetWorker Module for Microsoft SQL server (NMSQL) and NMM 2.3 can coexist on a server. You can back up and recover SharePoint data by using NMM and NMSQL, where NMM 2.3 provides disaster recovery protection for the SharePoint content databases, such as CFG database, SSP web application, and search. Supported configurations This section provides information on: Simple LAN-based configuration on page 19 LAN-based configuration with a proxy client on page 21 LAN-free configuration on page 22 LAN-free dedicated storage node configuration on page 23 Simple LAN-based configuration Figure 1 on page 20 shows a simple LAN-based configuration with a SAN. In a LAN-based configuration, the production data is stored on a SAN or direct-attached storage (DAS). The data path to the NetWorker storage node devices is over a LAN. The application server that is being protected has the NMM client installed. Supported configurations 19

20 Overview The data moves as follows: 1. The NetWorker server, which must be release 7.5 SP3 or later or 7.6 SP1 or later, initiates the process by contacting the application server where the NMM client software is installed. 2. The application server creates a snapshot of the data on the storage volume, by using the NMM software. Note: In Figure 1 on page 20, snapshots are represented by S1 through S5. 3. The application server with the NMM client software uses a snapshot in primary storage to transfer the data over the LAN to the storage node, which can be the NetWorker server itself, and from there into a conventional backup medium such as the following: File type disk Advanced file type disk Tape Data Domain device NetWorker Server or LAN Application server (NMM 2.3 and NetWorker client or 7.6.1) SAN NetWorker Storage Node or Traditional storage Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 GEN Figure 1 Simple LAN-based configuration 20 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

21 Overview LAN-based configuration with a proxy client Figure 2 on page 21 shows a LAN-based configuration with a SAN and a proxy client. Both the application server and the proxy client have the NMM client installed. Install the proxy client software by using the NMM client software package. Note: Both the application server and the proxy client must use the same NMM version, operating system version, NetWorker version, and VSS Provider version. A proxy client is a host that acts as a remote Data Mover (DM) when snapshots are rolled over to a conventional backup medium. A proxy client frees resources on the application server. When a backup operation uses a proxy client, it is known as a serverless backup. A proxy client can be used only with VSS Hardware based backup. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM client software is installed. 2. The application server creates a snapshot of the data on the storage volume, by using the NMM software. Note: In Figure 2 on page 21, snapshots are represented by S1 through S5. 3. The NMM software running on the proxy client will communicate with VSS to make the snapshot visible on the proxy client. 4. The proxy client uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, tape, or Data Domain device. NetWorker Server or LAN Application server (NMM 2.3 and NetWorker client or 7.6.1) Proxy client (NMM 2.3 and NetWorker client or 7.6.1) SAN Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 NetWorker Storage Node or Traditional storage GEN Figure 2 LAN-based configuration with a proxy client Supported configurations 21

22 Overview LAN-free configuration Figure 3 on page 23 shows a LAN-free configuration with a SAN. The NMM client is installed on the application server. The proxy client is installed on the NetWorker storage node by using the NMM client software package. You can set up a NetWorker storage node release 7.5 SP3 or 7.6 SP1 as a proxy client to avoid the network traffic that is generated when a snapshot is rolled over to a conventional backup medium. Network traffic is avoided because both the conventional backup device and the snapshot are directly attached to the storage node. The proxy client can be used only with VSS hardware-based backup. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM client software is installed. 2. The application server creates a snapshot of the data on the storage volume, by using the NMM software. Note: In Figure 3 on page 23, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the proxy client. 4. The proxy client, in this case the storage node, uses a snapshot in primary storage to transfer the data into a conventional backup medium such as a file type disk, advanced file type disk, or tape. The NetWorker server and the application server communicate through the LAN. However, the data itself is not transferred across the LAN because the conventional backup medium is directly attached to the NMM proxy node, which has NetWorker storage node software and backup media configured. The NMM proxy node acts as a NetWorker storage node. 22 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

23 Overview NetWorker Server or LAN Application server (NMM 2.3 and NetWorker client or 7.6.1) Proxy client (NMM 2.3 and NetWorker Storage Node or 7.6.1) SAN Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 Traditional storage GEN Figure 3 LAN-free configuration LAN-free dedicated storage node configuration A dedicated storage node (DSN) is a storage node that acts as a dedicated backup device for a local NMM host. A dedicated storage node allows data from the local host to be backed up to its devices. The NMM 2.3 support for dedicated storage node allows you to perform the following: LAN-free backups from a NMM client without configuring a NMM proxy host. Backups to SAN devices attached directly to the NMM client host. NMM 2.3 dedicated storage node supports backup and recovery of all applications supported by NMM 2.3. For example, DPM, Active Directory, Hyper-V, SharePoint, Exchange, SQL, and file system backups. Note: If you do not configure a storage node device, a default device is configured with NetWorker server to direct the backups to the appropriate storage node. Supported configurations 23

24 Overview NetWorker Server or LAN Application server (NMM 2.3 and NetWorker Storage Node or 7.6.1) SAN Primary storage (CLARiiON or Symmetrix) S5 S1 S4 S3 S2 Traditional storage GEN Figure 4 LAN-free configuration with a dedicated storage node Figure 4 on page 24 shows a LAN-free configuration with a dedicated storage node. The data in a LAN-free configuration with a dedicated storage node moves as follows: 1. The NetWorker server initiates the process by contacting the application server, where the NMM software and the NetWorker storage node 7.5 SP3 or 7.6 SP1 or later is installed. 2. The application server creates a snapshot of the data on the storage volume, by using the NMM software. Note: In Figure 4 on page 24, snapshots are represented by S1 through S5. 3. The snapshot is visible to the storage node that resides on the application server. 4. The storage node on the application server uses a snapshot in primary storage to transfer the data directly over to the backup media, which is attached to application server as direct attached or SAN. The NetWorker server and the application server communicates the metadata through the LAN. However, the data itself is not transferred across the LAN because the conventional backup medium is attached directly to the NetWorker storage node. 24 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

25 Overview The VSS snapshot creation process Microsoft Volume Shadow Copy Service (VSS) acts as a coordinator among the following three components that create, modify, back up, and recover data: Requestors Include the NMM backup application. Providers Include the Microsoft Software Shadow Copy provider or hardware-based providers such as the EMC VSS Provider. Writers Include writers for operating system data, application data such as Microsoft Exchange server 2003 or Microsoft SQL server data, and file system volumes such as a D:\ data drive. In VSS, NMM is a requestor, that is an application that performs the backup and recovery of applications or services. When a requestor performs a backup or recovery, the following occurs: 1. The requestor asks for information from VSS. 2. VSS reviews the request for validity. 3. VSS sends writer data from multiple application and system writers to the requestor. 4. The requestor tells VSS which writers and volumes to include in the snapshot. Each application and service that supports VSS has its own writer, which understands how the application or service works. After the writer signals that it has prepared the data, the following occurs: 1. The VSS software does the following: a. Directs the writer to freeze input/output (I/O) to the selected volumes. b. Queues transactions for later processing. c. Calls a provider to capture the requested data. 2. The provider does the following: a. Captures the prepared data. b. Creates a snapshot that exists side-by-side with the live volume. 3. After the snapshot is created: a. The provider signals VSS and this signal tells the writer to resume activity. b. I/O is released to the selected volumes and any queued writes that arrived during the provider's work are processed. Figure 5 on page 26 illustrates the VSS backup process. The VSS snapshot creation process 25

26 Overview 4. Requestor asks VSS to create snapshot. Requestor 1. NetWorker software (the requestor) asks VSS to enumerate writers and gether their metadata. 2. Writers provide an XML description of backup components and define the recover method. 5. VSS tells the writers to freeze activity. Writer Writer Writer Writer 7. VSS tells the writers to resume activity. Writer 3. VSS asks which providers can support a snapshot for each of the required volumes. 6. VSS tells the providers to create the snapshot of the current state on disk. Microsoft VSS Software Provider EMC VSS Provider (CLARiiON or Symmetrix) Disk 1 Disk 2 Disk 3 Disk 3 GEN Figure 5 VSS backup process The following sections provide information on: Providers on page 26 Writers supported by NMM on page 27 Dynamic volume support on page 29 Providers and backup performance on page 29 Providers A provider is used to capture snapshots. One of the following types of providers are available: EMC VSS Hardware Provider, which supports EMC Symmetrix and CLARiiON arrays EMC Celerra VSS Hardware Provider, which supports Celerra arrays Microsoft Software Shadow Copy provider The Microsoft Software Shadow Copy provider is a host-based provider that works with any type of storage hardware. The EMC VSS Hardware Provider works with a CLARiiON or a Symmetrix disk array. Some features of NMM, such as serverless backup (NMM proxy based backups) and rollback recovery, are available only with hardware providers such as the EMC VSS Hardware Provider. 26 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

27 Overview The EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide provides more information about using NMM with a VSS Hardware Provider, including hardware array installation and configuration, and NMM installation and configuration. Note: NMM does not support rollback restore for backups performed by Dell EqualLogic, Celerra, IBM, or Microsoft hardware. Only conventional restore and snapshot restore are supported for backups performed by Dell EqualLogic or Celerra hardware. Writers supported by NMM Writers provide information about what data to back up, and specific methods for handling components and applications during backup and recovery. They also identify the type of application or service that is being backed up. If a service or application is present on a system but is not active, information from its writer will not be available. Consequently, a writer can appear or disappear from backup to backup. Note: Files located in an FTP directory are not included in a SYSTEM COMPONENTS snapshot. Typically, FTP files are stored by IIS in C:\inetpub. IIS metabase files are configuration files, which are backed up as part of SYSTEM COMPONENTS. The FTP files are content files, and must be backed up separately. Table 2 on page 36 lists the writers that are supported for the NMM client. Note: All the VSS writers appear under Bootable System State in SYSTEM COMPONENTS:\ save set. These writers are listed when the vssadmin list writers command is used at the command prompt. Table 1 Currently supported writers (page 1 of 2) Writer type Volumes Writers supported by NMM A file system path such as D:\data Note: NMM only supports NTFS volumes. It does not support FAT16 and FAT32 volumes. Also, NMM does not support backup of raw volumes. The VSS snapshot creation process 27

28 Overview Table 1 Currently supported writers (page 2 of 2) Writer type Writers supported by NMM Microsoft applications Active Directory Application Mode (ADAM) Exchange server 2003 Exchange server 2007 Exchange 2010 System Center Data Protection Manager 2007 Distributed File Replication (Windows server 2003) Active Directory Lightweight Directory Services (AD LDS) SharePoint Portal server 2003 Office SharePoint server 2007 Windows SharePoint Services 2.0 Windows SharePoint Services 3.0 SharePoint 2010 SQL server 2008 SQL server 2005 Windows 2008 R2 Windows server 2008 (Full Installation) with Hyper-V Windows server 2008 (Server Core Installation) with Hyper-V Windows system components For Windows server 2003, Windows server 2008, and Windows server 2008 R2: Background Intelligent Transfer Service (BITS ) COM+ Registration Database (REGDB) Certificate Authority Cluster Database (Windows server 2003) Cluster Writer (Windows server 2008 and Windows server 2008 R2) Dynamic Host Configuration Protocol (DHCP) Jet Event log File Replication Server (FRS) File Storage Resource Manager (FSRM) Microsoft Distributed File Replication (Windows server 2003) IIS Configuration Writer (Windows server 2008 and Windows server 2008 R2) IIS Metabase MSSearch Service Writer (Windows server 2008 and Windows server 2008 R2) Network Policy and Access Service (NPS) VSS Writer (Windows server 2008 and Windows server 2008 R2) NTDS (Active Directory Schema) Registry Removable Storage Manager (RSM) Remote Storage Manager Shadow Copy Optimization Writer (Windows server 2008 and Windows server 2008 R2) SQL Embedded (SQL 2005 Express, or SQL 2008 Express, and Windows server 2008 R2 Express) Terminal Services Licensing Windows Internet Name Service (WINS) Windows Management Instrumentation (WMI) VSS Performance Counters Writer (Windows server 2008 R2) VSS Task Scheduler Writer (Windows server 2008 R2) VSS Express Metadata Store Writer (Windows server 2008 R2) DFS Replication Service Writer (Windows server 2008 R2) 28 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

29 Overview Dynamic volume support In Windows server 2003, Windows server 2008, and Windows server 2008 R2: NMM supports snapshots of dynamic volumes that use the Microsoft Software Shadow Copy provider. NMM provides software-based support for: Dynamic volume on a single disk. Dynamic volume spanning multiple disk. NMM does not support dynamic volumes in striping. NSR Data Mover parameter is not supported for dynamic volumes configuration. For example, hardware-based transportable snapshots are not supported when the dynamic volumes are on CLARiiON storage. NMM will attempt to perform the hardware-based snapshot, but the operation will fail during import of the hardware-based snapshot on the proxy backup host. IMPORTANT Any attempt to take a hardware-based replica of a dynamic volume will fail, and cause instability in the system. Windows server 2008 introduces support for local, hardware-based snapshots of dynamic volumes. NMM does not support local, nontransportable, hardware-based snapshots of dynamic volumes on Windows server For customer environments where dynamic volumes are provisioned by using a storage array, customers must not install the storage array vendor s VSS provider on the production host. For example, if a dynamic volume was created on a CLARiiON LUN, customers must not install the EMC VSS Hardware Provider on the production host. Providers and backup performance The Microsoft Software Shadow Copy provider uses a copy-on-write snapshot technology. Some hardware providers, such as the EMC VSS Hardware Provider, support split-mirror snapshot technology and copy-on-write technology. Although copy-on-write technology requires less hardware resources, split-mirror technology provides better performance. Large or fast-changing databases should not be saved with copy-on-write snapshot technology. The input/output requirements of these databases can cause the copy-on-write cache to overflow and invalidate the snapshot. Additionally, copy-on-write technology cannot match the performance of split-mirror technology. For large or fast-changing databases, use the EMC VSS Hardware Provider in conjunction with EMC hardware to provide a split-mirror storage solution such as a CLARiiON clone or a Symmetrix BCV. The VSS snapshot creation process 29

30 Overview NMM client snapshot policies Backups are configured as scheduled snapshot backups on a NetWorker server 7.5 SP3 and 7.6 SP1. Note: Manual (adhoc) backups, from either the command line or from the NMM client, are not supported. However, you can manually start a scheduled backup at any time. Snapshot backups are specified through a snapshot policy and various settings for the client resource. Snapshot policies and client resources are set up on the NetWorker server by using NMC. Perform either of the following: Specify a preconfigured policy Preconfigured snapshot policies on page 30 provides information. Create a custom snapshot policy Configure snapshot policies on page 54 provides information. Preconfigured snapshot policies The following preconfigured snapshot policies exist: Serverless A single snapshot is taken per day. The data is then rolled over to conventional storage and the snapshot is deleted. This is a simple snapshot policy that can be considered as a default snapshot policy in NMM. Note: The serverless snapshot policy in NMC can be used in true serverless backup operations, as described in Serverless backup on page 31, and can also be used in normal non-serverless operations. Daily The daily snapshot policy in NMC has Retain Snapshots set to eight. This indicates that NMM should keep eight snapshots per day. When the ninth backup starts at the beginning of the next day, the oldest snapshot is deleted, and so on. Each snapshot has 24-hour expiration policy. If you select the daily snapshot policy, persistent snapshots are created. Rollover a snapshot A rollover is the process of creating a conventional backup from a snapshot. Conventional backups include backup to tape, file type, or advanced file type devices. Rollover policies are automatically controlled through snapshot policy settings on the NetWorker server. If necessary, perform a rollover manually by using the NMM GUI: Before recovering a database that currently exists only as a persistent snapshot, roll over the snapshot to tape to protect the data in case the snapshot becomes corrupted during the recovery process. Creating a convention backup copy of the snapshot data. This conventional copy will reside on the device even if the retention deletes the snapshot. 30 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

31 Overview Types of NMM client snapshot backups The NMM client supports three types of snapshot backups: Serverless backup on page 31 Nonpersistent rollover backup on page 32 Instant backup with or without rollover on page 32 Serverless backup Serverless backup is a method of offloading backup procedures from an application server so that the time ordinarily devoted to backup functions can be used to carry out other server tasks. Serverless backup uses a NMM proxy client to move the data from the primary storage on the application server host to the secondary storage on another host. In this kind of backup, the snapshot is created on the application server and immediately moved to the proxy client. After the snapshot is created, the application server is not involved in the backup operation. During the rollover, that is backup from the snapshot, the application server is free and all of its resources are available for use. Examples of scenarios when serverless backups are used: When Exchange server is backed up by using serverless backup, Outlook users can continue to use the application server. Performing serverless backups are also useful when there is additional processing involved in a snapshot backup and is CPU intensive. For example, to help determine whether a snapshot of a Exchange database is consistent, the Exchange utility eseutil is run against the snapshot. Running eseutil can be disk intensive. Using serverless backup helps free resources on the Exchange server because the work from the Exchange server is offloaded to a proxy client. Serverless or proxy backup is enabled by specifying NSR_DATA_MOVER in the Application Information field of the client resource. Note: Serverless backup is available only with EMC VSS Hardware Providers and is subject to the capabilities of the vendor s hardware. The EMC VSS Provider for CLARiiON and Symmetrix provides the capability to perform serverless backup operations for these storage platforms. Ensure that the operating system version and the service pack or update level used is the same on both, the application server host and proxy host. For example, do not use a Windows server 2003 system as the proxy mount host for Windows server 2008 production host, otherwise backup fails. Note: If a production server is a virtual machine, then proxy host should be a physical machine. Types of NMM client snapshot backups 31

32 Overview Nonpersistent rollover backup Nonpersistent rollover backup means that snapshots are not retained once the backup is rolled over to a conventional backup medium such as tape, file, or advanced file type file type device, or Data Domain device. The snapshot is automatically deleted from the NMM client. The snapshot created is also called a temporary snapshot. For nonpersistent backup, the Retain Snapshots is set to 0 in the Snapshot Policy. Instant backup with or without rollover An instant backup creates and retains a snapshot on a mounted storage disk volume. During the period the snapshot resides on a mounted storage disk volume, it is referred to as a persistent snapshot. Retention of persistent snapshots on a mounted storage disk volume enables the user to perform an instant recovery. The number of persistent snapshots that can be retained on a volume depends on the amount of resources available. Other factors that constrain the number of persistent snapshots include: Snapshot technology that is used, either copy-on-write or split-mirror. Input/output patterns of the drive. Processing involved in running a snapshot backup group. Depending on how the backups are configured, a snapshot that is created during an instant backup may be configured to rollover to a conventional backup. For persistent backup with or without rollover, the Retain Snapshots is set to any non-zero value in the Snapshot Policy. Types of NMM client recoveries There are three types of recoveries: Conventional recovery on page 32 Instant recovery on page 33 Rollback recovery on page 33 By default, recoveries are performed from a conventional backup. If a conventional backup is not available for the selected browse time, an instant recovery is performed. The default recovery method can be specified in the NetWorker recovery options dialog box. NetWorker recovery options on page 106 provides more information about these recovery methods. Conventional recovery A conventional recovery consists of recovering data from a snapshot that has been rolled over to a backup media. Conventional recoveries support the same level of item selection as do instant recoveries. 32 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

33 Overview Instant recovery Instant recoveries are performed with persistent snapshots. An instant recovery can take less time to complete than a conventional recovery because the snapshot is available on a mounted disk storage volume rather than on a conventional backup medium. Instant recoveries support the selection of individual files in a file system snapshot. Additionally, instant recoveries support the selection of individual components at whatever level of granularity is supported by the system or application writer. If the persistent snapshot is created by using a proxy client, the snapshot file system on the proxy client is read to restore the files. In this way, performance is improved even further because the job of processing the snapshot for recovery is off-loaded from the NMM client production host to the proxy client. The procedure to perform an instant recovery of file system data differs if only a persistent snapshot is available. Chapter 7, Windows System Backup and Recovery, provides more information about performing recoveries. Note: When performing an instant recovery, the snapshot may become invalidated. This can occur if the snapshot is based on copy-on-write technology. If a large amount of data is recovered to the original volume, the cache may overflow. This is true for the Microsoft Software Shadow Copy provider and for hardware providers that use copy-on-write technology, such as CLARiiON snapshots and Symmetrix virtual devices. Rollback recovery A rollback recovery is the process of returning data volumes to an earlier point in time. The entire contents of a persistent snapshot are recovered during a rollback recovery. The user cannot select individual components in a rollback recovery operation. A rollback recovery is the fastest way to recover the contents of a persistent snapshot. A rollback recovery is known as a "destructive" recovery because all changes that were made to the file systems after the selected snapshot was taken are overwritten. For example, suppose that a snapshot of a database is taken every hour. At 5:30 p.m., it is determined that the database is corrupt and that the last known consistent database snapshot was taken at 5:00 p.m. When the database host is rolled back to the 5:00 p.m. snapshot, all database transactions between 5:00 p.m. and 5:30 p.m. are overwritten. To perform a rollback operation, the following requirements must be met: The snapshot to be rolled back must reside on a CLARiiON or Symmetrix storage system that is supported with the EMC VSS Provider. The NMM client to which the snapshot is to be rolled back must be supported with a proxy client and the snapshot must have been created by using a proxy client. The nested mount points on file systems are dismounted prior to performing the rollback restore. The Microsoft Exchange checkbox titled This database can be overwritten by a restore is selected for each Exchange database that is to be recovered. This checkbox can be found by using the Exchange SYSTEM Manager application. Types of NMM client recoveries 33

34 Overview The databases are detached for each Microsoft SQL server database that is to be recovered. NMM does not support rollback restore for backups performed with Microsoft Software Shadow Copy provider, Dell EqualLogic, or Celerra hardware. Only conventional restore and snapshot restore are supported for those hardware products. Distributed Link Tracking Client must be turned off during rollback, or else dismount will fail. Turn off the Distributed Link Tracking Client in Windows Services before starting rollback. The Microsoft software VSS provider must not be running during rollback, or else dismount will fail. The SYSTEM process must not be running during rollback, or else dismount will fail. The SYSTEM process leaves the volume open when there are software shadow copies on the volume. To ensure that the volumes are not open, delete any shadow copies on the volumes that are being rolled back. Storage array descriptor file A storage array descriptor file, sa.ini, contains information about the storage arrays connected to the proxy client Data Mover. The sa.ini file is created with the nsr_sa_ini.exe utility and placed in the nsr\res directory on the NMM client host. nsr_sa_ini.exe prompts you for information about the storage arrays connected to the proxy client. The required inputs are different for CLARiiON and Symmetrix: For a CLARiiON storage array, you must provide an array username and password. When you complete the entries for a CLARiiON sa.ini file, the password string is encrypted when you save the file. Sample CLARiiON sa.ini file on page 35 provides an example of the entries in this file. For a Symmetrix storage array, the sa.ini file has fewer parameters. You do not need an account name, password, or IP address. Sample Symmetrix sa.ini file on page 35 provides an example of the entries in this file. To create a storage array descriptor file: 1. At the command line, type: nsr_sa_ini.exe 2. Follow the prompts to provide the array information. Note: Even though the utility appears to allow you to type credentials for more than one storage array, only the first one will be used by NMM. You must create a separate sa.ini for each storage array. When you have completed typing the array information, the file is saved to the nsr\res directory on the NMM client host. 34 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

35 Overview IMPORTANT Do not edit the sa.ini file with a text editor to make changes in the array parameters. Using a text editor can corrupt the file, or compromise the password entries. Use the nsr_sa_ini.exe tool to edit the sa.ini file if you need to make changes after you create it. Sample CLARiiON sa.ini file A sample sa.ini file for a CLARiiON storage array would look similar to the following: [Storage_Array] Storage_Array_Count=2 Storage_Array_1=APM [APM ] Array_Type=CLARiiON Array_model=CX500 Array_user=sbarma Array_pass=**** Array_pass_confirm=**** Array_SPA= Array_SPB= Sample Symmetrix sa.ini file A sample sa.ini file for a Symmetrix storage array would look similar to the following: [Storage_Array] Storage_Array_Count=1 Storage_Array_1= [ ] Array_Type=Symmetrix Array_Sid= Array_Model=1000P-M2 Failure of system rollback with CLARiiON if the configuration information is not current If a CLARiiON array is migrated, or the information in the CLARiiON configuration is not up to date, rollback may fail. If there is more than one entry in the CLARiiON clarcnfg file, Replication Manager only uses the first entry. If the clarcnfg file is not current, the first entry may be pointing to a CLARiiON that is no longer connected to the system. Edit the clarcnfg file so that there is only one entry, pointing to the current CLARiiON you want to use. Full and granular backup and recovery for applications NMM provides full and granular backup and recovery for most applications: Full disaster backup and recovery The entire volume or database for that application is backed up, and the entire volume or database is recovered as a whole. In disaster backup and recovery, you cannot select individual items for backup and recovery. Full backup and recovery is used for disaster recovery. Granular backup and recovery In granular backup, individual items can be selected for backup and in granular recovery, individual items can be selected for recovery. Full and granular backup and recovery for applications 35

36 Overview For some applications, granular recovery of items requires that the items be specified for a granular backup. For other applications, items cannot be specified for backup at a granular level, but can be selected for granular recovery from the full backup. Table 2 on page 36 lists the support provided by NMM for disaster and granular backup and recovery for Microsoft applications and volumes. Table 2 Support for disaster and granular backup and recovery Types of backup and recovery Active Directory SQL server Exchange server Microsoft Office SharePoint server 2007 Microsoft Office SharePoint server 2010 Data Protection Manager Hyper-V File system Disaster (full backup) Granular backup X X X X X X Disaster (full recovery) Granular recovery X X X X X Directed recovery In a normal recovery, there are three roles involved in the process: Source Control Destination All of these roles are on the same computer: The source client is the computer where the backup data came from. The control client is the computer running the NMM UI to initiate the recover process. The destination client is the computer that the data is restored to. NMM supports normal recovery and directed recovery. In directed recovery, the source, control, and destination roles are not all on the same computer. There are two types of directed recovery: In pull directed recovery, the control role and destination role are performed on the same computer. The control role running on the destination computer pulls the recovery data to itself. Backup data from the source client is restored to the destination client. In push directed recovery, the control role can be run on the source client or a different client. Backup data from the source client is restored to the destination client. The control client computer pushes it out to another computer, the destination client. The destination client is not the same computer as the source client or control client. NMM supports pull directed recovery for most applications. You can run the recovery program NMM (the control role) on the same computer that the data is being restored to (the destination client). Some require additional or different steps. Otherwise, specify the alternate server to recover to in the regular recovery steps for the application. Performing a directed recovery with NMM on page 120 provides more information. 36 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

37 Overview NMM provides support for pull and push directed recovery for the following applications. Table 3 on page 37 details the pull and push directed recovery support. Table 3 Pull and push support Application Pull directed recovery Push directed recovery SQL server X File system X Hyper-V Data Protection Manager X Exchange server 2007 X Exchange server 2010 Only for DAG based recovery SharePoint server 2007 X X SharePoint server 2010 X X The NMM client interface The NMM client interface has three views: Recover view on page 37 Snapshot Management view on page 39 Monitor view on page 40 Recover view With the exception of rollback recovery, all recoveries are performed from the Recover view. Rollback recoveries use the Snapshot Management view. Figure 6 on page 38 shows the Recover view. The NMM client interface 37

38 Overview Main toolbar Navigation tree client selection (clustered client only) Available views Summary of selected items View specific toolbar Figure 6 NMM client main page The summary of selected items can also display exclusions, which shows only those items that are not selected for recovery. This view can be helpful when many items are selected for recovery. Figure 7 on page 38 shows an exclusion representation. Items in red are excluded from recovery Figure 7 Exclusion representation of recover items 38 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

39 Overview To view an exclusion representation: 1. Right-click in the summary pane at the bottom of the page. 2. Select Exclusion Representation. Snapshot Management view In most cases, snapshot rollover and delete operations are performed automatically based on snapshot policies, which are set up on the NetWorker server. However, if you need to manually delete or rollover a snapshot, do so in the Snapshot Management view. The following operations can be performed on snapshots: Rollback snapshot Rollover snapshot Delete snapshot The Rollback Snapshot and Delete Snapshot option are available as shown in Figure 8 on page 39. Figure 8 Snapshot Management view Chapter 2, Configuring a Scheduled Backup, provides more information about snapshot policies. The NMM client interface 39

40 Overview Monitor view Recovery and snapshot management operations can be monitored in the Monitor view shown in Figure 9 on page 40. Figure 9 Monitor view Most messages displayed in the Monitor view are also written to log files. NMM client graphical user interface This section describes how to perform the basic tasks in the NMM client interface. Opening the software and connecting to a NetWorker server on page 40 Selecting an item for recovery on page 41 Specifying a recovery browse time on page 42 Selecting a backup version for recovery on page 42 Viewing the volumes required for a recovery on page 43 Performing a snapshot rollover on page 43 Performing a rollback recovery on page 44 Deleting a snapshot on page 45 Opening the software and connecting to a NetWorker server You must first connect to the NetWorker server on which the backup was configured to recover data. To connect to a NetWorker server: 1. From the Start menu, open the NMM client GUI: If you have opened the NMM client before, proceed to step 2. If this is the first time you have opened the NMM client, the Change NetWorker Server dialog box appears, and you can proceed to step From the Main toolbar, click the NetWorker Server icon. The Change NetWorker Server dialog box appears. 3. Click Update Server List to browse for NetWorker 7.5 SP3 or 7.6 SP1 servers. The discovery process may take a few minutes. 40 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

41 Overview 4. When the list is updated, select a server. The selection appears in the Server field. You can also type a name in the Server field. 5. Click OK. Note: You can also select Configure Options from the Options menu to connect to a NetWorker server. Selecting an item for recovery To select items for recovery, select the checkbox beside a node in the navigation tree. A check mark indicates that the node is selected. By default, all items contained in the node, such as folders and files, will also be selected for recovery. To clear an item contained in a selected node, expand the node and clear the checkbox beside the item. The check mark disappears. Figure 10 on page 41 depicts one selected item and several partially selected nodes in the navigation tree. Check mark indicates that the item is selected. Solid box indicates that some items, not all, below this node are selected Figure 10 Selected and partially selected items Searching for an item To search for a recovery item: 1. Click Search above the navigation tree. 2. In the Path field, type a directory path. 3. Optionally, in the Name field, type the name of the search item. You can refine your search as follows: Literal match (case-insensitive) Type abc to return abc, ABC, or AbC but not abcd or ABCD. Literal match (case-sensitive) Type "abc" to return abc but not ABc or abcd. Name contains (case-insensitive) Type %abc% to return abc, abcd, ABCD, or xyzabcde. Name starts with (case-insensitive) Type abc% to return abcd or ABCde but not xyzabcde. Name ends with (case-insensitive) Type %abc to return xyzabc but not ABCde. NMM client graphical user interface 41

42 Overview Single-character match search by using the? wildcard: Type? to return single character entries and drive volumes, such as C or D. Type WMI?Writer to return WMI Writer. Multiple-character match search by using the * wildcard: Type *.txt to return all entries with a.txt extension. Type * to return all items within the selected container. Type *writer* to return all writers. Search by using both the * and? wildcard Type *??I*writer* to return WMI Writer. 4. Click Search. The Details pane displays the results of the search. Specifying a recovery browse time To browse for items that were backed up on or before a particular time: 1. From the application toolbar, click the Browse calendar icon. 2. Select the arrows to select the date and time, and then click OK. The navigation tree displays backup items from the specified date and earlier. Selecting a backup version for recovery This topic applies to: DPM granular recovery System recovery Active Directory recovery operations To view the versions of an item that were backed up prior to the current browse time: 1. In the navigation tree, select a recover item. Note: Selecting an item for recovery on page 41 provides more information about selecting an item. 2. Right-click the selected item and select Versions from the pop-up menu. 3. Select the backup version to recover. 4. Select Use selected item backup time as new browse time to change the browse time to the same date as the selected backup version. 5. Click OK. The recover items displayed in the navigation tree are from the selected browse time. 42 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

43 Overview Viewing the volumes required for a recovery There are no NetWorker volumes associated with a snapshot backup until the snapshot has been rolled over to backup media. If you select to view the required volumes for a system component or application data snapshot that has not been rolled over, no volumes will be displayed. To view the volumes that are required for a recovery operation: 1. In the navigation tree, select a recover item. Note: Selecting an item for recovery on page 41 provides more information about selecting an item. 2. Right-click the selected item and select Required Volumes from the pop-up menu. The Required NetWorker Volumes dialog box appears with a list of the volumes that must be mounted: If a volume is already mounted, the device name is shown after the volume name. If a required volume is not mounted, the administrator is prompted to mount it when the recovery operation is started. 3. Click OK. Limit of eight volumes in save set for a client resource with the EMC VSS Provider There is a limit of eight volumes in a snapshot that is supported with the EMC VSS Provider. The VSS framework also limits on the number of shadow copies per volume and this limit also applies to all VSS providers, including the VSS software provider. To back up more than eight volumes for a NMM host: 1. Create separate client resources for the host and limit the save set for each client resource to eight volumes. 2. Ensure that client resources are assigned to different backup groups so that no backup group contains more than eight volumes for a particular NMM host. Note: Other hardware providers have their own limit for volumes included. Performing a snapshot rollover To rollover a snapshot: 1. Open the NMM client GUI. 2. Select the NetWorker server on which the NetWorker client was configured for backup. 3. In the left pane, select Snapshot Management. 4. In the navigation tree, select the snapshot and expand the snapshot to view the save sets. Select the snapshot or snapshot save sets to be rolled over. 5. From the Snapshot Management toolbar, click Rollover to begin the rollover operation. NMM client graphical user interface 43

44 Overview 6. In the left pane, select Monitor to view the progress of the rollover operation. Figure 11 on page 44 displays the snapshots and snapshot save sets available for rollover. Figure 11 Snapshots and snapshot save sets Performing a rollback recovery Before performing a rollback recovery, ensure that the rollback requirements have been met. Rollback recovery on page 33 provides more information about these requirements. To perform a rollback recovery: 1. Open the NMM client and select the NetWorker server on which the NetWorker client was configured for backup. 2. In the left pane, select Snapshot Management. 3. If you are performing a rollback for EMC Symmetrix configurations that use RAID5 Business Continuance Volumes (BCVs), perform the following steps: a. Delete all snapshots for the Standard EMC Disk (STD), except for the snapshot to be rolled back. Deleting a snapshot on page 45 provides information about deleting snapshots. The deletion operation will put the snapshot BCVs in the established state. Once you have completed the deletions, there should be only one snapshot BCV in the split state, and that this is the snapshot BCV that is to be rolled back. b. Use the SYMCLI commands to disassociate the BCVs and Virtual Devices (VDEVs) that are in the established state. c. If the snapshot used multiple STDs, perform the previous steps for each STD. 4. In the navigation tree, select the snapshot to be rolled back. 5. Right-click the selected snapshot and select Rollback. 6. In the left pane, select Monitor to view the progress of the rollback operation. 44 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

45 Overview 7. When rollback processing has completed, reboot the host to complete the rollback operation. 8. If you performed a rollback on an Exchange or SQL database, remount or attach the database. If you performed a rollback on a file system that had nested mount points, remount the nested mount points. Deleting a snapshot Snapshot deletion policies are typically controlled automatically through snapshot policy settings on the NetWorker server. However, you can delete a snapshot manually. For instance, if space must be made available immediately on the storage system, you can manually rollover and then delete snapshots. Note: To prevent the loss of data from a snapshot that is to be deleted, perform a rollover of the snapshot before the deletion operation. Rollover a snapshot on page 30 provides more information about rolling over a snapshot. IMPORTANT If a snapshot is deleted without the use of the NMM client user interface, the snapshot may still appear to be recoverable in the NMM client user interface. If such a snapshot is selected for recovery, the recover operation will fail. A snapshot could also be deleted by VSS or the storage subsystem if resources are exhausted due to high input/output rates on the volumes. To delete a snapshot: 1. Open the NMM client GUI. 2. Select the NetWorker server on which the NetWorker client was configured for backup. Opening the software and connecting to a NetWorker server on page 40 provides more information about opening NMM and connecting to a NetWorker server. 3. In the left pane, select Snapshot Management. 4. In the navigation tree, select the snapshot to be deleted. 5. Right-click the selected snapshot and select Delete. 6. In the left pane, select Monitor to view the progress of the delete operation. NMM client graphical user interface 45

46 Overview 46 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

47 2 Configuring a Scheduled Backup This chapter includes the following topics: Backup configuration roadmap Configuration tasks Backing up a clustered NMM client Moving a NMM client to another NetWorker server Configuring a Scheduled Backup 47

48 Configuring a Scheduled Backup Backup configuration roadmap This chapter describes the seven tasks required to configure most types of backups. Review Table 4 on page 48 to determine which tasks are required to configure your backup. Table 4 Backup tasks (page 1 of 2) Type of backup Windows volumes: Volume data such as a drive letter, for example: D:\ A file system path, for example D:\data Windows system components, such as: The registration database Windows cluster Other Window system components, as listed in Table 1 on page 27 Required action Complete tasks 1 through 7: 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page Configure a backup group on page Configure a client resource on page Configure privileges on page Configure a proxy client on page 63 Note: Specific Windows system components do not have individual save sets. The Windows system components are all backed up under the save set SYSTEM COMPONENTS:\. Note: For Windows 2008 SYSTEM COMPONENTS backups: All registry keys that are created under HKCU will not be backed up. All user settings and logs related to PerfMon will not be backed up. Microsoft application data, such as: SQL server SharePoint Exchange server System Center Data Protection Manager (DPM) Hyper-V Windows server cluster For example the save set APPLICATIONS:\SqlServerWriter NMM support on page 16 lists the specific versions supported for each of these applications. For all other applications and systems supported by NMM Complete tasks 1 through 4: 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page Configure a backup group on page 57 Continue configuration with the specific instructions for the application provided in the respective chapter in the EMC NetWorker for Microsoft Applications Release 2.3 Application Guide. Complete tasks 1 through 7: 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page Configure a backup group on page Configure a client resource on page Configure privileges on page Configure a proxy client on page EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

49 Configuring a Scheduled Backup Table 4 Backup tasks (page 2 of 2) Type of backup An NMM client that is part of a cluster An Active Directory server Required action Review the information in Backing up a clustered NMM client on page 65. Complete tasks 1 through 7: 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page Configure a backup group on page Configure a client resource on page Configure privileges on page Configure a proxy client on page 63 Complete the tasks in Chapter Microsoft Active Directory Backup and Recovery in the EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide. This section provides information on: Name resolution on page 49 Best practices and considerations for backing up application data on page 49 Name resolution NetWorker server and the NMM client machines need proper name resolution to identify and back-translate computer names, such as from name-to-ip address or IP address-to-name. Also, the NMM client uses the host machine NETBIOS or short name when connecting to the NetWorker server to browse backups. If the NETBIOS name is not found, NMM will not be able to display backups. To ensure clear communication of computer names, perform the following: 1. Add the NetWorker server name to either of the following: The local hosts file, which is located in %SystemRoot%\system32\drivers\etc. The Domain Name Server that contains the names of all servers on your network. 2. When configuring a client resource for solutions like Exchange, SharePoint, and so on, specify the NETBIOS name for the client in the Aliases attribute. The sections in Configuring a client resource for System volumes, components, and applications on page 59 describe how to enter the NETBIOS name in the Aliases attribute. Best practices and considerations for backing up application data Table 5 on page 50 lists the considerations for specifying values in the Save Set attribute for a particular client resource. Backup configuration roadmap 49

50 Configuring a Scheduled Backup Table 5 Best practices and considerations for application backups Consideration Define different schedules for protecting the following: The operating system and the file system The application that is to be backed up Installation path for application server program Copy-on-write snapshot technology versus split-mirror snapshot technology, when using CLARiiON or Symmetrix. NetWorker modules and the NMM client Microsoft SQL server data Best practice For application servers such as SQL or Exchange servers, back up the server application data under a schedule different than the host operating system data and volumes. Typically, application data is backed up several times a day while operating system data and volumes are backed up less frequently. To accomplish this: 1. Create a separate backup group, snapshot policy, and client resource for: Server application data Volumes and operating system data 2. Assign the appropriate snapshot policy and client resource to each backup group. Do not install application server program files on the same volume as the application s database files and the log files. This applies to the following hardware-based snapshots. Large databases and databases that are updated frequently, should not be saved with copy-on-write snapshot technology. Instead, use a split-mirror snapshot technology such as a CLARiiON clone or a Symmetrix BCV. Although copy-on-write technology requires less hardware resources, split-mirror technology can better handle the requirements of large or fast-changing databases. Split-mirror technology is supported only with a VSS hardware provider, such as the EMC VSS Provider. It is not provided by the built-in Microsoft System Provider. If you attempt to use both the NMM client and a NetWorker module (for example, NME or NMSQL) to back up application data, the module backups will be promoted to Full backups. Perform a Full backup of the SQL server 2005 data when the following occurs: The SQL server Writer service is disabled and SQL server 2005 backups are performed The SQL server Writer service is reenabled Performing a full backup enables you to recover all SQL server 2005 data. 50 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

51 Configuring a Scheduled Backup Configuration tasks This section outlines the NMM configuration tasks: 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page Configure a backup group on page Configure a client resource on page Configure privileges on page Configure a proxy client on page 63 Configure a backup pool for snapshot operations Snapshots create metadata that is used in the management of snapshot operations such as an instant recovery operation. Create a snapshot pool to store the save sets that contain snapshot metadata. Configuring a backup pool is a four-part process: 1. Configuring a device on page Configuring a label template on page Configuring a backup pool on page Labeling the device on page 53 Note: All of the procedures in this section must be performed on a NetWorker server release 7.3 SP3 or later. Access the NetWorker server from the Administration page of the NetWorker Management Console. The EMC NetWorker Release 7.6. Service Pack 1 Administration Guide provides more detailed information about performing the steps included here. Configuring a device Configure a media device for snapshot metadata. Configure a tape, file, or advanced file type device. For best performance, configure a file or advanced file type device so that a snapshot can be recovered without the potential delay associated with retrieving a tape. To configure a device: 1. In the NetWorker Administration page of the NetWorker Management Console, select Devices on the taskbar. 2. In the expanded left pane, select Devices. 3. From the File menu, select New. 4. In the Name attribute, replace the default name with the path and name of the device: If the device is configured on the NetWorker server s storage node, the name is the simple device path. Configuration tasks 51

52 Configuring a Scheduled Backup For example, C:\tmp\d0 for a file type device. A tape device would have a format similar to \\.\Tape0. Note: Do not use the 'temp' directory for Networker DiskBackup devices because the data will be overwritten. If the device is configured on a remote storage node, the name must indicate that the storage node is remote, by including rd= and the name of the remote storage node in the device path. For example, if the remote storage node is neptune, then the device path might be rd=neptune:c:\tmp\d0. 5. In the Comment field, specify a comment for the device. 6. From the Media Type attribute, select the appropriate media type. 7. Select the Auto Media Management attribute. 8. Click Configuration. 9. In the Target Sessions attribute, type or select a value. Set this attribute to a value that will speed up the backup, for example, Click OK. Configuring a label template Labels identify the kind of data that is stored on the volumes in a backup pool. Label templates define a naming convention for labels. Create a label template for volumes that are used to contain snapshot metadata. To configure a label template: 1. In the Administration page of the NetWorker Management Console, click Media. 2. In the expanded left pane, select Label Templates. 3. From the File menu, select New. 4. In the Name attribute, type a name that identifies the series of labels as belonging to volumes for snapshot metadata. 5. In the Comment attribute, specify a comment for the label. 6. In the Fields attribute: a. Specify a text name such as Snapshot_Metadata. b. On a separate line, specify a numeric range such as or a text range such as aa zz. Note: These attributes are used to incrementally identify each label. 7. Click OK. 52 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

53 Configuring a Scheduled Backup Configuring a backup pool To configure a backup pool to store snapshot metadata: 1. In the Administration page of the NetWorker Management Console, click Media. 2. In the expanded left pane, select Media Pools. 3. From the File menu, select New. 4. For the Name attribute, type a name that matches the label template. 5. In the Comment attribute, specify a comment for the pool. 6. Select the Enabled attribute. 7. For the Pool type attribute, select the backup pool type. 8. For the Label template attribute, select the matching label template. 9. Do not select a group in the Groups attribute. 10. Perform either of the following steps; but not both: Click the Selection Criteria tab, and specify a NMM client for the Clients attribute. A value must be typed for this attribute if you choose not to specify groups in the Groups attribute. Or For the Groups attribute, select the applicable backup groups. 11. In the Devices attribute: a. Select the device that you created in the previous step. b. Ensure that this device can accept snapshot rollovers for this pool. Labeling the device on page 53 provides details. 12. Click OK. Labeling the device Before a device can be used for snapshot backups, it must be labeled using the snapshot pool that you created in the previous step. To label a device: 1. In the Administration page of the NetWorker Management Console, click Devices. 2. In the right pane, right-click on the name of the device and select Label. 3. In the Pool attribute, select the snapshot pool that was created in the previous step. 4. Select the Mount after Labeling attribute. 5. Click OK. Configuration tasks 53

54 Configuring a Scheduled Backup Configure snapshot policies A snapshot policy determines the following: When and how often snapshots are created Number of snapshots, and if any are retained as persistent snapshots Which snapshots, if any, are rolled over to conventional storage When snapshots expire and become eligible for deletion Note: Snapshots can also be manually rolled over or deleted. Chapter 1, Overview, describes these procedures in more detail. You can specify a preconfigured policy or create a custom snapshot policy. The preconfigured snapshot policies are described in NMM client snapshot policies on page 30. Disaster recovery To protect against a disaster: As part of disaster recovery plan, back up either of the following on the application hosts: The save set All attribute in the save set field of the client Resource The SYSTEM COMPONENTS:\ save set along with the system volume, for example C:\. Ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of first, last, or all. Do not specify none. Disaster recovery can only be performed from a conventional backup. Snapshot policies for SYSTEM COMPONENTS backup To back up SYSTEM COMPONENTS, the snapshot policy must specify All in the backup snapshot field. NMM enforces this policy to ensure that a permanent backup of the snapshot exists. Attempting to restore system components from a persistent snapshot may invalidate the snapshot and leave the system in an unrecoverable state. Creating a snapshot policy To create a custom snapshot policy: 1. In the Administration page of the NetWorker Management Console, click Configuration. 2. In the expanded left pane, select Snapshot Policies. 3. From the File menu, select New. 4. In the Name attribute, type a name for the snapshot policy. 5. In the Comment attribute, type a comment for the snapshot policy. 6. In the Number of Snapshots attribute, type the number of snapshots to be created per day. The Number of Snapshots attribute works in conjunction with the Group Resource Interval and Start Time attributes. 54 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

55 Configuring a Scheduled Backup The value for the Start Time and Interval attributes must allow the specified number of snapshots to be created in a 24-hour period. For example, to take four snapshots per day and the first snapshot must occur at 4:00 a.m. (Start Time attribute), the Interval attribute must be set to five hours or less: Number of Snapshots < (24:00 - Start Time) / Interval Configure a backup group on page 57 provides additional information about Snapshots and policies. 7. In the Retain Snapshots attribute, type the maximum number of snapshots that can be retained for a specified period of time before being expired. The period of time is specified in the Snapshot Expiration Policy attribute. Note: Use a minimum Retain Snapshot value of 2. This will ensure that the most recent snapshot is retained while the new snapshot is created. A Retain Snapshot value of 1 will delete the only snapshot copy while creating the new snapshot. 8. In the Snapshots Expiration Policy attribute, select a preconfigured expiration policy to determine how long snapshots can be retained before being deleted. 9. In the Backup Snapshots attribute, specify which snapshots will be rolled over to a conventional storage medium. Valid values are All, None, First, Last, Every n.! CAUTION To protect against a disaster, ensure that all volumes and Windows system components are backed up. Also, ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of First, Last, or All. Do not specify None. Disaster recovery can only be performed from a conventional backup. If the Backup Snapshot attribute is set to None, you can still rollover the snapshot manually. Chapter 1, Overview, provides additional information about snapshots. 10. Click OK. Note: For Data Protection Manager backups the Backup Snapshot attribute must be set to All. Backup will fail if any other value is used. Snapshot policy examples This section describes snapshot policies: Conventional backup settings Four snapshots per day are taken. All snapshots are rolled over to a conventional storage medium. Each snapshot is deleted after it is rolled over. Table 6 on page 55 depicts settings for a conventional backup. Table 6 Conventional backup settings (page 1 of 2) Name Comment Conventional backup Rollover and then delete Number of snapshots 4 Configuration tasks 55

56 Configuring a Scheduled Backup Table 6 Conventional backup settings (page 2 of 2) Retain snapshots 0 Snapshot expiration policy Backup snapshots Day All Hardware instant snapshot policy Four snapshots per day are taken. Up to 8 snapshots are retained for a maximum period of 1 week. No snapshots are rolled over. Table 7 on page 56 depicts settings for an instant backup for hardware snapshots. Table 7 Hardware instant snapshot policy Name Comment Instant backup Persistent snapshots with no rollovers Number of snapshots 4 Retain snapshots 8 Snapshot expiration policy Backup snapshots Week None Hardware instant snapshot with rollover policy Four snapshots per day are taken. Up to 8 snapshots are retained for a maximum period of 1 week. Every first and third snapshots are rolled over. Table 8 on page 56 depicts settings for an instant backup hardware snapshots with rollover to a conventional medium. Table 8 Hardware instant snapshot with rollover policy Name Comment Instant and conventional backup Persistent snapshots with rollover to tape Number of snapshots 4 Retain snapshots 8 Snapshot expiration policy Week Backup snapshots Every 1 Every 3 Configure a backup schedule Backup schedules determine the days on which full or incremental backups are run. Full backups include all of the data specified in an NMM client resource save set, while incremental backups include only the data that has changed since the last backup. Table 9 on page 57 contains the considerations for configuring a backup schedule for an NMM client. This information only applies to rollover backup operations. Snapshots are always taken at full level. 56 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

57 Configuring a Scheduled Backup The procedure for creating backup schedules for an NMM client is the same as for creating a backup schedule for a regular NetWorker client. Table 9 Considerations for NMM client backup schedules Backup levels Full level Incremental backups Consideration Full level backups are supported for all types of data. Incremental level backups are supported only for: Backup of volume directories or paths such as E:\ or E:\business_files\. Backup of Microsoft Exchange server 2007 Note: Incremental level backups of Exchange server 2007 require NetWorker release 7.5 SP1 or 7.4. NetWorker 7.5 users must obtain and install the NetWorker 7.5 SP1 hotfix. Level 1 to 9 backups Level 1 to 9 backups are supported only for backup of volume directories or paths such as E:\ or E:\business_files\. Note: The information in Table 9 on page 57 applies only to rollover backup operations. Snapshots are always taken at full level. Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. Use a backup group to assign the following attributes to a set of client resources: Snapshot policy Backup start times Schedules Backup pools! IMPORTANT A client resource or backup group cannot specify volumes that use both CLARiiON and Symmetrix storage systems. For hosts that have both CLARiiON and Symmetrix volumes, create separate backup groups and client resources. Each backup group and its client resources can specify volumes from only one type of storage system. Do not create multiple instances of the same client in one backup group when configuring a backup. To configure a backup group: 1. In the Administration page of the NetWorker Management Console, click Configuration. 2. In the expanded left pane, select Groups. 3. From the File menu, select New. 4. In the Name attribute, type a name for the backup group. 5. In the Comment attribute, type a description. Configuration tasks 57

58 Configuring a Scheduled Backup 6. For the Start Time attribute, type the time when the first snapshot is to be created. Note: The value for the Start Time attributes must allow the specified number of snapshots to be created in a 24-hour period. For example, if you want to take four snapshots per day (Number of Snapshots attribute) and the first snapshot must occur at 4:00 a.m. (Start Time attribute), then the Interval attribute must be set to 5 hours or less: Number of Snapshots < (24:00 - Start Time) / Interval 7. For the Autostart attribute, select Enabled. 8. Click the Snapshot attribute so that a check mark appears beside it. 9. For the Snapshot Policy attribute, select a snapshot policy. The Number of Snapshots attribute works in conjunction with the Group Resource Interval and Start Time attributes. The value for the Start Time and Interval attributes must allow the specified number of snapshots to be created in a 24-hour period. Configure snapshot policies on page 54 provides more information about snapshot policies. 10. For the Snapshot Pool attribute, select a pool that was created for the snapshot. Configure a backup pool for snapshot operations on page 51 provides more information about pools. 11. Click the Advanced tab. 12. For the Interval attribute, specify how often a snapshot will be created. The Interval attribute works in conjunction with the backup group Start Time attribute and the snapshot policy Number of Snapshots attribute. 13. Ensure that Restart Window attribute value is less than or equal to the Interval attribute value. 14. Set the Client Retries attribute to 0 (zero). This value specifies the number of times the Networker software attempts to back up a failed client. 15. Click OK to create the backup group.! CAUTION Once you have started a snapshot of a save group, do not interrupt or halt the snapshot process. For example, in an Exchange server backup, the nsrsnap_vss_save.exe process on the production server and the eseutil process on the proxy may continue to run after the snapshot is halted. Any attempt to stop a group in NetWorker Management Console will take a long time to complete. 58 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

59 Configuring a Scheduled Backup Configure a client resource A client resource specifies what to include in a snapshot of an NMM client. Client resources are associated with other backup resources such as groups and snapshot policies. You must create multiple client resources for the same NMM client host. In this way, you can apply different backup attributes to different types of information on the same host. For example, if the NMM client host is an Exchange server: 1. Create one client resource to back up the Exchange databases. 2. Create another client resource to back up Windows system component data. This way, you can back up Exchange databases many times a day, and back up Windows system component data once a day. The general process for configuring a client resource is the same for all applications or systems. The following list describes some of the differences: System volumes and components use save sets of All, volume name, mount points, or the save set name SYSTEM COMPONENTS. System volumes and components do not use application variables. Applications use the save set APPLICATIONS:\Name of writer. Some applications backed up by NMM have settings and requirements specific to the application. These settings are specified by application variables, described in the backup sections for each application. For more information, select one of the following topics: Configuring a client resource for System volumes, components, and applications on page 59 Specifying save sets for application data on page 60 Displaying valid application data save sets on page 60 Configuring a client resource for System volumes, components, and applications The client resource configuration task is detailed in separate sections for the system volumes, components, and applications. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides details about how to configure a client resource for an application. Configuration tasks 59

60 Configuring a Scheduled Backup Specifying save sets for application data Table 10 on page 60 lists the save set syntax to specify for supported types of application data. Specify application data save sets in the Save Set attribute of a client resource. Displaying valid application data save sets on page 60 describes how to find the exact name of a particular Exchange storage group or SQL server instance and database combination. Type of backup data Table 10 Save set syntax Save set syntax DFS data (Windows server 2003 only) APPLICATIONS:\DFS Replication service writer Also back up the SYSTEM COMPONENTS:\ save set on the namespace server (usually the domain controller) that is associated with the DFS configuration. Note: In Windows server 2008, DFS Replication service writer is backed up as part of SYSTEM COMPONENTS:\. ADAM data APPLICATIONS:\ADAM (instance_name) Writer For example, the ADAM instance named AddressBook would be typed as: APPLICATIONS:\ADAM (AddressBook) Writer In Windows server 2008, Active Directory Lightweight Directory Services (AD LDS) includes the Active Directory Application Mode (ADAM) functionality provided in Windows server EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides more information about Active Directory services. Microsoft SQL server EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides more information. Active Directory Exchange server System Center Data Protection Manager 2007 SharePoint server 2007 SharePoint Portal server 2003 Hyper-V EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides more information. Displaying valid application data save sets This section describes how to find the exact name of a particular Exchange storage group or SQL server instance and database combination. To display a list of the application data save sets that are available for backup: 1. Open a command prompt on the application server. 2. From the command prompt, type one of the following commands to list the valid application data save set names: Note: If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server. If the application server is not on a virtual host, type: nsrsnap_vss_save -? If the application server is on a virtual host, type: nsrsnap_vss_save -? -c virtual_server_name where virtual_server_name is the name of the virtual host. 60 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

61 Configuring a Scheduled Backup 3. Press Enter. The application data save sets that are available for backup are listed in a format similar to the following: APPLICATIONS:\SqlServerWriter APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\master APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\model APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\msdb APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NADATA Note: Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. URL encoding for SQL and Exchange save sets When specifying save set names in the Save Set attribute of the client resource, there are cases where special characters, such as the backslash (\), must be specified by their URL-encoded values. URL-encoded values are used to represent special characters in the following cases: SQL server named instances SQL server database names Exchange storage groups Consider the following example of a SQL server named instance: The name of a SQL server named instance consists of two parts: the hostname and a unique name. The hostname and a unique name are always separated with a backslash (\) character. When specifying a SQL server named instance in the Save Set attribute, replace the backslash with its URL-encoded value, which is %5C. In the following example, a SQL server named instance that is identified as: CORPDBSERV1\YUKON would be represented in the Save Set attribute as: CORPDBSERV1%5CYUKON To back up only the database named NADATA in the SQL server named instance CORPDBSERV1\YUKON, the complete entry in the Save Set attribute would be: APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NADATA If the database name in the previous example was NA#DATA, the save set entry would be: APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NA%23DATA Configuration tasks 61

62 Configuring a Scheduled Backup Table 11 on page 62 lists the most commonly used special characters and their URL values. Table 11 Special characters and their URL-encoded values Special character URL-encoded value Special character URL-encoded value \ %5C? %3F / %2F ] %5D " %22 [ %5B % %25 } %7D # %23 { %7B & %26 ^ %5E < %3C %60 > %3E %7C Application information variable settings Table 12 on page 62 lists the variables that can be specified in the Application information attribute of the client resource. Table 12 Application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=value Specifies the snapshot service provider name. Specifies the hostname of the NMM client that moves snapshots from the NMM client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This vss value is required. For example, NSR_SNAP_TYPE=vss The local host The proxy client hostname If no value is entered, the local host is used as the data mover. If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the client resource. For serverless backups, specify a proxy client. If setting up an Exchange client resource, it is recommended that you use a proxy client. If a proxy client is specified, Exchange consistency checks are performed on the proxy client. Related messages are written to the Replication Manager log files (erm_clientxx.log) on the proxy client. If no proxy client is specified for an Exchange client resource, consistency checks are performed on the client resource host. Related messages are logged on the client resource host in both the Replication Manager log files and the nmm.raw file. 62 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

63 Configuring a Scheduled Backup Configure privileges The NMM client must be granted NetWorker administrator privileges in order to perform media database operations during snapshot deletion. If you set up a proxy client for the NMM client, grant the proxy client NetWorker Administrator privileges. If you are setting up a NMM client in a cluster, grant NetWorker administrator privileges to each cluster node and virtual server. To configure privileges: 1. In the Administration page of the NetWorker Management Console, click Configuration. 2. In the expanded left pane, click User Groups. 3. Right-click the Administrators group, and then select Properties. The Properties dialog box appears. 4. In the Users attribute, add the following values for the NMM client host. Place each value on a separate line: user=administrator,host=nmm_client_host user=system,host=nmm_client_host where NMM_client_host is the DNS hostname of the NMM client. a. If a proxy client is set up for the NMM client: Where a single user is granted administrator rights to perform all Networker functionality for a host, add the following values: user=administrator,host=nmm_clientproxy_host user=system,host=nmm_clientproxy_host Where multiple users are configured and added to an administrator group and that group is added on NetWorker privilege list. All the users under this group have administrator rights. To perform all the Networker functionality for a host, add the following values: group=administrator,host=nmm_clientproxy_host group=system,host=nmm_clientproxy_host b. If the NMM client is installed in a cluster, grant NetWorker administrator privileges to each cluster node and virtual server. 5. Click OK. All NMM users must have administrator-level privileges. Configure a proxy client A proxy client is a separate host that acts as a data mover for a NMM client. By default, the NMM client acts as its own data mover. However, a proxy client is required for serverless backups. Serverless backups free the NMM client from much of the processing involved in a snapshot backup. In a serverless backup, a snapshot is created on the NMM client and then immediately moved to the proxy client for further processing. A proxy client can also be set up on a NetWorker storage node. In this way network traffic that is generated when a snapshot is rolled over to a conventional backup medium is avoided. Configuration tasks 63

64 Configuring a Scheduled Backup Table 13 on page 64 lists the requirements for setting up a proxy client. Table 13 Configuration requirements for a proxy client Requirement Description General requirements Installation Configuration The proxy client must have the same version of the NMM client software, and operating system version and patch level, as the host for which it is acting as the proxy client. The NetWorker Module for Microsoft Applications Release 2.3 Installation Guide provides more information about installation. Create a NMM client resource for the proxy client host. Configure a client resource on page 59 provides more information about performing this task. For the NMM client resource that will use the services of the proxy client, type the proxy client host name in the: Application Information attribute Remote Access attribute Connectivity Serverless backups Rollback recovery CLARiiON Third-party hardware providers The proxy client must have connectivity between the following: NMM client NetWorker server Storage subsystem on which snapshots reside. A proxy client is required for serverless backups. Additionally, serverless backups are supported only with VSS hardware providers and depend on the capabilities of the storage subsystem. For the EMC VSS Provider, serverless backups are supported for both CLARiiON and Symmetrix storage systems. The NMM client to which the snapshot is to be rolled back must be supported with a proxy client. Overview on page 15 provides more information rollback requirements. For proxy clients using CLARiiON storage and the EMC VSS Provider, at least one CLARiiON LUN must be permanently assigned to the proxy host. Hardware providers may have additional configuration requirements for proxy clients. The vendor s product documentation provides details on these requirements. Additional requirements for an Exchange server Exchange server performance Consistency checker utility Installation path to consistency checker utility Exchange mount paths Set up a proxy client for an Exchange server. A proxy client performs the processing associated with the Exchange server consistency checker utility, eseutil.exe, thus reducing the load on the Exchange server. The Exchange server consistency checker utility, eseutil.exe, must be installed on the proxy client. The version of eseutil.exe must be of the same version (service pack level) as the Exchange server. Ensure that you install the eseutil.exe utility from the Exchange Management Tools located on the Exchange server CD. For example, if Exchange server 2003 Service Pack 2 is installed on the Exchange server, then the version of eseutil.exe that is installed on the proxy client must be from the Exchange server 2003 SP2 Management utilities. Failure to do so will cause the consistency checker utility to report errors even when the databases are valid. If the installation of the Exchange consistency checker utility, eseutil.exe, is not performed from the Exchange server installation program, ensure that the path to the eseutil.exe program is in the $PATH environment variable. Use the NSR_ALT_PATH variable to specify a path to mount snapshots on the proxy client. Application information variable settings on page 62 provides more information about these settings. 64 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

65 Configuring a Scheduled Backup Backing up a clustered NMM client To configure a virtual NMM client for backup, complete all of the tasks required to back up a regular NMM client. However, Table 14 on page 65 outlines the considerations to be aware of when setting up a virtual NMM client. Table 14 Additional steps and considerations for backing up a clustered client resource Backup task 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page 56 Consideration No special configuration is required. No special configuration is required. No special configuration is required. 4. Configure a backup group on page 57 No special configuration is required. 5. Configure a client resource on page 59 Configure a client resource for: Each virtual server that is being backed up. Each physical node in the cluster on which the virtual server might run. For each client resource, type the names of the physical nodes of the cluster in the Remote Access attribute. 6. Configure privileges on page 63 Set up NetWorker administrator privileges for: Each physical node in the cluster. Each proxy client in the cluster. 7. Configure a proxy client on page 63 If a hardware provider such as the EMC VSS Provider is being used, a proxy client must be configured for a clustered NMM client. NetWorker pathownerignore cluster functionality is not supported Do not attempt to use the pathownerignore functionality. Ensure that a nsr\bin\pathownerignore file is not used or set. This restriction is not enforced by NMM code. In some circumstances the path owner may be ignored by NMM so that the data from a clustered disk is backed up under the indices of the physical node. But recovery of that data fails. Clustered disks must be backed up under a virtual cluster client. Cluster failover and backups If a node within a cluster undergoes failover during a backup operation, the operation will fail. The next scheduled backup operation will be the next valid backup. If you are using a hardware provider such as the EMC VSS Provider, use the disk management utilities provided with the associated hardware to delete any resources that may be left in an indeterminate state as a result of the failed backup. For example, a CLARiiON storage solution may have an InActive snapshot as the result of a failed backup. In this case, use the EMC Navisphere user interface or the NaviCLI command line interface to search for and delete the inactive snapshot. Backing up a clustered NMM client 65

66 Configuring a Scheduled Backup Moving a NMM client to another NetWorker server An NMM client should be protected by only one NetWorker server. Do not set up scheduled backups for a NMM client on multiple NetWorker servers. To move a NMM client to a different NetWorker server: 1. On the NetWorker server that you are moving from, disable or delete the client resources that are set up for the NMM client. Note: You can disable a client resource for scheduled backup by clearing the Scheduled backup attribute in the client resource. 2. On the NMM client, open the NMM client software and manually delete any snapshots for the client. Deleting a snapshot on page 45 provides more information about deleting snapshots manually. Note: Before deleting the snapshots, you can manually roll them over to a conventional backup. In this way, the data in the snapshot can be recovered. 3. On the NetWorker server that you are moving to, set up scheduled backups for the NMM client. Backup configuration roadmap on page 48 provides more information about setting up scheduled backups. 66 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

67 3 NetWorker Client Management This chapter includes the following topics: Specifying a remote client for directed recovery Connecting to a NetWorker server Specifying a recovery browse time Specifying ranges for service and connection ports Specifying a password NetWorker Client Management 67

68 NetWorker Client Management Specifying a remote client for directed recovery The volume of a remote client can be recovered locally. The default client for recovery is the local client. The NMM can also recover backups created on remote client attached to the same NetWorker server as the local client. To recover a remote client requires the following: NetWorker server 7.5 SP3 or 7.6 SP1. At least two NetWorker client attached to the NetWorker server. NMM 2.3 installed on the local client. A volume backup created on the remote client. The backup must be a conventional backup, not a snapshot. To specify a remote client volume for recovery locally: 1. In the NMM client GUI, connect to the NetWorker server that hosts the remote client. 2. From the Options menu, select Configure Options. 3. Next to the Client Name, click the Refresh Clients button. The Select Viewable Clients dialog box appears. 4. In the Available clients on list, click a client and then click the Add button. The remote client appears in the Clients to list on menu bar. 5. Repeat as required for each remote client that you want available for directed recovery from this local computer. 6. Click OK to close the Select Viewable Clients dialog box. 7. Close the Configure Options dialog box. In the mail toolbar the client name now provides a list box. To recover a remote client volume: 1. From the Client list in the menu bar, select the remote client. Note: If the active panel is Snapshot Management or Monitor, a message appears to confirm that you want to cancel the current operation and navigate to the System Recover Session panel. 2. Click Yes to change clients and navigate to the System Recover Session panel. The System Recover Session Options dialog box appears. 3. In the Relocate Recovered Data box, specify the destination for the data recovered from the remote client. 68 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

69 NetWorker Client Management Connecting to a NetWorker server If the NetWorker client was configured for backup on a different NetWorker server, you can connect to that server to recover backup items for this client. To connect to a NetWorker server: 1. From the Options menu, select Configure Options. The Configure Options dialog box appears. 2. To refresh the list of available NetWorker servers, click the NetWorker Server icon beside the Backup Server Name field. Note: The Select Servers page appears while NetWorker servers are being located. When the NetWorker servers have been located, the available servers are displayed in the Select Servers dialog box. 3. Select a NetWorker server from the Select Servers dialog box and click OK. The server name is displayed in the Backup Server Name field. 4. Click OK. Note: You can also connect to a NetWorker server by clicking the NetWorker Server icon on the Application toolbar. Specifying a recovery browse time To search for only those items that were backed up on or before a particular time, specify a recovery browse time. To specify a browse recovery time: 1. From the Options menu, select Configure Options. The Configure Options dialog box appears. 2. In the Browse Time field: a. Click the arrow to select a calendar date. b. You can also type a date and time in the Browse Time field. Specifying ranges for service and connection ports A service port is a listener port that provides services to NMM Client hosts. The default range for service ports is 7937 to A connection port is used to contact a service, whether it is on a NetWorker server, storage node, or client. The default range for connection ports is 0 0. To implement an enhanced security environment, it may be necessary to reduce the range of available ports. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides more information about determining the size of the port range. Connecting to a NetWorker server 69

70 NetWorker Client Management To reduce the range of available ports: 1. From the Options menu, select Configure Options. The Configure Options dialog box appears. 2. In the Service Ports attribute, type the range of available ports. 3. In the Connection Ports attribute, type the range of available ports. 4. Click OK. Note: If a firewall exists between the NetWorker client and any NetWorker servers, ensure that the firewall is configured to accept the port ranges typed in the Configure Options dialog box. The Configuring TCP Networks and Network Firewalls for EMC NetWorker Technical Note available on Powerlink provides more information on how to identify and configure the required ports for NetWorker hosts that need to communicate across a packet filtering or stateful inspection firewall. Specifying a password The password is used to protect items that will be backed up with either PW1 password-protection, or PW2 encryption and password-protection. PW1 and PW2 protection is enabled on the NetWorker server with a local or global directive. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides more information about PW1 and PW2 protection. IMPORTANT Changing the password does not change the password for files that have already been backed up. To recover PW1 or PW2 password-protected files, you must provide the password that was in effect at the time of the backup. To change the PW1 password: 1. From the Options menu, select Configure Options. The Configure Options dialog box appears. 2. In the Old password attribute, type the password that is currently in effect. 3. In the New password attribute, type the new password. 4. In the Confirm password attribute, retype the password. 5. Click OK. The new password will be applied to future scheduled backups for the NMM Client where password-protection has been enabled with a global or local directive. 70 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

71 4 Deduplication Backup and Recovery with Avamar This chapter includes the following topics: Data deduplication with Avamar Avamar integration in NMM Supported and unsupported applications, features, and configurations Related documentation about Avamar server and NetWorker server Avamar and NetWorker server configuration Deduplication backups requirements for NetWorker server Configuring a client resource for deduplication backup Querying deduplication save sets by using mminfo Recovering deduplicated data Deleting deduplication save sets Deduplication Backup and Recovery with Avamar 71

72 Deduplication Backup and Recovery with Avamar Data deduplication with Avamar IMPORTANT Because the data deduplication with Avamar process in NMM requires Avamar and NetWorker installation and configuration, it is recommended that you review the documentation listed in Related documentation about Avamar server and NetWorker server on page 75 for details about Avamar and NetWorker installation and configuration. NetWorker deduplication, which leverages Avamar Data Stores, solves the challenges associated with traditional backup, enabling fast, reliable backup and recovery for remote offices, and data center LANs. Data deduplication is a key feature of the Avamar system. Data deduplication ensures that each unique sub-file, variable length object is stored only once across sites and servers. During backups, the Avamar client software examines the client file system and applies the data deduplication algorithm that identifies redundant data sequences and breaks the client filesysytem into sub-file, variable length data segments. Each data segment is assigned a unique ID. The client software then determines whether or not this unique ID has already been stored on the Avamar server. If this object resides on the Avamar server, a link to the stored object is referenced in this backup. After an object has been stored on the server, it is never resent over the network, no matter how many times it is encountered on any number of clients. This feature greatly reduces network traffic and provides for enhanced storage efficiency on the server. Key deduplication differentiators are: Deduplicates backup data at the source, before data transfer across the network Enables fast, daily full backups across existing networks and infrastructure Reduces required daily network bandwidth dramatically by identifying redundant data at source Up to 10 times faster backups Data encrypted in flight and at rest Patented RAIN technology provides fault tolerance across nodes and eliminates single points of failure Scalable grid architecture Global data deduplication reduces total backup storage by up to 50 times Recoverability verified daily no surprises Centralized web-based management Simple one-step recovery Flexible deployment options, including EMC Avamar Data Store package Data deduplication replaces multiple copies of the same data scattered across networks with a reference to a single instance or source for the data. Edited files also have tremendous redundancy with previous versions. 72 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

73 Deduplication Backup and Recovery with Avamar Table 15 on page 73 provides a a rough comparison of deduplication and non-deduplication backups and recovery. All estimates are relative and approximate. Recovery time estimates are for save set recovery operations. Table 15 Backup and recovery schedule comparison Backup type Full initial backup Subsequent daily, full backups Subsequent daily, incremental backups (with a weekly full) Data recovery time after 1 week Non-deduplication x hours x hours 1/10 x hours 1.6 to 2.0x, if the full backup and all incremental backups were restored. Deduplication, daily full Deduplication, daily incremental x hours 1/5 x hours - Less than or equal to x (only one backup need be restored). x hours 1/20 x hours to 2.0x, if the full backup and all incremental backups were restored. Avamar integration in NMM The integration of Avamar in NMM provides deduplication for Microsoft applications through the familiar NetWorker features and GUI. This integration provides the ability to: Configure deduplication for a NMM client resource in NetWorker Management Console (NMC) The deduplication backup settings are part of the client resource configuration GUI. It is as simple as selecting a checkbox to enable deduplication, and then selecting the deduplication server. Perform deduplication backup at snapshot rollover time When deduplication is selected in the client resource, NMM automatically performs deduplication during the backup no separate or additional user input is required to perform deduplication. Perform deduplication recover during the rollover The process for recovering data from a deduplication node is basically the same as that for recovering from a storage node. File and data sizes vary between applications, so Avamar optimizes compression by analyzing the data in the save set and by using the best chunking size for that data. NMM supports deduplication with Avamar on the following operating systems: Windows server 2008 (x86, x64) Windows server 2003 R2 (x86, x64) Windows server 2003 (x86, x64) Avamar integration in NMM 73

74 Deduplication Backup and Recovery with Avamar Supported and unsupported applications, features, and configurations The EMC Information Protection Software Compatibility Guide, available on the EMC Powerlink website contains additional and the most up-to-date information about NMM compatibility. This section provides information on: Supported applications and configurations on page 74 Unsupported applications, features, and configurations on page 75 Supported applications and configurations NMM supports deduplication on the following: Microsoft applications SQL server 2008 (x86, x64) SQL server 2005 (x86, x64) SQL server 2008 R2 SharePoint server 2007 (x86, x64) SharePoint server 2003 (x86, x64) SharePoint server 2010 Exchange server 2007 (x64) Exchange server 2003 (x86) Exchange server 2010 Windows server 2008 with Hyper-V Windows server 2008, Microsoft server Core Installation, with Hyper-V System Components and File System Windows SharePoint Services 3.0 Windows SharePoint Services 2.0 Active Directory Configurations System Provider Hardware Provider: Proxy Backup Configurations Cluster configurations are supported for the operating systems, applications, and configurations in the preceding lists. 74 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

75 Deduplication Backup and Recovery with Avamar Unsupported applications, features, and configurations NMM does not support deduplication for the following applications, features, and configurations: Applications: Active Directory granular System Center Data Protection Manager 2007 NetWorker features: Cloning/Staging AES Encryption Compression Windows configurations: EFS File Systems Related documentation about Avamar server and NetWorker server Extensive documentation for the Avamar server and NetWorker server setup and configuration is available for download at The EMC white paper Efficient Data Protection with EMC Avamar Global De-duplication Software provides a technical overview of EMC Avamar backup and recovery software. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide describes creating a deduplication storage node, replication nodes, and other NetWorker deduplication features and services. The EMC Avamar 4.1 System Administration Manual describes how to administer an operational Avamar 4.1 system following successful installation, setup, and configuration. Additional NetWorker server deduplication operation information Additional deduplication operation information is available in the following NetWorker features: Backup statistics basic reports Events The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide describes the deduplication information provided by these features. Avamar and NetWorker server configuration Before a NMM backup client can be configured to use Avamar deduplication, the Avamar server and NetWorker server must be installed to receive deduplication data and process backups. The following topics provide the required information: Configure the Avamar and the NetWorker server to receive deduplication data and process backups on page 76 Set the DNS resolution for NetWorker deduplication node and NMM on page 76 Related documentation about Avamar server and NetWorker server 75

76 Deduplication Backup and Recovery with Avamar Configure the Avamar and the NetWorker server to receive deduplication data and process backups To configure Avamar and the NetWorker server to receive deduplication data and process backups: 1. Set up and configure the Avamar server. The Avamar hardware and software documentation provides information on Avamar setup and configuration. 2. Create deduplication nodes and replication nodes on the Avamar server: Perform this task through the Avamar user interface. The Avamar documentation provides detailed information. 3. Configure deduplication node and replication node settings on the NetWorker server: Configure the deduplication node through the NetWorker server s Administration interface. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides more information about configuring the deduplication node. 4. Create a replication node for a deduplication node, if required by the NetWorker deduplication node for automatic failover of data backup nodes. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides details. Set the DNS resolution for NetWorker deduplication node and NMM The NetWorker deduplication node and the NMM hosts require a DNS resolution between nodes. Note: The NMM hosts include one or more of the following: NMM client, NMM proxy client, or the NMM proxy storage node. DNS resolution must be working prior to starting deduplication backups: On the NMM hosts, ensure the hosts have DNS name resolution for the NetWorker Deduplication Node.: If the NMM hosts do not have DNS resolution for the NetWorker Deduplication Node, then that needs to be repaired. Check your operating system documentation for information on how to fix DNS resolution problems. On the NetWorker Deduplication Node, ensure it has DNS name resolution to the NMM hosts: If the NetWorker Deduplication Node does not have DNS resolution for the NMM hosts, then that needs to be repaired. Check your operating system documentation for information on how to fix DNS resolution problems. 76 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

77 Deduplication Backup and Recovery with Avamar Deduplication backups requirements for NetWorker server All typical client operations, such as adding, deleting, and drag-and-drop, work the same for deduplication clients as they do for other types of clients. A deduplication save set is treated as a regular NetWorker save set, although it actually has two parts: metadata (hash info) and the backed-up client data. Only the metadata is stored on a NetWorker storage node. The backed-up client data is stored on a deduplication node (Avamar server). The metadata can be cloned in the usual manner, while a copy of the backed-up data can be replicated on another deduplication node. When configuring a NMM client resource for deduplication, there are several special requirements or considerations. The following topics provide more information: Backup levels and schedules for deduplication clients on page 77 Retention policies on page 78 Backup configuration notes on page 78 Backup levels and schedules for deduplication clients When a NMM deduplication client is backed up for the first time after deduplication has been enabled, a full backup of the client data must be performed. Subsequent backups of the client then take advantage of deduplication to back up only those data segments that have changed since the previous backup. The exception to this is that full deduplication backups always include a complete backup of the index. Note: If the deduplication node for an existing deduplication client is changed or if another type of client is upgraded to a deduplication client, a new full backup of the client data must be performed, regardless whether the most recent backup performed was a full backup. The initial full backup of a deduplication client takes longer than a regular backup of the same client data due to the initial overhead involved in deduplicating the data. All subsequent deduplication backups benefit from the fact that now only the data segments (not files) that have changed since the previous backup will be backed up. However, the choice of subsequent backup levels, depends on what is more important to the user: backup performance or recovery performance. Deduplication clients should use backup schedules that support that priority. Deduplication backups must be scheduled to avoid the deduplication node's read-only periods, when such cron jobs as checkpoint and garbage-collection are run. The Avamar server documentation provides instructions on how to perform the following: Initial full backup followed by daily (Level 1) incremental backups Faster backups, longer recoveries: This schedule benefits an environment in which the speed of the backup is most important. The daily incremental (Level 1) deduplication backups will take significantly less time than daily regular incremental backups and even less time than daily full deduplication backups. After 1 week of backups, this schedule results in slightly longer recovery times, due to the latency involved in restoring seven backup images (the initial full backup, followed by applying each incremental backup to the full backup). Deduplication backups requirements for NetWorker server 77

78 Deduplication Backup and Recovery with Avamar Initial full backup followed by daily full backups Longer backups, faster recoveries: This schedule benefits an environment in which the speed of data recovery is most important. After the initial full backup, daily full deduplication backups take only slightly longer than regular daily incremental backups. After 1 week of backups, this schedule results in much shorter recovery times, since only a single backup image must be recovered. Retention policies If a volume contains one or more deduplication save sets, the resource for the deduplication node that was used to create the backup must exist when the save sets pass their retention policy. If the resource for the deduplication node has been deleted, the volume cannot be made recyclable or relabeled. Furthermore, when deduplication save sets pass their retention time, the NetWorker server will begin the process of deleting the deduplicated data from the deduplication node. Therefore, deduplication data may not be recoverable by using the scanner program after the deduplication save set has passed its retention time. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides more information about Retention Policies, and the save set recover and scanner programs. Backup configuration notes The following notes are described in more detail in the EMC NetWorker Release 7.6 Service Pack 1 Administration Guide: Do not place both regular and deduplication clients in the same groups. Ensure that all deduplication clients in the same group have the same deduplication node setting. Directives cannot be applied if deduplication is used for a client. Media pools do not apply when deduplication is used. The cloning of deduplication backups is handled differently from that of regular backups. Only the metadata is stored on a NetWorker storage node, while the backed up data is stored on a deduplication node. An alternate method is available to handle tape backups of the deduplication client data: 1. Create a second instance of the client to be backed up.! IMPORTANT Do not configure the second instance as a deduplication client. 2. If you are using multiple backup schedules, ensure that the backup level is set to full for all groups. This is required because the backup level and the last backup time are calculated by using both the group name and save set name, and the groups would interfere with each other. 78 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

79 Deduplication Backup and Recovery with Avamar Configuring a client resource for deduplication backup When NMM is installed, it automatically includes support for deduplication. You do not need to install anything extra on the NMM client. After the Avamar server and NetWorker server have been configured for deduplication, configure a client resource to use deduplication. After creating a deduplication node as described in the EMC NetWorker Release 7.6 Service Pack 1 Administration Guide, configure a NetWorker deduplication client. You can use either of these workflows: Create a new client resource, enable deduplication, and then configure the client Resource with the application-specific settings for whichever Microsoft application that you want to back up. Edit an existing client resource, for example, a NMM client resource that you previously created for Microsoft SQL server backup. Note: You can use this procedure for configuring deduplication for any client resource listed in Supported and unsupported applications, features, and configurations on page 74, except for configuring deduplication for an Exchange client running on a passive node in a CCR environment, which is described in the EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide. To configure a deduplication backup for any client resource: 1. On the NetWorker server, open the NetWorker Management Console, open the NetWorker Administration window, and then click Configuration. 2. Select Clients in the navigation tree. The Clients table appears and it lists any clients that have already been created: To add a new client resource, right-click Clients in the navigation tree or right-click any client in the Clients table, and then select New. The Create Client window appears. To edit an existing client resource, right-click the client in the Clients table, and then select Properties. The Properties window appears. 3. On the General tab, type the information for any client, with the following exceptions: The Name of the client must be a computer qualified to be a NetWorker deduplication client: The computer must run an operating system that supports deduplication. The Name must be a Fully Qualified Domain Name (FQDN). In the Backup area: Ensure that the deduplication client has been assigned to a group that contains only deduplication clients. Do not mix regular and deduplication clients within a group. Configure a backup group on page 57 provides information about creating backup groups. Configuring a client resource for deduplication backup 79

80 Deduplication Backup and Recovery with Avamar A recommended backup schedule for deduplication clients depends on whether your priority is faster backups or faster, less complicated recoveries. Configure a backup schedule on page 56 provides general information about setting backup schedules. Backup levels and schedules for deduplication clients on page 77 provides backup level and schedule information that is specific to deduplication clients. 4. The parallelism attribute in the client resource has no effect for NMM deduplication clients. By default, NMM uses client parallelism set to 4 for all deduplication clients. Because deduplication backups require more CPU and memory resources on the host where the backup is performed, it might be necessary to reduce the client parallelism for configurations with either a large number of save sets, or a large number of volumes. Note: For deduplication clients, NMM will not support a parallelism of greater than 4. If NSR_PS_SAVE_PARALLELISM is set to above 4, NMM automatically reduces the parallelism to 4. To reduce the client parallelism, in the Application Information field, use the NSR_PS_SAVE_PARALLELISM variable. For example, to set parallelism to 1, type the following: NSR_PS_SAVE_PARALLELISM=1 Note: NMM might report the NSR_PS_SAVE_PARALLELISM as an unknown parameter, however this warning can be ignored. 5. Click the Apps & Modules tab. 6. In the Access area, leave the Remote user and Password fields empty. 7. In the De-duplication area, select the De-duplication backup attribute to enable this client for deduplication backups. Figure 12 Deduplication backup attribute 80 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

81 Deduplication Backup and Recovery with Avamar 8. From the De-duplication node menu, select the name of the deduplication node to which this client s backup data will be sent. This is the deduplication node created in Configure the Avamar and the NetWorker server to receive deduplication data and process backups on page 76. Note: All clients in a group must have the same deduplication node value. This step links this client with its own deduplication node. Do not select the name of a replication node here.! IMPORTANT If the deduplication node for this client s backup data changes, the next backup done must be a level 0 (full) backup. 9. Complete the remaining configuration information as for any regular client. Configuring a client resource for System volumes, components, and applications on page 59 lists the application-specific client resource configuration procedures for each System or application backup. Querying deduplication save sets by using mminfo You can use the mminfo program to query information about save sets created by using deduplication. To limit the output of mminfo to only those save sets created by using deduplication, use the -q dedupe option. For example, to query deduplication save sets for the local host, use the following command: mminfo -S -q dedupe Be aware that this command does not list the following: Empty save sets Save sets in which nothing was backed up as the result of a skip schedule These save sets are treated as regular save sets, not as deduplicated save sets. Recovering deduplicated data The process for recovering data from a deduplication node is basically the same as that for recovering from a storage node. However, there is an underlying difference in where the information is kept. Only the metadata, which is hash information, is stored (or cloned or staged) on a NetWorker storage node. The backed-up data from a deduplication client is stored on a deduplication node that is an Avamar server. Both the deduplication node and the volume on the recovered side must be online during the recovery of deduplicated data. Note: Under some conditions, if recovery from the primary deduplication node fails, autorecovery will use a replication node. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides detailed information about recovery from a replication node. Querying deduplication save sets by using mminfo 81

82 Deduplication Backup and Recovery with Avamar Deleting deduplication save sets The process for deleting deduplication save sets is performed on the NetWorker and Avamar servers, and is described in the EMC NetWorker Release 7.6 Service Pack 1 Administration Guide. 82 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

83 5 Deduplication Backup and Recovery with Data Domain This chapter includes the following topics: Data deduplication with Data Domain Data Domain integration in NMM Supported applications, features, and configurations Related documentation about Data Domain and NetWorker server Data Domain and NetWorker configuration Configuring client resource for Data Domain Boost backups Recovering deduplicated data Deduplication Backup and Recovery with Data Domain 83

84 Deduplication Backup and Recovery with Data Domain Data deduplication with Data Domain IMPORTANT As the data deduplication process in NMM with Data Domain requires Data Domain and NetWorker installation and configuration, you must review the documentation listed in Related documentation about Data Domain and NetWorker server on page 86 for details about Data Domain and NetWorker installation and configuration. The Data Domain distributed segment processing feature allows backup data to be deduplicated on NetWorker storage node or NMM 2.3 client before it is sent for storage on a Data Domain system. It also enables multiple concurrent storage and recovery operations on the storage devices, unlike virtual tape library (VTL), and CIFS or NFS Advanced File Type Device (AFTD) conventional disk file system interfaces. These capabilities dramatically reduce the amount of data sent to be stored on the NetWorker Data Domain device and reduce the need for large bandwidths to the storage device. Data Domain integration in NMM NMM 2.3 leverages EMC NetWorker 7.6 SP1 integration with EMC Data Domain to offer the following features: NetWorker Data Domain storage devices Deduplicated data backups are stored on special NetWorker Data Domain storage devices that are accessed by the NetWorker storage node. Each device represents a storage unit and is associated with a named storage volume. Each device appears as a folder on the Data Domain system. Optimized cloning NMM 2.3 Data Domain optimized cloning will enable Data Domain based backups to clone faster on another Data Domain appliance by using fast cloning method through DD Boost (DD Boost library). Data domain Boost NMM 2.3 client-side IO optimization through NetWorker Data domain boost capability enables less data to be passed through the network during NMM backup, which results in faster backups. The NMM Data Domain integration requires the following software: NetWorker server 7.6 SP1 or later NetWorker storage node 7.6 SP1 or later NetWorker client 7.6 SP1 or later Data Domain Appliance with Data Domain OS version supported by NetWorker client installed on NMM 2.3 host Data Domain OS 4.8 or later for DD Boost functionality The supported operating systems are: Windows 2003 (x86, x64) Windows 2003 R2 (x86, x64) Windows 2008 SP2 (x86, x64) Windows 2008 R2 (x64) 84 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

85 Deduplication Backup and Recovery with Data Domain Supported applications, features, and configurations The EMC Information Protection Software Compatibility Guide, available on the EMC Powerlink website contains additional and the most up-to-date information about NMM compatibility. Data Domain deduplication support The Data Domain deduplication is supported for the following Microsoft applications: SQL server 2008 R2 (x64) Exchange 2003 Exchange 2007 Exchange server 2010 (x64) SQL server 2005 SQL server 2008 SharePoint 2007 (VSS based) SharePoint 2010 Active Directory DPM server Hyper-V Data Domain Boost on NMM support The Data Domain Boost on NMM client is supported for the following Microsoft applications VSS based backups: Exchange server 2010 (x64) SharePoint server 2010 SQL server 2008 R2 (x64) The Data Domain Boost on NMM client is not supported for the following Microsoft applications: Exchange 2003 Exchange 2007 SQL server 2005 SQL server 2008 SharePoint 2007 (VSS based) SharePoint 2010 Active Directory DPM server Hyper-V Supported applications, features, and configurations 85

86 Deduplication Backup and Recovery with Data Domain Related documentation about Data Domain and NetWorker server Extensive documentation for the Data Domain server and NetWorker server setup and configuration is available for download at EMC NetWorker Data Domain Deduplication Devices 7.6 SP1 Integration Guide EMC NetWorker 7.6 Service Pack 1 Administration Guide Documentation related to the use of Data Domain systems can be found at the Data Domain Support Portal (support account required), including: Data Domain Software Release 4.8 Release Notes Data Domain Administration Guide Data Domain Command Reference Data Domain CLI Guide Data Domain System Hardware Guide Installation and Setup Guide for each Data Domain system Data Domain Initial Configuration Guide Data Domain and NetWorker configuration Configuration, monitoring, and reporting of backup and restore operations on NetWorker Data Domain devices is provided by the NetWorker Management Console (NMC) portal. The NMC server is accessible from any supported remote Internet browser. The NMC Device Configuration Wizard simplifies the configuration of storage devices, backup clients, storage (target) pools, volume labeling, and save set cloning. Table 16 on page 86 provides the configuration details for Data Domain and NetWorker. Table 16 Configuration details for Data Domain and NetWorker (page 1 of 2) Feature Data Domain and NetWorker Consideration Optimized cloning NMM 2.3 Data Domain optimized cloning enables Data Domain based backups to clone faster on another Data Domain appliance by using fast cloning method by using DD Boost (DD Boost library). No special procedures or considerations are required for Data Domain optimized cloning by NMM 2.3. The EMC NetWorker 7.6 Service Pack 1 Administration Guide and the EMC NetWorker Data Domain Deduplication Devices 7.6 Service Pack 1 Integration Guide provide details. 86 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

87 Deduplication Backup and Recovery with Data Domain Table 16 Configuration details for Data Domain and NetWorker (continued) (page 2 of 2) Feature Data Domain and NetWorker Consideration Data Domain storage node Client-side IO optimization (Data Domain Boost) NMM 2.3 provides support for back up to Data Domain device with NetWorker storage node integration with DD Boost (DD Boost library) interface. NMM 2.3 provides support for client-side IO optimization or Data Domain Boost with NetWorker 7.6 SP1 Data Domain integration. NMM 2.3 client-side IO optimization that uses the NetWorker Data Domain Boost capability enables NMM backups to pass less data through network which result in faster backups. NMM 2.3 Data Domain integration requires the following software: NetWorker server version 7.6 SP1 or later NetWorker storage node version 7.6 SP1 or later NetWorker client version 7.6 SP1 or later PowerSnap version 2.5 SP1 or later Data Domain Appliance with Data Domain operating system version supported by NetWorker client installed on NMM version 2.3 host. No special procedures or considerations are required for Data Domain storage node by NMM version 2.3. The EMC NetWorker 7.6 Service Pack 1 Administration Guide and the EMC NetWorker Data Domain Deduplication Devices version 7.6 Service Pack 1 Integration Guide provide details. Configuring client resource for Data Domain Boost backups on page 87 provides more information. Configuring client resource for Data Domain Boost backups When NMM is installed, it automatically includes support for deduplication. You do not need to install anything extra on the NMM client. For Data Domain Boost backup, ensure that the device used is a Data Domain Boost device and that the appropriate enabler has been applied. After configuring a Data Domain-based storage node and device as described in the EMC NetWorker Data Domain Deduplication Devices 7.6 SP1 Integration Guide, configure a NetWorker deduplication client. After the Data Domain server and NetWorker server have been configured for deduplication, configure a client resource to use deduplication. A storage node, configured with at least one Data Domain Boost device, must exist for client-side IO optimization to be possible. You can use either of these workflows for a NetWorker deduplication client: Create a new client resource, and then configure the client resource with the application-specific settings for the Microsoft application that you want to back up. Edit an existing client resource, for example, a NMM client resource that you previously created for Microsoft SQL server backup. Configuring client resource for Data Domain Boost backups 87

88 Deduplication Backup and Recovery with Data Domain To configure a Data Domain Boost backup for any client resource: 1. On the NetWorker server, open the NetWorker Management Console > NetWorker Administration window, and then click the Configuration button. 2. Select Clients in the navigation tree. The Clients table appears and it lists any clients that have already been created: To add a new client resource, right-click Clients in the navigation tree or right-click any client in the Clients table, and then select New. The Create Client window appears. To edit an existing client Resource, right-click the client in the Clients table, and then select Properties. The Properties window appears. 3. On the General tab, type the information for any client, with the following exceptions: The Name of the client must be a computer qualified to be a NetWorker deduplication client: The computer must run an operating system that supports deduplication. The Name must be a FQDN. In the Backup area: Ensure that the deduplication client has been assigned to a group that contains only deduplication clients. Do not mix regular and deduplication clients within a group. Configure a backup group on page 57 provides information about creating backup groups. A recommended backup schedule for deduplication clients depends on whether your priority is faster backups or faster, less complicated recoveries. Configure a backup schedule on page 56 provides general information about setting backup schedules. Backup levels and schedules for deduplication clients on page 77 provides backup level and schedule information that is specific to deduplication clients. 4. Click the Apps & Modules tab. 5. In the Access area, leave the Remote user and Password fields empty. 6. In the Application Information field, add the following parameters: NSR_DIRECT_ACCESS=Yes/No/Default where: Yes is for DISK_ONLY, which means that the data travels directly to Data Domain appliance. No is for STORAGE_NODE, which means data travels to the Data Domain appliance through the NetWorker storage node. Default is for undefined, which means that NMM ignores this parameter and NetWorker decides about the media type based on client configuration. NSR_DEVICE_INTERFACE=DATA_DOMAIN where, DATA_DOMAIN enables NetWorker for Data Domain based backups. 88 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

89 Deduplication Backup and Recovery with Data Domain! IMPORTANT Do not select the Data Domain option when configuring the client resource. Backup fails if the Data Domain option is selected. 7. Select Globals (2 of 2) tab of the client configuration and provide the remote storage node name where the DD device is configured. This should be the first or only entry. During backup, the NMM 2.3 client contacts this storage node to obtain the DD device credentials. It then establishes connection using these credentials and sends data directly to the DD system. 8. Complete the remaining configuration information as for any regular client. Configuring a client resource for System volumes, components, and applications on page 59 lists the application-specific client resource configuration procedures for each System or application backup. 9. To verify if a backup is successful, use the following command: mminfo -avot -s <server name> -c <client name> where: server name is the name of the NetWorker server client name is the name of NMM client Recovering deduplicated data The process for recovering data from a Data Domain deduplication system is basically the same as that for recovering from a traditional storage node. The backed up data from a client is stored in a deduplicated state on the Data Domain device. Both the storage node and the Data Domain system must be online during the recovery of deduplicated data. The above is also valid for data that has been backed up using the client side IO feature. Recovering deduplicated data 89

90 Deduplication Backup and Recovery with Data Domain 90 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

91 6 Multihomed setup for backup and recovery This chapter includes the following topics: Overview Basic requirements for setting up a multihomed environment Generic requirements for setting up a multihomed environment for NMM backups Requirements for multihomed NMM client's network configuration Requirements for multihomed NetWorker server's network configuration Requirements for network configuration on NetWorker storage node Configuring NMM client resources in a multihomed environment Multihomed setup for backup and recovery 91

92 Multihomed setup for backup and recovery Overview In a multihomed environment, NMM backs up data by using Microsoft VSS technology and writes to a backup device like Avamar or Data Domain, by using a dedicated backup LAN instead of production LAN. Backing up NMM in a multihomed environment helps avoid contention between the application traffic and backup traffic. Note: For cluster virtual clients, the connection from NetWorker server is initiated on the production network. But the backup payload flows through the backup network. In a multihomed environment, NMM 2.3 supports backup and recovery for the following Microsoft applications: Exchange SQL Share Point Hyper-V DPM Basic requirements for setting up a multihomed environment Ensure that the following requirements are taken care of when setting up a multihomed environment: A computer has multiple NICs Each NIC is configured with only one IP address The IP belonging to any specific NIC resides in a separate subnet or VLAN The IP should resolve to one unique hostname per NIC Generic requirements for setting up a multihomed environment for NMM backups Review the following requirements when setting up a multihomed environment for NMM backups: All the hosts, like NetWorker server, storage node, or client, participating in the backup must have at least one NIC configured with an IP address on the backup subnet. This NIC is called the backup NIC. The IP subnet or VLAN through which the backup traffic is meant to pass is called the backup subnet. The IP address, which is configured on backup NIC, is called backup IP. The backup IP on any host must always resolve to a backup LAN FQDN. This IP address to hostname mapping can be implemented in various ways: By creating an entry for the backup IP on a backup domain. The backup domain is a domain that offers a mechanism to identify backup IPs by names. Examples of where and how to configure a backup domain are: Backup domain can be a separate domain hosted on an exclusive DNS server on the backup subnet. 92 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

93 Multihomed setup for backup and recovery A zone configured on existing DNS server accessible from NMM client. This may require customized configurations in the DNS server depending on the status of the DNS server, if the DNS server is separate or if the preexisting DNS server being used for multi-nic configuration. Note: Ensure that any FQDN being used in NetWorker backup is mapped to only one IP address at a time on the DNS server. Sample network topology of multihomed environment for backup By updating etc\hosts file with the IP to FQDN mapping. There can be several ways of setting up your multihomed environment. Figure 13 on page 93 is an example of how a NetWorker multihomed environment can be set up for backup. In this example, the NetWorker server authenticates the client through the production network, but uses the backup LAN for the data transfer. Storage Node Backup Lan NetWorker Server Production Management Lan NetWorker Client GEN Figure 13 Sample network topology of NetWorker multihomed backup Generic requirements for setting up a multihomed environment for NMM backups 93

94 Multihomed setup for backup and recovery Requirements for multihomed NMM client's network configuration Review the following requirements before configuring the NetWorker client s network in a multihomed environment: The bind order of network interfaces must be as follows: Production NIC Private NIC, if any, in case of Windows cluster Backup NIC Modify the bind order, if required. To modify the bind order: a. Go to Start > Settings > Control Panel > Network Connections. b. In the NetWork Connections dialog box, select Advanced > Advanced Settings. c. Reset the order of the connections. For each NIC, set the following: DNS server address as the only corresponding DNS server IP address. There should always be one entry per NIC and that is the DNS server IP of the domain where this backup IP has an entry. For example, if the DNS server of backup-domain.com is hosted on , the backup NIC on NMM client should have only one entry, that is DNS suffix for this connection as the corresponding suffix.! IMPORTANT Ensure not to use the Append these DNS suffixes (in order) attribute. To configure these settings: a. Go to Start > Settings > Control Panel > Network Connections. b. Right click on Network Connections, select Properties. Requirements for multihomed NetWorker server's network configuration Review the following requirements before configuring NetWorker server s network in a multihomed environment: The minimum requirement is that the NetWorker server must have a backup IP, which is essentially an IP address for a NIC on backup subnet. This backup IP should also resolve to a unique FQDN on backup domain. The backup NIC configuration on NetWorker server should follow the guidelines in Requirements for multihomed NMM client's network configuration on page 94. If a NMM client is a cluster virtual server and is identified by an FQDN in production domain, the NetWorker server must have access to the production subnet through another NIC. The NetWorker server should be able to resolve the production FQDN of cluster virtual server. In such cases, the NetWorker server needs at least two NICs, one on backup subnet and the other on production subnet. 94 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

95 Multihomed setup for backup and recovery Requirements for network configuration on NetWorker storage node The only requirement for a NetWorker storage node is a backup IP, which is essentially an IP address for a NIC on backup subnet. This backup IP should also resolve to a unique FQDN on backup domain. The backup NIC configuration on NetWorker storage Node should follow the guidelines in Requirements for multihomed NMM client's network configuration on page 94. Configuring NMM client resources in a multihomed environment Perform the following steps when configuring NMM client resources in a multihomed environment: 1. Create non-clustered clients with backup domain FQDN, for example, nmmclient.backupdomain.com. 2. Update each client resource, for NetWorker server, NetWorker storage node, or NMM client, with corresponding hostname entry in the Alias attribute of Globals (1 of 2) tab in NMM client. The production domain FQDN should be present in the aliases list. 3. Ensure that all clients have Server network interface attribute as the backup domain FQDN of NetWorker server in Globals (1 of 2) tab. 4. Create a NMM client for cluster virtual server with either NetBIOS name or production domain FQDN. If using the NetBIOS name, ensure that NetBIOS over TCP/IP is enabled for the production NIC on NetWorker server. 5. Ensure that all clients have Storage nodes: attribute set to backup domain FQDN of the storage nodes in Globals (2 of 2) tab. To perform a configuration check for multihomed NetWorker backup: Ping for hostnames of NetWorker server, storage node, or client, or more precisely the FQDNs corresponding to NICs participating in backup, to resolve and reach the correct IP address from one host to another. Check the DNS server s records. For each multi-nic FQDN, there is mapping for FQDN to IP address in DNS server's record. Requirements for network configuration on NetWorker storage node 95

96 Multihomed setup for backup and recovery 96 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

97 7 Windows System Backup and Recovery This chapter includes the following topics: Overview Performing system backups Performing a recovery Recovering file system snapshots that have not been rolled over Booting the NMM host in Directory Service Restore mode Performing an authoritative recovery of NTDS or FRS data Performing a directed recovery with NMM Recovering the Windows system configuration to an earlier state Restoring BOOT/BCD data in Windows 2008 R Performing Windows print queues backup and recovery Performing Windows DFS-R granular backup and recovery Pre and post command support Performing disaster recovery for Windows 2003 and Windows 2003 R Performing disaster recovery for Windows 2008 and Windows 2008 R Windows System Backup and Recovery 97

98 Windows System Backup and Recovery Overview NMM supports backup and recovery of: Windows server 2008 R2 Windows server 2008 R2 Web Edition (x64) Windows server 2008 R2 Standard Edition (x64) Windows server 2008 R2 Enterprise Edition (x64) Windows server 2008 R2 Datacenter Edition (x64) Note: NMM 2.3 does not provide support for Windows server 2008 R2 Foundation Edition. Windows server 2008 Windows server 2003 Windows storage server 2003 Windows clusters Active Directory IMPORTANT In addition to information in this chapter, review: Chapter 2, Configuring a Scheduled Backup, which supplements the overall NMM backup and the recovery procedures. It includes specific details needed to back up and recover Windows System data, such as Windows volumes and system components. Specifying system save sets for backup on page 99, which provides the privileges that are required for all resources that must be accessed. The EMC NetWorker Module for Microsoft Applications Release 2.3 Applications Guide, which provides the information needed to back up and recover Windows 2008, 2008 SP2 and 2008 R2 with NetWorker 7.6 SP2. Access privileges for backup and recovery When running or configuring NMM backups and recoveries, ensure that you have the appropriate level of privileges for all resources that must be accessed. Table 17 on page 98 describes the privilege levels needed. Table 17 Access privileges needed for backup and recovery (page 1 of 2) Resource NetWorker server NetWorker Module for Microsoft Applications client machine Privileges needed NetWorker Administrator or NetWorker Backup Operator Windows Administrator or Windows Backup Operator 98 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

99 Windows System Backup and Recovery Table 17 Access privileges needed for backup and recovery (page 2 of 2) Resource All applications protected by NMM, such as: Windows server Microsoft Data Protection Manager Microsoft Office SharePoint server Microsoft SQL server Microsoft Exchange server Network domain Storage node servers Privileges needed Windows Administrator Windows Domain Administrator Windows Administrator Performing system backups This section provides information on: Specifying system save sets for backup on page 99 NMM system data commands on page 100 Configuring system backups on page 100 Specifying system save sets for backup You can back up system data by specifying the volume and system components: Volume save set Can be as simple as a drive letter, or it can be a path or mount point. Note: When a volume that contains writer files for an application or the SYSTEM STATE is backed up, the files that belong to the writers are skipped during the backup. SYSTEM COMPONENTS:\ save set Contains many individual system writers. The individual system writers cannot be specified in a backup save set, they are all backed up in the SYSTEM COMPONENTS:\save set. The SYSTEM COMPONENTS:\ save set includes the following writers: Background Intelligent Transfer Service (BITS) COM+ Registration Database (REGDB) Certificate Authority Cluster Database (Windows server 2003) Cluster Writer (Windows server 2008) Dynamic Host Configuration Protocol (DHCP) Jet Event log File Replication Server (FRS) File Storage Resource Manager (FSRM) Microsoft Distributed File Replication (Windows server 2003) IIS Configuration Writer (Windows server 2008) IIS Metabase Microsoft SQL Server Desktop Engine (MSDE) for SQL 2000 embedded databases Performing system backups 99

100 Windows System Backup and Recovery MSSearch Service Writer (Windows server 2008) NPS VSS Writer (Network Policy and Access Service, Windows server 2008) NTDS (Active Directory Schema) Registry Removable Storage Manager (RSM) Remote Storage Manager Shadow Copy Optimization Writer (Windows server 2008) SQL Embedded (SQL 2005 Express) Terminal Services Gateway Writer (Windows server 2008) Terminal Services Licensing Windows Internet Name Service (WINS) Windows Management Instrumentation (WMI) VSS Performance Counters VSS Task Scheduler VSS Express Metadata Store NMM system data commands Table 18 on page 100 describes the commands that NMM uses to back up and recover system data. Table 18 NMM system data commands Item nsrsnap_vss_save nsrsnap_vss_recover Description NMM command that initiates the VSS-based backup. NMM command that initiates the VSS-based recovery. Configuring system backups The tasks for scheduling a backup are the same for all VSS writers. To perform a system backup for all VSS writers that are supported by NMM, complete the tasks outlined in Table 19 on page 100. Table 19 Tasks for scheduling a backup for VSS writers Backup task 1. Configure a backup pool for snapshot operations on page 51 Consideration No special configuration is required. 2. Configure snapshot policies on page 54 To back up SYSTEM COMPONENTS:\ the snapshot policy must specify All. NMM enforces this policy to ensure that a permanent backup of the snapshot exists. Attempting to restore system components from a persistent snapshot may invalidate the snapshot and leave the system in an unrecoverable state. 3. Configure a backup schedule on page 56 No special configuration is required. 4. Configure a backup group on page 57 No special configuration is required. 5. Configure a client resource on page 59 No special configuration is required. 100 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

101 Windows System Backup and Recovery Configure a system client resource To configure a system client resource: 1. In the Administration page of the NetWorker Management Console, click Configuration. 2. In the expanded left pane, select Clients. 3. From the File menu, select New. 4. In the Name attribute, type the hostname of the NetWorker client computer. 5. In the Comment attribute, type a description. If you are creating multiple client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines: To specify all volume data and all available Windows system components, type: All Note: Application data such as Exchange data is not included in the save set All. To back up specific volumes, type the volume name. For example, to specify the volume E and all of its subfolders and files, type: E:\ Note: Entries are not case-sensitive. To specify volume mount point data, place the name of the mount point on a separate line. For example, if you have a mount point named CAD_Drawings on volume E:\ and you want to back up all of the data on E:\ including the data under the mount point, type the following on separate lines: E:\ E:\CAD_Drawings Note: The save set All will include mount point data only if no other path to the remote data is found during backup. To specify all available Windows system components such as the registration database and Windows event log: Type the save set All or SYSTEM COMPONENTS:\. Ensure that the backslash (\) character is entered with the save set name SYSTEM COMPONENTS:\. Otherwise, backup fails and no concise error message is provided. Performing system backups 101

102 Windows System Backup and Recovery! IMPORTANT To protect against a disaster, ensure that all volumes and Windows system components are backed up. Backups of system components are required to have a snapshot policy of 'All' to ensure that they are all rolled over to a conventional backup. The snapshot policy for volumes, while not required to be a 'All' rolled over, should also specify a value of 'First', 'Last', or 'All' in the Backup Snapshots field. Do not specify 'None'. Disaster recovery can only be performed from a conventional backup. 10. For the Group attribute, select the backup group to which this client resource will be added: Note: If client resources for the same NMM client host are added to different backup groups, ensure that the Start Time attribute for each backup group is spaced far enough apart so that the backups for the host s client resources do not overlap. 11. For the Schedule attribute, select a backup schedule. 12. Click the Apps & Modules tab. 13. In the Access area, leave the Remote user and Password fields empty. 14. In the Backup command attribute, type the backup command. For all types of backup data except for Active Directory conventional backups, type: nsrsnap_vss_save.exe The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides additional information about Active Directory and SharePoint backups. 15. In the Application information attribute: a. Type the following variable and value: NSR_SNAP_TYPE=vss b. Type any additional variables and their values on a separate line. 16. If a proxy client is being set up for the NMM client, type the hostname of the proxy client in the Remote Access attribute. Note: If the NMM client is part of a cluster, type the names of the physical nodes of the cluster in the Remote Access attribute. 17. Click the Globals (1 of 2) tab. 102 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

103 Windows System Backup and Recovery Performing a recovery This section provides information on: Recovery considerations on page 103 System recovery in Windows server 2008 and Windows server 2003 on page 104 System Recovery Options Summary on page 105 Recovery options on page 105 Recovery considerations Review the following options and considerations before performing the procedures in these sections: Recovering file system snapshots that have not been rolled over on page 117 provides more information about recovering data from a persistent snapshot that has not been rolled over to a conventional backup medium.! IMPORTANT Attempting to restore system components from a persistent snapshot may invalidate the snapshot and leave the system in an unrecoverable state. NMM does not prevent an attempt to restore SYSTEM COMPONENTS from a point-in-time backup. Rollover a snapshot on page 30 describes how to rollover a snapshot to a conventional backup. To recover backup data that was password-protected and encrypted with another VSS client program, and not NetWorker VSS Client for Microsoft Windows 1.0 or NMM, use the recover.exe command from the command line interface (CLI). The EMC NetWorker Release 7.6 SP1 Command Reference Guide provides more information about the recover.exe command. Data that was backed up from a mount point is available for browsing at the root of the navigation tree. For example, if the drive H:\ has a mount point named H:\CAD_Drawings, then a separate entry for the mount point H:\CAD_Drawings will be available at the root of the navigation tree instead of as a subfolder under H:\. To recover data to a mount point that has been deleted, manually re-create the mount point before recovering the data. Otherwise, the data will be recovered to a local directory whose name corresponds to the deleted mount point. If the disk that is referenced by the mount point has been replaced, manually re-create the mount point. If a file was not backed up due to a skip directive, you may still be able to select the file for a recovery operation. In this case, although you can select the file, it is not recoverable. IMPORTANT If you are recovering File Replication Services (FRS) or Windows NT Directory Services (NTDS) data, boot the NetWorker client in Directory Service Recovery mode before completing the recovery options in this section. Booting the NMM host in Directory Service Restore mode on page 118 provides more information about these recovery options. Performing a recovery 103

104 Windows System Backup and Recovery System recovery in Windows server 2008 and Windows server 2003 When recovering an older backup of the system in Windows server 2008 or Windows server 2003, any application or NMM upgrades, service packs, or hot fixes that were installed since the backup may need to be reinstalled after the recovery. Recovering system data on page 104 describes using the System Recover Session commands and features for recovery. Some applications have their own name for the recover session. When you select Recover from the NMM client, it may display one or more of the following in addition to System Recover Session, depending on which of the applications are installed on the client: Active Directory Recover Session DPM Recover Session Exchange Recover Session Hyper-V Recover Session SharePoint Recover Session Application-specific recovery steps are provided in separate chapters for the applications. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides details. Recovering system data The System Recover Session window displays the backups that are available for recovery, and provides browsing and searching to locate and select items for recovery. To recover system data: 1. Open the NMM client software and select the NetWorker server on which the NMM client software was configured for backup. 2. If the NMM client is part of a cluster, select the virtual client to which you are recovering data. The virtual client can be selected from the Client list attribute in the application toolbar. 3. From the left pane, select Recover > System Recover Session. 4. In the navigation tree, select the items to be recovered. By default, items displayed in the navigation tree are from the most recent backup. For the System Recover Session view, both snapshot and rollovers can be displayed in the same view: If the most recent backup for an item is a snapshot, the snapshot appears. If the most recent backup for an item is a rollover, the rollover appears. To recover file system items from a previous backup: a. From the application toolbar, click the Browse calendar icon. b. Select an earlier browse time. To view versions of a backup item prior to the browse time: a. Right-click an item in the navigation tree. b. Select Versions from the pop-up menu. 104 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

105 Windows System Backup and Recovery 5. To determine whether any volumes need to be mounted for a selected item: a. Right-click the item. b. Select Required Volumes from the pop-up menu. 6. From the Options menu, select System Recover Session Options: NetWorker recovery options on page 106 DFS recovery options on page 111 FRS recovery options on page 114 NTDS recovery options on page Type the application-specific recover options or settings. The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides detailed information. 8. From the System Recover Session toolbar, click Start Restore. 9. From the left pane, select Monitor to view messages related to the progress of the recovery operation. Note: If you recovered items from a snapshot (instant recovery), the snapshot volume will be temporarily mounted during the recovery operation. The mounted volume is displayed in the Windows Explorer program. After the recovery is complete, you may have to refresh the Windows Explorer to update its view. System Recovery Options Summary The System Recovery Options window lists the System Recover and NetWorker Recover Options. This allows you to review the settings before starting the recovery. Performing a recovery on page 103 provides more information. You can perform the following tasks: To change the NetWorker and System Recover Options, click Recover Options. You can also access the settings from the System Recover Session view. On the System Recover Session toolbar, click Recover Options. The NetWorker Recover Options settings are specified on the General, NetWorker, and Security tabs. When the options are okay, click Start Recover to validate the options. If all option settings are valid, the dialog box closes and recovery starts. Recovery options This section describes the following recovery options: General recovery options on page 106 System recovery options: NetWorker recovery options on page 106 Cluster recovery options on page 107 ADAM recovery options on page 110 DFS recovery options on page 111 FRS recovery options on page 114 Performing a recovery 105

106 Windows System Backup and Recovery General recovery options NTDS recovery options on page 115 Security recovery options on page 116 Exchange recovery options described in the EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide. The General tab specifies how much diagnostic information is output for a recovery operation. For most recoveries, the diagnostic information is displayed in the Monitor view. To set the level of diagnostic information for a recovery: 1. Click the General tab from the Recover Options dialog box. 2. From the Diagnostic Level attribute, select a level from 1 to 9. A value of 1 produces the least amount of diagnostic information and a value of 9 produces the most diagnostic information. The value Normal produces no diagnostic information. 3. Click OK. Note: After each recovery, the Diagnostic Level attribute is automatically set to Normal. NetWorker recovery options The NetWorker tab is displayed in System Recover Session Options and Hyper-V Recover Session Options. Some of the following features are not applicable to Hyper-V Recover Session Options. To specify recovery options for file system data: 1. From the Options menu, select System Recover Session Options. 2. Click the NetWorker tab. 3. In the Relocate recovered data to: field, type a location other than the location from which the data was originally backed up: This feature is only applicable to System Recover Session Options. The location must be a local path. URL syntax such as \\servername\share is not supported. 4. Use the Restore Type field to determine the default recovery method: Select Conventional Restore to recover from a conventional backup medium. If a conventional backup is not available for the selected browse time, an snapshot restore is performed. Select Snapshot Restore to recover from a snapshot. If a snapshot is not available for the selected browse time, a conventional backup is performed: For snapshot restore, snapshot validation will occur prior to the restore. If the snapshot is invalid, the restore will fail. The invalid snapshot will be deleted automatically the next time the snapshot group runs. You can also delete a snapshot manually. Deleting a snapshot on page 45 provides more information about manually deleting snapshots. 106 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

107 Windows System Backup and Recovery 5. Select Use Microsoft best practices for selecting the system state to enforce Microsoft recommendations that determine which system state items must be selected as a group for recovery: This feature is only applicable to System Recover Session Options. Clear this attribute to select system state items individually.! IMPORTANT Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 6. Select Terminate recover of item if errors are encountered if it is not already selected: This option is selected by default. If this option is selected, then when an error occurs only the recovery of the specific item causing the error is halted. For example, during the recovery of the items C:\test and APPLICATIONS:\SqlServerWriter, an error occurs during recovery of a single file in the C:\test folder: If the option is selected, the rest of the recovery of C:\test is terminated, but NMM still attempts to recover APPLICATIONS:\SqlServerWriter\. If option is cleared and there is a recovery error with a file in C:\test, NMM still attempts to recover the rest of C:\test and APPLICATIONS:\SqlServerWriter. 7. Clear this option if file system recovery fails, and you encounter the error message: Files failed to be restored for File system marked objects. When this error occurs, open the EMC PowerSnap client log file and note which files caused the error. 8. Click OK. Cluster recovery options Use this tab to specify whether to perform an authoritative or nonauthoritative restore of the Cluster Writer. If the Cluster Writer was backed up in NetWorker 7.6 SP1 prior to upgrading to NMM 2.3, you must use a command line to perform an authoritative restore. Authoritative recovery from a NetWorker 7.6 SP1 save set after NMM upgrade on page 109 provides more information about the command line and when to use it. Cluster Writer nonauthoritative restore (default) Use this mode if the cluster is completely lost, in which case the cluster service does not run on either node, and the cluster database is missing or corrupted. Nonauthoritative restores will restore the cluster but will not restore a particular version of the database. Performing a recovery 107

108 Windows System Backup and Recovery After the nonauthoritative restore is complete: 1. Perform an authoritative restore to recover a specific version of the database. 2. Ensure that the SYSTEM COMPONENTS:\BootableSystemState save set is also selected. NMM will perform an nonauthoritative restore by default. To specify a nonauthoritative restore for the Windows server 2008 cluster writer: 1. From the Options menu, select System Recover Session Options. 2. Click the NetWorker tab, and then clear the Use Microsoft best practices for selecting system state option. 3. Click OK to close the System Recover Session Options dialog box. 4. In the navigation tree: a. Expand the SYSTEM COMPONENTS folder. b. Select Cluster Database. 5. Select the SYSTEM COMPONENTS:\BootableSystemState save set. 6. From the System Recover Session toolbar, click Start Restore. 7. Reboot the system when prompted. 8. If needed, repeat from step 1 on the other nodes. Cluster Writer authoritative restore Use this mode when the cluster configuration is lost, but the cluster is running okay otherwise. For example, when a cluster resource was accidentally deleted or you want to revert to a previous cluster configuration. The cluster must be healthy in all nodes. Note: Authoritative restores of the Cluster Writer are only supported for Windows server To specify an authoritative restore for the Windows server 2008 Cluster Writer: 1. Ensure that the cluster service is running on the local system. 2. Ensure that the cluster service is running on all remote nodes. Microsoft Windows server 2008 product documentation provides more information on running the cluster service. 3. From the Options menu, select System Recover Session Options. 4. Click the NetWorker tab, and clear the Use Microsoft best practices for selecting system state option. 5. Click the Cluster tab. 6. Select the Authoritative Restore options. 7. Click OK to close the System Recover Session Options dialog box. 8. In the navigation tree: a. Expand the SYSTEM COMPONENTS folder. b. Select Cluster Database. 9. From the System Recover Session toolbar, click Start Restore. 108 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

109 Windows System Backup and Recovery Note: Perform an authoritative restore of the Windows 2008 cluster writer by selecting only the Windows 2008 cluster writer in that recover session. In particular, do not perform an authoritative restore of the Windows 2008 cluster writer at the same time as the restore of any other NMM application. Authoritative restores of the Windows 2008 cluster writer will restart the cluster service on all nodes in the cluster. Authoritative recovery from a NetWorker 7.6 SP1 save set after NMM upgrade If the Windows server 2008 cluster database was backed up in NetWorker 7.6 SP1 prior to upgrading to NMM 2.3, you must use a command line to perform an authoritative restore. You cannot perform this authoritative recovery from the Cluster tab of System Recover Session Options. The following set of steps illustrates this installation, backup, and recovery sequence: 1. Install NetWorker 7.6 SP1 on a Windows server 2008 cluster. 2. Back up VSS SYSTEM SERVICES. 3. Uninstall NetWorker 7.6 SP1. 4. Install NMM 2.3: If you attempt to use the NMM recovery user interface to recover a cluster database that was backed up in NetWorker 7.6 SP1 prior to upgrading to NMM 2.3, NMM will change it to a nonauthoritative restore. You can only perform an authoritative restore of a Windows server 2008 Cluster Writer backup created with NetWorker 7.6 SP1 by using the command line. To perform an authoritative restore of the Windows server 2008serveriter: 1. Ensure that the cluster service is running in the local system. 2. Ensure that the cluster service is running on all remote nodes. 3. Type the following string on the command line: recover -s NWServer -U -N "VSS SYSTEM SERVICES:\Cluster Database" Note: Perform an authoritative restore of the Windows 2008 cluster writer by selecting only the Windows 2008 cluster writer in that recover session. In particular, do not perform an authoritative restore of the Windows 2008 cluster writer at the same time as the restore of any other NMM application. Authoritative restores of the Windows 2008 cluster writer will restart the cluster service on all nodes in the cluster. Nonauthoritative recovery of a Windows server 2008 cluster database with a NetWorker 7.6 SP1 save set A nonauthoritative recovery of a Windows 2008 cluster database backup that uses a save set created with NetWorker 7.6 SP1 can be performed through the NMM recovery user interface or through the recover command line. To specify a nonauthoritative recovery through the user interface by using a save set created with NetWorker 7.6 SP1: 1. From the Options menu, select System Recover Session Options. 2. Click the NetWorker tab, and clear the Use Microsoft best practices for selecting system state checkbox. 3. Click OK to close the System Recover Session Options dialog box. Performing a recovery 109

110 Windows System Backup and Recovery 4. In the navigation tree: a. Expand the VSS SYSTEM SERVICES folder. b. Select Cluster Database. 5. Select the entire VSS SYSTEM BOOT save set. 6. From the System Recover Session toolbar, click Start Restore. 7. Reboot the system when prompted. 8. Repeat step 1 through step 7 for each node on the cluster as needed. To specify a nonauthoritative recovery through the command line by using a save set created with NetWorker 7.6 SP1: 1. Type the following command: recover -s NWServer -N "VSS SYSTEM SERVICES:\Cluster Database" 2. Type the following command: recover -s NWServer -N "VSS SYSTEM BOOT:\" 3. Reboot the system when prompted. 4. Repeat step 1 through step 3 for each node on the cluster as needed. ADAM recovery options Use the ADAM tab in the System Recover Session Options dialog box to specify whether to perform an authoritative or nonauthoritative restore of Active Directory Application Mode (ADAM) data on this host. Note: In Windows server 2008, Active Directory Lightweight Directory Services (AD LDS) includes the ADAM functionality provided in Windows server Unless otherwise noted, assume that all references to ADAM also apply to AD LDS. ADAM nonauthoritative restore (default) This type of restore is typically performed when the host is being recovered due to catastrophic loss of data such as a disk failure. The most recent ADAM data is restored from backups and then the recovered host is updated with the most recent ADAM data from another ADAM server in the domain. This restore relies on at least one other ADAM server in the domain to have accurate and up-to-date ADAM data. ADAM authoritative restore Perform an authoritative restore only when corrupted or deleted ADAM data has been propagated to other ADAM server. This type of recovery restores the most recent ADAM data from backups, and then updates other ADAM servers in the domain with the recovered data. Note: To recover ADAM data, the APPLICATIONS:\ADAM <instance_name> Writer\ save set must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about specifying save sets when configuring a backup. 110 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

111 Windows System Backup and Recovery To specify recovery options for ADAM data: 1. From the Options menu: a. Select System Recover Session Options. b. Click the ADAM tab. 2. Select one of the following options: Non Authoritative Restore Authoritative Restore 3. Click OK to close the System Recover Session Options dialog box. 4. In the navigation tree: a. Expand the Applications folder. b. Select ADAM <instance_name>writer. 5. From the System Recover Session toolbar, click Start Restore. 6. If an authoritative restore has been performed, restore for all selections has completed, and NMM reports success, complete the following steps: a. Exit the NMM client, and open a command window. b. Run the dsdbutil.exe utility, and select Authoritative Restore option. c. This marks the objects that are to be restored in authoritative mode. d. When processing is complete, exit the dsdbutil.exe utility and start the ADAM instance service manually. Note: If a nonauthoritative restore was performed, the ADAM instance has already been started. DFS recovery options You can specify whether to perform an authoritative or nonauthoritative recovery of Distributed File System (DFS) data on this host. There are some differences between DFS recovery options on Windows server 2003 and Windows server 2008: Authoritative restore is available on Windows server 2003 and on some Windows server 2008 systems. In Windows server 2003, the writer is recovered from Applications:\DFS Replication service writer. In Windows server 2008, the writer is recovered from SYSTEM COMPONENTS:\Bootable System State. In Windows server 2008, DFS can have DFS shares or it can also be part of Active Directory recovery. In Windows server 2008, DFS is part of Active Directory recovery if it was promoted to a Domain Controller with the 2008 Functional level setting selected. To restore DFS on a Windows 2008 system as part of Active Directory, the system must be booted into Directory Services Restore Mode. Booting the NMM host in Directory Service Restore mode on page 118 provides more information. Performing a recovery 111

112 Windows System Backup and Recovery The steps for performing a DFS recovery from Windows server 2003 and Windows server 2008 are described in separate procedures. Nonauthoritative restore (default) This type of recovery restores the most recent DFS data from backups and then updates the recovered host with the most recent DFS data from another DFS server in the domain. A nonauthoritative recovery relies on at least one other DFS server in the domain to have accurate up-to-date DFS data. Nonauthoritative recoveries are typically performed when the host is being recovered due to catastrophic loss of data such as a disk failure. Authoritative restore An authoritative recovery restores the most recent DFS data from backups, and then updates other DFS servers in the domain with the recovered data. Perform an authoritative recovery only when corrupted or deleted DFS data has been propagated to other DFS servers. The procedures differ to the following platforms: Windows server 2003 on page 112 Windows server 2008 on page 113 Note: To recover DFS data, the APPLICATIONS:\DFS Replication service writer save set must have been backed up. The DFS Replication service writer is available with Windows server 2003 R2 or later. Additionally, the SYSTEM COMPONENTS:\ save set on the namespace server (usually the domain controller) that is associated with the DFS configuration must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about specifying save sets when configuring a backup. Windows server 2003 To specify which type of DFS recovery to perform in Windows server 2003: 1. From the Options menu: a. Select System Recover Session Options. b. Click the DFS tab. 2. Select one of the following options: Non Authoritative Restore to perform a nonauthoritative recovery. Authoritative Restore to perform an authoritative recovery. 3. Click OK to close the System Recover Session Options dialog box. 4. From the navigation tree: a. Expand the Applications folder. b. Select DFS Replication service writer. 5. From the System Recover Session toolbar, click Start Restore. 6. After the DFS Replication service writer has been recovered, you must recover the Bootable System State components on the namespace server (usually the domain controller) that is associated with the DFS configuration: a. Boot the namespace server in directory service restore mode as described in Performing a recovery on page 103. b. Open the NMM client software on the namespace server (usually the domain controller) that is associated with the DFS configuration. 112 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

113 Windows System Backup and Recovery c. From the Options menu, select System Recover Configuration Options and then click the NetWorker tab. d. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection.! IMPORTANT Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. e. Click OK to close the dialog box. f. From the left pane, select Recover > System Recover Session. g. From the navigation tree, expand the SYSTEM COMPONENTS folder and select BootableSystemState. h. From the System Recover Session toolbar, click Start Restore. After the recovery has completed, the Use Microsoft best practices for selecting the system state attribute is automatically selected. Windows server 2008 To specify which type of DFS recovery to perform in Windows server 2008: 1. From the Options menu: a. Select System Recover Session Options. b. Click the DFS tab. 2. Select one of the following options: Non Authoritative Restore to perform a nonauthoritative recovery. Authoritative Restore to perform an authoritative recovery. 3. Click OK to close the System Recover Session Options dialog box. 4. From the left pane, select Recover > System Recover Session. 5. From the navigation tree: a. Expand the SYSTEM COMPONENTS folder. b. Select BootableSystemState. 6. From the System Recover Session toolbar: a. Click Start Restore. b. After the recovery has completed, the Use Microsoft best practices for selecting the system state attribute is automatically selected. Performing a recovery 113

114 Windows System Backup and Recovery IMPORTANT Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. FRS recovery options You can specify whether to perform an authoritative or nonauthoritative recovery of File Replication Services (FRS) data on this host. The following topics describe these types of FRS restores: FRS nonauthoritative restore (default) on page 114 FRS nonauthoritative restore (default) on page 114 IMPORTANT Boot the NetWorker client in Directory Service Recovery mode before completing the recovery options in this section. Booting the NMM host in Directory Service Restore mode on page 118 provides more information. FRS nonauthoritative restore (default) A nonauthoritative recovery restores the most recent FRS data from backups and then updates the recovered host with the most recent FRS data from another FRS server in the domain. A nonauthoritative recovery relies on at least one other FRS server to have accurate up-to-date FRS data. Nonauthoritative recoveries are typically performed when the host is being recovered due to catastrophic loss of data such as a disk failure. FRS authoritative recovery An authoritative recovery restores the most recent FRS data from backups, and then updates the other FRS servers in the domain with the recovered data. Perform an authoritative recovery only when corrupted or deleted FRS data has been propagated to other FRS servers. Note: To recover FRS data, the SYSTEM COMPONENTS:\ save set must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about specifying save sets when configuring a backup. To specify whether to perform an authoritative or nonauthoritative recovery: 1. From the Options menu: a. Select System Recover Session Options. b. Click the FRS tab. 2. Select one of the following options: Non Authoritative Restore to perform a nonauthoritative recovery. Authoritative Restore to perform an authoritative recovery. 114 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

115 Windows System Backup and Recovery 3. Click the NetWorker tab. 4. Clear the attribute titled Use Microsoft best practices for selecting the system state. 5. Click Yes when asked to confirm your selection. IMPORTANT Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 6. Click OK to close the System Recover Session Options dialog box. 7. From the navigation tree: a. Expand the SYSTEM COMPONENTS folder. b. Click FRS. 8. From the System Recover Session toolbar, click Start Restore. If you are performing an authoritative recovery, complete the remaining steps in Performing an authoritative recovery of NTDS or FRS data on page 119. NTDS recovery options You can specify whether to perform an authoritative or nonauthoritative recovery of Windows NT Directory Services (NTDS) data on this host. The following topics describe these types of NTDS restores: NTDS nonauthoritative restore (default) on page 115 NTDS authoritative restore on page 115 IMPORTANT Boot the NetWorker client in Directory Service Recovery mode before completing the recovery options in this section. Booting the NMM host in Directory Service Restore mode on page 118 provides more information about these recovery options. NTDS nonauthoritative restore (default) A nonauthoritative recovery restores the most recent NTDS data from backups and then updates the recovered host with the most recent NTDS data from another NTDS server in the domain. A nonauthoritative recovery relies on at least one other NTDS server to have accurate up-to-date NTDS data. Nonauthoritative recoveries are typically performed when the host is being recovered due to catastrophic loss of data such as a disk failure. NTDS authoritative restore An authoritative recovery restores the most recent NTDS data from backups, and then updates other NTDS servers in the domain with the recovered data. Perform an authoritative recovery only when corrupted or deleted NTDS data has been propagated to other NTDS servers. Performing a recovery 115

116 Windows System Backup and Recovery Note: To recover NTDS data, the SYSTEM COMPONENTS:\ save set must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about specifying save sets when configuring a backup. To specify whether to perform an authoritative or nonauthoritative recovery: 1. From the Options menu: a. Select System Recover Session Options. b. Click the NTDS tab. 2. Select one of the following options: Non Authoritative restore to perform a nonauthoritative recovery. Authoritative Restore to perform an authoritative recovery. 3. Click the NetWorker tab. 4. Clear the attribute titled Use Microsoft best practices for selecting the system state. 5. Click Yes when asked to confirm your selection.! IMPORTANT Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 6. Click OK to close the System Recover Session Options dialog box. 7. From the navigation tree: a. Expand the SYSTEM COMPONENTS folder. b. Click NTDS. 8. From the System Recover Session toolbar, click Start Restore. If you are performing an authoritative recovery, complete the remaining steps in Performing an authoritative recovery of NTDS or FRS data on page 119. Security recovery options Backup and archive data on Windows hosts can be encrypted with an Advanced Encryption Standard (AES) Application Specific Module (ASM) pass phrase. If no pass phrase was specified when the backup data was encrypted, then the data is encrypted with a default pass phrase. During data recovery, you must specify the pass phrase used at the time of backup if it is not the default or current pass phrase. To specify pass phrases: 1. From the Options menu: a. Select System Recover Session Options. b. Click the Security tab. 116 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

117 Windows System Backup and Recovery 2. Type the pass phrases. 3. Click OK. The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides more information about AES encryption, and setting the pass phrase. IMPORTANT Do not use AES encryption when backing up files that are encrypted by using Windows Encrypting File System (EFS). When AES encryption is applied to a file that is also encrypted by using the Microsoft EFS, the backup will be reported as successful. However, recovery of the file will fail. Recovering file system snapshots that have not been rolled over The procedure to recover items in a file system snapshot differs depending on whether the snapshot has been rolled over to a conventional storage medium. This section describes how to recover items from a file system snapshot that has not been rolled over. Performing a rollback recovery on page 44 provides more information about recovering file system snapshots that have been rolled over. Note: If a snapshot volume has been mounted by using a client utility such as the EMC NaviCLI interface or the Windows Disk Management utility, remove the mount point before performing the next backup or recovery operation. If the mount point is not removed, it will be removed at the end of the next NetWorker backup or recovery operation. To recover items in a file system backup that has not been rolled over: 1. Connect to the NetWorker server on which the NetWorker client was configured for backup. Connecting to a NetWorker server on page 69 provides more information about connecting to the NetWorker server. 2. From the left pane, select Recover > System Recover Session. 3. In the navigation tree, right-click the snapshot and select Mount Snapshot. If the Mount Snapshot option is unavailable, then the snapshot has been rolled over. In this case, follow the steps described in Performing a rollback recovery on page 44. If another snapshot is currently mounted, a message indicates that the currently mounted volume will be unmounted. Click OK to unmount the volume and to proceed with mounting the selected snapshot volume. 4. When the taskbar animation stops and a green mark appears, click the mounted snapshot. The mounted snapshot item will expand in the navigation tree. 5. Under the expanded snapshot, select the items to be recovered. Selecting an item for recovery on page 41 provides more information about selecting items for recovery. 6. Select any additional file system options if applicable. NetWorker recovery options on page 106 provides more information about these options. 7. From the System Recover Session toolbar, click Start Restore. After the recovery starts, the snapshot is automatically unmounted. 8. From the left pane, select Monitor to view the progress of the recovery. Recovering file system snapshots that have not been rolled over 117

118 Windows System Backup and Recovery Booting the NMM host in Directory Service Restore mode Before you can complete the following recovery operations, boot the NMM client in Directory Service Restore mode: DFS recovery FRS recovery NTDS recovery Active Directory (AD) disaster recovery To boot the NMM client in Directory Service Restore mode: 1. On the NetWorker client domain controller, close all programs and restart Windows: When the computer restarts, a list of startup choices appears. The startup choices and the duration of the startup display are based on the settings in the operating systems section and the boot loader section of the boot.ini file. 2. Select the Windows boot option for the domain controller. 3. Press F8 to display a list of special boot options. 4. Select Directory Service Restore Mode (Windows Domain Controllers only) from the list of special boot options. When you boot in this mode, AD is taken offline. 5. Log in as administrator. Use the password that was specified when the domain controller was created. Windows starts in safe mode. 6. Open the NMM client application. 7. From the left pane, select Recover > System Recover Session. 8. Continue with the recovery options. The following sections provide more specific information: DFS recovery options on page 111 FRS recovery options on page 114 NTDS recovery options on page 115 Security recovery options on page 116 Recovering the Windows system configuration to an earlier state on page 122 includes information about SYSTEM STATE or VSS SYSTEM BOOT save sets, and save set recovery. Granular Active Directory or ADAM backup option The EMC NetWorker Module for Microsoft Application Release 2.3 Application Guide includes information about save sets on a domain controller. Note: Active Directory schema objects cannot be recovered and therefore, should never be deleted. 118 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

119 Windows System Backup and Recovery Performing an authoritative recovery of NTDS or FRS data Perform an authoritative recovery only when corrupted or deleted data has been propagated to other Windows NT Directory Services (NTDS) or File Replication Services (FRS) servers. After the authoritative recovery, the domain administrator can delete any unnecessary newer objects. NTDS and FRS objects may have associated group policies, for example, organizational units, domains, and site objects. Group policies are stored in the SYSVOL directory. A recovery of the SYSVOL directory cannot be separated from an authoritative recovery of NTDS or FRS. To perform an authoritative recovery: 1. If you have not already done so, boot the NMM client in Directory Service Restore mode. Performing a recovery on page 103 provides more information about performing this procedure. 2. If you have not already done so, complete the NTDS or FRS recovery options. The following sections provide more specific information on the recovery options: FRS recovery options on page 114 NTDS recovery options on page From the command line, use the xcopy command to copy sysvol\domain to another location. This preserves group policy, and file and directory permissions. 4. Run the Windows ntdsutil utility. 5. At the ntdsutil prompt, type: NTDSUTIL: authoritative restore 6. To perform an authoritative recovery of the following: Entire database, type: NTDSUTIL: restore database Subtree or individual object, type: NTDSUTIL: restore subtree distinguished_name For example: NTDSUTIL: restore subtree OU=engineering,DC=Seattle,DC=jupiter,DC=com NTDSUTIL: restore subtree CN=mars,CN=users,DC=Seattle,DC=jupiter,DC=com The Microsoft Windows Server Resource Kit provides more information and Active Directory documentation. 7. Exit the ntdsutil utility by typing quit at each successive ntdsutil prompt until the command prompt appears. 8. Copy the entire recovered SYSVOL\domain directory and all of its subdirectories to a new location. 9. Restart the domain controller in normal mode. 10. Log in to the domain controller. Performing an authoritative recovery of NTDS or FRS data 119

120 Windows System Backup and Recovery 11. Wait for the SYSVOL share to be published. Note: This can take several minutes while the recovered domain controller synchronizes with its replication partners. 12. After the SYSVOL share has been published, perform one of the following: For an authoritative recovery of the entire database, copy the entire SYSVOL\domain directory tree from the new location to the existing SYSVOL\domain directory as described in step 8. When the copy operation prompts for confirmation, select Yes to All. For an authoritative recovery of only a part of AD that includes Policy objects, copy the policy folders from the new location (see step 8) to the existing policy folders. Policy objects can be identified by their global universal ID (GUID). Policy folders are located in SYSVOL\domain\Policies. Performing a directed recovery with NMM Directed recovery on page 36 provides details about directed recovery and the types of directed recovery. To perform a directed recovery with NMM: 1. In NetWorker, create a volume backup. The backup can be snapshot or coventional. This will be the source for a directed recover. 2. Run the NMM UI. Connect to the NetWorker server that hosts the source NMM client. 3. Add the NMM client that created the volume backup as a locally browsable client. Figure 14 on page 120 shows the default of only one NMM client available, the local client. Figure 14 Local client on the taskbar next to client 4. On the Options menu, click Configure Options. Figure 15 on page 121 shows the Configuration Options dialog box. 120 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

121 Windows System Backup and Recovery Refresh button Figure 15 Configuration Options dialog box 5. Click the Refresh button, which is to the right of the Client name. Figure 16 on page 121 shows the Select Viewable Clients dialog box. The clients available on the NetWorker server that you are attached to are listed under Available clients on. Figure 16 Select Viewable Clients dialog box 6. Click the client to add in the Available clients on list box, and then click Add. Add or remove clients as needed. 7. Click OK. Figure 17 on page 121 shows the NMM window with the client box. Client list Figure 17 NMM client menu list Performing a directed recovery with NMM 121

122 Windows System Backup and Recovery 8. Click the Client list, and select the client that created the volume backup as the browsable client. 9. If the Snapshot Management or Monitor is the active navigation bar item, and you are prompted with the Navigate Away dialog box, click Yes. 10. On the System Recover Sessions bar, select Recover Options. The NetWorker System Recover Session Options dialog box appears. 11. On the NetWorker tab, specify the destination for the recovery in the Relocate Recovered Data box, and then click OK. 12. Recover remote client's backup to local destination. Recovering the Windows system configuration to an earlier state Hosts that were upgraded from a regular NetWorker client to a NMM client can have their Windows operating system configuration recovered to a state prior to upgrading to the NMM client. IMPORTANT If the Windows operating system was upgraded on the host, you cannot recover the Windows system configuration to the state it was in before the operating system software was upgraded. To recover the Windows system state to a point-in-time that precedes the installation of the NMM client: 1. If the NMM client is: A Windows domain controller, boot the NMM client in Directory Services Restore mode. Booting the NMM host in Directory Service Restore mode on page 118 provides more information about booting in this mode. Not a Windows domain controller, start with step Recover the contents of the volume on which the Windows operating system was installed. 3. Recover the Windows configuration save sets: If VSS was licensed and enabled, recover: VSS SYSTEM BOOT VSS SYSTEM FILESET VSS SYSTEM SERVICES If VSS was not licensed or enabled, recover: SYSTEM STATE SYSTEM FILES SYSTEM DB 4. Update the recovered registry with NMM client entries. Because the registry was recovered to a client state prior to the NMM client installation, you must update the registry with entries for the NMM client. To update the registry, perform the following uninstall and install steps: a. Uninstall the NMM client software. b. Install the NMM client software. 122 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

123 Windows System Backup and Recovery c. Uninstall the NetWorker PowerSnap software. PowerSnap is installed with the NMM client software. d. Uninstall the NMM client software. e. Reinstall the NMM client software. f. Reinstall, as necessary, any other applications that were installed after the point-in-time to which the Windows operating system configuration was recovered. The EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide provides more information about the uninstall and install steps. Restoring BOOT/BCD data in Windows 2008 R2 This procedure is optional. In Microsoft Windows 2008 R2, the BOOT Configuration Data (BCD) store contains the boot configuration parameters and controls the computer s boot environment. BCDEdit is a command-line tool provided by Microsoft to add, delete, edit, and modify data in a BCD store. Note: Restoring the recovered file is optional. The BCDEdit reference document in the Microsoft documentation provides more information about BCDEdit. During recovery, the BCD file is recovered to the folder C:\boot_restored-{timestamp} To restore the recovered file, import the file by using the following command: bcdedit /import c:\boot_restored-{timestamp}\boot Performing Windows print queues backup and recovery The NMM 2.3 software supports backup and recovery operations for Windows print queues as part of the file system. There is no writer support for Windows print queues. Depending on the status of the print queue during a restore operation you might be prompted to reboot the system. Performing Windows DFS-R granular backup and recovery NMM 2.3 provides support for granular backup and recovery of Windows Distributed File System Replication (DFS-R) folders only on Microsoft Windows server 2008 (x64 and x86) and Microsoft Windows server 2008 R2 (x64). DFS-R replicated and shared directories can be backed up like standard file directories by allowing granular DFS-R folder and file backup and recoveries on Windows server 2008 SP2 and Windows server 2008 R2 operating systems. You are not required to recover the entire SYSTEM COMPONENTS:\ save set to restore DFS-R replicated or shared directories: DFS-R granular support DFS-R replicated folders and data is backed up as file system data and is not backed up as a part of DFS-R writer in SYSTEM COMPONENTS:\ save set backup. DFS-R replicated folders and data recovery is Restoring BOOT/BCD data in Windows 2008 R2 123

124 Windows System Backup and Recovery supported to both original or alternate location. Directed recovery of DFS-R replicated folders and data is also supported. Because DFS-R replicated folders and data is backed up as file system data, all the features supported by file system data backup and recovery are supported by DFS-R granular support. DFS-R writer support DFS-R writer backs up only SYSVOL in a domain controller as a part of Bootable System State. Recovery of DFS-R writer is supported only to original location as this is a part of SYSTEM COMPONENTS:\ save set. On non-domain controller, the DFS-R writer is not part of the SYSTEM COMPONENTS:\ save set. NMM 2.3 support for DFS-R backup and recovery for Windows 2003 (x64 and x86), Windows 2003 R2 (x64) is the same as previous releases of NMM: DFS-R writer backs up the DFS replicated folders along with the data inside the folders through the save set APPLICATIONS:\DFS Replication service writer. Perform authoritative restore to recover the DFS replicated folders and data that are backed up with DFS-R writer. Authoritative restore on page 112 provides details. The DFS replicated folders and data can not be backed up as part of file system data. Even if backup is attempted as part of file system data, backup succeeds in backing up the replicated folders only excluding the contents of the replicated folders. That is DFS-R granular support is not present in Windows 2003 r2. DFS-R writer is not backed up as part of SYSTEM COMPONENTS:\ backup. DFS-R writer does not back up SYSVOL folder in a domain controller machine. Pre and post command support With NMM 2.3, the following pre and post commands are now supported. These commands allow you to include customized backup actions before and after a client backup operation: precmd.bat script on page 124 postcmd.bat script on page 125 nsrsnapvsssavepnpc file on page 125 precmd.bat script You can create a precmd.bat script file to enable actions to be performed prior to a backup operation. When the NetWorker server starts the backup, the contents of the nsrsnap_vss_savepnpc.exe file is run on the client to perform the required actions. To create a precmd.bat script file: 1. Create a new file on the Windows client by using Notepad. 2. Specify a command to run prior to the backup. For example, add the following lines to the file: echo "Start pre backup action" >> Pre-postBackup.log time /t >> Pre-postBackup.log date /t >> Pre-postBackup.log <Add commands to run here> echo "Complete Pre backup action" >> Pre-postBackup.log time /t >> Pre-postBackup.log date /t >> Pre-postBackup.log 124 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

125 Windows System Backup and Recovery 3. Save this file as precmd.bat in a new directory that does not contain spaces. For example: C:\Scripts postcmd.bat script You can create a postcmd.bat script file to enable actions to be performed after a backup operation. To create a postcmd.bat script: 1. Create a new file on the Windows client by using Notepad. 2. Specify a command to run after the NetWorker software has backed up the data. 3. Save this file as postcmd.bat in a new directory that does not contain spaces. For example: C:\Scripts nsrsnapvsssavepnpc file To run the pre and post command scripts that were created in the previous steps, you must create the nsrsnapvsssavepnpc file. This file lets the NetWorker software know that a pre and post action is required. To create a nsrsnapvsssavepnpc file to run the pre and post actions: 1. Create a new file on the Windows client by using Notepad. 2. Add the following lines to the file: type: nsrsnapvsssavepnpc; precmd: "C:\\Scripts\\precmd.bat"; pstcmd: "C:\\Scripts\\postcmd.bat"; 3. Save and name the file as groupname.res in the following location: C:\Program Files\Legato\nsr\res Where groupname is the name of the NetWorker backup group to which this client belongs. Performing disaster recovery for Windows 2003 and Windows 2003 R2 NMM provides recovery for the NMM client itself, as well as the applications NMM protects, such as the following: Microsoft Exchange server Microsoft SQL server Microsoft Office SharePoint Services Microsoft Hyper-V Microsoft Data Protection Manager A good disaster recovery requires a complete and timely backup. The procedures for recovering an application include prerequisites of what particular files and data should already be backed up when you need to perform the disaster recovery. Performing disaster recovery for Windows 2003 and Windows 2003 R2 125

126 Windows System Backup and Recovery IMPORTANT Ensure that your snapshot policies include at least one rollover to conventional backup. Disaster recovery can only be performed from a conventional backup. NMM requires conventional backup for SYSTEM COMPONENTS. Attempting to restore SYSTEM COMPONENTS from a point-in-time backup can leave the system in an unrecoverable state. NMM does not prevent an attempt to restore SYSTEM COMPONENTS from a point-in-time backup. Rollover a snapshot on page 30 describes how to rollover a snapshot to a conventional backup. Disaster recovery of the entire NMM client machine requires completion of the following tasks: 1. Recovery of the NMM client. Perform one of the following, whichever is applicable: Perform a disaster recovery operation when the NMM client is not on a domain controller on page 126 Or Perform a disaster recovery operation when the NMM client is on a domain controller on page Full recovery of the applications on that machine. Review these procedures when setting up backup plans to ensure that the prerequisite files and data will be backed up for future disaster recoveries. Perform one of the following, whichever is applicable: SQL server disaster recovery Windows server 2003 clustered client disaster recovery SharePoint server 2007 disaster recovery SharePoint server 2010 disaster recovery Exchange server 2007 disaster recovery Exchange server 2010 disaster recovery DPM disaster recovery Hyper-V parent partition disaster recovery Active Directory disaster recovery Perform a disaster recovery operation when the NMM client is not on a domain controller To perform a disaster recovery if the NMM client is not on a domain controller: 1. Install the original operating system to the same specifications and configuration as originally on the client. 2. Ensure to apply all service packs and updates that had been applied to the operating system before the disaster, to bring it up to the exact same level as existed at the time it was lost. 3. Install the required Microsoft applications. 4. Install the NMM client software exactly as it was configured before the disaster. 5. Open the NMM client GUI. 6. From the left pane, select Recover > System Recover Session. 126 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

127 Windows System Backup and Recovery 7. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) folder, typically C:\Program Files\Legato\nsr\rmagentps. 8. Select the SYSTEM COMPONENTS folder. Note: If recovering a backup created with NetWorker VSS client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. 9. From the System Recover Session toolbar, click Start Restore. 10. When prompted, restart the client. This restores the operating system to the state it was in when last backed up. Now the following applications can be restored from previous backups: Exchange server SQL server Office SharePoint server Data Protection Manager 11. To restore an application, follow the procedures for the specific application, listed in Performing disaster recovery for Windows 2003 and Windows 2003 R2 on page Reinstall the applications that you are using to complete the disaster recovery process. Perform a disaster recovery operation when the NMM client is on a domain controller To perform a disaster recovery if the NMM client resides on a domain controller: 1. Install the original operating system to the same specifications and configuration as originally on the client. 2. Ensure to apply all service packs and updates that had been applied to the operating system before the disaster, to bring it up to the exact same level as existed at the time it was lost. 3. Install the required Microsoft applications. 4. Install the NMM client software exactly as it was configured before the disaster. Note: This is for an Active Directory client NMM installation, and is not for the Active Directory plugin within a client. 5. Boot the NMM client in directory service restore mode. Performing a recovery on page 103 provides more information about these recovery options. 6. Open the NMM client GUI. 7. From the left pane, select Recover > System Recover Session. 8. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) folder, typically C:\Program Files\Legato\nsr\rmagentps. 9. Select the SYSTEM COMPONENTS folder. Performing disaster recovery for Windows 2003 and Windows 2003 R2 127

128 Windows System Backup and Recovery Note: If recovering a backup created with NetWorker VSS client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. 10. From the System Recover Session toolbar, click Start Restore. 11. When prompted, restart the client. This restores the operating system to the state it was in when last backed up. Now the following applications can be restored from previous backups: Exchange server SQL server SharePoint server Data Protection Manager 12. To restore an application, follow the procedures for the specific application, listed in Performing disaster recovery for Windows 2003 and Windows 2003 R2 on page Reinstall the applications that you are using to complete the disaster recovery process. Performing disaster recovery for Windows 2008 and Windows 2008 R2 For disaster recovery with NetWorker 7.6 SP2, use Windows Disaster Recovery. The EMC NetWorker Module for Microsoft Application Release 2.3 Application Guide provides details. Note: When performing a disaster recovery on a Domain Controller in Windows server 2008 and Windows server 2008 R2, there is no need for installation of applications after performing disaster recovery of the NMM client. 128 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

129 8 Microsoft Windows Cluster Backup and Recovery This chapter includes the following topics: Windows server cluster backup and recovery Performing Windows server cluster backups Performing Windows server cluster recovery Performing Windows server 2003 clustered client disaster recovery Microsoft Windows Cluster Backup and Recovery 129

130 Microsoft Windows Cluster Backup and Recovery Windows server cluster backup and recovery This chapter supplements the overall NMM backup procedures in the following sections: Chapter 2, Configuring a Scheduled Backup Chapter 7, Windows System Backup and Recovery With the specific details needed to back up and recover clusters in: Windows server 2008 Windows Server Failover Clustering (WSFC) Windows server 2003 Microsoft Cluster Service (MSCS) This section contains information on: Cluster support in NMM client on page 130 Compatibility with previous Windows cluster backups on page 130 Components used by NMM for Windows Cluster backup and recovery on page 131 Windows Cluster application information variable settings on page 131 Cluster support in NMM client NMM client supports Windows server clusters running on the following versions of Microsoft Windows server: Microsoft Cluster Service (MSCS) Windows server 2003 SP2 (x86, x64) and Windows server 2003 R2 with SP2 (x86, x64): Standard Edition Enterprise Edition Datacenter Edition Windows Server Failover Clustering (WSFC) Windows server 2008 (x86, x64): Standard Edition Enterprise Edition Datacenter Edition Compatibility with previous Windows cluster backups Windows server 2008 does not support recoveries of Windows server 2003 backups of the Cluster Writer. Many Windows legacy APIs in Windows server 2003 are not supported in Windows server NMM client does not prevent attempting to recover a Windows server 2003 cluster to a Windows server 2008 cluster, but recovery will fail. 130 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration Guide

131 Microsoft Windows Cluster Backup and Recovery Components used by NMM for Windows Cluster backup and recovery NMM backs up Windows Cluster data as part of the SYSTEM COMPONENTS save set. A Cluster writer is used within SYSTEM COMPONENTS, but it cannot be specified in a save set. The Cluster writer is recovered when one of the following is selected for recover: SYSTEM COMPONENTS As part of recovery of this entire save set SYSTEM COMPONENTS:\Cluster Writer As an authoritative restore in Windows server 2008 SYSTEM COMPONENTS:\Cluster Writer and SYSTEM COMPONENTS:\BootableSystemState As part of a nonauthoritative restore in Windows server 2008 Windows Cluster application information variable settings Table 20 on page 131 lists the variables that can be specified in NetWorker Management Console, in the Application Information attribute of the client resource. Table 20 Windows Cluster application information variable settings Attribute Name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=valueapplica tion information attribute Specifies the snapshot service provider name. Specifies the hostname of the NMM client that moves snapshots from the NMM client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This value is required. The local host The proxy client hostname Consider the following: If no value is entered, the local host is used as the data mover. If setting up a proxy client for a virtual cluster server, ensure to type the proxy client hostname in the Remote Access attribute of the client resource. For serverless backups, specify a proxy client. If setting up an Windows Cluster client resource, it is recommended that you use a proxy client. If a proxy client is specified, Windows Cluster consistency checks are performed on the proxy client. Related messages are written to the Replication Manager log files (erm_clientxx.log) on the proxy client. If no proxy client is specified for an Windows Cluster client resource, consistency checks are performed on the client resource host. Related messages are logged on the client resource host in both the Replication Manager log files and the nmm.raw file. Windows server cluster backup and recovery 131

132 Microsoft Windows Cluster Backup and Recovery Performing Windows server cluster backups To perform Exchange system backups, complete the tasks outlined in Table 21 on page 132. Table 21 Steps and considerations for backing up a clustered client resource Backup task Consideration Description 1. Configure a backup pool for snapshot operations on page Configure snapshot policies on page Configure a backup schedule on page Configure a backup group on page Configure privileges on page Configure a proxy client on page 63 No special configuration is required. No special configuration is required. No special configuration is required. Configure a client resource for each virtual server that is being backed up and each physical node in the cluster on which the virtual server may execute. Type the names of the physical nodes of the cluster in the Remote Access attribute of each virtual client resource. Set up NetWorker administrator privileges for each physical node and proxy client in the cluster. If a hardware provider such as the EMC VSS Provider is being used, a proxy client must be configured for a clustered NMM client. Tasks 1, 2, and 3 are performed for scheduling a backup, and are the same for all VSS writers supported by NMM. Tasks 4, 5, and 6 are additional considerations that are required for setting up a virtual NMM client.! IMPORTANT There is an additional consideration for backing up a clustered client resource. The proxy client is not allowed to be a member of the cluster. This is by Microsoft design and Microsoft describes this restriction in a MSDN article at in the subsection Auto-Import Hardware Shadow Copies Are Not Supported on Windows Cluster Service. Cluster failover and backups Considerations include: If a node within a cluster undergoes failover during a backup operation, the operation fails. The next scheduled backup operation will be the next valid backup. If using a hardware provider, such as the EMC VSS Provider, use the disk management utilities provided with the associated hardware to delete any resources that may be left in an indeterminate state as a result of the failed backup. For example, a CLARiiON storage solution may have an inactive snapshot as the result of a failed backup. In this case, use the Navisphere user interface or the NaviCLI command line interface to search for and delete the inactive snapshot. 132 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration Guide

133 Microsoft Windows Cluster Backup and Recovery Performing Windows server cluster recovery The cluster recovery procedures are different for Windows server 2003 and Windows server The following sections provide more information: Performing Windows server 2003 clustered client disaster recovery on page 133 provides information about cluster recovery in Windows server Cluster recovery options on page 107 describes the Cluster tab in NMM Recovery options. This tab provides options for authoritative or nonauthoritative restore. Authoritative restores of the Cluster Writer are only supported for Windows server Performing Windows server 2003 clustered client disaster recovery There are three different cluster recovery scenarios presented: Perform disaster recovery of a cluster client on page 133 describes how to recover a cluster from a backup created by the NMM client. Perform disaster recovery from a legacy VSS backup on page 136 describes how to recover a cluster from a VSS backup created before the NMM client was installed. Perform a disaster recovery of a clustered client from a legacy non-vss backup on page 140 provides recommendations for how to handle legacy non-vss backup which does not work with the NMM client.! CAUTION Ensure that your snapshot policies include at least one rollover to conventional backup. Disaster recovery can only be performed from a conventional backup. Chapter 1, Overview, describes how to rollover a snapshot to a conventional backup.! IMPORTANT As part of disaster recovery plan, backup either of the following on the application hosts: - The save set All attribute in the save set field of the client Resource. - The SYSTEM COMPONENTS:\ save set along with the system volume, for example C:\. Perform disaster recovery of a cluster client The following procedure describes how to recover a single node in a two-node cluster. The procedure assumes that you are recovering Node_B and that Node_A is available.! IMPORTANT While performing cluster disaster recovery, evict a node from cluster only if the node is corrupt or down. However before recovery, ensure to rejoin the node with the cluster once the node is up and running. Performing Windows server cluster recovery 133

134 Microsoft Windows Cluster Backup and Recovery To perform a disaster recovery of a cluster client, follow these tasks: 1. Evict Node_B from the cluster on page Select the required items to be recovered for Node_B on page Start the Cluster service on Node_A on page 136 Evict Node_B from the cluster Follow these steps: 1. Use the Cluster Administrator tool on Node_A to evict Node_B from the cluster. The Microsoft website or documentation for the Cluster Administrator tool provides information about evicting a cluster. 2. At the command prompt, type the following to clean up MSCS: cluster node Node_B /forcecleanup! CAUTION After cleaning the cluster server, you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform a recovery for each application that was previously installed on the node. 3. Use the Cluster Administrator tool to select Join an existing Cluster and type the cluster name. 4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations. 5. Stop the cluster service in Node_A by using one of the following methods: With the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc Select the required items to be recovered for Node_B The procedure differs depending on whether or not the cluster service resides on a domain controller. The following sections provide more information: If the cluster service resides on a member server and is not a domain controller on page 134 If the cluster service resides on a domain controller on page 135 If the cluster service resides on a member server and is not a domain controller If the cluster service resides on a member server and is not a domain controller: 1. Open the NMM client software on Node_B. 2. From the left pane, select Recover > System Recover Session. 3. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) installation folder. 4. Select the SYSTEM COMPONENTS folder. 134 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration Guide

135 Microsoft Windows Cluster Backup and Recovery Note: If recovering a backup created with NetWorker VSS client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. 5. From the System Recover Session toolbar, click Start Restore. If the cluster service resides on a domain controller If the cluster service resides on a domain controller: 1. Boot the NMM client in directory service restore mode. Booting the NMM host in Directory Service Restore mode on page 118 provides more information about these recovery options. 2. Open the NMM client software. 3. From the Options menu, select System Recover Configuration Options and click NetWorker. 4. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection.! IMPORTANT Do not clear the Microsoft Best Practices box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 5. Click OK to close the dialog box. 6. From the left pane, select Recover > System Recover Session. 7. Stop the cluster service in Node_B by using one of the following methods: With the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc 8. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) installation folder. 9. In the navigation tree, select BootableSystemState and Cluster Writer. 10. Select the SYSTEM COMPONENTS:\ folder. If recovering a backup created with NetWorker VSS client 1.0 SP1, under SYSTEM COMPONENTS:\, clear ASR DISK. 11. From the System Recover Session toolbar, click Start Restore. When prompted, restart Node_B. Performing Windows server 2003 clustered client disaster recovery 135

136 Microsoft Windows Cluster Backup and Recovery Start the Cluster service on Node_A Follow these steps: 1. Start the Cluster service on Node_A by using one of the following methods: With the control panel service tool, start the Cluster service. At the command prompt, type the following: net start clussvc 2. Use the Cluster Administrator on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred. Note: If you are performing regular scheduled backups, this will recover the cluster database to a point shortly before the loss of Node_B. 3. Use the Cluster Administrator on Node_A to monitor the cluster joining status of node_b. 4. Use the Cluster Administrator on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group. Cluster recovery environment variable settings If a Windows server 2003 cluster database recover failed because the partition layout of the quorum disk has changed since the backup, or the drive letter of the quorum disk is already being used, the recovery process can be repeated with these environment variables defined as: %NsrClusterForceRecover% should be set to 1. %NsrClusterNewQuorumDrive% should be set to the drive letter of the new quorum disk (for example, R:). There should only be one active node during the recovery. If other nodes are active and the environment variable %NsrClusterForceRecover% is not defined, then the recovery will fail. With %NsrClusterForceRecover% defined, the recover process will attempt to shut down the cluster service on the other active nodes. It will also attempt to change the signature and drive letter (if %NsrClusterNewQuorumDrive% is defined) of the current quorum disk even if its partition layout does not match the one described in the backup. However, the success of the recovery is not guaranteed even with %NsrClusterForceRecover% defined. Perform disaster recovery from a legacy VSS backup The procedure for disaster recovery of a clustered client from a legacy VSS backup differs depending on whether or not the cluster service resides on a domain controller: For cluster service on a member server on page 137 For cluster service on a domain controller on page EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration Guide

137 Microsoft Windows Cluster Backup and Recovery For cluster service on a member server This recovery is for a VSS backup created before the NMM client was installed. This backup would include VSS SYSTEM SERVICES, VSS SYSTEM FILESET, and VSS SYSTEM BOOT. The following procedure describes how to recover a single node in a two-node cluster. The procedure assumes that you are recovering Node_B and that Node_A is available: 1. Use the Cluster Administrator tool on Node_A to evict Node_B from the cluster. 2. At the command prompt, type the following to clean up MSCS: cluster node Node_B /forcecleanup! IMPORTANT After cleaning up the cluster server, you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform a recovery for each application that was previously installed on the node. 3. Use the Cluster Administrator tool to select Join an existing Cluster and type the cluster name. 4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations. 5. Stop the cluster service in Node_A by using one of the following methods: Using the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc 6. Select the required items to be recovered for Node_B: a. Open the NMM client software on Node_B. b. From the left pane, select Recover > System Recover Session. c. Select all local drives except for the NMM client installation directory. d. Select the following: VSS SYSTEM SERVICES VSS SYSTEM FILESET VSS SYSTEM BOOT e. From the System Recover Session toolbar, click Start Restore. f. When prompted, restart Node_B. 7. Start the Cluster service on Node_A by using one of the following methods: Use the control panel service tool to start the Cluster service. At the command prompt, type the following: net start clussvc 8. Use the Cluster Administrator tool on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred. Performing Windows server 2003 clustered client disaster recovery 137

138 Microsoft Windows Cluster Backup and Recovery Note: If you have been performing regular scheduled backups, this will recover the cluster database to a point in time shortly before the loss of Node_B. For cluster service on a domain controller 9. Use the Cluster Administrator tool on Node_A to monitor the cluster joining status of Node_B. 10. Use the Cluster Administrator tool on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group. This recovery is for a VSS backup created before the NetWorker VSS client was installed. This backup would include VSS SYSTEM BOOT, VSS SYSTEM FILESET, and VSS SYSTEM SERVICE. The following procedure describes how to recover a single node in a two-node cluster. This procedure assumes that you are recovering Node_B and that Node_A is available: To recover a single node in a two node cluster: 1. Use the Cluster Administrator on Node_A to evict Node_B from the cluster. 2. At the command prompt, type the following to clean up MSCS: cluster node Node_B /forcecleanup! IMPORTANT After cleaning up the cluster server, you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform a recovery for each application that was previously installed on the node. 3. Use the Cluster Administrator to select Join an existing Cluster and type the cluster name. 4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations. 5. Stop the cluster service in Node_A by using one of the following methods: Use the control panel service tool to stop the Cluster service. At the command prompt, type the following: net stop clussvc 6. Select the required items to be recovered for Node_B: a. Boot the NMM client in directory service restore mode. Booting the NMM host in Directory Service Restore mode on page 118 provides more information about these recovery options. b. Open the NMM client software. c. From the Options menu, select System Recover Configuration Options and click the NetWorker tab. 138 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration Guide

139 Microsoft Windows Cluster Backup and Recovery d. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection.! CAUTION Do not clear the Microsoft Best Practices option, except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. e. Click OK to close the dialog box. f. From the left pane, select Recover > System Recover Session. g. Stop the cluster service in Node_B by using one of the following methods: Using the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc h. Select all local drives except for the NMM client installation directory. i. Select VSS SYSTEM SERVICES, VSS SYSTEM FILESET, and VSS SYSTEM BOOT. j. From the System Recover Session toolbar, click Start Restore. When prompted, restart Node_B. 7. Start the Cluster service on Node_A by using one of the following methods: Use the control panel service tool to start the Cluster service. At the command prompt, type the following: net start clussvc 8. Use the Cluster Administrator tool on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred. Note: If you have been performing regular scheduled backups, this will recover the cluster database to a point in time shortly before the loss of Node_B. 9. Use the Cluster Administrator tool on Node_A to monitor the cluster joining status of Node_B. 10. Use the Cluster Administrator on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group. Performing Windows server 2003 clustered client disaster recovery 139

140 Microsoft Windows Cluster Backup and Recovery Perform a disaster recovery of a clustered client from a legacy non-vss backup This recovery is for a non-vss backup that was created before the NMM client was installed. This backup would include SYSTEM STATE, SYSTEM DB, and SYSTEM FILES. Consider the following: Recovery of non-vss backups of the cluster database by using the NMM client does not work. To ensure that backups of the cluster database are available for recovery, perform a full backup of the system directly after updating the system to the NMM client. This creates a post-installation cluster backup that can be recovered by using the NMM client. Monitoring a recovery The progress of all recovery operations can be viewed from the Monitor window. Monitor view on page 40 provides more information about the Monitor window. 140 EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Administration Guide

141 Glossary This glossary contains terms related to disk storage subsystems. Many of these terms are used in this manual. A ad hoc backup administrators group ASM (application specific module) ASR writer archive archive volume auto media management autochanger autochanger sharing See manual backup. Microsoft Windows user group whose members have the rights and privileges of users in other groups, plus the ability to create and manage the users and groups in the domain. Program that is used in a directive to specify how a set of files or directories is to be backed up or recovered. For example, compressasm is a NetWorker directive used to compress files. The VSS writer, which is responsible for identifying critical data that is needed to perform an offline restores. Backing up directories or files to an archive volume to free disk space. Archived data is not recyclable. Volume used to store archive data. Archived data cannot be stored on a backup volume or a clone volume. Feature that enables the storage device to automatically label, mount, and overwrite an unlabeled or recyclable volume. See library. See library sharing. B backup Operation that saves data to a volume. See also conventional backup and snapshot. backup components backup group backup level See metadata document. See group. See level. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 141

142 Glossary backup volume bootstrap Boot Configuration Data (BCD) browse policy Volume used to store backup data. Backup data cannot be stored on an archive volume or a clone volume. See also volume. Save set that is essential for NetWorker disaster recovery procedures. The bootstrap consists of three components that reside on the NetWorker server. The media database, the resource database, and the server index. The ASR writer component that identifies the location of the boot configuration database. This is required to perform an offline restore. NetWorker policy that specifies how long backed-up data will be readily available for recovery. Backed-up data that has not exceeded its browse policy time can be recovered more quickly than data that has exceeded its browse policy time but not its retention policy time. See also retention policy. C carousel client client file index client-initiated backup client resource clone clone volume cluster See library. Computer, workstation, or fileserver whose data can be backed up and recovered. Database that tracks every database object, file, or file system that is backed up. The NetWorker server maintains a single client index file for each client. See manual backup. NetWorker server resource that identifies the save sets to be backed up on a client. The client resource also specifies information about the backup, such as the schedule, browse policy, and retention policy for the save sets. See also client and resource. Reliable copy of backed up data. Unlike volumes created with a simple copy command, clone volumes can be used in exactly the same way as the original backup volume. Single save sets or entire volumes can be cloned. Exact duplicate of a backup volume. One of four types of volumes that NetWorker software can track (backup, archive, backup clone, and archive clone). Save sets of these different types may not be intermixed on one volume. 1. Two or more independent network servers that operate and appear to clients as if they are a single unit. The cluster configuration enables work to be shifted from one server to another, providing "high availability" that allows application services to continue despite most hardware or software failures. Also known as an agent (Sun), logical server (HP TruCluster), package (HP-UX), and virtual server (Microsoft). 2. Group of disk sectors. The operating system assigns a unique number to each cluster and keeps track of files according to which clusters they use. command line component Line on a display screen, also known as a command prompt or shell prompt, where you type software commands. 1. Group of related data that must be treated as a single unit for backup and recovery. 2. In Microsoft VSS terminology, a component is a subordinate unit of a Writer. components metadata document See metadata document. 142 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

143 Glossary consistent Console server conventional backup Critical Volume State of a dataset that is fully and immediately available to an application view. Software program that is used to manage NetWorker servers and clients. The Console server also provides reporting and monitoring capabilities for all NetWorker processes. See nonpersistent snapshot. Any volume containing system state files or files for an installed service, including volumes mounted as NTFS directories which contain such files. The volume where a critical volume is mounted is also considered to be critical. This is required to perform an offline restore, however maybe optional for this release depending upon the difficulties of implementing this feature. D domain controller Data Mover (DM) data retention policy datawheel datazone Dynamic Drive Sharing (DDS) device Computer that stores directory data and manages user interactions within a domain, including logon, authentication, directory searches, and access to shared resources. Client system or application, such as NetWorker, that moves the data during a backup, recovery, or snapshot operation. See also proxy client. See retention policy. See library. Group of hosts administered by a NetWorker server. Feature that allows NetWorker software to recognize shared drives. 1. Storage unit that reads from and writes to backup volumes. A storage unit can be a tape device, optical drive, autochanger, or file connected to the server or storage node. 2. When dynamic drive sharing (DDS) is enabled, refers to the access path to the physical drive. DFS (Distributed File System) directed recovery directive disk subsystem Microsoft Windows add-on that allows you to create a logical directory of shared directories that span multiple machines across a network. Method of recovery that recovers data that originated on one client computer and re-creates it on another client computer. Instruction that directs NetWorker software to take special actions on a given set of files for a specified client during a backup or recovery operation. Directives are ignored in manual (unscheduled) backups. Integrated collection of storage controllers or HBAs, disks, and any required control software that provides storage services to one or more hosts, such as CLARiiON arrays. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 143

144 Glossary F file index file system See client file index. 1. The software interface used to save, retrieve, and manage files on storage media by providing directory structures, data transfer methods, and file association. 2. The entire set of all files. full backup See level. G group granular recovery Client or group of client computers that are configured to back up files at a designated time of day. Granular recovery provides the ability to recover specific files in seconds from a single backup. This dramatically reduces the recovery time and the footprint of the backup on storage resources. H high-available system host ID System of multiple computers configured as cluster nodes on a network that ensures that the application services continue despite a hardware or software failure. Each cluster node has its own IP address with private resources or disks that are available only to that computer. Serial number that uniquely identifies a host computer. I inactivity timeout incremental backup instant backup instant restore Number of minutes to wait before a client is considered to be unavailable for backup. Backup level in which only files that have changed since the last backup are backed up. See also level. Process of creating a point-in-time copy (snapshot) of data from a single client and saving it on a primary storage volume, which can be immediately recovered as a backup copy. Process of copying data created during an instant backup to its original location, or to an alternate location, during a recover operation. J jukebox label legacy method See library. Electronic header on a volume used for identification by NetWorker or other Data Mover application. Use of special-case Microsoft APIs to back up and recover operating system components, services, and applications. 144 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

145 Glossary level library library sharing local cluster client locale settings LUN (logical unit) LUN address Backup configuration option that specifies how much data is saved during a scheduled or manual backup. A full (f) backup backs up all files, regardless of whether they have changed. Levels one through nine [1-9] backup files that have changed since the last lower numbered backup level. An incremental (incr) backup backs up only files that have changed since the last backup. Hardware device that contains one or more removable media drives, as well as slots for pieces of media, media access ports, and a robotic mechanism for moving pieces of media between these components. Libraries automate media loading and mounting functions during backup and recovery. The term library is synonymous with autochanger, autoloader, carousel, datawheel, jukebox, and near-line storage. Shared access of servers and storage nodes to the individual tape drives within a library. NetWorker client that is not bound to a physical machine, but is instead managed by a cluster manager. It is also referred to as a logical or virtual client. Settings that specify the input and output formats for date and time, based on local language conventions. Logical unit of storage on a CLARiiON system. This refers to a device or set of devices, usually in a CLARiiON storage array. SCSI identifier of a logical unit number (LUN) within a device target. Each LUN address identifies a device on a SCSI bus that can perform input/output (I/O) operations. M manual backup media media database media index metadata document mount mount point Backup that a user performs from the client, also known as an unscheduled backup or an ad hoc backup. The user specifies the files, file systems, and directories to back up. Physical storage medium, such as magnetic tape, optical disk, or file system to which backup data is written. Database that contains indexed entries of storage volume location and the life cycle status of all data and volumes managed by the NetWorker server. See also volume. See media database. VSS Information stored in an XML document that is passed from the Writer to the requestor. Metadata includes the writer name, files, and components to back up, a list of components to exclude from the backup, and the methods to use for recovery. See also shadow copy set. To make a database available for use or to place a removable tape or disk volume into a drive for reading or writing. See volume mount point. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 145

146 Glossary N NDMP (Network Data Management Protocol) NetWorker administrator NetWorker client NetWorker Console server NetWorker Management Console NetWorker server NetWorker storage node nonclone pool noncritical volume nonpersistent snapshot TCP/IP-based protocol that specifies how heterogeneous network components communicate for the purposes of backup and recovery. User who can add to or change the configuration of the NetWorker server, media devices, and libraries. NetWorker administrators must have their usernames included in the NetWorker server Administrator list. See client. See Console server. See Console server. Computer on a network running the NetWorker software, containing the online indexes, and providing backup and recover services to the clients on the same network. See storage node. Pools that contain data that has not been cloned. A volume containing files that are not part of the system state or an installed service. The backup of non-critical volumes is not supported by either product for their initial releases. Snapshot backup that is moved to secondary storage on the NetWorker server or storage node and is no longer available for instant restore from a supported type of primary storage. O online indexes Online restore Offline restore operator Databases located on the NetWorker server that contain all the information pertaining to the client backups (client file index) and backup volumes (media database). A restore operation performed using the normal recover UI, and the computer has been booted from an installed operating system. A restore operation performed from the WinPE environment. Person who monitors the server status, loads backup volumes into storage devices, and executes day-to-day NetWorker tasks. P pathname Set of instructions to the operating system for accessing a file. An absolute pathname indicates how to find a file starting from the root directory. A relative pathname indicates how to find the file starting from the current directory. 146 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

147 Glossary persistent snapshot PiT (point-in-time copy) policy pool PowerSnap provider proxy client Snapshot that is retained on disk. A persistent snapshot may or may not be rolled over to tape. Fully usable copy of a defined collection of data, such as a consistent file system, database, or volume, which contains an image of the data as it appeared at a single point in time. A PiT copy is also called a shadow copy or a snapshot. Set of constraints that specify how long the save sets for a client are available for recovery. Each client has a browse policy and a retention policy. When the retention policy expires, the save sets associated with that policy are marked recyclable. Feature to sort backup data to selected volumes. EMC technology that provides point-in-time snapshots of data to be backed up. Applications that are running on the host system continue to write data during the snapshot operation, and data from open files is included in the snapshots. Software component defined by Microsoft VSS, that plugs in to the VSS environment. A provider, usually produced by a hardware vendor, enables a storage device to create and manage snapshots. Surrogate client that performs the NetWorker save operation for the client that requests the backup. A proxy client is required to perform a serverless backup. Q quiescing Process in which all writes to disk are stopped and the file system cache is flushed. Quiescing the database prior to creating the snapshot provides a transactionally consistent image that can be remounted without file system checks or database consistency checks. Quiescing a database is the most common way of creating a database snapshot. R recover Registry requestor replica resource restore retention policy To recover files from a backup volume to a client disk. Microsoft Windows database that centralizes all Windows settings and provides security and control over system, security, and user account settings. Interface with the Microsoft VSS infrastructure to initiate the creation and destruction of shadow copy. NetWorker software is a requestor. See shadow copy. Component that describes the NetWorker server or its clients. Clients, devices, schedules, groups, and policies are all NetWorker resources. Each resource has attributes that define its properties. Process of retrieving individual datafiles from backup storage and copying the files to disk. NetWorker policy that specifies the minimum period of time that must elapse before backed-up data is eligible to be overwritten on the backup media. Backed-up data that has not exceeded its browse policy time can be recovered more quickly than data that has exceeded its browse policy time but not its retention policy time. See also browse policy. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 147

148 Glossary retrieve rollback restore rollover root To locate and recover archived files and directories. Process by which a specific point-in-time copy (snapshot) of data is restored to the source location by using the hardware's particular capabilities. A rollback restore is a destructive save set restore. Process of backing up a snapshot to a conventional backup medium such as tape. Whether or not the snapshot is retained on disk depends on the snapshot policy. Highest level of the system directory structure. S save set SSID (save set ID) save set recover save set status server index serverless backup service port shadow copy shadow copy set shadow copy technology skip snap clone snap ID snap set Group of files or a file system from a single client computer, which is backed up on storage media. Internal identification number assigned to a save set. To recover data by specifying save sets rather than by browsing and selecting files or directories. NetWorker attribute that indicates whether a save set is browsable, recoverable, or recyclable. The save set status also indicates whether the save set was successfully backed up. See client file index. Backup method that uses a proxy client to move the data from primary storage on the application server host to secondary storage on another host. Serverless backups free up resources on the application server by offloading the work of processing snapshots to a secondary host. Port used to listen for backup and recover requests from clients through a firewall. Temporary, point-in-time copy of a volume created using VSS technology. See also Volume Shadow Copy Service (VSS). Complete roadmap of what was backed up at a single instant in time. The shadow copy set contains information about the writers, their components, metadata, and the volumes. A backup components metadata document containing that information is created and returned to the requestor after the snapshot is complete. Networker uses this document with the corresponding save set at recover time. Defined and standard coordination between business application, file system, and backup application that allows a consistent copy of application and volume data to exist for replication purposes. Backup level in which designated files are not backed up. Exact copy of a snap set data backup. The clone operation is an archive operation without the deletion of the source data. A new snap ID is assigned to the cloned copy. Also known as a snapid, a unique 64-bit internal identification number for a snap set. Group of files, volumes, or file systems from a single client, describing the collection of data for which a point-in-time copy is created on an external disk subsystem, such as a storage array. 148 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

149 Glossary snapshot snapshot expiration policy snapshot policy snapshot retention policy staging stand-alone device storage device storage node system state Point in time, read-only copy of data created during an instant backup. Policy that determines how long snapshots are retained before their storage space is made available for the creation of a new snapshot. Set of rules that control the lifecycle of a snap set. The snapshot policy specifies the frequency of snapshots, and how long snapshots are retained before recycling. Policy that determines how many PIT copies are retained in the media database and thus are recoverable. Moving data from one storage medium to a less-costly medium, and later removing the data from its original location. Storage device that contains a single drive for backing up data. Stand-alone devices cannot store or automatically load backup volumes. See device. Storage device physically attached to a computer other than the NetWorker server, whose backup operations are administered from the controlling NetWorker server. All files that belong to VSS writers with a usage type of BootableSystemState or SystemService. This is required to perform an offline restore. V volume 1. A unit of physical storage medium, such as a magnetic tape, optical disk, or file system to which backup data is written. 2. An identifiable unit of data storage that may reside on one or more host disks. volume ID volume mount point volume name volume pool Volume Shadow Copy Service (VSS) VSS VSS component Internal identification that NetWorker software assigns to a backup volume. Disk volume that is grafted into the namespace of a host disk volume. This allows multiple disk volumes to be linked into a single directory tree, and a single disk or partition to be linked to more than one directory tree. Name assigned to a backup volume when it is labeled. See also label. See pool. Microsoft technology that creates a point-in-time shadow copy of a disk volume. NetWorker software backs up data from the shadow copy. This allows applications to continue to write data during the backup operation, and ensures that open files are not omitted. See Volume Shadow Copy Service (VSS). Subordinate unit of a Writer. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 149

150 Glossary W Writer Database, system service, or application code that provides metadata document information about what to back up and how to handle VSS components and applications during backup and recovery operations. A Writer provides information to requestors to ensure that application data is consistent, application files are closed and ready for a slight pause to make a Shadow Copy. 150 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

151 Index A Active Directory (AD) disaster backup and recovery 36 granular backup and recovery 36 Active Directory Lightweight Directory Services (AD LDS) 110 ADAM authoritative restore 111 nonauthoritative restore 111 recovery options 110 AES encryption conflict with EFS encryption 117 All save set considerations for 101 application information attribute applications 62 Cluster Writer 131 Application Specific Module (ASM) pass phrase 116 authoritative restore ADAM 111 Cluster Writer 133 DFS 112, 113 FRS 114 NTDS 116 Avamar 75, 86 configuration 76 B backup client resource configuring 59 configuring multiple 59 backup command attribute applications 102 backup groups configuring 57 backup levels, deduplication 77 backup pool creating for snapshots 51 backup save sets applications 60 specifying 101 backup schedule configuring 56 backup time selecting for recovery 42 backups deduplication 77 browse time selecting for recovery 42 C CLARiiON provider overview 26 client resource configuring for backup 59 configuring for deduplication 79 configuring multiple 59 configuring when in a cluster 65, 100, 132 cluster server entering physical hostname of 102 scheduling backups for 65, 100, 132 Cluster tab 133 Cluster Writer recovery authoritative restore 133 for Windows Server nonauthoritative restore 133 options 107 common provider See EMC VSS Provider 25 connection port range specifying 69 connection to NetWorker server 40 consistency checker utility 64 conventional recovery overview 32 D data deduplication 72, 84 deduplication Avamar integration 75, 86 backup configuration notes 78 backups 77 configuration 76 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 151

152 Index configuring client 79 prerequisites 75, 86 querying deduplication save sets with mminfo 81 support 74 unsupported 74 Deduplication Node configuration 76 deduplication, data 72, 84 device configuring for rollover backup 51 DFS recovery options 111 directory services restore mode booting in for FRS recovery 118 booting in for NTDS recovery 118 disaster recovery backup 35 clustered client from a legacy non-vss backup 140 legacy VSS backup 136 NMM client 125, 128 NMM Client not on a domain controller 126 NMM Client on a domain recovery 127 support in NMM 36 SYSTEM COMPONENTS 125, 128 DNS resolution, NetWorker Deduplication Node 76 DPM disaster backup and recovery 36 granular backup and recovery 36 E EFS encryption conflict with AES encryption 117 EMC VSS Provider overview 25 encryption recovering backup data 103 Exchange consistency checker utility 64 disaster backup and recovery 36 granular backup and recovery 36 exclusion representation of save sets 38 F file system disaster backup and recovery 36 granular backup and recovery 36 recovery options 106, 108 FRS recovery booting in directory services restore mode 118 consideration for 103 options 114 full backup level consideration for 56 G granular backup and recovery support in NMM 36 granular recovery backup 35 groups configuring for backup 57 H hardware providers 26 HIDD_SELECT_VIEWABLE_CLIENTS 68 Hyper-V disaster backup and recovery 36 granular backup and recovery 36 I incremental backup level consideration for 56 instant backup overview 32 instant recovery overview 33 instant snapshot policy example 56 interface overview 38 items searching for recovery 41 L label creating for pool 52 level 1 to 9 backups consideration for 56 level for backup considerations for 56 M marking items for recovery 41 Microsoft Cluster Service 130 Microsoft VSS software provider overview 25 Microsoft Windows Server , 60, 108, 110, 130 Microsoft Windows Server 2008 support 108 mminfo, querying deduplication save sets using 81 monitoring a recovery 103, 118, 140 MSCS 130 multihomed environment 92 multiple client resources for backup 59 N NetWorker Deduplication Node, DNS resolution 76 Networker recovery options 106, 108 NetWorker server connecting to 40 nonauthoritative restore ADAM 111 Cluster Writer 133 DFS 112, 113 FRS 114 NTDS 116 nonpersistent backup overview 32 NSR_DATA_MOVER command 62 nsr_sa_ini.exe EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide

153 Index NTDS recovery booting in directory services restore mode 118 consideration for 103 options 115 O overview conventional recovery 32 instant backup 32 instant recovery 33 interface 38 nonpersistent backup 32 persistent backup 32 provider 25 requestor 25 rollback recovery 33 rollover backup 32 serverless backup 31 software provider 25 VSS writers 27 P pass phrase recovering AES encrypted data 116 password changing 70 consideration for changing 70 specifying for backup 70 password-protected recovering backup data 103 persistent backup overview 32 policies for snapshots 54 pool creating for snapshots 51 label for 52 ports service and connection port ranges 69 prerequisites deduplication 75, 86 provider overview 25 proxy client configuring 63 requirements for 64 specifying hostname of 62 R recover.exe 103 recovery ADAM options 110 browse time selection 42 Cluster options 107 Cluster Writer options 107 default method, choosing 106 DFS options 111 encrypted backup data 103 FRS options 114 marking items 41 NTDS options 115 password-protected backup data 103 performing for system data 104 searching for items 41 selecting a version 42 snapshots that have not been rolled over 117 viewing progress for 103, 118, 140 volumes required for 43 recovery, deduplication 81, 89 remote access attribute virtual cluster server specification 102 requestor overview 25 resource for backup configuring 59 configuring multiple 59 rollback recovery overview 33 performing 44 requirements for 33 rollover backup device for 51 overview 32 performing 30 S sa.ini 34 safe mode, booting in 118 save sets applications 60 exclusion representation 38 specifying for backup 101 URL encoding 61 searching for a recovery item 41 selecting items for recovery 41 server connecting to NetWorker 40 serverless backup 26 overview 31 proxy client requirement 63 service port range specifying 69 SharePoint 2007 disaster backup and recovery 36 granular backup and recovery 36 snapshot policies configuring 54 snapshots pool for 51 recovering when not rolled over 117 rollover operation 30 software provider overview 25 SQL disaster backup and recovery 36 storage array creating descriptor 34 descriptor file 34 Symmetrix provider overview 26 EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide 153

154 Index syntax application save sets 60 SYSTEM COMPONENTS disaster recovery 125, 128 system recovery performing 104 T time of backup selecting for recovery 42 topology of NetWorker multihomed 93 U URL encoding save sets 61 V version selecting for recovery 42 virtual cluster server entering physical hostname of 102 scheduling backups for 65, 100, 132 Volume Shadow Copy Service (VSS) writers 27 volumes required for recovery 43 W Windows Encrypting File System (EFS) 117 Windows Server , 60, 108, 110 Windows Server 2008 Cluster Writer nonauthoritative restore 108 Windows Server Failover Clustering (WSFC) EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide