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

Transcription

1 EMC NetWorker Module for Microsoft Applications Release 2.3 Application 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 Application Guide

3 Contents Preface Chapter 1 Microsoft SQL Server Backup and Recovery Overview SQL server versions supported by NMM Types of supported backup and recovery Writers for SQL data backup and recovery Commands used by NMM for SQL data backup and recovery Performing SQL server backups SQL server application information variable settings Displaying valid SQL data save sets URL encoding for SQL save sets Specifying save sets for SQL data Configuring SQL server backups Performing SQL server recovery Recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases from the SQLServerWriter save set Recovering SQL server 2005, SQL server 2008, or SQL server 2008 R2 Express databases from the SYSTEM COMPONENTS save set Recovering SQL instance for SQL clusters Performing SQL server directed recovery to an alternate location Steps for SQL server directed recovery Selecting the NetWorker server Selecting a client Selecting the desired SQL databases for directed recovery Recover by using the default recover path Recover by using an alternate recover path Examples of log messages in NMM log file and Monitor page Attaching the recovered SQL databases Performing SQL server disaster recovery SQL server (stand-alone) disaster recovery on Windows server SQL server (stand-alone) disaster recovery on Windows server SQL server cluster disaster recovery on Windows server 2008 and Windows server Best practices EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 3

4 Contents Chapter 2 Chapter 3 Chapter 4 Microsoft Active Directory Backup and Recovery Overview Types of supported backup and recovery Specifying save sets for scheduled backups Performing an Active Directory or ADAM full backup Performing Active Directory or ADAM granular backup Considerations for granular backup Configuring Active Directory or ADAM granular backups Performing an all Active Directory data recovery Performing an Active Directory granular recovery Recovery restrictions for Active Directory Recovering an Active Directory object or object attribute Selecting Active Directory object attributes Performing Active Directory disaster recovery Microsoft Data Protection Manager Backup and Recovery Overview NMM and DPM scenario Types of supported backup and recovery Types of DPM data backed up by NMM DPM backup writers NMM commands required for DPM backup and recovery Performing DPM server backups DPM application information variable settings Displaying valid DPM data save sets Specifying DPM save sets for application data Configuring DPM backups Performing a granular recovery of DPM objects Recovering a folder or file from a DPM replica Reviewing settings before starting recovery Performing a granular directed recovery to a DPM-protected server DPM directed granular recovery scenario Performing a directed granular recovery Performing DPM writer disaster recovery Microsoft Hyper-V Backup and Recovery Overview Operating system versions supported by NMM client Integration Components version Hyper-V parent partitions, child partitions, and applications within child partitions Types of supported backup and recovery Hyper-V configuration Hyper-V storage configurations supported by NMM Hyper-V configuration requirements for backing up a child partition that contains multiple volumes Components used by NMM for Hyper-V backup and recovery Performing Hyper-V backups Hyper-V application information variable settings Specifying Hyper-V save sets for application data Displaying valid Hyper-V save sets NMM support for proxy backup of Hyper-V Preparing a child partition for backup EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

5 Contents Configuring Hyper-V backups Configuring a Hyper-V client resource Performing Hyper-V recovery Turning the child partition offline for recovery Hosting the recovered virtual systems Specifying the destinations for the Hyper-V configuration files and virtual system Selecting Hyper-V recovery options Selecting the destination of Hyper-V recovery Performing Hyper-V recovery to the original machine and location Performing directed Hyper-V recovery to a different machine or location Performing Hyper-V parent partition disaster recovery Best practices Hyper-V parent partition backup and recovery Hyper-V child partition applications backup and recovery Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 failover cluster Chapter 5 Microsoft Exchange Server Backup and Recovery Overview Microsoft Exchange server 2007 MAPI client and Collaboration Data Objects support Exchange server versions supported by NMM client NMM and Exchange server support for I18N Types of supported backup Backup levels Types of supported recovery Compatibility with previous Exchange server backups Creation of shadow copy and snapshot process in an Exchange server production LAN-based Exchange server configuration with a storage area network and a proxy client Exchange backup scenarios Exchange recovery scenarios Exchange 2003 and 2007 writers Commands and attributes for Exchange backup and recovery Configuring dedicated storage node for Exchange 2007 CCR environment Performing Exchange server backups Exchange 2003 and 2007 application information variable settings Specifying Exchange 2003 and 2007 save sets for application data Displaying valid Exchange data save sets Configuring persistent snapshots Configuring Exchange server backups Configuring Exchange backup schedule Configuring Exchange client resource Performing Exchange server recovery Exchange recovery requirements Exchange recovery options Configuring Exchange recovery Selecting a storage group restore destination EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 5

6 Contents Performing Microsoft Exchange server 2007 directed recovery Performing a directed recovery Performing Microsoft Exchange server 2007 disaster recovery Performing Microsoft Exchange server 2007 (stand-alone) disaster recovery Performing Microsoft Exchange server 2007 disaster recovery for Microsoft Exchange CCR to a two-node cluster in a production environment Performing Microsoft Exchange server 2007 disaster recovery for Exchange CCR in a production environment Performing a quick recovery of a deleted mailbox in Exchange Best practices Backups should be grouped with no more than 10 storage groups at a time Use consistency check parameters to set threading and throttling to handle performance issues Additional Exchange backup and recovery best practices Exchange recovery limitations Chapter 6 Microsoft Exchange 2010 Server Backup and Recovery Overview Supported operating systems Types of backup and recovery Exchange 2010 VSS writers LAN-based Exchange server configuration with a storage area network and a proxy client Exchange server 2010 DAG scenario Backup initiated transaction log file truncation Microsoft Exchange server 2010 MAPI client and Collaboration Data Objects version for Recovery Database item level recovery in Exchange Performing Exchange 2010 backups Backup options Specifying Exchange 2010 application data save sets Displaying save set syntax Exchange 2010 application information variable settings Configuring persistent and non-persistent snapshots Configurations for backing up Exchange 2010 in non-dag and DAG environment Prerequisites before running a backup on the Exchange 2010 system Promoting Exchange 2010 incremental backup to full backup Configuring Exchange server 2010 backups Configuring Avamar deduplication backups in a DAG environment Performing non-persistent backup of Microsoft Exchange Verifying backups Performing Exchange server 2010 recovery Performing full recovery Performing advanced recovery Performing granular recovery of mailbox, folder, or Performing a quick recovery of a deleted mailbox in Exchange Microsoft Exchange server 2010 disaster recovery Best practices EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

7 Contents Chapter 7 Chapter 8 Microsoft SharePoint Server 2003 Backup and Recovery Overview VSS backup support provided by NMM Microsoft SharePoint Portal server 2003 and Windows SharePoint Services Types of supported backup Supported SharePoint 2003 writers Commands used SharePoint 2003 backup and recovery Performing SharePoint 2003 backups SQL application information variable settings in SharePoint 2003 backup Displaying valid SQL data save sets for SharePoint 2003 backup Configuring SharePoint 2003 backup tasks Performing SharePoint 2003 recovery Example of SharePoint 2003 backup and recovery process Creating a new SharePoint portal with three new databases Viewing the location and hierarchy of databases as they appear in SQL Enterprise Manager UI Configuring and performing a backup of the new databases with NMM save sets Verifying that all databases are backed up through the UI Deleting the new databases Performing an NMM recovery of the databases Verifying database recovery through the SQL Enterprise Manager Recovering the portal site through SharePoint Portal Server Central Administration Verifying the creation of the portal site in SharePoint Server Central Administration Microsoft SharePoint Server 2007 Backup and Recovery Overview NMM solutions for protecting a Microsoft SharePoint 2007 farm Microsoft Office SharePoint server 2007 and Windows SharePoint Services Types of SharePoint server 2007 backup and recovery Microsoft Office SharePoint 2007 farm configurations SharePoint 2007 writers Performing SharePoint 2007 backups SharePoint 2007 application information variable settings URL encoding for SharePoint save sets Specifying SharePoint 2007 save sets for application data Displaying valid SharePoint 2007 data save sets Configuring SharePoint 2007 backups Performing SharePoint 2007 farm hardware backups Performing SharePoint 2007 recovery Full recovery of a stand-alone SharePoint farm Full recovery of a distributed SharePoint farm Recovery of individual SharePoint content databases Recovery of SharePoint Search/Content Indexes Rollback of SharePoint SQL databases Performing SharePoint 2007 disaster recovery Disaster recovery planning Performing a disaster recovery Keeping backups and recoveries in sync EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 7

8 Contents Best practices for disaster recovery Backing up SharePoint database by using NMM and NMSQL Chapter 9 Chapter 10 Chapter 11 Microsoft SharePoint Server 2010 Backup and Recovery Overview New features in Microsoft SharePoint Microsoft SharePoint 2010 support on Microsoft Windows server Microsoft SharePoint server 2010 and SharePoint Foundation Types of SharePoint server 2010 backup and recovery NMM and Microsoft Office SharePoint 2010 farm configurations SharePoint 2010 writers Performing SharePoint 2010 backups Specifying SharePoint 2010 application data save sets Displaying valid SharePoint 2010 data save sets Prerequisites for SharePoint 2010 backup Performing SharePoint 2010 backup Performing SharePoint 2010 recovery Performing SharePoint 2010 disaster recovery Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM Overview Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is installed Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is uninstalled Basic steps for Windows Disaster Recovery backup and recovery Performing Windows Disaster Recovery backup and recovery for Microsoft applications Perform a Windows DR backup Perform a Windows DR recovery Troubleshooting About the troubleshooting process Setting up notifications Finding errors NMM client error messages E_VOLUME_NOT_SUPPORTED E_VETO_PROVIDER VSS_E_WRITERERROR_RETRYABLE error code 0x800423f VSS CLIENT... Invalid Writer Selection... for APPLICATIONS Savegroup failed in scheduled backup Insufficient permission to access mailbox. See documentation for required permission settings. Server MBX is not capable of RSG operations :nsrsnap_vss_save NMM validation for NSP Writer failed, unable to restore NPS VSS Writer data NMM client issues In-progress backup fails NetWorker is blocked by Windows firewall NMM backups might fail where a firewall exists between the 8 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

9 Contents NetWorker server and client Need to run utility to obtain Exchange server information Requesting a snapshot for a volume on hardware that is not transportable The PowerSnap service must be restarted after the NetWorker service is restarted PowerSnap validation for recovery fails Snapshot backup may fail with writer errors Microsoft I/O write error when taking a replica in a CLARiiON array Creating a replica takes a long time in CLARiiON environment Cannot recover Exchange database due to overwrite prevention error Incremental backups may be promoted to full backups Diagnosing VSS Writer Issues Modifying the Microsoft Exchange 2007 COM+ component s user account or password Save sets may not appear in the Recover page Recovery of AES-encrypted files fails without passphrase Unable to restore files encrypted with both Microsoft Windows Encrypting File System and AES encryption Antivirus programs block recovery Snapshot cannot include both hardware and software snapshot volumes for clustered NetWorker VSS clients Cross-platform directed recovery operations are not supported on NMM Recovery of large number of items fails if one or more items in a folder is not selected Multiple client resources with the same name cannot be combined in the same group Backup of two partitions of the same CLARiiON disk fails Connection to DPM service lost during DPM recovery DPM replica backup is not correctly configured Backup fails if Exchange server in is renamed after it is created In Exchange 2010, recovery fails for renamed mailbox database, however backup completed successfully for renamed database In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of new database name after renamed mailbox database Save sets from an Avamar AFTD for NMM backups show retention set to 1/18/ Microsoft updates required to fix the vds.exe crash errors during retention on Windows 2008 and Windows Back up of SYSTEM COMPONENTS fails due to missing System Writer Problems with RMExchangeInterface component SharePoint backup fails when host and proxy client do not match NMM installation issues RMAgentPS fails to uninstall when uninstalling NMM Recovery failure after.net 3.5 framework installation SYSTEM COMPONENTS failure after McAfee uninstall If Exchange is installed after NMM, NMM reinstallation is required to get Replication Manager Exchange Interface NMM uninstall and reinstall required to change the Replication Manager port number EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 9

10 Contents Checking log files NMM client PowerSnap client Replication Manager Solutions Enabler Active Directory NetWorker server Manually stopping and starting services Configuring dedicated web front-end crawling Using nsr.dir to skip files for NMM backup and recovery Troubleshooting issues during SQL databases directed recovery Name resolution Other troubleshooting resources Glossary Index 10 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

11 Tables Title Page 1 Writers used by NMM for SQL data backup and recovery Commands used by NMM for SQL data backup and recovery SQL variable settings for Application Information attribute Special characters and their URL-encoded values SQL save set syntax Tasks for scheduling a backup SQL server backup and recovery best practices and considerations Tasks for Active Directory or ADAM granular backup Considerations for NMM client backup schedules System-only attributes that are not backed up Retained attributes after object is deleted NMM Data Protection Manager commands DPM application information variable settings DPM server 2007 save set syntax Special characters and their URL-encoded values Tasks for scheduling a backup Hyper-V child partition configurations NMM Hyper-V components Hyper-V application information variable settings Hyper-V save set syntax Backup tasks for Hyper-V Writers used by NMM for Exchange server backup and recovery Commands and attributes used by NMM for Exchange server backup and recovery Exchange application information variable settings Exchange 2003 and 2007 save set names Special characters and their URL-encoded values Tasks for configuring an Exchange server backup Different backup procedures for Exchange recovery Best practices and considerations for application backups Exchange 2010 VSS writers Exchange 2010 save sets for application data Exchange application information variable settings Configurations required for backup in non-dag and DAG environment Tasks for configuring an Exchange server backup SharePoint features and details List of supported SharePoint writers Backup tasks for SharePoint Example: Minimum required save sets to be backed up List of supported SharePoint 2007 writers EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 11

12 Tables 40 SharePoint application information variable settings Special characters and their URL-encoded values SharePoint save set syntax Tasks for SharePoint 2007 backups SharePoint server backup list for disaster recovery List of supported SharePoint 2010 writers SharePoint save set syntax Supported and unsupported system recovery scenarios Notifications and errors Services and processes used in NMM client EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

13 Figures Title Page 1 Configuration Options dialog box Client menu APPLICATIONS > SqlServerWriter tree nodes File System Recovery dialog box NMM protection of DPM DPM recovery modes Recover submenu for DPM recovery DPM granular recovery available to file level DPM granular recovery options Directed recovery of FileServer DPM database and replicas available as selectable items DPM disaster recovery options Windows server 2008 or Windows server 2008 R2 host with Hyper-V child partitions NMM backup of Hyper-V components Hyper-V storage options Disaster recovery order for a Hyper-V server Snapshot process with Exchange production server and proxy client SCC architecture CCR core architecture Exchange Recovery Options window with Conventional Restore option selected Available and unavailable storage groups Restore To command on context menu RSG Configuration error message RSG Configuration correct message Public folders cannot be recovered to an RSG Selected and partially selected items Recovered Items folders in user mailbox Select Storage Group Restore Destination dialog box Local client on the taskbar next to Client Select Viewable Clients dialog box Select Exchange 2010 database Advanced Recovery dialog box Manage RDB window Create_DB window Exchange Recovery Summary Select Database window Select mailbox, folder or for recovery Newly created databases created in SharePoint EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 13

14 Figures 39 NMM backups available for recovery SQL databases selected for recovery in NMM Databases recovered to SQL server SharePoint Server Central Administration page SharePoint Portal Server Central Administration, Manage Portal Sites window Portal creation and restore options Portal restore and database names Confirmation page for request to create a portal site Status window for portal creation process Operation Successful page displayed when portal creation is complete Recovered databases and SharePoint portal visible and available in SharePoint SharePoint 2007 stand-alone farm configuration SharePoint 2007 distributed farm configuration Restore Remote Dependencies dialog box List of Microsoft applications that are supported for Windows DR backups Troubleshooting process EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

15 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 Powerlink website to ensure that you are using the latest version of this document. Purpose This guide contains information for backing up and recovering Microsoft applications like SQL, SharePoint, Exchange, Active Directory, Hyper-V, and Data Protection Manager by using EMC NetWorker Module for Microsoft Applications. IMPORTANT The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide supplements the NetWorker Module for Microsoft Application backup and recovery procedures described in this guide and must be referred to when performing application specific tasks in this guide. Ensure to download a copy of the EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide from the EMC Powerlink website before using this guide. 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: Storage subsystems, such as EMC CLARiiON or Symmetrix, if used EMC NetWorker software EMC NetWorker Snapshot management Microsoft Volume Shadow Copy Service (VSS) technology EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 15

16 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 Administration Guide EMC NetWorker Module for Microsoft Applications and EMC CLARiiON Implementing Proxy Node Backups 2.3 Technical Notes EMC NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing Proxy Node Backups 2.3 Technical Notes EMC NetWorker Licensing Guide EMC Information Protection Software Compatibility Guide EMC Solutions Enabler Symmetrix CLI Quick Reference EMC NetWorker Release 7.6 Service Pack 1 documentation EMC NetWorker Release 7.6 Service Pack 2 documentation Note: 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 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) 16 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

17 Preface 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 select 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 Application Guide 17

18 Preface 18 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

19 1 Microsoft SQL Server Backup and Recovery This chapter includes the following topics: Overview Performing SQL server backups Performing SQL server recovery Performing SQL server directed recovery to an alternate location Performing SQL server disaster recovery Best practices Microsoft SQL Server Backup and Recovery 19

20 Microsoft SQL Server Backup and Recovery Overview Backup and recovery of Microsoft SQL server involves the following: SQL server support for VSS through Microsoft-supplied application writers. Creation of a point-in-time copy of data in EMC NetWorker Module for Microsoft Applications (NMM). The snapshot includes point-in-time copy of data and open files, which allows the backup of the SQL server while the SQL database is online or in use. Review the following sections before performing SQL server backup and recovery: SQL server versions supported by NMM on page 20 Types of supported backup and recovery on page 21 Writers for SQL data backup and recovery on page 22 Commands used by NMM for SQL data backup and recovery on page 22 SQL server versions supported by NMM The EMC Information Protection Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions supported by the NMM client. NMM client supports the following versions of Microsoft SQL server: SQL server 2008 R2 (x86, x64): Standard Enterprise Note: It is recommended that you use Cumulative Update 4. SQL server 2008 SP2 (x86, x64): Standard Enterprise SQL server 2005 (x86, x64) Service Pack 4: Standard Enterprise SQL server 2008 R2 Express edition SQL server 2008 Express edition SQL server 2005 Express edition Note: NMM only supports databases in SQL simple recovery. NMM client does not support the following: SQL server running on IA64 SQL server EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

21 Microsoft SQL Server Backup and Recovery Types of supported backup and recovery NMM supports database granularity for snapshot backup and restore. This allows you to back up a particular SQL database without having to shut down the database, and then select and restore that database from the backed-up databases. NMM provides the following types of backup: Point-in-time snapshots, which include exact copy of data at that time including open files information Full backups for both SQL server 2005, SQL server 2008, and SQL server 2008 R2: Both default and named instances of SQL sever can be backup User defined Database level backup can also be performed Backup of databases with TDE encryption and file stream for SQL server 2008 and SQL server 2008 R2 Backup of databases having file groups for SQL server 2005, SQL server 2008 and SQL server 2008 R2 Performing SQL server backups on page 22 provides details. Note: NMM 2.3 does not support: SQL log backups for either SQL 2005, SQL 2008, and SQL 2008 R2. Incremental backups for SQL application. Individual file groups and files backup. NMM provides the following types of recovery: Full recovery of SQL server 2005, SQL 2008, and SQL 2008 R2 databases Disaster recovery Recovery of databases with TDE encryption and file stream for SQL 2008 and SQL 2008 R2 Recovery of databases having file groups for SQL 2005, SQL 2008 and SQL 2008 R2 Performing SQL server recovery on page 27 and Performing SQL server disaster recovery on page 35 provide details. Overview 21

22 Microsoft SQL Server Backup and Recovery Writers for SQL data backup and recovery Table 1 on page 22 lists the writers used by NMM to back up SQL data. Table 1 Writers used by NMM for SQL data backup and recovery Writers Application writers SqlServerWriter Description NMM uses the application writers provided by SQL server. NMM uses the VSS writer for SQL server 2005, SQL server 2008, SQL server 2008 R2. Note: The MSDEWriter for SQL server 2000 is no longer supported. IMPORTANT When performing SQL writer recovery, manually stop and start of the services. Commands used by NMM for SQL data backup and recovery Table 2 on page 22 lists the commands used by NMM to back up SQL data. Table 2 Commands used by NMM for SQL data backup and recovery Commands nsrsnap_vss_save nsrsnap_vss_recover Description The NMM command to initiate the VSS-based backup. The NMM command to initiate the VSS-based recovery. Performing SQL server backups Ensure that: The SQL server VSS Writer service is enabled during backup. All databases are mounted when backing up data for a Microsoft SQL application. Unmounted databases are not backed up, and no warning appears during the backup operation to indicate if any databases are unmounted. IMPORTANT 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. or - The SYSTEM COMPONENTS:\ save set along with the system volume, for example, C:\. EMC recommends that no more than 200 databases are backed up at one time. If database sizes are large, this should be less. 22 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

23 Microsoft SQL Server Backup and Recovery This section provides the following information: SQL server application information variable settings on page 23 Displaying valid SQL data save sets on page 23 URL encoding for SQL save sets on page 24 Specifying save sets for SQL data on page 25 Configuring SQL server backups on page 25 SQL server application information variable settings Table 3 on page 23 lists the variables that can be specified in the Application Information attribute of the client resource. Table 3 SQL variable settings for Application Information attribute Attribute name Description Values NSR_SNAP_TYPE=value Specifies the snapshot service provider name. vss This value is required. NSR_DATA_MOVER=value application information attribute Specifies the hostname of the NMM client that mounts the snapshot from NMM client to the proxy host. The host can be either a local host or a proxy client host. Note: This attribute is required for hardware provider backups that are configured to use data mover. The local host The proxy client hostname Consider the following: If no value is typed, 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. Displaying valid SQL data save sets To display a list of the SQL save sets that are available for backup: 1. Open a command prompt on the application server. 2. Ensure that the SQL server VSS Writer service is enabled and running. 3. From the command prompt, type the following command to list the valid application data save set names: If the application server is not on a virtual host, type: nsrsnap_vss_save -? If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server: nsrsnap_vss_save -? -c virtual_server_name 4. Press Enter: 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, without the double quotes. Performing SQL server backups 23

24 Microsoft SQL Server Backup and Recovery The 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 URL encoding for SQL 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 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 Table 4 on page 24 lists the most commonly used special characters and their URL values. Table 4 Special characters and their URL-encoded values (page 1 of 2) Special character URL-encoded value Special character URL-encoded value \ %5C? %3F / %2F ] %5D " %22 [ %5B 24 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

25 Microsoft SQL Server Backup and Recovery Table 4 Special characters and their URL-encoded values (page 2 of 2) Special character URL-encoded value Special character URL-encoded value % %25 } %7D # %23 { %7B & %26 ^ %5E < %3C %60 > %3E %7C Specifying save sets for SQL data Specify SQL data save sets in the Save Set attribute of a client resource. Table 5 on page 25 lists the SQL save set syntax to specify for supported types of SQL data. Type of data to back up Table 5 SQL save set syntax Save set syntax All default instance SQL data along with SQL Server named instances and databases. Only the named instance and database name combination APPLICATIONS:\SqlServerWriter Ensure that the SQL server VSS Writer service is enabled and running before using this save set. For instance level backup: APPLICATIONS:\SqlServerWriter\host%5Cinstance For example, to back up a SQL Server named instance MT11\BU, type the following: APPLICATIONS:\SqlServerWriter\MT11%5CBU\ Some special characters in a SQL server named instance or database name must be replaced with their URL-encoded values. URL encoding for SQL save sets on page 24 provides more information about URL encoding. IMPORTANT nsrsnap_vss_save -? does not list APPLICATIONS:\SqlServerWriter as a save set if only SQL Express is installed. The SQL 2005, SQL 2008, and SQL 2008 R2 Express databases are backed up from SYSTEM COMPONENTS:\ save set. Configuring SQL server backups To perform a full backup of SQL server for all VSS writers that are supported by NMM, complete the tasks outlined in Table 6 on page 26. Performing SQL server backups 25

26 Microsoft SQL Server Backup and Recovery IMPORTANT The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details for the first four tasks in Table 6 on page 26. Table 6 Tasks for scheduling a backup Backup task 1. Configure a backup pool for snapshot operations Consideration Snapshots create meditate 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 meditate. 2. Configure snapshot policies For SQL server backups, the backup snapshot policy can be set to All or None. 3. Configure a backup schedule Backup schedules determine the days on which full backups are run. Full backups include all of the data specified in an NMM client resource save set. 4. Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. 5. Configure a SQL server client resource on page 26 This task is specific to configuring a SQL server client resource. Configure a SQL server client resource To configure a SQL server 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, that is the fully qualified name, of the NetWorker client computer. Note: If backing up a SQL clustered instance, use the virtual SQL name here. Create client resources for all physical cluster nodes where the SQL clustered instance is run. 5. In the Comment attribute, type a description. Note: 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: If needed, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource. 26 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

27 Microsoft SQL Server Backup and Recovery URL-encoded values are used to represent special characters such as the backslash (\). A table of values is provided in URL encoding for SQL save sets on page 24. To back up SQL server 2005, SQL server 2008, SQL server 2008 R2 named instances and default instances together, specify the save set name: APPLICATIONS:\SqlServerWriter The SQL server save set syntax is described in Displaying valid SQL data save sets on page Specify SQL application variable settings in the Application information attribute of the client resource. These settings are described in Table 3 on page Click the Globals (1 of 2) tab. 11. In the Aliases attribute, type the NETBIOS name for the client. Note: 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. Performing SQL server recovery Note: Although this release no longer supports SQL server 2000, you can use NMM to recover previous backups of SQL server 2000 data. The tasks for recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases are different from those for SQL server 2005, SQL server 2008, SQL server 2008 R2 Express databases. Review the following sections that are applicable for your setup: Recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases from the SQLServerWriter save set on page 27 Recovering SQL server 2005, SQL server 2008, or SQL server 2008 R2 Express databases from the SYSTEM COMPONENTS save set on page 28 Recovering SQL instance for SQL clusters on page 28 Recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases from the SQLServerWriter save set When system databases are recovered, the SQL server services for the SQL database instances are automatically detected and stopped by NMM. After the recovery is complete, NMM automatically starts the SQL server services for the SQL server database instances. When user databases are recovered, the services are not stopped or started as with system databases. Performing SQL server recovery 27

28 Microsoft SQL Server Backup and Recovery To recover SQL server 2005, SQL server 2008, and SQL server 2008 R2 stand-alone databases: 1. From the navigation tree, expand the Applications folder and the SQLServerWriter folder. 2. Select the databases to recover. 3. From the System Recover Session toolbar, click Start Restore. Recovering SQL server 2005, SQL server 2008, or SQL server 2008 R2 Express databases from the SYSTEM COMPONENTS save set To recover SQL server Express databases that were backed up to the SYSTEM COMPONENTS save set: 1. If restoring the master database, stop the SQL server services for the SQL server database instances. 2. From the navigation tree, expand the SYSTEM COMPONENTS:\ folder. 3. In the Recovery Options dialog box, clear the option Use Microsoft Best Practices for selecting the System State. 4. Under System Components, browse the writer SQL Embedded and select the required databases for restore. 5. From the System Recover Session toolbar, click Start Restore. 6. After the recovery is complete, start the SQL server services for the SQL database instances. Recovering SQL instance for SQL clusters Note: This procedure is common to all supported SQL versions and Windows platforms. For instance level recovery on SQL server cluster, perform the following steps: 1. Using Windows Cluster Management console, make the SQL Server resource under the Cluster Group of SQL Server, offline. Now the instance is down but the disk is available because the group is up. 2. Perform SQL writer recovery. Note: When performing SQL writer recovery, manually stop and start of the services. 3. In the Cluster Management console, make the SQL Server resource online. Ensure that all the other SQL resources that depend on that SQL Server are online. 28 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

29 Microsoft SQL Server Backup and Recovery Performing SQL server directed recovery to an alternate location For SQL server directed recovery: SQL databases can be selected. The NMM GUI can be started on the machine to which the SQL database is restored. The directed recovery is Pull directed recovery. Once restore is complete, the SQL Management Studio program can be used to manually attach the SQL database. The directed recovery procedure does not use SQL Writer. A restore performed without using SQL Writer guarantees a crash-consistent database, which means that there are no torn or corrupted pages. However, all transactions which were in progress at the time of the snapshot are rolled back. You would lose the ability to restore the database with no recovery, and apply log backups to it. Directed recovery is supported on the same versions of Windows servers. For example, if the backup is done on a Windows 2003 machine, then the directed recover can be done only to another Windows 2003 machine. All the database files must be recovered to a single drive. Steps for SQL server directed recovery on page 29 provides the steps for SQL directed recovery. The following are not supported: Directed recovery is not allowed from SQL System database. Directed recovery of filestream database is not supported. Directed recovery of TDE Encryption database is not supported. Directed recovery of cross-sql platform is not supported. For examples, directed recovery of SQL databases on Windows 2003 cannot be recovered on Windows 2008 and vice versa. Directed recovery to the same machine is not supported. Directed recovery to encrypted target is not supported. Directed recovery to compressed drive is not supported. Although recovery takes place, the database attachment fails. SQL Data Protection Manager (DPM) directed recovery is not supported. Directed recovery of SQL express is not supported. No validation available for restore target paths clustered paths. When a path is selected, the NMM GUI does not validate if the path is valid. The path validation is done only after recovery is started. Steps for SQL server directed recovery Before restoring the SQL database content, ensure that: The target machine on which NMM GUI is started and the source machines are added as client resource on NetWorker. The recovery drive is available and has sufficient free disk space to accommodate the data. Performing SQL server directed recovery to an alternate location 29

30 Microsoft SQL Server Backup and Recovery To perform directed recovery of SQL databases, perform the following steps: 1. Start the NMM GUI on the machine to which the SQL database is recovered. 2. Select the NetWorker server containing the SQL backups, as described in Selecting the NetWorker server on page Select the client whose backup has been taken, from the NMM GUI, as described in Selecting a client on page Select the desired SQL backups, as described in Selecting the desired SQL databases for directed recovery on page Recover the SQL databases: To the default recovery path, as described in Recover by using the default recover path on page 32. or To an alternate location from the SQL tab, as described in Recover by using an alternate recover path on page Select Start Recover. 7. When the recovery is complete: a. Copy the recovered.mdf and.ldf files to the desired location, which may be on the same drive or different drive. b. Use the SQL Management Studio program to manually attach the.mdf and the.ldf files from the respective locations. Attaching the recovered SQL databases on page 35 provides details. For multiple NMM directed recovery on same recovery farm, use the same procedure for each of the source clients. Provided there is no media access conflict, the restores can take place in parallel. Selecting the NetWorker server To select the NetWorker server containing the SQL backups: 1. To change the currently selected server, click the Change NetWorker Server icon on the toolbar. The Change NetWorker Server dialog box appears. 2. In the Change NetWorker Server dialog box: a. Click the Update Server List button to refresh the list of NetWorker servers. b. Select the desired NetWorker server and click OK. 3. Select the backed up client machine as described in Selecting a client on page 30. Selecting a client To select a client: 1. From the Options menu, select the Configure Options to add the backed-up client machine to the list of client machines that you can browse. The Configuration Options dialog box as shown in Figure 1 on page 31 appears. 30 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

31 Microsoft SQL Server Backup and Recovery Figure 1 Configuration Options dialog box 2. Click the button next to the Client Name field. The Select Viewable Clients dialog box appears. 3. Select the backed up SQL client from the Selected clients on: a. List and click Add >> to add the selected client to the list of clients in the Client to list on menu bar: list. b. Click OK. The Client menu in the NMM GUI displays the list of selected clients that you can browse. 4. Select the desired SQL client in the Client menu. Figure 2 on page 31 shows the Client menu. Figure 2 Client menu 5. Select the desired SQL server for directed recovery as described in Selecting the desired SQL databases for directed recovery on page 32. Performing SQL server directed recovery to an alternate location 31

32 Microsoft SQL Server Backup and Recovery Selecting the desired SQL databases for directed recovery To select the desired SQL databases for directed recovery: 1. After the application reloads the current browse tree, ensure that the System Recover Session option is selected. The Microsoft SQL server application backups are now displayed for directed recover browsing in the current browse tree. 2. Expand the APPLICATIONS > SqlServerWriter tree nodes as shown in Figure 3 on page 32. Figure 3 APPLICATIONS > SqlServerWriter tree nodes 3. Select the desired instance and databases. Note: The SQL System databases are not supported for SQL directed recovery. 4. Recover the SQL databases: To the default recover path, as described in Recover by using the default recover path on page 32. or To an alternate location from the SQL tab, as described in Recover by using an alternate recover path on page 33. Recover by using the default recover path To recover SQL databases by using the default recover path: 1. Select the database to be recovered using directed recovery in System recover Session. 2. Click Recover. The System Recover Session Options appears. 3. Select the Recover option, and then click the SQL tab. 4. Select the Restore SQL file to local machine using their original directory path option. 5. Click OK. 32 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

33 Microsoft SQL Server Backup and Recovery The File System Recover Summary form as shown in Figure 4 on page 33 appears. Figure 4 File System Recovery dialog box Note: The SQL database recover path is based on the original path. This is the default SQL recover path option. 6. Click Start Recover to initiate the directed recover. 7. Switch to the Monitor page to view the status and progress of the recover. Recover by using an alternate recover path There are two alternate ways of navigating to the System Recover Session Options dialog box where an alternate SQL recover path can be specified: Selecting Recover Options from the toolbar. Selecting the Recover Options button in the File System Recover Summary dialog box. This section describes how you can use the Recover Options option from the toolbar to select an alternate recover path to recover SQL databases. To recover SQL databases by using an alternate recover path: 1. Select the database to be recovered using directed recovery in System Session. 2. Click the SQL tab. 3. Specify the destination path for the SQL databases: a. Select the Specify the file system path where the SQL database(s) restored option. This enables the Browse button. Note: The field is read-only and you cannot manually type a path. b. Click Browse. The Browse For Folder dialog box appears. Performing SQL server directed recovery to an alternate location 33

34 Microsoft SQL Server Backup and Recovery 4. Select the desired recover location and click OK. The System Recover Session Options dialog box appears. 5. Click Recover. The File System Recover Summary dialog box appears. 6. Click Start Recover to initiate the directed recover. Note: If the SQL alternate recover path is invalid, for example, blank or network share is incorrect, a error message dialog box appears. 7. Switch to the Monitor page to view the status and progress of the recover. Examples of log messages in NMM log file and Monitor page Examples of messages for SQL directed recover in both the NMM log file and the UI Monitor page. Case 1: Restore to original location messages in NMM log Command line:\n C:\Program Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A NSR_SQL_TARGET_ORIG=yes -I - nsrsnap_vss_recover: flag=a arg=nsr_sql_recover_mode=alt_location nsrsnap_vss_recover: flag=a arg=nsr_sql_target_orig=yes NMM.. Performing SQL directed restore. NMM.. SQL directed restore will relocate database files to their original locations. Case 2: Restore to alternate location messages in NMM log Command line:\n C:\Program Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A NSR_SQL_TARGET_DIR=E:\ -I - nsrsnap_vss_recover: flag=a arg=nsr_sql_recover_mode=alt_location nsrsnap_vss_recover: flag=a arg=nsr_sql_target_dir=e:\ NMM.. Performing SQL directed restore. NMM.. SQL directed restore will relocate database files to path[e:\]. NMM.. SQL directed restore relocating database files for database [APPLICATIONS:\SqlServerWriter\MB-CLNT-3\AcmeBank]. NMM.. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf] to [E:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf]. NMM.. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf] to [E:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf]. NMM.. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf] to [E:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf]. 34 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

35 Microsoft SQL Server Backup and Recovery Attaching the recovered SQL databases To manually attach the recovered SQL databases: 1. Start the SQL Management Studio. 2. Start attachment of SQL database from the SQL Management Studio. 3. In the SQL Attach Database dialog box: a. Locate the primary data file to attach. SQL restores all primary database files (.mdf), logs files (.ldf), and secondary database files (.ndf), if present. b. The SQL administrator must know which files are the primary data files. c. Once the primary data file is attached, SQL automatically identifies the other database files, provided the files are all at the same location. d. If the files are not in the same location, then you must specify the respective locations of the restored files:.mdf.ldf.ndf 4. Click OK to create the database. The database is now created and available. Performing SQL server disaster recovery For SQL disaster recovery on Windows 2008 and Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery. Chapter 10, Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM provides details. In cases where the SQL server databases must be completely rebuilt, NMM can facilitate a disaster recovery. Prior to disaster recovery, use NMM to perform regular backups of volumes, system components, and application save sets. The following save sets should be backed up regularly: 1. Back up the following with the snapshot policy all. C:\ SYSTEM COMPONENTS:\ The backup of C:\ automatically includes the following: Windows Boot Volume Windows System Volume Note: If the system has been set up with a separate file system for the Windows boot\system partition and separate file system for application installation, then along with C:\ drive, back up the file system that includes the Windows Boot Volume, Windows System Volume, and application software. Specifying save sets for SQL data on page 25 provides information for SYSTEM COMPONENTS:\ backup. Note: Back up Cluster Management when backing up SQL server cluster. Performing SQL server disaster recovery 35

36 Microsoft SQL Server Backup and Recovery 2. Back up application data for SQL server with the following save set: APPLICATIONS:\SqlServerWriter Note: You must specify a separate applications save set for each SQL cluster instance when backing up SQL server cluster. The following are scenarios and procedures for recovery: SQL server (stand-alone) disaster recovery on Windows server 2008 on page 36 SQL server (stand-alone) disaster recovery on Windows server 2003 on page 36 SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003 on page 37 SQL server (stand-alone) disaster recovery on Windows server 2008 To perform a disaster recovery of SQL server on a Windows server 2008 machine: 1. Install SQL server and latest service packs, including the SQL server instances that were running on the machine before the disaster. Note: The instance names must be exactly the same as the previous ones. 2. Perform a recover of the system components and volumes. 3. Perform a recovery of the SQL server data for all previous instances. Note: In the NMM interface, clear the options for all of the system databases, or the recovery will fail. SQL server (stand-alone) disaster recovery on Windows server 2003 To perform a SQL server (stand-alone) disaster recovery on Windows server 2003: 1. Set up a new Windows 2003 machine to the following on the old machine: Machine name IP address Domain status 2. Recover SYSTEM COMPONENTS:\ and the local file system volumes. 3. Reboot the machine. 4. Log in to the machine as local administrator. 5. Unjoin the domain, and then rejoin the domain. 6. Recover the APPLICATIONS:\SqlServerWriter save set. 7. Reboot, and then recovery will be complete. 36 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

37 Microsoft SQL Server Backup and Recovery SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003 To perform a SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003: 1. Set up each new cluster machine to match the following on the corresponding old machine: Machine name IP address Domain status 2. For only Windows server 2008, on each cluster machine: a. Install SQL server 2005 and all updates that were installed on the old machines. b. Install all instances that were installed on the old machines. 3. Recover each node s SYSTEM COMPONENTS:\ and local file system volumes. 4. Reboot each new machine. 5. On each machine: a. Log in to the machine as local administrator. b. Unjoin the domain. c. Rejoin the domain. 6. For only Windows server 2008, on the active node: a. Stop SQL Instance Services. b. Restore APPLICATIONS:\SQLServerWriter save set. c. Start SQL Instance Services. 7. For only Windows server 2003, on each machine: a. Recover the APPLICATIONS:\SqlServerWriter save set. b. Reboot each machine. Cluster status recovery is complete. Performing SQL server disaster recovery 37

38 Microsoft SQL Server Backup and Recovery Best practices Consideration Table 7 Table 7 on page 38 lists the best practices and recommendations to follow when using NMM to back up and recover SQL server. SQL server backup and recovery best practices and considerations Best practice 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 against split-mirror snapshot technology, when using EMC CLARiiON or EMC Symmetrix. NetWorker modules and the NMM client CLARiiON limits for the CX500 SQL instances in suspect mode Verify VSS SQL Writer service is running Ignore tempdb database Special character databases SQL server crash may occur when the SQL server executable or the supporting system components get corrupted. 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 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 are promoted to Full backups. If the number of snapshots exceeds the limit for number of snapshots supported per CLARiiON, a "VETO" failure occurs during snapshot creation. The CLARiiON limits for the CX500 are as follows: For a CX500, the limit is 150 snapshots or snapshot sessions system-wide. This includes reserved snapshots/sessions for SAN Copy TM. There is also a limit of 8 snapshots or snapshot sessions per LUN. Limits for CLARiiON systems can be found in the EMC SnapView Integration Module for SQL Server (SIMS) Administrator s Guide. If any of the databases belonging to a SQL instance are in suspect mode, and a backup of the SQL instance is attempted with the Microsoft MSDE Writer, the snapshot backup will fail. After installing SQL server, verify that the VSS SQL Writer service is running for the VSS SQL Writer snapshot to be successful. It must be enabled or set to automatic after installation. Microsoft indicates that tempdb is a database that is rebuilt when the server is rebooted, and that VSS Requestors can ignore this database. The database is not reported by the writer and is not backed up. Special character databases are not backed up and the best practice is to have the list of databases without special character tables and columns. 1. Restore the system components, which by default has the Windows boot volume and Windows system volume. 2. Reinstall the SQL server with its latest software updates and then recover the SQL databases by using APPLICATIONS:\SqlServerWriter. 38 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

39 2 Microsoft Active Directory Backup and Recovery This chapter includes the following topics: Overview Performing an Active Directory or ADAM full backup Performing Active Directory or ADAM granular backup Performing an all Active Directory data recovery Performing an Active Directory granular recovery Performing Active Directory disaster recovery Microsoft Active Directory Backup and Recovery 39

40 Microsoft Active Directory Backup and Recovery Overview This chapter provides the information required for backup and recovery of Active Directory by using NMM. Performing an Active Directory backup enables the recovery of the entire Active Directory database in the event of a catastrophic loss such as a hardware failure. Active Directory data that is protected for a disaster is recoverable on an all or nothing basis. You cannot choose individual objects for recovery, instead you must recover the entire Active Directory database in one recovery operation. Note: NMM does not support deduplication for the Active Directory. IMPORTANT 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 in this chapter also apply to AD LDS. Review the following sections before performing Active Directory backup and recovery: Types of supported backup and recovery on page 40 Specifying save sets for scheduled backups on page 41 Types of supported backup and recovery NMM supports the following types of backup for Active Directory: Full backup: Backs up the entire Active Directory database Utilizes VSS framework to create snapshot of Active Directory data Backup level Full only Performing an Active Directory or ADAM full backup on page 41 provides details. Granular backup: Traditional or non-vss backup of individual Active Directory objects and object attributes Backup levels Full and incremental Performing Active Directory or ADAM granular backup on page 42 provides details. NMM supports the following types of recovery for Active Directory: All Active Directory database recovery Authoritative or nonauthoritative recovery modes Performing an all Active Directory data recovery on page 50 provides details. 40 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

41 Microsoft Active Directory Backup and Recovery Granular recovery Recovery of individual Active Directory objects or attributes, including objects that are in the tombstone database. Granular recovery should only be performed as a supplement to the full Active Directory database backup. Performing an Active Directory granular recovery on page 51 provides details. Disaster recovery A disaster recovery plan requires regular full Active Directory database backups. Performing Active Directory disaster recovery on page 55 provides details. Specifying save sets for scheduled backups When specifying save sets for the scheduled backup, follow these guidelines: Active Directory is backed up by normal system save operations. It is backed up as part of system components, as part of standard Windows Server Backups. Note: Microsoft best practices recommends that a backup Active Directory server be set up so that it can be promoted to the primary Active Directory server in the event of a disaster. For an ADAM client resource, specify the save set as: APPLICATIONS:\ADAM <instance_name> Writer where <instance_name> is the name of the ADAM instance. Performing an Active Directory or ADAM full backup Use NMM to perform regular backups of volumes, system components, and application save sets. The following save sets should be backed up regularly: 1. Back up the following with the snapshot policy All. C:\ SYSTEM COMPONENTS:\ The backup of C:\ automatically includes the following: Windows Boot Volume Windows System Volume Application software Note: If the system has been set up with a separate file system for the Windows boot\system partition and separate file system for application installation, then along with C:\ drive, back up the file system that includes the Windows Boot Volume, Windows System Volume, and application software. 2. Back up the domain controller on the Active Directory machine. Performing an Active Directory or ADAM full backup 41

42 Microsoft Active Directory Backup and Recovery Performing Active Directory or ADAM granular backup A granular or traditional non-vss Active Directory backup enables you to recover individual objects and object attributes. A granular ADAM backup enables you to recover individual application partitions. A granular backup does not use snapshot technology. Instead, the backup is routed directly to a granular backup medium. IMPORTANT Take a full backup when the properties or main attributes of an object are changed, or when an security group is deleted and then recreated. Considerations for granular backup Consider the following general guidelines before performing a granular Active Directory backup: System-only attributes are not backed up with Active Directory objects. System-only attribute values should not be changed. Those attributes are restored through tombstone reanimation. Changing the system date and time to an older date in the domain controller is not recommended. Each item in Active Directory is marked by time. Active Directory uses time to resolve any data conflicts. Restore of a deleted object with the NMM client will fail if the date and time are changed after objects are backed up. If a change in the system date or time is necessary, immediately take a backup of the domain. The Group Policy object exists in two places: as an Active Directory object in the Group Policy Container and in the Windows registry. Many of the settings that can be edited from the Group Policy Management Console actually reside in the system registry and not in Active Directory. Therefore, if these values are changed after a backup, a recovery will not restore the attribute values and the system values will take precedence. A restored user account is automatically set to disabled and the pwdlastset attribute is not recovered for security. A new password must be set after a user account is restored. A change to a user object s memberof attribute is reflected for the target and not the user s properties. For example, if a user is added to the Guests group, the Guests group object is modified, not the user object. If an incremental backup is performed, the Guests object should be included in the backup and not the user object. The rootdse object is dynamic when created. ADAM lists the connection and the primary registered partition. When a bind is requested on the rootdse object, ADAM returns the value of the default Naming Context. On a domain controller, this is always the Domain Naming Context. Since the domain is visible in ADAM, do not backup the domain that uses port Use the standard LDAP port EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

43 Microsoft Active Directory Backup and Recovery Do not modify the msnpallowdialin attribute directly in Windows server 2003, SP1. Use the RAS administration function to modify the value. The Active Directory Users and Computers (ADUC) MMC snap-in uses the RAS API to modify this attribute and correctly modifies the userparameters attribute as well. If the RAS API is not used, the userparameters attribute is not modified with the msnpallowdialin attribute and the configuration will be incomplete. Many configuration settings are stored in Active Directory, but LDAP cannot always be used to write data directly. Also, some items stored in Active Directory are only copies. Use the appropriate interfaces or APIs to modify settings. Configuring Active Directory or ADAM granular backups IMPORTANT Do not configure a proxy client for granular ADAM or Active Directory backups. To configure an Active Directory or ADAM granular backup, perform the following tasks outlined in Table 8 on page 43. Table 8 Tasks for Active Directory or ADAM granular backup Backup task 1. Set up local Windows SYSTEM account as an ADAM administrator on page 44 Considerations The ADAM server, which is also a NetWorker client, relies on the NetWorker client s nsrexecd service to spawn the required binaries to perform a backup. The nsrexecd service and other binaries run under the Windows SYSTEM account. To ensure that these binaries can access ADAM data, the Windows SYSTEM account must be given access rights to each instance on the ADAM server. Note: This task is required only for granular ADAM backups. Skip this task for granular Active Directory backups. 2. Configure a pool for backup operations on page Configure a backup schedule on page Configure a backup group on page Configure a client resource on page 47 First create a backup pool to store the save sets that contain metadata and then configure the backup pool. 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. Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. A client resource specifies what to include in a backup of an NMM client. client resources are associated with other backup resources, such as groups. 6. Configure privileges on page 49 NMM client must be granted NetWorker administrator privileges to perform media database operations during a deletion. Performing Active Directory or ADAM granular backup 43

44 Microsoft Active Directory Backup and Recovery Set up local Windows SYSTEM account as an ADAM administrator IMPORTANT These steps are not required for Active Directory backup. To set up the Windows SYSTEM account with permissions on the local ADAM server: 1. Open the ADAM ADSI Edit utility. The ADAM ADSI Edit utility is available with ADAM SP1. 2. Connect to the ADAM instance. 3. In the Connection Settings dialog box, select Well-known naming context and select Configuration from the menu. 4. Type the port number (typically 50000) of the ADAM partition in the Port box and then click OK. 5. In the left pane, select CN=Roles. 6. In the right pane, right-click on CN=Administrators and then select Properties. 7. In the CN=Administrators Properties dialog box, select the Member Attribute from the attributes list, and then click Edit. 8. Click Add Windows Account and add the local ADAM server name. 9. Save your changes. 10. Repeat this procedure for each ADAM instance that you want to back up. Configure a pool for backup operations Configuring a backup pool is a four-part process: Configuring a device on page 44 Configuring a label template on page 45 Configuring a backup pool on page 45 Labeling the device on page 46 The EMC NetWorker Release 7.6 Service Pack 1 Administration Guide provides more detailed information about performing the steps included in this section. 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 data 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, click Devices on the taskbar. 2. In the expanded left pane, select Devices. 3. From the File menu, select New. 44 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

45 Microsoft Active Directory Backup and Recovery 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. For example, C:\tmp\d0 for a file type device. A tape device would have a format similar to \\.\Tape0. 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 and then 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 metadata. 5. In the Comment attribute, specify a comment for the label. 6. In the Fields attribute, specify a text name such as Metadata and on a separate line, specify a numeric range such as or a text range such as aa-zz. These attributes are used to incrementally identify each label. 7. Click OK. Configuring a backup pool Note: Use backup pools for granular Active Directory or ADAM backups that are different than the pools used for NMM client backups that include snapshots. In this way, you can sort granular Active Directory and ADAM backups from other backups. 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. Performing Active Directory or ADAM granular backup 45

46 Microsoft Active Directory Backup and Recovery 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. Perform either of the following steps; but not both: Click the Selection Criteria tab, and specify an 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. 10. In the Devices attribute, select each device that can accept backups for this pool. 11. Click OK. Labeling the device Before a device can be used for backup, it must be labeled. To label a device: 1. In the Administration page of the NetWorker Management Console, click Devices. 2. In the right pane, right-click the name of the device and select Label. 3. In the Pool attribute, select the backup pool that was created. 4. Select the Mount after Labeling attribute. 5. Click OK. Configure a backup schedule Table 9 on page 46 contains the considerations for configuring a backup schedule for an NMM client. 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 These backups are supported for all types of data. These are supported only for backup of volume directories or paths such as E:\ or E:\business_files\. Note: Level 1 to 9 backups are not supported for granular Active Directory and ADAM backups. Configure a backup group Use a backup group to assign the following attributes to a set of client resources: Backup start times Schedules Backup pools 46 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

47 Microsoft Active Directory Backup and Recovery Note: 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. 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. 6. For the Start Time attribute, enter the time when the first backup is to be created. 7. For the Autostart attribute, select Enabled. Note: Unlike most other NMM application backup client resources, snapshot policies are not applicable to granular Active Directory or ADAM backups. Do not specify or assign a snapshot policy or a snapshot pool to the backup group: Ensure that the Snapshot attribute is clear, so that there is no check mark beside it. Do not select a snapshot policy in the Snapshot Policy attribute. Do not select a pool in the Snapshot Pool attribute. 8. Click the Advanced tab. 9. Set the Client Retries attribute to 0 (zero). 10. Click OK to create the backup group. IMPORTANT Once you have started a backup of a save group, do not interrupt or halt the 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 backup is halted. Any attempt to stop a group in NetWorker Management Console will take a long time to complete. Configure a client resource IMPORTANT Do not use the same client resource for Active Directory or ADAM granular backups and other NMM client backups including Active Directory or ADAM backups for the purposes of disaster recovery. To create a client resource for granular Active Directory or ADAM backup: 1. In the Administration page of the NetWorker Management Console, click Configuration. 2. In the expanded left pane, select Clients. Performing Active Directory or ADAM granular backup 47

48 Microsoft Active Directory Backup and Recovery 3. From the File menu, select New. 4. In the Name attribute, type the fully qualified 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. Specify domain objects in the following format: DC=corp, DC=domain,DC=com For example: DC=corp, DC=xyz, DC=com where the backup saves the entire domain named corp.xyz.com from its root level. 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 Backup command attribute, type the appropriate command for Active Directory objects or ADAM objects: Active Directory objects: Type the following command in the Backup Command attribute: nsradsave.exe Active Directory domain objects and application partitions on the domain host cannot be backed up in the same client resource. Each type of data must be specified on a separate client resource. For example, to back up an Active Directory domain or part of a domain, type the following in one client resource: nsradsave.exe ADAM objects: To back up ADAM application partitions, type the following command in the Backup Command attribute, specifying the port number For example, type the following: nsradsave.exe -p EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

49 Microsoft Active Directory Backup and Recovery 14. Click the Globals (1 of 2) tab. 15. In the Aliases attribute, validate that the NETBIOS name for the client is present. This will be automatically populated by NetWorker when name resolution is configured. If the NETBIOS name is not present, add the NETBIOS name for the client. Note: 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. 16. Click the Globals (2 of 2) tab. 17. If the NMM client is part of a cluster: a. Type the names of the physical nodes of the cluster in the Remote Access attribute. b. Click OK.! IMPORTANT Do not check the deduplication backup option because deduplication backup with EMC Avamar is not supported for Active Directory granular. Configure privileges In addition to the permission set up in Set up local Windows SYSTEM account as an ADAM administrator on page 44 for performing granular ADAM backup, in both ADAM and Active Directory granular backup the NMM client must be granted NetWorker Administrator privileges to perform media database operations during a deletion. If you are setting up an NMM client in a cluster, grant NetWorker administrator privileges to each cluster node and virtual server. To add 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, 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. If the NMM client is installed in a cluster, grant NetWorker Administrator privileges to each cluster node and virtual server. 5. Click OK. Performing Active Directory or ADAM granular backup 49

50 Microsoft Active Directory Backup and Recovery Performing an all Active Directory data recovery The steps in this procedure assume that any damaged hardware has been replaced and that all software has been reinstalled. To ensure the successful recovery of the Active Directory server, complete the backup steps described in Performing an Active Directory or ADAM full backup on page 41. IMPORTANT If you have followed Microsoft best practices, you will have a backup Active Directory server that can be promoted to the primary Active Directory server in the event of a disaster. If you do not have a backup Active Directory server that can be promoted to the primary Active Directory server, complete the steps in this section to recover from a disaster of the Active Directory server. To recover Active Directory server data: 1. Before you can recover Active Directory server data, you must boot the NMM client in Directory Service Recovery mode: If you have not booted the NMM client in Directory Service Recovery mode, proceed to step 2. If you have already booted the NMM client in Directory Service mode, proceed to step 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. For Windows server 2003 this is boot.ini. For Windows server 2008 it is called the Boot Configuration Data (BCD) Store. 3. Select the Windows boot option for the domain controller. 4. Press F8 to display a list of special boot options. 5. Select Directory Service Restore Mode (Windows Domain Controllers only) from the list of special boot options. When you boot in this mode, Active Directory is taken offline. 6. Log in as administrator. Use the password that was specified when the domain controller was created. Windows starts in safe mode. 7. Open the NMM client software and select the NetWorker Server on which the NMM client software was configured for backup. 8. In the left pane, select Recover > System Recover Session. 9. From the navigation tree, open the SYSTEM COMPONENTS folder. By default, the objects displayed in the navigation tree are from the most recent backup. To recover from a previous backup: From the application toolbar, click the Browse calendar icon and select an earlier browse time. To view all versions of a backup object prior to the selected browse time, right-click an object in the navigation tree and select Versions. 50 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

51 Microsoft Active Directory Backup and Recovery 10. Select items to recover: If the Active Directory server is not in a clustered environment, select all of the items under the SYSTEM COMPONENTS folder. If the Active Directory server is part of a cluster environment: a. From the Options menu, select System Recover Session Options and then click the NetWorker tab. b. Clear the attribute titled Use Microsoft best practices for selecting the system state. Click Yes when asked to confirm your selection. c. Click OK to close the System Recover Session Options dialog box. d. Select all of the items under the SYSTEM COMPONENTS folder except for the Cluster Writer. 11. To determine whether any volumes need to be mounted, right-click the selected item and select Required Volumes. 12. From the System Recover Session toolbar, click Start Restore. 13. To perform an authoritative recovery of the Active Directory server, complete the procedure for authoritative recovery of NTDS or FRS data. The EMC NetWorker Module for Microsoft Applications, Release 2.3 Administration Guide provides more information about these types of recovery. 14. After the Active Directory recovery is complete, reboot the host to restart the Active Directory server. 15. If the Active Directory server is part of a cluster environment, select the Cluster Writer for recovery. 16. Recover any remaining volume or application data. Performing an Active Directory granular recovery You can individually select deleted Active Directory objects and their attributes for recovery. The Microsoft website provides more information about Active Directory objects and attributes. Due to Active Directory limitations, there are some restrictions on the recovery of objects and attributes. Recovery restrictions for Active Directory on page 51 provides more information about recovery restrictions. Recovery restrictions for Active Directory The following restrictions apply when recovering Active Directory objects and attributes: Note: After starting an Active Directory recovery, access the Monitor view to verify the status of the recovery. Tombstone lifetime restriction When an Active Directory object is deleted, it is sent to a special container, named Deleted Objects. This object is now invisible to normal directory operations, and is called tombstone. It is better to recover a tombstone object instead of re-creating it because data such as the security Performing an Active Directory granular recovery 51

52 Microsoft Active Directory Backup and Recovery identifier (SID) and the globally unique identifier (GUID) are stored with the tombstone object. This data is critical for additional data recoveries, such as assigned group permissions. For example, access control lists (ACLs) use the SID of a security identifier object to store its permissions. A re-created group would get a new SID and GUID so that permissions assigned to the old group would be lost. Similarly, the SID and GUID are both used to recover a user profile. A user's profile would become unusable if a user with the same name is re-created. This is because the new profile would be given a new SID and GUID. Objects in tombstone are deleted when they reach the tombstone lifetime age for the domain, which is, by default, 180 days. After an object is deleted from the tombstone, it cannot be recovered. This is an Active Directory restriction. The tombstone lifetime is a configurable attribute of a Windows domain. System-only attributes cannot be recovered Object attributes that are system-only can neither be backed up nor recovered. This is an Active Directory restriction. Table 10 on page 52 provides a sample list of system-only attributes that are not backed up. Table 10 System-only attributes that are not backed up badpwdcount lastlogon usnchanged badpasswordtime logoncount usncreated distinguishedname objectcategory useraccountcontrol dscorepropagationdata objectclass whenchanged instancetype objectguid whencreated lastlogoff samaccounttype Attributes that are retained for a deleted object Table 11 on page 52 provides a sample list of attributes that are retained for an Active Directory object when it is deleted and moved to the tombstone database. Table 11 Retained attributes after object is deleted attributeid msmqownerid subclassof attributesyntax name systemflags distinguishedname ncname trustattributes dnreferenceupdate objectclass trustdirection flatname objectguid trustpartner governsid objectsid trusttype grouptype omsyntax useraccountcontrol instancetype proxiedobjectname usnchanged IDAPDisplayName replpropertymetadata usncreated legacyexchangedn samaccountname whencreated ms-ds-creatorsid securityidentifier 52 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

53 Microsoft Active Directory Backup and Recovery These attributes are restored when deleted objects from the tombstone database are restored. Objects that do not retain all of their mandatory attributes would cause a constraint violation error during a restore attempt. For example, a published shared printer has mandatory attributes (printername, servername, shortservername, uncname, and versionnumber), which are not retained in the tombstone database. Note: To recover objects that typically have mandatory attributes deleted, set the search flags of the specific attributes to eight. When the object is deleted, the attributes with search flag set to eight are transferred to the tombstone database. The entire object can then be restored from tombstone with the NMM client. Object password attributes An object s password is not recovered. After recovering an object with a password attribute, the Windows administrator must reset the password. Moved or renamed objects If an object is moved to another location or renamed, but not deleted from Active Directory they cannot be restored even if they are successfully backed up. This is due to the objects not being stored in the deleted storage database (tombstone). Only objects in that database can be restored. However, the attributes for these objects can be restored from the Context menu of the Active Directory interface, which restores the objects with the specific attribute sets. Attributes with null values Attributes with null values are not backed up and therefore are not recovered. For example, if an attribute for a phone number was empty (null), then the null Phone Number attribute would not be backed up. This is an Active Directory restriction and is intended to prevent the unintentional overwriting of valid attribute values. For example, if a Phone Number attribute was null when a snapshot was taken but later a valid phone number was added, subsequent recovery operations would not overwrite the valid phone number with a null value. Schema objects Schema objects cannot be recovered and therefore are not backed up, and should never be deleted. Recovering an Active Directory object or object attribute To recover an Active Directory object or object attribute: 1. Start the NMM client program. 2. From the application toolbar, click the NetWorker Server icon to select the NetWorker server on which the NetWorker client was configured for backup. 3. In the left pane, select Recover > Active Directory Recover Session. 4. In the navigation tree, select the Active Directory objects to be recovered. By default, the objects displayed in the navigation tree are from the most recent backup: To search for an item, click the Search tab. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details about searching for a recovery item. Performing an Active Directory granular recovery 53

54 Microsoft Active Directory Backup and Recovery To recover objects from a previous backup: From the application toolbar, click the Browse calendar icon and select an earlier browse time. To view all versions of a backup object prior to the selected browse time, select an object in the navigation tree, right-click and select Versions. 5. To determine whether any volumes need to be mounted for a selected object, right-click an object and select Required Volumes. 6. Recover the entire object or selected object attributes: To recover the entire object: a. Select the object. b. From the Active Directory Recover Session toolbar, click Start Recover to begin the recovery operation. Note: An entire object can only be restore if it is deleted. The attributes are restored to an existing object. To recover just selected attributes of an object: a. Right-click an object and select Recover this Item. The Active Directory Recover Attributes dialog box appears. b. Select each attribute that is to be recovered. If all attributes or no attributes are selected, the entire object is recovered. c. Click OK. 7. Click Start Recovery. 8. From the left pane, select Monitor to view the progress of the recovery. Selecting Active Directory object attributes Use the Active Directory Recovery Attributes dialog box to select which attributes to recover for an Active Directory object. To select object attributes for recovery: 1. Select each attribute that is to be recovered. If all attributes are selected or no attributes are selected, the entire object is recovered. 2. Click OK. The Active Directory Recovery Attributes dialog box closes. 3. From the Active Directory Recover Session toolbar, click Start Recover. 54 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

55 Microsoft Active Directory Backup and Recovery Performing Active Directory disaster recovery A disaster recovery would require a complete system recovery in addition to an application data restore. The disaster recovery procedure for Active Directory is generally a system recovery followed by a standard Active Directory recovery. Performing a disaster recovery requires that proper measures were taken during backup of Active Directory data. The following sections provide information: The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides information about system component recovery. Performing an Active Directory or ADAM full backup on page 41 provides information for backing up data for disaster recovery. Performing an all Active Directory data recovery on page 50 and Performing an Active Directory granular recovery on page 51 provide recovery information. Performing Active Directory disaster recovery 55

56 Microsoft Active Directory Backup and Recovery 56 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

57 3 Microsoft Data Protection Manager Backup and Recovery This chapter includes the following topics: Overview Performing DPM server backups Performing a granular recovery of DPM objects Performing a granular directed recovery to a DPM-protected server Performing DPM writer disaster recovery Microsoft Data Protection Manager Backup and Recovery 57

58 Microsoft Data Protection Manager Backup and Recovery Overview Microsoft System Center DPM is Microsoft s solution for backing up and recovering Microsoft application and system data and files by using the VSS framework. EMC NetWorker VSS Client for Microsoft Windows (NMM) client supports Microsoft DPM 2007 that runs on x86 and x64 machines. The EMC Information Protection Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions supported by the NMM client. DPM stores and manages this backup information in its own database. DPM can provide backup and recovery for: Windows file services Exchange server SQL server SharePoint server Virtual server 2005 NMM does not support deduplication for DPM. Review the following sections before starting DPM backup and recovery: NMM and DPM scenario on page 58 Types of supported backup and recovery on page 59 Types of DPM data backed up by NMM on page 60 DPM backup writers on page 60 NMM commands required for DPM backup and recovery on page 61 NMM and DPM scenario Figure 5 on page 59 shows how NMM provides support for backup and recovery of DPM data. Note: DPM server must protect clients attached within the same domain as that of the DPM server. 58 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

59 Microsoft Data Protection Manager Backup and Recovery NetWorker Module for Microsoft Applications protects items within DPM Server 2007: DPM Configuration Database DPM Replicas DPM protects items within Microsoft Servers: Database files Storage groups Volumes Transaction logs NetWorker Server or 7.6.1: Provides services for NetWorker clients such as NMM LAN Microsoft Servers: Backup and Recovery provided by DPM Server 2007 DPM Server 2007: Backup and Recovery provided by NetWorker Module for Microsoft Applications (NMM) client GEN Figure 5 NMM protection of DPM Types of supported backup and recovery NMM supports the following types of backup for DPM: DPM configuration database backup Backup of the DPM configuration database. DPM replica backup Backup all or selected DPM replicas for DPM-protected servers. Backup level supported Full backup only. Performing DPM server backups on page 61 provides details. NMM supports the following types of recovery for DPM: Recovery of DPM server This includes recovery of the DPM configuration database, or recovery of missing replicas in their entirety to their original locations. Granular recovery to DPM-protected clients This allows you to browse DPM replicas and select individual folders or files for recovery. Performing a granular recovery of DPM objects on page 67 provides details. Disaster recovery Performing DPM writer disaster recovery on page 72 provides details. Overview 59

60 Microsoft Data Protection Manager Backup and Recovery Types of DPM data backed up by NMM NMM supports only full backups for DPM It backs up the following DPM data: DPM configuration database This is a SQL database. The DPM writer describes the location of the database, and NMM uses VSS SQL writers to protect it. NMM requires a local instance of SQL. It does not support remote instances of SQL. The instance used by DPM server must be on the same machine as the DPM server. DPM replicas These are data containers that DPM uses to store its save sets. NMM will protect these as file system shares. A DPM replica is not a VSS replica, and is not directly manipulated outside the DPM environment. IMPORTANT NMM 2.3 does not support: Transportable backup of DPM replicas. DPM replica is in a dynamic volume. Local nontransportable hardware-based snapshots of dynamic volumes on Windows server The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about dynamic volume and transportable support in NMM 2.3. DPM backup writers DPM server may be backed up by using either of the following writers: SQL writer or MSDE writer IMPORTANT Microsoft recommends that you use the MSDE writer with DPM, if it is available. Windows server 2008 does not include the MSDE writer. Detecting the enabled writer To detect which writer is enabled, run nsrsnap_vss_save -? in a command window on the DPM server: Enabling and disabling the MSDE writer To turn the MSDE writer on or off: Among the writers displayed, you should see either a list of MSDE writer components or a list of SQL writer components. On a Windows server 2003 machine, you can enable the MSDE writer. 1. Open Registry Editor. 2. Locate the registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Se ttings\msdeversionchecking 60 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

61 Microsoft Data Protection Manager Backup and Recovery 3. To enable the MSDE writer, set the value to To disable the MSDE writer, set the value to Exit Registry Editor. 6. Restart the VSS service. NMM commands required for DPM backup and recovery Table 12 on page 61 describes commands NMM uses to back up and recover DPM data. Table 12 NMM Data Protection Manager commands Command nsrsnap_vss_save nsrsnap_vss_recover dpmsync -restoredb -dbloc [path] \DBMDB2007.mdf dpmsync -sync dpmsync -reallocatereplica Description of command Initiates VSS-based backup. Initiates VSS-based recovery. Instructs DPM to use the database at the specified location. Instructs DPM to synchronize itself with the new environment. Instructs DPM server to verify its replicas and to create the appropriate number and size of partitions to receive the recovered replicas. Run on DPM server before performing DPM replica recover. Note: You cannot use this command for replicas that use Custom Volumes. You must manually create the necessary volumes before you can proceed with DPM replica recovery. The Microsoft DPM documentation provides more information about the use of Custom Volumes. nsr_dpm_retry_wait nsr_dpm_retry_maximum Specifies that if the DPM replica is unavailable for backup because it is in use, to wait for the specified time (in minutes) before re-starting the backup. The default value is 10. Specifies the total number of attempts (the first try plus retries) to start the backup. The default value is 3. Performing DPM server backups This section contains the following information: DPM application information variable settings on page 62 Displaying valid DPM data save sets on page 62 Specifying DPM save sets for application data on page 63 Configuring DPM backups on page 64 Performing DPM server backups 61

62 Microsoft Data Protection Manager Backup and Recovery DPM application information variable settings Table 13 on page 62 lists the variables that can be specified in the application information attribute of the client resource. Table 13 DPM application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value NSR_PS_SINGLE_SAVE_PER_SAVESET=value NSR_PS_FIRST_SAVESET_SAVE=value NSR_DPM_RETRY_WAIT=value NSR_DPM_RETRY_MAXIMUM=value Specifies the snapshot service provider name. Specifies to create a separate PowerSnap save set for each save set in the client entry. Specifies the save set that PowerSnap must operate upon first. This must be set to the DPM configuration database save set because Microsoft recommends that it be saved first. This attribute should not be used if the DPM configuration database is not one of the save sets or if the DPM configuration database is the only save set. This attribute should only be used if the DPM configuration database is one of the multiple save sets that is being backed up under a single NetWorker client resource. Specifies that if the DPM replica is unavailable for backup because it is in use, wait for the specified time (in minutes) before retrying to start the backup. The default setting is 10. Specifies the total number of times the first try plus retries to attempt to start the backup. vss This value is required. yes NSR_PS_SINGLE_SAVE_PER_SAVESET=yes Configuration database save set name For example: NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS: \Microsoft DPM\DPM Database A positive integer For example, to specify a wait time of two minutes: NSR_DPM_RETRY_WAIT=2 A positive integer For example, to specify of three attempts: nsr_dpm_retry_maximum=3 Displaying valid DPM data save sets To display a list of the DPM save sets that are available for backup: 1. Open a command prompt on the application server. 2. If the application server is not on a virtual host, list the valid application data save set names. Type: nsrsnap_vss_save -? 3. Press Enter. Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a client resource. Note: Ensure to type each save set entry on a separate line. Ensure that you remove the inverted commas when you copy the saveset name from the output. 62 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

63 Microsoft Data Protection Manager Backup and Recovery Example of output: The application data save sets that are available for backup are listed in a format similar to the following: APPLICATIONS:\Microsoft DPM\DPM database APPLICATIONS:\Microsoft DPM\Volume C: on server mars.saturn.company.com Specifying DPM save sets for application data Table 14 on page 63 lists the DPM save set syntax to specify for supported types of DPM data. Specify DPM data save sets in the Save Set attribute of a client resource. Some special characters in a DPM protection group name must be replaced with URL-encoded values. URL encoding for DPM save sets on page 63 provides more information about URL encoding. Table 14 DPM server 2007 save set syntax Type of backup data Description Save set syntax Configuration database Protection group replica set, of a non-vss datasource Protection group replica set There will always be exactly one DPM configuration database. There are usually multiple protection group replica sets. For example, a DPM replica resulting from DPM protection of a system state on a server named Mars.DPM.Server. There are usually multiple protection group replica sets. For example, a DPM replica resulting from DPM protection of a SQL database Luna\FAcmeBank on a server named Pluto SQL Server. APPLICATIONS:\Microsoft DPM\DPM database APPLICATIONS:\Microsoft DPM\Non VSS Datasource Writer component Computer%2FSystemState on server Mars DPM Server APPLICATIONS:\Microsoft DPM\SqlServerWriter component Luna%2FAcmeBank on server Pluto SQL Server. URL encoding for DPM 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 when naming DPM components: The forward slash (/) in the component name Computer/SystemState is considered a special character: APPLICATIONS:\Microsoft DPM\Non VSS Datasource Writer component Computer/SystemState on server Mars DPM Server Replace it with its URL-encoded value, %2F: APPLICATIONS:\Microsoft DPM\Non VSS Datasource Writer component Computer%2FSystemState on server Mars DPM Server Performing DPM server backups 63

64 Microsoft Data Protection Manager Backup and Recovery Table 15 on page 64 lists the most commonly used special characters and their URL values. Table 15 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 Configuring DPM backups NMM DPM backup provides: Point-in-time snapshots, which include exact copies of files and open files. Full backup of DPM databases, logs, and protection groups, as well as administrator-selected protection groups. DPM requires a snapshot policy that retains snapshots. In the best practice section, mention that customers should only retain one snapshot and rollover all snapshots. To perform a DPM backup, complete the tasks outlined in Table 16 on page 64. IMPORTANT The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details for the first four tasks in Table 16 on page 64. Table 16 Tasks for scheduling a backup Backup task 1. Configure a backup pool for snapshot operations Consideration 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. 2. Configure snapshot policies DPM requires a snapshot policy that retains snapshots. The backup snapshot policy must be set to All. Backup fails, if any other value is used. 64 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

65 Microsoft Data Protection Manager Backup and Recovery Table 16 Tasks for scheduling a backup (continued) Backup task Consideration 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. Incremental backups include only the data that has changed since the last backup. 4. Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. 5. Configuring a DPM client resource on page 65 This task is specific to configuring a DPM client resource. Configuring a DPM 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 can create multiple client resources for the same NMM host. In this way, you can apply different backup attributes to different types of information on the same host. When configuring a DPM client resource, it is best practice to: 1. Create a DPM client resource for the backup of the DPM configuration database and the system database. 2. Run the database backup before replica backups. 3. For each of the DPM-protected application server replicas, create separate instances. 4. If creating a separate client resource, also create a separate group. Note: This version of NMM requires a local instance of SQL. It does not support remote instances of SQL. The instance used by a DPM server must be on the same machine as the DPM server. To create a DPM 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. Performing DPM server backups 65

66 Microsoft Data Protection Manager Backup and Recovery 9. In the Save Set attribute, specify the components to be backed up: Place multiple entries on separate lines. To back up all DPM server data, specify the save set name of every database and replica. For example: APPLICATIONS:\Microsoft DPM\DPM database. APPLICATIONS:\Microsoft DPM\Volume H: on server babaco.mars.com APPLICATIONS:\Microsoft DPM\Volume I: on server babaco.mars.com Displaying valid DPM data save sets on page 62 describes how to find the save sets available on the DPM server. Specifying DPM save sets for application data on page 63 describes the DPM server save set syntax. 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 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 Backup command attribute, type the backup command: nsrsnap_vss_save.exe 14. For Application information attribute, perform either of the following: To back up the DPM database and some or all of the replicas through a single client resource, type the following variables and values, each on a separate line: NSR_PS_SINGLE_SAVE_PER_SAVESET=yes NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS:\Microsoft DPM\DPM database. NSR_SNAP_TYPE=vss Or To back up only the DPM replicas through a single client resource, type the following variables and values, each on a separate line: NSR_SNAP_TYPE=vss NSR_PS_SINGLE_SAVE_PER_SAVESET=yes NSR_DPM_RETRY_WAIT=5 NSR_DPM_RETRY_MAXIMUM=3 Note: The NSR_DPM_RETRY_WAIT and the NSR_DPM_RETRY_MAXIMUM variables do not need to be specified if the default values are acceptable. The default is 10 minutes between attempts and three total attempts. DPM replicas are rolled over one at a time. For example, if there are 10 DPM replica savesets listed in the client resource, NMM creates 10 snapshots, one for each replica saveset, one at a time, and then rolls over the 10 snapshots, one for each replica saveset, one at a time. Because NMM cannot run multiple groups in parallel, DPM backups will take longer than other application backups. DPM application information variable settings on page 62 provides information about these variables and their values. 66 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

67 Microsoft Data Protection Manager Backup and Recovery! IMPORTANT For Microsoft System Center Data Protection Manager 2007, do not check the deduplication backup option because deduplication backup with Avamar is not supported. 15. Click the Globals (1 of 2) tab. 16. In the Aliases attribute, type the NETBIOS name for the client. Note: 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. 17. Click OK. Performing a granular recovery of DPM objects When NMM backs up a DPM server, all of the DPM-protected server replicas that are backed up are indexed to allow granular recovery of individual files in the replica. This granular recovery of DPM replica files can be completed back to the DPM server which is being protected, or to the DPM-protected server. You can browse DPM replicas and select individual folders or files for recovery. In DPM granular recovery, the DPM configuration database cannot be selected. However, NMM directed recovery is available. Recovering a folder or file from a DPM replica To recover a folder or file from a DPM replica: 1. Start the NMM client program. 2. From the application toolbar, click the NetWorker Server icon to select the NetWorker server on which the NetWorker client was configured for backup. 3. Right-click the NetWorker server in the navigation tree. When running NMM recovery on a DPM server, the default recovery mode is Disaster Recovery. When running on a non-dpm server, the default recovery method is Granular, and the Disaster Recovery mode is unavailable. Figure 6 on page 67 displays the DPM recovery modes available. Figure 6 DPM recovery modes Performing a granular recovery of DPM objects 67

68 Microsoft Data Protection Manager Backup and Recovery 4. In the left pane, select Recover. Figure 7 on page 68 displays the Recover submenu. Figure 7 Recover submenu for DPM recovery 5. Select DPM Recover Session. 6. Select Granular. 7. In the navigation tree, select the DPM files or folders to be recovered. By default, the objects displayed in the navigation tree are from the most recent backup. Figure 8 on page 68 is an example of a DPM server tree expanded to the file level. Figure 8 DPM granular recovery available to file level To recover objects from a previous backup: From the application toolbar, click the Browse calendar icon and select an earlier browse time. To view all versions of a backup object prior to the selected browse time, select an object in the navigation tree, right-click and select Versions. 8. Click Start Recover to begin the recovery operation. Figure 9 on page 68 displays the options available for DPM granular recovery. Figure 9 DPM granular recovery options 68 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

69 Microsoft Data Protection Manager Backup and Recovery 9. In the Recovery path box, specify the folder where the recovered items are to be placed. 10. Select Display these options when initiating a Recovery to show this dialog box when Start Recovery is selected. If this checkbox is cleared, options must be through the Recover Options button on the main NMM screen. 11. Click OK. 12. From the left pane, select Monitor to view the progress of the recovery. Reviewing settings before starting recovery The DPM Recovery Options Summary window lists the DPM recovery and NetWorker recover options. To review the settings before starting the recovery: 1. To change the NetWorker and DPM recover options, click Recover Options. You can also access the settings from the DPM Recover Session view. Click Recover Options. 2. The NetWorker Recover Options settings are specified on the General, NetWorker, Security, and DPM tabs. 3. After specifying the options, click Start Recover to validate the options. If all option settings are valid, the dialog box closes and recovery starts. Performing a granular directed recovery to a DPM-protected server For directed recovery to a DPM-protected server, NMM is installed on the DPM server for replica backup and on the DPM-protected server for directed recovery of individual folders or files. This allows you to run the recovery of files in a DPM-protected server replica, from the DPM server, and direct the recovery to the DPM-protected server computer. In the basic NMM backup and recovery process, the backup flows in the following direction: 1. The NMM client is installed on the computer that will be backed up. 2. That NMM client is configured to work with a specific NetWorker server on another computer. 3. Backups are configured on and performed by the NetWorker server. 4. Recovery is performed through the NMM client UI on the NMM client computer, and recovered to the same NMM client computer. A more typical use for DPM backup would be a directed granular recovery. In the NetWorker backup of DPM, the NMM software is installed on the DPM server to protect: The DPM server The replicas of the DPM-protected servers. Performing a granular directed recovery to a DPM-protected server 69

70 Microsoft Data Protection Manager Backup and Recovery DPM directed granular recovery scenario The following scenario describes how DPM directed granular recovery would work with a hypothetical FileServer1 as shown in Figure 10 on page 70. NetWorker Server: Provides backup services for NetWorker clients such as NMM LAN DPM-protected servers: Microsoft Applications SharePointServer3 SQLServer4 FileServer1 ExchangeServer2 Directed Recovery: Granular file recoveries to DPM-protected servers, directly from NetWorker Server, through NMM client UI on the DPM-protected server. DPM Server 2007: NMM client provides backup of DPM Server and DPM-protected server replicas. GEN Figure 10 Directed recovery of FileServer1 In this scenario, the FileServer1data was backed up through the NMM client on the DPM server, as part of the backup of DPM replicas. In the directed recovery, an NMM client installed on FileServer1 performs the recovery, instead of the NMM client on the DPM server: 1. The DPM server protects a Windows server client, FileServer1. 2. The NMM client on the DPM server backs up the DPM server, including the Protected-Client Replicas for the DPM server, such as FileServer1. 3. The administrator receives a request to recover a file, LostFile, from FileServer1. 4. The administrator checks DPM to see if DPM has the recoverable data. DPM no longer has the file that needs to be recovered. But because NMM backs up the file server replica as part of the DPM backup, the file should exist in a previous NMM backup of DPM. 5. The NMM client is installed on FileServer1. 6. The NMM client on FileServer1 is configured for directed recovery from the DPM server: Though the file the administrator wants to recover is from FileServer1, and it is being recovered to FileServer1, the backup was performed through a remote client on the DPM server. The administrator must make the NMM client on the DPM server available for recovery through the NMM client on FileServer1. 7. In the NMM client on FileServer1 the administrator adds the DPM server as an available client. 70 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

71 Microsoft Data Protection Manager Backup and Recovery 8. Once DPM server is an available client, the administrator can: a. Select items for recovery from the remote client, and the DPM server. b. Recover the items to the local client, FileServer1. Performing a directed granular recovery To perform a directed granular recovery of a DPM-protected client: Note: The backup must be a conventional backup, or a rolled over snapshot type backup. 1. Install NMM on the DPM-protected client, if it is not already installed. The NMM client on the DPM server, and the NMM client on the DPM-protected client must be on the same NetWorker server. 2. Open the NMM client on the DPM-protected client. 3. On the Options menu, click Configure Options. 4. Click the Refresh button, which is to the right of the client name. 5. Click the client that you want to add in the Client name menu, and then click Add. Add or remove clients as needed. 6. Click OK. 7. Click the Client menu, and select the DPM server NMM client that created the backup as the current local client. 8. If the Snapshot Management or Monitor is the active navigation bar item, and you are prompted with the Navigate Away dialog box, click Yes. 9. On the System Recover Sessions bar, select Recover Options. The NetWorker System Recover Session Options dialog box appears. 10. On the NetWorker tab, specify the destination for the recovery in the Relocate Recovered Data box, and then click OK. 11. In the left pane, select Recover: a. Select DPM Recover Session. b. Select Granular. 12. In the navigation tree, select the DPM files or folders to be recovered. By default, the objects displayed in the navigation tree are from the most recent backup. To recover objects from a previous backup: From the application toolbar, click the Browse calendar icon and select an earlier browse time. To view all versions of a backup object prior to the selected browse time, select an object in the navigation tree, right-click and select Versions. 13. Click Start Recover to begin the recovery operation. 14. In the Recovery path box, specify the folder where the recovered items are to be placed. Performing a granular directed recovery to a DPM-protected server 71

72 Microsoft Data Protection Manager Backup and Recovery 15. Select Display these options when initiating a Recovery to show this dialog box when Start Recovery is selected. If this checkbox is cleared, options must be through the Recover Options button on the main NMM screen. 16. Click OK. 17. From the left pane, select Monitor to view the progress of the recovery. Performing DPM writer disaster recovery 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. or The SYSTEM COMPONENTS:\ save set along with the system volume, for example, C:\. In DPM writer disaster recovery, NMM allows the DPM database and replicas to be selectable in the file view pane of NMM. This results in selecting all missing replicas, because replicas are not selectable individually. You can browse DPM replicas and select individual folders or files for recovery. Disaster recovery mode is not available when doing a directed recovery to a NetWorker client other than the DPM server which was originally backed up. When a remote client is selected, this mode is displayed as unavailable on the contextual menu. Figure 11 on page 72 displays the DPM database and replicas in the file view pane. Figure 11 DPM database and replicas available as selectable items To recover a folder or file from a DPM replica: 1. Start the NMM client program. 2. From the application toolbar, click the NetWorker Server icon to select the NetWorker server on which the NetWorker client was configured for backup. 3. Right-click the NetWorker server in the navigation pane: When running NMM recovery on a DPM server, the default recovery mode is Disaster Recovery. When running on a non-dpm server, the default recovery method is Granular, and the Disaster Recovery mode is unavailable. 4. In the left pane, select Recover, and then select DPM Recover Session. 72 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

73 Microsoft Data Protection Manager Backup and Recovery 5. In the navigation tree, select the DPM replicas or databases to be recovered. By default, the objects displayed in the navigation tree are from the most recent backup. To recover objects from a previous backup: From the application toolbar, click the Browse calendar icon and select an earlier browse time. To view all versions of a backup object prior to the selected browse time, select an object in the navigation tree, right-click and select Versions. 6. Select Disaster. 7. Click Start Recover to begin the recovery operation. Figure 12 on page 73 displays the options available for DPM disaster recovery. Figure 12 DPM disaster recovery options 8. In the Recovery path box, specify the folder where the recovered databases are to be placed. 9. Select Run DPM synchronization utilities for NMM to automatically run the DPM sync commands after recovery. 10. Select Allocate non-custom volumes for replicas to specify for recovery to run the dpmsync.exe to allocate disk volumes for any missing replicas prior to replica recovery. Note: This option does not apply to replicas that were created by using custom volumes. Custom DPM volumes must be created manually. The Microsoft DPM documentation provides more information regarding custom volumes. 11. Select Initiate consistency checks on recovered replicas to specify for recovery to initiate consistency checks on replicas following their recovery. 12. Select Display these options when initiating a Recovery to show this dialog box when Start Recovery is selected. If this checkbox is cleared, options must be through the Recover Options button on the main NMM screen. 13. Click OK. 14. From the left pane, select Monitor to view the progress of the recovery. Performing DPM writer disaster recovery 73

74 Microsoft Data Protection Manager Backup and Recovery 74 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

75 4 Microsoft Hyper-V Backup and Recovery This chapter includes the following topics: Overview Performing Hyper-V backups Performing Hyper-V recovery Selecting the destination of Hyper-V recovery Performing Hyper-V parent partition disaster recovery Best practices Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 failover cluster Microsoft Hyper-V Backup and Recovery 75

76 Microsoft Hyper-V Backup and Recovery Overview EMC NetWorker Module for Microsoft Applications (NMM) provides full backup and recovery of: Windows server 2008 with Hyper-V Windows server 2008 R2 with Hyper-V Windows server 2008, server Core Installation with Hyper-V Hyper-V is a Windows server 2008 and 2008 R2 role that provides hypervisor-based server virtualization. NMM utilizes the Hyper-V VSS writer to back up and recover the following: Hyper-V Initial Store configuration file Each virtual machine or child partition NMM does not support: Windows 2008 R2 Clustered Shared Volumes Backup of Volumes with no file system access path for Hyper-V Cluster configurations that use this configuration The following sections provide information that must be reviewed before starting Hyper-V backup and recovery: Operating system versions supported by NMM client on page 76 Integration Components version on page 77 Hyper-V parent partitions, child partitions, and applications within child partitions on page 77 Types of supported backup and recovery on page 78 Hyper-V configuration on page 78 Hyper-V storage configurations supported by NMM on page 79 Hyper-V configuration requirements for backing up a child partition that contains multiple volumes on page 82 Components used by NMM for Hyper-V backup and recovery on page 82 Operating system versions supported by NMM client The NMM client supports Hyper-V parent partitions that runs Windows server 2008 and Windows server 2008 R2 installations on 64-bit, virtualization aware, CPUs: For parent partitions, NMM also supports Windows server 2008 and Windows server 2008 R2 with the Server Core installation. When NMM is running in the Hyper-V parent partition, NMM can back up child partitions that are running the following guest operating systems: Windows server 2008 (x86 and x64) Windows server 2008 R2 (x64) Windows server 2003 R2 (x86 and x64) SP2 Windows server 2003 (x86 and x64) SP2 76 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

77 Microsoft Hyper-V Backup and Recovery Windows Vista (x86 and x64) SP1 Windows XP (x86) SP3 SUSE Linux Enterprise server 10 with SP1 x86 Edition The NMM client is also supported in Hyper-V child partitions (guests). NMM supports the same Windows server operating systems and applications that are supported on physical servers. Integration Components version Ensure that the version of Integration Components running inside the child partition is the same as the version of Hyper-V on the host. For Hyper-V RTM, it is To confirm this, in the Device Manager inside the guest child partition: 1. Under System Devices in Device Manager: a. Right-click the entry Hyper-V Volume Shadow Copy. b. Select Properties. 2. Check the version under the Driver tab. If the version does not match, insert the integration services disk by choosing the option under the Action menu in the child partition console. 3. Install the integration components and reboot the child partition. Hyper-V parent partitions, child partitions, and applications within child partitions Hyper-V requires a parent partition that is running Windows server 2008 and Windows server 2008 R2 to host the child partitions. Each child partition is usually a server operating system that runs applications, such as: Exchange server SharePoint server SQL server Data Protection Manager Hyper-V runs as a role in Windows server 2008 and Windows server 2008 R2. NMM uses the Microsoft Hyper-V VSS writer on the host to back up and recover Hyper-V through APPLICATION save sets. The Hyper-V writer backs up and recovers Hyper-V configuration and child partition files. When the integration components are installed on a virtual machine, and an application with a VSS Writer, such as Exchange or SQL, is also running on that virtual machine, the Hyper-V backup of that virtual machine takes a copy-type backup of the application data. You must configure in-guest backups for the applications, Exchange and SQL, so that the logs are truncated. Overview 77

78 Microsoft Hyper-V Backup and Recovery Types of supported backup and recovery NMM supports the following types of backup for Hyper-V: Disaster recovery backup of parent partition Does not include child partitions and Initial Store. Full backup of Hyper-V Writer Includes all child partitions and Initial Store. Granular backup of Hyper-V Writer Can back up individual child partitions and Initial Store. Deduplication backup Performing Hyper-V backups on page 82 provides details. NMM supports the following types of recovery for Hyper-V: Disaster recovery of Hyper-V server and role Operational recovery of individual child partitions and the Initial Store Performing Hyper-V recovery on page 88 provides details. Hyper-V configuration Figure 13 on page 78 illustrates a physical server running Windows server 2008 or Windows server 2008 R2. The Hyper-V role has been enabled on the server, and four child partitions have been created, each running a separate operating system and different Microsoft applications. Physical server with Windows Server 2008 host operating system and Hyper-V role Hyper-V virtual machines with child partition operating systems and applications Virtual Machine VS-1 Windows Server 2008 x64 Microsoft Exchange Server 2007 Configure Client resources within each child partitions to back up applications, volumes, and system components on the child partition Virtual Machine VS-2 Windows Server 2003 Microsoft Office SharePoint Server 2003 Virtual Machine VS-3 Windows Server 2003 Microsoft Data Protection Manager Virtual Machine VS-4 Windows Server 2003 Microsoft SQL Server Hyper-V configuration file Configure Client resources on parent partition to back up parent partition volumes and system components Configure Client resources on parent partition to back up Hyper-V child partitions and Hyper-V configuration file GEN Figure 13 Windows server 2008 or Windows server 2008 R2 host with Hyper-V child partitions 78 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

79 Microsoft Hyper-V Backup and Recovery For complete data protection, configure NetWorker client resources for each of the following: The Hyper-V server, or parent partition: system components, volumes, and applications Hyper-V child partitions and configuration information on the Hyper-V server The applications within each child partition Figure 14 on page 79 describes what the NMM client backs up in Hyper-V, by using the Microsoft Hyper-V VSS writer and NMM save sets. APPLICATIONS:\Microsoft Hyper-V Save set backs up Hyper-V components, which includes each virtual machine and the Hyper-V configuration file Parent Partition: Windows Server 2008 OS with Hyper-V Role APPLICATIONS:\Microsoft Hyper-V\VS-1 Save set to back up virtual machine VS-1 VS-1 Virtual Machine Child Partition APPLICATIONS:\Microsoft Hyper-V\VS-2 Save set to back up virtual machine VS-2 VS-2 Virtual Machine Child Partition APPLICATIONS:\Microsoft Hyper-V\Initial Store Save set to back up configuration file Initial Store Hyper-V Configuration File GEN Figure 14 NMM backup of Hyper-V components Hyper-V storage configurations supported by NMM There are a wide variety of storage configurations available for Hyper-V child partitions, such as passthrough disks, direct-attached storage (DAS), storage area networks (SANs), and file servers. The following documentation provides more details: The Microsoft website provides more details and the most up-to-date information about storage hardware supported by Hyper-V. The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about what software and hardware providers are supported for Hyper-V backup and recovery in NMM. Figure 15 on page 80 illustrates Hyper-V storage options. Overview 79

80 Microsoft Hyper-V Backup and Recovery Hyper-V Server DAS Parent Partition Child Partition Disk1-> X: X:\V1\V1.VHD -> VHD1 VHD1 -> C: Configuration 1 Disk 2 passthrough Disk 2 -> D: Configuration 2 SAN FC or iscsi LUN1 LUN 1 -> Y: Y:\V2\V2.VHD -> VHD2 VHD2 -> E: Configuration 3 LUN2 FC or iscsi LUN 2 passthrough LUN2 -> F: Configuration 4 LUN3 iscsi LUN 3 -> G: Configuration 5 S: SHARE1 File Server CIFS/SMB/ SMBv2 \\FS\SHARE1 \\FS\SHARE1\V3\V3.VHD -> VHD3 VHD3 -> H: Configuration 6 GEN Figure 15 Hyper-V storage options Table 17 on page 80 lists the Hyper-V child partition configurations. Table 17 Hyper-V child partition configurations Configuration Type 1 VHD1 on DAS 2 DAS passthrough 3 VHD2 on LUN 4 LUN passthrough 5 iscsi target attached within child partition 6 VHD3 on file server NMM supports Hyper-V snapshots of the child partitions and the parent partition with the Microsoft Software VSS provider or VSS hardware providers, depending on the hardware storage type and partition type. 80 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

81 Microsoft Hyper-V Backup and Recovery The following list describes how these configuration types are supported in NMM: Snapshot support Snapshot support is provided for both child and parent partitions: Child partition NMM is running within the child partition to perform the backup. The following storage configurations are supported for this environment: If using the Microsoft Software VSS provider, all configurations listed in Table 17 on page 80 are supported. If using a VSS hardware provider, configuration 5 (LUN exposed directly to child partition) is supported. Currently, this support includes the EMC VSS hardware provider with EMC CLARiiON storage. The EMC Information Protection Software Compatibility Guide provides the latest support information. Parent partition NMM is run in the parent to perform the backup. The following storage configurations are supported for this environment: If using the Microsoft Software VSS provider, configuration 1 (VHD1) and configuration 3 (VHD2) are supported. If using a VSS hardware provider, configuration 3 (VHD2) is supported. Currently, this support includes the EMC VSS hardware provider with EMC CLARiiON storage. The EMC Information Protection Software Compatibility Guide provides the latest support information. Note: When performing child partition backups while executing on the parent partition, the Microsoft Hyper-V Writer does not include the passthrough or child-attached iscsi drives for a child partition. Configurations such as 2, 4, and 5 are not supported by the Hyper-V Writer. Configuration 6 is not supported because the VSS framework does not support network shares. Cluster support In addition to the supported configurations listed for snapshots, parent and child cluster scenarios support the following storage configurations: Child partition clustering NMM is running within the child partition to perform the backup: For drives configured as failover resources, configuration 5 (LUN exposed directly to child partition) is supported as this is the only configuration Microsoft currently supports for Windows server 2008 Failover Clustering. For drives configured for operating system or local drives for the cluster nodes, the child partition support listed under Snapshot support applies. Parent partition clustering NMM is run in the parent to perform the backup. All configurations are supported. Overview 81

82 Microsoft Hyper-V Backup and Recovery Hyper-V configuration requirements for backing up a child partition that contains multiple volumes When there are multiple virtual hard disks in the guest, backup of the associated child partition from the parent partition may fail because of a Microsoft limitation. When there are multiple volumes on the guest, VSS determines the shadowstorage area for the snapshots based on which volume has more space. This can lead to a condition where volume C s snapshot and volume D s snapshot both reside on volume D since volume D has more space. During the snapshot revert stage in PostSnapshot, volume C s snapshot may be lost if volume D s snapshot is reverted first. To prepare a multiple volume guest for backup: 1. Use the vssadmin command to force the shadowstorage of each volume to be on the same volume: Note: These commands must be run inside each guest, not the parent physical Hyper-V server. vssadmin Add ShadowStorage /For=C: /On=C: vssadmin Add ShadowStorage /For=D: /On=D: 2. Repeat as needed for each volume in the child partition. Components used by NMM for Hyper-V backup and recovery Table 18 on page 82 describes the components that NMM uses to back up and recover Hyper-V data. Table 18 NMM Hyper-V components Item Application writer nsrsnap_vss_save nsrsnap_vss_recover Description There is one VSS writer for Hyper-V it is named Microsoft Hyper-V VSS writer NMM command that initiates the VSS-based backup. NMM command that initiates the VSS-based recovery. Performing Hyper-V backups The following sections describe how to configure and run a Hyper-V backup. Hyper-V application information variable settings on page 83 Specifying Hyper-V save sets for application data on page 83 Displaying valid Hyper-V save sets on page 83 NMM support for proxy backup of Hyper-V on page 84 Preparing a child partition for backup on page 84 Configuring Hyper-V backups on page 85 Note: In NMM 2.3, backups of Cluster Shared Volumes in Windows 2008 R2 are skipped at both file system level or HyperV writer level. 82 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

83 Microsoft Hyper-V Backup and Recovery Hyper-V application information variable settings Table 19 on page 83 lists the variables that can be specified in the Application information attribute of the client resource. Table 19 Hyper-V application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value Specifies the snapshot service provider name. vss This value is required. Specifying Hyper-V save sets for application data Table 20 on page 83 lists the Hyper-V save set syntax to specify for supported types of Hyper-V backup. Specify Hyper-V data save sets in the Save Set attribute of a client resource. Table 20 Hyper-V save set syntax Type of backup data Hyper-V Manager The entire Hyper-V configuration: the Hyper-V configuration file and each child partition. Save set syntax APPLICATIONS:\Microsoft Hyper-V Note: The Hyper-V writer does not support offline backup of the configuration file. The APPLICATIONS:\Microsoft Hyper-V save set cannot be used in a proxy backup group. Hyper-V configuration file, also known as Initial Store. There is one configuration file in the Hyper-V Manager installation, listing the Hyper-V settings for the host operating system and the guest operating systems. APPLICATIONS:\Microsoft Hyper-V\Initial Store Note: The Hyper-V writer does not support offline backup of the configuration file. The APPLICATIONS:\Microsoft Hyper-V\Initial Store save set cannot be used in a proxy backup group. Hyper-V child partition. There are usually multiple child partitions on the host operating system. APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name Child pertains or virtual machines can be included in a proxy backup group. Displaying valid Hyper-V save sets To display a list of the Hyper-V save sets that are available for backup: 1. Open a command prompt on the Hyper-V server. 2. List the valid application data save set names: If the Hyper-V server is not on a cluster virtual host, type: nsrsnap_vss_save -? If the Hyper-V server is on a cluster virtual host, type: nsrsnap_vss_save -? -c cluster_virtual_server_name Note: If the application server is on a cluster virtual host, run the command from the physical node that is currently hosting the application server. Performing Hyper-V backups 83

84 Microsoft Hyper-V Backup and Recovery 3. Press Enter: 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. Note: Ensure that you remove the inverted commas when you copy the save set name from the output. The following example shows the application data save sets that are available on a Hyper-V system with two child partitions, child_partition_name_1 and child_partition_name_2: APPLICATIONS:\Microsoft Hyper-V APPLICATIONS:\Microsoft Hyper-V\Initial Store APPLICATIONS:\Microsoft Hyper-V\child_partition_name_1 APPLICATIONS:\Microsoft Hyper-V\child_partition_name_2 The list of Microsoft Hyper-V save sets will include the top-level entry for Microsoft Hyper-V, the configuration file, and all the child partitions if any exist. NMM support for proxy backup of Hyper-V NMM does not support SAN boot configurations, where a hardware snapshot of the system drive is performed. The Microsoft Hyper-V writer requires that the configuration component Initial Store always reside on the system partition. This path cannot be changed. NMM supports proxy backup for child partitions. Child partition-only save sets can be specified in a proxy backup group: APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_1 APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_2 The Microsoft Hyper-V save set and configuration file (Initial Store) save set cannot be specified in a proxy backup group: APPLICATIONS:\Microsoft Hyper-V APPLICATIONS:\Microsoft Hyper-V\Initial Store Preparing a child partition for backup Before NMM can create a backup of a Hyper-V child partition, Integration Services must be installed on the child partition. These services provide integration between the physical server and the child partitions, such as time synchronization, guest operating system shutdown messaging, and backup support: Integration Services can only be installed after the guest operating system has been installed on the child partition. To install Integration Services, on the child partition guest system click the Action menu, click Insert Integration Services Setup Disk, and then click the.exe to run setup. When Windows server 2008 or Windows server 2008 R2 is installed as the operating system on a guest system, Integration Services are installed by default. 84 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

85 Microsoft Hyper-V Backup and Recovery Configuring Hyper-V backups Table 21 on page 85 describes the backup tasks for the Hyper-V parent and child partitions. Table 21 Backup tasks for Hyper-V (page 1 of 2) Hyper-V parent partition On the parent partition Windows volumes: Volume data, such as a drive letter, for example, D:\. A file system path, such as D:\ data. Windows system components, such as: The registration database Windows Cluster and so on Other Window system components The EMC NetWorker Module of Microsoft Applications Release 2.3 Administration Guide provides the list. On the parent partition The Hyper-V role can coexist with other applications, such as: SQL server SharePoint server Exchange server System Center DPM Windows server Cluster Hyper-V on parent partition Hyper-V child partitions and Initial Store configuration file Tasks Complete tasks 1 through 7: Note: The EMC NetWorker Module of Microsoft Applications Release 2.3 Administration Guide provides details about tasks 1 through Configure a backup pool for snapshot operations 2. Configure snapshot policies 3. Configure a backup schedule 4. Configure a backup group 5. Configure a client resource 6. Configure privileges 7. Configure a proxy client Complete tasks 1 through 7: Note: The NetWorker Module of Microsoft Applications Release 2.3 Administration Guide provides details about tasks 1 through Configure a backup pool for snapshot operations 2. Configure snapshot policies 3. Configure a backup schedule 4. Configure a backup group 5. Configure a client resource 6. Configure privileges 7. Configure a proxy client Configure application backups Specific instructions for the application are provided in: Performing SQL server backups on page 22 Performing Exchange server backups on page 113 Performing SharePoint 2003 backups on page 188 Performing SharePoint 2007 backups on page 210 Performing DPM server backups on page 61 Configure Windows server Cluster backups Specific instructions for the application are provided in the EMC NetWorker Module of Microsoft Applications Release 2.3 Administration Guide. Complete tasks 1 through 5: Note: The EMC NetWorker Module of Microsoft Applications Release 2.3 Administration Guide provides details about tasks 1 through Configure a backup pool for snapshot operations 2. Configure snapshot policies 3. Configure a backup schedule 4. Configure a backup group 5. Configuring a Hyper-V client resource on page 86 Performing Hyper-V backups 85

86 Microsoft Hyper-V Backup and Recovery Table 21 Backup tasks for Hyper-V (page 2 of 2) Hyper-V parent partition Hyper-V child partition applications Application data, such as: SQL server SharePoint server Exchange server System Center DPM Windows server Cluster Tasks Configure application backups Specific instructions for the application are provided in: Performing SQL server backups on page 22 Performing Exchange server backups on page 113 Performing SharePoint 2003 backups on page 188 Performing SharePoint 2007 backups on page 210 Performing DPM server backups on page 61 Configure Windows server cluster backups Specific instructions for the application are provided in the EMC NetWorker Module of Microsoft Applications Release 2.3 Administration Guide. Note: Hyper-V child partition snapshots are not related to NMM or NetWorker snapshots. Hyper-V child partition snapshots are created, viewed, and applied to the child partition through Hyper-V Manager. When NMM backs up a Hyper-V child partition, the Hyper-V child partition snapshots are part of that backup. Configuring a Hyper-V 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 can create multiple client resources for the same NMM host. In this way, you can apply different backup attributes to different types of information on the same host. For example, if the NMM host is an Exchange server, you can: Create one client resource to back up the Exchange databases. Create another client resource to back up Windows system component data. This allows you to back up Exchange databases many times a day and back up Windows system component data only once a day. To create a Hyper-V 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. 86 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

87 Microsoft Hyper-V Backup and Recovery 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines: To back up all of Hyper-V child partitions and the Initial Store configuration file, specify: APPLICATIONS:\Microsoft Hyper-V To back up the child partitions, specify: APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_1 APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_2 To back up the Initial Store configuration file, specify: APPLICATIONS:\Microsoft Hyper-V\Initial Store Note: The Microsoft Hyper-V save set and Initial Store configuration file save set cannot be specified in a proxy backup group: APPLICATIONS:\Microsoft Hyper-V APPLICATIONS:\Microsoft Hyper-V\Initial Store 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 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 following fields empty: Remote user Password 14. In the Backup command attribute, type the backup command: nsrsnap_vss_save.exe 15. In the Application information attribute: a. Type the following variable and value: NSR_SNAP_TYPE=vss NSR_DATA_MOVER=<proxy_client_name> b. Type application variable settings and their values on separate lines. 16. Click the Globals (1 of 2) tab. 17. In the Aliases attribute, type the NETBIOS name for the client. Note: 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. 18. Click the Globals (2 of 2) tab. Performing Hyper-V backups 87

88 Microsoft Hyper-V Backup and Recovery 19. 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 is part of a cluster, type the names of the physical nodes of the cluster in the Remote Access attribute. 20. Click OK. Performing Hyper-V recovery When the files are backed up, administrators can recover all of the Hyper-V components, the Initial Store configuration file, or individual child partitions, depending on what was specified in the backup save set. The following sections describe Hyper-V recovery: Turning the child partition offline for recovery on page 88 Hosting the recovered virtual systems on page 88 Specifying the destinations for the Hyper-V configuration files and virtual system on page 89 Selecting Hyper-V recovery options on page 89 Turning the child partition offline for recovery A child partition must be offline before recovery can start. If the child partition is online at the time recovery is started, the Hyper-V writer will first turn off the child partition. Once the child partition is offline, the current child partition is destroyed, the recovery version is restored, and the child partition is registered. The Hyper-V writer automatically handles detecting whether the child partition is on-line, and turning it off. There is no action required by the administrator. Hosting the recovered virtual systems The Destination Host window allows you to specify the server on which you want to host the recovered virtual systems. To recover to the same location as the original: 1. Select Recover (Overwrite) Virtual System to original location. The Finish button is available and Next button will be unavailable when this option is selected. 2. Click Finish. The Finish button validates the server location and displays the Hyper-V Recovery Options page. 88 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

89 Microsoft Hyper-V Backup and Recovery Specifying the destinations for the Hyper-V configuration files and virtual system The Destination Path page allows you to specify the destination for the Hyper-V configuration files, and the destination for each virtual system. To change settings on this page: 1. In the Destination for Hyper-V configuration files box, click Browse to change the destination path. The Select Virtual System Destination list displays the destinations for each virtual system VHD. 2. To change a destination: a. Select a virtual system. b. Click Change Destination. The Remote Directory Browser dialog box appears. 3. Click Finish to validate the settings. If the destinations are valid, the Hyper-V Recovery Options Summary dialog box appears. Selecting Hyper-V recovery options The Recovery Options Summary page lists the Hyper-V Recovery and NetWorker Recover Options. This allows you to review the settings before starting the recovery. The Hyper-V Recovery Options page appears when you click Recover in the Hyper-V Recover Session view or at the end of the Hyper-V Recovery wizard. This page displays the settings specified in the Destination Host Selection page and Destination Path page. To change the Hyper-V recovery options: If you have reached this page through the Hyper-V Recover Session toolbar: a. Click Cancel > Advanced Options. This launches the Hyper-V Recovery Options wizard. b. In the Hyper-V Recovery Options wizard, click Back. If you have reached this page through the Hyper-V Recover Session view, click Advanced Options on the Hyper-V Recover Session toolbar. To change the NetWorker recover options, either: Click Recover Options. or In the Hyper-V Recover Session view, click Recover Options on the Hyper-V Recover Session toolbar. The NetWorker Recover Options settings are specified on the General, NetWorker, and Security tabs. To validate all pages, click Start Recover. If all pages are valid, the wizard closes and recovery starts. Performing Hyper-V recovery 89

90 Microsoft Hyper-V Backup and Recovery Selecting the destination of Hyper-V recovery The destination of the Hyper-V recovery can be selected: To the original machine Performing Hyper-V recovery to the original machine and location on page 90 provides details. To a different machine or location Performing directed Hyper-V recovery to a different machine or location on page 91 provides details. Note: When a Hyper-V recovery is performed on Windows server Core 2008 or 2008 R2, the recovery is a directed recovery. Performing Hyper-V recovery to the original machine and location To recover Hyper-V components to the original machine and location: 1. Open the NMM software and select the NetWorker Server on which the NMM software was configured for backup. If NMM is part of a cluster, select the physical client to which you are recovering data. The physical client can be selected from the Client list attribute in the application toolbar. 2. From the left pane, select Recover > Hyper-V Recover Session. 3. From the navigation tree, select the Microsoft Hyper-V writer, or individual child partitions under the Microsoft Hyper-V writer. 4. From the Hyper-V Recover Session toolbar, click Recover. The Hyper-V Recover Session Summary dialog box appears. 5. If all the options look correct, go to step 11. If you want to change options, go to step Click Recover Options. 7. On the General tab, specify the Diagnostic Output Level. 8. On the NetWorker tab specify the Restore Type, and select or clear Terminate recover of item if errors are encountered. Note: Restore of Hyper-V components requires a Restore Type of Conventional Restore. 9. On the Security tab, specify pass phrases if any are needed. 10. Click OK to close the Hyper-V Recover Session Options dialog box. 11. Click Start Recover. NMM validates all pages. If all pages are valid, recovery begins. 90 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

91 Microsoft Hyper-V Backup and Recovery Performing directed Hyper-V recovery to a different machine or location To recover Hyper-V components to a different machine or location: 1. Open the NMM software and select the NetWorker Server on which the NMM software was configured for backup. Note: If NMM is part of a cluster, select the physical client to which you are recovering data. The physical client can be selected from the Client list attribute in the application toolbar. 2. From the left pane, select Recover > Hyper-V Recover Session. 3. From the navigation tree, select the Microsoft Hyper-V writer, or individual child partitions under the Microsoft Hyper-V writer. 4. From the Hyper-V Recover Session toolbar, click Advanced Recovery. The Hyper-V Restore Wizard starts and the Destination Host page appears. 5. Specify the destination host server for the Virtual System recover: To recover to the same location as the original: a. Select Recover (Overwrite) Virtual System to original location. b. Perform the steps in To perform validation and start recovery: on page 92. To recover to a different path on the same Hyper-V server: a. Select Recover Virtual System to a different path and then click Next. The Destination Path page appears, and you can specify a destination for each Virtual System. b. Click Browse to specify the destination location for the configuration files. After selecting the destination location for the configuration files, you can change the destination location for the child partition s virtual disks. c. To change the destination location for a virtual disk, select the child partition s virtual disk in the list, and then click Change Destination. Repeat as needed for each virtual disk destination that you want to change. d. When you have completed changing destinations, go to To perform validation and start recovery: on page 92. Note: The destinations provided on this page are Microsoft's default configuration file locations and may not match your Hyper-V configuration. Change the destination as needed. When a directed recovery is attempted to a different path on the same Hyper-V server, the child partition that is recovered is taken offline and the data is recovered to the alternate location. The child partition is then registered pointing to the data in the new location. You can remove the Virtual Hard Disk (VHD) files of the original child partition manually after the recovered Hyper-V child components are up and running. Selecting the destination of Hyper-V recovery 91

92 Microsoft Hyper-V Backup and Recovery To recover to a different Hyper-V server: a. Click Recover Virtual System to a different Hyper-V server. b. From the Select Remote Host list click the server you want to recover to. c. Click Next. The Destination Path page appears, where you can specify a destination for each Virtual System. d. Click Browse to specify the destination location for the configuration files. After selecting the destination location for the configuration files, you can change the destination location for the child partition s virtual disks. e. To change the destination location for a virtual disk, select the child partition s virtual disk in the list, and then click Change Destination. Repeat as needed for each virtual disk destination that you want to change. f. When you have completed changing destinations, go to To perform validation and start recovery: on page 92. Note: The destinations provided on this page are Microsoft's default configuration file locations and may not match your Hyper-V configuration. Change the destination as needed. When a directed recovery is attempted to a different Hyper-V server and the destination Hyper-V server has an existing child partition with the same name as the one being recovered, then this child partition is taken offline and the data is recovered to the alternate location. The child partition being recovered is then registered pointing to the data in the new location. You can remove the VHD files of the original child partition present earlier with the same name manually after the recovered Hyper-V child components are up and running. To perform validation and start recovery: 1. Click Finish. NMM performs validation: If the validation is not successful, an error message is displayed. If the validation is successful, a Summary page is displayed listing the Hyper-V and NetWorker Recover options specified. If you need to change any of the options, click the Recover Options or Back button. 2. Click Start Recover: NMM validates all pages. If all pages are valid, recovery begins. 92 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

93 Microsoft Hyper-V Backup and Recovery Restrictions on relocating and restoring to other locations Hyper-V has several restrictions on relocating and restoring to other locations: Directed recover or relocated recover of Hyper-V objects on a Hyper-V server cluster is not supported. Restoring Hyper-V child partitions to non-hyper-v servers is not supported. Relocation recover of Initial Store is not supported. Relocation or redirection of NMM Hyper-V backups taken before an NMM 2.3 upgrade is not supported. When a child partition is redirect recovered to a second Hyper-V server, the user must update the Network Adapter settings of the child partition with the Hyper-V Manager before starting the child partition. Performing Hyper-V parent partition disaster recovery Successful disaster recovery starts with good backups at all levels on the Hyper-V physical server. The frequency of these backups depends on your retention policies, the frequency that the data on your servers and applications changes, and the type of application. IMPORTANT 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. or - The SYSTEM COMPONENTS:\ save set along with the system volume, for example C:\. Regardless of the frequency of your backups, disaster recovery must proceed in a specific order starting with the host machine and ending with the application data on your child partition guests. Figure 16 on page 94 describes the order and types of recovery. Performing Hyper-V parent partition disaster recovery 93

94 Microsoft Hyper-V Backup and Recovery Hyper-V virtual machines with guest operating systems and applications Physical server with Windows Server 2008 host operating system Virtual Machine VS-1 Windows Server 2008 x64 Microsoft Exchange Server On each guest, recover the applications using the recovery process appropriate for each application. Virtual Machine VS-2 Windows Server 2003 Microsoft Office SharePoint Server 2003 Virtual Machine VS-3 Windows Server 2003 Microsoft Data Protection Manager Virtual Machine VS-4 Windows Server 2003 Microsoft SQL Server Hyper-V configuration file 1. On the physical server host, recover the host volumes and system components. 2. Re-enable the Hyper-V role. 3. On the physical server host, recover the Hyper-V virtual machine guests and Hyper-V configuration file. GEN Figure 16 Disaster recovery order for a Hyper-V server Full disaster recovery requires that the following backups are performed ahead of time on a regular schedule: Physical host: Application data Windows volumes Windows system components Hyper-V on host: Hyper-V child partitions and Initial Store configuration file Hyper-V in-guest: Application data IMPORTANT Before starting disaster recovery, ensure the target machine is up to date with the Hyper-V Update for Windows server 2008 x64 Edition (KB950050). This article and download is available from the Microsoft Download Center. If this update is not installed prior to recovery, the system will not come back after recovery of system components. 94 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

95 Microsoft Hyper-V Backup and Recovery To perform a Hyper-V host disaster recovery: 1. Review best practices: Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 failover cluster on page 97 Best practices on page Recover the physical host which was backed up by NMM. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about recovering the NMM client. 3. Re-enable the Hyper-V role on the host. Consult Microsoft documentation for information about enabling the Hyper-V role on Windows server 2008 and Windows server 2008 R2. 4. On the host, perform a recovery of Hyper-V as described in Performing Hyper-V recovery on page From within each guest, perform a recovery of each application by using the appropriate procedure for the application. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about recovering applications, including links to specific recovery steps for each application. Best practices This section provides the best practices for: Hyper-V parent partition backup and recovery on page 95 Hyper-V child partition applications backup and recovery on page 96 Hyper-V parent partition backup and recovery This type of backup uses the Hyper-V writer on the parent partition: To get the most benefit from the Hyper-V role, create separate child partitions for each application, so that the only application-type backup and recovery performed at the host level is for Hyper-V. After disaster recovery of the parent partition, you may need to recover applications within each child partition if you are doing separate child partition backups, and those backups are more recent than the complete parent partition backups. Performing Hyper-V parent partition disaster recovery on page 93 provides a complete list of these tasks. Best use for this type of backup is bare metal recover of a guest and for recovery of operating system roles. Best practice for Initial Store backup is to back up when Hyper-V configuration changes are made. Initial Store does not need to be backed up each time a child partition guest is backed up. In NMM, the Hyper-V writer does not support backup of the configuration file Initial Store to a proxy client. The primary purpose for restoring Initial Store in NMM is for disaster recovery of the Hyper-V server. Best practices 95

96 Microsoft Hyper-V Backup and Recovery Back up Data Protection Manager, Exchange, SQL server, or SharePoint applications from within the child partition. The Hyper-V backup is not recommended as the method to back up applications on a child partition. In Hyper-V backup: The child partition copy backup method is used. There is no child partition log management. For example, Exchange logs are not truncated. Roll-forward recovery is not available for child partition level disaster scenarios. From a parent partition, a roll-forward recovery of a child partition is not possible. Recoveries from a parent partition are point-in-time (disaster recovery). Child partition pass-through disks are skipped during Hyper-V parent partition backup. Basic disks are supported only within child partitions. Note: Backup of dynamic disks within child partitions is not supported. The guest snapshot is mounted during the Hyper-V backup process, and this changes the disk signature on dynamic disks in a guest. Any VSS hardware or software provider can be used. The hardware provider must support Windows 2008 extensions for AutoRecoverable snapshots. Windows server 2008 and 2008 R2 Failover Clustering is supported Allows you to configure failover of child partition. EMC storage connected to Fibre Channel or iscsi storage can be used in the parent to host child partitions. Do not take a Hyper-V VSS parent partition snapshot of Hyper-V child partitions that are part of a SharePoint farm. To back up SharePoint on the Hyper-V child partition: a. Install the NMM client on the child partition. b. Perform the Share Point backup locally from within the child partition. The Microsoft website provides recommendations and requirements about using SharePoint and Hyper-V together. Hyper-V child partition applications backup and recovery This type of backup and recovery is performed within the child partition, and uses application and system components writers available on that child partition: The Exchange team recommends using backups within the child partition as the preferred method for Exchange backup and recovery. NMM supports roll-forward recovery for Exchange, when Exchange is backed up within the child partition. Within child partitions, standard application backup and recovery rules and capabilities apply, including roll-forward recoveries. VSS hardware providers for iscsi storage are supported for iscsi disks that are native within the child partition. 96 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

97 Microsoft Hyper-V Backup and Recovery VSS hardware providers for Fibre Channel storage are supported when the hardware provider can support hardware snapshots without Custom ControlDataBlock (CDB): CLARiiON arrays are supported because they do not require custom CDB. Symmetrix DMX TM arrays are not supported because they require custom CDB. For VSS hardware provider, a transportable snapshot must be created, and the proxy node must be a physical machine. The proxy cannot be the host machine, and it must match the operating system version of the child partition. This requirement is independent of Hyper-V. Child partition pass-through disks are skipped in Hyper-V parent partition backup and are supported by backups within the child partition. Windows server 2008 Failover Clustering with iscsi storage is supported. Child partition Windows server 2008 Failover Clustering with Fibre Channel storage is not supported because SCSI-3 is not supported in Hyper-V child partitions. Windows server 2003 Clustering is supported, but at the time of this NMM 2.3 release, Microsoft has not issued a support statement for it. Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 failover cluster When a Hyper-V child partition resides on a physical machine, which is part of a Windows 2008 Failover Cluster, you cannot back up or recover the child partition as part of the cluster virtual server. For example, consider the following Failover Cluster setup: A cluster, Cluster_Virtual_Name, contains two physical machines, Physical_Machine_1 and Physical_Machine_2. Physical_Machine_1 contains two child partitions, VM1 and VM2. You want to back up and recover VM1. If you create a NetWorker client resource for: Cluster_Virtual_Name, backup and recover of VM1 through that client resource is not supported. Physical_Machine_1, you can specify: Backup of the Hyper-V application (APPLICATIONS:\Microsoft Hyper-V). This includes all child partitions on the physical machine. An individual child partition VM1 (APPLICATIONS:\Microsoft Hyper-V\VM1). You can recover VM1 from the NW client resource of the physical machine, Physical_Machine_1. This type of recovery is described in Performing Hyper-V recovery to the original machine and location on page 90. You can use redirected recover to recover VM1 from the NetWorker client resource of the physical machine, Physical_Machine_1 to the Physical_Machine_2. This type of recovery is described in Performing directed Hyper-V recovery to a different machine or location on page 91. Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 failover cluster 97

98 Microsoft Hyper-V Backup and Recovery 98 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

99 5 Microsoft Exchange Server Backup and Recovery This chapter includes the following topics: Overview Performing Exchange server backups Performing Exchange server recovery Selecting a storage group restore destination Performing Microsoft Exchange server 2007 directed recovery Performing Microsoft Exchange server 2007 disaster recovery Performing a quick recovery of a deleted mailbox in Exchange Best practices Microsoft Exchange Server Backup and Recovery 99

100 Microsoft Exchange Server Backup and Recovery Overview Microsoft Exchange server 2003 and Exchange server 2007 support VSS through Microsoft-supplied application writers. By using the VSS writers, you can back up and restore Exchange databases and transaction log files. Review the following sections before starting Exchange server backup and recovery: Microsoft Exchange server 2007 MAPI client and Collaboration Data Objects support on page 100 Exchange server versions supported by NMM client on page 101 NMM and Exchange server support for I18N on page 101 Types of supported backup on page 101 Backup levels on page 102 Types of supported recovery on page 102 Compatibility with previous Exchange server backups on page 103 Creation of shadow copy and snapshot process in an Exchange server production on page 103 LAN-based Exchange server configuration with a storage area network and a proxy client on page 104 Exchange backup scenarios on page 105 Exchange recovery scenarios on page 110 Exchange 2003 and 2007 writers on page 111 Commands and attributes for Exchange backup and recovery on page 112 Configuring dedicated storage node for Exchange 2007 CCR environment on page 112 Microsoft Exchange server 2007 MAPI client and Collaboration Data Objects support In Exchange server 2007, the Messaging API (MAPI) and Collaboration Data Objects (CDO) kit is required for Recovery Storage Group (RSG) support. Access to Exchange messaging stores utilized by NMM mailbox backups requires the MAPI and CDO kit. The MAPI client libraries and CDO are not included with Exchange server 2007 and can be downloaded from Microsoft s website. For information on downloading and installing this package, search for Microsoft Exchange server MAPI Client and Collaboration Data Objects 1.2.1" on the Microsoft Download Center website. Download version EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

101 Microsoft Exchange Server Backup and Recovery Exchange server versions supported by NMM client The EMC Information Protection Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions that are supported by the NMM client. NMM client supports the following versions of Microsoft Exchange server: Exchange server 2003 (x86) SP2 Exchange server 2007 (x64) SP1 or later Exchange 2007 and 2007 SP3 on Windows server 2008 R2 Note: NMM does not support Exchange server 2000 or earlier. NMM and Exchange server support for I18N Microsoft requires that Exchange server 2003 storage group names to be in the same locale as the Microsoft Exchange server. Types of supported backup NMM supports the following types of backups: By using Microsoft VSS software provider: For Exchange server 2003: Point-in-time snapshot backup NMM allows the creation of a point-in-time copy of data. The snapshot includes exact copies of data and open files. This allows the backup of the Exchange server while the Exchange database is online or in use. Single server backup For Exchange server 2007 In addition to backup options listed for Exchange server 2003, Exchange server 2007 provides addition support for: Single copy cluster (SCC) backup Exchange server 2007 cluster continuous replication (CCR) active node and passive node backup! IMPORTANT In an Exchange CCR configuration, perform backups from the passive node. Recoveries go to the active node. Local continuous replication (LCR) backup of the production data, but not of the replicated data Global source-based deduplication By using EMC hardware provider EMC CLARiiON and EMC Symmetrix: Proxy node and proxy storage node backups Performing Exchange server backups on page 113 provides details about how to perform Exchange system backups. Overview 101

102 Microsoft Exchange Server Backup and Recovery Backup levels NMM supports the following backup levels: Full backups Full backups are available for both Microsoft Exchange server 2003 and Microsoft Exchange server A full backup is a complete backup that archives every selected database and all necessary log files. Log files older than the checkpoint at the time the backup was started are deleted after the backup completes. If you perform a full backup on a daily basis, you can prevent log files from consuming space on the hard disk. Incremental backups Incremental backups are only available for Microsoft Exchange server It is not available for Microsoft Exchange server An incremental backup backs up only selected data, and therefore improves backup performance by reducing the amount of data that is processed. However, recovery may take longer because you are recovering the last full backup plus each incremental backup that was performed since the full backup. Note: Incremental backup of Exchange server 2007 requires NetWorker 7.4, NetWorker 7.5.1, or NetWorker 7.6, or later. If you are using NetWorker 7.5, obtain and install NetWorker to use this functionality. The following Exchange server data are backed up: Mounted Exchange server databases Transaction log files Checkpoint files in a storage group Types of supported recovery NMM supports several types of recovery: For Exchange server 2003: Roll-forward recovery: This recovery can be performed when the current log LUN is available. No data is lost when restoring from backup. Recovers the Exchange server data from the last backup, and allows granular recovery selection down to the individual mailbox database level. Deleted is not recovered. Point-in-time recovery: Use when log files have been lost. All new data after the last backup is lost. Only the transaction files that were part of the backup set are restored. Deleted can be recovered. Rollback recovery: Also known as a destructive recovery, because all changes that are made after the selected snapshot is taken are overwritten. The whole snapshot must be selected for recovery. Storage groups within a snapshot cannot be selected for recovery. A single storage group can be recovered if the save set specified only that storage group for backup. 102 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

103 Microsoft Exchange Server Backup and Recovery Exchange server 2007 In addition to recovery options listed for Exchange server 2003, Exchange server 2007 provides addition support for: Database recoveries to the Exchange RSG. Mailbox items recoveries from RSG databases with Exchange Exchange RSG mailbox browsing; mailbox, folder, and message recovery. Exchange database recoveries to alternate servers and alternate storage groups. Performing Exchange server recovery on page 131 provides details about Exchange 2003 and 2007 recovery. Compatibility with previous Exchange server backups The Exchange database and logs that are backed up by using previous releases of NetWorker software may not be restored by using NMM: If you have upgraded to NMM, perform a full backup of Exchange server to perform NMM point-in-time restores in the future. For example, if you are currently using NetWorker Module for Exchange (NME): a. Restore the Exchange backups by using NME. b. After the recovery, perform a full backup of the Exchange server with NMM. If you are currently using previous NMM releases, you can restore backups by using NMM 2.3. If you have upgraded the Microsoft Exchange server, including Exchange Service Pack upgrades, you cannot perform recovery from a backup created before the upgrade. After an Exchange server upgrade, perform a full backup to ensure that you have a new recoverable backup. Creation of shadow copy and snapshot process in an Exchange server production In NMM 2.3, the creation of shadow copy is separated from the notification to VSS writers that backup is complete. NMM registers the shadow copy as a snapshot and backs it up to media successfully before the notification is sent to the VSS writers. If the backup to media fails, then that failure is reported to the Exchange VSS writer and log truncation does not occur. Setting the Exchange snapshot policy In NMM 2.3, Exchange backups require the following settings for the snapshot policy before a backup is started: Do not set the Backup Snapshots attribute to None for snapshot policies. If the Backup Snapshots attribute is set to None, there is a backup failure and an appropriate error message is sent to savegrp. The Retain Snapshots attribute can be set to any number, including zero. If the Retain Snapshots attribute is set to a non -zero value, add the NSR_EXCH_RETAIN_SNAPSHOTS=yes entry to Application information. The upgrade from NMM 2.2.x to NMM 2.3 is only impacted for the backups completed before the upgrade. In such a case, full backups must be taken. Overview 103

104 Microsoft Exchange Server Backup and Recovery LAN-based Exchange server configuration with a storage area network and a proxy client Figure 17 on page 105 illustrates LAN-based Exchange server configuration with a storage area network and a proxy client: Both the Exchange server and the proxy client have the NMM client installed and the NMM client installed must be of the same version. The proxy client frees resources on the Exchange server by offloading from the Exchange server the work of processing and backing up snapshots. When a backup operation uses a proxy client, it is known as a serverless backup. The data moves as follows: 1. The NetWorker server initiates the process by contacting the Exchange server where the NMM client software is installed. 2. The Exchange server with the NMM client software creates a snapshot of the data on the storage volume. Note: In Figure 17 on page 105, snapshots are represented by S1 through S5. 3. The snapshot is made visible to the proxy client. 4. NMM runs the eseutil consistency check for Exchange on the proxy host. 5. If the consistency check is successful, NMM commits the shadow copy. 6. 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, or tape. 7. Once backup is complete and successful, a notification is sent by NMM to VSS about it. VSS in turn notifies the Exchange writer that the backup is complete and successful. Logs may or may not be truncated and this decision is taken by Exchange. Exchange also decides which logs to be truncated and when. Logs may be truncated but not immediately. The EMC VSS provider is used for the transportable snapshot. When the administrator moves the shadow copy to the traditional storage medium connected to the proxy host, NMM provides the option to move the transportable snapshot from the proxy host to the traditional storage medium. For this setup, the administrator must configure a SAN storage node as a proxy client. 104 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

105 Microsoft Exchange Server Backup and Recovery. NetWorker Server or LAN Exchange Server NetWorker Module for Microsoft Applications Proxy client NetWorker Module for Microsoft Applications SAN Primary storage (For example, CLARiiON or Symmetrix) S5 S1 S4 S3 S2 NetWorker Storage Node or Traditional storage GEN Figure 17 Snapshot process with Exchange production server and proxy client Exchange backup scenarios This section describes the various Exchange backup scenarios: Single server backup with VSS software provider on page 105 SCC backup on page 106 Microsoft Exchange server 2007 CCR active node and passive node backup with a VSS software provider on page 107 Global source-based deduplication on page 109 Proxy node and proxy storage node backups with EMC CLARiiON and EMC Symmetrix VSS hardware providers on page 109 Following the failure of the snapshot storage media, the Exchange database or storage group must be restored, but before another snapshot is created. However, it becomes necessary to restore from an older snapshot because the most recent snapshot is unavailable. Any data that was backed up after that is lost. Single server backup with VSS software provider Microsoft Exchange server 2007 introduces role-based deployment. With this feature, you can deploy specific server roles that provide messaging functionality. A server role is a unit that logically groups the required features and components that are required to perform a specific function in your messaging environment. Overview 105

106 Microsoft Exchange Server Backup and Recovery Figure 18 on page 107 illustrates how Microsoft Exchange 2007 provides the following five distinct server roles that align to how messaging systems are typically deployed and distributed: Client access Edge transport Hub transport Mailbox Unified messaging Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122 provides details about the Exchange client resource and describes the steps for configuring standard Exchange client resources for a single server backup with a VSS software provider. Note: Use the NetWorker client to back up the transport servers. NMM is not required for backing up the transport servers as there are no storage groups to back up. SCC backup SCC is a clustered mailbox server that uses shared storage in a failover cluster configuration to allow multiple servers to manage a single copy of the storage groups. This feature is similar to the clustering features in previous versions of Microsoft Exchange. However, some significant changes and improvements that have been made. The improvements include the following: Improved setup experience Setup of a clustered mailbox server in a single copy cluster is very different from the setup process used in previous versions of Microsoft Exchange: In previous versions, when Exchange setup was complete there were additional tasks that were required to be performed by using Cluster Administrator before a clustered mailbox server (referred to in previous versions as an Exchange virtual server) was created. In Microsoft Exchange 2007, clustered mailbox server installation is integrated into the Exchange setup. As a result, the clustered and non-clustered setup experience is similar which reduces the learning curve traditionally associated with clustered applications. In addition, when setup is complete, a clustered mailbox server is created. Optimized default settings In previous versions, after the clustered mailbox server was created, additional administrative tasks had to be manually performed to configure the clustered mailbox server for optimal behavior. In Microsoft Exchange 2007, each clustered mailbox server is configured with the optimal settings during setup. Doing so eliminates the need for an administrator to perform these tasks manually. Improved management experience In previous versions, Cluster Administrator was required for several management tasks, such as stopping and starting a clustered mailbox server and moving a clustered mailbox server between nodes in the cluster: 106 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

107 Microsoft Exchange Server Backup and Recovery In Microsoft Exchange 2007, these tasks and new clustered mailbox server management tasks have been integrated into the Exchange management tools. For example, you can use the Exchange Management Shell to stop, start, and move clustered mailbox servers. In Microsoft Exchange 2007 SP1 or later, you can also use the Exchange Management Console to stop, start, and move clustered mailbox servers. SCC architecture As illustrated in Figure 18 on page 107, SCCs require the use of a shared-nothing architecture, which includes shared disk storage. In a shared-nothing architecture, although all nodes in the cluster can access shared data, they cannot access it at the same time. For example, if a physical disk resource is assigned to node 1 of a two-node cluster, node 2 cannot access the disk resource until node 1 is taken offline, fails, or the disk resource is manually moved to node 2. Mailbox server Active Node Private Network Mailbox server Passive Node Public Network Shared storage array Logs DB Quorum Storage connection to Passive Node Storage connection to Active Node GEN Figure 18 SCC architecture Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122 provides details about the Exchange client resource and describes the steps for configuring standard Exchange client resources for SCC. Microsoft Exchange server 2007 CCR active node and passive node backup with a VSS software provider CCR is a high-availability feature of Microsoft Exchange server It combines the asynchronous log shipping and replay technology built into Microsoft Exchange 2007 with the failover and management features provided by the Cluster service. Overview 107

108 Microsoft Exchange Server Backup and Recovery Figure 19 on page 108 illustrates how CCR combines the following elements: Failover and virtualization features provided by Microsoft failover clusters A majority-based failover cluster quorum model that uses a file share as a witness for cluster activity Transaction log replication and replay features in Microsoft Exchange 2007 Message queue feature of the Hub Transport server called the transport dumpster Figure 19 CCR core architecture In Exchange 2007 SP1 and later, CCR uses two computers (referred to as nodes) joined in a single failover cluster running either Windows server 2003 Service Pack 2 or Windows server 2008: The nodes in the failover cluster host a single clustered mailbox server. A node that is currently running a clustered mailbox server is called the active node. A node that is not running a clustered mailbox server, but is part of the cluster, and the target for continuous replication, is called the passive node. As a result of scheduled, maintained, and unscheduled outages, the designation of a node as active or passive changes several times throughout the lifetime of the failover cluster. 108 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

109 Microsoft Exchange Server Backup and Recovery Backups in the Exchange CCR environment The steps for configuring an Exchange client resource for an Exchange CCR environment vary depending on whether: The node is active node or passive node. Configuring backup for an Exchange CCR active node or passive node on page 124 provides the details. The node is the active node or passive node, and a Data Mover is used, the following sections provide details: Configuring backup for an Exchange CCR active node with a Data Mover on page 126 Configuring backup for an Exchange CCR passive node with a Data Mover on page 126 The node is passive node and deduplication is required. Configuring deduplication backups in a CCR environment for a passive node on page 127 provides details. Global source-based deduplication An Exchange client resource can be configured to use deduplication. These sources provide more information: The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides in-depth information about deduplication. Configuring deduplication backups in a CCR environment for a passive node on page 127 provides additional steps for creating an Exchange client resource in a CCR environment. Proxy node and proxy storage node backups with EMC CLARiiON and EMC Symmetrix VSS hardware providers Proxy node and proxy storage backups require the use of VSS hardware providers, which allow transporting application server snapshots to a proxy node and a proxy storage node, respectively, for backup services. For example, the EMC VSS provider supports CLARiiON and Symmetrix disk arrays. NMM supports multiple VSS hardware providers. The following sources provide more information: The EMC Information Protection Software Compatibility Guide provides a complete list of providers. Configuring proxy node or proxy storage node backup with the CLARiiON hardware provider on page 128 provides the procedure for configuring proxy node and proxy storage node backups with the EMC hardware provider. Configuring proxy node or proxy storage node backups with the EMC Symmetrix hardware provider on page 130 provides the procedure for configuring proxy node and proxy storage node backups with the Symmetrix hardware provider. Overview 109

110 Microsoft Exchange Server Backup and Recovery Exchange recovery scenarios This section provides details about the various Microsoft Exchange recovery scenarios and the respective configurations requirements: Conventional recovery from disk, tape, and VTL on page 110 Roll-forward recovery on page 110 Point-in-time recovery on page 110 Rollback recovery on page 111 Conventional recovery from disk, tape, and VTL A conventional recovery consists of recovering data from a snapshot that has been rolled over to tape, disk, or Virtual Tape Library (VTL). Conventional recoveries support the same level of item selection as do instant recoveries. Configurations for traditional recovery from disk, tape, and VTL on page 133 provides configuration details. Roll-forward recovery This option recovers the Exchange databases from the last full backup, and logs from incremental backups. All existing Exchange transactions that occurred after the time of the last backup are retained. This recovery is carried out when the Exchange server or database fails but the current log LUN is available. NMM restores the database files and transaction logs from backups and uses the current logs on the server to roll the database forward. No data is lost by restoring from backup. A single mailbox database can be marked for this type of recovery in NetWorker Module for Microsoft Applications. While performing the roll-forward recover, all of the mailboxes pertaining to that storage group are dismounted and once the recovery is successful, all of the mailboxes are remounted. Configurations for roll-forward recovery on page 134 provides configuration details. Note: If you perform a roll-forward recovery, perform a full backup after the recovery. Doing so enables you to recover data to a point-in-time that is after the point-in-time of the roll-forward recovery, if necessary. Also, a roll-forward recovery is not possible after performing a point-in-time recovery. Point-in-time recovery This recovery type is useful when log files have been lost or databases must be restored to a specific backup time. With this option, data can be selected at a storage group level, but not at an individual database level. Point-in-time recovers Exchange data only up to the time of the backup that is being recovered, and does not include subsequent transactions. All new data after that backup is lost. When point-in-time recovery is used, only the transaction log files that were part of the backup set are restored. Additional log files generated since the time of backup are not restored, and the databases are recovered only to the point of the backup. Configurations for point-in-time recovery of an Exchange 2007 on page 135 provides configuration details. Note: To perform a point-in-time restore, the administrator must first select the whole storage group and then perform the recover. The log files currently on disk are moved to another directory before the restore takes place. They can be manually deleted by the user if they are no longer required after a successful restore. 110 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

111 Microsoft Exchange Server Backup and Recovery Rollback recovery This is a volume-level operation so any other data on the volume will also be lost during a rollback. This recovery is known as destructive recovery because all changes that are made after the selected snapshot is taken are overwritten. Note: NMM does not support rollback restore for backups performed with EqualLogic or Celerra hardware. Only conventional restore and snapshot restore are supported for those hardware. Rollback recovery of Exchange does not allow granular selection of storage groups for recovery, the whole snapshot must be selected for recovery. To perform rollback restore of a particular storage group, the storage group must have previously been backed up by itself, and by using a save set that specified that particular storage group. For example, to perform a rollback restore of the storage group SG1, the storage group would have had to been previously backed up with the save set APPLICATIONS:\Microsoft Exchange Writer\SG1 (Exchange server 2003) or APPLICATIONS:\Microsoft Exchange 2007\SG1 (Exchange server 2007). To perform an Exchange rollback operation the following requirements apply: The snapshot should be a transportable snapshot. The rollback option is not available if the snapshot is taken by the software provider. A storage array descriptor file, sa.ini, must be configured with details of the type of storage used. The Microsoft Exchange checkbox titled This database can be overwritten by a restore must be selected for each Exchange database that is to be recovered. This checkbox can be found by using the Exchange SYSTEM Manager application in Exchange server 2003 or Exchange Management Console in Exchange server The administrator must manually mount the Exchange databases after recovery. Automatic mounting of database is not available for rollback restore. The EMC NetWorker Module for Microsoft Application Release 2.3 Administration Guide provides more information about rollback recovery, creating a storage array descriptor file, and the steps to perform a rollback recovery. Configurations for point-in-time recovery of an Exchange 2007 on page 135 provides configuration details. Exchange 2003 and 2007 writers Table 22 on page 111 lists the Application writers used by NMM for Exchange server backup and recovery. Table 22 Writers used by NMM for Exchange server backup and recovery Application writers Exchange 2003 uses one writer Description An Information Store writer Exchange 2007 uses two writers An Information Store writer A Replication Service writer. The Replication Service writer is only used in a CCR environment. Overview 111

112 Microsoft Exchange Server Backup and Recovery Commands and attributes for Exchange backup and recovery Table 23 on page 112 lists the commands and attributes used by NMM for Exchange server backup and recovery. Table 23 Commands and attributes used by NMM for Exchange server backup and recovery Components Details Description Commands nsrsnap_vss_save.exe This NMM command is used to initiate the VSS-based backup. nsrsnap_vss_recover.exe This NMM command is used to initiate the VSS-based recovery. eseutil.exe This program provided by Microsoft Exchange server 2003 and 2007 is used to check that the database and log files do not contain errors, and that the Exchange server is valid before performing the restore. Attributes NSR_VIRT_SERV This attribute is used to specify the name of the Exchange virtual server client resource in a CCR passive node backup. NSR_INDEX_CLIENT NSR_CHECK_JET_ERRORS NSR_EXCHANGE_LIMIT_SG This attribute is used to specify the backup to be indexed under the client name of the Exchange virtual server; not the passive node client name in a CCR passive node backup. This attribute is used with the nsrsnap_vss_save.exe command to detect Jet errors in the Exchange backup. NSR_CHECK_JET_ERRORS is run before committing the shadow copy for Exchange. This attribute is used to set the number of storage groups for a save set. This is a yes or no attribute, and if set to yes then the save set is restricted to a maximum of 10 storage groups. Configuring dedicated storage node for Exchange 2007 CCR environment Before performing the steps in this section, review the EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide for details about how to set up a dedicated storage node (DSN) in NMM 2.3. To configure a DSN for Exchange 2007 CCR with two mailbox servers by using NMC: 1. Configure CCR setup with two mailbox servers. 2. Create two nodes, for example Node1 and Node2, and virtual client resources by using NMC. 3. Create a DSN device for Node1. 4. Create a DSN device for Node2. 5. Under Node1 client properties, select Globals (2 of 2) > Storage Node column, specify Node1. This could be the Node1 IP or the FQDN name. 6. Under Node2 client properties, select Globals (2 of 2) > Storage Node column, specify Node2. This could be the Node1 IP or the FQDN name. 7. Now under virtual client properties, select Globals (2 of 2) > Storage Node column, specify curphyhost. 112 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

113 Microsoft Exchange Server Backup and Recovery Performing Exchange server backups This section contains the following information: Exchange 2003 and 2007 application information variable settings on page 113 Specifying Exchange 2003 and 2007 save sets for application data on page 115 Displaying valid Exchange data save sets on page 116 Configuring persistent snapshots on page 117 Configuring Exchange server backups on page 119 Configuring Exchange backup schedule on page 120 Configuring Exchange client resource on page 121 IMPORTANT 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. or - The SYSTEM COMPONENTS:\ save set along with the system volume, for example C:\. When backing up data for a Exchange application, ensure that all databases are mounted. Unmounted databases are not backed up, and no warning appears during the backup operation to indicate if any databases are unmounted. Exchange 2003 and 2007 application information variable settings Table 24 on page 113 lists the variables that can be specified in the Application information attribute of the client resource. Table 24 Exchange application information variable settings (page 1 of 3) Attribute name Description Values NSR_SNAP_TYPE=value NSR_DM_PORT=value Specifies the snapshot service provider name. This attribute: Specifies the control port number to use in communicating with the data mover client. This is the control port that the Replication Manager (RM) client service is running on. EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide provides more information about RM ports. vss This value is required. The RM client control port number. For example: NSR_DM_PORT=6728 An RM client control port number must be specified, and must match the value specified during installation. The default value that NMM uses during installation is If you specify a different value during installation, you must specify that value here. Performing Exchange server backups 113

114 Microsoft Exchange Server Backup and Recovery Table 24 Exchange application information variable settings (page 2 of 3) Attribute name Description Values NSR_DATA_MOVER=value application information attribute NSR_ALT_PATH=value This attribute: 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. This attribute: Specifies the path on which to mount Exchange snapshots during the backup process. Exchange snapshots are mounted so that the database consistency check utility, eseutil.exe, can be run. The values include: 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 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 you are setting up an Exchange client resource, it is recommended that you use a proxy client. A proxy client requires hardware for transportable snapshots. 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 Exchange server. Related messages are logged in the client resource host in both the Replication Manager log files and the nmm.raw file. A mount path. For example: NSR_ALT_PATH=G:\mount_replica\ If a proxy client is specified in the NSR_DATA_MOVER attribute, type the mount path on the proxy client. Note: If the file system path specified for NSR_ALT_PATH in Exchange client does not exist, it is automatically created in NMM. NSR_CHECK_JET_ERRORS=value NSR_VIRT_SERV=value Specifies which JET database errors to check for in the event log before taking a snapshot. Note: If errors are found, the snapshot will fail. Specifies the name of the Exchange virtual server client resource in a CCR passive node backup. Note: Do not use this attribute for CCR active node backup. Values include the following: 447 (Exchange server 2007 only) 448 (Exchange server 2007 only) all none Values can be separated with a comma, for example: NSR_CHECK_JET_ERRORS=1018,1019 The default is none. The name of the Exchange virtual server. For example: NSR_VIRT_SERV=virtual_server_name This value is required in a CCR passive node backup. 114 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

115 Microsoft Exchange Server Backup and Recovery Table 24 Exchange application information variable settings (page 3 of 3) Attribute name Description Values NSR_INDEX_CLIENT=value Specifies to index the backup under the client name of the Exchange virtual server, not the passive node client name in a CCR passive node backup. Note: Do not use this attribute for CCR active node backup. The name of the Exchange virtual server. For example: NSR_INDEX_CLIENT=virtual_server_name This value is required in a CCR passive node backup. NSR_EXCHANGE_LIMIT_SG=yes NSR_EXCH_RETAIN_SNAPSHOTS= yes NSR_EXCH_CHECK= yes/no Specifies that the number of Exchange storage groups that are configured for scheduled backup is not more than 10. Specifies snapshot retention for only full backups in Exchange 2003 and Exchange To specify the consistency check for databases. Yes sets the number of SG for scheduled backup to 10. Retains snapshots for full backup. For incremental backups, perform serverless backup only. For Exchange 2007 backups, consistency check is 'yes' by default. Note: If the consistency check is turned off, then the information is logged in the mega.xml file during backup. Specifying Exchange 2003 and 2007 save sets for application data Table 25 on page 115 lists the Exchange save set syntax to specify for supported types of Exchange data. Specify Exchange data save sets in the Save Set attribute of a client resource. Table 25 Exchange 2003 and 2007 save set names (page 1 of 2) Exchange server Type of data to back up Specify the save set name Exchange server 2003 All Exchange server 2003 data APPLICATIONS:\Microsoft Exchange Writer A specific Exchange server 2003 storage group, for example, a storage group named Group_1 APPLICATIONS:\Microsoft Exchange Writer\Group_1 Performing Exchange server backups 115

116 Microsoft Exchange Server Backup and Recovery Table 25 Exchange 2003 and 2007 save set names (page 2 of 2) Exchange server Type of data to back up Specify the save set name Exchange server 2007 All Exchange server 2007 data APPLICATIONS:\Microsoft Exchange 2007 A specific Exchange server 2007 storage group, for example, a group named Group_2 All Exchange server 2007 data in a CCR environment on the active or passive CCR node A specific Exchange server 2007 storage group in a CCR environment on the active or passive CCR node, for example, a group named Group_1 All Exchange server 2007 data on a virtual server, on the active CCR node APPLICATIONS:\Microsoft Exchange 2007\Group_2 APPLICATIONS:\Microsoft Exchange 2007 APPLICATIONS:\Microsoft Exchange 2007\Group_1 APPLICATIONS:\Microsoft Exchange 2007 Note: When backing up an Exchange server 2007 in a CCR environment on a passive CCR system, you must use the NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes. All Exchange server 2007 data in a LCR environment APPLICATIONS:\Microsoft Exchange 2007 A specific Exchange server 2007 storage group in a LCR environment, for example, a group named Group_1 APPLICATIONS:\Microsoft Exchange 2007\Group_1 Displaying valid Exchange data save sets After the NMM client is installed on the Microsoft Exchange server, you can display a list of Exchange save sets available for backup. To display a list of the Microsoft Exchange save sets that are available for backup: 1. Open a command prompt on the Microsoft Exchange server. 2. From the command prompt, type the following command to list the valid application data save set names: If the Microsoft Exchange server is a stand-alone node or LCR active node, type: nsrsnap_vss_save -? If the Microsoft Exchange server is on an Microsoft Exchange 2007 SCC node, type: nsrsnap_vss_save -c virtual_server_name -? Note: If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server. In an Exchange 2007 CCR environment, type the following on both the active and passive nodes as one line: nsrsnap_vss_save -c physical_server_name -A NSR_VIRT_SERV=virtual_server_name -? 3. Press Enter: 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. 116 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

117 Microsoft Exchange Server Backup and Recovery In the Save Set attribute, you can specify either the writer name or the storage group names, but not both in the same save set. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. The application data save sets that are available for backup are listed in a format similar to the following: APPLICATIONS:\Microsoft Exchange Writer APPLICATIONS:\Microsoft Exchange Writer\first_group APPLICATIONS:\Microsoft Exchange 2007 APPLICATIONS:\Microsoft Exchange 2007\second_group URL encoding for 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 when naming Exchange storage groups. For example, a storage group named: Accounting\Bellevue This storage group would be represented in the Save Set attribute as: APPLICATIONS:\Microsoft Exchange 2007\Accounting%5CBellevue Table 26 on page 117 lists the most commonly used special characters and their URL-encoded values. Table 26 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 Configuring persistent snapshots The information in this section is applicable to Exchange server 2003, 2007, and The NSR_EXCH_RETAIN_SNAPSHOTS=yes attribute used for configuring persistent snapshots can be used only for full level backups. For incremental level backup, use the serverless backup policy because the data must be rolled over for incremental backup. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details about serverless backup policy. Performing Exchange server backups 117

118 Microsoft Exchange Server Backup and Recovery When the NSR_EXCH_RETAIN_SNAPSHOTS=yes attribute is used in Application Information field: For full level backup, a warning is displayed: The specified snapshot policy allows snapshots to be stored locally on the client for a period of time before expiration. Locally stored snapshots present a risk of data loss if there is a failure of the local media containing the snapshot, or if a snapshot rollover fails and the corresponding locally retained snapshot expires before a manual rollover can be performed. Group: "%s" Snapshot Policy: "%s" Snapshots Per Day: "%s" Retain: "%s" Backup Snapshots: "%s" Level: "%s". For incremental level backup, an error message is displayed: NMM.. Error: Local retention of snapshots is not allowed when snapshot level is not set to "full". Group: "%s" Snapshot Policy: "%s" Snapshots Per Day: "%s" Retain: "%s" Backup Snapshots: "%s" Level: "%s". To configure local Exchange snapshot retention on an NMM client, perform the following configuration tasks on the NetWorker server: 1. In the NMM client, click Properties > Apps & Modules tab. 2. Add the following attribute to the Application Information field: NSR_EXCH_RETAIN_SNAPSHOTS=yes 3. In the Properties window, for the snapshot policy to be used: a. Set the number of snapshots that you want to retain on the NMM client in the Retain Snapshots field. Ensure to retain at least two snapshots. b. Type the snapshots that you want to rollover to the NetWorker server on a daily basis in the Backup Snapshots text box. Some valid examples are First, Last, All, every n, or n. None and 0 are invalid entries for this feature. This configuration results in the most recent n backups being stored locally on the NMM client, where n is the number added in the snapshot policy's Retain Snapshots field. If the snapshot policy designates a backup to be rolled over to the server, it will also be retained locally until there are n newer snapshots present. The snapshots are stored locally on the NMM client and not on the NetWorker server. Snapshots that are stored locally only present a risk of data loss in the following situation: 1. There is a failure of the local media containing the most recent snapshot, which has not been backed up to a NetWorker server. 2. A need then arises to restore an Exchange database or storage group after the failure of the snapshot storage media, but before another snapshot is created. 3. Because the most recent snapshot is unavailable, it is necessary to restore from an older snapshot, and data newer than that snapshot is lost. 118 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

119 Microsoft Exchange Server Backup and Recovery Configuring Exchange server backups To perform an Exchange server backups, complete the tasks outlined in Table 27 on page 119. IMPORTANT The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details for the first five tasks in Table 27 on page 119. Table 27 Backup task Tasks for configuring an Exchange server backup Consideration 1. 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. 2. Configure snapshot policies For Exchange server backups, always set the backup snapshot policy to All. Backup snapshot policy cannot be set to. Setting the Exchange snapshot policy on page 103 provides more information. 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. This is applicable for Exchange 2007 and Incremental backups include only the data that has changed since the last backup. This is applicable for Exchange Configuring Exchange backup schedule on page 120 provides more information. 4. Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. 5. Configure a client group The Group resource is created so that the client resource can be added to the required group. The main requirement when configuring the Group resource is that the Snapshot checkbox must be selected. You can also select the snapshot policy manually. For backups in an Exchange CCR environment, ensure that the virtual and physical clients are placed on different NetWorker group resources. 6. Configuring Exchange client resource on page 121 This task is specific to configuring a Exchange client resource. Ensure that: Once you have started a snapshot of a save group, do not interrupt or halt the snapshot process. For example, in Exchange 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 save group in NetWorker Management Console will take a long time to complete. When performing a backup of Microsoft Exchange, specify the same directory location (such as E:\) for both the system path and the transaction log under the Storage Group properties in Microsoft Exchange System Manager. When performing a backup of Microsoft Exchange, the database and log files are on different paths. Performing Exchange server backups 119

120 Microsoft Exchange Server Backup and Recovery Configuring Exchange backup schedule In addition to the content on scheduling a backup in the EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide and Backup levels on page 102, review the content in this section. Scheduling backups with more than 10 Exchange storage groups Note: It is recommended that no more than 10 Exchange storage groups be configured for scheduled backs. Use the application variable. To schedule backups for Exchange configurations with more than 10 Microsoft Exchange storage groups: 1. Complete the backup configuration that matches your configuration scenario according to the details provided in Exchange backup scenarios on page Break the Exchange storage groups into sets of 10: Consider the size of each storage group and the time it takes to back up each set. Try to ensure that the size of the data for each set of 10 is roughly the same. This will ensure predicable backup windows. 3. For the client configuration created in step 1: a. Create one additional copy of the client for each set of the 10 Exchange storage groups to back up all the sets. For example, if you have 30 storage groups, create two additional copies of the client. b. If you have configured a deduplication backup for the passive node, also make a copy of the Exchange Virtual server client that was created as part of this configuration. 4. For the original client created: a. Modify the saveset list to list the first 10 Exchange storage groups that you want to back up: b. If you have configured a deduplication backup for the passive node, also modify the Exchange virtual server client resource that was created as part of this configuration. By doing so, you set the saveset list to list the first 10 Exchange storage groups that you want to back up. 5. For each subsequent set of 10, repeat step 4 for the copy of the client resource created. 6. For the group configuration created in step 1: a. Create one additional copy of the group, without copying clients, for each set of 10 Exchange storage groups to back up all the sets. For example, if you have 30 storage groups, create two additional copies of the group. b. For the new groups, set the autostart to disabled. 7. For the clients created in step 3: a. Add one client to the group that you have just created. b. If you have configured a deduplication backup for the passive node, also add the Exchange virtual server client resource with the same saveset listing as the client that you just added to the same group. 8. Repeat step 6 and step 7 for each remaining set of 10 clients. 120 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

121 Microsoft Exchange Server Backup and Recovery 9. Multiple NetWorker groups cannot run at the same time on the same client for NMM, so ensure that you schedule the groups to run correctly. For example, you can schedule the groups to run as follows: a. Schedule the first group on the first night to see how long it takes. b. Add the second group to the schedule for the second night. c. Assign the group a start time based on the run time of the first group from the night before. d. Repeat the process until all groups are scheduled. Configuring Exchange 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. Ensure that: For Exchange SCC backups, client resources are created for the virtual client and all the cluster nodes, which are part of the cluster. But the backups are always done by using the virtual client resource. For Exchange CCR backups, client resources are created for the virtual client and all the cluster nodes, which are part of the cluster. Both active and passive node backups use separate Group resources in the NetWorker server for backup. For Exchange Cluster CCR active node backups, three client resources are created. One for each physical nodes and one for the Exchange virtual server. This takes care of failover, if any. Table 28 on page 121 lists the different procedures of backup for Exchange stand-alone, LCR, SCC, and CCR backups. Create an Exchange group resource and an Exchange client resource for each. Table 28 Different backup procedures for Exchange recovery Exchange client resource Exchange client resources for stand-alone, LCR, or SCC An Exchange client resource can be specified to perform a full backup, or back up a storage group. Details Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122 provides the steps for configuring standard Exchange client resources for stand-alone, LCR, or SCC. Note: For Exchange SCC backups, ensure that a client resource is created for the virtual client because the backups are always done by using the virtual client resource. Performing Exchange server backups 121

122 Microsoft Exchange Server Backup and Recovery Table 28 Different backup procedures for Exchange recovery Exchange client resource An Exchange client resource can be configured for an Exchange CCR. Details The steps vary depending on whether the node is the active node or passive node, and whether a data mover is used: Configuring backup for an Exchange CCR active node or passive node on page 124 Configuring backup for an Exchange CCR active node with a Data Mover on page 126 Configuring backup for an Exchange CCR passive node with a Data Mover on page 126 Note: For all Exchange cluster backups, ensure that client resources are created for the virtual client and all the cluster nodes, which are part of the cluster. Both active and passive node backups use separate Group resources in the NetWorker server for backup. An Exchange client resource can also be configured to use deduplication. Configuring deduplication backups in a CCR environment for a passive node on page 127 provides additional steps for creating an Exchange client resource for deduplication backups in a CCR environment. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides in-depth information about deduplication. Configuring a client resource for Exchange stand-alone, LCR, or SCC backups To create a client resource for Exchange stand-alone, LCR, or SCC backups: 1. In the Administration window 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 either of the following: The fully qualified domain name (FQDN) of the NetWorker client computer. or 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 the rolled-over data is available for quick access. Ensure that the browse policy is long enough for your expected recovery needs. If your recovery needs are beyond the browse policy, an index recovery can be performed and should be the preferred first step. If index recovery is not possible, you can scan tapes to rebuild the index but this should be the last option. 7. From the Retention Policy attribute, select a retention policy from the list. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details about the retention policy for Exchange. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute: 122 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

123 Microsoft Exchange Server Backup and Recovery a. Specify the components to be backed up. b. Place multiple entries on separate lines by using the save set names in Table 24 on page If required, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource. Table 26 on page 117 provides the URL-encoded values for Exchange save sets that are used to represent special characters, such as the backslash (\) and a table of values: 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 when naming Exchange storage groups. For example, a storage group is named: Accounting\Bellevue This storage group would be represented in the Save Set attribute as: APPLICATIONS:\Microsoft Exchange 2007\Accounting%5CBellevue 11. For the Group attribute, select the backup group to which this client resource will be added. Note: The backup group must be a snapshot group. 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. 12. For the Schedule attribute, select a backup schedule. 13. Click the Apps & Modules tab. 14. In the Access area, leave the Remote user and Password fields empty. 15. 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 16. In the Application information attribute: a. Type the following variable and value: NSR_SNAP_TYPE=vss NSR_ALT_PATH=<mount_path_on_local_host> b. Type Exchange application variable settings and their values on separate lines. Table 24 on page 113 describes these settings. c. Create the directory path, for example C:\mount_dir on the client machine before specifying: NSR_ALT_PATH=C:\mount_dir 17. Click the Globals (1 of 2) tab. Performing Exchange server backups 123

124 Microsoft Exchange Server Backup and Recovery 18. Verify that the Aliases attribute displays the NETBIOS name for the client. This name should have already been filled in automatically. Note: 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. 19. Click OK. Configuring backup for an Exchange CCR active node or passive node When backing up Exchange from the active or passive node in the Exchange CCR environment, you must create two client nodes and one virtual client to take care of failover scenarios. Review the following configurations to ensure that failover scenarios are taken care of: Scenario 1: Perform backup from passive node To perform backup from a passive node, you must configure three client resources: Client for physical node 1 (NSR_INDEX_CLIENT and NSR_VIRT_SERV are required) Client for physical node 2 (NSR_INDEX_CLIENT and NSR_VIRT_SERV are required) Client for virtual node (NSR_INDEX_CLIENT and NSR_VIRT_SERV not required) Scenario 2: Perform backup from active node To perform backup from a active node, you must configure three client resources: Client for Physical Node 1 (NSR_INDEX_CLIENT and NSR_VIRT_SERV are not required) Client for Physical Node 2 (NSR_INDEX_CLIENT and NSR_VIRT_SERV are not required) Client for Virtual Node (NSR_INDEX_CLIENT and NSR_VIRT_SERV are not required) In both the above scenarios, configuring all three client resources takes care of failover scenario, because NetWorker needs all the client resources the backup is being performed on. The steps for creating a Exchange client resource if the backup is performed from an Exchange CCR active or passive node are similar to that of Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122. However, the steps for two attributes, the Name attribute and Application information attribute, are different and are described in this section. To create an Exchange client resource if backup is performed from an Exchange CCR active or passive node: 1. Perform step 1through step 3 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page In the Name attribute, create client resources for the virtual server and all physical machines, which are part of CCR environment. For example: For active node: 124 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

125 Microsoft Exchange Server Backup and Recovery Type <Exchange Virtual Server hostname>. For passive node: Create a client resource for the Exchange virtual server. Type <Exchange Virtual Server hostname>. Create a client resource for each physical machine of the CCR environment. Type <physical machine hostname>.! IMPORTANT In CCR backup of passive node through Exchange, the virtual client should be added to the same group as the passive client. 3. Perform step 5 through step 15 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page In the Application information attribute: For active node: a. Type the following variables and values: NSR_SNAP_TYPE=vss NSR_ALT_PATH=<mount_path_on_local_host> b. Type Exchange application variable settings and their values on separate lines. For passive node: These steps should be performed for both the physical nodes as it will cover a failover situation. However, only the current passive node should be enabled for backups. a. Type the following variables and values: NSR_SNAP_TYPE=vss NSR_ALT_PATH=<mount_path_on_local_host> b. For a passive node client resource, but not the virtual server resource, also specify the following: NSR_VIRT_SERV=<Exchange_Virtual_Server_hostname> NSR_INDEX_CLIENT=<Exchange_Virtual_Server_hostname> Note: Ensure that you type Exchange application variable settings and their values on separate lines. Table 24 on page 113 lists the variables that can be specified in the Application information attribute of the client resource. 5. Perform step 17 through step 19 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122. Performing Exchange server backups 125

126 Microsoft Exchange Server Backup and Recovery Configuring backup for an Exchange CCR active node with a Data Mover The procedure for creating an Exchange client resource if the backup is performed from an Exchange CCR active node with a Data Mover is similar to that of Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122. However, the step for the Application information attribute is different and is described below. To create an Exchange client resource if the backup is performed from an Exchange CCR active node with a Data Mover: 1. Perform step 1 through step 15 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page In the Application information attribute: a. Type the following variables and values: NSR_SNAP_TYPE=vss NSR_ALT_PATH=<mount_path_on_proxy_client> NSR_DATA_MOVER=<proxy_client_hostname> NSR_DM_PORT=6728 Note: The default value in NMM installation is b. If you changed the DM Port number to a different value in your NMM client configuration or installation: Use that value for NSR_DM_PORT. Type Exchange application variable settings and their values on separate lines. Table 24 on page 113 describes these settings. 3. Perform step 17 through step 19 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122. Configuring backup for an Exchange CCR passive node with a Data Mover The procedure for creating an Exchange client resource if the backup is performed from an Exchange CCR passive node with a Data Mover is the same as Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122. However, the step for the Name attribute is different and is described below. To create an Exchange client resource if the backup is performed from an Exchange CCR passive node with a Data Mover: 1. Perform step 1 through step 3 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page In the Name attribute, create two client resources: a. Create a client resource for the Exchange virtual server. Type <Exchange Virtual Server hostname> No other configuration is needed. b. Create a client resource for the passive node of the CCR environment. Type <passive node client> 126 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

127 Microsoft Exchange Server Backup and Recovery! IMPORTANT The remaining steps are performed for the client resource for the passive node of the CCR environment. 3. Perform step 5 through step 19 as in Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on page 122. Configuring deduplication backups in a CCR environment for a passive node Before performing these steps, ensure that you have: The correct save set list, application information, and backup command of the passive node client resource. Enabled for deduplication by selecting the deduplication server under Apps & Modules from the passive node client properties. IMPORTANT These steps must be performed in addition to the steps specified in Configuring backup for an Exchange CCR active node or passive node on page 124 for passive node backup with deduplication. To perform deduplication backup of a passive node in a CCR environment: 1. In the server s Administration interface, click Configuration. 2. Select Clients in the navigation tree. The clients table appears. It lists any deduplication clients that have already been created. 3. Right-click Clients in the navigation tree, or right-click any client in the Clients table, and select New. The General tab appears in the Create Client window. 4. On the General tab, specify Exchange virtual name as client name, with the following exceptions: a. Clear the Scheduled backup checkbox. b. In the Save set list, add the same save set list that is in the passive node Client resource. 5. Click the Apps & Modules tab: a. In the Access area, leave the Remote user and Password fields empty. b. In the De-duplication area, select the De-duplication backup attribute to enable this client for deduplication backups. c. Select the name of the deduplication node to which this client s backup data will be sent. This should be the same deduplication node specified for the passive node. 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 performed must be a level 0 (full) backup. 6. Add the new virtual client resource to the backup group that contains the passive node client resource. Performing Exchange server backups 127

128 Microsoft Exchange Server Backup and Recovery Configuring proxy node or proxy storage node backup with the CLARiiON hardware provider The minimum configurations for proxy node backup and proxy storage node backup with the EMC CLARiiON hardware provider are the same. Perform the following configuration steps: 1. Ensure that the proxy node host and the production host have LUNs from the same CLARiiON box. 2. Ensure that the NMM client is installed on both production and Data Mover hosts. 3. The following software must be installed on both the production and proxy hosts: EMC PowerPath with a license EMC Solution Enabler with the symapi_licenses.dat file copied in C:\ProgramFiles\EMC\symapi\config NaviAgent Note: The version of the NaviAgent must match that of FLARE on the CLARiiON. NaviCli Note: When installing NaviCLi, you are prompted to provide the CLARiiON credentials. Ensure that you provide the correct CLARiiON login details. Admsnap 4. Run the following commands on the production host: a. Run this command: C:\Program Files\EMC\SYMCLI\bin> symcfg authorization add -host <CLARiiON IP> -user <CLARiiON Username> -password <CLARiiON Password> For example: symcfg authorization add -host user powersnap -password password symcfg authorization add -host user powersnap -password password b. Add both the IPs of CLARiiON. c. Run this command: C:\Program Files\EMC\Navisphere CLI>NaviSECCli -user <Username> -Scope 0 -address <CLARiiON IP> -AddUserSecurity For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity d. After running this command, you are prompted for a password. Ensure to use the CLARiiON password. e. Add the second IP of CLARiiON and provide the password again. For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity 128 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

129 Microsoft Exchange Server Backup and Recovery 5. Run the following commands on the proxy host: a. Run this command: C:\Program Files\EMC\SYMCLI\bin> symcfg authorization add -host <CLARiiON IP> -user <CLARiiON Username> -password <CLARiiON Password> For example: symcfg authorization add -host user powersnap -password password symcfg authorization add -host user powersnap -password password b. Add both the IPs of CLARiiON. c. Run this command: C:\Program Files\EMC\Navisphere CLI>NaviSECCli -user <Username> -Scope 0 -address <CLARiiON IP> -AddUserSecurity For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity d. After running this command, you are prompted for a password. Ensure to use the CLARiiON password. e. Add the second IP of CLARiiON and provide the password again. For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity 6. For the production host: a. Add the NaviSECCli.exe entry under environmental variables: For example: C:\ProgramFiles (X86)\EMC\Navisphere CLI\NaviSECCli.exe b. Reboot the production host. 7. For the proxy host: a. Add the NaviSECCli.exe entry under environmental variables: For example: C:\ProgramFiles (X86)\EMC\Navisphere CLI\NaviSECCli.exe b. Reboot the proxy host. 8. Perform the following NetWorker server side configuration for proxy backup: a. Create a proxy client resource on the NetWorker server side. b. After creating both the production and proxy client resources, add the following information on both production client resource and proxy client resource properties: Select Production Client Resource properties > Globals(2 of 2) > Remote Access > SYSTEM@proxy host name Performing Exchange server backups 129

130 Microsoft Exchange Server Backup and Recovery Select Proxy Client Resource properties > Globals(2 of 2) > Remote Access > host name c. Specify the following Exchange application information on production client resource to perform proxy backup. The attributes are: NSR_SNAP_TYPE=vss NSR_DM_PORT=6728 [this value is default] NSR_DATA_MOVER=<Proxy host name> NSR_ALT_PATH=<temporary path> [specify the path here, for example C:\mount] The EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Release 2.3 Technical Notes provides more information on this topic. Configuring proxy node or proxy storage node backups with the EMC Symmetrix hardware provider The minimum configurations for proxy node backup and proxy storage node backup with the Symmetrix hardware provider are the same. Perform the following configuration steps: 1. Ensure that the proxy storage node host and the production host have LUNs from the same Symmetrix box. 2. Ensure that the NMM client is installed on both production and Data Mover hosts. 3. The following software must be installed on both the production and proxy hosts: EMC PowerPath with a license EMC Solution Enabler with the symapi_licenses.dat file copied in C:\ProgramFiles\EMC\symapi\config. 4. Create a device and attach both of the following to that device: Business continuance volume (BCV) Standard EMC Disk (STD) 5. After attaching both STD and BCV, establish the connection between STD and BCV. 6. Perform the following NetWorker server side configuration for proxy backup: a. Create a proxy client resource on the NetWorker server side. b. After creating both the production and proxy client resources, add following information on both production client resource and proxy client resource properties: Select Production Client Resource properties > Globals(2 of 2) > Remote Access > SYSTEM@proxy host name Select Proxy Client Resource properties > Globals(2 of 2) > Remote Access > SYSTEM@production host name 130 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

131 Microsoft Exchange Server Backup and Recovery c. Specify the following Exchange application information on production client resource to perform proxy backup. The attributes are: NSR_SNAP_TYPE=vss NSR_DM_PORT=6728 [this value is default] NSR_DATA_MOVER=<Proxy host name> NSR_ALT_PATH=<temporary path> [specify path here, for example C:\mount] 7. The EMC NetWorker Module for Microsoft Applications and EMC Symmetrix: Implementing Proxy Node Backups Release 2.3 Technical Notes provides more information on this topic. Performing Exchange server recovery This section provides information on: Exchange recovery requirements on page 131 Exchange recovery limitations on page 160 Configuring Exchange recovery on page 133 Note: Backups can be performed from both the CCR active node and the CCR passive node. However, recoveries cannot be done from the CCR passive node. IMPORTANT Perform a full level backup after every restore performed in Exchange Exchange recovery requirements The following requirements must be met before recovering Microsoft Exchange data: The writer set or storage group save set must have been backed up: For Exchange server 2003 writer: APPLICATIONS:\Microsoft Exchange Writer For Exchange server 2007 writer: APPLICATIONS:\Microsoft Exchange 2007 For Exchange server 2003 storage group: APPLICATIONS:\Microsoft Exchange Writer\first_group For Exchange server 2007 storage group: APPLICATIONS:\Microsoft Exchange 2007\second_group The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about backups. For each Exchange database to be recovered, you must select the following: For Exchange server 2003: The Exchange checkbox titled This database can be overwritten by a restore must be selected in the Exchange System Manager () Performing Exchange server recovery 131

132 Microsoft Exchange Server Backup and Recovery Exchange server 2007: The Exchange checkbox titled This database can be overwritten by a restore must be selected in the Exchange Management Console This is a Microsoft requirement. The Microsoft Exchange documentation provides more information about this checkbox. When new Microsoft service packs for Exchange server are installed, transactions (log files) created with previous service pack versions of Exchange server generally cannot be recovered onto the updated Exchange server. Microsoft sometimes provides hotfix kits to address this Microsoft restriction. Note: It is recommended that you perform a full backup after any Exchange server software upgrade. If you are recovering Exchange data that was backed up from a legacy NetWorker client by using the save set VSS USER DATA:\ in an NMM File System Recovery Session: a. The Exchange databases to which data is being recovered must be unmounted before the recovery operation. b. After the recovery, the databases must be mounted. Exchange recovery options To specify recovery options for Exchange data: 1. Open the NMM client GUI. 2. Select the NetWorker Server on which the NMM client software was configured for backup. 3. 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. 4. From the left pane, select Exchange Recover Session, and then select one of the following: Database Recover (default) to view Exchange database backups. RSG Mailbox Recover to browse and recover items from existing RSG databases. 5. In the Exchange Server Session toolbar, click Recover Options. 6. Select the type of recovery to perform: To recover data for Exchange server 2003 or 2007 and retain all existing Exchange transactions that occurred after the time of backup, select Include existing logs (Roll forward recovery). Roll-forward recovery on page 110 describes this type of recovery in detail. To recover data for Exchange server 2003 or 2007 up to the time of backup only and to not include subsequent transactions, select Include logs only from this restore (Point-in-time recovery). Note: If you select point-in-time recovery, you cannot select an individual database for recovery. However, you can select to recover items at the storage group level or later. Point-in-time recovery on page 110 describes this type of recovery in detail. 132 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

133 Microsoft Exchange Server Backup and Recovery 7. To make the Exchange database available after the recovery, select Put databases online after restore. 8. Click OK to close the Exchange Recover Options dialog box. 9. From the navigation tree, expand the Applications folder and the appropriate Microsoft Exchange writer folder: Microsoft Exchange Writer for Microsoft Exchange server 2003 Microsoft Exchange 2007 for Microsoft Exchange server Select the Exchange storage groups and databases that are to be recovered. 11. From the Exchange Recover toolbar, click Start Restore. Configuring Exchange recovery This section provides the procedures required for the various recovery scenarios: Configurations for traditional recovery from disk, tape, and VTL on page 133 Configurations for roll-forward recovery on page 134 Configurations for point-in-time recovery of an Exchange 2007 on page 135 Configurations for rollback recovery of an Exchange 2007 on page 136 Configurations for recovery to storage group on page 137 Configurations for traditional recovery from disk, tape, and VTL To configure for traditional recovery: 1. In the NMM GUI, in the Exchange Recovery Options window, click the NetWorker tab, as shown in Figure 20 on page 133. Figure 20 Exchange Recovery Options window with Conventional Restore option selected Performing Exchange server recovery 133

134 Microsoft Exchange Server Backup and Recovery 2. By default, the Conventional Restore option is selected. 3. Click OK. Configurations for roll-forward recovery To perform a roll-forward recovery of an Exchange server 2007 in a CCR environment: IMPORTANT Perform the recovery from the active node. 1. In the Exchange Management Console application, select the This database can be overwritten by a restore checkbox. 2. In the Exchange Management shell, stop replication to the passive node with the suspend-storagegroupcopy command. For example: Suspend-StorageGroupCopy -Identity "bv-hood-cluse12\first Storage Group" 3. Open the NMM client. 4. In the main toolbar, select the Client menu, and then select the client that is the Exchange virtual server. 5. From the left pane, select Exchange Recover, and then select one of the following: Database Recover (default) To view Exchange database backups. RSG Recover To browse and recover items from existing RSG databases. 6. In Transaction Log File Replay window, ensure that Include existing logs (Roll-forward recovery) is selected. This is the default setting, but it may have been changed if the previous recovery was a point-in-time recovery. 7. From the navigation tree, expand the Applications folder and select the Microsoft Exchange 2007 folder. 8. Select the Exchange server items that you want to restore. 9. From the Exchange Recover Session toolbar, click Recover. The Exchange Recovery Options Summary dialog box appears. 10. Review the options: If you need to change the options, click Recover Options. This opens the NetWorker Recovery Options dialog box, where you can change settings on the General, NetWorker, Security, and Exchange tabs. If the options are okay, click the Start Recover button. This closes the Exchange Recovery Options dialog box, and starts the recovery. 11. Restore replication between the nodes with the resume-storagegroupcopy command. For example: resume-storagegroupcopy -Identity "bv-hood-cluse12\first Storage Group 134 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

135 Microsoft Exchange Server Backup and Recovery IMPORTANT Perform a full backup after performing roll-forward recovery. Configurations for point-in-time recovery of an Exchange 2007 To perform a point-in-time recovery of an Exchange server 2007 in a CCR environment: IMPORTANT Perform the recovery from the active node. Failing over the passive node to the active node if necessary. 1. In the Exchange Management Console application, select the This database can be overwritten by a restore checkbox. 2. In the Exchange command shell, stop replication to the passive node with the suspend-storagegroupcopy command. For example: suspend-storagegroupcopy -Identity "bv-hood-cluse12\first Storage Group" 3. Open the NMM client. 4. In the main toolbar: a. Select the Client menu. b. Select the client that is the Exchange virtual server. 5. From the left pane, select Exchange Recover, and then select one of the following: Database Recover (default) To view Exchange database backups. RSG Recover To browse and recover items from existing RSG databases. 6. In Transaction Log File Replay window, select Include only logs from this restore (Point-in-time recovery). 7. From the navigation tree, expand the Applications folder and select the Microsoft Exchange 2007 folder. 8. Select the Exchange server items that you want to restore. 9. From the Exchange Recover Session toolbar, click Start Restore. 10. After restore, on the passive node manually delete log files and database file. 11. On the passive node, in the Exchange command shell, re-seed the passive node with the Update-StorageGroupCopy command. For example: Update-StorageGroupCopy -Identity "bv-hood-cluse12\first Storage Group" 12. Restore replication between the nodes with the resume-storagegroupcopy command. For example: resume-storagegroupcopy -Identity "bv-hood-cluse12\first Storage Group Performing Exchange server recovery 135

136 Microsoft Exchange Server Backup and Recovery IMPORTANT Perform a full backup after performing point-in-time recovery. Configurations for rollback recovery of an Exchange 2007 Note: Ensure that the current Exchange active node is the node where the files existed at save time. Failover the virtual Exchange server to the passive node where the backup was taken, if necessary. Use the following settings when performing rollover recovery for and the Exchange server: The Exchange server 2007 recovery type is Point-in-time. Browse and select the items for recovery from the client type Exchange Virtual Server. To perform a rollback recovery of an Exchange server 2007 in a CCR environment: 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. If you are performing a rollback for EMC Symmetrix configurations that use RAID5 BCVs, perform the following steps: a. Delete all snapshots for the STD, except for the snapshot to be rolled back. 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. 5. In the navigation tree, select the snapshot to be rolled back. 6. Right-click the selected snapshot and select Rollback. 7. In the left pane, select Monitor to view the progress of the rollback operation. When rollback processing has completed, reboot the host to complete the rollback operation. Mounting the database after recovery Certain pre- and post-restore operations that are provided for Exchange enable quick access to after recovery. Until Exchange databases are remounted, is not available for users to browse and verify. NMM provides options to automatically mount Exchange databases after restore. 136 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

137 Microsoft Exchange Server Backup and Recovery The Exchange administrator can decide if a restore of a particular Exchange database is required and if an automatic mounting of the database must be done after the restore is complete: If this option is specified, then the database is mounted after the successful restore of the Exchange server. If this option is disabled, then the administrator must manually mount the database. By default, this option is enabled in NMM. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide describes how to select or disable automatic mounting option. Configurations for recovery to storage group This section provides the procedures for recovery to storage groups, depending on the restore location: Recovery to the original storage group on page 137 Recovery to an Exchange RSG on page 138 Setting Exchange server 2007 permissions to enable NMM browsing of RSG mailboxes on page 142 Additional requirements for browsing RSG mailboxes on page 142 Selecting and recovering items in the RSG database on page 143 Selecting an item for recovery on page 143 Searching for an item on page 144 Recovering selected items on page 145 Recovery to the original storage group By default, recovery to the original storage group overwrites all of the current content of the selected databases in the storage group. To recover to the original storage group: 1. Open the NMM client GUI. 2. Select the NetWorker Server on which the NMM client software was configured for backup. 3. 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 menu in the application toolbar. 4. From the left pane, select Exchange Recover, and then select Database Recover. 5. In the navigation tree, expand the Exchange server that you want to recover from. NMM displays the contents of the storage groups that have been backed up. 6. Right-click the storage group that you want to recover, and then click Restore To. 7. In the Select Storage Group Restore Destination dialog box: a. Verify that Original Storage Group is selected. b. Click OK. 8. Click Start Recover. After the restore, the administrator may need to mount the databases if the option to put databases online was not automatically selected. Performing Exchange server recovery 137

138 Microsoft Exchange Server Backup and Recovery Recovery to an Exchange RSG NMM does not back up the contents of an RSG. The RSG is used only as a location for restoring backups from normal storage groups. There are two parts to the recovery process: Creating an RSG and adding target databases on page 138 Recovering to the RSG on page 139 Setting a different Exchange server for recovery on page 142 Creating an alternate storage group and adding target databases on page 145 Creating an RSG and adding target databases Before NMM can restore to an RSG, an RSG must be created and linked to a storage group. Microsoft Exchange server 2007 supports only one RSG at a time per server. IMPORTANT When you use the restore to an RSG feature, always delete the existing RSG and then create a new clean RSG. If you are performing a directed recovery, delete the existing RSG on the original server as well as the RSG on the destination server. The following methods are available within Microsoft Exchange to configure an RSG database: Use the Exchange Management Console Database Recovery Management tool for one storage group mailbox. Use the Exchange Management Shell for more than one storage group mailbox. To configure an RSG with Exchange Management Shell: 1. On the Microsoft Exchange server, select the Start menu and then select Exchange Management Shell. 2. Use the new-storage group command to create the Recovery Storage Group: new-storagegroup server exch_server name rsg_name LogFolderPath rsg_path SystemFolderPath rsg_path Recovery where: exch_server is the Exchange 2007 server name. rsg_name is the RSG name that you want to create. rsg_path is the path to the RSG directory. The Recovery option is also required to specify that an RSG is created. For example: new-storagegroup server bv-rmx64-1 name SG2_RSG LogFolderPath T:\exchsrvr\SG2\SG2_RSG SystemFolderPath T:\exchsrvr\SG2\SG2_RSG Recovery 3. Use the new-mailboxdatabase command to add target databases to the RSG: new-mailboxdatabase -Name db_name -MailboxDatabaseToRecover db_name -StorageGroup exch_server\rsg_name -EdbFilePath rsg_edb_path where: db_name is the name of the database that will be recovered. 138 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

139 Microsoft Exchange Server Backup and Recovery -EdbFilePath is the path of the database in the RSG, not the original storage group. edb_path is the path to the database file in the RSG directory. 4. Use the same name for the RSG database as the original database to avoid confusion. For example: new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1 -StorageGroup bv-rmx64-1\sg2_rsg -EdbFilePath U:\exchsrvr\SG2\SG2_RSG\DB1.edb 5. Repeat the new-mailboxdatabase for each database that will be recovered. Note: You must specify the correct database name and edb path. 6. NMM allows the administrator to leave the database offline or have it automatically put online after the restore: If you choose to leave the database offline after the restore, it must be manually mounted. This can be done with the mount-database command: mount-database Identity exch_server\sg_name\db_name For example: mount-database Identity bv-rmx64-1\sg2_rsg\db1 Databases can be dismounted with the dismount-database command: dismount-database Identity exch_server\sg_name\db_name For example: dismount-database Identity bv-rmx64-1\sg2_rsg\db1 7. To repeat an RSG restore by using the same database after it has been mounted, set the database can be overwritten property: set-mailboxdatabase Identity exch_server\rsg_name\db_name AllowFileRestore:$true For example: set-mailboxdatabase Identity bv-rmx64-1\rsg\db1 AllowFileRestore:$true Recovering to the RSG When an RSG has been created and linked to a storage group, it is enabled in NMM and can be selected as a restore destination. After databases have been recovered to the RSG, NMM can perform item-level recovery for folders or individual items. IMPORTANT When you use the restore to an RSG feature, always delete the existing RSG and then create a new clean RSG. Right-click the RSG and select Delete RSG. To recover to an RSG: 1. Open the NetWorker User GUI. 2. Select the NetWorker Server on which the NMM client software was configured for backup. Performing Exchange server recovery 139

140 Microsoft Exchange Server Backup and Recovery 3. 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 menu in the application toolbar. 4. From the left pane, select Recover Session > Exchange Recover, and then select Database Recover. This displays the available Exchange database backups. 5. In the navigation tree, expand the Exchange server that you want to recover from. NMM displays the contents of the storage groups that have been backed up. Figure 21 on page 140 shows the SG2 storage group has been selected, so the First storage group and Public_SG are unavailable and cannot be selected. This prevents simultaneous restore of one storage group to the RSG and another storage group to the original location. Figure 21 Available and unavailable storage groups 6. Right-click the storage group that is linked to the RSG. Figure 22 on page 140 shows the context menu with the Restore To command available. Figure 22 Restore To command on context menu 7. Select Restore To, and then select RSG Configuration. This verifies that all RSG databases exist and can be overwritten. It checks all databases, in case the administrator marks the entire storage group. If an error message like the one in Figure 23 on page 141 appears, there is a configuration problem. The configuration problem must be fixed before the database with the configuration problem can be restored. Then the restore operation can be started. 140 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

141 Microsoft Exchange Server Backup and Recovery In the example shown in Figure 23 on page 141, DB1 and DB2 could be restored, but DB3 cannot until the configuration problem is fixed. Figure 23 RSG Configuration error message When a message like the one in Figure 24 on page 141 appears, the RSG configuration is correct. Figure 24 RSG Configuration correct message 8. RSG configuration is also checked when a restore is started, but only marked databases are checked. If a configuration problem is detected, NMM stops the restore operation. 9. Select the storage group linked to the RSG that you want to recover. You can also select individual mailbox databases in that storage group. Only one storage group can be selected when Restore to RSG is enabled. 10. Click Start Recover. When Restore to RSG is enabled, Public Folders cannot be selected because Exchange server 2007 does not support restoring a public folder to the RSG. Figure 25 on page 141 shows the entire SG2 storage group cannot be selected. Only the Mailbox Database is selectable. Figure 25 Public folders cannot be recovered to an RSG 11. After the restore, the administrator may need to mount the databases if the option to put databases online was automatically selected. Performing Exchange server recovery 141

142 Microsoft Exchange Server Backup and Recovery Setting a different Exchange server for recovery NMM supports restoring to an RSG in a cluster environment. When an Exchange server is set up in a cluster, and there are multiple active Exchange servers, you can select the RSG that you want to use for an Exchange recover session. To select an active Exchange server RSG: 1. Open the NMM client GUI. 2. Select the NetWorker Server on which the NMM client software was configured for backup. 3. On the browse tab, right-click the Exchange server, and then click Change Exchange Server. The Change Exchange Server dialog box appears. Note: If the Exchange server is a stand-alone installation, this menu item will be unavailable. 4. In Available Exchange Servers, click the server that you want to browse, and then click OK. The browse tree is displayed with the RSG that is associated with the selected Exchange server. Setting Exchange server 2007 permissions to enable NMM browsing of RSG mailboxes An Exchange administrator must configure Exchange server 2007 to enable browsing of an RSG mailbox. An error message dialog box displays stating that NMM is unable to browse mailboxes because the required permission is not configured correctly. This message appears if the following two conditions are met: If the Send-As and Receive-As permissions are not correctly configured Browsing the RSG is attempted To configure permissions for browsing an RSG mailbox: 1. On the Microsoft Exchange server, select Start > All Programs > Exchange Management Shell. 2. Enable Send-As and Receive-As permissions. For example: get-exchangeserver <Exchange Server name> Add-AdPermission -user <username> -extendedrights Receive-As, Send-As where: <Exchange Server name> is the server where the RSG mailbox is located. <username> is the name of the user being granted permissions. Additional requirements for browsing RSG mailboxes There are other requirements for browsing RSG mailboxes: An RSG must exist. The RSG must contain one or more databases. Databases must be online. NMM does not display mailboxes in offline databases. 142 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

143 Microsoft Exchange Server Backup and Recovery The MAPI/CDO kit must be installed: Access to Exchange messaging stores used by the NMM mailbox backups require the Messaging API (MAPI) and Collaboration Data Objects (CDO) kit. Note: The MAPI client libraries and CDO are not included with Exchange server The package with these objects can be downloaded from the Microsoft website: This package is also required for RSG support in Exchange server Download version or later. For information on downloading and installing this package, search for Microsoft Exchange Server MAPI Client and Collaboration Data Objects on the Microsoft Download Center website. IPV6 must be disabled on Windows server 2008 and Windows server 2008 R2. Exchange System Attendant and Information Store services must be running. One public folder database should exist in the Exchange domain. Selecting and recovering items in the RSG database Once the databases have been recovered to an RSG, you can browse the user mailboxes, folders, and messages, in the navigation tree, and then select which items to recover to the user mailboxes. You can also search for items in the navigation tree through the Search tab. Selecting an item for recovery Items can be selected for recovery at the storage group, mailbox, mail folder, and mail message level: To select items for recovery, select the checkbox beside a node in the navigation tree. A check mark indicates that the node is selected. To clear an item contained in a selected node, expand the node and select the checkbox beside the item to clear it. The check mark disappears. When you select a node, by default, all items contained in the node such as mailboxes, mail folders, and messages, will also be selected for recovery. If all items in the node are selected, the check mark will be green, and the background of the box will be white. To select an item without selecting all items at the same level, expand down to the level that you want, without selecting. When you have located the item, select the checkbox for the item. The containers above that item are automatically partially selected. For example, if Figure 26 on page 144 the mail message Is everybody online? is selected for recovery, without selecting all the items in the containing mail folder, user mail box, or storage group, a gray check mark in a checkbox with a gray background appears. This indicates that the item is partially selected. When Is everybody online? is selected, the nodes above it are partially selected all the way up to the server. Figure 26 on page 144 depicts one selected mail message and several partially selected nodes in the navigation tree. Performing Exchange server recovery 143

144 Microsoft Exchange Server Backup and Recovery Figure 26 Selected and partially selected items Searching for an item You can also search for a recovery item. Once you have located an item, you can select it for recovery. 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. 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. 144 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

145 Microsoft Exchange Server Backup and Recovery Recovering selected items Once you have completed selecting items through browsing or searching, you can recover the items to the user s mailboxes. To recover the selected items, from the Exchange Recover Session toolbar, click Start Recovery. Note: Recovered items do not overwrite existing items. They are placed in separate folders in the user s mailbox. When NMM performs an RSG item level recovery, the items are placed in a new Recovered Items folder created in the user s mailbox on the production server. Figure 27 on page 145 shows an example of two Recovered Items folders in the mailbox of user Steve M. Figure 27 Recovered Items folders in user mailbox The name of the folder begins with a time and date stamp. An example is 14:35:171 3/13/2009 Recovered Items. A new Recovered Items folder is created for each recovery. This prevents the selected items from overwriting the existing items in the user s mailbox, and allows the user to view and work with existing and recovered items without overwriting either. When the user completes sorting through the recovered items, the user can delete the Recovered Items folder. Recovery to an alternate storage group Recovery to an alternate storage group allows you to recover the storage group data to a different Exchange server from the original source. Creating an alternate storage group and adding target databases Before NMM can restore to an alternate storage group, a new database must be created in the alternate storage group with the same name as the original database. There are three methods available within Microsoft Exchange to configure an alternate storage location database: Exchange Management Shell at the command line, which is the recommended method Exchange Management Console Database Recovery Management tool By using the Select Storage Group Restore Destination dialog box in the NMM GUI when performing a recovery to an alternate storage group. To configure an alternate storage group with Exchange Management Shell: 1. On the Microsoft Exchange server: a. Select the Start menu. b. Select Exchange Management Shell. Performing Exchange server recovery 145

146 Microsoft Exchange Server Backup and Recovery 2. Use the new-storage group command to create the alternate storage group: new-storagegroup server exch_server name alt_name LogFolderPath alt_path SystemFolderPath alt_path where: exch_server is the Exchange 2007 server name. alt_name is the required alternate storage group name. alt_path is the path to the alternate storage group directory. For example: new-storagegroup server bv-rmx64-1 name Alternate_SG LogFolderPath T:\exchsrvr\SG2\Alternate_SG SystemFolderPath T:\exchsrvr\SG2\Alternate_SG 3. Use the new-mailboxdatabase command to add target databases to the alternate storage group: new-mailboxdatabase -Name db_name -MailboxDatabaseToRecover db_name -StorageGroup exch_server\alt_name -EdbFilePath edb_path where: db_name is the name of the database that will be recovered. -EdbFilePath is the path of the database in the alternate storage group, not the original storage group. edb_path is the path to the database file in the alternate storage group directory. Note: The alternate storage group database name must match exactly the original database name. For example, the name for the alternate storage group specified in new-mailboxdatabase -Name: is DB1, the same as the name of the original database name specified in MailboxDatabaseToRecover, DB1. new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1 -StorageGroup bv-rmx64-1\alternate_sg -EdbFilePath U:\exchsrvr\SG2\Alterenate_SG\DB1.edb 4. Repeat new-mailboxdatabase command for each database that will be recovered. Ensure to specify the correct database name and edb path. 5. NMM allows the administrator to leave the database offline or have it automatically put online after the restore: If you choose to leave the database offline after the restore. It must be manually mounted. This can be done with the mount-database command: mount-database Identity exch_server\sg_name\db_name For example: mount-database Identity bv-rmx64-1\alternate_sg\db1 Databases can be dismounted with the dismount-database command: dismount-database Identity exch_server\sg_name\db_name 146 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

147 Microsoft Exchange Server Backup and Recovery For example: dismount-database Identity bv-rmx64-1\alternate_sg\db1 6. To repeat an alternate storage group: a. Restore by using the same database after it has been mounted. b. Set the database can be overwritten property: set-mailboxdatabase Identity exch_server\alt_sg_name\db_name AllowFileRestore:$true For example: set-mailboxdatabase Identity bv-rmx64-1\alternate_sg\db1 AllowFileRestore:$true To recover to an alternate storage group: 1. In the Select Storage Group Restore Destination dialog box, select Alternate Storage Group. 2. In the Exchange Server list, select the Exchange server that contains the alternate storage group. 3. If the alternate recovery storage group is not available, then the No Recovery Storage Group exists dialog box appears: a. In the dialog box, click Yes. The Create Exchange 2007 Recovery Storage Group dialog box appears. b. Provide details for the new Recovery Storage Group in this dialog box. c. Click OK. The new Recovery Storage Group is successfully created. 4. In Select Alternate Storage Group select the storage group, and then click OK. 5. Click Start Recover. After the restore, the administrator may need to mount the databases if the option to put databases online was automatically selected. Selecting a storage group restore destination When restoring from a point-in-time backup, files are copied from a snapshot to the specified location. When restoring from a rollover, files are copied from a NetWorker device such as tape, file, or adv_file to the specified location. Selecting a storage group restore destination on page 147 provides details. IMPORTANT When you use the restore to an RSG feature, always delete the existing RSG and then create a new clean RSG. Right-click the RSG and select Delete RSG. NMM provides several options for selecting the target storage group. These options are specified in the Select Storage Group Restore Destination dialog box, which is accessed in the Exchange Recover Session. Figure 28 on page 148 displays the options available in this dialog box. Selecting a storage group restore destination 147

148 Microsoft Exchange Server Backup and Recovery Figure 28 Select Storage Group Restore Destination dialog box The Select Storage Group Restore Destination dialog box provides the following settings and information: <Storage Group Name> Storage Group (Source) This box displays the name of the storage group selected in the Browse tab in the Exchange Recover Session window. Restore To (Destination) This specifies where you want the storage group restored to. Exchange Server By default, this is the server or virtual server where the source storage group is located. You can select a different server here if you are recovering to an RSG or alternate storage group that is not on the source server. Original Storage Group This specifies to restore the content to the original storage group, which will overwrite the content currently in that storage group. Recovery Storage Group This specifies to restore the storage group to a separate RSG that you have already created: Recovering to an RSG allows you to browse and select items to restore without overwriting the entire storage group. When this option is selected, the Check Recovery Storage Group dialog box appears. The Check button is used to verify that the Recovery Storage Group exists and databases are configured properly. Alternate Storage Group This specifies to restore databases to a different storage group. When this option is selected, the Select Alternate Storage Group dialog box provides a menu where you can select from the available storage groups available on the Exchange server listed in the Restore To dialog box. Note: Exchange server 2007 does not support restoring a public folder to the RSG. If a storage group contains a public folder, it cannot be selected. Only the mailboxes within that storage group can be selected. 148 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

149 Microsoft Exchange Server Backup and Recovery The steps to specify which location to restore to are described in the separate procedures for each location type: Recovery to the original storage group on page 137 Recovery to an Exchange RSG on page 138 Recovery to an alternate storage group on page 145 Configurations for recovery to storage group on page 137 provides configuration details. Performing Microsoft Exchange server 2007 directed recovery In the event of a problem recovering to the original Exchange server host, such as disk drive failure, you can perform a directed recovery to recover Exchange data to a different Exchange server. The database portability feature in Microsoft Exchange server 2007 allows a mailbox to be mounted on any server in the same organization. Microsoft TechNet describes this feature in more detail. In the normal NMM backup and recovery process, the backup flows in the following direction: 1. The NMM client is installed on the computer that will be backed up. For example, ExchangeServer1. 2. That NMM client is configured to work with a specific NetWorker server on another computer. For example, NetWorkerServer1. 3. Backups are configured on and performed by the NetWorker server, NetWorker Server1. 4. Recovery is performed through the NMM client UI on the NMM client computer, ExchangeServer1, and recovered to the same NMM client computer. In a directed recovery, the NMM client is also installed on another server, for example Server2. The recovery of ExchangeServer1 is directed from the NMM client on Server2: 1. The NMM client is installed on the computer that will be backed up. For example, ExchangeServer1. 2. The NMM client is also installed on another computer that will direct the recovery. For example, Server2. 3. The NMM client on both machines are configured to work with the same NetWorker server on another computer. For example, NetWorkerServer1. 4. Backups are configured on and performed by the NetWorker server, NetWorker Server1. 5. Recovery of ExchangeServer1 is performed through the NMM client UI on another NMM client computer, Server2, and recovered to another location. Performing Microsoft Exchange server 2007 directed recovery 149

150 Microsoft Exchange Server Backup and Recovery Performing a directed recovery To perform a directed recovery of an Exchange server with NMM: 1. In NetWorker, create a backup of the NMM client, the Exchange server. 2. Run NMM on the machine that will receive the data. 3. Connect to the NetWorker server that hosts the NMM Exchange server client. 4. Add the NMM Exchange server client that created the backup as a locally viewable client. Figure 29 on page 150 shows the default of only one NMM client available, the local client. Figure 29 Local client on the taskbar next to Client 5. On the Options menu, click Configure Options. 6. Click the Refresh button, which is to the right of the Client name. Figure 30 on page 150 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 30 Select Viewable Clients dialog box 7. Click the client to add in the Available clients on menu, and then click Add. Add or remove clients as needed. 8. Click OK. 9. Click the Client list, and select the client that created the Exchange server backup as the current local client. 150 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

151 Microsoft Exchange Server Backup and Recovery 10. If the Snapshot Management or Monitor is the active navigation bar item, and you are prompted with the Navigate Away dialog box, click Yes. 11. On the Exchange Recover Sessions bar, select Recover Options. The Exchange Recover Session Options dialog box appears. 12. Recover remote client's backup to local Exchange server. Performing Microsoft Exchange server 2007 disaster recovery For Microsoft Exchange server 2007 disaster recovery on Windows 2008 and Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery. Chapter 10, Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM provides details. NMM can perform the following types of disaster recovery for Microsoft Exchange server 2007: Performing Microsoft Exchange server 2007 (stand-alone) disaster recovery on page 151 Performing Microsoft Exchange server 2007 disaster recovery for Microsoft Exchange CCR to a two-node cluster in a production environment on page 152 Performing Microsoft Exchange server 2007 disaster recovery for Exchange CCR in a production environment on page 155 Performing Microsoft Exchange server 2007 (stand-alone) disaster recovery The process for performing this disaster recovery follows these steps: 1. The Exchange data must have already been backed up with the save set Applications:\Microsoft Exchange Rebuild the Exchange server hardware, following the instructions provided by Microsoft. 3. After the Exchange server is rebuilt, ensure with the name, account information, and configuration, and other information is the same as the old server that is being replaced. 4. Reinstall NMM. 5. In NMM, perform an Exchange server point-in-time recovery. To perform a disaster recovery of a stand-alone installation of Microsoft Exchange server 2007: 1. Back up all Exchange data with the save set Applications:\Microsoft Exchange Build new machine hardware for an Exchange server, following Microsoft s instructions on TechNet: Moving Exchange Servers to New Hardware and Keeping the Same Server Name 3. Capture all of your manually set Internet Information Services (IIS) virtual directory configurations. Run the following Exchange Management Shell command: Performing Microsoft Exchange server 2007 disaster recovery 151

152 Microsoft Exchange Server Backup and Recovery Get-OwaVirtualDirectory "owa (default web site)" export-clixml Owa.xml - depth 4. Copy the Owa.xml file to a location that can be accessed by the new server after it is available and the old server is shut down. 5. Shut down the existing Exchange 2007 server. (The backup should have already been taken, at step 1 on page 151 of this procedure.) 6. Reset the computer account for the existing Microsoft Exchange 2007 server. 7. Bring the new computer online, and then confirm that the new computer is running the same operating system that was installed on the existing Microsoft Exchange 2007 server. 8. Rename the new server to the same name as the original server that you are replacing, and then join this computer to the domain. 9. For drives that contained Exchange 2007 data, configure drive letters on the new server to map to or match the configuration of the old server. 10. Verify that the drives have sufficient space to accommodate the restored data. 11. Run Exchange server 2007 Setup with the following parameter: Setup.com /M:RecoverServer 12. Reboot the machine. 13. Restore your manually set IIS virtual directory configurations by running the following Exchange Management Shell script: Restorevdir.ps1 Owa.xml Note: The Microsoft Exchange server should come online with all previous storage groups. 14. Install NMM. The EMC Module for Microsoft Applications Release 2.3 Installation Guide provides instructions for installing NMM, including Exchange server-specific configuration settings. 15. In NMM, perform an Exchange server point-in-time recovery. Point-in-time recovery on page 110 describes these recovery steps in detail. Performing Microsoft Exchange server 2007 disaster recovery for Microsoft Exchange CCR to a two-node cluster in a production environment Prior to disaster recovery, use NMM to perform regular backups of volumes, system components, and application save sets. The following save sets should be backed up regularly: 1. Back up the following with the snapshot policy all. C:\ SYSTEM COMPONENTS:\ The backup of C:\ automatically includes the following: Windows Boot Volume Windows System Volume 152 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

153 Microsoft Exchange Server Backup and Recovery Application software Note: If the system has been set up with a separate file system for the Windows boot\system partition and separate file system for application installation, then along with C:\ drive, back up the file system that includes the Windows Boot Volume, Windows System Volume, and application software. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about configuring snapshot policies for SYSTEM COMPONENTS backup. 2. Back up application data for Microsoft Exchange CCR on the NetWorker server on the passive node by using the following save set with snapshot policy all. Applications:\Microsoft Exchange 2007 The steps in this disaster recovery scenario are based on the following host details for the production environment you are recovering, and the isolated environment you are recovering to. Production environment setup Domain Controller, one physical machine CCR setup with an active node and a passive node, two physical machines Isolated environment setup Domain Controller setup with the same hardware and software configuration as the production environment CCR setup with only a passive node, one physical machine To perform a disaster recovery of Microsoft Exchange server 2007 to a two-node cluster in a CCR environment: 1. Configure an AD domain setup in an isolated environment by using the same operating system version, machine IP, and machine name as the production Active Directory Domain setup. Note: There should not be any communication between the production environment and the isolated environment. 2. Configure the AD domain on the isolated environment with the same domain name as the production AD domain name. Ensure that both environments use the same make and model of hardware. 3. Install all Windows updates, and applications such as Exchange, in the isolated environment AD domain setup, to match the production Active Directory Domain setup. 4. Disconnect the NetWorker server from the production environment, and connect the NetWorker server to the isolated environment. Note: In this scenario, the backup was taken on the file system, not on tape. Since the backup is not on tape, to move the backup to the isolated environment you must connect isolated environment to the NetWorker server which is storing the backup. 5. Install NMM on the isolated environment AD domain machine. 6. Restart the machine in Directory Service Restore Mode. Performing Microsoft Exchange server 2007 disaster recovery 153

154 Microsoft Exchange Server Backup and Recovery 7. Use the NMM software to recover C:\ and SYSTEM COMPONENTS:\. Note: Ensure that legato and RMagentPS folders are not selected before starting C:\ recovery. 8. When recovery completes, you will be prompted to restart the machine. Restart the machine. This recovers all production AD domain objects into the isolated AD domain. This also recovers all application information. 9. On the isolated environment AD domain setup, reset the computer account for the existing Exchange virtual server, or Clustered Mailbox Server (CMS), or virtual Exchange server. 10. Rebuild another stand-alone server in the isolated environment with the same operating system version as the production CCR setup. 11. Provide this new machine with a new IP address and new Network name, and bring it online in the isolated environment. 12. Install all roles required for Exchange setup to run. 13. Create the same drive letters and paths for Storage Groups (SG) and databases as the production CCR SGs and databases. 14. Install the cluster feature and configure a new cluster with Quorum. Note: The Majority Node Set (MNS)/Quorum shared folder must be different from the old. 15. Run Exchange setup in Custom mode, and only install the Passive Cluster Role. 16. Run the following command, by using the CMS name and IP address from the Production CCR server: Setup.com /recovercms /CMSName:<name> /CMSIPaddress:<ip> This puts the production virtual server online on this new node. Note: All storage groups that were created in the CCR are recreated in this installation. Verify that all drive letters and paths for storage groups and databases are recreated in the same way as those in the production CCR server. 17. All databases will be in dismounted state, which is required for recovery from NMM. 18. Install NMM on the new CCR machine. 19. Browse through Production CCR EVS index and then perform PIT recovery of Exchange. 20. Install Microsoft Exchange on the new CCR machine: a. Run Exchange setup in Custom mode. b. Install only the Passive Cluster Role. 21. Reseed the passive cluster node to get it in sync with the active node. 154 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

155 Microsoft Exchange Server Backup and Recovery Performing Microsoft Exchange server 2007 disaster recovery for Exchange CCR in a production environment Prior to disaster recovery, use NMM to perform regular backups of volumes, system components, and application save sets. The following save sets should be backed up regularly: 1. Back up the following with the snapshot policy all. C:\ SYSTEM COMPONENTS:\ The backup of C:\ automatically includes the following: Windows Boot Volume Windows System Volume Application software. Note: If the system has been set up with a separate file system for the Windows boot\system partition and separate file system for application installation, then along with drive C:, back up the file system that includes the Windows Boot Volume, Windows System Volume, and application software. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about configuring snapshot policies for SYSTEM COMPONENTS backup. 2. Back up application data for Exchange CCR on the NetWorker server on the passive node by using the following save set with snapshot policy all. Applications:\Microsoft Exchange 2007 The steps in this disaster recovery scenario are based on the following host details for the production environment you are recovering, and the production environment you are recovering to. Production environment setup Domain Controller, one physical machine CCR setup with an active node and a passive node, two physical machines Recovery site setup (in the same network as the production setups) Domain Controller setup with the same hardware and software configuration as the production environment CCR setup with only a passive node, one physical machine In this disaster recovery procedure, the machines are referred to as follows: Production MC1: Domain controller CL1: cluster node 1 CL2: cluster node 2 Performing Microsoft Exchange server 2007 disaster recovery 155

156 Microsoft Exchange Server Backup and Recovery Recovery site (in the same network as the production setups) CL11: cluster node 1 CL21: cluster node 2 To perform a Microsoft Exchange server 2007 CCR disaster recovery in production to a two-node cluster: 1. Shut down the Exchange CCR setup. Ensure to shut down both CCR nodes, assuming the Exchange Cluster is lost or crashed. 2. Reset the computer account for the following: Existing Exchange virtual server CMS Virtual Exchange server. 3. Reset the computer account for CL1 and CL2 if you want the base cluster names to be the same as those in original production setup. 4. Rebuild two machines CL21 and CL11 with the same operating system version as the old server. 5. Assign the new machine with a new IP address and new Network name, and bring it online in the same domain. Note: If you want the same IP address and Network name as the production machine, assign the same IP and name. 6. Install all roles required for Exchange setup to run on both CL11 and CL Install cluster feature and create a new cluster with Quorum. Note: The Majority Node Set (MNS)/Quorum shared folder must be different from the old. 8. Ensure the host has all of the drive letters created as those that were on the original Exchange server. 9. Run Exchange setup in Custom mode. 10. Install only the Passive Cluster Role on CL Run the following command, by using the CMS name and IP address from the old CCR server: Setup.com /recovercms /CMSName:<name> /CMSIPaddress:<ip> 12. When this command is run: It puts the old virtual server online on this new node. All storage groups which were created in CCR are recreated in this installation. All databases will be in a dismounted state, which is required to recover from NMM. 13. Install NMM. 14. Browse through OLD CCR EVS index and perform PIT recovery of Exchange. 15. On CL211, install Exchange passive node. Run Exchange setup in custom mode and install only the Passive Cluster Role. 156 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

157 Microsoft Exchange Server Backup and Recovery Performing a quick recovery of a deleted mailbox in Exchange 2007 The procedure to recover a deleted mailbox in Exchange 2007 is performed independent of NMM backup or recovery operations. In the event that a user mailbox is deleted, you can quickly recover the mailbox through the Exchange Management Console. To recover a deleted mailbox: 1. In Exchange Management Console, ensure that deleted user mailbox entry appears under Disconnected mailbox under Recipient management. 2. Re-create the user mailbox with same name. 3. Disable the re-created user mailbox. 4. Open Disconnected mailbox under Recipient management; and then select the user mailbox which was accidentally deleted. 5. Right-click the user mailbox and then select Connect. 6. Select User mailbox radio button, and then click Next. 7. Select Matching user > User mailbox, and then click Next. The deleted user mailbox is then re-created under Recipient management > Mailbox. Note: Recreated deleted mailboxes are not always immediately visible. It may take from 15 minutes to an hour before the mailbox is visible and accessible through Outlook. Best practices In addition to the information in Table 29 on page 157, which lists the considerations for specifying values in the Save Set attribute for a particular client resource, also review the following sections on best practices and recommendations to follow when by using NMM to back up and recover Exchange server: Backups should be grouped with no more than 10 storage groups at a time on page 158 Use consistency check parameters to set threading and throttling to handle performance issues on page 158 Additional Exchange backup and recovery best practices on page 159 Table 29 Best practices and considerations for application backups (page 1 of 2) 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 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. Performing a quick recovery of a deleted mailbox in Exchange

158 Microsoft Exchange Server Backup and Recovery Table 29 Best practices and considerations for application backups (page 2 of 2) Consideration 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 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. Backups should be grouped with no more than 10 storage groups at a time When backing up Exchange 2007, backups should be grouped with no more than 10 storage groups at a time. This is especially important when parallel consistency checking has been turned on. Grouping more than 10 storage groups consumes the available resources of the CPU, I/O, and memory, which can lead to backup failures. Set the NSR_EXCHANGE_LIMIT_SG attribute to yes to set the number of storage groups to 10. Specifying Exchange 2003 and 2007 save sets for application data on page 115 provides details about the NSR_EXCHANGE_LIMIT_SG attribute. Use consistency check parameters to set threading and throttling to handle performance issues Exchange backup performance is greatly affected by the consistency check utility. The larger the databases and logs, the longer it takes to run the consistency checker. NMM provides the options to run the consistency check on multiple storage groups in parallel. NMM provides the ability to set threading and throttling to handle performance issues through the use of the -A attribute values for eseutil configuration settings. Note: If multiple consistency checks are run in parallel without setting proper throttle limits, it may cause performance problems on the proxy system. In extreme cases, this can cause I/O bottlenecks so severe that consistency checks will fail and other operations with the system are adversely affected. The following attributes have been added. These are set in the Application Information attribute of the client resource: NSR_ESE_UTIL_SEQUENTIAL Set to true to specify if eseutil should be run sequentially (single threaded) or to false to specify if eseutil should be run in parallel against multiple SGs (multi-threaded). By default, it is set to true for sequentially. NSR_ESE_UTIL_THROTTLE Set to true or false to specify if eseutil should be throttled. 158 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

159 Microsoft Exchange Server Backup and Recovery NSR_ESE_THROTTLE_IOS Number of I/Os between pauses when throttling, value range of 100 < The default value is 100. NSR_ESE_THROTTLE_DURATION Duration of pause in milliseconds when throttling, value range of 1000 < The default value is For example: A NSR_ESE_UTIL_SEQUENTIAL=false -A NSR_ESE_UTIL_THROTTLE=true A NSR_ESE_THROTTLE_IOS=500 -A NSR_ESE_THROTTLE_DURATION=5000 Additional Exchange backup and recovery best practices This section lists the additional best practices that you review for Exchange backup and recovery: Backup time can be reduced by spreading data across different storage groups. For example, it takes longer to back up a single storage group with 200 GB of data, than it does to back up 200 GB of data spread across 10 different storage groups. Avoid using mount points for creating storage groups. It takes longer to run a snapshot operation for a storage group with mount points, than it does for a storage group with no mount points. In addition to your scheduled full backups, you should also perform a full backup copy of Exchange server after: Every successful recovery. Upgrading to NMM from previous releases of NetWorker clients. The database directory path is changed or the storage group Log Path or System Path are changed. Ensure that all databases in a specified storage group are mounted before backing up the Exchange servers. Unmounted databases are not backed up. Ensure that database (mailbox and public folder) files and transaction log files reside on separate volumes for backup, otherwise the backup will fail. Also, ensure that the volume drive letter of the databases files is different from the volume drive letter of the transaction log files. If Exchange objects like storage groups and databases are deleted by using Exchange System Manager in Exchange server 2003, or Exchange Management Console in Exchange server 2007, these objects cannot be recovered until disaster recovery is performed. Objects from the Exchange server should not be deleted unless they no longer need to be recovered. After upgrading to the NMM client, you cannot recover Exchange backups that were performed with a previous version of the NetWorker client. To ensure that all Exchange data can be recovered to the point-in-time of the upgrade, perform a full backup of Exchange data immediately after upgrading to the NMM client. In Exchange server 2003 backups, save sets and backup groups that include the Exchange writer cannot include other application writers or the system components writer. The Exchange writer can, however be included in the same save set with volume components such as D:\. In Exchange server 2007, save sets and backup groups that include the Exchange writer cannot include any other volumes, applications, or non-exchange items in the save set. Best practices 159

160 Microsoft Exchange Server Backup and Recovery The Exchange consistency checker utility (eseutil.exe) must be installed on the proxy host that uses the Exchange Management tools installation. Ensure that the version of eseutil (Service Pack level) is the same as the Exchange server. For example, if Exchange server 2003 SP1 is installed on the Exchange server, then the version of eseutil that is installed on the proxy client, the Data Mover host, must be from the Exchange server 2003 SP1 management utilities. Failure to do so causes the consistency checker utility to report errors even when the database is valid. Exchange recovery limitations There are several limitations when backing up and restoring Exchange objects with NMM: Cannot restore a single mailbox using point-in-time recovery A single mailbox database cannot be restored by using point-in-time recovery of Exchange, because it requires both logs and databases to be selected for restore: VSS-marking semantics do not allow selecting logs for backup or restore. Logs are included only when the a storage group is selected for either backup or restore. Logs are not included when a database is selected. Roll-forward recovery not be possible after point-in-time restore After you complete a successful point-in-time restore, perform a full backup of the Exchange server so that you can perform roll-forward recovers. No support for RSG configuration where the RSG system path restore location and RSG logs restore location can be different Although Microsoft Exchange server supports an RSG configuration where the RSG system path restore location and RSG logs restore location are different, NMM currently does not support that configuration. The location for the RSG system path and the RSG log path must be the same. MAPI memory errors when recovering mailbox items from RSG databases There is a known memory error that may occur with Microsoft Exchange MAPI when recovering mailbox items from RSG databases. The error MAPI_E_NOT_ENOUGH_MEMORY may be reported in the NMM logs. When this error occurs, NMM recovers the mailbox item, but may lose properties such as the original font and formatting. This is a known problem, but Microsoft has no workaround or fix for this issue at this time. IPv6 issues affect browsing RSG mailboxes There is a known issue with IPv6 affecting MAPI calls. NMM uses MAPI calls to browse RSG mailboxes. This may occur when the NMM client is running Windows server 2008 x64 and Exchange server 2007, and IPv6 is enabled. IPv6 is enabled by default by Windows server 2008 installation. When IPv6 is enabled on the client, and there is no IPv6 network present, RSG mailbox browsing will fail. This can prevent you from viewing and selecting RSG mailboxes. This problem must be fixed through the registry, not the network connections dialog box. 160 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

161 Microsoft Exchange Server Backup and Recovery To fix RSG browsing issue in the registry: a. Open the registry. b. Navigate to HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters. c. Edit or create the 32-bit DWORD value DisabledComponents, and type the hex value FFFFFFFF. d. Reboot the machine. Best practices 161

162 Microsoft Exchange Server Backup and Recovery 162 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

163 6 Microsoft Exchange 2010 Server Backup and Recovery This chapter includes the following topics: Overview Performing Exchange 2010 backups Performing Exchange server 2010 recovery Performing a quick recovery of a deleted mailbox in Exchange Microsoft Exchange server 2010 disaster recovery Best practices Microsoft Exchange 2010 Server Backup and Recovery 163

164 Microsoft Exchange 2010 Server Backup and Recovery Overview NMM 2.3 supports both Exchange server 2010 and Exchange server 2010 SP1. The details for Exchange 2010 are relevant for Exchange 2010 SP1. NMM 2.3 provides Exchange server 2010 backup and recovery support in: Data Availability Group environment Microsoft Exchange 2010 has introduced Data Availability Group (DAG) for high availability of Exchange databases: Each Exchange database can be replicated to multiple Exchange servers, the maximum being 16 copies. Out of multiple copies of a database, only one copy of database is active at a time, the remaining copies are passive. Back up of active databases, passive databases, or both can be performed. Back up of databases in DAG environment can be restored only to active database copies. Non-DAG environment or stand-alone Exchange server 2010 environment Microsoft Exchange 2010 stand-alone applies to a Microsoft Exchange 2010 mailbox server where all the databases are hosted on one machine and there is no DAG configured. This section provides the following information: Supported operating systems on page 164 Types of backup and recovery on page 165 Exchange 2010 VSS writers on page 166 LAN-based Exchange server configuration with a storage area network and a proxy client on page 166 Exchange server 2010 DAG scenario on page 166 Backup initiated transaction log file truncation on page 166 Microsoft Exchange server 2010 MAPI client and Collaboration Data Objects version for Recovery Database item level recovery in Exchange 2010 on page 167 Supported operating systems NMM 2.3 provides support for Microsoft Exchange 2010 on Microsoft Windows server 2008 R2: Windows server 2008 R2 Standard Edition (x64) Windows server 2008 R2 Enterprise Edition (x64) NMM 2.3 provides support for Microsoft Exchange 2010 on Microsoft Windows server 2008 SP2: Windows server 2008 SP2 Standard Edition (x64) Windows server 2008 SP2 Enterprise Edition (x64) 164 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

165 Microsoft Exchange 2010 Server Backup and Recovery Types of backup and recovery NMM 2.3 will support Exchange 2010 following backup types on Windows 2008 R2 for both DAG and stand-alone environments: Full backup By using NMM 2.3, you can perform full backup of Microsoft Exchange 2010 databases for both DAG and non-dag environments. Both database files and logs files are backed up: Incase of backups performed in DAG environment, it must be specified if the database that is to be backed up is active, passive, or both. You can optionally run a consistency check on Exchange In case of passive databases backup, the replication status is selected. Index entries are created against the DAG. In non-dag environment, backup is done for all the databases that are mounted at that point of time. Consistency check takes place if no value is added for application information. Incremental backup By using NMM v2.3, you can perform incremental backup of Microsoft Exchange 2010 databases for both DAG and non-dag environments. Unlike full backup where both database files and logs files are backed up, in incremental backup only logs files are backed up. An incremental backup of a passive copy of a database can be run after a full backup of an active copy on another server, and vise versa: Incase of backups performed in DAG environment, it must be specified if the database that is to be backed up is active or passive. You can run a consistency check on Exchange In case of passive database backup, the replication status is selected. Index entries are created against the DAG. In non-dag environment, backup is done for all the databases those are mounted at that point of time. Index entries are created against the Mailbox Sever or the physical host. NMM 2.3 supports Exchange 2010 following recovery types on Windows 2008 (x64) R2 for both DAG and stand-alone environments: Full and incremental recovery Granular recovery for mailbox, folder, and IMPORTANT You must ensure that you have Exchange 2010 SP1 Rollup 2 installed when performing Recovery Database (RDB) item level recovery on any Exchange mailbox server. Overview 165

166 Microsoft Exchange 2010 Server Backup and Recovery Exchange 2010 VSS writers Microsoft Exchange 2010 has two writers for active and passive databases. NMM 2.3 uses both the writers during backup. Table 30 on page 166 lists the Exchange 2010 VSS writers. Table 30 Exchange 2010 VSS writers Writer name Microsoft Exchange Information Store writer Microsoft Exchange Replication writer Description In non-dag environment, this writer is used for database backup. In DAG environment, this writer is used to back up active database. In DAG environment, this writer is used to back up passive databases on the physical node. LAN-based Exchange server configuration with a storage area network and a proxy client The LAN-based Exchange server configuration with storage area network and a proxy server is the same for Exchange server 2010 and Exchange server LAN-based Exchange server configuration with a storage area network and a proxy client on page 104 provides details. Exchange server 2010 DAG scenario Exchange server 2010 has introduced DAG for high availability of Exchange databases. Each Exchange database can be replicated to multiple Exchange servers, with a maximum of 16 copies. Out of multiple copies of a database, only one copy of database is active at a time and rest of the copies are passive. NMM 2.3 supports DAG to back up active databases, passive databases, or both. NMM 2.3 supports restore of active and passive copies of databases to only active database copies. Information about Exchange 2010 DAG architecture is available on the Microsoft Technet website at Backup initiated transaction log file truncation Backup initiated transaction log file truncation is started based on the type of backup chosen: In non-dag configurations, the Store Writer truncates the transaction log files at the completion of successful full or incremental backups. In DAG replicated configurations, log truncation is delayed by the Replication service until all necessary log files are replayed into all other copies. The Replication service deletes the backed up log files both from the active and the copy log file paths after the service verifies that the to-be-deleted log files have successfully been applied to the copy database and both active database and the database copies checkpoint has passed the log files to be deleted. provides more details. 166 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

167 Microsoft Exchange 2010 Server Backup and Recovery Microsoft Exchange server 2010 MAPI client and Collaboration Data Objects version for Recovery Database item level recovery in Exchange 2010 Download the MAPI Collaboration Data Objects (CDO) version for Recovery Database item level recovery from the following location: C4-4D8D-9BC5-3E B1F Performing Exchange 2010 backups This section provides the following information: Backup options on page 167 Specifying Exchange 2010 application data save sets on page 168 Displaying save set syntax on page 168 Exchange 2010 application information variable settings on page 169 Configuring persistent and non-persistent snapshots on page 171 Configurations for backing up Exchange 2010 in non-dag and DAG environment on page 171 Prerequisites before running a backup on the Exchange 2010 system on page 171 Promoting Exchange 2010 incremental backup to full backup on page 172 Configuring Exchange server 2010 backups on page 172 Configuring Avamar deduplication backups in a DAG environment on page 175 Performing non-persistent backup of Microsoft Exchange 2010 on page 176 Verifying backups on page 176 Backup options The following options are provided for backup: Backup only active databases on the server In NMM 2.3, you can back up all the active database copies residing on a Microsoft Exchange 2010 mailbox server in a DAG environment. You can perform full and incremental backups. Backup only passive databases on the server In NMM 2.3, you can back up all the passive database copies residing on a Microsoft Exchange 2010 mailbox server in a DAG environment. You can perform full and incremental backups. Backup both active and passive databases on the server In NMM 2.3, you can back up both active and passive databases on Microsoft Exchange 2010 mailbox server in the DAG environment. Backup from storage node In NMM 2.3, you can perform Microsoft Exchange 2010 backup from the NetWorker storage node which means that both the Microsoft Exchange 2010 and NetWorker storage node are on the same machine. In such installation, Microsoft Exchange 2010 can be in a DAG or non DAG environment. You can perform full and incremental backups. Performing Exchange 2010 backups 167

168 Microsoft Exchange 2010 Server Backup and Recovery Backup from remote storage node In NMM 2.3, you can perform Microsoft Exchange 2010 database backup by using a remote NetWorker storage node in a DAG or non-dag environment. This means that the Microsoft Exchange 2010 and NetWorker storage node are on different machines. You can perform both full and incremental backups. Backup from NetWorker proxy node In NMM 2.3, you can back up of Microsoft Exchange 2010 databases by using a NetWorker proxy node in both a DAG or non-dag environment. You can do both full and incremental backups. Specifying Exchange 2010 application data save sets Table 31 By using NMM 2.3, you can configure client resources with Exchange 2010 Mailbox server name. You can provide the save set name in client resource at writer-level or database name-level. Table 31 on page 168 provides the list of Exchange 2010 save sets for application data. Exchange 2010 save sets for application data Type of backup data Save set syntax Writer-level APPLICATIONS:\Microsoft Exchange 2010 Database name-level APPLICATIONS:\Microsoft Exchange 2010\<Database name> Displaying save set syntax After the NMM client is installed on the Exchange 2010 server, you can display a list of Exchange save sets available for backup. To display a list of the Exchange 2010 save sets that are available for backup: 1. Open a command prompt on the Microsoft Exchange server. 2. From the command prompt, type the following command to list the valid application data save set names: For writer-level back and all databases on the mailbox server: nsrsnap_vss_save -? For example, C:\Users\administrator.NMMEXCH2010>nsrsnap_vss_save -? APPLICATIONS:\Microsoft Exchange 2010 APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database :nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success. For writer-level backup and a list of all the databases on the mailbox sever categorized by the active or passive database state on the current node: nsrsnap_vss_save -v -? 168 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

169 Microsoft Exchange 2010 Server Backup and Recovery For example: C:\Users\administrator.NMMEXCH2010>nsrsnap_vss_save -v -? "APPLICATIONS:\Microsoft Exchange 2010" "APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database Passive" "APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database Active" 68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success. Note: Remove the inverted commas when copying the saveset name from the output. Also, do not include the - - Passive or - - Active when copying the output. These just denote the database state. Exchange 2010 application information variable settings You can define active or passive backup type through Application Information field. Table 32 on page 169 lists the variables that can be specified in the Application information attribute of the client resource. Table 32 Exchange application information variable settings (page 1 of 2) Attribute name Description Values NSR_SNAP_TYPE=value Specifies the snapshot service provider name. vss This value is required. NSR_DATA_MOVER=value application information attribute This attribute: 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. The values include: 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 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 you are setting up an Exchange client resource, it is recommended that you use a proxy client. A proxy client requires hardware for transportable snapshots. 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 Exchange server. Related messages are logged in the client resource host in both the Replication Manager log files and the nmm.raw file. Performing Exchange 2010 backups 169

170 Microsoft Exchange 2010 Server Backup and Recovery Table 32 Exchange application information variable settings (page 2 of 2) Attribute name Description Values NSR_DM_PORT=value NSR_ALT_PATH=value This attribute: Specifies the control port number to use in communicating with the data mover client. This is the control port that the Replication Manager (RM) client service is running on. EMC NetWorker Module for Microsoft Applications Release 2.2 SP1 Installation Guide provides more information about RM ports. This attribute: Specifies the path on which to mount Exchange snapshots during the backup process. Exchange snapshots are mounted so that the database consistency check utility, eseutil.exe, can be run. The RM client control port number. For example: NSR_DM_PORT=6728 An RM client control port number must be specified, and must match the value specified during installation. The default value that NMM uses during installation is If you specify a different value during installation, you must specify that value here. A mount path. For example: NSR_ALT_PATH=G:\mount_replica\ If a proxy client is specified in the NSR_DATA_MOVER attribute, type the mount path on the proxy client. Note: If the file system path specified for NSR_ALT_PATH in Exchange client does not exist, it is automatically created in NMM. NSR_CHECK_JET_ERRORS=value Specifies which JET database errors to check for in the event log before taking a snapshot. Note: If errors are found, the snapshot will fail. Values include the following: 447 (Exchange server 2007 only) 448 (Exchange server 2007 only) all none Values can be separated with a comma, for example: NSR_CHECK_JET_ERRORS=1018,1019 The default is none. NSR_EXCH2010_BACKUP=active For only active database copies backup. Active NSR_EXCH2010_BACKUP=passive For only passive database copies backup. Passive NSR_EXCH2010_BACKUP=all For both active and passive databases backup. All NSR_EXCH_CHECK=yes/no To specify the consistency check for databases. For Exchange 2010 DAG-based backup: The consistency check by default is no if the database is a passive copy. The consistency check by default is "yes" if the database is an active copy and does not have passive copies. For Exchange 2010 stand-alone backups, consistency check is "yes" by default. NMM does not detect the consistency check if there are only database copies in a DAG environment. Note: If consistency check is turned off, then the information is logged in the mega.xml file during backup. NSR_EXCH2010_DAG=<DAG name> To specify the DAG name for backup in a DAG environment. DAG FQDN name For example, DAG name.domain name.com 170 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

171 Microsoft Exchange 2010 Server Backup and Recovery Configuring persistent and non-persistent snapshots To configure: Persistent snapshots Configuring persistent snapshots on page 117 provides details about how to configure persistent snapshots for Exchange server Non-persistent snapshots To configure non-persistent backups in Exchange 2010, follow the steps provided for configuring persistent snapshots. In the Properties > Backup Snapshots field, where you enter the value for the snapshot policy to rollover snapshots to the NetWorker server, enter All. All the snapshots that are created are rolled over to the tape or disk. Note: In NMM, conventional recovery is performed. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details for conventional recovery. To recover the non-persistent snapshot backups, in the NMM UI, under Recover Options > NetWorker, ensure that the Conventional Restore option is selected. By default, the Conventional Restore option is selected. Configurations for backing up Exchange 2010 in non-dag and DAG environment Table 33 on page 171 lists the considerations for backup in a DAG and non-dag environment. Table 33 Configurations required for backup in non-dag and DAG environment Type of environment For non-dag Exchange 2010 server backup For DAG Exchange 2010 DAG backup Considerations Configuration does not have anything specific other than using the save set name APPLICATIONS:\Microsoft Exchange Configure the following clients on the NetWorker server: DAG as a client or in other words, the DAG client All the client members of the DAG For clients other than DAG client, provide the following attributes: NSR_EXCH2010_DAG=<DAG FQDN> NSR_EXCH2010_BACKUP = (all/active/passive) DAG resource is required in case of DAG backup because the data being backed up is indexed on DAG name. Prerequisites before running a backup on the Exchange 2010 system Ensure that: The databases under a DAG are in a healthy and mounted state before running the backup. Windows Authentication is enabled and Kernel Mode Authentication is not selected. Use the following process to check or set Windows authentication: 1. Go to IIS Manager > Your Host > Sites > Default Web Site > Powershell. 2. On the right-hand side pane, double-click Authentication and Enable Windows Authentication. 3. In Windows Authentication, right-click and ensure that the Kernel Mode Authentication is clear. Performing Exchange 2010 backups 171

172 Microsoft Exchange 2010 Server Backup and Recovery Promoting Exchange 2010 incremental backup to full backup An incremental backup is promoted to a full backup when: No previous full backup is found for a database within a specified saveset. From the last backup till the current incremental backup, if there a new database or new database files are introduced, the writer or database incremental backup is promoted to full backup. Log gaps are detected since last backup, that is gaps between highest log number retrieved from index and the lowest log number retrieved from the disk. The last backup was a snapshot backup. The current backup is a snapshot backup. IMPORTANT In Exchange 2010, after changing the log and database path, it is recommended that you perform a full backup. If after changing the log and database path, if an incremental backup is performed without first performing a full backup, then later a recovery from an incremental backup may lead to failures with log gaps. Configuring Exchange server 2010 backups To perform an Exchange server backups, complete the tasks outlined in Table 34 on page 172. IMPORTANT The first five tasks for scheduling a backup are the same for all VSS writers supported by NMM. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details. Table 34 Tasks for configuring an Exchange server backup (page 1 of 2) Backup task 1. Configure a backup pool for snapshot operations Consideration 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. 2. Configure snapshot policies The snapshot retention and number of snapshots should be set to zero. 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. Incremental backups include only the data that has changed since the last backup. Configuring Exchange backup schedule on page 120 provides more information. 172 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

173 Microsoft Exchange 2010 Server Backup and Recovery Table 34 Tasks for configuring an Exchange server backup (page 2 of 2) Backup task Consideration 4. Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. 5. Configure a client group The Group resource is created so that the client resource can be added to the required group. The main requirement when configuring the Group resource is that the Snapshot checkbox must be selected. You can also select the snapshot policy manually. 6. Configuring Exchange client resource on page 173 This task is specific to configuring a Exchange client resource. Configuring Exchange client resource For the Exchange 2010 DAG environment, configure a client resource for each Exchange 2010 mailbox server participating in the DAG. This is a must requirement even if a particular mailbox server is not used for backup. Exchange 2010 DAG backup will fail if NMM does not find the client resource for other mailbox servers participating in DAG. You can: Configure multiple client resources for the same physical host with different database names in save set field. Configure multiple client resources for a different physical host with databases residing on those physical hosts. To create a client resource for Exchange stand-alone or DAG environment: 1. In the Administration window 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 fully qualified domain name FQDN of the NetWorker client computer. Note: Ensure not to use the short name of the NetWorker client computer because only FQDN is supported. 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 list, select a browse policy. The browse policy determines how long the rolled-over data is available for quick access. Ensure that the browse policy is long enough for your expected recovery needs. If your recovery needs are beyond the browse policy, an index recovery can be performed and should be the preferred first step. If index recovery is not possible, you can scan tapes to rebuild the index but this should be the last option. 7. From the Retention Policy attribute list, select a retention policy. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details about the retention policy for Exchange. Performing Exchange 2010 backups 173

174 Microsoft Exchange 2010 Server Backup and Recovery 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute: a. Specify the components to be backed up. b. Place multiple entries on separate lines by using the save set names in Table 31 on page If required, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource. Table 26 on page 117 provides the URL-encoded values for Microsoft Exchange save sets that are used to represent special characters, such as the backslash (\) and a table of values: 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 when naming Exchange mailbox database. For example, a mailbox database is named: Accounting\Bellevue This mailbox database would be represented in the Save Set attribute as: APPLICATIONS:\Microsoft Exchange 2010\Accounting%5CBellevue 11. For the Group attribute, select the backup group to which this client resource will be added. Note: The backup group must be a snapshot group. 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. 12. For the Schedule attribute, select a backup schedule. 13. Click the Apps & Modules tab. 14. In the Access area, leave the Remote user and Password fields empty.! IMPORTANT Do not select the DSN option under Device properties, otherwise the DAG backup will fail. 15. 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 16. In the Application information attribute: a. Type the following variable and value: NSR_SNAP_TYPE=vss NSR_ALT_PATH=<mount_path_on_local_host> b. Type Exchange application variable settings and their values on separate lines. Table 32 on page 169 describes these settings. 174 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

175 Microsoft Exchange 2010 Server Backup and Recovery c. Create the directory path, for example C:\mount_dir on the client machine before specifying: NSR_ALT_PATH=C:\mount_dir 17. Click the Globals (1 of 2) tab. 18. Verify that the Aliases attribute displays the NETBIOS name for the client. This name should have already been filled in automatically. Note: 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. 19. Click OK. Configuring Avamar deduplication backups in a DAG environment Before performing the steps described in this section, ensure that the following prerequisites are taken care of: Create client resources for all DAG member servers. Create a client resource with the DAG name. Before starting DAG backup, perform the following steps in NMC: 1. In the server's administration interface, click Configuration. 2. Select Clients in the navigation tree. The Clients table appears. 3. Right-click on Clients in the navigation tree, or right-click any client in the Clients table, and select New. The General tab appears in the Create Client window. 4. In the General tab, specify Exchange DAG name as client name, with the following exceptions: a. Clear the Scheduled backup option. b. In the Save set list, add the same save set list that is in the passive node client resource. 5. In the Apps & Modules tab: a. In the Access area, leave the Remote user and Password fields empty. b. In the De-Duplication area: a. Select the De-Duplication backup attribute to enable this client for deduplication backups. b. Select the name of the deduplication node to which this client's backup data will be sent. This should be the same deduplication node specified for the DAG member server. This step links this client with its own deduplication node. Do not select the name of a replication node. 6. Add this new DAG client resource to the backup group that contains the DAG member client resource. 7. Start DAG backup. Performing Exchange 2010 backups 175

176 Microsoft Exchange 2010 Server Backup and Recovery Performing non-persistent backup of Microsoft Exchange 2010 Non-persistent snapshots are possibly only when Backup Snapshots is set to ALL in NMC GUI. This is done so that all the snapshots that are created are rolled over to the tape or disk. Note: To recover non-persistent snapshot backups, in the NMM GUI, ensure that Recover Options > NetWorker > Conventional Restore option is selected. In NMM GUI, this option is selected by default. Verifying backups To verify if a backup is successful, use the following command on the NetWorker server: nsrinfo -s <Server> <Client Name> where, the <Client Name> is the DAG name or Exchange 2010 mailbox server name. Performing Exchange server 2010 recovery This section provides the following information: Performing full recovery on page 176 Performing advanced recovery on page 177 Performing granular recovery of mailbox, folder, or on page 181 IMPORTANT Perform a full level backup after every restore performed in Exchange Performing full recovery You can recovery the contents of a backed up database to the original database by performing full recovery. To perform full recovery: 1. In NMM 2.3, select Exchange 2010 Recover Session > Recover Options > Recover in the task bar. 1. Select the database in the NMM 2.3 GUI. 2. Select Recover in task bar. IMPORTANT Perform a full backup after performing a point-in-time or roll-forward recovery. 176 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

177 Microsoft Exchange 2010 Server Backup and Recovery Performing advanced recovery In NMM 2.3, by using Exchange 2010 Recover Session > Recover Options > Advanced Recover you can perform: Alternate restore to Recovery Database (RDB) Restore to alternate location Restore to remote location To perform recovery of a DAG database: 1. Open the NMM client GUI. 2. Select the NetWorker Server on which the NMM client software was configured for backup. 3. Select the DAG database to be recovered as shown in Figure 31 on page 177.! IMPORTANT You can browse and recovery of individual mailboxes and mailbox items from the list on the right pane. Figure 31 Select Exchange 2010 database 4. In the Exchange 2010 Recover Session toolbar, and click the Advanced Recover Option. The Advanced Recover dialog box appears. This dialog box provides three steps for recovery: Select Recovery Select Recovery Database Summary Performing Exchange server 2010 recovery 177

178 Microsoft Exchange 2010 Server Backup and Recovery Figure 32 Advanced Recovery dialog box Note: Click Recover Options to skip the steps for Advanced Recovery and perform traditional recovery of the database listed in Database (Source). Alternate recovery to Recovery Database 5. In Select Recovery, under Recovery Type, select one of the following: Recovery Database Recovery Alternate recovery to Recovery Database on page 178 provides details. Alternate Database Recovery Recovery to an alternate or remote database on page 180 provides details. Remote Database Recovery Recovery to an alternate or remote database on page 180 provides details. To perform alternate recoveries to RDB for Microsoft Exchange 2010: 1. In the Advanced Recovery window, select Recovery Database (RDB) Recovery and click Next. The Manage RDB window appears. Figure 33 Manage RDB window 178 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

179 Microsoft Exchange 2010 Server Backup and Recovery 2. If a RDB is not available, you can create a new RDB. Click the red alert icon next to the Recovery Database (RDB) List and click Create. The Create_DB window appears. Figure 34 Create_DB window 3. In the RDB Name field, type a name for the new RDB. 4. In the EBD File Path field, browse and select the file path location for the new RDB. 5. In the Log File Path field, browse the location for the log file. 6. Click Create. The new RDB is created and appears in the Recovey Database (RDB) List box. 7. You can also: Delete a RDB Select a RDB and click Delete to remove a RDB from the Recovey Database (RDB) List box. Unmount a RDB If a RDB is mounted but you are getting an error during recovery, you can unmount the RDB and mount the same or another RDB for recovery. Select a RDB and click Unmount. Mount a RDB Ensure the RDB is mounted on the current node of the NMM client for recovery to take place. If the database being recovered is not mounted on the current node or if the replication is on, then the recovery will fail. Select a RDB and click Mount. Overwrite a RDB The RDB Overwrite option marks the RDB that can be overwritten by a restore operation.! IMPORTANT Ensure that the RDB is mounted before proceeding to the next step. 8. Select the created RDB and click Next. The Exchange Recovery Summary window appears. This window lists the Exchange server recovery options and the NetWorker recovery options and allows you to review the details before proceeding with recovery. Performing Exchange server 2010 recovery 179

180 Microsoft Exchange 2010 Server Backup and Recovery Note: Click Back if you want to make changes to the recovery options that were previously selected by you. Figure 35 Exchange Recovery Summary Recovery to an alternate or remote database 9. To proceed with recovery, click Start Recovery. You can recover a database to: The original database mounted on a remote location. The same location as the backed up database. An alternate database mounted on the same host (alternate database recovery) In alternate database recovery, a desired mailbox database is restored to a alternate (different) mailbox database on the local Exchange mailbox server. Perform alternate database recovery from the mailbox server where the desired mailbox database is restored. Alternate database recovery can be used to: Recover a mailbox database, when backup was taken from the local mailbox server to a different mailbox database on the local mailbox server. Recover a mailbox database, when backup was taken from a different mailbox server to a different mailbox database on the local mailbox server. An alternate database mounted on a remote host (remote database recovery) In remote database recovery, a desired mailbox database is restored to a remote mailbox server, in the Exchange 2010 DAG where the active database resides. The remote database recovery option is only available for Exchange 2010 DAG and not for Exchange 2010 standalone. Remote database recovery can be used to: Recover a mailbox database, when backup was taken from the Exchange 2010 DAG to the original active mailbox database on the remote mailbox server. Recover a mailbox database, when backup was taken from the Exchange 2010 DAG to a different active mailbox database on the remote mailbox server. 180 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

181 Microsoft Exchange 2010 Server Backup and Recovery To perform recoveries to an alternate database: 1. In the Advanced Recovery window: Select Alternate Database Recovery for recovery to an alternate database. Select Remote Database Recovery for recovery to an remote database. 2. Click Next. The Select Database window with a list of other databases for recovery appears. Figure 36 Select Database window 3. Select the database to which you want to perform the recovery to and click Next. The Exchange Recovery Summary window appears. This window lists the Exchange server recovery options and the NetWorker recovery options and allows you to review the details before proceeding with recovery. Note: Click Back if you want to make changes to the recovery options that were previously selected by you. 4. To proceed with recovery, click Start Recovery. Performing granular recovery of mailbox, folder, or Before performing RDB item-level browsing, review the following prerequisites: Ensure that at least one public folder database is created in that Exchange organization. Ensure IPv6 is disabled in the Exchange machine, where RDB item-level browsing is performed. Ensure Exchange server 2010 permissions for RDB mailboxes browsing are provided. To provide the permissions, perform the following steps: a. On the Microsoft Exchange server, select the Start > All Programs > Exchange Management Shell. b. Enable Send-As and Receive-As permission. Performing Exchange server 2010 recovery 181

182 Microsoft Exchange 2010 Server Backup and Recovery For example: get-exchangeserver <Exchange Server name> Add-AdPermission -user <username> -extendedrights Receive-As, Send-As where: <Exchange Server name> is the server where the RDB mailbox is located. <username> is the name of the user being granted permissions. Ensure MAPI/CDO Kit installed. To recover a mailbox, folder, or even an 1. Open the NMM client GUI. 2. Select the NetWorker Server on which the NMM client software was configured for backup. 3. Select the mailbox, folder, or to be recovered as shown in Figure 37 on page 182. Figure 37 Select mailbox, folder or for recovery 4. Select Recover in task bar. Performing a quick recovery of a deleted mailbox in Exchange 2010 The procedure to recover a deleted mailbox in Exchange 2010 is performed independent of NMM backup or recovery operations, and is similar to the procedure followed for Exchange Performing a quick recovery of a deleted mailbox in Exchange 2007 on page 157 provides details. 182 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

183 Microsoft Exchange 2010 Server Backup and Recovery Microsoft Exchange server 2010 disaster recovery For Microsoft Exchange server 2010 disaster recovery on Windows 2008 and Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery. Chapter 10, Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM provides details. Best practices Review the following while performing Exchange 2010 backups and recovery in a stand-alone and DAG environment: Backup in a DAG environment If a node is added to a DAG and a database is backed up, then: Refresh the GUI. Or Close the UI and then reopen the UI. Directed recovery Remote recovery and directed recovery are supported only in the same domain. Cross-domain Exchange recovery is not supported. That is, if two machines are in different domains, then directed recovery is not supported. Backup in a stand-alone environment If a node is backed up in a stand-alone environment and then moved to a DAG, then the stand-alone backups of the node cannot be browsed. To recover the stand-alone backup, the node should be removed from DAG. The data can now be browsed in the NMM UI and recovered. Backup fails if the logs path and mailbox database path are in the same volume. Ensure that the logs path and mailbox database path are not in the same volume, even if the logs and database reside on mount point or normal path. Microsoft Exchange server 2010 disaster recovery 183

184 Microsoft Exchange 2010 Server Backup and Recovery 184 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

185 7 Microsoft SharePoint Server 2003 Backup and Recovery This chapter includes the following topics: Overview Performing SharePoint 2003 backups Performing SharePoint 2003 recovery Example of SharePoint 2003 backup and recovery process Microsoft SharePoint Server 2003 Backup and Recovery 185

186 Microsoft SharePoint Server 2003 Backup and Recovery Overview This section contains the following: VSS backup support provided by NMM on page 186 Microsoft SharePoint Portal server 2003 and Windows SharePoint Services 2.0 on page 187 Types of supported backup on page 187 Supported SharePoint 2003 writers on page 187 Commands used SharePoint 2003 backup and recovery on page 187 VSS backup support provided by NMM Table 35 on page 186 provides details for backup support for SharePoint features. Table 35 SharePoint features and details Feature Objects Search Directed recovery Support provided Web applications Site collection Sites Lists calendars, events, surveys, wiki's, blog's, announcements, and so on Libraries document, picture, and so on Items Versioning Metadata Author, Timestamp, and so on Author, Name, Title, Size, Creation Date, Modification Date, Keyword, Save set Date Range In-place recovery same farm Out-of-place recovery same farm Farm to farm recovery VSS backup for disaster recovery Backup support Farm Yes Databases Backup type Full Yes Yes Backup type Incremental (log) Recovery support Farm Yes CFG Database Search database/index Content databases Yes Yes Yes 186 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

187 Microsoft SharePoint Server 2003 Backup and Recovery Microsoft SharePoint Portal server 2003 and Windows SharePoint Services 2.0 Microsoft SharePoint Portal server 2003 with Windows SharePoint Services 2.0 is supported. The EMC Information Protection Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions supported by the NMM client. Microsoft SharePoint Portal server 2003 and Windows SharePoint server (WSS) 2.0 do not have their own VSS writers. Microsoft SQL server hosts the SharePoint 2003 databases. In NMM, backup and disaster recovery use the Microsoft SQL server VSS writers to perform the backup and recovery of the Microsoft SQL databases. After the Microsoft SQL databases are recovered, the SharePoint recovery is performed. Types of supported backup NMM provides the following types of backups for SharePoint 2003: SharePoint 2003 database backup Configuration database SharePoint Portal server 2003 portal sites backup, including the following databases: Content database User profile database Services database Index databases Windows SharePoint Services database Web storage system-based Document Library Store and Document Libraries backup After a full backup of a library, individual items can be recovered to the web storage system-based library or redirected to filepaths. Backup level supported Full only Supported SharePoint 2003 writers Table 36 on page 187 list the writers supported by SharePoint 2003: Table 36 List of supported SharePoint writers SharePoint server SharePoint writer Description SharePoint 2003 Microsoft SQL server provides application writers. SqlServerWriter The writer for SQL 2000/MSDE MSDEWriter-SQL2000 The writer for SQL server 2005 Commands used SharePoint 2003 backup and recovery The commands used for SharePoint 2003 backup and recovery are the same as those for Microsoft SQL server. Table 2 on page 22 lists the commands to back up SharePoint 2003 databases hosted on Microsoft SQL server. Overview 187

188 Microsoft SharePoint Server 2003 Backup and Recovery Performing SharePoint 2003 backups NMM provides full backup, and backup of individual content databases, which allows you to protect your SharePoint farm with individual content database backups between full backups. Consider configuring separate backup schedules for full backups and individual content database backups. IMPORTANT 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. or - The SYSTEM COMPONENTS:\ save set along with the system volume, for example C:\. This section provides the following information: SQL application information variable settings in SharePoint 2003 backup on page 188 Displaying valid SQL data save sets for SharePoint 2003 backup on page 188 Configuring SharePoint 2003 backup tasks on page 189 SQL application information variable settings in SharePoint 2003 backup The application information variable settings in SharePoint 2003 backup are the same as those for Microsoft SQL server. Table 3 on page 23 lists the application information variable settings. Displaying valid SQL data save sets for SharePoint 2003 backup To display a list of the SQL save sets that are available for SharePoint 2003 backup: 1. Open a command prompt on the application server. 2. From the command prompt, type the following command to list the valid application data save set names: 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 Note: If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server. 3. Press Enter: 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. 188 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

189 Microsoft SharePoint Server 2003 Backup and Recovery The save sets that are available for backup are listed in a format similar to the following: APPLICATIONS:\MSDEWriter-SQL2000 APPLICATIONS:\MSDEWriter-SQL2000\GALL%5CReportServer APPLICATIONS:\MSDEWriter-SQL2000\GALL%5CReportServerTempDB APPLICATIONS:\MSDEWriter-SQL2000\GALL%5CSPS01_Config_db APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_PROF APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_SERV APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_SITE Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. Configuring SharePoint 2003 backup tasks Table 37 on page 189 lists the backup tasks for SharePoint IMPORTANT The first two tasks are described in the EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide. Table 37 Backup tasks for SharePoint 2003 Backup task Consideration 1. Configure a backup schedule Backup schedules determine the days on which full backups are run. Full backups include all of the data specified in an NMM client resource save set. 2. Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. 3. Configure a SharePoint 2003 client resource on page 189 This task is specific to configuring a SharePoint 2003 client resource. Configure a SharePoint 2003 client resource The backup will use either SqlServerWriter or MSDEWriter-SQL2000, depending on which writer is displayed when you run the nsrsnap_vss_save-? command to list the available save sets. You can back up all SQL databases on the server, or individual databases, depending on what you specify in the save set. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. To configure a SharePoint 2003 client resource using SQL server writers: 1. In the Administration window 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. Performing SharePoint 2003 backups 189

190 Microsoft SharePoint Server 2003 Backup and Recovery 5. In the Comment attribute, type a description. Note: 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. The backup will use either SqlServerWriter or MSDEWriter-SQL2000, depending on which writer is displayed when you run the nsrsnap_vss_save-? command to list the available save sets. You can back up all SQL databases on the server, or individual databases, depending on what you specify in the save set. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. To back up all SQL 2000 embedded databases, specify the save set name: SYSTEM COMPONENTS:\ Note: The SYSTEM COMPONENTS:\ save set should be backed up as part the system disaster recovery strategy. To back up all SQL 2000 named instances and stand-alone databases, specify the save set name: APPLICATIONS:\MSDEWriter-SQL2000 To back up only the SQL 2000 host instance and database name combination, specify the save set name: APPLICATIONS:\MSDEWriter-SQL2000\host%5Cinstance\master To back up all SQL server 2005 named instances and stand-alone databases, specify the save set name: APPLICATIONS:\SqlServerWriter If the SQL server 2005 VSS Writer service is running, then SQL 2005 Express databases are backed up under SYSTEM COMPONENTS: SYSTEM COMPONENTS:\ If the SQL server 2005 VSS Writer service is not running, then SQL 2005 Express databases are backed up under MSDEWriter-SQL2000: APPLICATIONS:\MSDEWriter-SQL Specify SQL application variable settings in the Application information attribute of the client resource. The Application information attribute of the client resource for SharePoint 2003 is the same as those for SQL server. These settings are described in Table 3 on page Click the Globals (1 of 2) tab. 190 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

191 Microsoft SharePoint Server 2003 Backup and Recovery 11. In the Aliases attribute, type the NETBIOS name for the client. Note: 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. Performing SharePoint 2003 recovery NMM provides the steps to recover the SQL server databases to the SQL server. After recovering the databases, they may need to be updated and added to the SharePoint portal. Consider the following when recovering SQL 2005 databases for SharePoint 2003: If the SQL server VSS Writer service was enabled during backup, then SQL server 2005 Express databases must be recovered from the following save set: SYSTEM COMPONENTS:\ If the SQL server VSS Writer service was disabled during backup, then SQL server 2005 Express databases must be recovered from the following saveset: APPLICATIONS:\MSDEWriter-SQL2000 The SQL server VSS Writer service is disabled by default when Microsoft SQL server 2005 is installed. To recover the SQL server databases and restore them in SharePoint: 1. Stop the SQL server services that correspond to the type of SQL database you are recovering: For the SQL server 2000 stand-alone database instances, the SQL server services are: SQL server <MSSQLSERVER 2000> service SQL server <Instance name> service For the SQL 2005 database instances, the SQL server services are: SQL server <MSSQLSERVER 2005> service SQL server <Instance name> service 2. From the navigation tree in the NMM GUI: For the SQL server 2000 stand-alone database instances, expand the Applications folder and the MSDEWriter-SQL2000 folder. For the SQL 2005 database instances: That are backed up to the SQLServerWriter save set, expand the Applications folder and the SQLServerWriter folder. That are backed up to the SYSTEM COMPONENTS save set, expand the SYSTEM COMPONENTS:\ folder. That are backed up to the MSDE-Writer-SQL2000 save set, expand the Applications folder and the MSDEWriter-SQL2000 folder. 3. Select the databases to recover. 4. From the System Recover Session toolbar, click Start Restore. 5. After the recovery is complete, start the SQL server services. Performing SharePoint 2003 recovery 191

192 Microsoft SharePoint Server 2003 Backup and Recovery 6. Launch SQL Enterprise Manager to verify that the databases have been successfully recovered within SQL server. 7. Launch SharePoint Server 2003 Central Administration. 8. Click List and Manage Portal Sites. 9. If the databases or portals are not displayed, click Restore Portal Site, and follow the instructions to add the databases and restore the portal site. Example of SharePoint 2003 backup and recovery process The backup and recovery for SharePoint 2003 and Windows SharePoint Services 2.0 configuration database is a backup of a Microsoft SQL server database. In this example: An organization is running Microsoft SharePoint Portal server 2003 Service Pack 2/Windows SharePoint Services 2.0 Service Pack 2 on Windows server It uses SQL 2000/SQL 2005 for the database server. The backup and recovery is performed with NMM 2.3. The following sections describe a backup and recovery operation performed by the NMM administrator: Creating a new SharePoint portal with three new databases on page 193 Viewing the location and hierarchy of databases as they appear in SQL Enterprise Manager UI on page 193 Configuring and performing a backup of the new databases with NMM save sets on page 193 Verifying that all databases are backed up through the UI on page 194 Deleting the new databases on page 195 Performing an NMM recovery of the databases on page 195 Verifying database recovery through the SQL Enterprise Manager on page 195 Recovering the portal site through SharePoint Portal Server Central Administration on page 196 Verifying the creation of the portal site in SharePoint Server Central Administration on page 200 Note: This descriptive example provides an overview of the interaction between Microsoft SQL server, NMM, and Microsoft SharePoint server. For detailed information on using Microsoft SQL server and Microsoft SharePoint server, consult the respective Microsoft documentation for those products. 192 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

193 Microsoft SharePoint Server 2003 Backup and Recovery Creating a new SharePoint portal with three new databases The SharePoint administrator uses SharePoint Portal Server Central Administration to create a new portal test11 with three SQL databases: test11_site test11_prof test11_serv The organization puts the portal into use by creating sites, and by uploading documents, pictures, events, and other items. Viewing the location and hierarchy of databases as they appear in SQL Enterprise Manager UI Figure 38 on page 193 displays the new databases as they appear in SQL Enterprise Manager. Figure 38 Newly created databases created in SharePoint Configuring and performing a backup of the new databases with NMM save sets The administrator sets up a backup of the SQL database. The administrator runs the following command on a command line: nsrsnap_vss_save -? This command lists the SQL writer, and the save sets available for backup. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. Example of SharePoint 2003 backup and recovery process 193

194 Microsoft SharePoint Server 2003 Backup and Recovery Displaying valid SQL data save sets on page 23 provides more information about using this command. The syntax for save sets is described in detail in nsrsnap_vss_save -? does not list APPLICATIONS:\SqlServerWriter as a save set if only SQL Express is installed. The SQL 2005, SQL 2008, and SQL 2008 R2 Express databases are backed up from SYSTEM COMPONENTS:\ save set. on page 25. In this example, the databases created by the organization are as follows: APPLICATIONS:\MSDEWriter-SQL2000 APPLICATIONS:\MSDEWriter-SQL2000\GALL%5CReportServer APPLICATIONS:\MSDEWriter-SQL2000\GALL%5CReportServerTempDB APPLICATIONS:\MSDEWriter-SQL2000\GALL%5CSPS01_Config_db APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_PROF APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_SERV APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_SITE In the example: The administrator determined the save sets available, and followed the steps for creating a SQL Server backup as described in Performing SQL server backups on page 22. The administrator specified the save set APPLICATIONS:\MSDEWriter-SQL2000 to back up all of the SharePoint databases. To back up just the test11_prof database, the administrator would specify APPLICATIONS:\MSDEWriter-SQL2000\GALL%5Ctest11_PROF. Verifying that all databases are backed up through the UI The administrator verified that the databases had been backed up by looking at the available recovery sets in NMM. In the navigation tree, the administrator expanded the Applications folder, the MSDEWriter-SQL2000 folder, and then the GALL (server) folder. Figure 39 on page 194 shows that all of the databases, including the three new test11... databases, were backed up. Figure 39 NMM backups available for recovery 194 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

195 Microsoft SharePoint Server 2003 Backup and Recovery Deleting the new databases The administrator wants to test NMM recovery, and deletes the portal from the SharePoint server. This deletion of the portal deletes the three new test11... databases from SQL. During deletion, SharePoint displays a message to verify that the administrator wants to delete the databases. The administrator clicks Yes and the databases are deleted. Performing an NMM recovery of the databases The administrator opens NMM again to recover the three databases. The administrator selects the new databases that were just deleted from SharePoint. Figure 40 on page 195 shows test11_prof, test11_serv, and test11_site databases selected by the administrator. Figure 40 SQL databases selected for recovery in NMM The administrator clicks Start Recover. The recovery is successful. Verifying database recovery through the SQL Enterprise Manager The administrator launches SQL Enterprise Manager and verifies that all three databases have been recovered. Figure 41 on page 196 shows that the three databases were recovered to the SQL server. Example of SharePoint 2003 backup and recovery process 195

196 Microsoft SharePoint Server 2003 Backup and Recovery Figure 41 Databases recovered to SQL server Recovering the portal site through SharePoint Portal Server Central Administration Recovering the SQL databases does not automatically bring them back into SharePoint. In SharePoint, the administrator launches SharePoint Portal Server Central Administration. Figure 42 on page 196 shows the Portal Site and Virtual Server Configuration page. Figure 42 SharePoint Server Central Administration page 196 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

197 Microsoft SharePoint Server 2003 Backup and Recovery The administrator clicks List and manage portal sites. In Figure 43 on page 197, the Manage Portal Sites page does not display the portal site. Figure 43 SharePoint Portal Server Central Administration, Manage Portal Sites window The administrator clicks Recover Portal Site. Figure 44 on page 197 shows the options for creating and restoring the portal. Figure 44 Portal creation and restore options Example of SharePoint 2003 backup and recovery process 197

198 Microsoft SharePoint Server 2003 Backup and Recovery Figure 45 on page 198 shows the settings specified by the administrator: Restore a portal, and the Site database name test11_site, User profile database name test11_prof, and Services database name test11_serv. Figure 45 Portal restore and database names After typing information in this page, a confirmation page appears, as shown in Figure 46 on page 198. Figure 46 Confirmation page for request to create a portal site 198 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

199 Microsoft SharePoint Server 2003 Backup and Recovery The administrator clicks OK and portal creation begins. Figure 47 on page 199 shows the status window that appears in SharePoint Portal Server Central Administration during portal creation. Figure 47 Status window for portal creation process Figure 48 on page 199 shows the page that indicates that the portal creation was successful. Figure 48 Operation Successful page displayed when portal creation is complete Example of SharePoint 2003 backup and recovery process 199

200 Microsoft SharePoint Server 2003 Backup and Recovery Verifying the creation of the portal site in SharePoint Server Central Administration In SharePoint Portal Server Central Administration, the administrator launches the Manage Portal Sites page, and the Portal Site is now listed as shown in Figure 49 on page 200. Figure 49 Recovered databases and SharePoint portal visible and available in SharePoint IMPORTANT Table 7 on page 38 lists the best practices and recommendations to follow when using NMM to back up and recover SQL Server. 200 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

201 8 Microsoft SharePoint Server 2007 Backup and Recovery This chapter includes the following topics: Overview Performing SharePoint 2007 backups Performing SharePoint 2007 farm hardware backups Performing SharePoint 2007 recovery Performing SharePoint 2007 disaster recovery Keeping backups and recoveries in sync Best practices for disaster recovery Backing up SharePoint database by using NMM and NMSQL Microsoft SharePoint Server 2007 Backup and Recovery 201

202 Microsoft SharePoint Server 2007 Backup and Recovery Overview This section contains the following: NMM solutions for protecting a Microsoft SharePoint 2007 farm on page 202 Microsoft Office SharePoint server 2007 and Windows SharePoint Services 3.0 on page 204 Types of SharePoint server 2007 backup and recovery on page 204 Microsoft Office SharePoint 2007 farm configurations on page 205 SharePoint 2007 writers on page 209 IMPORTANT NMM 2.3 does not support SharePoint granular backup and recovery support, including SharePoint optimized backup and SharePoint granular (non-optimized) backup. If you require SharePoint granular recoveries of SharePoint sites and site components, you can use the NMM 2.3 SharePoint VSS farm level backup capability. Content databases from the SharePoint VSS farm backup can also be recovered to alternate locations for data mining by third party SharePoint granular recovery tools, such as Kroll Ontrack PowerControls. However, if you do not want to use third party tools, it is recommended that you continue to use the NMM 2.2.x version that you are currently using. NMM solutions for protecting a Microsoft SharePoint 2007 farm You can use the SharePoint VSS Writer for backup and recovery. This method leverages the Windows server VSS framework to take VSS snapshots of the SharePoint configuration database, search databases or indexes, and content databases. These VSS snapshots can be backed up on-host by using the Windows VSS system provider or off-host by using VSS hardware providers. There is no performance impact on the SharePoint farm except for the backup to disk or tape operation, and this can be eliminated by using a proxy node and VSS hardware provider for off-host and LAN-free backup. Note: The System Provider is the software VSS provider that Microsoft provides as part of the operating system. The cache sizes and locations are managed in the Disk Management applet. NMM provides the solution for business continuity for SharePoint: By using the SharePoint VSS writer backup and recovery method, either the full farm in which case it is a disaster scenario, or individual content databases can be recovered. NetWorker and NMM integrate with Microsoft Office SharePoint server 2007 by using the SharePoint VSS writer. The Microsoft SharePoint server 2007 VSS writer is dependent on the Microsoft SQL server 2005 VSS writer. By using the SharePoint VSS writer, NetWorker takes VSS snapshots of the entire SharePoint farm for data protection. By using this VSS writer, NMM backs up the following SharePoint components: Configuration database SQL configuration database Content database SQL content database SharePoint search SharePoint search index and associated SQL databases 202 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

203 Microsoft SharePoint Server 2007 Backup and Recovery Office search Office search index and associated databases This type of data protection allows recovery of an entire farm when there is a disaster. NMM leverages the Windows VSS framework and the Microsoft Office SharePoint server 2007 VSS Writer or consistent point-in-time snapshots and backup of the entire SharePoint farm. NMM also supports off-host or LAN-free backups with the use of supported VSS hardware providers: Supported arrays include the EMC Symmetrix, V-MAX, Symmetrix DMX, CLARiiON and Celerra, arrays. Third-party arrays are also supported. The EMC Open Software Compatibility Guide (SCG) provides details. By using a supported VSS hardware provider, it is possible to take transportable snapshots of the complete SharePoint farm. The SharePoint farm system states, configuration database, content databases, and search indexes would be snapped by using VSS. A NetWorker NMM proxy node installed on a NetWorker storage node would allow off-host backup of the snapshot data. This allows higher performing backups as there is no backup load on the SharePoint application servers. If SAN-based backup to disk or tape is used, the off-host backup can be LAN-free for the best backup performance. For information about VSS technology, download the Microsoft TechNet article, Best Practices for Using Volume Shadow Copy Service, available on the Microsoft website. The advantages of taking backup and restore through a VSS writer are as follows: A single VSS reference writer There has been no easy way for applications to describe their data to backup applications. To successfully back up a full farm application, the SharePoint VSS writer enables NMM to take advantage of the single writer to back up Office SharePoint server Full farm backup and restore for catastrophe The writer allows a backup application NMM to easily access the VSS API to request a backup or a restore operation for an entire SharePoint farm, including a single box setup or a web farm configuration. Database level granularity The writer allows a requestor or NMM to select all databases, a segment of the databases (multiple select), or a single database (single select) for backup operations. NMM allows two recovery scenarios: Full configuration database, content databases, search and index databases, and associated generic database. Content database only Recovery of one or more content databases. Overview 203

204 Microsoft SharePoint Server 2007 Backup and Recovery SharePoint inventory list Before backup, the SharePoint writer generates a flat inventory list of databases selected for backup within the farm. The list is returned to the requestor (NMM) so that backup can be run on the location where the database is physically located. Recovery of the SharePoint search database and the index database allows recovery without the need to perform a full crawl of the SharePoint farm. Backup content without interruption An application can modify a file while it is being backed up, causing data corruption or causing an error when the file is opened. VSS allows a quick snapshot of the application to be made, while allowing the application to operate at the original location without interruption. Search index files backup and recovery Because search index files are stored in the file system, a separate file writer is required to back them up. To resolve this, Office SharePoint server 2007 includes a separate search writer that handles search index files. To simplify the process for backup application writers, Office SharePoint server 2007 declares cross-writer dependencies in such a way that search index files are also backed up or restored when backing up registered databases in the farm. Post-restore synchronization of databases To ensure that all databases are synchronized with the farm after a restore operation is complete, each database is automatically detached and reattached to the farm post recovery. Administrators do not need to run additional procedures to resynchronize the restored databases. Microsoft Office SharePoint server 2007 and Windows SharePoint Services 3.0 Microsoft Office SharePoint server 2007 with Windows SharePoint Services 3.0 is supported. The EMC Information Protection Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions supported by the NMM client. Backup and disaster recovery use the SharePoint VSS writers and Microsoft SQL server VSS writers. Types of SharePoint server 2007 backup and recovery NMM provides the following type of backup: Farm backup To back up all SharePoint data in the farm, including: Content/configuration databases Search/index databases NMM provides the following type of recovery: Snapshot recovery Farm recovery Disaster recovery Note: Rollback recovery is unsupported. 204 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

205 Microsoft SharePoint Server 2007 Backup and Recovery Microsoft Office SharePoint 2007 farm configurations A Microsoft Office SharePoint 2007 farm can be deployed in a: Stand-alone farm system The stand-alone configuration runs all the services on one machine, as shown in Figure 50 on page 205. Distributed farm configuration The distributed farm configuration includes several servers that host separate services, as shown in Figure 51 on page 206. A SharePoint farm includes the following services and servers: Central Administration site and shared services This is usually installed on an application server. Front-end web servers This is the web page-based user interface to manage the server. Index server Can be included on the query server if there is only one query server. Query servers If there is more than one query server, the index server cannot be included on a query server. Application servers For example, Excel Calculation Services. Microsoft SQL server This server contains the SharePoint databases: Configuration database (only one per farm) Content databases (one or more per farm) Search database (one or more per farm) Configuration Database Content Database NetWorker Server or later: Administers protection for NetWorker clients such as NMM Web Front End Index Server Query Server Microsoft SQL Server NetWorker Module for Microsoft Applications GEN Figure 50 SharePoint 2007 stand-alone farm configuration Overview 205

206 Microsoft SharePoint Server 2007 Backup and Recovery Query Server Index Server If there is more than Query Server, the Query Servers cannot be included on the Index Server NetWorker Module for Microsoft Applications Configuration Database (1 per farm) NetWorker Server or later: Administers protection for NetWorker clients such as NMM Web Front End On an application server NetWorker Module for Microsoft Applications Microsoft SQL Server Contains all SharePoint databases NetWorker Module for Microsoft Applications Content Database 1 (1 or more per farm) Content Database 2 GEN Figure 51 Example 1: SharePoint stand-alone farm Example 2: SharePoint distributed farm SharePoint 2007 distributed farm configuration A stand-alone farm in which the host contains the SharePoint server and SQL server. The NetWorker server has two client instances. Each client instance has different save sets: Save set for instance 1: APPLICATIONS:\Microsoft Office SharePoint Services Save set for instance 2: APPLICATIONS:\SqlServerWriter A distributed farm with two servers of which one contains the web front-end and Central Admin, and the other contains the SQL server. The NetWorker server has two client resources, one for each server. Each client resource has different save sets: SharePoint web front-end host save set for resource 1: APPLICATIONS:\Microsoft Office SharePoint Services SQL server host save set for resource 2: APPLICATIONS:\SqlServerWriter Example 3: SharePoint distributed farm A distributed farm with three servers running the following services: Server 1 Server 1 runs the following services: Windows SharePoint Services Incoming Windows SharePoint Services Web Application 206 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

207 Microsoft SharePoint Server 2007 Backup and Recovery Server 1 has the following roles: Web front-end server Windows SharePoint Services VSS Writer (registered on this machine) The output for Server 1 is as follows: nsrsnap_vss_save -? APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS:\Microsoft Office SharePoint Services\server2%5Csp07inst APPLICATIONS:\Microsoft Office SharePoint Services\server2%5Csp07inst\Content Database WSS_Content_ b07fd4d2e9c2a3ab47ca2361c Ensure NetWorker client 'server2' is part of the snapshot group with saveset for 'SQL Writer' component 'server2%5csp07inst \WSS_Content_ b07fd4d2e9c2a3ab47ca2361c' APPLICATIONS:\Microsoft Office SharePoint Services\server2%5Csp07inst\Content Database SharePoint_AdminContent_c12ae a-4ffc-8e2b-b2b10425be06 Ensure NetWorker client 'server2' is part of the snapshot group with saveset for 'SQL Writer' component 'server2%5csp07inst \SharePoint_AdminContent_c12ae a-4ffc-8e2b-b2b10425be06' APPLICATIONS:\Microsoft Office SharePoint Services\server2%5Csp07inst\Content Database WSS_Content Ensure NetWorker client 'server2' is part of the snapshot group with saveset for 'SQL Writer' component 'server2%5csp07inst \WSS_Content' APPLICATIONS:\Microsoft Office SharePoint Services\server3 APPLICATIONS:\Microsoft Office SharePoint Services\server3\SPSearch Content Index Catalog Ensure NetWorker client 'server3' is part of the snapshot group with saveset for 'SPSearch VSS Writer' component 'server3\conte ntindex_spsearch' APPLICATIONS:\Microsoft Office SharePoint Services\server1 APPLICATIONS:\Microsoft Office SharePoint Services\server1\SPSearch Content Index Catalog" Depends on 'SYSTEM COMPONENTS:\Microsoft Office SharePoint Search\ContentIndex_SPSearch' on Client 'server1' Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. Server 2 Server 2 runs the following services: Runs the SQL database service Maintains the content database server role The output for Server 2 is as follows: nsrsnap_vss_save -? APPLICATIONS:\SqlServerWriter APPLICATIONS:\SqlServerWriter\server2%5CSP07INST APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\master APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\model APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\msdb APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharePoint_Config APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharePoint_AdminCont ent_c12ae956 Overview 207

208 Microsoft SharePoint Server 2007 Backup and Recovery -397a-4ffc-8e2b-b2b10425be06 APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Content APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Search_WS200 APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Content_ b 07fd4d2e9c2a 3ab47ca2361c" APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharedServices1_DB APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharedServices1_Sear ch_db APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Search_WS2 APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Search_WS2-temp Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. Server 3 Server 3 runs the following services: Central Administration Document Conversions Launcher Service Document Conversions Load Balancer Service Office SharePoint Server Search Windows SharePoint Services Help Search Windows SharePoint Services Incoming Windows SharePoint Services Web Application Server 3 has the following roles: Web front-end server Windows SharePoint Services Help Search Office Sharepoint Server Search Index and Search server Query server Server 3 The output for Server 3 if registered is as follows: SYSTEM COMPONENTS:\Microsoft Office SharePoint Search 208 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

209 Microsoft SharePoint Server 2007 Backup and Recovery Conclusion In this example, the following save sets are backed up on each server. Table 38 Example: Minimum required save sets to be backed up Type of backup data Server 1 Minimum required save sets to be backed up Take individual backups of all these save sets: APPLICATIONS:\Microsoft Office SharePoint Services SYSTEM COMPONENTS:\ C:\ D:\ Note: If the client is using a hardware backup with a Data Mover, then this combination might fail because both hardware and software backup operations are used. Note: It is required to register the Windows SharePoint Services VSS writer on one of the web front servers in the farm. In this example, the Windows SharePoint Services VSS writer on Server 1 has been registered. Server 2 Server 3 Take individual backups of all these save sets: APPLICATIONS:\SqlServerWriter SYSTEM COMPONENTS:\ C:\ (All Volumes) D:\ (All Volumes) Take individual backups of all these save sets: SYSTEM COMPONENTS:\ C:\ (All Volumes) D:\ (All Volumes) SharePoint 2007 writers Table 39 on page 209 list the writers supported by SharePoint 2007:. Table 39 List of supported SharePoint 2007 writers SharePoint server SharePoint writer Description SharePoint 2007 Microsoft SharePoint 2007 provides VSS writers SqlServer Writer Windows SharePoint Services VSS Writer SharePoint Search Writer Office Server Search Writer The writer for SQL databases The writer for SharePoint 2007, which runs on the web front-end The writer for SharePoint 2007 search The writer for Microsoft Office Server search Overview 209

210 Microsoft SharePoint Server 2007 Backup and Recovery Performing SharePoint 2007 backups This section provides information that is needed to back up SharePoint 2007: SharePoint 2007 application information variable settings on page 210 URL encoding for SharePoint save sets on page 210 Specifying SharePoint 2007 save sets for application data on page 212 Displaying valid SharePoint 2007 data save sets on page 212 Configuring SharePoint 2007 backups on page 213 IMPORTANT Any major changes made to the SharePoint configuration or database structure requires a full backup. For example, if a full farm backup is performed on Monday, and then a new content database is added on Tuesday, a full backup needs to be performed to keep the backups up-to-date. The save set list also needs to be updated to include the new SharePoint objects. SharePoint 2007 application information variable settings Table 40 on page 210 lists the variables that can be specified in the application information attribute of the client resource. Table 40 SharePoint application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value Specifies the snapshot service provider name. vss This value is required. NSR_DATA_MOVER=value application information attribute Specifies the hostname of the NMM client that mounts the snapshot from NMM client to the proxy host. The host can be either a local host or a proxy client host. Note: This attribute should be used only for hardware backups. The local host The proxy client hostname Consider the following: If no value is typed, 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 SQL client resource, use a proxy client. URL encoding for SharePoint 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 210 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

211 Microsoft SharePoint Server 2007 Backup and Recovery 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 Table 41 on page 211 lists the most commonly used special characters and their URL values. Table 41 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 Performing SharePoint 2007 backups 211

212 Microsoft SharePoint Server 2007 Backup and Recovery Specifying SharePoint 2007 save sets for application data Specify the SharePoint 2007 data save sets in the Save Set attribute of a client resource. Table 42 on page 212 lists the SharePoint 2007 save set syntax that specifies the supported types of SharePoint 2007 data. Table 42 SharePoint save set syntax Type of backup data SharePoint databases on SQL server Full SharePoint backup SharePoint content database SharePoint Search Index and SharePoint Content Index Save set syntax APPLICATIONS:\SqlServerWriter APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS:\SqlServerWriter\Mars1%5CInsta ncename\database_name SYSTEM COMPONENTS:\ IMPORTANT For SharePoint 2007 standalone backup and recovery, when the APPLICATIONS:\Microsoft Office SharePoint Services\instance\database save set is used, it automatically includes all the local dependent SQL save sets, like SYSTEM COMPONENTS: \sql embedded\instance\database for embedded SQL server and APPLICATIONS:\SqlServerWriter\instance\database for any other SQL server. Do not specify the SQL save sets separately. Displaying valid SharePoint 2007 data save sets To display a list of the SharePoint 2007 save sets that are available for backup: 1. Open a command prompt on the application server. 2. From the command prompt, type the following command to list the valid application data save set names: nsrsnap_vss_save -? 3. Press Enter: Observe the output to determine the save sets that can be add to the Save Set attribute of the client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. The application data save sets that are available for backup are listed in a format similar to the following: APPLICATIONS:\Microsoft Office SharePoint Services 212 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

213 Microsoft SharePoint Server 2007 Backup and Recovery Configuring SharePoint 2007 backups Ensure that the following are take care of before configuring SharePoint 2007 backups: Install the NMM client on each machine in the SharePoint farm. For distributed configurations, register the SharePoint writer on only one of the web front-end servers. This web front-end server will be included in the NetWorker backup schedule, and will be used to perform any recoveries. Create client resources for each web front-end servers and SQL servers in the SharePoint farm. Set the save set syntax reported by nsrsnap_vss_save.exe -? in the client resources of each web front-end servers and SQL servers: SharePoint save sets: APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS:\Microsoft Office Search APPLICATIONS:\Microsoft Office SharePoint Search SQL save set: APPLICATIONS:\SqlServerWriter Based on backup strategies and requirements, include ALL or System Volumes(C:\, D:\, and so on), and SYSTEM COMPONENTS:\ in save set list. Put the SharePoint and SQL server client resources in the same group to avoid inconsistencies in SharePoint data. Do not put more than one instance of a client resource in the same group. APPLICATIONS:\ and file system save sets can be in different groups. To configure an SharePoint 2007 backup, perform the following tasks outlined in Table 43 on page 213. Table 43 Tasks for SharePoint 2007 backups Tasks 1. Enable services for backup on page 214 Considerations Several services must be enabled and started on the computers where the VSS writers are run or SharePoint search activities are being performed, or else backup fails. 2. Schedule backup NMM provides full backup, and backup of individual content databases, which allows you to protect your SharePoint farm with individual content database backups between full backups. Consider configuring separate backup schedules for full backups and individual content database backups. Perform the following tasks for scheduling a backup as described the EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide: 1. Configure a backup schedule 2. Configure a backup group Note: All the SharePoint hosts must be in the same NetWorker group resource and only one instance of each client must be present in the group. 3. Configure a SharePoint 2007 client resource on page 215 Create the client resource and then perform the backup. Performing SharePoint 2007 backups 213

214 Microsoft SharePoint Server 2007 Backup and Recovery IMPORTANT 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. or - The SYSTEM COMPONENTS:\ save set along with the system volume, for example C:\. Enable services for backup All of the following services must be enabled and started on the computers where the VSS writers will be run, or else backup will fail: Windows SharePoint Services VSS Writer that runs on the web front-end computer only SQLserver services VSS writer that runs on any computer that contains the Configuration database or one or more content databases In addition, the following services should already be enabled and started on the computers where SharePoint search activities are being performed. There will be VSS Writers associated with them: Office SharePoint Server Search Windows SharePoint Server Search Note: On a stand-alone farm, all of these writers and services run on one computer. In a distributed farm, the SQL server and SharePoint servers may run on separate computers. The service for the writers must be enabled on the computer running the service. To register the SharePoint writer for distributed configurations: 1. The SharePoint writer must be registered on a web front-end server by using the command line STSADM.exe. Go to the following location for the STSADM.exe: C:\Program Files\Common files \Microsoft Shared \Web server extension\12\bin 2. Type the following command to register the SharePoint writer: Run STSADM.EXE -o registerwsswriter To start the SharePoint and SQL server writers, complete the following steps on the computer where the writer is registered: IMPORTANT These steps must be completed on each machine where the VSS writers will be run. 1. Start Windows Services by using the appropriate steps for your operating system: a. In Windows server 2003, click Start >Control Panel >Administrative Tools. b. Double-click Services. c. In Windows server 2008, click Start > Administrative Tools >Services. 2. Right-click the following service and then click Properties: SQLServer Services VSS Writer 214 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

215 Microsoft SharePoint Server 2007 Backup and Recovery Note: The SQLServer Services VSS Writer is available on any machine that contains the configuration database or one or more content databases. 3. In Startup type, click Automatic, and then click OK. 4. Right-click the writer you just enabled, and then click Start. 5. For each of the listed writers present on the computer, repeat step 2 to step 4. Note: The SQLServer Services VSS Writer is available on any machine that contains the configuration database or one or more content databases. 6. Repeat the following steps as required on each computer in the farm to enable and start the appropriate writers on each computer: a. Start Windows Services by using the appropriate steps for your operating system: In Windows server 2003, click Start > Control Panel > Administrative Tools, and then double-click Services. In Windows server 2008, click Start > Administrative Tools > Services. b. For each of the listed writers present on the computer, repeat Repeat step 2 to step Once these writers are registered and started, you can schedule a backup. 8. After scheduling the backup, configure a SharePoint 2007 client resource. Configure a SharePoint 2007 client resource on page 215 describes how to configure a SharePoint 2007 client resource. Configure a SharePoint 2007 client resource For each machine in the SharePoint farm, create a client resource in NetWorker Management Console, and assign it to the same backup group. The steps to create the client resource depend on whether it is a stand-alone SharePoint farm, distributed SharePoint farm, and a full or component backup: Configuring a SharePoint client resource to back up a stand-alone farm on page 216. Configuring a SharePoint client resource to perform a full backup of a distributed farm on page 217. In a distributed SharePoint farm, one or more SharePoint services may be located remotely on separate machines from the SharePoint web front-end. In order for NetWorker to successfully save all client resources in the SharePoint farm: Backups must be initiated through the client resource on each remote machine, as well as the web front-end, and all client resources must be in the same NetWorker group. If the backup is only initiated through the web front-end, recovery will fail because even though NMM displays all of the SharePoint farm save sets on the web front-end, the remote client backups were never performed. Performing SharePoint 2007 backups 215

216 Microsoft SharePoint Server 2007 Backup and Recovery Configuring a SharePoint client resource to back up a stand-alone farm In a stand-alone SharePoint configuration, only one component is required in the save set to perform a full backup. To configure a SharePoint client resource to back up a stand-alone farm: 1. In the Administration window 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. Note: 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. Ensure that the Scheduled Backups attribute has been checked (enabled). 9. In the Save Set attribute, specify the components to be backed up: Place multiple entries on separate lines. To back up all SharePoint server data, where all server components are located on the same machine, specify the save set name: APPLICATIONS:\Microsoft Office SharePoint Services Note: The SQL system databases are not backed with this save set; only the databases associated with the SharePoint farm are backed up. 10. If needed, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource. URL-encoded values are used to represent special characters such as the backslash (\). A table of values is provided in Table 41 on page 211. Note: If a save set is copied from the nsrsnap_vss_save -? output, it will already include the URL encoding. 11. 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. 12. For the Schedule attribute, select a backup schedule. 13. Click the Apps & Modules tab. 14. In the Access area, leave the Remote user and Password fields empty. 216 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

217 Microsoft SharePoint Server 2007 Backup and Recovery 15. In the Backup command attribute, type the backup command. For VSS backups, type the following command: nsrsnap_vss_save.exe 16. In the Application information attribute, type the following variable and value: NSR_SNAP_TYPE=vss Type each SharePoint application variable setting and it values on a separate line. These settings are described in Table 40 on page Click the Globals (1 of 2) tab: a. In the Aliases attribute, type the NETBIOS name for the client. Note: 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. b. Click OK. Configuring a SharePoint client resource to perform a full backup of a distributed farm In a distributed configuration, you must set up a client resource for the web front-end server where the Windows SharePoint Services VSS Writer was enabled using STSADM.exe. You do not need a client resource on each web front-end unless you are implementing a system-level disaster recover backup schedule for these hosts. The client resource can specify to perform a full farm backup, or to back up a content database. To configure a SharePoint client resource to perform a full backup of a distributed farm: 1. For each machine in the farm: a. In the Administration window of the NetWorker Management Console, click Configuration. b. In the expanded left pane, select Clients. c. From the File menu, select New. d. In the Name attribute, type the hostname of the NetWorker client computer. e. In the Comment attribute, type a description. f. If you are creating multiple client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. g. 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. h. 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. i. Select the Scheduled Backups attribute. Performing SharePoint 2007 backups 217

218 Microsoft SharePoint Server 2007 Backup and Recovery Note: For a distributed farm backup, add all client resources for the farm members to the same NetWorker backup group. 2. In the Save Set attribute, specify the components to be backed up: Note: Each machine in a distributed farm requires a separate client resource, and the client resource for a given machine should only contain the SharePoint save sets on that machine. For the machine where the SharePoint VSS writer is registered: a. Specify the save set name: APPLICATIONS:\Microsoft Office SharePoint Services b. Proceed to the next step. For the SQL server machine: a. Specify the save set name: APPLICATIONS:\SqlServerWriter b. Proceed to the next step. For all other SharePoint machines: a. Determine the save sets available on the specific machine by following the steps in Displaying valid SharePoint 2007 data save sets on page 212. b. Specify the available save set names for that machine. c. Proceed to the next step. Note: The Search and Index databases cannot be backed up by themselves. Search/Index databases are backed up as part of a Farm-level SharePoint backup. 3. If needed, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource. URL-encoded values are used to represent special characters such as the backslash (\). A table of values is provided in Table 41 on page 211. Note: If a save set is copied from the nsrsnap_vss_save -? output, it will already include the URL encoding. 4. For the Group attribute, select the backup group to which this client resource will be added. Note: If the 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. 5. For the Schedule attribute, select a backup schedule. 6. Click the Apps & Modules tab. 7. In the Access area, leave the Remote user and Password fields empty. 8. In the Backup command attribute, type the backup command. For VSS backups, type the following command: nsrsnap_vss_save.exe 218 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

219 Microsoft SharePoint Server 2007 Backup and Recovery 9. In the Application information attribute, type the following variable and value: NSR_SNAP_TYPE=vss Type each SharePoint application variable setting and it values on a separate line. These settings are described in Table 40 on page Click the Globals (1 of 2) tab: a. In the Aliases attribute, type the NETBIOS name for the client. Note: 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. b. Click OK. Performing SharePoint 2007 farm hardware backups VSS hardware providers allow you to create shadows without imposing a load on the local client, or production server. For the purposes of VSS, the snapshot is referred to as a shadow. You also have an option to make the shadow transportable, which allows you to mount, or import, the shadow on another client. If a shadow is not marked as transportable, you will not be able to mount the shadow and will not be able to perform rollback recovery. When using NMM, the system uses the default provider to create the shadow. If you have installed a hardware provider, this becomes the default provider. The NMM software uses the hardware provider in place of Microsoft VSS. The VSS hardware provider takes precedence over the Microsoft Software Shadow Copy provider. EMC has providers for Symmetrix and CLARiiON. Using these specific providers allows you to take hardware snapshots of these arrays. When performing a hardware backup of a SharePoint 2007 farm, ensure that the SQL server and that the SharePoint application data are installed on a LUN from CLARiiON or other hardware that allows hardware snaps to be taken. If not, backup will use a software snapshot. That is, if the installation is on a local drive like C:\, only then a software snapshot will be performed. Note: Mixing hardware and software providers will cause the backup to fail. Perform the following steps: 1. Configure a proxy node or proxy storage node backup on page Configure a client resource for the proxy client on page Configure a client resource for the production host on page 223 Configure a proxy node or proxy storage node backup This section details how to configure a proxy node or a proxy storage backup with CLARiiON and Symmetrix hardware providers. CLARiiON hardware provider The minimum configurations for proxy node backup and proxy storage node backup with the EMC CLARiiON hardware provider are the same. Performing SharePoint 2007 farm hardware backups 219

220 Microsoft SharePoint Server 2007 Backup and Recovery Perform the following configuration steps: 1. Ensure that the proxy node host and the production host have LUNs from the same CLARiiON box. 2. Ensure that the NMM client is installed on both production host and proxy node. 3. The following software must be installed on both the production and proxy hosts: EMC PowerPath with a license EMC Solution Enabler with the symapi_licenses.dat file copied in C:\ProgramFiles\EMC\symapi\config NaviAgent Note: The version of the NaviAgent must match that of FLARE on the CLARiiON. NaviCli Note: When installing NaviCLi, you are prompted to provide the CLARiiON credentials. Ensure that you provide the correct CLARiiON login details. Admsnap 4. Run the following commands on the production host: a. Run this command: C:\Program Files\EMC\SYMCLI\bin> symcfg authorization add -host <CLARiiON IP> -user <CLARiiON Username> -password <CLARiiON Password> For example: symcfg authorization add -host user powersnap -password password symcfg authorization add -host user powersnap -password password b. Add both the IPs of CLARiiON. c. Run this command: C:\Program Files\EMC\Navisphere CLI>NaviSECCli -user <Username> -Scope 0 -address <CLARiiON IP> -AddUserSecurity For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity d. After running this command, you are prompted for a password. Ensure to use the CLARiiON password. e. Add the second IP of CLARiiON and provide the password again. For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity 220 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

221 Microsoft SharePoint Server 2007 Backup and Recovery 5. Run the following commands on the proxy host: a. Run this command: C:\Program Files\EMC\SYMCLI\bin> symcfg authorization add -host <CLARiiON IP> -user <CLARiiON Username> -password <CLARiiON Password> For example: symcfg authorization add -host user powersnap -password password symcfg authorization add -host user powersnap -password password b. Add both the IPs of CLARiiON. c. Run this command: C:\Program Files\EMC\Navisphere CLI>NaviSECCli -user <Username> -Scope 0 -address <CLARiiON IP> -AddUserSecurity For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity d. After running this command, you are prompted for a password. Ensure to use the CLARiiON password. e. Add the second IP of CLARiiON and provide the password again. For example: NaviSECCli -user powersnap -Scope 0 -address AddUserSecurity 6. For the production host: a. Add the NaviSECCli.exe entry under environmental variables: For example: C:\ProgramFiles (X86)\EMC\Navisphere CLI\NaviSECCli.exe b. Reboot the production host. 7. For the proxy host: a. Add the NaviSECCli.exe entry under environmental variables: For example: C:\ProgramFiles (X86)\EMC\Navisphere CLI\NaviSECCli.exe b. Reboot the proxy host. 8. Perform the following NetWorker server side configuration for proxy backup: a. Create a proxy client resource on the NetWorker server side. b. After creating both the production and proxy client resources, add the following information on both production client resource and proxy client resource properties: Select Production Client Resource properties > Globals(2 of 2) > Remote Access > SYSTEM@proxy host name Select Proxy Client Resource properties > Globals(2 of 2) > Remote Access > SYSTEM@production host name Performing SharePoint 2007 farm hardware backups 221

222 Microsoft SharePoint Server 2007 Backup and Recovery c. Specify the following Exchange application information on production client resource to perform proxy backup. The attributes are: NSR_SNAP_TYPE=vss NSR_DM_PORT=6728 [this value is default] NSR_DATA_MOVER=<Proxy host name> The EMC NetWorker Module for Microsoft Applications and EMC CLARiiON: Implementing Proxy Node Backups Release 2.3 Technical Notes provides more information on this topic. Symmetrix hardware provider The minimum configurations for proxy node backup and proxy storage node backup with the Symmetrix hardware provider are the same. Perform the following configuration steps: 1. Ensure that the proxy storage node host and the production host have LUNs from the same Symmetrix box. 2. Ensure that the NMM client is installed on both production and Data Mover hosts. 3. The following software must be installed on both the production and proxy hosts: EMC PowerPath with a license EMC Solution Enabler with the symapi_licenses.dat file copied in C:\ProgramFiles\EMC\symapi\config 4. Create a device and attach both STD and BCV to that device. After attaching both STD and BCV, establish the connection between STD and BCV. The EMC NetWorker Module for Microsoft Applications and EMC Symmetrix: Implementing Proxy Node Backups Release 2.3 Technical Notes provides more information on this topic. Configure a client resource for the proxy client To create a client resource for both the production and proxy client resources: 1. In the Administration window 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 either of the following: The fully qualified domain name (FQDN) 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. Ensure that the Scheduled Backups attribute has been checked. 222 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

223 Microsoft SharePoint Server 2007 Backup and Recovery 7. In the Save Set attribute: a. Specify the components to be backed up. b. Place multiple entries on separate lines, by using the save set names in Table 40 on page Click the Globals (1 of 2) tab: a. Verify that the Aliases attribute displays the NETBIOS name for the client. This name should have already been filled in automatically. Note: 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. b. Click OK. Configure a client resource for the production host To create a client resource for both the production and proxy client resources: 1. In the Administration window 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 either of the following: The FQDN or 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 the rolled-over data is available for quick access. Ensure that the browse policy is long enough for your expected recovery needs: If your recovery needs are beyond the browse policy, an index recovery can be performed and should be the preferred first step. If index recovery is not possible, you can scan tapes to rebuild the index but this should be the last option. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long the rolled-over data is available for restore in the media database. The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details. 8. Ensure that the Scheduled Backups attribute has been checked (enabled). 9. In the Save Set attribute: a. Specify the components to be backed up. b. Place multiple entries on separate lines by using the save set names in Table 40 on page 210. Performing SharePoint 2007 farm hardware backups 223

224 Microsoft SharePoint Server 2007 Backup and Recovery 10. If required, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource. Table 41 on page 211 provides the URL-encoded values for SharePoint save sets that are used to represent special characters, such as the backslash (\) and a table of values: 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 when naming SQL server databases. For example, to backup a SharePoint SQL server database: APPLICATIONS:\SqlServerWriter 11. For the Group attribute, select the back up group to which this client resource will be added. Note: The backup group must be a snapshot group. 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. 12. For the Schedule attribute, select a backup schedule. 13. Click the Apps & Modules tab. 14. In the Access area, leave the Remote user and Password fields empty. 15. 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 16. In the Application information attribute: a. Type the following variables and values: NSR_SNAP_TYPE=vss NSR_ALT_PATH=<mount_path_on_proxy_client> NSR_DATA_MOVER=<proxy_client_hostname> NSR_DM_PORT=6728 Note: The default value in NMM installation is b. If you changed the DM Port number to a different value in your NMM client configuration or installation, use that value for NSR_DM_PORT. 17. Click the Globals (1 of 2) tab: a. Verify that the Aliases attribute displays the NETBIOS name for the client. This name should have already been filled in automatically. Note: 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. 224 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

225 Microsoft SharePoint Server 2007 Backup and Recovery b. Click OK. 18. Click the Globals (2 of 2) tab: a. Select Production Client Resource properties > Globals(2 of 2) > Remote Access > host name. b. Select Proxy Client Resource properties > Globals(2 of 2) > Remote Access > host name. c. Click OK. Performing SharePoint 2007 recovery You can perform the following types of recovery: Full recovery of a stand-alone SharePoint farm on page 225 Full recovery of a distributed SharePoint farm on page 226 Recovery of individual SharePoint content databases on page 227 Recovery of SharePoint Search/Content Indexes on page 227 Rollback of SharePoint SQL databases on page 228 IMPORTANT In all SharePoint recoveries, the recovery process must be performed in the following sequence: 1. C:\ 2. SYSTEM COMPONENTS:\ 3. Configuration database 4. Content databases Data loss will occur if this sequence is not followed in order. When a SharePoint Configuration database is recovered as part of the recovery of an entire farm, all Content databases in that farm must also be recovered in order for the Microsoft SharePoint Writer to ensure consistency. Previously, this was considered a best practice, but Microsoft states that this is a requirement. An individual Content database can still be recovered if the recovery is not part of an entire farm recovery. Recovery of individual SharePoint content databases on page 227 provides steps for recovering individual SharePoint Content databases. Full recovery of a stand-alone SharePoint farm To perform a full recovery of Microsoft Office SharePoint Portal server 2007: 1. Open NetWorker Module for Microsoft Applications. 2. Recover the SQL configuration database and the content database. 3. In the navigation tree, expand the APPLICATIONS folder and select Windows SharePoint Services VSS Writer. 4. From the System Recover Session toolbar, click Start Restore. Recovery proceeds to completion. Details about the recovery appear in the monitoring page. Performing SharePoint 2007 recovery 225

226 Microsoft SharePoint Server 2007 Backup and Recovery Full recovery of a distributed SharePoint farm To perform a full recovery of Microsoft Office SharePoint Portal server 2007: 1. Open NetWorker Module for Microsoft Applications on the web front-end that was used to perform the backups of the SharePoint 2007 Writer. 2. In the navigation tree, expand the APPLICATIONS folder and select Windows SharePoint Services VSS Writer. 3. From the System Recover Session toolbar, click Start Restore. The Restore Remote Dependencies dialog box appears, alerting you to go to the specified hosts and start the recovery processes. Figure 52 on page 226 shows an example of several remote hosts that must be recovered. In this example, though 13 service components are displayed, they are located on three remote hosts. You would need to go to each of those three hosts once to recover all 13 services. Figure 52 Restore Remote Dependencies dialog box 4. At each remote host listed in the Restore Remote Dependencies dialog box: a. Open NetWorker Module for Microsoft Applications. b. In the navigation tree, locate and mark the items. c. Restore the items. 5. After all remote hosts have been recovered: a. Return to NetWorker Module for Microsoft Applications on the web front-end. b. Click Continue in the Restore Remote Dependencies dialog box. Recovery proceeds to completion. Details about the recovery display in the monitoring page. 226 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

227 Microsoft SharePoint Server 2007 Backup and Recovery Recovery of individual SharePoint content databases One or more content databases can be recovered after the configuration database has been restored. In the previous releases of NMM, a user was unable to select only individual SharePoint content databases for restore. When any content database was selected, the corresponding configuration and generic databases were also selected for recovery. This release of NMM provides the ability to select individual SharePoint content databases for recovery. To perform a recovery of one or more individual Microsoft Office SharePoint server 2007 content databases: 1. Open NetWorker Module for Microsoft Applications on the web front-end that was used to perform the backups of the SharePoint 2007 Writer. 2. In the navigation tree, expand the APPLICATIONS folder and select the Windows SharePoint Services VSS Writer. 3. Expand the Windows SharePoint Services VSS Writer folder until you find a database folder with an entry similar to the following example: APPLICATIONS:\Microsoft Office SharePoint Services\Mars1\db_1 where: Mars1 is the name of the server db_1 is the name of the database. 4. Select the databases to restore. 5. From the System Recover Session toolbar, click Start Restore. The Restore Remote Dependencies dialog box appears, alerting you to go to the specified hosts and start the recovery processes. 6. At the remote host: a. Open NetWorker Module for Microsoft Applications. b. In the navigation tree, locate and mark the items. c. Restore the items. 7. Return to NetWorker Module for Microsoft Applications on the web front-end, and click Continue in the Restore Remote Dependencies dialog box. Recovery proceeds to completion. Details about the recovery appear in the monitoring page. Recovery of SharePoint Search/Content Indexes IMPORTANT When the Search/Content Index folder is backed up, only the APPLICATIONS folder is backed up and available for recovery. The Config and Office servers folders are not backed up and cannot be recovered. To perform a full recovery of Microsoft Office SharePoint server 2007: 1. Open NetWorker Module for Microsoft Applications. 2. In the navigation tree, expand the SYSTEM COMPONENTS folder and select SPSearch VSS Writer and OSearch VSS Writer. Performing SharePoint 2007 recovery 227

228 Microsoft SharePoint Server 2007 Backup and Recovery 3. From the System Recover Session toolbar, click Start Restore. The Restore Remote Dependencies dialog box appears, alerting you to go to the specified hosts and start the recovery process. 4. Go to the remote host, and verify that the configuration database needs to be recovered. If it needs to be recovered, then recover it. 5. Return to NetWorker Module for Microsoft Applications and click Continue in the Restore Remote Dependencies dialog box. Recovery proceeds to completion. Details about the recovery appear in the monitoring page. Rollback of SharePoint SQL databases Consider the following: NMM does not support a SharePoint SQL rollback. SharePoint content databases are backed up by NMM, but the master SQL database is not. The master database can be backed up separately and then used in a SharePoint SQL rollback. To back up SharePoint for rollback of SharePoint SQL databases, take a backup of the master database each time an NMM SharePoint backup is taken. To perform a full rollback, restore the backups created by the NMM SharePoint backup and then restore the SharePoint SQL master database. Performing SharePoint 2007 disaster recovery One of the keys to successful disaster recovery is making sure you have a full and complete backup available before disaster strikes. Plan your backup schedule and strategy to ensure that you always have an up-to-date backup available in case of disaster. SharePoint disaster recovery is more than restoring a full backup. NMM backs up the SharePoint configuration and content databases, and the query and index servers. In a disaster recovery, you need to restore the IIS, SQL servers, and SharePoint servers that make up the farm, including file systems and registries of each machine. This section contains the following: Disaster recovery planning on page 228 Performing a disaster recovery on page 229 Disaster recovery planning The following sections describe the steps you must take as part of your disaster recovery plan: SharePoint server backup list on page 229 Additional requirements for successful SharePoint disaster recovery on page EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

229 Microsoft SharePoint Server 2007 Backup and Recovery SharePoint server backup list Table 44 on page 229 lists each server type in the SharePoint farm and the items that should be backed up on that server as part of your disaster recovery plan. Best practices on page 38 in Chapter 1, Microsoft SQL Server Backup and Recovery, provides the considerations for configuring groups. Table 44 SharePoint server backup list for disaster recovery Server type Web front-end Web front-end without Microsoft Office Windows SharePoint Services VSS Writer Search server SQL server Stand-alone SharePoint server Items to back up SYSTEM COMPONENTS:\ All System Volumes, for example, C:\, D:\, APPLICATIONS:\Microsoft Office SharePoint Services\ SYSTEM COMPONENTS:\ All System Volumes, for example, C:\, D:\, SYSTEM COMPONENTS:\ All System Volumes, for example, C:\, D:\,. SYSTEM COMPONENTS:\ All System Volumes, for example, C:\, D:\, All SQL databases, including the master database SYSTEM COMPONENTS:\ All System Volumes, for example, C:\, D:\, All system databases, including the master database APPLICATIONS:\Microsoft Office SharePoint Services\ Additional requirements for successful SharePoint disaster recovery The following conditions and requirements must be met for a successful disaster recovery: The SYSTEM COMPONENTS:\ save set and all system volumes must be recovered at the same time to ensure consistency on the system. For systems with remote dependencies, the remote machines must be recovered first. Once all remote machines have been recovered, the primary system can then be recovered. Performing a disaster recovery To perform a disaster recovery: 1. Back up the following: APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS:\SqlServerWriter C:\ SYSTEM COMPONENTS:\ In addition, you may want to back up various servers, folders, and other components as described in Disaster recovery planning on page 228. Performing SharePoint 2007 disaster recovery 229

230 Microsoft SharePoint Server 2007 Backup and Recovery 2. For Windows 2003 with NetWorker 7.5 SP3, 7.5 SP4, or 7.6 SP1: a. Prepare a setup similar to the one that is currently being used. Ensure that you use the same: OS Service packs IP address Hostname Domain b. Install the same versions of SQL server and SharePoint server as currently being used on the new setup. 3. For Windows 2008 and Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery. Chapter 10, Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM provides details. 4. Recover the following in the specified order: a. C:\ b. SYSTEM COMPONENTS:\ c. SQL data 5. Perform a full recovery of the SharePoint writer. IMPORTANT Ensure to restart the system after performing a disaster recovery of SharePoint. Currently, a message about the completion of disaster recovery and the need to restart the system appears in the Monitor window and the logs. Check the Monitor page and the logs before restarting the system. Keeping backups and recoveries in sync Set up a consistent schedule of full farm-level backups. If backing up individual content databases, schedule these in between the full farm-level backups. However, whenever there are significant changes to the SharePoint farm, you should immediately update the NetWorker backup configuration with any new SharePoint objects, and perform a new full farm-level backup as soon as possible: Configuration or database structure changes Any major changes made to the SharePoint configuration or database structure require an update of the save set lists and a full backup. For example, if a full farm backup is performed on Monday, and then the user adds a new content database on Tuesday, a full backup needs to be performed to keep the backups up-to-date. For the full backup to be up-to-date, the NetWorker backup configuration must be manually updated to include the new database save sets. Out-of-sync expiration policies between clients In a distributed farm, a snapshot policy is specified at the group level, to apply uniformly to all SharePoint clients in a group. The snapshot policy is then applied to each client independently. As long as the farm is working properly in a steady state, the snapshot expiration policy for the group and for each client stay in sync. But if one of the clients fails, and you do a manual rollover or a delete on one of the 230 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

231 Microsoft SharePoint Server 2007 Backup and Recovery hosts, the rest of the hosts fall out-of-sync. When they get out-of-sync, some of the snapshots will expire and a full recovery is no longer possible from those snapshots. To bring the snapshots up-to-date, run a new full backup. A full backup of a distributed farm requires special steps in configuring the client resources and running the backup. Configuring a SharePoint client resource to perform a full backup of a distributed farm on page 217 provides details. Best practices for disaster recovery The following best practices can help you get the most out of disaster recoveries: Check that all services of SharePoint are started; otherwise, backup fails with the following error: NMM... ERROR. Writer SharePoint Services Writer with local dependent writer id {comp Content Index _ SPSearch cannot be found. CONTINUE PROCESSING. Start Windows SharePoint Services Search. This service is not started automatically. Ensure that search is configured on the server. Run the following command to list the applicable save sets: nsrsnap_vss_save -? Note: If it does not list the save set, register the Windows SharePoint Services by using the STSADM.exe. Ensure that you remove the inverted commas when you copy the saveset name from the output. IMPORTANT NMM backup will not run unless Windows SharePoint Services is registered. Go to the path C:\Program Files\Legato\nsr\bin and run nsrsnap_vss_save -? The applicable save sets are displayed as follows: C:\Program Files\Legato\nsr\bin>nsrsnap_vss_save -? List of valid saveset entries for APPLICATIONS on client IISDELL3-W2K8... Initializing data to display... APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8 APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\content Database Communication Depends on 'APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8 \Communication' on Client 'IISDELL3-W2K8'. APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\content Database Custom_list Depends on 'APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8 \Custom_list' on Client 'IISDELL3-W2K8'. APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\content Database Library Depends on 'APPLICATIONS:\SqlServerWriter \IISDELL3-W2K8\Library' on Client 'IISDELL3-W2K8'. APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\content Database new Depends on 'APPLICATIONS:\SqlServerWriter \IISDELL3-W2K8\new' on Client 'IISDELL3-W2K8'. Best practices for disaster recovery 231

232 Microsoft SharePoint Server 2007 Backup and Recovery APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\content Database WSS_Content Depends on 'APPLICATIONS:\SqlServerWriter \IISDELL3-W2K8\WSS_Content' on Client 'IISDELL3-W2K8'. APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\content Database SharePoint_AdminContent_fe6e b1-412a-952e-9645 Depends on 'APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8 \SharePoint_AdminContent_fe6e b1-412a-952e-9645df879a43' on Client 'IISDE APPLICATIONS:\Microsoft Office SharePoint Services \iisdell3-w2k8\spsearch Content Index Catalog Depends on 'SYSTEM COMPONENTS:\Microsoft Office SharePoint Search\ContentIndex_SPSearch' on Client 'IISDELL3-W2K8'. APPLICATIONS:\SqlServerWriter APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8 APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\master APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\model APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\msdb APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8 \SharePoint_Config APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\SharePoint_AdminConten t_fe6e b1-412a-952e-9645df879a43 APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\WSS_Search_iisdell3-w2 k8 APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\Communication APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\Library APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\Custom_list APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\new APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\SharePoint_Config_2k8_ x86 APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\SharePoint_AdminConten t_4527f2d6-377c-4136-a a1789e15 APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\WSS_Search_SCTESTVM3 APPLICATIONS:\SqlServerWriter\IISDELL3-W2K8\WSS_Content 68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success. Ensure to apply SQL server 2005 Service Pack 2; otherwise, the backup may fail. For proxy backup to work, ensure that the Data Mover machine has the same configuration as the source machine. For example, if farm setup is on Windows 2008, then the Data Mover host should also have Windows Group inactivity timeout must be set to zero, especially for farm-based backups that use a proxy host. For farm hosts that use the same proxy server, the import, deport, and delete operations that occur on the proxy are serialized. This introduces additional delay into the overall group. The actual delay depends on the number of LUNs for each NMM client that are imported on the proxy. Setting the inactivity timeout to zero insures that the Group is not canceled during the period when NMM clients are waiting for their turn to perform proxy operations. Perform a full backup of SharePoint after every successful recovery. Also, a full backup should be performed after the SharePoint farm has been changed in any way. Ensure that all SharePoint databases are mounted before backing up the application server. Unmounted databases will not be backed up. 232 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

233 Microsoft SharePoint Server 2007 Backup and Recovery For copy-on-write versus mirroring, do not save a large or fast-changing database with copy-on-write snapshot technology. Fast changing data contains more writes. Instead use split mirror snapshot technology like CLARiiON clones or Symmetrix business continuance volumes. Sometimes after recovery of the SharePoint Config database, the Central Admin local cache is not in sync with the SharePoint Config database. If this occurs, clear the file system cache on all servers in the server farm on which the Windows SharePoint Services Timer service is running. The Microsoft Knowledgebase article on the Microsoft website provides steps for clearing the cache. Backing up SharePoint database by using NMM and NMSQL The advantages of backing up data using NMM and NMSQL include the use of full, differential, and incremental backups for SharePoint content databases and directed recoveries to alternate locations for use with third-party data mining applications. This procedure also allows direct SAN backups for SharePoint content databases using NetWorker dedicated storage node capabilities with NMSQL. For example, you could be using: One SharePoint Configuration database server, protected by NMM. One SharePoint Search database or index server, protected by NMM. One SharePoint or SQL content database cluster, protected by NMSQL and configured with dedicated storage node, SAN backups, and full or differential backups. The dedicated storage node can be created by installing NetWorker storage node and NMSQL on the host. Use the following procedure for backup: 1. Configure SharePoint Web Front-end and SharePoint Central Administration in NMM for backup. Use the command nsrsnap_vss_save -? and provide the save set from the command for the configuration. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. 2. Configure a separate group for SQL database backup through NMSQL. Backup is successful for both groups. Use the following procedure for recovery: 1. Ensure to stop all SharePoint services because recovery will fail when database is in use. 2. Start recovery of SharePoint database from Web Front-end. The dependency dialog box to recover SQL databases appears. 3. Recover SharePoint database from SharePoint Server Central Administration. The dependency dialog box to recover SQL databases appears. You must first recover SQL. 4. Recover SQL through NMSQL. 5. Recover all SQL databases protected by SharePoint. 6. Now continue to recover NMM SharePoint data on both Web Front-end and Central Administration. Backing up SharePoint database by using NMM and NMSQL 233

234 Microsoft SharePoint Server 2007 Backup and Recovery 234 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

235 9 Microsoft SharePoint Server 2010 Backup and Recovery This chapter includes the following topics: Overview Performing SharePoint 2010 backups Performing SharePoint 2010 recovery Performing SharePoint 2010 disaster recovery Microsoft SharePoint Server 2010 Backup and Recovery 235

236 Microsoft SharePoint Server 2010 Backup and Recovery Overview This chapter provides information specific to SharePoint 2010 backup and recovery by using NMM 2.3. IMPORTANT In addition to the content in this chapter, also review Chapter 8, Microsoft SharePoint Server 2007 Backup and Recovery, for details on backup and recovery procedures because the backup and restore workflows for Microsoft SharePoint 2007 are applicable to Microsoft SharePoint The disaster recovery procedures are the same for Microsoft SharePoint 2007 and Microsoft SharePoint This section provides the following information: New features in Microsoft SharePoint 2010 on page 236 Microsoft SharePoint 2010 support on Microsoft Windows server 2008 on page 237 Microsoft SharePoint server 2010 and SharePoint Foundation 2010 on page 237 Types of SharePoint server 2010 backup and recovery on page 237 NMM and Microsoft Office SharePoint 2010 farm configurations on page 238 SharePoint 2010 writers on page 238 New features in Microsoft SharePoint 2010 Review these new SharePoint 2010 features that are used for SharePoint data protection in NMM 2.3: Service applications Service applications are services that are shared across web applications within a farm (for example, Search and Excel Calculation Services). Some service applications can be shared across multiple farms: The Search service application includes multiple application components and multiple databases. The People service application includes multiple databases. Services in SharePoint 2010 In SharePoint server 2010, the number of services and corresponding databases is comparatively more than in previous releases of SharePoint. In Microsoft SharePoint 2010, services are no longer contained within a Shared Services Provider (SSP). Instead, the infrastructure for hosting services moves into SharePoint Foundation 2010 and the configuration of service offerings is much more flexible. Individual services can be configured independently and third-party companies can add services to the platform. The services are selectable and can be deployed individually in a farm. Services that are deployed are called service applications. Web applications can be configured to use only the services that are needed, rather than the entire set of services that are deployed. Multiple instances of a service can be deployed in a farm and be assigned unique names to the resulting service applications. Services can be shared across multiple Web applications within the same farm. 236 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

237 Microsoft SharePoint Server 2010 Backup and Recovery Microsoft SharePoint 2010 support on Microsoft Windows server 2008 NMM 2.3 provides support for Microsoft SharePoint 2010 on Microsoft Windows server 2008: Windows server 2008 R2 Standard Edition (x64) Windows server 2008 R2 Enterprise Edition (x64) Windows server 2008 SP2 Standard Edition (x64) Windows server 2008 SP2 Enterprise Edition (x64) Note: Microsoft SharePoint 2010 is not supported on 2008 SP2 (x86) and 2008 R2 (x86). Microsoft SharePoint server 2010 and SharePoint Foundation 2010 Microsoft SharePoint server 2010 and SharePoint Foundation 2010 is supported. In Microsoft SharePoint 2010, services are no longer contained within a Shared Services Provider (SSP). Instead, the infrastructure for hosting services moves into SharePoint Foundation 2010 and the configuration of service offerings is much more flexible: Individual services can be configured independently and third-party companies can add services to the platform. The services are selectable and can be deployed individually in a farm. Services that are deployed are called service applications. Web applications can be configured to use only the services that are needed, rather than the entire set of services that are deployed. Multiple instances of a service can be deployed in a farm and be assigned unique names to the resulting service applications. Services can be shared across multiple Web applications within the same farm. Types of SharePoint server 2010 backup and recovery For SharePoint server 2010 with Windows server 2008, NMM supports the following backup and recovery: Type of backup: SharePoint 2010 stand-alone farm backup SharePoint 2010 distributed farm backup Types of recovery: Individual content database recovery Individual web application recovery Search service application recovery Farm recovery IMPORTANT NMM 2.3 does not support SharePoint 2010 granular backup and recovery. Overview 237

238 Microsoft SharePoint Server 2010 Backup and Recovery NMM and Microsoft Office SharePoint 2010 farm configurations The topological setup for SharePoint 2010 farms are the same as SharePoint 2007 farms. Microsoft Office SharePoint 2007 farm configurations on page 205 provides details. SharePoint 2010 writers Table 45 Table 45 on page 238 list the writers supported by SharePoint 2010: List of supported SharePoint 2010 writers SharePoint server SharePoint writer Description SharePoint 2010 Microsoft SharePoint 2010 provides VSS writers. SPSearch4 VSS Writer OSearch14 VSS Writer SharePoint Services Writer The writer for SharePoint 2010 help search The writer for Microsoft Office server search The writer for SharePoint 2010, which runs on the web front-end IMPORTANT When registering the SharePoint 2010 writers using the stsadm.exe -o registerwsswriter command, ensure that this command is executed on each and every web front-end servers to backup the entire SharePoint 2010 farm. Note that this is unlike the SharePoint 2007 backup workflow where it is not necessary to run this command on all the web front-end servers but only on one web front-end server that is running the services. Performing SharePoint 2010 backups This section provides the following information: Specifying SharePoint 2010 application data save sets on page 238 Displaying valid SharePoint 2010 data save sets on page 239 Prerequisites for SharePoint 2010 backup on page 240 Performing SharePoint 2010 backup on page 240 Specifying SharePoint 2010 application data save sets The application data save sets for SharePoint 2007 are applicable for SharePoint 2010 without any changes in the syntaxes. The usage type for SharePoint 2010 writers, OSearch14 and SPSearch4 VSS writers, has changed from system data to user data. The save set syntax for OSearch14 and SPSearch4 VSS start with APPLICATIONS: \ and not SYSTEM COMPONENTS:\. 238 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

239 Microsoft SharePoint Server 2010 Backup and Recovery Specify the SharePoint 2010 data save sets in the Save Set attribute of a client resource. Table 46 on page 239 lists the SharePoint 2010 save set syntax that specifies the supported types of SharePoint 2010 data. Table 46 SharePoint save set syntax Type of backup data SharePoint databases on SQL server One SharePoint database on SQL server Full SharePoint backup SharePoint web front-end SharePoint component (content database name) Search Applications Save set syntax APPLICATIONS:\SqlServerWriter APPLICATIONS: \SqlServerWriter\SQL database APPLICATIONS: \SqlServerWriter\SQL Database\Database Name APPLICATIONS:\Microsoft Office SharePoint Services APPLICATIONS: \Microsoft Office SharePoint Services APPLICATIONS: \Microsoft Office SharePoint Services\WFE_NAME APPLICATIONS: \Microsoft Office SharePoint Services\WFE_NAME\Component Name APPLICATIONS:\Microsoft Office SharePoint Services\WFE_NAME\Component Name APPLICATIONS:\Microsoft Office Search APPLICATIONS:\Microsoft Office SharePoint Search Note: For SharePoint 2010 standalone backup and recovery, when the APPLICATIONS: \SqlServerWriter\SQL Database\Database Name save set is used, it automatically includes all the local dependent SQL save sets, like SYSTEM COMPONENTS:\sql embedded\instance\database for embedded SQL server and APPLICATIONS:\SqlServerWriter\instance\database for any other SQL server. Do not specify the SQL save sets separately. Displaying valid SharePoint 2010 data save sets Use the following commands: For the list of SharePoint 2010 save sets: nsrsnap_vss_save -? Displaying valid SharePoint 2007 data save sets on page 212 provides more details. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output. For complete details about save sets: nsrsnap_vss_save -v -? Performing SharePoint 2010 backups 239

240 Microsoft SharePoint Server 2010 Backup and Recovery Prerequisites for SharePoint 2010 backup Ensure that: The SharePoint Services writer has to be registered to browse the savesets and for successful backup. NetWorker client and NMM is installed on all the web front-ends, application server and SQL database server. To get the Search Service Application components name instead of its GUID, the user account performing the backup should have the SharePoint_Shell_Access role membership to the configuration database. Performing SharePoint 2010 backup To configure and perform backup: 1. Register writer using STSADM command. To register the SharePoint writer for distributed configurations: a. The SharePoint writer must be registered on a web front-end server. b. Use the command line STSADM.exe utility. Go to the following location for the front-end: C:\Program Files\Common files \Microsoft Shared \Web server extension\14\bin c. Type the following command to register the SharePoint writer: run STSADM -o registerwsswriter When registering the SharePoint 2010 writers by using the stsadm.exe -o registerwsswriter command: Ensure that this command is run on each and every web front-end server to back up the entire SharePoint 2010 farm. Note that this is unlike the SharePoint 2007 backup workflow where it is not necessary to run this command on all the web front-end servers but only on one web front-end server that is running the services. 2. Create client resources with required parameters as created for SharePoint 2007 by using the NetWorker Management Console for all the hosts in the SharePoint 2010 farm. Configure a SharePoint 2007 client resource on page 215 provides details. 3. Type the save sets for the respective client resources created for SharePoint Displaying valid SharePoint 2010 data save sets on page 239 provides the save sets for SharePoint Note: Ensure that you back up all of the SharePoint databases. 4. Ensure that the following are backed up so that web application, service applications and farm settings can be recovered: SYSTEM COMPONENTS C:\inetpub 5. Start the group in NMC to perform backup. 240 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

241 Microsoft SharePoint Server 2010 Backup and Recovery Performing SharePoint 2010 recovery To perform SharePoint 2010 recovery: 1. In the NMM GUI, select the items to recover. 2. Click Recover. A dialog box prompting you to select the database and search components that contain the selected items appear. 3. In NMM GUI on the SQL server, select the required databases 4. In NMM GUI on WFE where Search is installed, select Search Writers. 5. Click Recover. 6. After the recovery is complete, in the web front-end or application server, click Continue to continue the recover. Note: The configuration database must be selected and recovered to recover web applications and service applications. 7. Restart the machine, if prompts, to finish the recovery. Note: You can recover a web application that was completely deleted, but to do this you must first recover SYSTEM COMPONENTS:\ and C:\inetpub before performing the SharePoint writer recovery. Note that only recovery of content database will not recover a deleted web application. Performing SharePoint 2010 disaster recovery For Microsoft SharePoint server 2010 disaster recovery on Windows 2008 and Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery. Chapter 10, Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM provides details. Performing SharePoint 2007 disaster recovery on page 228 provides the information needed to perform disaster recovery for SharePoint However, refer to Table 46 on page 239 for SharePoint 2010 save set syntax. Performing SharePoint 2010 recovery 241

242 Microsoft SharePoint Server 2010 Backup and Recovery 242 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

243 10 Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM This chapter includes the following topics: Overview Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is installed Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is uninstalled Basic steps for Windows Disaster Recovery backup and recovery Performing Windows Disaster Recovery backup and recovery for Microsoft applications Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM 243

244 Windows Disaster Recovery by using NetWorker 7.6 SP2 and Overview IMPORTANT Successful recovery of system state to the same or a similar hardware, can only be achieved through offline disaster recovery. Disaster recovery backup needs to be taken after system components are changed. This includes adding, changing, removing roles, and features, or installing Windows updates. Online restore of SYSTEM COMPONENTS save set is generally not supported. Improper restore of the SYSTEM COMPONENTS save set online could lead to inconsistent state of the system. They can only be restored to the same Windows OS instance. NMM 2.3 leverages the support provided in EMC NetWorker 7.6 SP2 for Windows Disaster Recovery (DR) for NetWorker clients on the following platforms: Windows 2008 (x86 and x64) and Windows 2008 server Core Windows 2008 R2 SP1 (x64) and Windows 2008 R2 server Core NetWorker Windows DR provides an automated Bare Metal Recovery (BMR) solution by using the Windows ASR writer and other VSS writers to identify critical volumes that are needed to perform a disaster recovery on a disabled system. NetWorker DR is performed offline, which means that the Windows operating system is not active. This avoids the need to reinstall Windows manually and also avoids the problems that occur when restoring operating system files to an active Windows system. Table 53 on page 244 lists the Microsoft applications for which the Windows DR feature is supported in this release: Figure 53 List of Microsoft applications that are supported for Windows DR backups Microsoft application x64 x86 Virtual Machine Onbox Exchange 2007 SP3 standalone Exchange 2007 CCR SharePoint 2007 SP2 distributed farm (with SQL residing on separate machine) SharePoint 2007 SP2 Standalone SharePoint 2010 SQL 2008 R2 standalone SQL 2008 R2 cluster SQL 2008 SP1 standalone SQL 2008 SP1 cluster SQL 2005 SP3 standalone SQL 2005 SP3 cluster Exchange 2010 SP1 standalone Exchange 2010 SP1 DAG 244 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

245 Windows Disaster Recovery by using NetWorker 7.6 SP2 and IMPORTANT For all the applications, after a Windows DR recovery is complete and the system is rebooted, check all the disk and volume configurations. It is likely that all disks and volumes appear as on the original system. However it is possible, especially in Bare Metal Recovery scenarios where the disk signatures do not match the original disks, that the noncritical disks are offline and not mounted. Use the Microsoft Disk Manager to bring the disks online. Once online, a simple reboot will usually result in disk drive letter reassignments. However, if disk drive letter reassignments do not take place, then assign drive letters to noncritical disks, as needed. Noncritical volumes that are accessed by mount points may have similar issue. Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is installed Installing NMM 2.3 over NetWorker 7.6 SP2 affects the way the NetWorker 7.6 SP2 core client functions. Before NMM 2.3 is installed, the NetWorker core client handles the save sets All, DISASTER_RECOVERY:\, and any other save set where unique paths are specified. When the save set All is specified in the NetWorker core client and a full backup is performed, a DISASTER_RECOVERY:\ backup automatically takes place as well. The NetWorker core client GUI is used for any ad-hoc backups, showing all the disks on the system and DISASTER_RECOVERY:\. Similarly, for recovery, the core client GUI shows any save set that it saved on the server. After NMM 2.3 is installed, the NetWorker 7.6 SP2 client gets limited to only handling the DISASTER_RECOVERY:\ save set. The NetWorker 7.6 SP2 client GUI only displays DISASTER_RECOVERY:\ as an option for backup and only previous DISASTER_RECOVERY:\ backups for recovery. Although the NMM 2.3 GUI displays any previous saved backups by the NetWorker 7.6 SP2 client, including DISASTER_RECOVERY:\ save sets, it is not possible to recover the DISASTER_RECOVERY:\ save set with NMM 2.3. The Windows DR backs up only the critical volumes. If there are non-application files on noncritical volumes then you must use NMM to back them up because the NetWorker 7.6 SP2 client GUI only recognizes DISASTER_RECOVERY:\. If the data on noncritical volumes is not backed up and for some reason the noncritical volumes are formatted during the Windows DR process, then the data is lost. IMPORTANT Once NMM 2.3 is installed, running a save set other than DISASTER_RECOVERY:\ on a NetWorker core client resource, will fail. Note: It is recommended that you review the EMC NetWorker Release 7.6 Service Pack 2 Administration Guide for details about Windows DR support on a NetWorker client before proceeding with the procedures in this chapter to have a better understanding of how the Windows DR support works. Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is installed 245

246 Windows Disaster Recovery by using NetWorker 7.6 SP2 and Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is uninstalled Uninstalling NMM 2.3 reverts the functionality of the NetWorker core client to what it was before NMM 2.3 was installed: The core client will now handle file system backups. The core client GUI Backup window will once again show all the disks, as well as DISASTER_RECOVERY:\ for backup. The core client GUI Recovery window will show the DISASTER_RECOVERY:\ save set. Any other save set that is displayed should be used for backup. IMPORTANT After uninstalling NMM, perform a full backup with NetWorker 7.6 SP2 using the save set All from the NetWorker Management Console. Basic steps for Windows Disaster Recovery backup and recovery This section provides the basic steps for Windows DR backup and recovery. Details of Windows DR backup and recovery for Microsoft SQL, Microsoft SharePoint, and Exchange is provided in the subsequent section. To perform Windows DR backup, you must perform the following steps: 1. By using NMM client, perform a backup of noncritical volume. 2. By using NMM client, perform a backup of Microsoft application data for SQL, SharePoint, and Exchange. 3. By using core NetWorker client, perform a Windows DR backup. To perform Windows DR recovery, you must perform the following steps: 1. By using NetWorker client, perform a Windows DR recovery. 2. By using NMM client, perform a recovery of noncritical volume. 3. By using NMM client, perform a recovery of Microsoft application data for SQL, SharePoint, and Exchange. IMPORTANT For details about how to back up Microsoft SQL, SharePoint 2007, SharePoint 2010, Exchange 2007, and Exchange 2010 by using NMM, review the respective chapter for each application: - Chapter 1, Microsoft SQL Server Backup and Recovery - Chapter 5, Microsoft Exchange Server Backup and Recovery - Chapter 6, Microsoft Exchange 2010 Server Backup and Recovery - Chapter 8, Microsoft SharePoint Server 2007 Backup and Recovery - Chapter 9, Microsoft SharePoint Server 2010 Backup and Recovery 246 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

247 Windows Disaster Recovery by using NetWorker 7.6 SP2 and Table 47 on page 247 outlines supported and unsupported system recovery scenarios. The Microsoft support article at provides more details. Table 47 Supported and unsupported system recovery scenarios Scenario System State Recovery to the same instance of Windows Server 2008 System State Recovery after BMR / Full Server restore to the same hardware System State Recovery after BMR / Full Server restore to different hardware System State Recovery after Full Server restore (without BMR) to the same or different hardware System State Recovery after a new installation of Windows Server 2008 on new hardware or same hardware Supported X X X Performing Windows Disaster Recovery backup and recovery for Microsoft applications This section provides the steps for Windows DR backup and recovery for SQL, SharePoint, and Exchange: Perform a Windows DR backup on page 247 Perform a Windows DR recovery on page 248 Perform a Windows DR backup To perform Windows DR backup: 1. By using NMM, perform a backup of noncritical volume of the NMM client: Run a full backup, by using the save set All. The backup saves all the local file system and SYSTEM COMPONENTS. 2. By using NMM client: Run a full backup of the SQL 2008 R2, SharePoint 2007, and SharePoint 2010 data by using the following save sets: APPLICATIONS:\SqlServerWriter APPLICATIONS:\Microsoft Office SharePoint Services Run a full backup of the Microsoft Exchange 2007 application data by using the following save set: APPLICATIONS:\Microsoft Exchange 2007 Run a full backup of the Microsoft Exchange 2010 application data by using the following save set: APPLICATIONS:\Microsoft Exchange By using core NetWorker client, perform Windows DR backup: a. Use the save set DISASTER_RECOVERY:\. b. Use the standard client save.exe command. Performing Windows Disaster Recovery backup and recovery for Microsoft applications 247

248 Windows Disaster Recovery by using NetWorker 7.6 SP2 and Perform a Windows DR recovery To perform Windows DR recovery: 1. Using the NetWorker Recovery image, perform a Windows DR recovery: a. To start the Windows Disaster Recovery image, you can do either of the following: Booth from the CD containing the Windows Disaster Recovery image (.iso file). Boot the image from Network location, for which you will need Windows Deployment Service (WDS), DNS service, and DHCP service. The Welcome to NetWorker System Recovery wizard appears. b. In the Select Network Interface window, select the NIC that will be used to connect to the NetWorker server, and click Next. c. Configure the NetWorker client. Provided the following information and click Next: The Host name, which is the source machine name. The DNS domain, as configured in the source machine. The IP address, as configured in the source machine. The Subnet mask, as configured in the source machine. The Default gateway, as configured in the source machine. The DNS Server IP address, as configured in the source machine. d. The Available Disks window displays the disks drives on the machine, they may not all be critical drives. If not all the drives are shown then load any drivers needed by the missing drive or drives. Click Next. e. For the NetWorker server, type the IP address. Click Next. f. The Wizard shows all the DISASTER_RECOVERY save sets on the server for this host. Choose the desired backup to recover. g. The wizard displays the critical volumes and provides you the option of formatting the disk. a. Select the Perform a quick format of disks option to format the disks. However, if you choose this option all existing data will be lost. b. Click Next. The System Recovery Summary window appears. This window displays all the details for the recovery. h. Check all the details in the System Recovery Summary window and click Next. i. The Windows DR recovery starts. The System Recovery Status window shows the progress of the recovery. Cancelling the critical volumes recovery will result in the disks being restored in an undefined state. You will need to restart the recovery process. j. The Windows DR recovery process is complete. The System Recovery Results windows shows the details of the successful recovery. You can reboot the system and restore the application data as needed. 248 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

249 Windows Disaster Recovery by using NetWorker 7.6 SP2 and 2. By using NMM client, perform a recovery of noncritical volume. This is to ensure that all the data stored in noncritical volume is recovered by using NMM software. 3. By using the NMM client, perform a recovery of either SQL, SharePoint 2007, SharePoint 2010, Exchange 2007, or Exchange 2010, as applicable. The SQL databases, including the internal database such as master, msdb and models, are not recovered by the Windows DR recovery. Note: To rectify the following, perform a writer level of SQL recovery: - The SQL server instance service is not in start state. - When the SQL service is started, an error message about that master database not being available, appears. - A SQL exception is thrown when the SQL server management studio is started to connect to SQL server instance. Performing Windows Disaster Recovery backup and recovery for Microsoft applications 249

250 Windows Disaster Recovery by using NetWorker 7.6 SP2 and 250 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

251 Invisible Body Tag 11 Troubleshooting This chapter includes the following topics: About the troubleshooting process NMM client error messages NMM client issues NMM installation issues Checking log files Manually stopping and starting services Configuring dedicated web front-end crawling Using nsr.dir to skip files for NMM backup and recovery Troubleshooting issues during SQL databases directed recovery Name resolution Other troubleshooting resources Troubleshooting 251

252 Troubleshooting About the troubleshooting process NetWorker and the NMM provide many resources to help discover and isolate problems. Setting up these resources before problems occur can help if and when troubleshooting problems occur later. If the problem is not with the NMM client, there are other NetWorker resources and documentation that may provide a solution. The flowchart shown in Figure 54 on page 252 provides an overview of the process and sections of this chapter for troubleshooting a scheduled backup or recovery problem. Find error NetWorker Server NetWorker Client-side or Server-side? NetWorker Client No Unique to NMM Client (volumes and writers)? Yes Check other EMC documentation Does the error appear in a log file or message window? No Yes Check NMM Client error messages section Check NMM Client issues section Fixed? Yes Finish No Try a different solution? Yes No Contact Technical Support GEN Figure 54 Troubleshooting process 252 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

253 Troubleshooting Setting up notifications Set up NetWorker software and NMM client software to send notifications about events. These notifications can be sent to several locations, including log files, SNMP printers, SNMP management console, and messages. The EMC NetWorker Release 7.6 SP1 Administration Guide describes how to set up notifications. Finding errors Table 48 When a problem occurs, a notification or message might be displayed, or appear in a log file. Table 48 on page 253 describes several ways that NetWorker server, NMM client, and other NetWorker features provide information about problems. Notifications and errors Type notification of a NetWorker event Error message pages NetWorker Monitor page Event viewer Log files Description NetWorker client can be set up to send an notification about NetWorker events. Appear on the NetWorker server when an error occurs during backup or recovery operations. Displays details of current NetWorker server activities, operations related to devices and libraries, and events that require user intervention. Alerts users that user intervention is required on the NetWorker server. Log files are created for each operation and process. Separate log files are available for NetWorker and various features, depending on what features are installed and in use: NetWorker VSS Client for Microsoft Windows NetWorker NetWorker server NetWorker PowerSnap Replication Manager Solutions Enabler EMC VSS Provider The logging level of the log file is controlled by the debug level of the process. NMM client error messages Error messages help to identify which product is having a problem. The following sections describe error messages that are specific to the NMM client: E_VOLUME_NOT_SUPPORTED on page 254 E_VETO_PROVIDER on page 254 VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 on page 255 VSS CLIENT... Invalid Writer Selection... for APPLICATIONS on page 255 Savegroup failed in scheduled backup on page 255 NMM client error messages 253

254 Troubleshooting Savegroup failed in scheduled backup on page 255 Insufficient permission to access mailbox. See documentation for required permission settings. Server MBX is not capable of RSG operations on page :nsrsnap_vss_save on page 256 NMM validation for NSP Writer failed, unable to restore NPS VSS Writer data on page 257 E_VOLUME_NOT_SUPPORTED This error occurs when CLARiiON is down, an array is unmanaged, or the CLARiiON disk is not visible. This error also occurs when Data Mover is used to take a local volume replica. The error message will appear in NMM client and Replication Manager logs. Solution Check in the CLARiiON array for storage allocation. E_VETO_PROVIDER There are several possible causes for this error: Storage resources, such as Symmetrix BCVs or CLARiiON clones have been added, but the Replication Manager service was not recycled to rebuild the storage resource cache. The provider finds the LUN as hosted by the storage array, but fails to find storage resources in the storage resource cache. There is a load on the CLARiiON array, and replica creation fails. A CLARiiON snapshot is performed when there are not enough LUNs in the reserved LUN pool. In this case, the rmsnap command fails. A CLARiiON snapshot is performed, but the number of established snapshot sessions to the LUN has already reached the limit. Solution Use the net stop and net start commands to stop and restart the EMC VSS provider, Microsoft VSS services, and Replication Manager services. For example, to stop and restart the Replication Manager service: 1. From the command line, stop the rmagentps service: net stop rmagentps 2. Start the rmagentps service: net start rmagentps 254 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

255 Troubleshooting VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 This error occurs if a savegroup is rerun, and it was stopped previously while a replica was being taken and the replica did not complete. Solution 1. Stop the following services: EMC VSS Provider Microsoft VSS services Replication Manager 2. Restart these services: EMC VSS provider Microsoft VSS services Replication Manager 3. Restart Exchange Information store if it was running and was backed up. VSS CLIENT... Invalid Writer Selection... for APPLICATIONS This error might occur if Microsoft Exchange services are not up or if SQL databases are offline. Another cause of this error is if there is a typographical error in writing APPLICATIONS:\Microsoft Exchange Writer. Solution Perform either of the following: For Microsoft Exchange applications, start the Exchange services. If Exchange services were already up, dismount and mount the databases and then start the savegroup. For SQL server applications, bring the databases online. Retype the words correctly or use the nsrsnap_vss_save -? command, as described in EMC NetWorker Module for Microsoft Application Release 2.3 Administration Guide, to display a listing of all valid application save sets on the NMM client. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output of the nsrsnap_vss_save -? command. Savegroup failed in scheduled backup A notification appears in the NetWorker Monitor page that a savegroup failed. Solution Check the savegroup details for the failed save set. This may provide an exact cause, or a general error, which should indicate whether it is a client-side or server-side issue. The EMC NetWorker Release 7.6 SP1 Administration Guide provides information about viewing group backup details. NMM client error messages 255

256 Troubleshooting If there is not enough information in the savegroup details: 1. Check the NMM client log. 2. Check the other client-side logs. Checking log files on page 274 provides more information about the log names, locations, and details. Insufficient permission to access mailbox. See documentation for required permission settings. Server MBX is not capable of RSG operations This error message appears if RSG browsing permissions are not provided when recovering a storage group to a RSG that was already created. Solution Before starting the RSG recovery: 1. Install MAPI Collaboration Data Objects The EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide provides details. 2. Provide RSG browsing permissions. This step ensures that the error message does not appear, and the recovery is performed smoothly. For example, get-exchangeserver <Exchange Server name> Add-AdPermission -user <username> -extendedrights Receive-As, Send-As 3. Set registry to disable IPV6. To fix RSG browsing issue in the registry: a. Open the registry. b. Go to: HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters c. Edit or create the 32-bit DWORD value DisabledComponents, and enter the value FFFFFFFF. The public folder must be present on the Exchange server for RSG browsing to work. In the CCR or SCC cluster, we should perform all above steps on both nodes of cluster :nsrsnap_vss_save When performing a passive node backup when only a single passive node client is configured for Exchange deduplication backups in a CCR setup, the following error message appears: 77108:nsrsnap_vss_save:NMM.. Operation unit failed with error 'Traditional save returned error. saverc :-Possible cause: 1)Unsupported file system or 2)write-protected disc or 3)No space on disc NMM.. Error backing up one or more of the file system savesets: NMM.. Operation unit failed with error Traditional save returned error. saverc : EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

257 Troubleshooting Solution Whenever performing a passive node backup for Exchange deduplication backups in a CCR setup, make sure to perform the following steps: 1. Configure a virtual client in same savegroup where the passive node is configured. 2. Make sure not to schedule this virtual client for backup in same group. 3. Make sure to enable deduplication settings for this virtual client. Note: Although the client will be there in the same savegroup, it will not be part of backup. NMM validation for NSP Writer failed, unable to restore NPS VSS Writer data If Network Policy and Access Services (NPS) Role is installed, but not configured properly, the file C:\windows\system32\ias\ias.xml is not created, which is in the NPS Writer file list. NPS Writer recovery fails, if not configured properly on Windows server 2008, in Windows server 2008 R2, and Windows server 2008 R2 x64 platforms, with the following error message: NMM validating for NSP Writer failed, unable to restore NPS VSS Writer data Solution You must configure NPS role data correctly. NMM client issues Check this section first when there is a problem or if no specific error message in monitoring or event logs appears: In-progress backup fails on page 258 NetWorker is blocked by Windows firewall on page 259 NMM backups might fail where a firewall exists between the NetWorker server and client on page 259 Need to run utility to obtain Exchange server information on page 260 Requesting a snapshot for a volume on hardware that is not transportable on page 260 The PowerSnap service must be restarted after the NetWorker service is restarted on page 261 PowerSnap validation for recovery fails on page 261 Snapshot backup may fail with writer errors on page 261 Microsoft I/O write error when taking a replica in a CLARiiON array on page 262 Creating a replica takes a long time in CLARiiON environment on page 262 Cannot recover Exchange database due to overwrite prevention error on page 262 Incremental backups may be promoted to full backups on page 263 Diagnosing VSS Writer Issues on page 263 NMM client issues 257

258 Troubleshooting Modifying the Microsoft Exchange 2007 COM+ component s user account or password on page 264 Save sets may not appear in the Recover page on page 264 Recovery of AES-encrypted files fails without passphrase on page 265 Unable to restore files encrypted with both Microsoft Windows Encrypting File System and AES encryption on page 265 Antivirus programs block recovery on page 265 Snapshot cannot include both hardware and software snapshot volumes for clustered NetWorker VSS clients on page 266 Cross-platform directed recovery operations are not supported on NMM on page 266 Recovery of large number of items fails if one or more items in a folder is not selected on page 267 Multiple client resources with the same name cannot be combined in the same group on page 267 Backup of two partitions of the same CLARiiON disk fails on page 267 Connection to DPM service lost during DPM recovery on page 267 DPM replica backup is not correctly configured on page 267 Backup fails if Exchange server in is renamed after it is created on page 268 In Exchange 2010, recovery fails for renamed mailbox database, however backup completed successfully for renamed database on page 269 In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of new database name after renamed mailbox database on page 269 Save sets from an Avamar AFTD for NMM backups show retention set to 1/18/2038 on page 269 Microsoft updates required to fix the vds.exe crash errors during retention on Windows 2008 and Windows 2003 on page 270 Back up of SYSTEM COMPONENTS fails due to missing System Writer on page 270 Problems with RMExchangeInterface component on page 271 SharePoint backup fails when host and proxy client do not match on page 271 In-progress backup fails If a node within a cluster undergoes failover during a backup operation, the operation will not be successful. The next scheduled backup operation will be the next valid backup. Solution 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 NaviCLI interface to search for and delete the InActive snapshot. 258 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

259 Troubleshooting NetWorker is blocked by Windows firewall After installing Microsoft Windows server 2003 (SP1), the Windows Firewall may be blocking NetWorker processes from sending information through the firewall. Solution The EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide provides information about how to extend the Security Configuration Wizard or manually configure Windows Firewall exceptions. NMM backups might fail where a firewall exists between the NetWorker server and client The following errors might appear during long running NMM backup operations where a firewall exists between the NetWorker server and client. This might indicate that a nsr socket was closed before the backup successfully completed: 0 9/22/2009 5:41:40 PM t4tabor.test.portal nsrbragent:\program Files\ 0 9/22/2009 5:41:40 PM t4tabor.test.portal nsrbragent C:\ /22/2009 5:41:40 PM exchsv.test.local nsrbragent nsrbragent completion time: 9/22/2009 2:41:40 PM /22/2009 5:41:40 PM exchsv.test.local nsrbragent Traditional save returned error. saverc : /22/2009 5:41:40 PM exchsv.test.local nsrbragent Please check file C:\Program Files\Legato\nsr\logs\nsrbragent.2009_09_22.14_41_ trace for more detailed information about this error /22/2009 5:41:40 PM exchsv.test.local nsrbragent Traditional save FAILED /22/2009 5:41:40 PM exchsv.test.local nsrbragent cwd=c:\ /22/2009 5:41:40 PM exchsv.test.local nsrbragent after chdir -> cwd=c:\program Files\Legato\nsr\tmp /22/2009 5:41:45 PM exchsv.test.local nsrbragent Processed all messages. Now exiting 0 9/22/2009 5:41:45 PM exchsv.test.local nsrbragent nsrbragent process is exiting with status :0 Unable to render the following message: NSRBRAGENT [ PID = 6512] [HOST = t4tabor.test.portal] COMPLETED. Solution 1. Set the TCP keepalive parameter to a low value such as 5 minutes on the following: NetWorker server NetWorker storage node NetWorker client (NMM host) For example, on Microsoft Windows, create a registry key: \HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Tcpip\Paramete rs Value name: KeepAliveTime Value Type: REG_DWORD Value Data: (Decimal) NMM client issues 259

260 Troubleshooting! IMPORTANT Exercise caution when modifying the Windows registry. The following Microsoft article provides details: Your Operating System documentation provides information on how to set the TCP keepalive parameter. 2. After the backup failure is resolved, you can increase the KeepAliveTime value if required based upon your backup environment. Need to run utility to obtain Exchange server information The nwexinfo.exe utility runs when the NMM client is installed on an Microsoft Exchange server. This utility gathers the Exchange username, password, and domain, and then inserts this information in the registry. Solution Rerun the utility if any of the following conditions occurs: Exchange server is installed after NMM client is installed. The Exchange username, password, or domain values change after the NMM client is installed. To run the utility: 1. Navigate to the following folder: <NetWorker_install_path>\nsr\bin 2. Run nwexinfo.exe. 3. For Exchange 2003, change the Exchange password, username, and domain as required. Requesting a snapshot for a volume on hardware that is not transportable When volumes are added to the NMM client snapshot set, an error might appear if a transportable hardware snapshot is requested and the volume that is being replicated is not a volume that resides on special hardware that is transportable. The following error message might also appear: VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER. Solution The Exchange server and proxy server (if one is set up for Exchange) must have matching volumes or alternate mount path in PowerSnap (PS) attribute. An Exchange backup that is mounted on a proxy server needs either matching volumes or an alternate location to mount Exchange databases and logs: An example of matching volumes would be D: to D: and E: to E:. An example of alternate location would be "G:\altpath" on the proxy server. In this example: The snapshot of "D:\" would be mounted on the proxy server as "G:\altpath\D\" The snapshot of "E:\" would be mounted on the Proxy server as "G:\altpath\E\." 260 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

261 Troubleshooting To use the alternate mount path, set the PowerSnap attribute NSR_ALT_PATH in the client resource. In the preceding example of an alternate location, the attribute would be set to "NSR_ALT_PATH=G:\altpath." EMC NetWorker Module for Microsoft Application Release 2.3 Administration Guide provides more information about creating a client resource. The PowerSnap service must be restarted after the NetWorker service is restarted After restarting the NetWorker service, if the PowerSnap service is not restarted, the first retention or rollover will fail. The following message appears: RPC send operation failed. A network connection could not be established with the host. The PowerSnap service will re-establish the connection on the next operation, so this failure will only occur once. Solution To fix this problem: 1. Restart the NetWorker service. 2. Restart the PowerSnap service 3. Run a PowerSnap operation. PowerSnap validation for recovery fails When the service is not stopped, recovery fails while validating PowerSnap for recovery. Some VSS writers require that the service be stopped while recovering. For example, the SQL writer requires that the service be stopped while recovering the SQL database. Solution To fix this problem, stop the service before recovering. Snapshot backup may fail with writer errors A snapshot backup may fail with VSS writer errors that indicate the writer may be in an unstable state, such as the following: VSS_E_WRITERERROR_NONRETRYABLE VSS_E_BADSTATE VSS_E_UNEXPECTED_WRITER_ERROR Solution Contact EMC Technical Support. NMM client issues 261

262 Troubleshooting Microsoft I/O write error when taking a replica in a CLARiiON array This problem might occur when a replica is taken in a CLARiiON array LUN backup. Solution To fix this problem: 1. Stop the following services: EMC VSS provider Volume Shadow Copy Service Replication Manager 2. Restart these services: EMC VSS provider Volume Shadow Copy Service Replication Manager Creating a replica takes a long time in CLARiiON environment Older version of CLARiiON FLARE OS that is running on CLARiiON may take a long time to create a replica. Solution To fix this problem, update CLARiiON FLARE OS to the latest version. Cannot recover Exchange database due to overwrite prevention error If an Exchange database has not been selected for recovery in the Exchange System Manager, recovery for that database will fail. When a recovery attempt fails, several entries are displayed in the NetWorker Monitor page. For example: "VSS CLIENT... Database "Mailbox Store 2 (SERVERX)" in Storage Group "Second Storage Group" does not have the "This database can be overwritten by a restore." checkbox marked." "VSS validatation and preprocessing failed for Microsoft Exchange Writer." "nsrsnap_vss_recover: Recovery operation failed. Refer to log file(s) for details." The following message may be displayed by Microsoft Exchange: The database files in this store were replaced with older versions by an offline restore. To use the restored files, open the database property page for this store, select "this database can be overwritten by a restore", wait for active directory replication, and try again. Error ID: C104173A Exchange System Manager Solution 1. Search for "KB293324"on the Microsoft Help and Support website, and go to the article "XADM: "C104173A" Error Message Occurs After You Restore the Database." 2. Follow the instructions for changing the setting in Exchange System Manager. 262 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

263 Troubleshooting Incremental backups may be promoted to full backups NetWorker Module for Exchange client This section outlines when incremental backups may be promoted to full backups: NetWorker Module for Exchange client on page 263 NetWorker Module for SQL server client on page 263 If the NMM client is installed, requests for an incremental backup through the NetWorker Module for Exchange client are automatically promoted to a full backup. This does not affect NMM client incremental backups of volumes. For example: Suppose that NetWorker Module for Exchange client requests an incremental backup for Exchange server EXSRV1. If NetWorker NMM client is installed, then the NetWorker Module for Exchange client promotes its own incremental backup to a full backup to maintain the integrity of the backup and prevent data loss. However, the NetWorker NMM client can still perform an incremental backup of a volume, such as D:\ on EXSRV1. NetWorker Module for SQL server client If the NetWorker NMM client is active and configured to back up the SQL database, requests for an incremental backup through the NetWorker Module for SQL client are automatically promoted to a full backup to maintain the integrity of the backup and prevent data loss. Installation of the NMM client itself does not automatically promote NetWorker Module for SQL client incremental backups to full backups. This does not affect NMM client incremental backups of volumes. For example: Suppose that the NetWorker Module for SQL client requests an incremental backup for SQL server SQLSRV1. If the NMM client is installed, and the NetWorker NMM client performs backups of the SQL database, then the NetWorker Module for SQL client automatically promotes the incremental backup to a full backup. However, if the NMM client is installed but does not perform backups of the SQL database, then a request through the NetWorker Module for SQL client for an incremental backup is allowed. In either case, the NMM client can still perform an incremental backup of a volume, such as D:\ on SQLSRV1. Diagnosing VSS Writer Issues NMM provides a command to dump the Microsoft VSS Writer metadata to XML files. These XML files detail what each active writer on the system is doing, and may be useful to support personnel for investigating and analyzing writer issues. To dump the VSS Writer metadata to XML files, run the nsrsnap_vss_save command with the -G command switch, for example: D:\Legato\nsr\bin>nsrsnap_vss_save -G NMM client issues 263

264 Troubleshooting When you run the command, a message displays the directory that the files were sent to. For example: NMM.. requesting of writer metadata completed successfully and deposited in C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\ The directory contains an.xml for each writer on that system, for example: Exchange Writer.XML SQL Writer.XML etc. The files will probably be hidden because the directory they are sent to are hidden by default. You can make the folder visible by using Start > Control Panel > Folder Options > View > Show Hidden Files and Folders. Double-click a XML file to view it in your browser, such as Internet Explorer or Firefox. You can also copy the files to another folder. For example: D:\>mkdir xmlfiles D:\>cd xmlfiles D:\xmlfiles>copy C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\*.* C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\ExchangeWriter.xml C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\SQL Writer.xml 2 file(s) copied. Modifying the Microsoft Exchange 2007 COM+ component s user account or password If your user account, your password information, or both change after the COM+ component is registered, use the following procedure to change the user account or password information for the COM+ component: 1. Start component services. 2. Expand Computers > My Computer > DCOM Configuration. 3. Right-click Replication Manager Exchange Interface and select Properties from the context menu. 4. Click the Identity tab. 5. Modify the domain user account or password and click OK. This will also modify the account information for the Replication Manager Exchange Interface Service. Save sets may not appear in the Recover page 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. Solution Add the NETBIOS name to the Aliases attribute of the client resource. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about creating a client resource. 264 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

265 Troubleshooting Recovery of AES-encrypted files fails without passphrase If an application such as SQL server or Exchange server is backed up with AES encryption, and then a recovery is attempted without the correct passphrase, recovery will fail. The application files will only be partially recovered, and will be empty or in a corrupted state. Solution During data recovery, you must: 1. Specify the passphrase used at the time of backup if it is not the default or current pass phrase. 2. Provide the passphrase when recovering AES encrypted files by using the NMM Security recovery options. EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides more information about specifying pass phrases in NMM. Unable to restore files encrypted with both Microsoft Windows Encrypting File System and AES encryption When AES encryption is applied to a file that is also encrypted using the Microsoft Windows Encrypting File System (EFS), the backup will be reported as successful. However, recovery of the file will fail and the following message will be written to the NetWorker log file: recover: Error recovering <filename>. The RPC call completed before all pipes were processed. Solution Do not use AES encryption when backing up files that are encrypted using EFS. Antivirus programs block recovery When a recovery from a save set of all is attempted, antivirus programs may block NMM recovery. Antivirus programs are designed to protect their own program files and settings from external threats that may be attempting to disable the program. The antivirus program cannot always distinguish the recovery from an attack. Solution Prior to recovery: 1. Disable the antivirus programs protection properties. The name and location of the settings varies, but look for a setting like Prevent modification of <AntiVirus Program Name> command agent files and settings. 2. Clear or disable the setting. 3. Check the antivirus program s documentation or online help for information about finding and disabling this setting. To recover files to a system protected by an antivirus program: 1. Disable the antivirus program s setting for protecting its own files and settings. 2. Perform the recovery. 3. Reset the antivirus program to protect its files and settings. NMM client issues 265

266 Troubleshooting Snapshot cannot include both hardware and software snapshot volumes for clustered NetWorker VSS clients A NetWorker VSS client resource running on a cluster cannot include both hardware and software volumes in the same save set. Additionally, save set All cannot be specified for such a client resource. If both hardware and software volumes are included in a save set, then backup fails. Solution If a NMM client on a cluster has both hardware and software volumes, create at least two client resources: one for hardware volumes and one for software volumes. Additionally, do not specify save set All in any of the client resources for the NMM client. When using a hardware provider with a NMM client, you must configure a proxy client and the snapshot volume must be exported to a proxy outside of the cluster. Cross-platform directed recovery operations are not supported on NMM NMM does not support cross-platform recovery. A directed recovery operation might fail if the source and the destination NetWorker client machines are not running the same operating system. For example, to perform a directed recover operation of a Exchange Mailbox, both the source and the destination NetWorker client machines must be running the same version of the operating system. For example, both NetWorker client machines must be running either Windows 2003 or Windows The recovery will fail if the source NetWorker client machine is running Windows 2003 and the destination NetWorker client machine is running Windows As a directed recovery operation is performed at the application level, the underlying differences between the operating system might not be apparent. Also, the error message that appears with this failure does not specify the actual cause, for example: 63511:nsrsnap_vss_recover:NMM.. VSS failed to initialize the Backup Component document for restore -- 0x :nsrsnap_vss_recover:NMM.. XML file processing failed. Missing or invalid BCDocument :nsrsnap_vss_recover:NMM.. failed to process BCDoc in XML file. Cannot proceed :nsrsnap_vss_recover:NMM.. error 0x while processing XML file -- C:\temp\vssclient_ xml :nsrsnap_vss_recover:NMM.. fatal error during processing of the Metadata file for savetime :nsrsnap_vss_recover:nsrsnap_vss_recover: Recovery operation succeeded. nsrsnap_vss_recover complete time: 10/28/2009 2:14:24 PM Recover program exited with status: 0 Restore destination has been reset for storage group W2k8DC-SG The options specified in the Recover Options Dialog have been reset back to their safe default values. Recover end time: 10/28/2009 2:14:24 PM Recover elapsed time: 0 minutes, 24 seconds. 266 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

267 Troubleshooting Recovery of large number of items fails if one or more items in a folder is not selected If one or more items is not selected in a folder that has been selected for recovery, then recovery may fail if the number of items in that folder is very large. This scenario has occurred when testing the recovery of 50 K items in a folder. Solution Select all items or the entire folder, and then perform recovery. After recovery, delete any unwanted items. Multiple client resources with the same name cannot be combined in the same group If two or more client resources with the same name are in the same snapshot group, then some of the save sets will not be recoverable. NMM does not support combining multiple client resources with the same name in the same group. Solution Either combine the client resources into a single client resource, or create separate groups and back up the individual clients in separate groups. Backup of two partitions of the same CLARiiON disk fails Backup of two partitions of one SAN LUN is not supported. The EMC Information Protection Software Compatibility Guide contains the latest support information. This limitation only applies to hardware-based snapshot and does not apply to software-based snapshot. When you try to back up two partitions of one SAN LUN, the backup fails and the following error appears in nmm.raw: An error was detected during the replica creation. Details in nmm.raw on % s. \n starwar.duke.com starwar.duke.com nsrsnap_vss_save 26 NMM.. Exception caught: %s Failed to create replica. Connection to DPM service lost during DPM recovery During DPM database recovery or DPM replica recovery that uses the NMM client on a DPM server, if the DPM management console is open, then a dialog box appears and the connection to DPM service is lost: 1. Close the dialog box that appears. The DPM management console is closed. 2. After the recovery operation is complete, reopen the DPM management console. DPM replica backup is not correctly configured If not configured properly, DPM replica backups may fail and the following error message may appear: /22/2009 8:16:43 AM es-chl-dpm-001.es.govt.state.ma.us nsrsnap_vss_save RM ERROR:DPM Writer is stable. The error is VSS_E_WRITERERROR_RETRYABLE. The code is: 0x800423f3. Check the application event log for more information. NMM client issues 267

268 Troubleshooting Review the following before starting DPM replica backup: 1. NSR_PS_FIRST_SAVESET_SAVE attribute should be set to actual database name. For example: NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS:\Microsoft DPM\DPM database 2. NSR_PS_FIRST_SAVESET_SAVE attribute should not be used if the DPM configuration database is not one of the save sets or if the DPM configuration database is the only save set. This attribute should only be used if the DPM configuration database is one of the multiple save sets that is being backed up under a single NetWorker client resource. 3. The Client Retries attribute of the Group resource must be set to 0. Note: NMM does not support Group retry. 4. Populate the Application Information of the client resource for replica backups with the following: NSRSNAP_SNAP_TYPE=vss NSR_PS_SINGLE_SAVE_PER_SAVESET=yes NSR_DPM_RETRY_WAIT=5 NSR_DPM_RETRY_MAXIMUM=3 The default value for NSR_DPM_RETRY_WAIT and NSR_DPM_RETRY_MAXIMUM are 10 minutes and three attempts respectively. 5. Re-run the backup with a single replica in the save set to make sure that the backup is successful. Backup fails if Exchange server in is renamed after it is created If the name of a Exchange server 2007 is changed after it is created and then a backup is performed, the backup fails. Restart the Microsoft Exchange Information Store Service to successfully backup the renamed storage group: 1. Click Start, point to Administrative Tools, and then click Services. 2. On the Services window, right-click Microsoft Exchange Information Store, and then click Restart. The Microsoft Support website provides more information. 268 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

269 Troubleshooting In Exchange 2010, recovery fails for renamed mailbox database, however backup completed successfully for renamed database After a successful backup, if a mailbox database is renamed, then recovery of renamed mailbox database fails with an error message. To recover a database that has been renamed: 1. Restart the Microsoft Exchange Information Store Service. 2. Click Start> administrative Tools, and then click Services. 3. On the Services window, right-click Microsoft Exchange Information Store, and then click Restart. The KnowledgeBase Article on the Microsoft Support website provides more information. In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of new database name after renamed mailbox database nsrsnap_vss_save -? lists old database name instead of new database name after the mailbox database is renamed. For example, if the actual mailbox database name is DB2, rename it to DB21, and back up DB21. The backup fails and the rename database is not listed when the command nsrsnap_vss_save -? is used. Note: Ensure that you remove the inverted commas when you copy the saveset name from the output of nsrsnap_vss_save -?. Restart the Microsoft Exchange Information Store Service to successfully backup the renamed storage group: 1. Click Start, point to Administrative Tools, and then click Services. 2. On the Services window, right-click Microsoft Exchange Information Store, and then click Restart. The KnowledgeBase Article on the Microsoft Support website provides more information. Save sets from an Avamar AFTD for NMM backups show retention set to 1/18/2038 When using mminfo command on media, save sets like VSS:\ display an odd expiration date, for example, year This is normal behavior and can be ignored as these save sets do not affect the browse and retention of the backups. Do not alter or delete these save sets. NMM client issues 269

270 Troubleshooting Microsoft updates required to fix the vds.exe crash errors during retention on Windows 2008 and Windows 2003 On Windows 2008 and Windows 2003, during NMM backups, Virtual Disk Service (VDS) crashes while applying retension because VDS incorrectly accesses some providers that are unloaded, when VDS is in the exit process. Install the following Microsoft hotfixes on the respective platforms to fix the issue: For Windows 2008 (x64 SP2) Apply KB For Windows 2003 (x86 SP2) Apply KB The Microsoft Support website provides more information. Back up of SYSTEM COMPONENTS fails due to missing System Writer If the System Writer is missing, the backup of SYSTEM COMPONENTS fails with the following error message: " win-geui5lp5gei.nmm23.emc.com nsrsnap_vss_save 85 ERROR : Found 'System Writer' missing which is required for SYSTEM COMPONENTS backup. 0" Solution The System Writer runs in the context of Cryptographic Services (CryptSvc service) on Windows server 2003, Windows server 2008, or Windows server 2008 R2. The System Writer may be missing due to several reasons. To identify and rectify this problem, perform the following steps: 1. Open the Services console and verify that the Cryptographic Services log in has the Network Service account credentials. 2. On the Windows server: a. Click Start >Run. b. Type msconfig and press Enter. c. Click Services tab and select Hide All Microsoft Services and Disable All Third Party Services. d. Click Startup tab and Disable All startup Items. e. Click OK and choose Restart. f. Reboot the server. g. Run vssadmin list writers command to check if the System Writer is displayed. h. If the issue still persists: open a command prompt as Run As Administrator, and type the CD c:\windows\system32 Takeown /f command to see if it the System Writer is displayed. For example, 270 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

271 Troubleshooting CD c:\windows\system32 Takeown /f %windir%\winsxs\filemaps\* /a icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)" icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)" icacls %windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)" it has been reported that there is some permissions issue which can cause this kind of issue. Please follow the steps below and check if it can be helpful. 3. On domain controller: a. Open Active Directory Users > Computers. b. Click View and then Advanced features. c. Right-click Builtin and click Properties. d. Click Security tab. e. Grant read permission to the authenticated users. Note: By default, authenticated users should have read permission for the system to take system state backup. f. Click Apply and OK. g. Restart Cryptographic Services. Problems with RMExchangeInterface component If there are problems with the RMExchangeInterface component, try one or more of the following: Check that the service is installed. Check service account. It should not be local system. It should be an account that has Exchange Administrator privileges. Note: The service is not running by default, it runs on demand. Check the Install.log in C:\Program Files\EMC\rmagentps\client\bin\Install.log. The file itself does not contain much information. The existence of this log confirms that the COM component was registered and the service was installed. Validate COM entry is present by using the Component Services manager. Check the event log for any errors. SharePoint backup fails when host and proxy client do not match When using data mover to perform a SharePoint backup, the application host and proxy client must use the same operating system release, patch level and processor architecture: The application host and proxy client must be same operating system release. For example, both are Windows server 2003 or both are Windows server NMM client issues 271

272 Troubleshooting The application host and proxy client must be same operating system patch or service pack level. For example, both are Windows server 2003 R2 or both are Windows server 2003 SP3. The application host and proxy client must have the same processor architecture. For example, both are x86 or both are amd64/x64. NMM installation issues The following sections describe some common problems and possible solutions for NMM installation: RMAgentPS fails to uninstall when uninstalling NMM on page 272 Recovery failure after.net 3.5 framework installation on page 273 SYSTEM COMPONENTS failure after McAfee uninstall on page 274 RMAgentPS fails to uninstall when uninstalling NMM During NMM uninstallation, the Replication Manager is not uninstalled completely. Solution On Non-server core machines: 1. From the Add or Remove Programs, uninstall RMAPI. This removes the RMAPI binaries. 2. Check the installation folder and delete the files, if any. 3. Go to services.msc. 4. Check if the RMAgentPS service and Replication Manager Exchange interface service are shown as registered. If yes, delete the required registry keys: RMAgentPS under the following: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\RMAgentPS HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RMAge ntps RM_ExchangeInterface under the following: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\ RM_ExchangeInterface HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ RM_ExchangeInterface Note: The RM_ExchangeInterface key exists only when Exchange is installed in the setup. 5. Ensure that the services are no longer shown in services.msc. 6. Rerun the PowerSnap installer to see if RM installs fine. 272 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

273 Troubleshooting On server core machines: 1. Go to the path where NMM binary is copied. 2. To uninstall Replication Manager manually, use the command: \networkr\ps\setup.exe /s /v "/qn /L*v """%temp%\psuninstall.log""" " /x This removes the RMAPI binaries. 3. Check the installation folder and delete the files, if any. 4. To see the status of the RM service, if it still exists, use the following command: >sc queryex RMAgentPS 5. If the service exists, use the following command to stop the service: >taskkill /F RMAgentPS Make sure that the service is also stopped from registry in the locations: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services 6. Check for the entry of RMAgentPS. 7. Open the registry by typing regedit.exe at command prompt and go to the location: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Un install\ to check if the RM binaries are still installed. 8. Under Uninstall, look for the key {9E5ED863-C18B-4BAB-8248-C0D443837D4F}. If found, delete this key. 9. Rerun the PowerSnap installer to see if RM installs fine. Recovery failure after.net 3.5 framework installation Volume and SYSTEM COMPONENTS restore fails if the system previously had.net Framework 3.5 installed, and the OS was reinstalled but the.net Framework 3.5 was not re-installed before attempting recovery. When recovery fails, an error is displayed: The directory is not empty... Solution To restore the Volume and SYSTEM COMPONENTS on a system that previously had.net Framework 3.5 installed at the time of the backup: 1. Reinstall the operating system. 2. Reinstall.NET Framework Install NMM. 4. Recover the volume and SYSTEM COMPONENTS. NMM installation issues 273

274 Troubleshooting SYSTEM COMPONENTS failure after McAfee uninstall If a program does not uninstall cleanly, some program files may still remain after uninstallation. This may cause SYSTEM COMPONENTS:\ backups to fail. This has been known to occur with McAfee VirusScan 8.5i, but may occur with other programs. Solution Microsoft has identified this as an issue with the VSS System Writer. Microsoft Support KB article describes this issue and provides several solutions. If Exchange is installed after NMM, NMM reinstallation is required to get Replication Manager Exchange Interface If Exchange 2010 stand-alone is installed on Windows 2008 R2 after NetWorker client and NMM have been installed, snapshots fail. If changes are made for NMM from Programs and Features, the window to identify domain, and add username and password appears, but Replication Manager is not updated. Solution Uninstall and reinstall NMM 2.3. NMM uninstall and reinstall required to change the Replication Manager port number The Replication Manager port number can be changed after NMM is installed. Solution Uninstall and reinstall NMM 2.3. During the reinstallation process, change the required Replication Manager port settings. Checking log files There are many log files generated by NMM client and associated features. These log files include errors that occur during the processes. Check the log files in the following order: 1. NMM client on page PowerSnap client on page Replication Manager on page Solutions Enabler on page Active Directory on page NetWorker server on page 276 In addition, third-party providers generate their own logs in place of the Solutions Enabler log (hwprov.log). The third-party documentation provides more information. 274 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

275 Troubleshooting NMM client Log files The NMM client log files are named: nmm.raw nsrcscd.raw Location Applogs folder. For example, C:\Program Files\Legato\nsr\applogs\. Description Both save and recover CLIs write to these files. The log files are cumulative, so they are appended with each run. The logging level of each log file is controlled by the debug level of the process (-D). PowerSnap client Log files NetWorker VSS client Interface Library: libvsspsclnt.xxxxx.log PowerSnap Client Core Processes. There are log files for each process that runs: nsrbragent.xxxxx.log nsrsnapagent.log nsrsnapbwragent.log nsrsnapck.log Location Logs folder. For example, C:\Program Files\Legato\nsr\logs\. Description Usually, the PowerSnap client creates one set of log files for each backup or recover session, and a debug and trace log are created. These log files are tied together by using the Snapshot Session ID. The logging level of the log files is controlled by setting a variable in NSR_PS_DEBUG_LEVEL in NetWorker server, in client configuration. Error messages in PowerSnap client log files also appear in the standard user interface outputs for NMM client. Replication Manager Log files The Replication Manager log files are: erm_clientxxxxx_debug.log erm_clientxxxxx_detail.log erm_clientxxxxx_summary.log Location Replication Manager Agent Service log files are in the logs\client folder of the RM installation. For example, C:\Program Files\EMC\rmagentps\logs\client\. Checking log files 275

276 Troubleshooting Description The log files are cumulative, and will wrap once they reach a certain length. The debug level can be set through the registry key HKLM\SOFTWARE\EMC\RMService\RMAgentPS\Client\CC_DEBUG_LEVEL. The default value is 2, but can be changed to 3. To change the default value: 1. Stop RM Services. 2. Change the value in the registry. 3. Restart RM Services. Error messages in Replication Manager log files also appear in the standard user interface outputs for NMM client. Solutions Enabler Log files The log files include a log file for the EMC VSS Provider and SYMAPI: hwprov.log symapi-<date>.log Location The Solutions Enabler product creates log files in the SYMAPI\logs folder of the Solutions Enabler installation. For example, C:\Program Files\EMC\SYMAPI\log\. Description The log files are cumulative, or based on the date. The logging level of the EMC VSS Provider log file is controlled by a registry key. Error messages in Solutions Enabler log files do not appear in the standard user interface outputs for NMM client. Active Directory Log files The log files associated with Active Directory are: nsradsave.log nsradrecover.log Location Applogs folder. For example, C:\Program Files\Legato\nsr\applogs\. NetWorker server Log files The NetWorker server creates several log files, which are documented in the EMC NetWorker Release 7.6 SP1 Administration Guide. 276 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

277 Troubleshooting Manually stopping and starting services NMM client processes may need to be manually stopped and started in conjunction with configuration and troubleshooting activities. The NetWorker server creates several log files. These log files are documented in the EMC NetWorker Release 7.6 SP1 Administration Guide which provides more information about starting and stopping services on Windows and UNIX hosts, Console server, NetWorker server, client, or storage node. Table 49 on page 277 lists the services for NetWorker, PowerSnap, and Replication Manager that are active on the system. Table 49 Services and processes used in NMM client Executable Product Category Function nsrexecd NetWorker Service Authenticates and processes the NetWorker server s remote execution requests and executes the save programs on the client. nsrpsd PowerSnap Service Provides PowerSnap client services, including snapshot consistency check function, to apply retention policy and backup functions to rollover snapshots. irccd.exe Replication Manager Service Provides Replication Manager client application and storage services for creating VSS-based snapshots and for rollback of VSS-based snapshots for EMC storage. RM_ExchangeInterface.exe Replication Manager Service Provides Replication Manager Server Exchange Interchange services to handle Exchange server 2007-specific commands for Replication Manager. rm_api.dll Replication Manager Library Library that provides Replication Manager client interface library for NetWorker, used by NetWorker backup and recover processes. nsrsnap PowerSnap Process Temporary process active during snapshot groups that provides client-side workflow for snapshot groups, including applying retention policy, spawning process to create the snapshot, and spawning process to rollover the snapshot. nsrsnap_vss_save NetWorker Process Temporary process active during snapshot groups that is responsible for executing the client-side workflow to create the snapshot for the save sets specified in the client resource. It is spawned by nsrsnap and will communicate with irccd.exe to create the VSS-based snapshot, and then will communicate with PowerSnap services to register the snapshot. nsrcscd.exe NetWorker Service This service acts as an agent to provide details about a system environment to the NMM user interface. A log file named nsrcscd.raw is generated in nsr\applogs folder. Libpsvssclnt.dll PowerSnap Library Library that provides PowerSnap client Interface for NetWorker backup and recover processes. nsrsnapagent nsrsnapbwragent Temporary Service Temporary Service Temporary service active during snapshot backup and restore operations that provides snapshot management functions to import and assign drive letters to a snapshot. Temporary service active during snapshot backup and file system snapshot browse operations that provides the ability to read the file system on the snapshot. winclient NetWorker Process Provides graphical user interface for NetWorker software. Manually stopping and starting services 277

278 Troubleshooting Configuring dedicated web front-end crawling NMM 2.3 supports dedicated web front-end crawling. To configure a dedicated web front-end by using the SharePoint Central Administration: 1. First, back up the existing host file. 2. By using SharePoint Central Administration, configure dedicated web front-end crawling. 3. Once the configuration is complete, a new host file is created by SharePoint Central Administration. 4. Append the host file information from backed-up host file to the new host file. 5. Configure NMM backup. Using nsr.dir to skip files for NMM backup and recovery Use nsr.dir, which is the NMM directive for exclusion of files for NMM backup and recovery. The files can be skipped both at file level as well as directory level. Ensure that both nsr.dir and the files that are to be skipped are at the same location. Troubleshooting issues during SQL databases directed recovery Review the following to troubleshoot issues that might come up during directed recovery of SQL databases: Make sure that the client machine where directed recovery browsing is performed has NMM 2.2 SP1 installed, otherwise the SQL databases are not displayed for directed recover browsing. Restore one database at a time. For directed recovery of multiple databases, separate paths cannot be provided for each database. All the selected databases are restored to a single target path. 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: 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. 278 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

279 Troubleshooting 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 EMC NetWorker Module for Microsoft Application Release 2.3 Administration Guide describe how to enter the NETBIOS name in the Aliases attribute. The EMC NetWorker Release 7.6 SP1 Administration Guide provides details about Network and server communication errors. Other troubleshooting resources Determine where the problem appears: If the problem appears on the NetWorker server, or otherwise seems to be on the server side, check to make sure that the NetWorker server is installed and configured correctly. Also, check the log files and error message documentation for the NetWorker server. If the problem appears to be with PowerSnap or Replication Manager, and is not unique to NMM client, check other documentation. The following documents provide specific error message, troubleshooting, or other documentation outside of NMM client: EMC NetWorker Installation Guide Release 7.6 SP1 EMC NetWorker Administration Guide Release 7.6 SP1 EMC NetWorker Error Message Release 7.6 SP1 EMC NetWorker PowerSnap Module Installation and Administration Guide EMC Replication Manager Administrator s Guide Other troubleshooting resources 279

280 Troubleshooting 280 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

281 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 Application Guide 281

282 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. 282 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

283 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 Application Guide 283

284 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. 284 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

285 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. N NDMP (Network Data Management Protocol) TCP/IP-based protocol that specifies how heterogeneous network components communicate for the purposes of backup and recovery. EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 285

286 Glossary NetWorker administrator NetWorker client NetWorker Console server NetWorker Management Console NetWorker server NetWorker storage node nonclone pool noncritical volume nonpersistent snapshot 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 Windows PE environment. Person who monitors the server status, loads backup volumes into storage devices, and executes day-to-day NetWorker tasks. P pathname persistent snapshot PiT (point-in-time copy) 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. 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. 286 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

287 Glossary policy pool PowerSnap provider proxy client 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 retrieve rollback restore 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. 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 287

288 Glossary rollover root 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 snapshot snapshot expiration policy 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. 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. 288 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

289 Glossary snapshot policy snapshot retention policy staging stand-alone device storage device storage node system state 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 copyof 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. W writer Database, system service, or application code that provides metadata document information about what to back up and how to handle VSS component 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. EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 289

290 Glossary 290 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

291 Index A Active Directory (AD) backups for disaster recovery 40 backups for object selection granularity 42 log files 276 Active Directory Lightweight Directory Services (AD LDS) 40 active node 134 AD LDS backup and recovery 40 AD recovery all objects for a disaster recovery 50 individual objects and attributes 51 null value restriction 53 restrictions for 51 schema object restriction 53 system-only attribute restriction 52 tombstone restriction 52 alternate mount path for proxy client 114, 170 alternate storage group, Exchange recovery to 145 application data save sets considerations for 158 application information attribute DPM 62 Exchange 113, 125, 169 Hyper-V 83 SharePoint SQL 23 application writers Hyper-V 82, 85 B backup Active Directory 42 backup client resource configuring 47 configuring DPM 65 configuring Hyper-V 86 configuring multiple 65, 86 backup command attribute DPM 66 Exchange 123, 174, 224 Hyper-V 87 SharePoint , 218 Backup content without interruption 204 backup groups configuring 46 backup roadmap Hyper-V 79 backup save sets DPM 63 Exchange 115 Hyper-V 83, 87 SharePoint , 239 SharePoint 2007 disaster recovery 229 specifying 48, 66 SQL 25 Bare Metal Recovery 244 best practices SQL backup and recovery 35 best practices for backup and recovery Exchange 113 Hyper-V child partition 95 Hyper-V parent partition 95 SQL in SharePoint C child partition best practices for backup and recovery 95 Hyper-V configurations 79 child partitions 77 CLARiiON E_VETO_PROVIDER error message 254 error message 254 replica takes long time 262 client resource configuring for backup 47 configuring for DPM backup 65 configuring for Hyper-V backup 86 configuring for SharePoint 2007 backup 215 configuring for SQL backup 26 configuring multiple 65, 86 configuring when in a cluster 26, 43, 64, 119, 172, 189 cluster server entering physical hostname of 49 scheduling backups for 26, 43, 64, 119, 172, 189 configuration database EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 291

292 Index SharePoint SharePoint 2007 recovery 225 critical volumes 245 D database level granularity 203 device configuring for rollover backup 44 directed recovery DPM-protected server 69 Exchange Server disaster recovery DPM 72 Hyper-V 93 Hyper-V parent partition 93 Microsoft Exchange Server planning for active directory 40 recovery for active directory 50 SharePoint SQL 35 DISASTER_RECOVERY 245 DPM configuring client resource for backup 65 directed recovery 69 disaster recovery options 73 granular recovery 67 DPM disaster recovery individual objects and attributes 72 E notification NetWorker events 253 EMC NetWorker 7.6 SP2 244 errors E_VETO_PROVIDER 254 E_VOLUME_NOT_SUPPORTED 254 error code 0x800423f3 255 Microsoft I/O write 262 NMM client 253 replica in a CLARiiON array 262 VSS CLIENT... Invalid Writer Selection 255 VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDE R 260 VSS_E_WRITERERROR_RETRYABLE 255 with Exchange 255 Event viewer 253 events notification 255 exceptions Windows Firewall 259 Exchange errors 255 point-in-time recovery 135 roll-forward recovery 134 URL encoding for save sets 117 Exchange backup scenarios 105 Exchange recovery alternate storage group 145 database can be overwritten selection 132 options for 131 Exchange Server 2007 directed recovery 149 F failover from the passive node 134 five distinct server roles Exchange 106 full farm backup and restore for catastrophe 203 G granular recovery DPM objects 67 groups configuring for backup 46 guest. See also child partition H host Hyper-V 78 Hyper-V backing up a virtual machine with multiple volumes 82 backup roadmap 79 components used for backup and recovery 82 configuring backups 85 configuring client resource for backup 86 disaster recovery 93 granular backup and recovery 96 host 78 parent partition disaster recovery 93 recovery 88 save sets 83 VSS writer 82 Hyper-V best practices child partition backup and recovery 95 parent partition backup and recovery 95 Hyper-V child partition configurations 79 Hyper-V storage and backup options 79 I improved management experience Exchange 106 improved setup experience Exchange 106 items searching for recovery 144 L label creating for pool 45 log files 253 Active Directory 276 NetWorker Server 276, 277 NMM client 275 PowerSnap client EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide

293 Index Replication Manager 275 Solutions Enabler 276 troubleshooting with 274 M marking items for recovery 143 Microsoft Exchange Server 2007 disaster recovery 151 Microsoft Windows Server , 60 mount path for proxy client 114, 170 MSDE turning writer on or off in registry 60 multiple client resources for backup 65, 86 N NetWorker events notification 253 NetWorker Monitor window 253 NetWorker Server log files 276, 277 NMM client error messages 253 log files 275 noncritical volume 246 notification NetWorker events 255 savegroup failed 255 notifications 253 types 253 NSR_ALT_PATH command 114, 170 NSR_DM_PORT command 113, 170 O offline recovery 244 optimized default settings Exchange 106 OSearch14 VSS Writer 238 overwrite prevention error Exchange database recovery 262 P parent partition best practices for backup and recovery 95 passive node 135 password restriction for active directory recovery 53 physical server Hyper-V 78 pool label for 45 ports Exchange proxy client communications 113, 170 post-restore synchronization of databases 204 PowerSnap client log files 275 proxy client mount path 114, 170 port number for communicating 113, 170 SharePoint serverless backup 210 SQL serverless backup 23 R recovery Exchange options 131 Hyper-V 88 marking items 143 searching for items 144 recovery error Exchange database 262 remote access attribute virtual cluster server specification 49 replica error message 255 takes long time in CLARiiON environment 262 Replication Manager error message 254 log files 275 resource for backup configuring 47 configuring multiple 65, 86 rollover backup device for 44 S save sets DPM 63 Exchange 115 Hyper-V 83 SharePoint SharePoint , 239 specifying for backup 48, 66 specifying for Hyper-V backup 87 SQL 25 SQL databases in SharePoint savegroup failed notification 255 search index files backup and recovery 204 searching for a recovery item 144 Security Configuration Wizard 259 selecting items for recovery 143 serverless backup 23 SharePoint 2007 backup 210 Service application 236 services 277 Services in SharePoint Shared Services Provider 237 SharePoint 2003 backups 189 best practices for backup and recovery 192 Client resource 189 recovery 191 save sets 188 SQL 2005 database recovery 191 SQL Server 2000 recovery 191 SharePoint 2007 configuration database 204 configuration database recovery 225 serverless backup 210 EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 293

294 Index specifying save sets for backup 216, 218 URL encoding 209 URL encoding for save sets 209 SharePoint Foundation SharePoint inventory list 204 SharePoint Services Writer 238 single VSS reference writer 203 Solutions Enabler log files 276 SPSearch4 VSS Writer 238 SQL database recovery for SharePoint serverless backup 23 URL encoding 25 SQL proxy client 23 SQL Server configure client resource 26 storage and backup options Hyper-V 79 storage array Exchange rollback requirements 111 syntax DPM save sets 63 Exchange save sets 115 Hyper-V save sets 83 SharePoint , 239 SQL 25 T troubleshooting checking other documents 279 U URL encoding Exchange save sets 117 SharePoint SharePoint 2007 save sets 209 SQL save sets 25 V virtual cluster server entering physical hostname of 49 scheduling backups for 26, 43, 64, 119, 172, 189 VSS CLIENT... Invalid Writer Selection 255 VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER 260 VSS_E_WRITERERROR_RETRYABLE 255 W Windows DR backup 247 Windows DR recovery 248 Windows Firewall NetWorker blocked by 259 Windows Server , 60 Windows SharePoint Services 2.0 see SharePoint EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide