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: BSGdocumentation@emc.com 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