EMC NetWorker Module for Microsoft Applications Release 2.1. Administration Guide P/N REV A01

Transcription

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

2 Copyright EMC Corporation. All rights reserved. Published September, 2008 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 listing of EMC product names, see EMC Corporation Trademarks on EMC.com. For the most up-to-date regulatory document for your product line, go to the Document/Whitepaper Library on EMC Powerlink All other trademarks used herein are the property of their respective owners. 2

3 Contents Figures Tables Preface Chapter 1 Overview NetWorker Module for Microsoft Applications NetWorker Module features Privileged user-level access Supported configurations Supported NetWorker Server hosts Windows operating system support Simple LAN-based configuration LAN-based configuration with a proxy client LAN-free configuration The VSS snapshot creation process Writers Providers Dynamic volume support Providers and backup performance NMM client snapshot backups Nonpersistent rollover backup Instant backup with or without rollover Serverless backup NMM client recoveries Conventional recovery Instant recovery Rollback recovery Disaster and granular backup and recovery for applications The NMM client interface Recover view Snapshot Management view Monitor view NMM client graphical user interface Opening the software and connecting to a NetWorker server Selecting an item for recovery Searching for an item

4 Contents Specifying a recovery browse time Selecting a backup version for recovery Viewing the volumes required for a recovery Chapter 2 Chapter 3 Configuring a Scheduled Backup Backup configuration roadmap Privileged user-level access Name resolution Best practices and considerations for backing up application data Best practices for backing up system volumes Task 1: Configure a backup pool for snapshot operations Configuring a device Configuring a label template Configuring a backup pool Labeling the device Task 2: Configure snapshot policies Snapshot policies for SYSTEM COMPONENTS backup Creating a snapshot policy Snapshot policy examples Task 3: Configure a backup schedule Task 4: Configure a backup group Task 5: Configure a Client resource Configuring a Client resource for applications Specifying save sets for application data Application information variable settings Task 6: Configure privileges Task 7: Configure a proxy client Backing up a clustered NMM Client NetWorker pathownerignore cluster functionality is not supported Cluster failover and backups Moving an NMM Client to another NetWorker server Recovering Data Performing a recovery System Writer recovery in Windows Server NetWorker recovery options Cluster recovery options ADAM recovery options DFS recovery options FRS recovery options NTDS recovery options Security recovery options Recovering file system snapshots that have not been rolled over Performing a disaster recovery of a NMM Client Disaster recovery when the NMM Client is not on a domain controller Disaster recovery when the NMM Client is on a domain controller Booting Windows in Directory Service Restore mode Performing an authoritative recovery of NTDS or FRS data Performing a directed recovery Recovering the Windows system configuration to an earlier state

5 Contents Chapter 4 Chapter 5 Microsoft SQL Server Backup and Recovery Microsoft SQL Server backup and recovery SQL Server versions supported by NMM Types of supported backup and recovery Components used by NMM for SQL data backup and recovery Specifying save sets for SQL data Displaying valid SQL data save sets URL encoding for SQL save sets SQL Server application information variable settings Serverless backup Performing SQL Server backups Full backup of an SQL Server Performing SQL Server recovery Recovering SQL Server 2000 embedded databases Recovering SQL Server 2000 stand-alone databases Recovering SQL Server 2005 databases Best practices for SQL Server backup and recovery Microsoft SharePoint Server Backup and Recovery Microsoft SharePoint Server backup and recovery SharePoint Server versions supported by NMM client SharePoint Server 2007 backup and recovery Types of SharePoint Server 2007 backup and recovery Requirements for installing SharePoint service pack NMM installation requirements for a Microsoft Office SharePoint 2007 system SharePoint 2007 data backed up by NMM Keeping backups and recoveries in sync Components used by NMM for SharePoint backup and recovery Specifying SharePoint 2007 save sets for application data Displaying valid SharePoint 2007 data save sets URL encoding for SharePoint save sets SharePoint 2007 Application information variable settings Performing SharePoint 2007 backups Configuring SharePoint 2007 backups Task 5: Configure a SharePoint 2007 Client resource Performing a full backup for a distributed SharePoint farm Performing SharePoint 2007 recovery Mandatory order for SharePoint recoveries Configuration database recovery requirements in full farm recovery Selecting valid items for 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 SharePoint 2007 disaster recovery Disaster recovery planning Additional conditions for successful SharePoint disaster recovery NMM backup of SharePoint servers SharePoint 2003 backup and recovery Types of supported backup and recovery Components used by NMM for SQL backup and recovery Specifying save sets for SharePoint 2003 SQL data

6 Contents Displaying valid SQL data save sets for SharePoint 2003 backup URL encoding for SQL save sets in SharePoint 2003 backup SQL application information variable settings in SharePoint 2003 backup Performing SharePoint 2003 backups Task 5: Configuring a SharePoint 2003 Client resource Performing a SharePoint 2003 recovery Recovering SQL Server 2000 stand-alone databases for SharePoint Recovering SQL 2005 databases for SharePoint Best practices for SQL Server backup and recovery of SharePoint 2003 databases SharePoint 2003 scenario of backup and recovery process Chapter 6 Chapter 7 Microsoft SharePoint 2007 Granular Backup and Recovery NMM support for granular backup and recovery of SharePoint items SharePoint objects available in NMM granular backup SharePoint limitations on document metadata recovery Components used by NMM for SharePoint 2007 granular backup and recovery Storage requirements and performance impact in SharePoint granular backup Specifying save sets for SharePoint granular backup SharePoint 2007 granular application information variable settings Performing SharePoint 2007 granular backups Configuring a SharePoint 2007 Client resource for granular backup SharePoint 2007 granular recovery SharePoint recovery search Searching and marking tips Searching for a SharePoint item Performing a granular recovery of SharePoint items SharePoint prerecovery options SharePoint recovery options Microsoft Exchange Server Backup and Recovery Exchange Server backup and recovery Exchange Server versions supported by NMM client NMM and Exchange Server support for L18N Exchange Server backup and recovery types Updating and modifying Exchange credentials Compatibility with previous Exchange Server backups Exchange Server data backed up by NMM Components used by NMM for Exchange Server backup and recovery Specifying Exchange save sets for application data Exchange Application information variable settings Serverless backup Snapshot process in an Exchange Server production and proxy client setup Best practices for Exchange backup and recovery Performing Exchange Server backups Configuring Exchange Server backups Configuring an Exchange Client resource

7 Contents Performing Exchange Server recovery Exchange recovery requirements and limitations Exchange recovery options Roll-forward recovery Point-in-time recovery Mounting the database after recovery Rollback restore of Exchange data by using NMM Exchange rollback operation requirements Recovery to an Exchange Recovery Storage Group Creating an RSG and adding target databases Recovering to the RSG Chapter 8 Chapter 9 Chapter 10 Microsoft Data Protection Manager Backup Data Protection Manager backup and recovery DPM Server versions supported by NMM client DPM backup and recovery types DPM data backed up by NMM Transportable backups of DPM Replicas not supported Components used by NMM for DPM backup and recovery Specifying DPM save sets for application data DPM application information variable settings Performing DPM Server backups Configuring DPM backups Configuring a DPM Client resource Performing DPM Server recovery Microsoft Data Protection Manager Granular and Disaster Recovery Performing a granular recovery of DPM objects Performing a granular directed recovery to a DPM-protected server DPM directed granular recovery scenario Performing a granular directed recovery Performing a disaster recovery of DPM Microsoft Hyper-V Backup and Recovery Hyper-V backup and recovery Hyper-V version requirements Operating system versions supported by NMM client Hyper-V parent partition backup and recovery types Hyper-V parent partitions, child partitions, and applications within child partitions Hyper-V storage and backup options supported by NMM Backup roadmap for Hyper-V Best practices for Hyper-V parent partition backup and recovery Best practices for Hyper-V child partition applications backup and recovery Components used by NMM for Hyper-V backup and recovery Specifying Hyper-V save sets for application data Hyper-V application information variable settings Performing Hyper-V backups Preparing a virtual machine for backup Hyper-V configuration requirements for backing up a virtual machine that contains multiple volumes NMM support for proxy backup of Hyper-V

8 Contents Configuring Hyper-V backups Configuring a Hyper-V Client resource Performing Hyper-V recovery Off-line and on-line recovery Hyper-V recovery Disaster recovery of a Hyper-V parent partition Chapter 11 Chapter 12 Chapter 13 Chapter 14 Chapter 15 Microsoft Windows Cluster Backup and Recovery Windows Server Cluster backup and recovery Cluster support in NMM client Compatibility with previous Windows Cluster backups Components used by NMM for Windows Cluster backup and recovery Windows Cluster application information variable settings Performing Windows Server Cluster backups Cluster failover and backups Windows Server Cluster recovery Performing a disaster recovery of a clustered client in Windows Server Disaster recovery of a cluster client Disaster recovery from a legacy VSS backup Disaster recovery of a clustered client from a legacy non-vss backup Monitoring a recovery Active Directory Recovery Recovering all Active Directory data Performing a granular recovery of AD objects and attributes Recovery Restrictions for Active Directory Active Directory and ADAM Backups Active Directory backup and recovery Types of supported backup and recovery Performing an AD or ADAM backup Performing a granular AD or ADAM backup Set up local Windows SYSTEM account as an ADAM administrator Granular backup tasks Snapshot Management Roll over a snapshot Roll back a snapshot Rollback recovery requirements Storage array descriptor file System rollback may fail with CLARiiON if the configuration information is not current Performing a rollback recovery Delete a snapshot NetWorker Client Management Specifying ranges for service and connection ports Specifying a password

9 Contents Chapter 16 Troubleshooting 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 NMM client issues Savegroup failed in scheduled backup In progress backup fails NetWorker is blocked by Windows Firewall Need to run utility to obtain Exchange Server information Requesting a snapshot for a volume on hardware that is not transportable 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 within NetWorker Module for Exchange Client may be promoted to full backups Incremental backups within NetWorker Module for SQL Server Client may be promoted to full backups Diagnosing VSS Writer Issues Modifying the Exchange 2007 COM+ component s user account or password Save sets may not appear in the recover window Recovery of AES-encrypted files fails without passphrase Unable to restore files encrypted with both Microsoft Windows Encrypting File System and AES encryption Anti-virus programs block recovery Checking log files NMM client PowerSnap client Replication Manager Solutions Enabler Active Directory NetWorker server Manually stopping and starting services Other troubleshooting resources Glossary Index 9

10 Contents 10

11 Figures Title Page 1 Simple LAN-based configuration LAN-based configuration with a proxy client LAN-free configuration VSS backup process NMM client main window Exclusion representation of recover items Snapshot Management view Monitor view Selected and partially selected items Using a conventional backup for directed recovery Local client on the taskbar next to Client Configuration Options dialog box Select Viewable Clients dialog box NMM Client dropdown list SharePoint 2007 stand-alone farm configuration SharePoint 2007 distributed farm configuration Restore Remote Dependencies dialog box Newly created databases created in SharePoint NMM backups available for recovery SQL databases selected for recovery in NMM Databases recovered to SQL Server SharePoint Server Central Administration window SharePoint Portal Server Central Administration, Manage Portal Sites page Portal creation and restore options Portal restore and database names Confirmation page for request to create a portal site Status page for portal creation process Operation Successful page displayed when portal creation is complete Recovered databases and SharePoint portal visible and available in SharePoint Sample output from nsr_moss_save NMM displaying SharePoint 2007 browsing for recovery items NMM displaying Search tab for SharePoint 2007 recovery Snapshot process with Exchange production server and proxy client Restore to RSG command on context menu RSG Configuration command on context menu RSG Configuration error message RSG Configuration correct message Public folders cannot be recovered to an RSG NMM protection of DPM Directed granular recovery to a DPM-protected client

12 Figures 41 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 recovery modes Recover submenu for DPM recovery DPM disaster recovery options Windows Server 2008 host with Hyper-V virtual machine child partitions Hyper-V storage options NMM backup of Hyper-V components Hyper-V recovery items available Disaster recovery order for a Hyper-V server Troubleshooting process

13 Tables Title Page 1 Currently supported writers Support for disaster and granular backup and recovery Backup tasks Access privileges needed for NMM Best practices and considerations for application backups Conventional backup settings Instant snapshot policy Instant snapshot with rollover policy Considerations for NMM Client backup schedules Save set syntax Special characters and their URL-encoded values Application information variable settings Configuration requirements for a proxy client Additional steps and considerations for backing up a clustered Client resource Access privileges needed for NMM SQL save set syntax Special characters and their URL-encoded values SQL variable settings for Application Information attribute SQL Server backup and recovery best practices and considerations SharePoint save set syntax Special characters and their URL-encoded values SharePoint application information variable settings SharePoint server backups for disaster recovery SQL save set syntax for SharePoint Special characters and their URL-encoded values SQL variable settings for application information attribute SQL Server backup and recovery best practices and considerations SharePoint granular recovery save set syntax for SharePoint 2007 objects Application information variable settings SharePoint recovery search fields Exchange save set syntax Special characters and their URL-encoded values Exchange application information variable settings NMM Data Protection Manager commands DPM Server 2007 save set syntax DPM application information variable settings Hyper-V child partition configurations Backup tasks for Hyper-V NMM Hyper-V commands Hyper-V save set syntax

14 Tables 41 Hyper-V application information variable settings Windows Cluster application information variable settings Additional steps and considerations for backing up a clustered Client resource Setting up a granular AD or ADAM backup Notifications and errors Services used in NMM client

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. Audience Related documentation Conventions 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 Related documents include: EMC NetWorker Module for Microsoft Applications Release 2.1 Installation Guide EMC NetWorker Module for Microsoft Applications Release 2.1 Release Notes EMC NetWorker Release 7.4 Service Pack 2 Multiplatform Version Administration Guide EMC Information Protection Software Compatibility Guide EMC Solutions Enabler Symmetrix CLI, Version 6.3 Quick Reference EMC uses the following conventions: Note: A note presents information that is important, but not hazard-related. 15

16 Preface CAUTION A caution note contains information that is essential to avoid data loss. 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, filenames, functions, utilities URLs, pathnames, filenames, directory names, computer names, 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 call, 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) 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 EMC Customer Service on Powerlink. To open a service request through Powerlink, you must have a valid support agreement. Please contact your EMC sales representative for details about obtaining a valid support agreement or to answer any questions about your account. 16

17 Preface 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: 17

18 Preface 18

19 1 Overview This chapter includes the following topics: NetWorker Module for Microsoft Applications Supported configurations The VSS snapshot creation process NMM client snapshot backups NMM client recoveries The NMM client interface NMM client graphical user interface Overview 19

20 Overview NetWorker Module for Microsoft Applications The EMC NetWorker Module for Microsoft Applications (NMM) works with Microsoft Volume Shadow Copy Service (VSS) technology to provide snapshot backup and recovery services for file systems, and application, and operating system data. The NMM client allows for the creation of point-in-time snapshot data. A snapshot can be retained on storage volumes for quick access. One can also perform a rollover of a snapshot to a traditional backup medium such as a tape, file type device, or advanced file type device. Data can be recovered either from a snapshot or from the backup. NetWorker Module features This NetWorker Module can be set up in a LAN-based or LAN-free environment. NMM provides the following features: Support for the following topologies: Simple LAN-based configuration on page 23 LAN-based configuration with a proxy client on page 24 LAN-free configuration on page 25 Support for several types of backup and recovery, depending on the types available for the given application or operating system: Instant backup with or without rollover on page 32 Nonpersistent rollover backup on page 32 Serverless backup on page 32 Conventional recovery on page 34 Instant recovery on page 34 Rollback recovery on page 34 Application support: Microsoft Exchange Server 2007 Microsoft Exchange Server 2003 Microsoft SQL Server 2005 Microsoft SQL Server 2000 Microsoft Office SharePoint Server 2007 Microsoft SharePoint Portal Server 2003 Windows SharePoint Services 3.0 Windows SharePoint Services 2.0 Microsoft System Center Data Protection Manager 2007 Windows Server 2008 Hyper-V Windows volumes and system components Windows Cluster support Active Directory Application Mode (ADAM) Active Directory 20

21 Overview Note: Application support often requires a minimum specific service pack level. The service pack levels frequently change. The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about which service packs are required for each application. Support for Windows VSS Provider: Microsoft Software Shadow Copy provider for use with most leading hardware arrays EMC Symmetrix and Symmetrix DMX TM arrays with EMC VSS Provider EMC CLARiiON arrays with EMC VSS Provider Celerra arrays with Celerra VSS Provider EqualLogic PS Series arrays with EqualLogic Integration ToolKit IBM Storage System DS8000 IBM Storage System DS6000 Check the EMC Information Protection Software Compatibility Guide for the most up-to-date information about hardware array versions supported and NMM compatibility. Privileged user-level access All NMM users must have administrator-level privileges for all resources they access: NetWorker server Each NetWorker Module for Microsoft Applications (NMM) client machine All Microsoft applications protected by NMM, such as: Windows Server Data Protection Manager (DPM) SharePoint Server SQL Server Exchange Server Network domains Storage servers NetWorker Module for Microsoft Applications 21

22 Overview Supported configurations This section describes the basic configurations in which the NMM client is supported. Supported NetWorker Server hosts The NMM Client supports NetWorker Server or later on the following hosts: AIX HP-UX (PA-RISC) Solaris (SPARC) Windows Note: The NMM Client is not supported from NetWorker Server that is running on Linux. The NMM Client supports Internationalization (I18N). NetWorker 7.4 SP3 or later is required for Microsoft Office SharePoint 2007 granular protection. The following NetWorker features are not supported: NetWorker clone, staging and archive Localization (L10N) Installation of dedicated storage node on NMM client host. Note: NMM does support proxy storage node, as described in LAN-free configuration on page 25. Manual (adhoc) backups De-duplication Windows operating system support NMM client supports the following versions of Windows and Windows-related features: Microsoft Windows Server 2008 (x86, x64) Standard, Enterprise, DataCenter Editions Microsoft Windows Server 2003 R2 (x86, x64) Standard, Enterprise, DataCenter Editions Microsoft Windows Server 2003 (x86, x64) Standard, Enterprise, DataCenter Editions Microsoft Windows Storage Server 2003 Microsoft Windows Storage Server 2003 R2 System state recovery, file servers, and operating system roles including Active Directory, DHCP and Terminal Services GUID Partition Table disks: No disk size limit on Windows environments with CLARiiON storage (SnapView clone, SnapView snap, and SAN Copy technologies only) 22

23 Overview Disk size limit of less than 2 TB on Windows environments with Symmetrix storage Note: The following Windows Server versions are not supported: Windows Server 2008 Core installation, and Windows IA64 editions. In addition, the following Windows features are not supported: BitLocker encryption LAN-based Proxy Client or LAN-free backups, if dynamic disks are used VSS Hardware Providers with Windows dynamic disks Microsoft Software Shadow Copy provider to perform persistent snapshots of clustered disks Windows Automated System Recovery (ASR) Note: Windows Storage Server Single Instance Storage (SIS) is supported, but recoveries will recover file data for all duplicate files. Data will not be lost if there is sufficient disk space to hold the duplicate copies. The EMC Information Protection Software Compatibility Guide contains additional and the most up-to-date information about NMM compatibility. Simple LAN-based configuration Figure 1 on page 24 shows a simple LAN-based configuration with a storage area network. In a LAN-based configuration, the production data is stored on a storage area network (SAN) or direct-attached storage (DAS). The data path to the NetWorker storage node devices is over a LAN. The application server that is being protected has the NMM client installed. The data moves as follows: 1. The NetWorker server, which must be release or later, initiates the process by contacting the application server where the NMM client software is installed. 2. The application server with the NMM client software creates a snapshot of the data on the storage volume. Note: In Figure 1 on page 24, snapshots are represented by S1 through S5. 3. The application server with the NMM client software uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, or tape. Supported configurations 23

24 Overview NetWorker Server or later LAN Application server NetWorker Module for Microsoft Applications SAN NetWorker Storage Node 7.3.x Traditional storage Primary storage (For example, CLARiiON or Symmetrix) S5 S1 S4 S3 S2 GEN Figure 1 Simple LAN-based configuration LAN-based configuration with a proxy client Figure 2 on page 25 shows a LAN-based configuration with a storage area network and a proxy client. Both the application server and the proxy client have the NMM client installed. Note: The application server and the proxy client must use the same version, NetWorker Module for Microsoft Applications release 2.1. If NMM 2.1 is installed on either the application server or the proxy client machine, then the other machine must also use NMM 2.1. Backup and recovery will fail if NMM 2.1 is used on one of these machines, and an earlier version of NMM is used on the other. A proxy client is a host that acts as a remote DM (data mover) when snapshots are rolled over to a conventional backup medium. A proxy client frees resources on the application server. When a backup operation uses a proxy client, it is known as a serverless backup. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM client software is installed. 2. The application server with the NMM client software creates a snapshot of the data on the storage volume. Note: In Figure 2 on page 25, snapshots are represented by S1 through S5. 24

25 Overview 3. The snapshot is made visible to the proxy client. 4. The proxy client uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, or tape. NetWorker Server or later LAN Application 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 7.3.x Traditional storage GEN Figure 2 LAN-based configuration with a proxy client LAN-free configuration Figure 3 on page 26 shows a LAN-free configuration with a storage area network. The NMM client is installed on the application server. The proxy client is installed on the NetWorker storage node. You can set up a NetWorker storage node release or later as a proxy client to avoid the network traffic that is generated when a snapshot is rolled over to a conventional backup medium. Network traffic is avoided because both the conventional backup device and the snapshot are directly attached to the storage node. Note: Install the proxy client software by using the NMM client software package. The data moves as follows: 1. The NetWorker server initiates the process by contacting the application server where the NMM client software is installed. 2. The application server with the NMM client software creates a snapshot of the data on the storage volume. Note: In Figure 3 on page 26, snapshots are represented by S1 through S5. Supported configurations 25

26 Overview 3. The snapshot is made visible to the proxy client. 4. The proxy client, in this case the storage node, uses a snapshot in primary storage to transfer the data into a conventional backup medium such as a file type disk, advanced file type disk, or tape. The NetWorker server and the application server communicate through the LAN. However, the data itself is not transferred across the LAN because the conventional backup medium is attached directly to the NetWorker storage node. NetWorker Server or later LAN Application server NetWorker Module for Microsoft Applications Proxy client NetWorker Storage Node 7.3.x SAN Primary storage (For example, CLARiiON or Symmetrix) S5 S1 S4 S3 S2 Traditional storage GEN Figure 3 LAN-free configuration 26

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

28 Overview 4. Requestor asks VSS to create snapshot. Requestor 1. NetWorker software (the requestor) asks VSS to enumerate writers and gether their metadata. 2. Writers provide an XML description of backup components and define the recover method. 5. VSS tells the writers to freeze activity. Writer Writer Writer Writer 7. VSS tells the writers to resume activity. Writer 3. VSS asks which providers can support a snapshot for each of the required volumes. 6. VSS tells the providers to create the snapshot of the current state on disk. Microsoft VSS Software Provider EMC VSS Provider (CLARiiON or Symmetrix) Disk 1 Disk 2 Disk 3 Disk 3 GEN Figure 4 VSS backup process Writers Writers provide information about what data to back up, and specific methods for handling components and applications during backup and recovery. They also identify the type of application or service that is being backed up. If a service or application is present on a system but is not active, information from its writer will not be available. Consequently, a writer can appear or disappear from backup to backup. 28

29 Overview Table 1 on page 29 lists the writers that are supported for the NMM client. Table 1 Currently supported writers Writer type Volumes Writers supported by NMM A file system path such as D:\data Note: NMM only supports NTFS volumes. It does not support FAT16 and FAT32 volumes. Also, NMM does not support backup of raw volumes. Applications Windows system components (Windows Server 2003 and Windows Server 2008 unless otherwise noted) Microsoft ADAM (Active Directory Application Mode) Microsoft Exchange Server 2003 Microsoft Exchange Server 2007 Microsoft System Center Data Protection Manager 2007 Microsoft Distributed File Replication (Windows Server 2003) Microsoft Active Directory Lightweight Directory Services (AD LDS) Microsoft SharePoint Portal Server 2003 Microsoft Office SharePoint Server 2007 Windows SharePoint Services 2.0 Windows SharePoint Services 3.0 Microsoft SQL Server 2000 Microsoft SQL Server 2005 Windows Server 2008 Hyper-V BITS (Background Intelligent Transfer Service) COM+ REGDB (Registration Database) Certificate Authority Cluster Database (Windows Server 2003) Cluster Writer (Windows Server 2008) DHCP (Dynamic Host Configuration Protocol) Jet Event log FRS (File Replication Server) FSRM (File Storage Resource Manager) Microsoft Distributed File Replication (Windows Server 2003) IIS Configuration Writer (Windows Server 2008) IIS Metabase MSDE (Microsoft SQL Server Desktop Engine for SQL 2000 embedded databases) MSSearch Service Writer (Windows Server 2008) NPS VSS Writer (Network Policy and Access Service, Windows Server 2008) NTDS (Active Directory Schema) Registry RSM (Removable Storage Manager) Remote Storage Manager Shadow Copy Optimization Writer (Windows Server 2008) SQL Embedded (SQL 2005 Express) Terminal Services Gateway Writer (Windows Server 2008) Terminal Services Licensing WINS (Windows Internet Name Service) WMI (Windows Management Instrumentation) The VSS snapshot creation process 29

30 Overview Note: Files located in an FTP directory are not included in a SYSTEM COMPONENTS snapshot. Typically, FTP files are stored by IIS in C:\inetpub. IIS Metabase files are configuration files, which are backed up as part of SYSTEM COMPONENTS. The FTP files are content files, and must be backed up separately. Providers A provider is used to capture snapshots. One of the following types of providers are available: EMC VSS Hardware Provider, which supports EMC Symmetrix, Symmetrix DMX, and CLARiiON arrays EMC Celerra VSS Hardware Provider, which supports Celerra arrays Dell EqualLogic VSS Hardware Provider, which supports EqualLogic PS Series arrays Microsoft Software Shadow Copy provider IBM SystemStorage DS Open API Package, which supports IBM Storage, which supports IBM Storage System DS6000 and DS8000 The Microsoft Software Shadow Copy provider is a host-based provider that works with any type of storage hardware. The EMC VSS Hardware Provider works with an CLARiiON or a Symmetrix disk array. Some features of the NMM client, such as serverless backup and rollback recovery, are available only with hardware providers such as the EMC VSS Hardware Provider. The NetWorker Module for Microsoft Applications Release 2.1 Installation Guide provides more information about using NMM with a VSS Hardware Provider, including hardware array installation and configuration, and NMM installation and configuration. Note: NMM does not support rollback restore for backups performed by EqualLogic or Celerra hardware. Only conventional restore and snapshot restore are supported for backups performed by EqualLogic or Celerra hardware. Dynamic volume support In Windows Server 2003 and Windows Server 2008: NMM supports snapshots of dynamic volumes that use the Microsoft Software Shadow Copy provider. NMM provides software-based support for: Dynamic volume on a single disk. Dynamic volume spanning multiple disk. NMM does not support dynamic volumes in striping. NMM does not support hardware-based VSS transportable snapshots of dynamic volumes. NMM will attempt to perform a hardware-based VSS transportable snapshot when a proxy backup host is specified by using NSR_DATA_MOVER in the application information field of the Client resource. 30

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

32 Overview NMM client snapshot backups Backups are configured as scheduled snapshot backups on a NetWorker server release or later. Note: Manual (adhoc) backups, from either the command line or from the NMM client, are not supported. However, one can manually start a scheduled backup at any time. The NMM client supports three types of snapshot backups: Nonpersistent rollover backup on page 32 Instant backup with or without rollover on page 32 Serverless backup on page 32 Snapshot backups are specified through a snapshot policy and various settings for the Client resource. Snapshot policies and Client resources are set up on the NetWorker server. Chapter 2, Configuring a Scheduled Backup, provides more information about configuring snapshot policies and Client resources. Nonpersistent rollover backup A nonpersistent snapshot backup (also referred to as a live backup) creates a point-in-time snapshot of the data and then performs a rollover to a conventional backup medium such as tape, file, or advanced file type device. The original snapshot is automatically deleted from the NMM client. Instant backup with or without rollover An instant backup creates and retains a snapshot on a mounted storage disk volume. Depending on how backups are configured, a snapshot that is created during an instant backup may be configured to roll over to a conventional backup. While the snapshot resides on a mounted storage disk volume, it is referred to as a persistent snapshot. Retention of persistent snapshots on a mounted storage disk volume enables one to perform an instant recovery. The number of persistent snapshots that can be retained on a volume depends on the amount of resources available. Other factors that constrain the number of persistent snapshots include: Snapshot technology that is used, either copy-on-write or split-mirror. Input/output patterns of the drive. Processing involved in running a snapshot backup group. Serverless backup A proxy client is used in conjunction with instant snapshot backups to provide serverless backups. Serverless backups free the application server from much of the processing involved in a nonpersistent or instant snapshot backup. In a serverless backup, a snapshot is created on the application server and then immediately moved to the proxy client for further processing. Serverless backups are particularly useful when there is additional processing involved in a snapshot backup. For example, to help determine whether a snapshot of a Microsoft Exchange database is consistent, the Exchange utility, eseutil, should be 32

33 Overview run against the snapshot. Running eseutil can be disk intensive. Offloading the work from the Exchange Server to a proxy client frees resources on the Exchange Server. A serverless backup can be rolled over to a conventional backup. That backup can then remain on the mounted storage disk volume as a persistent snapshot. Note: Serverless backup is available only with VSS hardware providers and is subject to the capabilities of the vendor s hardware. The EMC VSS Provider for CLARiiON and Symmetrix provides the capability to perform serverless backup operations for these storage platforms. NMM client snapshot backups 33

34 Overview NMM client recoveries There are three types of recoveries: Conventional recovery on page 34 Instant recovery on page 34 Rollback recovery on page 34 By default, recoveries are performed from a conventional backup. If a conventional backup is not available for the selected browse time, an instant recovery is performed. The default recovery method can be specified in the NetWorker recovery options dialog box. NetWorker recovery options on page 74 provides more information about these recovery methods. Conventional recovery A conventional recovery consists of recovering data from a snapshot that has been rolled over to tape. Conventional recoveries support the same level of item selection as do instant recoveries. Instant recovery Instant recoveries are performed on persistent snapshots. An instant recovery can take less time to complete than a conventional recovery because the snapshot is available on a mounted disk storage volume rather than on a conventional backup medium. Instant recoveries support the selection of individual files in a file system snapshot. Additionally, instant recoveries support the selection of individual components at whatever level of granularity is supported by the system or application writer. If the persistent snapshot is created by using a proxy client, the snapshot file system on the proxy client is read to restore the files. In this way, performance is improved even further because the job of processing the snapshot for recovery is off-loaded from the NMM client production host to the proxy client. The procedure to perform an instant recovery of file system data differs if only a persistent snapshot is available. Chapter 3, Recovering Data, provides more information about performing recoveries. Note: When performing an instant recovery, the snapshot may become invalidated. This can occur if the snapshot is based on copy-on-write technology. If a large amount of data is recovered to the original volume, the cache may overflow. This is true for the Microsoft VSS software provider and for hardware providers that use copy-on-write technology, such as CLARiiON snapshots and Symmetrix virtual devices. Rollback recovery A rollback recovery is the process of returning data volumes to an earlier point-in-time. The entire contents of a persistent snapshot is recovered during a rollback recovery. One cannot select individual components in a rollback recovery operation. A rollback recovery is the fastest way to recover the contents of a persistent snapshot. 34

35 Overview A rollback recovery is known as a "destructive" recovery because all changes that were made to the file systems after the selected snapshot was taken are overwritten. For example, suppose that a snapshot of a database is taken every hour. At 5:30 p.m., it is determined that the database is corrupt and that the last known consistent database snapshot was taken at 5:00 p.m. When the database host is rolled back to the 5:00 p.m. snapshot, all database transactions between the time of the 5:00 p.m. and 5:30 are overwritten. The following list describes additional requirements and conditions that apply to snapshots and rollback restore: The snapshot to be rolled back must reside on a CLARiiON or Symmetrix storage system that is supported with the EMC VSS Provider. The NMM client to which the snapshot is to be rolled back must be supported with a proxy client. 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 products. Roll back a snapshot on page 269 provides more information about rollback recoveries. Disaster and granular backup and recovery for applications NMM provides disaster and granular backup and recovery for most applications: Full disaster backup and recovery means the entire volume or database for that application is backed up, and the entire volume or database is recovered as a whole. In disaster backup and recovery, items cannot be selected at a granular level. In granular backup, individual items can be selected for backup. In granular recovery, individual items can be selected for recovery. For some applications, granular recovery of items requires that the items be specified for a granular backup. For other applications, items cannot be specified for backup at a granular level, but can be selected for granular recovery from the full backup. NMM client recoveries 35

36 Overview Table 2 on page 36 lists the support provided by NMM for disaster and granular backup and recovery for Microsoft applications and volumes. Table 2 Support for disaster and granular backup and recovery Active Directory SQL Server Exchange Server Microsoft Office SharePoint Server 2007 Data Protection Manager Hyper-V File system Disaster (full backup Granular backup Disaster (full recovery) Granular recovery X X X X X X X X X X X X X X X X X X X X X X X X X X 36

37 Overview The NMM client interface The NMM client interface has three views: Recover view on page 37 Snapshot Management view on page 39 Monitor view on page 40 Recover view With the exception of rollback recovery, all recoveries are performed from the Recover view. Rollback recoveries use the Snapshot Management view. Figure 5 on page 37 shows the Recover view. Main toolbar Navigation tree Client selection (clustered client only) Available views Figure 5 Summary of selected items NMM client main window View-specific toolbar The NMM client interface 37

38 Overview The summary of selected items can also display exclusions, which shows only those items that are not selected for recovery. This view can be helpful when many items are selected for recovery. Figure 6 on page 38 shows an exclusion representation. Items in red are excluded from recovery Figure 6 Exclusion representation of recover items To view an exclusion representation, right-click in the summary pane at the bottom of the window and select Exclusion Representation. 38

39 Overview Snapshot Management view Various operations on snapshots are performed from the Snapshot Management view shown in Figure 7 on page 39. Figure 7 Snapshot Management view The following operations can be performed on snapshots: Rollover snapshot Rollback snapshot Delete snapshot In most cases, snapshot rollover and delete operations are performed automatically based on snapshot policies, which are set up on the NetWorker server. However, if you need to manually delete or roll over a snapshot, you can do so in the Snapshot Management view. Chapter 2, Configuring a Scheduled Backup, provides more information about snapshot policies. Chapter 14, Snapshot Management, provides more information about performing manual snapshot operations from the Snapshot Management view. The NMM client interface 39

40 Overview Monitor view Recovery and snapshot management operations can be monitored in the Monitor view shown in Figure 8 on page 40. Figure 8 Monitor view Most messages displayed in the Monitor view are also written to log files. Chapter 16, Troubleshooting, provides more information about log files. You can also copy and paste text from the Monitor view to another application. 40

41 Overview NMM client graphical user interface This section describes how to perform the basic tasks in the NMM client interface. Opening the software and connecting to a NetWorker server You must first connect to the NetWorker server on which the backup was configured to recover data. To connect to a NetWorker server: 1. From the Start menu, open the NMM client software. If you have opened the NMM client before, proceed to step 2 on page 41. If this is the first time you have opened the NMM client, the Change NetWorker Server dialog box appears, and you can proceed to step 3 on page From the Main toolbar, click the NetWorker Server icon. The Change NetWorker Server dialog box appears. 3. Click Update Server List to browse for NetWorker or later servers. The discovery process may take a few minutes. 4. When the list is updated, select a server. The selection appears in the Server field. You can also type a name in the Server field. 5. Click OK. Note: You can also select Configure Options from the Options menu to connect to a NetWorker server. NMM client graphical user interface 41

42 Overview Selecting an item for recovery To select items for recovery, click the checkbox beside a node in the navigation tree. A check mark indicates that the node is selected. By default, all items contained in the node, such as folders and files, will also be selected for recovery. To clear an item contained in a selected node, expand the node and click the checkbox beside the item to clear it. The check mark disappears. Figure 9 on page 42 depicts one selected item and several partially selected nodes in the navigation tree. Solid box indicates that some items, not all, below this node are selected Check mark indicates that the item is selected. Figure 9 Selected and partially selected items Searching for an item To search for a recovery item: 1. Click Search above the navigation tree. 2. In the Path field, type a directory path. 3. Optionally, in the Name field, type the name of the search item. You can refine your search as follows: Literal match (case-insensitive) Type abc to return abc, ABC, or AbC but not abcd or ABCD. Literal match (case-sensitive) Type "abc" to return abc but not ABc or abcd. Name contains (case-insensitive) Type %abc% to return abc, abcd, ABCD, or xyzabcde. Name starts with (case-insensitive) Type abc% to return abcd or ABCde but not xyzabcde. 42

43 Overview Name ends with (case-insensitive) Type %abc to return xyzabc but not ABCde. Single-character match search using the? wildcard Type? to return single character entries and drive volumes, such as C or D. Type WMI?Writer to return WMI Writer. Multiple-character match search by using the * wildcard Type *.txt to return all entries with a.txt extension. Type * to return all items within the selected container. Type *writer* to return all writers. Search by using both the * and? wildcard Type *??I*writer* to return WMI Writer. 4. Click Search. The Details pane displays the results of the search. Specifying a recovery browse time To browse for items that were backed up on or before a particular time: 1. From the application toolbar, click the Browse calendar icon. 2. Select the arrows to select the date and time, then click OK. The navigation tree displays backup items from the specified date and earlier. Selecting a backup version for recovery This topic applies to system recovery or Active Directory recovery operations only. Snapshot Management on page 267 provides more information about rollback snapshot recoveries. To view the versions of an item that were backed up prior to the current browse time: 1. In the navigation tree, select a recover item. Selecting an item for recovery on page 42 provides more information about selecting an item. 2. Right-click the selected item and select Versions from the pop-up menu. 3. Select the backup version to recover. 4. Select Use selected item backup time as new browse time to change the browse time to the same date as the selected backup version. 5. Click OK. The recover items displayed in the navigation tree are from the selected browse time. NMM client graphical user interface 43

44 Overview Viewing the volumes required for a recovery There are no NetWorker volumes associated with a snapshot backup until the snapshot has been rolled over to a NetWorker server. If you select to view the required volumes for a system component or application data snapshot that has not been rolled over, no volumes will be displayed. To view the volumes that are required for a recovery operation: 1. In the navigation tree, select a recover item. Selecting an item for recovery on page 42 provides more information about selecting an item. 2. Right-click the selected item and select Required Volumes from the pop-up menu. The Required NetWorker Volumes dialog box appears with a list of the volumes that must be mounted: If a volume is already mounted, the device name is shown after the volume name. If a required volume is not mounted, the administrator is prompted to mount it after the recovery operation is started. 3. Click OK. 44

45 2 Configuring a Scheduled Backup This chapter includes the following topics: Backup configuration roadmap Task 1: Configure a backup pool for snapshot operations Task 2: Configure snapshot policies Task 3: Configure a backup schedule Task 4: Configure a backup group Task 5: Configure a Client resource Task 6: Configure privileges Task 7: Configure a proxy client Backing up a clustered NMM Client Moving an NMM Client to another NetWorker server Configuring a Scheduled Backup 45

46 Configuring a Scheduled Backup Backup configuration roadmap This chapter describes the seven tasks required to configure most types of backups. Review Table 3 on page 46 to determine which tasks are required to configure your backups. Table 3 Backup tasks (1 of 2) Type of backup 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, etc. Other Window system components, as listed in Table 1 on page 29. Application data, such as: Microsoft SQL Server Microsoft SharePoint Microsoft Exchange Server Microsoft System Center Data Protection Manager (DPM) Microsoft Hyper-V Microsoft Windows Server Cluster NetWorker Module features on page 20 lists the specific versions supported for each of these applications. Required action Complete tasks 1 through 7: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Task 5: Configure a Client resource on page 59 Task 6: Configure privileges on page 66 Task 7: Configure a proxy client on page 67 Complete tasks 1 through 4: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Review the information in Best practices and considerations for backing up application data on page 48. Continue configuration with the specific instructions for the application in: Performing SQL Server backups on page 104 Performing SharePoint 2003 backups on page 142 Performing SharePoint 2007 backups on page 121 Performing Exchange Server backups on page 187 Performing DPM Server backups on page 209 Performing Hyper-V backups on page 234 Performing Windows Server Cluster backups on page

47 Configuring a Scheduled Backup Table 3 Backup tasks (2 of 2) Type of backup For all other applications and systems supported by NMM Required action Complete tasks 1 through 7: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Task 5: Configure a Client resource on page 59 Task 6: Configure privileges on page 66 Task 7: Configure a proxy client on page 67 An NMM client that is part of a cluster Review the information in Backing up a clustered NMM Client on page 69 Complete tasks 1 through 7: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Task 5: Configure a Client resource on page 59 Task 6: Configure privileges on page 66 Task 7: Configure a proxy client on page 67 An Active Directory server Complete the tasks in Chapter 13, Active Directory and ADAM Backups. Privileged user-level access Because NMM requires access to protected data and system files, make sure all users who will be running or configuring NMM backups and recoveries have the appropriate level of privileges for all resources they must access. Table 4 on page 47 describes the privilege levels needed. Table 4 Access privileges needed for NMM Resource NetWorker Server NetWorker Module for Microsoft Applications client machine All applications protected by NMM, such as: Windows Server Microsoft Data Protection Manager Microsoft Office SharePoint Server Microsoft SQL Server Microsoft Exchange Server Network domain Storage node servers Privileges needed NetWorker Administrator or NetWorker Backup Operator Windows Administrator or Windows Backup Operator Windows Adminstrator Windows Domain Administrator Windows Administrator Backup configuration roadmap 47

48 Configuring a Scheduled Backup 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, 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, make sure to perform the following: Add the NetWorker server name to either the local hosts file (located in %SystemRoot%\system32\drivers\etc) or the Domain Name Server that contains the names of all servers on your network. When configuring a Client resource, specify the NETBIOS name for the client in the Aliases attribute. Configuring a Client resource for applications on page 59 describes how to enter the NETBIOS name in the Aliases attribute. Best practices and considerations for backing up application data Table 5 on page 48 lists the considerations for specifying values in the Save Set attribute for a particular Client resource. Table 5 Best practices and considerations for application backups Consideration Different policies for application server data Installation path for application server program Copy-on-write versus mirroring NetWorker modules and the NMM Client Microsoft SQL Server data Best practice For application servers such as SQL or Exchange Servers, back up the server application data under a schedule different than the host operating system data and volumes. Typically, application data is backed up several times a day while operating system data and volumes are backed up less frequently. To accomplish this, create a separate backup group, snapshot policy, and Client resource for: Server application data Volumes and operating system data 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. Large or fast-changing databases 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 the EMC VSS Provider. If you attempt to use both the NMM Client and a NetWorker module to back up application data, the module backups will be promoted to Full backups. NMM client issues on page 284 provides more information about issues that may be encountered with the NMM client. If SQL Server 2005 backups were performed when the SQL Server VSS Writer service was disabled, and you subsequently enable the writer, perform a complete backup of SQL 2005 data. Performing a complete backup enables you to recover all SQL Server 2005 data from the same application folder, which is named SQLServerWriter. 48

49 Configuring a Scheduled Backup In addition to these best practices for all NetWorker Module for Microsoft Applications(NMM) backups, there are application-specific best practices: Best practices for Exchange backup and recovery on page 185 Best practices for SQL Server backup and recovery on page 108 Best practices for backing up system volumes To protect against a disaster, ensure that all volumes and Windows system components are backed up. Also ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of first, last, or all. Note: Do not specify none. Disaster recovery can only be performed from a conventional backup. Creating a snapshot policy on page 53 provides more information about snapshot policies and values. Backup configuration roadmap 49

50 Configuring a Scheduled Backup Task 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. Configuring a backup pool is a four-part process: 1. Configuring a device on page Configuring a label template on page Configuring a backup pool on page Labeling the device on page 52 Note: All of the procedures in this section must be performed on a NetWorker server release or later. Access the NetWorker server from the Administration window of the NetWorker Management Console. The EMC NetWorker Release 7.4 Service Pack 1 Multiplatform Version Administration Guide provides more detailed information about performing the steps included here. Configuring a device Configure a media device for snapshot metadata. Configure a tape, file, or advanced file type device. For best performance, configure a file or advanced file type device so that a snapshot can be recovered without the potential delay associated with retrieving a tape. To configure a device: 1. In the NetWorker Administration window 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. 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. 10. Click OK. 50

51 Configuring a Scheduled Backup 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 window of the NetWorker Management Console, click Media. 2. In the expanded left pane, select Label Templates. 3. From the File menu, select New. 4. In the Name attribute, type a name that identifies the series of labels as belonging to volumes for snapshot metadata. 5. In the Comment attribute, specify a comment for the label. 6. In the Fields attribute, specify a text name such as Snapshot_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 To configure a backup pool to store snapshot metadata: 1. In the Administration window of the NetWorker Management Console, click Media. 2. In the expanded left pane, select Media Pools. 3. From the File menu, select New. 4. For the Name attribute, type a name that matches the label template. 5. In the Comment attribute, specify a comment for the pool. 6. Select the Enabled attribute. 7. For the Pool type attribute, select the backup pool type. 8. For the Label template attribute, select the matching label template. 9. Do not select a group in the Groups attribute. Do not associate the pool with a particular group. This pool may be associated with several backup groups, so a single group should not be specified here. 10. Click the Selection Criteria tab. 11. For the Clients attribute, specify a NMM Client. A value must be entered for this attribute because no group was specified. 12. In the Devices attribute, select each device that can accept snapshot rollovers for this pool. 13. Click OK. Task 1: Configure a backup pool for snapshot operations 51

52 Configuring a Scheduled Backup Labeling the device Before a device can be used for backup, it must be labeled. To label a device: 1. In the Administration window of the NetWorker Management Console, click Devices. 2. In the right pane, right-click on the name of the device and select Label. 3. In the Pool attribute, select the backup pool that was created. 4. Select the Mount after Labeling attribute. 5. Click OK. 52

53 Configuring a Scheduled Backup Task 2: Configure snapshot policies A snapshot policy determines the following: When and how often snapshots are created Number of snapshots, and if any are retained as persistent snapshots Which snapshots, if any, are rolled over to conventional storage When snapshots expire and become eligible for deletion Note: Snapshots can also be manually rolled over or deleted. Chapter 14, Snapshot Management, describes these procedures in more detail. You can specify a preconfigured policy or create a custom snapshot policy. The following preconfigured snapshot policies exist: Serverless A single snapshot is taken per day. The data is then rolled over to conventional storage and the snapshot is deleted. Daily Eight snapshots are taken per day. The data in the first snapshot is rolled over to conventional storage. Each snapshot has 24-hour expiration policy.! CAUTION To protect against a disaster, ensure that all volumes and Windows system components are backed up. Also ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of first, last, or all. Do not specify none. Disaster recovery can only be performed from a conventional backup. Snapshot policies for SYSTEM COMPONENTS backup To back up SYSTEM COMPONENTS, the snapshot policy must specify all. NMM enforces this policy to ensure that a permanent backup of the snapshot exists. Attempting to restore system components from a persistent snapshot may invalidate the snapshot and leave the system in an unrecoverable state. Creating a snapshot policy To create a custom snapshot policy: 1. In the Administration window of the NetWorker Management Console, click Configuration. 2. In the expanded left pane, select Snapshot Policies. 3. From the File menu, select New. 4. In the Name attribute, type a name for the snapshot policy. 5. In the Comment attribute, type a comment for the snapshot policy. Task 2: Configure snapshot policies 53

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

55 Configuring a Scheduled Backup Snapshot policy examples Table 6 on page 55 depicts settings for a conventional backup. Four snapshots per day are taken. All snapshots are rolled over to a conventional storage medium. Each snapshot is deleted after it is rolled over. Table 6 Conventional backup settings Name Comment Conventional backup Rollover and then delete. Number of snapshots 4 Retain snapshots 0 Snapshot expiration policy Backup snapshots Day All Table 7 on page 55 depicts settings for an instant backup. Four snapshots per day are taken. Up to 28 snapshots are retained for a maximum period of one week. No snapshots are rolled over. Table 7 Instant snapshot policy Name Comment Instant backup Persistent snapshots with no rollovers. Number of snapshots 4 Retain snapshots 28 Snapshot expiration policy Backup snapshots Week None Table 8 on page 55 depicts settings for an instant backup with rollover to a conventional medium. Four snapshots per day are taken. Up to 28 snapshots are retained for a maximum period of one week. Every first and third snapshots are rolled over. Table 8 Instant snapshot with rollover policy Name Comment Instant and conventional backup Persistent snapshots with rollover to tape. Number of snapshots 4 Retain snapshots 28 Snapshot expiration policy Week Backup snapshots Every 1 Every 3 Task 2: Configure snapshot policies 55

56 Configuring a Scheduled Backup Task 3: Configure a backup schedule Backup schedules determine the days on which full or incremental backups are run. Full backups include all of the data specified in an NMM Client resource save set, while incremental backups include only the data that has changed since the last backup. Table 9 on page 56 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 Level 1 to 9 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\. These are supported only for backup of volume directories or paths such as E:\ or E:\business_files\. Note: The information in Table 9 on page 56 applies only to rollover backup operations. Snapshots are always taken at full level. 56

57 Configuring a Scheduled Backup Task 4: Configure a backup group Backup groups enable you to balance backup loads to reduce the impact on your storage and network resources. Use a backup group to assign the following attributes to a set of Client resources: Snapshot policy Backup start times Schedules Backup pools 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 window 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 snapshot is to be created. 7. For the Autostart attribute, select Enabled. 8. Click the Snapshot attribute so that a check mark appears beside it. 9. For the Snapshot Policy attribute, select a snapshot policy. Task 2: Configure snapshot policies on page 53 provides more information about snapshot policies. 10. For the Snapshot Pool attribute, select a pool that was created for the snapshot. Task 1: Configure a backup pool for snapshot operations on page 50 provides more information about pools. 11. Click the Advanced tab. 12. For the Interval attribute, specify how often a snapshot will be created. The Interval attribute works in conjunction with the backup group Start Time attribute and the snapshot policy Number of Snapshots attribute. For example, if you want to take four snapshots per day (Number of Snapshots attribute) and the first snapshot must occur at 4:00 a.m. (Start Time attribute), then the Interval attribute must be set to 5 hours or less: Number of Snapshots < (24:00 - Start Time) / Interval 13. Ensure that Restart Window attribute value is less than or equal to the Interval attribute value. 14. Set the Client Retries attribute to 0 (zero). 15. Click OK to create the backup group. Task 4: Configure a backup group 57

58 Configuring a Scheduled Backup! CAUTION Once you have started a snapshot of a save group, do not interrupt or halt the snapshot process. For example, in an Exchange Server backup, the nsrsnap_vss_save.exe process on the production server and the eseutil process on the proxy may continue to run after the snapshot is halted. Any attempt to stop a group in NetWorker Management Console will take a long time to complete. 58

59 Configuring a Scheduled Backup Task 5: Configure a Client resource A Client resource specifies what to include in a snapshot of an NMM Client. Client resources are associated with other backup resources such as groups and snapshot policies. You can create multiple Client resources for the same NMM Client host. In this way, you can apply different backup attributes to different types of information on the same host. For example, if the NMM Client host is an Exchange Server, you can create one Client resource to back up the Exchange databases and create another Client resource to back up Windows system component data. This way, you can back up Exchange databases many times a day, and back up Windows system component data once a day. The general process for configuring a Client resource is the same for all applications or systems. Some applications backed up by NMM have settings and requirements specific to the application. Configuring a Client resource for applications The Client resource configuration task is detailed in separate sections for the following applications: Performing Exchange Server backups on page 187 Performing DPM Server backups on page 209 Performing SharePoint 2003 backups on page 142 Performing SharePoint 2007 backups on page 121 Performing SharePoint 2007 granular backups on page 163 Performing SQL Server backups on page 104 Performing Hyper-V backups on page 234 Performing Windows Server Cluster backups on page 246 For all other applications and systems supported by NMM, To create a Client resource: on page 59 provides the Client resource configuration task steps. To create a Client resource: 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. 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. Task 5: Configure a Client resource 59

60 Configuring a Scheduled Backup 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines: To specify all volume data and all available Windows system components, type: All Application data such as Exchange data is not included in the save set All. To back up specific volumes, type the volume name. For example, to specify the volume E and all of its subfolders and files, type: E:\ Entries are not case-sensitive. To specify volume mount point data, place the name of the mount point on a separate line. For example, if you have a mount point named CAD_Drawings on volume E:\ and you want to back up all of the data on E:\ including the data under the mount point, type the following on separate lines: E:\ E:\CAD_Drawings The save set All will include mount point data only if no other path to the remote data is found during backup. To specify all available Windows system components such as the registration database and Windows event log, type the save set All or type following: SYSTEM COMPONENTS:\ Ensure that the backslash (\) character is entered with the save set name SYSTEM COMPONENTS:\. Otherwise, backup fails and no concise error message is provided. To specify application data, type: APPLICATIONS:\Name of writer Specifying save sets for application data on page 61, provides more information about specifying save set syntax for applications, and links to corresponding save set sections for specific applications.! CAUTION To protect against a disaster, ensure that all volumes and Windows system components are backed up. Also ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of first, last, or all. Do not specify none. Disaster recovery can only be performed from a conventional backup. 10. For the Group attribute, select the backup group to which this Client resource will be added. 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. 60

61 Configuring a Scheduled Backup 13. 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 Active Directory backup and recovery on page 262 provides additional information about Active Directory backups. 14. In the Application information attribute, type the following variable and value: NSR_SNAP_TYPE=vss Type any additional variables and their values on a separate line. Additional variables include specifications for a data mover (proxy client) and for Exchange setup attributes. Application information variable settings on page 65 provides more information about additional variables and their values. 15. If a proxy client is being set up for the NMM Client, type the hostname of the proxy client in the Remote Access attribute. If the NMM Client is part of a cluster, type the names of the physical nodes of the cluster in the Remote Access attribute. 16. Click the Globals (1 of 2) tab. 17. 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. 18. Click OK. Specifying save sets for application data Table 10 on page 62 lists the save set syntax to specify for supported types of application data. Specify application data save sets in the Save Set attribute of a Client resource. Displaying valid application data save sets on page 63 describes how to find the exact name of a particular Exchange storage group or SQL Server instance and database combination. save set syntax: Task 5: Configure a Client resource 61

62 Configuring a Scheduled Backup Table 10 Save set syntax Type of backup data DFS data (Windows Server 2003 only) Save set syntax APPLICATIONS:\DFS Replication service writer Also back up the SYSTEM COMPONENTS:\ save set on the namespace server (usually the domain controller) that is associated with the DFS configuration. Note: In Windows Server 2008, DFS Replication service writer is backed up as part of System Components:\ ADAM data Active Directory APPLICATIONS:\ADAM (instance_name) Writer For example, the ADAM instance named AddressBook would be typed as: APPLICATIONS:\ADAM (AddressBook) Writer Chapter 13, Active Directory and ADAM Backups, provides more information about Active Directory services. In Windows Server 2008, Active Directory Lightweight Directory Services, (AD LDS) includes the Active Directory Application Mode (ADAM) functionality provided in Windows Server Chapter 13, Active Directory and ADAM Backups, provides more information about Active Directory services. Microsoft Exchange Server Displaying valid Exchange data save sets on page 180 provides more information about Exchange save sets and syntax. Microsoft SQL Server Displaying valid SQL data save sets on page 100 provides more information about Microsoft SQL Server save sets and syntax. Microsoft System Center Data Protection Manager 2007 Microsoft Office SharePoint Server 2007 and Microsoft SharePoint Portal Server 2003 Microsoft Office SharePoint Server 2007 Granular backup Displaying valid DPM data save sets on page 206 provides more information about DPM save sets and syntax. Displaying valid SharePoint 2007 data save sets on page 118 provides more information about Microsoft Office SharePoint Server Displaying valid SQL data save sets for SharePoint 2003 backup on page 139 provides more information about Microsoft SharePoint Portal Server Displaying valid SharePoint 2007 data save sets on page 118 provides more information about Microsoft Office SharePoint Server 2007 granular backup. Hyper-V Displaying valid Hyper-V save sets on page 233 provides more information about Hyper-V save sets and syntax. 62

63 Configuring a Scheduled Backup Displaying valid application data save sets To display a list of the application data save sets that are available for backup: 1. Open a command prompt on the application server. 2. From the command prompt, type 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 where virtual_server_name is the name of the virtual host. nsrsnap_vss_save -? -c 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. The application data save sets that are available for backup are listed in a format similar to the following: "APPLICATIONS:\SqlServerWriter" "APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON" "APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\master" "APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\model" "APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\msdb" "APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NADATA" Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a Client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. URL encoding for SQL and Exchange save sets When specifying save set names in the Save Set attribute of the Client resource, there are cases where special characters, such as the backslash (\), must be specified by their URL-encoded values. URL-encoded values are used to represent special characters in the following cases: SQL Server named instances SQL Server database names Exchange storage groups Consider the following example of a SQL Server named instance. The name of a SQL Server named instance consists of two parts: the hostname and a unique name. These two parts 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 Task 5: Configure a Client resource 63

64 Configuring a Scheduled Backup 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 11 on page 64 lists the most commonly used special characters and their URLvalues. Table 11 Special characters and their URL-encoded values Special character URL-encoded value Special character URL-encoded value \ %5C? %3F / %2F ] %5D " %22 [ %5B % %25 } %7D # %23 { %7B & %26 ^ %5E < %3C %60 > %3E %7C 64

65 Configuring a Scheduled Backup Application information variable settings Table 12 on page 65 lists the variables that can be specified in the Application information attribute of the Client resource. Table 12 Application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=value Specifies the snapshot service provider name. Specifies the hostname of the NMM Client that moves snapshots from the NMM Client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This vss value is required. The local host The proxy client hostname If no value is entered, the local host is used as the data mover. If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the Client resource. For serverless backups, specify a proxy client. If setting up an Exchange Client resource, it is recommended that you use a proxy client. If a proxy client is specified, Exchange consistency checks are performed on the proxy client. Related messages are written to the Replication Manager log files (erm_clientxx.log) on the proxy client. If no proxy client is specified for an Exchange Client resource, consistency checks are performed on the Client resource host. Related messages are logged on the Client resource host in both the Replication Manager log files and the nmm.raw file. In addition to the attributes listed in Table 12 on page 65, there are also application-specific attributes: Exchange Application information variable settings on page 182 DPM application information variable settings on page 208 SharePoint 2007 Application information variable settings on page 120 SQL Server application information variable settings on page 102 Task 5: Configure a Client resource 65

66 Configuring a Scheduled Backup Task 6: Configure privileges The NMM Client must be granted NetWorker Administrator privileges in order to perform media database operations during snapshot deletion. If you set up a proxy client for the NMM Client, grant the proxy client NetWorker Administrator privileges. If you are setting up a NMM Client in a cluster, grant NetWorker administrator privileges to each cluster node and virtual server. To add configure privileges: 1. In the Administration window 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 a proxy client is set up for the NMM Client, add the following values: user=administrator,host=nmm_clientproxy_host user=system,host=nmm_clientproxy_host If the NMM Client is installed in a cluster, grant NetWorker Administrator privileges to each cluster node and virtual server. 5. Click OK. 66

67 Configuring a Scheduled Backup Task 7: Configure a proxy client A proxy client is a separate host that acts as a data mover for a NMM Client. By default, the NMM Client acts as its own data mover. However, a proxy client is required for serverless backups. Serverless backups free the NMM Client from much of the processing involved in a snapshot backup. In a serverless backup, a snapshot is created on the NMM Client and then immediately moved to the proxy client for further processing. A proxy client can also be set up on a NetWorker storage node. In this way network traffic that is generated when a snapshot is rolled over to a conventional backup medium is avoided. Table 13 on page 67 lists the requirements for setting up a proxy client. Table 13 Configuration requirements for a proxy client (1 of 2) Requirement Description General requirements Installation Configuration The proxy client must have the same version of the NMM Client software, and operating system version and patch level, as the host for which it is acting as the proxy client. The NetWorker Module for Microsoft Applications Release 2.0 Installation Guide provides more information about installation. Create a NMM Client resource for the proxy client host. Task 5: Configure a Client resource on page 59 provides more information about performing this task. Type the proxy client host name in the Application Information and the Remote Access attributes of the NMM Client resource that will use the services of the proxy client. Connectivity Serverless backups Rollback recovery CLARiiON Third-party hardware providers The proxy client must have connectivity between the NMM Client, the NetWorker server, and the storage subsystem on which snapshots reside. A proxy client is required for serverless backups. Additionally, serverless backups are supported only with VSS hardware providers and depend on the capabilities of the storage subsystem. For the EMC VSS Provider, serverless backups are supported for both CLARiiON and Symmetrix storage systems. The NMM Client to which the snapshot is to be rolled back must be supported with a proxy client. Roll back a snapshot on page 269 provides more information rollback requirements. For proxy clients using CLARiiON storage and the EMC VSS Provider, at least one CLARiiON LUN must be permanently assigned to the proxy host. Hardware providers may have additional configuration requirements for proxy clients. Refer to the vendor s product documentation for details on these requirements. Task 7: Configure a proxy client 67

68 Configuring a Scheduled Backup Table 13 Configuration requirements for a proxy client (2 of 2) Requirement Description Additional requirements for an Exchange Server Exchange Server performance Consistency checker utility Installation path to consistency checker utility Exchange mount paths Set up a proxy client for an Exchange Server. A proxy client performs the processing associated with the Exchange Server consistency checker utility, eseutil.exe, thus reducing the load on the Exchange Server. The Exchange Server consistency checker utility, eseutil.exe, must be installed on the proxy client. The version of eseutil.exe, must be of the same version (service pack level) as the Exchange Server. For example, if Exchange Server 2003 Service Pack 2 is installed on the Exchange Server, then the version of eseutil.exe that is installed on the proxy client must be from the Exchange Server 2003 SP2 Management utilities. Failure to do so will cause the consistency checker utility to report errors even when the databases are valid. Install the eseutil.exe utility from the Exchange Management Tools located on the Exchange Server CD. If the installation of the Exchange consistency checker utility, eseutil.exe, is not performed from the Exchange Server installation program, ensure that the path to the eseutil.exe program is in the $PATH environment variable. Use the NSR_ALT_PATH variable to specify a path to mount snapshots on the proxy client. Application information variable settings on page 65 provides more information about these settings. 68

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

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

71 3 Recovering Data This chapter includes the following topics: Performing a recovery Recovering file system snapshots that have not been rolled over Performing a disaster recovery of a NMM Client Booting Windows in Directory Service Restore mode Performing an authoritative recovery of NTDS or FRS data Performing a directed recovery Recovering the Windows system configuration to an earlier state Recovering Data 71

72 Recovering Data Performing a recovery Make sure all users who will be running or configuring NetWorker Module for Microsoft Applications (NMM) backups and recoveries have the appropriate level of privileges for all resources they must access. Table 15 on page 72 describes the privilege levels needed. Table 15 Access privileges needed for NMM Resource NetWorker Server NetWorker Module for Microsoft Applications client machine All applications protected by NMM, such as: Windows Server Microsoft Data Protection Manager Microsoft Office SharePoint Server Microsoft SQL Server Microsoft Exchange Server Network domain Storage node servers Privileges needed NetWorker Administrator or NetWorker Backup Operator Windows Administrator or Windows Backup Operator Windows Administrator Windows Domain Administrator Windows Administrator Review the following options and considerations before performing the procedures in this chapter: Chapter 12, Active Directory Recovery, provides more information about recovering Active Directory (AD) data. Recovering file system snapshots that have not been rolled over on page 86 provides more information about recovering data from a persistent snapshot that has not been rolled over to a conventional backup medium.! IMPORTANT Attempting to restore system components from a persistent snapshot may invalidate the snapshot and leave the system in an unrecoverable state. NMM does not prevent an attempt to restore SYSTEM COMPONENTS from a point-in-time backup. Chapter 14, Snapshot Management, describes how to roll over a snapshot to a conventional backup. To recover backup data that was password-protected and encrypted with another VSS client program, and not NetWorker VSS Client for Microsoft Windows 1.0 or NetWorker Module for Microsoft Applications, use the recover.exe command from the CLI (command line interface). The EMC NetWorker Command Reference Guide, release or later, provides more information about the recover.exe command. Data that was backed up from a mount point is available for browsing at the root of the navigation tree. For example, if the drive H:\ has a mount point named H:\CAD_Drawings, then a separate entry for the mount point H:\CAD_Drawings will be available at the root of the navigation tree instead of as a subfolder under H:\. 72

73 Recovering Data To recover data to a mount point that has been deleted, manually re-create the mount point before recovering the data. Otherwise, the data will be recovered to a local directory whose name corresponds to the deleted mount point. If the disk that is referenced by the mount point has been replaced, manually re-create the mount point. If a file was not backed up due to a skip directive, you may still be able to select the file for a recovery operation. In this case, although you can select the file, it is not recoverable.! IMPORTANT If you are recovering File Replication Services (FRS) or Windows NT Directory Services (NTDS) data, boot the NetWorker client in Directory Service Recovery mode before completing the recovery options in this section. Booting Windows in Directory Service Restore mode on page 89 provides more information about these recovery options. System Writer recovery in Windows Server 2008 When recovering an older backup of the System Writer in Windows Server 2008, any application or NMM upgrades, service packs, or hot fixes that were installed since the backup may need to be reinstalled after the recovery. To recover system data: 1. Open the NMM client software and select the NetWorker server on which the NMM client software was configured for backup. 2. If the NMM client is part of a cluster, select the virtual client to which you are recovering data. The virtual client can be selected from the Client list attribute in the application toolbar. 3. From the left pane, select Recover > System Recover Session. 4. In the navigation tree, select the items to be recovered. By default, items displayed in the navigation tree are from the most recent backup. For the System Recover Session view, both snapshot and rollovers can be displayed in the same view: If the most recent backup for an item is a snapshot, the snapshot is displayed. If the most recent backup for an item is a rollover, the rollover is displayed. To recover file system items from a previous backup: From the application toolbar, click the Browse calendar icon and select an earlier browse time. To view versions of a backup item prior to the browse time, right-click an item in the navigation tree and select Versions from the pop-up menu. 5. To determine whether any volumes need to be mounted for a selected item, right-click the item and select Required Volumes from the pop-up menu. 6. From the Options menu, select System Recover Session Options. 7. Enter application-specific recover options or settings, as described in: NetWorker recovery options on page 74 Exchange recovery options on page 191 Performing DPM Server recovery on page 212 Performing a recovery 73

74 Recovering Data Performing SharePoint 2007 recovery on page 129 ADAM recovery options on page 78 DFS recovery options on page 79 FRS recovery options on page 82 NTDS recovery options on page 83 Performing SQL Server recovery on page From the System Recover Session toolbar, click Start Restore. 9. From the left pane, select Monitor to view messages related to the progress of the recovery operation. Note: If you recovered items from a snapshot (instant recovery), the snapshot volume will be temporarily mounted during the recovery operation. The mounted volume is displayed in the Windows Explorer program. After the recovery is complete, you may have to refresh the Windows Explorer to update its view. NetWorker recovery options To specify recovery options for file system data: 1. From the Options menu, select System Recover Session Options. 2. Click the NetWorker tab. 3. In the Relocate recovered data to: field, type a location other than the location from which the data was originally backed up. The location must be a local path. URL syntax such as \\servername\share is not supported. 4. Use the Restore Type field to determine the default recovery method: Select Conventional Restore to recover from a conventional backup medium. If a conventional backup is not available for the selected browse time, an instant recovery is performed. Select Instant Restore to recover from a snapshot. If a snapshot is not available for the selected browse time, a conventional backup is performed. For instant restore, snapshot validation will occur prior to the restore. If the snapshot is invalid, the restore will fail. The invalid snapshot will be deleted automatically the next time the snapshot group runs. You can also delete a snapshot manually. Delete a snapshot on page 273 provides more information about manually deleting snapshots. 5. Select Use Microsoft best practices for selecting the system state to enforce Microsoft recommendations that determine which system state items must be selected as a group for recovery. Clear this attribute to select system state items individually.! CAUTION Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. 74

75 Recovering Data Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 6. Click OK. Performing a recovery on page 72 provides more information about recovering data. Performing a recovery 75

76 Recovering Data Cluster recovery options Use this tab to specify whether to perform an authoritative or nonauthoritative restore of the Cluster Writer. If the Cluster Writer was backed up in NetWorker 7.4 SP2 prior to upgrading to NMM 2.0, you must use a command line to perform an authoritative restore. Authoritative recovery from a NetWorker 7.4 SP2 save set after NMM upgrade on page 77 provides more information about the command line and when to use it. Cluster Writer nonauthoritative restore (default) Use this mode if the cluster is completely lost, in which case the cluster service does not run on either node, and the cluster database is missing or corrupted. Nonauthoritative restores will restore the cluster but will not restore a particular version of the database. After the nonauthoritative restore is complete, you must follow up with an authoritative restore to recover a specific version of the database. NMM will perform an nonauthoritative restore by default, but you must make sure that the SYSTEM COMPONENTS:\BootableSystemState saveset is also selected. To specify a nonauthoritative restore for the Windows Server 2008 Cluster Writer: 1. From the Options menu, select System Recover Session Options. 2. Click the NetWorker tab, and then clear the Use Microsoft best practices for selecting system state check box. 3. Click OK to close the System Recover Session Options dialog box. 4. In the navigation tree, expand the SYSTEM COMPONENTS folder and select Cluster Database. 5. Select the SYSTEM COMPONENTS:\BootableSystemState saveset. 6. From the System Recover Session toolbar, click Start Restore. 7. Reboot the system when prompted. 8. Repeat from step 1 on page 76 on the other nodes, if needed. Cluster Writer authoritative restore Use this mode when the cluster configuration is lost, but the cluster is running okay otherwise. For example, when a cluster resource was accidentally deleted or you want to revert to a previous cluster configuration. The cluster must be healthy in all nodes. Note: Authoritative restores of the Cluster Writer are only supported for Windows Server To specify an authoritative restore for the Windows Server 2008 Cluster Writer: 1. Make sure the cluster service is running on the local system. 2. Make sure that the cluster service is running on all remote nodes. Microsoft Windows Server 2008 product documentation provides more information on running the cluster service. 3. From the Options menu, select System Recover Session Options. 4. Click the NetWorker tab, and clear the Use Microsoft best practices for selecting system state check box. 5. Click the Cluster tab. 76

77 Recovering Data 6. Select the Authoritative Restore options. 7. Click OK to close the System Recover Session Options dialog box. 8. In the navigation tree, expand the SYSTEM COMPONENTS folder and select Cluster Database. 9. From the System Recover Session toolbar, click Start Restore. Note: Perform an authoritative restore of the Windows 2008 cluster writer by selecting only the Windows 2008 cluster writer in that recover session. In particular, do not perform an authoritative restore of the Windows 2008 cluster writer at the same time as the restore of any other NMM application. Authoritative restores of the Windows 2008 cluster writer will restart the cluster service on all nodes in the cluster. Authoritative recovery from a NetWorker 7.4 SP2 save set after NMM upgrade If the Windows Server 2008 cluster database was backed up in NetWorker 7.4 SP2 prior to upgrading to NMM 2.0, you must use a command line to perform an authoritative restore. You cannot perform this authoritative recovery from the Cluster tab of System Recover Session Options. The following set of steps illustrates this installation, backup, and recovery sequence: 1. Install NetWorker 7.4 SP2 on a Windows Server 2008 cluster. 2. Back up VSS SYSTEM SERVICES. 3. Uninstall NetWorker 7.4 SP2. 4. Install NMM 2.0. If you attempt to use the NMM recovery user interface to recover a cluster database that was backed up in NetWorker 7.4 SP2 prior to upgrading to NMM 2.0, NMM will change it to a nonauthoritative restore. You can only perform an authoritative restore of a Windows Server 2008 Cluster Writer backup created with NetWorker 7.4 SP2 by using the command line. To perform an authoritative restore of the Windows Server 2008 Cluster Writer: 1. Make sure that the cluster service is running in the local system. 2. Make sure that the cluster service is running on all remote nodes. 3. Type the following string on the command line: recover -s NWServer -U -N "VSS SYSTEM SERVICES:\Cluster Database" Note: Perform an authoritative restore of the Windows 2008 cluster writer by selecting only the Windows 2008 cluster writer in that recover session. In particular, do not perform an authoritative restore of the Windows 2008 cluster writer at the same time as the restore of any other NMM application. Authoritative restores of the Windows 2008 cluster writer will restart the cluster service on all nodes in the cluster. Nonauthoritative recovery of a Windows Server 2008 cluster database a NetWorker 7.4 SP2 save set A nonauthoritative recovery of a Windows 2008 cluster database backup that uses a save set created with NetWorker 7.4 SP2, can be performed through the NMM recovery user interface or through the recover command line. Performing a recovery 77

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

79 Recovering Data To specify recovery options for ADAM data: 1. From the Options menu, select System Recover Session Options and then click the ADAM tab. 2. Select one of the following options: Non Authoritative Restore Authoritative Restore 3. Click OK to close the System Recover Session Options dialog box. 4. In the navigation tree, expand the Applications folder and select ADAM <instance_name>writer. 5. From the System Recover Session toolbar, click Start Restore. 6. If an authoritative restore has been performed, restore for all selections has completed, and NMM reports success, complete the following steps: a. Exit the NMM Client, and open a command window. b. Run the dsdbutil.exe utility, and select Authoritative Restore option. This marks the objects that are to be restored in authoritative mode. c. When processing is complete, exit the dsdbutil.exe utility and start the ADAM instance service manually. If a nonauthoritative restore was performed, the ADAM instance has already been started. DFS recovery options You can specify whether to perform an authoritative or nonauthoritative recovery of Distributed File System (DFS) data on this host. There are some differences between DFS recovery options on Windows Server 2003 and Windows Server 2008: Authoritative restore is available on Windows Server 2003 and on some Windows Server 2008 systems. In Windows Server 2003, the writer is recovered from Applications:\DFS Replication service writer. In Windows Server 2008, the writer is recovered from SYSTEM COMPONENTS:\Bootable System State. In Windows Server 2008, DFS can have DFS shares or it can also be part of Active Directory recovery. Performing a recovery 79

80 Recovering Data In Windows Server 2008, DFS is part of Active Directory recovery if it was promoted to a Domain Controller with the 2008 Functional level setting selected. To restore DFS on a Windows 2008 system as part of Active Directory, the system must be booted into Directory Services Restore Mode. The steps for performing a DFS recovery from Windows Server 2003 and Windows Server 2008 are described in separate procedures. Nonauthoritative restore (default) Authoritative restore This type of recovery restores the most recent DFS data from backups and then updates the recovered host with the most recent DFS data from another DFS server in the domain. A nonauthoritative recovery relies on at least one other DFS server in the domain to have accurate up-to-date DFS data. Nonauthoritative recoveries are typically performed when the host is being recovered due to catastrophic loss of data such as a disk failure. An authoritative recovery restores the most recent DFS data from backups, and then updates other DFS servers in the domain with the recovered data. Perform an authoritative recovery only when corrupted or deleted DFS data has been propagated to other DFS servers. Note: To recover DFS data, the APPLICATIONS:\DFS Replication service writer save set must have been backed up. The DFS Replication service writer is available with Windows Server 2003 R2 or later. Additionally, the SYSTEM COMPONENTS:\ save set on the namespace server (usually the domain controller) that is associated with the DFS configuration must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about specifying save sets when configuring a backup. To specify which type of DFS recovery to perform in Windows Server 2003: 1. From the Options menu, select System Recover Session Options and then click the DFS tab. 2. Select one of the following options: Non Authoritative Restore to perform a nonauthoritative recovery. Authoritative Restore to perform an authoritative recovery. 3. Click OK to close the System Recover Session Options dialog box. 4. From the navigation tree, expand the Applications folder and select DFS Replication service writer. 5. From the System Recover Session toolbar, click Start Restore. 6. After the DFS Replication service writer has been recovered, you must recover the Bootable System State components on the namespace server (usually the domain controller) that is associated with the DFS configuration: a. Boot the namespace server in directory service restore mode as described in Booting Windows in Directory Service Restore mode on page 89. b. Open the NMM client software on the namespace server (usually the domain controller) that is associated with the DFS configuration. c. From the Options menu, select System Recover Configuration Options and then click the NetWorker tab. d. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection. 80

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

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

83 Recovering Data! CAUTION Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 4. Click OK to close the System Recover Session Options dialog box. 5. From the navigation tree, expand the SYSTEM COMPONENTS folder and click FRS. 6. From the System Recover Session toolbar, click Start Restore. If you are performing an authoritative recovery, complete the remaining steps in Performing an authoritative recovery of NTDS or FRS data on page 90. Performing a recovery on page 72 provides more information about recovering system data. NTDS recovery options You can specify whether to perform an authoritative or nonauthoritative recovery of Windows NT Directory Services (NTDS) data on this host.! CAUTION Boot the NetWorker client in Directory Service Recovery mode before completing the recovery options in this section. Booting Windows in Directory Service Restore mode on page 89 provides more information about these recovery options. NTDS nonauthoritative restore (default) A nonauthoritative recovery restores the most recent NTDS data from backups and then updates the recovered host with the most recent NTDS data from another NTDS server in the domain. A nonauthoritative recovery relies on at least one other NTDS server to have accurate up-to-date NTDS data. Nonauthoritative recoveries are typically performed when the host is being recovered due to catastrophic loss of data such as a disk failure. NTDS authoritative restore An authoritative recovery restores the most recent NTDS data from backups, and then updates other NTDS servers in the domain with the recovered data. Perform an authoritative recovery only when corrupted or deleted NTDS data has been propagated to other NTDS servers. Note: To recover NTDS data, the SYSTEM COMPONENTS save set must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about specifying save sets when configuring a backup. Performing a recovery 83

84 Recovering Data To specify whether to perform an authoritative or nonauthoritative recovery: 1. From the Options menu, select System Recover Session Options and then click the NTDS tab. 2. Select one of the following options: Non Authoritative restore to perform a nonauthoritative recovery. Authoritative Restore to perform an authoritative recovery. 3. Click the NetWorker tab and then clear the attribute titled Use Microsoft best practices for selecting the system state. Click Yes when asked to confirm your selection.! CAUTION Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 4. Click OK to close the System Recover Session Options dialog box. 5. From the navigation tree, expand the SYSTEM COMPONENTS folder and click NTDS. 6. From the System Recover Session toolbar, click Start Restore. If you are performing an authoritative recovery, complete the remaining steps in Performing an authoritative recovery of NTDS or FRS data on page 90. Performing a recovery on page 72 provides more information about recovering system data. 84

85 Recovering Data Security recovery options Backup and archive data on Windows hosts can be encrypted with an Advanced Encryption Standard (AES) Application Specific Module (ASM) pass phrase. If no pass phrase was specified when the backup data was encrypted, then the data is encrypted with a default pass phrase. During data recovery, you must specify the pass phrase used at the time of backup if it is not the default or current pass phrase. To specify pass phrases: 1. From the Options menu, select System Recover Session Options and then click the Security tab. 2. Type the pass phrases, and then click OK. The EMC NetWorker Multiplatform Version Administration Guide, release or later, provides more information about AES encryption, and setting the pass phrase.! CAUTION Do not use AES encryption when backing up files that are encrypted using Windows Encrypting File System (EFS). When AES encryption is applied to a file that is also encrypted using the Microsoft EFS, the backup will be reported as successful. However, recovery of the file will fail. Performing a recovery 85

86 Recovering Data Recovering file system snapshots that have not been rolled over The procedure to recover items in a file system snapshot differs depending on whether the snapshot has been rolled over to a conventional storage medium. This section describes how to recover items from a file system snapshot that has not been rolled over. Performing a recovery on page 72 provides more information about recovering file system snapshots that have been rolled over. Note: If a snapshot volume has been mounted by using a client utility such as the EMC NaviCLI interface or the Windows Disk Management utility, remove the mount point before performing the next backup or recovery operation. If the mount point is not removed, it will be removed at the end of the next NetWorker backup or recovery operation. To recover items in a file system backup that has not been rolled over: 1. Connect to the NetWorker server on which the NetWorker client was configured for backup. Opening the software and connecting to a NetWorker server on page 41 provides more information about connecting to the NetWorker server. 2. From the left pane, select Recover > System Recover Session. 3. In the navigation tree, right-click the snapshot and select Mount Snapshot. If the Mount Snapshot option is unavailable, then the snapshot has been rolled over. In this case, follow the steps described in Performing a recovery on page 72. If another snapshot is currently mounted, a message indicates that the currently mounted volume will be unmounted. Click OK to unmount the volume and to proceed with mounting the selected snapshot volume. 4. When the taskbar animation stops and a green mark appears, click the mounted snapshot. The mounted snapshot item will expand in the navigation tree. 5. Under the expanded snapshot, select the items to be recovered. Selecting an item for recovery on page 42 provides more information about selecting items for recovery. 6. Select any additional file system options if applicable. NetWorker recovery options on page 74 provides more information about these options. 7. From the System Recover Session toolbar, click Start Restore. Once the recovery starts, the snapshot is automatically unmounted. 8. From the left pane, select Monitor to view the progress of the recovery. 86

87 Recovering Data Performing a disaster recovery of a NMM Client NMM provides recovery for the NMM Client itself, as well as the applications NMM protects, such as Microsoft Exchange Server, Microsoft SQL Server, Microsoft Office SharePoint Services, and Microsoft Data Protection Manager. Disaster recovery of the entire NMM Client machine requires completion of the following tasks: 1. Recovery of the NMM Client 2. Full recovery of the applications on that machine! CAUTION Ensure that your snapshot policies include at least one rollover to conventional backup. Disaster recovery can only be performed from a conventional backup. NMM requires conventional backup for SYSTEM COMPONENTS. Attempting to restore SYSTEM COMPONENTS from a point-in-time backup can leave the system in an unrecoverable state. NMM does not prevent an attempt to restore SYSTEM COMPONENTS from a point-in-time backup. Chapter 14, Snapshot Management, describes how to roll over a snapshot to a conventional backup. Disaster recovery when the NMM Client is not on a domain controller To perform a disaster recovery if the NMM Client is not on a domain controller: 1. Install the original operating system to the same specifications and configuration as originally on the client. Note: Be sure to apply all service packs and updates that had been applied to the operating system before the disaster, to bring it up to the exact same level as existed at the time it was lost. 2. Install the NMM Client software exactly as it was configured before the disaster. 3. Open the NMM Client software. 4. From the left pane, select Recover > System Recover Session. 5. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) folder, typically C:\Program Files\EMC\rmagentps. 6. Select the SYSTEM COMPONENTS folder. If recovering a backup created with NetWorker VSS Client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. 7. From the System Recover Session toolbar, click Start Restore. 8. When prompted, restart the client. This restores the operating system to the state it was in when last backed up. Now applications, such as Microsoft Exchange Server, SQL Server, Office SharePoint Server, or Data Protection Manager can be restored from previous backups. 9. To restore APPLICATIONS, open NMM and select the APPLICATIONS for restore. Performing a disaster recovery of a NMM Client 87

88 Recovering Data Disaster recovery when the NMM Client is on a domain controller To perform a disaster recovery if the NMM Client resides on a domain controller: 1. Install the original operating system to the same specifications and configuration as originally on the client. Note: Be sure to apply all service packs and updates that had been applied to the operating system before the disaster, to bring it up to the exact same level as existed at the time it was lost. 2. Install the NMM Client software exactly as it was configured before the disaster. Note: This is for an Active Directory client NMM installation, and is not for the Active Directory plugin within a client. 3. Boot the NMM client in directory service restore mode. Booting Windows in Directory Service Restore mode on page 89 provides more information about these recovery options. 4. Open the NMM Client software. 5. From the left pane, select Recover > System Recover Session. 6. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) folder, typically C:\Program Files\EMC\rmagentps. 7. Select the SYSTEM COMPONENTS folder. If recovering a backup created with NetWorker VSS Client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. 8. From the System Recover Session toolbar, click Start Restore. 9. When prompted, restart the client. This restores the operating system to the state it was in when last backed up. Now applications, such as Microsoft Exchange Server, SQL Server, Office SharePoint Server, or Data Protection Manager, can be restored from previous backups. 10. To restore APPLICATIONS, open NMM and select the APPLICATIONS for restore. 88

89 Recovering Data Booting Windows in Directory Service Restore mode Before you can complete the following recovery operations, boot the NMM client in Directory Service Restore mode: DFS recovery FRS recovery NTDS recovery Active Directory (AD) disaster recovery To boot the NMM client in Directory Service Restore mode: 1. On the NetWorker client domain controller, close all programs and restart Windows. When the computer restarts, a list of startup choices appears. The startup choices and the duration of the startup display are based on the settings in the operating systems section and the boot loader section of the boot.ini file. 2. Choose the Windows boot option for the domain controller. 3. Press F8 to display a list of special boot options. 4. Select Directory Service Restore Mode (Windows Domain Controllers only) from the list of special boot options. When you boot in this mode, AD is taken offline. 5. Log in as administrator. Use the password that was specified when the domain controller was created. Windows starts in safe mode. 6. Open the NMM client application. 7. From the left pane, select Recover > System Recover Session. Continue with the recovery options. The following sections provide more specific information: DFS recovery options on page 79 FRS recovery options on page 82 NTDS recovery options on page 83 Schema objects on page 260 Performing a recovery on page 72 includes information about SYSTEM STATE or VSS SYSTEM BOOT save sets, and save set recovery. Performing a granular recovery of AD objects and attributes on page 258 includes information about save sets on a domain controller. Booting Windows in Directory Service Restore mode 89

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

91 Recovering Data 11. Wait for the SYSVOL share to be published. This can take several minutes while the recovered domain controller synchronizes with its replication partners. 12. After the SYSVOL share has been published, perform one of the following: For an authoritative recovery of the entire database, copy the entire SYSVOL\domain directory tree from the new location to the existing SYSVOL\domain directory as described in step 8 on page 90. When the copy operation prompts for confirmation, select Yes to All. For an authoritative recovery of only a part of AD that includes Policy objects, copy the policy folders from the new location (see step 8 on page 90) to the existing policy folders. Policy objects can be identified by their global universal ID (GUID). Policy folders are located in SYSVOL\domain\Policies. Performing an authoritative recovery of NTDS or FRS data 91

92 Recovering Data Performing a directed recovery NMM supports directed recovery, where data that originated on one NetWorker client host is recovered to another NetWorker client host. To perform a directed recovery with NMM: 1. In NetWorker, create a volume backup of a NMM client. The backup must be a conventional backup, or a rolled over snapshot type backup. Figure 10 on page 92 shows a conventional backup, with the Snapshot check box cleared. Figure 10 Using a conventional backup for directed recovery 2. Connect to the NetWorker Server that hosts the NMM client. 3. Add the NMM client that created the volume backup as a locally viewable client. Figure 11 on page 93 shows the default of only one NMM client available, the local client. 92

93 Recovering Data Figure 11 Local client on the taskbar next to Client 4. On the Options menu, click Configure Options. Figure 12 on page 93 shows the Configuration Options dialog box. Figure 12 Configuration Options dialog box 5. Click the Refresh button, which is to the right of the Client name. Figure 13 on page 93 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 13 Select Viewable Clients dialog box 6. Click the client to add in the Available clients on list box, and then click Add. Add or remove clients as needed. Performing a directed recovery 93

94 Recovering Data 7. Click OK. Figure 14 on page 94 shows the NMM window with the Client box. Figure 14 NMM Client dropdown list 8. Click the Client list, and select the client that created the volume backup as the current local client. 9. If the Snapshot Management or Monitor is the active navigation bar item, and you are prompted with the Navigate Away dialog box, click Yes. 10. On the System Recover Sessions bar, select Recover Options. The NetWorker System Recover Session Options dialog box appears. 11. On the NetWorker tab, specify the destination for the recovery in the Relocate Recovered Data box, and then click OK. 12. Recover remote client's backup to local destination. 94

95 Recovering Data Recovering the Windows system configuration to an earlier state Hosts that were upgraded from a regular NetWorker client to a NMM client can have their Windows operating system configuration recovered to a state prior to upgrading to the NMM client.! CAUTION If the Windows operating system was upgraded on the host, you cannot recover the Windows system configuration to the state it was in before the operating system software was upgraded. To recover the Windows system state to a point-in-time that precedes the installation of the NMM client: 1. If the NMM client is a Windows domain controller, boot the NMM client in Directory Services Restore mode. Booting Windows in Directory Service Restore mode on page 89 provides more information about booting in this mode. If the NMM client is not a Windows domain controller, start with step 2 on page Recover the contents of the volume on which the Windows operating system was installed. 3. Recover the Windows configuration save sets: If VSS was licensed and enabled, recover: VSS SYSTEM BOOT VSS SYSTEM FILESET VSS SYSTEM SERVICES If VSS was not licensed or enabled, recover: SYSTEM STATE SYSTEM FILES SYSTEM DB 4. Update the recovered registry with NMM client entries. Because the registry was recovered to a client state prior to the NMM client installation, you must update the registry with entries for the NMM client. To update the registry, perform the following uninstall and install steps: a. Uninstall the NMM client software. b. Install the NMM client software. c. Uninstall the NetWorker PowerSnap software. PowerSnap is installed with the NMM client software. d. Uninstall the NMM client software. e. Reinstall the NMM client software. Reinstall, as necessary, any other applications that were installed after the point-in-time to which the Windows operating system configuration was recovered. Recovering the Windows system configuration to an earlier state 95

96 Recovering Data The NetWorker Module for Microsoft Applications Release 2.1 Installation Guide provides more information about the uninstall and install steps. 96

97 4 Microsoft SQL Server Backup and Recovery This chapter includes the following topics: Microsoft SQL Server backup and recovery Performing SQL Server backups Performing SQL Server recovery Microsoft SQL Server Backup and Recovery 97

98 Microsoft SQL Server Backup and Recovery Microsoft SQL Server backup and recovery This chapter supplements the overall NetWorker Module for Microsoft Applications (NMM) backup procedures in Chapter 2, Configuring a Scheduled Backup, and recovery procedures in Chapter 3, Recovering Data, with the specific details needed to back up and recover Microsoft SQL Server. Microsoft SQL Server supports Volume Shadow Copy Service (VSS) through Microsoft-supplied application writers. 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 SQL Server while the SQL database is online or in use. SQL Server versions supported by NMM NMM client supports the following versions of Microsoft SQL Server: Microsoft SQL Server 2005 (x86, x64) Standard Enterprise Microsoft SQL Server 2005 Express edition Express Microsoft SQL Server 2000 (x86) Standard Enterprise Desktop (MSDE) Note: NMM client does not support Microsoft SQL Server 2000 or 2005 that runs on IA64. 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. Note: To perform snapshot operations on an installation of Microsoft SQL Server 2000 service pack 4 32-bit that runs on Windows Server 2003 x64 based systems, you must download and install the Update for Windows Server 2003 (KB931312) package from the Microsoft Download Center. For more information, search for KB on the Microsoft Support website. Types of supported backup and recovery Using point-in-time snapshot technology, NMM supports several types of backup and recovery for SQL 2000 embedded databases and Microsoft SQL Server. 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: Only full level backups All SQL Server 2005 named instances and databases, including express and stand-alone databases Only the SQL 2005 host instance and database name combination 98

99 Microsoft SQL Server Backup and Recovery All SQL 2000 embedded databases All SQL 2000 named instances and stand-alone databases Only the SQL 2000 host instance and database name combination NMM supports the following types of recovery: Microsoft SQL Server 2005 stand-alone or express databases SQL 2000 embedded or stand-alone databases Components used by NMM for SQL data backup and recovery NMM uses the following writers and commands to back up SQL data: Application writers NMM uses the application writers provided by Microsoft SQL Server: MSDEWriter- SQL2000 The VSS writer for SQL 2000/MSDE SqlServerWriter The VSS writer for SQL Server 2005 Specifying save sets for SQL data on page 100 describes how the writer name is used in the save set syntax. Nsrsnap_vss_save The NMM command to initiate the VSS-based backup. Nsrsnap_vss_recover The NMM command to initiate the VSS-based recovery. Microsoft SQL Server backup and recovery 99

100 Microsoft SQL Server Backup and Recovery Specifying save sets for SQL data Table 16 on page 100 lists the SQL save set syntax to specify for supported types of SQL data. Specify SQL data save sets in the Save Set attribute of a Client resource. save set syntax: Table 16 SQL save set syntax Type of data to back up All SQL Server 2005 named instances and databases, including express and stand-alone databases Only the SQL 2005 host instance and database name combination All SQL 2000 embedded databases All SQL 2000 named instances and stand-alone databases Only the SQL 2000 host instance and database name combination Save set syntax If the SQL Server VSS Writer service is enabled (it is disabled by default), type the following: APPLICATIONS:\SqlServerWriter If the SQL Server VSS Writer service is disabled, SQL 2005 named instances and databases including express and stand-alone databases, can be backed up with the following syntax: APPLICATIONS:\MSDEWriter-SQL2000 APPLICATIONS:\SqlServerWriter\host%5Ci nstance\master For example, to back up the database named trans07 on the SQL Server named instance MT11\BU, type the following: APPLICATIONS:\SqlServerWriter\MT11%5CB U\ trans07 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 101 provides more information about URL encoding. SYSTEM COMPONENTS:\ APPLICATIONS:\MSDEWriter-SQL2000 APPLICATIONS:\MSDEWriter-SQL2000\host% 5C instance\master For example, to back up the database named accounts07 on the SQL Server named instance MT11\AP, type the following: APPLICATIONS:\MSDEWriter-SQL2000\ MT11%5CAP\accounts07 Some special characters in a SQL Server named instance or database name must be replaced with URL-encoded values. URL encoding for SQL save sets on page 101 provides more information about URL encoding. 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. 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 100

101 Microsoft SQL Server Backup and Recovery 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. 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" Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a Client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. URL encoding for SQL 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. These two parts 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 Microsoft SQL Server backup and recovery 101

102 Microsoft SQL Server Backup and Recovery Table 17 on page 102 lists the most commonly used special characters and their URL values. Table 17 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 SQL Server application information variable settings Table 18 on page 102 lists the variables that can be specified in the Application Information attribute of the Client resource. Table 18 SQL variable settings for Application Information attribute Attribute name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=valueap plication information attribute Specifies the snapshot service provider name. Specifies the hostname of the NMM client that moves snapshots from the NMM client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This value is required. The local host The proxy client hostname If no value is entered, the local host is used as the data mover. If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the Client resource. For serverless backups, specify a proxy client. If setting up an SQL Client resource, it is recommended that you use a proxy client. If a proxy client is specified, SQL 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 SQL Client resource, consistency checks are performed on the Client resource host. Related messages are logged on the Client resource host in both the Replication Manager log files and the nmm.raw file. 102

103 Microsoft SQL Server Backup and Recovery Serverless backup A proxy client is used in conjunction with instant snapshot backups to provide serverless backups. Serverless backups free the application server from much of the processing involved in a nonpersistent or instant snapshot backup. In a serverless backup, a snapshot is created on the application server and then immediately moved to the proxy client for further processing. A serverless backup can be rolled over to a conventional backup, which can remain on the mounted storage disk volume as a persistent snapshot. Note: Serverless backup is available only with VSS hardware providers and is subject to the capabilities of the vendor s hardware. The EMC VSS Provider for CLARiiON and Symmetrix provides the capability to perform serverless backup operations for these storage platforms. Microsoft SQL Server backup and recovery 103

104 Microsoft SQL Server Backup and Recovery Performing SQL Server backups NMM supports several types and levels of backup: Point-in-time snapshots, which include exact copies of files and open files Full backup of SQL databases and logs Full backup of an SQL Server The first four tasks for scheduling a backup are the same for all VSS writers that are supported by NMM. Chapter 2, Configuring a Scheduled Backup, describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Task 5: Configure a SQL Server Client resource The next task is specific to configuring a SQL Server Client Resource: 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. 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: 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 104

105 Microsoft SQL Server Backup and Recovery 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-SQL2000 The SQL Server save set syntax is described in Specifying save sets for SQL data on page 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 URL encoding for SQL save sets on page Specify SQL application variable settings in the Application information attribute of the Client resource. These settings are described in Table 18 on page Click the Globals (1 of 2) tab. 12. 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 backups 105

106 Microsoft SQL Server Backup and Recovery Performing SQL Server recovery The following requirements must be met to recover SQL databases: To recover SQL 2000 embedded databases, the SYSTEM COMPONENTS:\ save set must have been backed up. To recover SQL2000 stand-alone databases, the APPLICATIONS:\ MSDEWriter-SQL2000 save set must have been backed up. To recover SQL 2005 Express databases, the following save sets must have been backed up: SYSTEM COMPONENTS:\ save set if the SQL 2005 VSS Writer was started. APPLICATIONS:\ MSDEWriter-SQL2000 save set if the SQL 2005 VSS Writer was not started. Recovering SQL Server 2000 embedded databases To recover SQL Server 2000 embedded databases: 1. Stop the SQL Server services for the SQL Server 2000 embedded database instances. 2. From the Options menu, select System Recover Configuration Options and then click the NetWorker tab. 3. Clear the checkbox titled, Use Microsoft best practices for selecting the system state and click Yes when asked to confirm your selection.! CAUTION The "Microsoft Best Practices" box should not be cleared except where specifically noted in this document. There are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. 4. Click OK to close the dialog box. 5. From the left pane, select Recover > System Recover Session. 6. From the navigation tree, expand the SYSTEM COMPONENTS folder and the MSDEWriter folder. 7. Select the databases to recover. 8. From the System Recover Session toolbar, click Start Restore. 9. After the recovery is complete, start the SQL Server services for the SQL Server 2000 embedded database instances. 106

107 Microsoft SQL Server Backup and Recovery Recovering SQL Server 2000 stand-alone databases To recover SQL Server 2000 stand-alone databases: 1. Stop the SQL Server services for the SQL Server 2000 stand-alone database instances. 2. From the navigation tree, 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 for the SQL Server 2000 stand-alone database instances. Recovering SQL Server 2005 databases If the SQL Server VSS Writer service was enabled during backup, then SQL Server 2005 Express databases must be recovered from the SYSTEM COMPONENTS:\ save set. If the SQL Server VSS Writer service was disabled during backup, then SQL Server 2005 Express databases must be recovered from the APPLICATIONS:\MSDEWriter-SQL2000 save set. The SQL Server VSS Writer service is disabled by default when Microsoft SQL Server 2005 is installed. Recovering SQL Server 2005 stand-alone databases from the SQLServerWriter save set To recover SQL Server 2005 stand-alone databases that were backed up to the SQLServerWriter save set: 1. If restoring the master database, stop the SQL Server services for the SQL 2005 database instances. 2. From the navigation tree, expand the Applications folder and the SQLServerWriter 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 for the SQL Server 2005 database instances. Recovering SQL Server 2005 express databases from the System Components save set If the SQL Server VSS Writer service was enabled during backup, then SQL Server 2005 Express databases must be recovered from the SYSTEM COMPONENTS:\ save set. To recover SQLServer 2005 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 2005 database instances. 2. From the navigation tree, expand the SYSTEM COMPONENTS:\ folder. 3. Select the databases to recover. 4. From the System Recover Session toolbar, click Start Restore. Performing SQL Server recovery 107

108 Microsoft SQL Server Backup and Recovery 5. After the recovery is complete, start the SQL Server services for the SQL 2005 database instances. Recovering SQL Server 2005 stand-alone or express databases from the MSDE-Writer-SQL2000 save set If the SQL Server VSS Writer service was disabled during backup, then SQL 2005 express and stand-alone databases must be recovered from the MSDEWriter-SQL2000 save set. To recover SQL 2005 stand-alone or express databases that were backed up to the MSDE-Writer-SQL2000 save set: 1. Stop the SQL Server services for the SQL 2005 database instances. 2. From the navigation tree, 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 for the SQL 2005 database instances. Best practices for SQL Server backup and recovery Table 19 on page 108 lists the best practices and recommendations to follow when using NMM to back up and recover SQL Server. Table 19 SQL Server backup and recovery best practices and considerations (1 of 2) Consideration Different policies for application server data Installation path for application server program Copy-on-write versus mirroring NetWorker modules and the NMM client Best practice For application servers such as SQL servers, consider backing 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, create a separate backup group, snapshot policy, and Client resource for: Server application data Volumes and operating system data 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. Large or fast-changing databases 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 the EMC VSS Provider. If you attempt to use both the NMM client and a NetWorker module such as NetWorker Module for Microsoft SQL Server to back up application data, the module backups will be promoted to full backups. NMM client issues on page 284 provides more information about client issues. 108

109 Microsoft SQL Server Backup and Recovery Table 19 SQL Server backup and recovery best practices and considerations (2 of 2) Consideration Microsoft SQL data CLARiiON limits for the CX500 SQL instances in suspect mode Verify VSS SQL Writer service is running Ignore tempdb database Special character databases Some SQL service may have to be manually shut down to perform recovery Best practice If SQL 2005 backups were performed when the SQL Server VSS Writer service was disabled, and you subsequently enable the writer, perform a complete backup of SQL 2005 data. A complete backup enables you to recover all SQL 2005 data from the same application folder, which is named SQLServerWriter. If the number of snapshots exceeds the limit for number of snapshots supported per CLARiiON, a "VETO" failure will occur 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 SANCopy. 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 the SQL Server, especially SQL Server 2005, a user needs to verify that the VSS SQL Writer service is up and running in order for the VSS SQL Writer snapshot to be successful. The SQL Writer is installed but is disabled by default. A user must enable it or set it to automatic to use its functionality. 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 will not be 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. Administrators may have to manually shut down some SQL services to restore SQL system databases. For SQL Server 2000, manually shut down the SQL Server and the SQL Server Agent. For MSDE or SQL Server 2005, shut down the "master" and "msdb" database only if it is being recovered. Otherwise, do not shut down any MSDE or SQL 2005 database services. SQL restore does not automate this process, and requires VSS Requestors to take responsibility for controlling the SQL services during restore. Performing SQL Server recovery 109

110 Microsoft SQL Server Backup and Recovery 110

111 5 Microsoft SharePoint Server Backup and Recovery This chapter includes the following topics: Microsoft SharePoint Server backup and recovery SharePoint Server 2007 backup and recovery Performing SharePoint 2007 backups Task 5: Configure a SharePoint 2007 Client resource Performing SharePoint 2007 recovery SharePoint 2007 disaster recovery SharePoint 2003 backup and recovery Performing SharePoint 2003 backups Performing a SharePoint 2003 recovery SharePoint 2003 scenario of backup and recovery process Microsoft SharePoint Server Backup and Recovery 111

112 Microsoft SharePoint Server Backup and Recovery Microsoft SharePoint Server backup and recovery This chapter supplements the overall NetWorker Module for Microsoft Application (NMM) backup procedures in Chapter 2, Configuring a Scheduled Backup, and recovery procedures in Chapter 3, Recovering Data. SharePoint Server versions supported by NMM client NMM client supports the following versions of Microsoft SharePoint Server: Microsoft Office SharePoint Server 2007 (SP1 or later) Windows SharePoint Services 3.0 (SP1 or later) Microsoft SharePoint Portal Server 2003 (SP2) Windows SharePoint Services 2.0 (SP2) 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. The backup and recovery procedures are different for Microsoft Office SharePoint Server 2003 and Microsoft Office SharePoint Server Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 Backup and disaster recovery uses the SharePoint VSS writers and Microsoft SQL Server VSS writers. SharePoint Server 2007 backup and recovery on page 113 provides examples and steps for Microsoft Office SharePoint Server 2007 backup and recovery. This section also applies to Windows SharePoint Services 3.0. NMM also provides granular backup and recovery of SharePoint 2007 items. Chapter 6, Microsoft SharePoint 2007 Granular Backup and Recovery provides steps for performing granular backup and recovery. Microsoft SharePoint Portal Server 2003 and Windows SharePoint Services 2.0 Backup and disaster recovery uses the Microsoft SQL Server VSS writers. SharePoint 2003 backup and recovery on page 137 provides examples and steps for Microsoft SharePoint Portal Server 2003 backup and recovery. This section also applies to Windows SharePoint Services

113 Microsoft SharePoint Server Backup and Recovery SharePoint Server 2007 backup and recovery This section describes NMM support for backup and recovery of Microsoft Office SharePoint 2007, and Windows SharePoint Services 3.0 that use SharePoint 2007 writers. Microsoft SharePoint 2007 Granular Backup and Recovery on page 157 describes NMM support for granular backup and recovery of SharePoint Types of SharePoint Server 2007 backup and recovery NMM client provides these backup features: Backup types: Backup for stand-alone and distributed SharePoint farms Utilizes Volume Shadow Copy framework to create snapshot of SharePoint data Full backup level, to provide: Full backup of SharePoint content databases Full backup of Search/Content Indexes Backup granularity: Farm backup, to back up all SharePoint data in the farm, including: Content/Configuration databases Search/Index Databases Web Application backup, to provide granular backup of single web application SharePoint Object, to provide granular backup of: Farm Site collection Site Sub-site Microsoft SharePoint 2007 Granular Backup and Recovery on page 157 describes NMM support for granular backup of Web Applications and SharePoint Objects. NMM client provides these recovery features: Recovery types: Conventional Restore from snapshot Content Recovery and Disaster Recovery Directed Recovery in the same SharePoint farm Recovery for stand-alone and distributed SharePoint farms Note: Rollback is unsupported. Recovery level Full, Content/Configuration Database, Search/Content Indexes SharePoint Server 2007 backup and recovery 113

114 Microsoft SharePoint Server Backup and Recovery Advanced search The backup data can be searched by: Document Name Document Type Date Range Creation Date Modification Date Author Size Recovery granularity: Item-level recovery Extensive granular support for List Libraries, Site-Collection Templates, Web Applications, Site Collections, and Sites. Microsoft SharePoint 2007 Granular Backup and Recovery on page 157 provides a list of SharePoint items available in NMM for granular recovery. Farm recovery: Content databases Configuration database Search/Index databases Content database recovery Restore of SharePoint content databases Note: 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 the user adds a new content database 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. Requirements for installing SharePoint service pack Microsoft Office SharePoint Service Pack 1 (SP1 or later) must be installed. Without this fix installed on SharePoint machines, NMM may incorrectly list the presence of the SharePoint Help Search Writer (SPSearch Writer) on a SharePoint machine that does not actually have the writer. This could lead to a user creating an invalid saveset, and backup or recovery failure. Go to the Microsoft web site and search for Microsoft Office SharePoint Server 2007 Service Pack 1 (SP1). Download and install this on all machines in the SharePoint Server farm. Once it is installed, no further action is required for NMM. When installing SP1on a SharePoint farm, Microsoft recommends installing it in a specific order: 1. Start the SP1 installation on all machines at the same time. 2. When the Proceed message box is displayed, click OK on all remote clients, but do not click OK to proceed on the web front end yet. 3. After installation completes on all remote clients, click OK on all remote clients, and then click OK to proceed with installation on the web front end. 4. Start the SharePoint configuration wizard. 114

115 Microsoft SharePoint Server Backup and Recovery NMM installation requirements for a Microsoft Office SharePoint 2007 system A Microsoft Office SharePoint 2007 farm can be deployed in a stand-alone system. This system runs all services on one machine as shown in Figure 15 on page 115, or in a configuration that includes several servers that host separate services, as shown in Figure 16 on page 116. For NMM to backup a SharePoint farm, the NMM client must be installed on each machine in the farm. A SharePoint farm includes the following services: SharePoint 2007 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)! IMPORTANT To back up the entire farm, the NMM client must be installed on each server that hosts SharePoint data, and at least one front-end server. 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 15 SharePoint 2007 stand-alone farm configuration SharePoint Server 2007 backup and recovery 115

116 Microsoft SharePoint Server 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 16 SharePoint 2007 distributed farm configuration SharePoint 2007 data backed up by NMM NMM client backs up the following SharePoint components: Configuration database, which is a SQL configuration database Content databases which are SQL content databases SharePoint Search which includes SharePoint Search Index and associated SQL database Office Search, which includes Office Search Index and associated SQL database Note: The Search and Index databases cannot be backed up by themselves. Search/Index databases are backed up and recovered as part of farm-level backup and recovery. 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. 116

117 Microsoft SharePoint Server Backup and Recovery Configuration or database structure changes Any major changes made to the SharePoint configuration or database structure requires 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 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 124 Performing a full backup for a distributed SharePoint farm on page 127 Components used by NMM for SharePoint backup and recovery NMM uses the following VSS writers provided by Microsoft for SharePoint 2007, as well as a writer to back up the SQL database: SqlServer Writer, backs up the SQL databases. SharePoint Services Writer, the writer for SharePoint 2007, which runs on the Web front end. SharePoint Search Writer, the writer for SharePoint 2007 search. Office Server Search Writer, the writer for Microsoft Office Server search. SharePoint Server 2007 backup and recovery 117

118 Microsoft SharePoint Server Backup and Recovery Specifying SharePoint 2007 save sets for application data Table 20 on page 118 lists the SharePoint 2007 save set syntax to specify for supported types of SharePoint 2007 data. Specify SharePoint 2007 data save sets in the Save Set attribute of a Client resource. save set syntax: Table 20 SharePoint save set syntax Type of backup data SharePoint databases on SQL Server Full SharePoint backup The SharePoint Search Index and SharePoint Content Index are included when this save set is specified. Save set syntax APPLICATIONS:\SqlServerWriter APPLICATIONS:\Microsoft Office SharePoint Services 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. SharePoint content database A specific content database. For example, on the host Mars1, a database named generic_database_1 SharePoint Search Index and SharePoint Content Index APPLICATIONS:\Microsoft Office SharePoint Services\Mars1\generic_database_1 SYSTEM COMPONENTS:\Microsoft Office SharePoint Search or SYSTEM COMPONENTS:\Microsoft Office Search Note: The Search and Index save set names are provided for information only. These databases cannot be backed up by themselves. Search/Index databases are backed up as part of a farm-level SharePoint backup. 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. 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 currently hosts the application server. 118

119 Microsoft SharePoint Server Backup and Recovery 3. Press Enter. The application data save sets that are available for backup are listed in a format similar to the following: APPLICATIONS:\Microsoft Office SharePoint Services Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a Client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. URL encoding for 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 when naming SQL or SharePoint 2007 save sets. Table 21 on page 120 lists the most commonly used special characters and their URL values. Note: Save sets displayed by the nsrsnap_vss_save -? command will already include the URL encoding. The name of a SQL Server named instance or SharePoint Server content database consists of two parts: the hostname and a unique name. These two parts 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 # would be replaced with the URL-encoded value %23. The save set entry would be: APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NA%23DATA When specifying a SharePoint Server content database in the Save Set attribute, replace the backslash with its URL-encoded value, which is %5C. In the following example, a SharePoint Server content database that is identified as: Mars1\generic_database_1 would be represented in the Save Set attribute as: Mars1%5generic_database_1 To back up only the database named generic_database_1 on the server Mars1 the complete entry in the Save Set attribute would be: APPLICATIONS:\Microsoft Office SharePoint Services\Mars1%5generic_database_1 SharePoint Server 2007 backup and recovery 119

120 Microsoft SharePoint Server Backup and Recovery Table 21 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 SharePoint 2007 Application information variable settings Table 22 on page 120 lists the variables that can be specified in the Application information attribute of the Client resource. Table 22 SharePoint application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=valueap plication information attribute Specifies the snapshot service provider name. Specifies the hostname of the NMM Client that moves snapshots from the NMM Client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This value is required. The local host The proxy client hostname 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. 120

121 Microsoft SharePoint Server Backup and Recovery Performing SharePoint 2007 backups NMM backup of SharePoint provides: Point-in-time snapshots, which include exact copies of files and open files. Full SharePoint Server backup. SharePoint content and configuration database backup. Configuring SharePoint 2007 backups The NMM client must be installed on each machine in the SharePoint farm. In addition, for distributed configurations, the SharePoint writer must be registered on on one, and 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. 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: SharePoint Services Writer, on the web front-end computer only SQLServer Services VSS Writer, 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 SharePoint writer, run the following command line: STSADM.EXE o registerwsswriter The default location for STSADM.EXE is in the following folder: C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin To start the SharePoint and SQL Server writers, complete the following steps on the computer where the writer is registered. To determine the writers available on a specific machine, follow the steps in Displaying valid SharePoint 2007 data save sets on page 118. Complete the following steps 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, click Control Panel, click Administrative Tools, and then double-click Services. b. In Windows Server 2008, click Start, point to Administrative Tools, and then click Services. 2. Right-click one of the following services, and then click Properties: Performing SharePoint 2007 backups 121

122 Microsoft SharePoint Server Backup and Recovery SharePoint Services Writer (on the web front-end machine only) SQLServer Services VSS Writer (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. Repeat step 2 through step 4 for each of the listed writers present on the computer. 6. Repeat step 1 through step 5as needed on each computer in the farm to enable and start the appropriate writers on each computer. Once these writers are registered and started, you can schedule a backup. The first four tasks for scheduling a backup are the same for all VSS writers supported by NMM. Configuring a Scheduled Backup on page 45 describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 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. The following task provides specific steps for SharePoint 2007: Task 5: Configure a SharePoint 2007 Client resource on page

123 Microsoft SharePoint Server Backup and Recovery Task 5: 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 123. Configuring a SharePoint Client resource to perform a full backup of a distributed farm on page 124 Configuring a SharePoint Client resource to back up a component on a machine in a distributed farm on page 126. There are also special steps when running the distributed SharePoint farm backup, as described in Performing a full backup for a distributed SharePoint farm on page 127. 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. If you are creating multiple Client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines. To 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 The SharePoint Server save set syntax is described in Specifying SharePoint 2007 save sets for application data on page If needed, use URL-encoded values when specifying save set names in the Save Set attribute of the Client resource. Task 5: Configure a SharePoint 2007 Client resource 123

124 Microsoft SharePoint 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 SharePoint save sets on page 119. 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. 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 Backup command attribute, type the backup command. For all types of backup data except for Active Directory conventional backups, type: nsrsnap_vss_save.exe 15. In the Application information attribute, type the following variable and value: NSR_SNAP_TYPE=vss Type SharePoint application variable settings and their values on separate lines. These settings are described in Table 22 on page 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 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 SharePoint 2007 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. The components to specify in the save set for a particular machine are determined by performing the steps in Displaying valid SharePoint 2007 data save sets on page 118 on that machine. To configure a SharePoint Client resource to perform a full backup of a distributed farm: 1. Repeat step 2 on page 124 through step 19 on page 126 for each machine in the farm, specifying the appropriate save set for the machine in step 10 on page 125. For a distributed farm backup, add all client resources for the farm members to the same NetWorker backup group. 2. In the Administration window of the NetWorker Management Console, click Configuration. 3. In the expanded left pane, select Clients. 124

125 Microsoft SharePoint Server Backup and Recovery 4. From the File menu, select New. 5. In the Name attribute, type the hostname of the NetWorker client computer. 6. 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. 7. 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. 8. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available. 9. Select the Scheduled Backups attribute. 10. 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, specify the save set name: APPLICATIONS:\Microsoft Office SharePoint Services Then proceed to step 11. For the SQL Server machine, specify the save set name: APPLICATIONS:\SqlServerWriter Then proceed to step 11. For all other SharePoint machines, determine the save sets available on the specific machine by following the steps in Displaying valid SharePoint 2007 data save sets on page 118. Specify the available save set names for that machine. Then proceed to step 11. 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. The SharePoint Server save set syntax is described in Specifying SharePoint 2007 save sets for application data on page 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 URL encoding for SharePoint save sets on page 119. Note: If a save set is copied from the nsrsnap_vss_save -? output, it will already include the URL encoding. 12. For the Group attribute, select the backup group to which this Client resource will be added. For a distributed farm backup, add all client resources for the farm members to the same NetWorker backup group. Task 5: Configure a SharePoint 2007 Client resource 125

126 Microsoft SharePoint Server Backup and Recovery 13. For the Schedule attribute, select a backup schedule. 14. Click the Apps & Modules tab. 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, type the following variable and value: NSR_SNAP_TYPE=vss Type SharePoint application variable settings and their values on separate lines. These settings are described in Table 22 on page Click the Globals (1 of 2) tab. 18. 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. 19. Click OK. After the Client resources have been configured on each machine, the backup process itself requires special steps as described in Performing a full backup for a distributed SharePoint farm on page 127. Configuring a SharePoint Client resource to back up a component on a machine in a distributed farm To configure a SharePoint Client resource to back up a component on a machine in a distributed 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. If you are creating multiple Client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines: To back up all SharePoint databases (Configuration database and Content databases), specify the save set name: APPLICATIONS:\SqlServerWriter 126

127 Microsoft SharePoint Server Backup and Recovery Note: The Configuration database cannot be backed up by itself. Then proceed to step 10 on page 127. To back up a specific Content database, specify the save set name: APPLICATIONS:\SqlServerWriter\<database name> Then proceed to step 10 on page 127. 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. The SharePoint Server save set syntax is described in Specifying SharePoint 2007 save sets for application data on page 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 URL encoding for SharePoint save sets on page For the Group attribute, select the backup group to which this Client resource will be added. 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 Backup command attribute, type the backup command. For all types of backup data except for Active Directory conventional backups, type: nsrsnap_vss_save.exe 15. In the Application information attribute, type the following variable and value: NSR_SNAP_TYPE=vss Type SharePoint application variable settings and their values on separate lines. These settings are described in SharePoint application information variable settings on page 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 OK. Performing a full backup for a distributed SharePoint farm 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 Task 5: Configure a SharePoint 2007 Client resource 127

128 Microsoft SharePoint Server Backup and Recovery 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. To perform a full backup for a distributed SharePoint farm: 1. Configure a Client resource for each machine, as described in Configuring a SharePoint Client resource to perform a full backup of a distributed farm on page 124. Note: All clients in the farm must be part of the same backup group. 2. Run the NetWorker group to back up the data for all of the members of the farm. To perform a recovery after a full backup, it must be initiated from the web front end. In that process, NMM prompts you to recover each remote machine before recovering the web front-end machine. These steps are described in Full recovery of a distributed SharePoint farm on page

129 Microsoft SharePoint Server Backup and Recovery Performing SharePoint 2007 recovery After the backup is complete, NMM truncates the files. When the files are backed up, administrators can perform: Full recovery of a stand-alone SharePoint farm on page 130 Full recovery of a distributed SharePoint farm on page 130 Recovery of individual SharePoint content databases on page 132 Recovery of SharePoint Search/Content Indexes on page 132 SharePoint 2007 disaster recovery on page 134 Microsoft SharePoint 2007 Granular Backup and Recovery on page 157 Mandatory order for SharePoint recoveries In all SharePoint recoveries, the recovery process must be performed in the following sequence: 1. Configuration database 2. Content databases Note: Data loss will occur if this sequence is not followed in order. Configuration database recovery requirements in full farm recovery 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 132 provides steps for recovering individual SharePoint Content databases. Selecting valid items for recovery All valid SharePoint items available for recovery are displayed in the APPLICATIONS folder in NMM. A SYSTEM COMPONENTS node may be listed in NMM after a SharePoint backup, but it might not contain valid savesets. If SharePoint items appear under both the APPLICATIONS folder and SYSTEM COMPONENTS node, select the recovery items from the APPLICATIONS folder. Performing SharePoint 2007 recovery 129

130 Microsoft SharePoint Server Backup and Recovery 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. In the navigation tree, expand the APPLICATIONS folder and select SharePoint Services Writer. 3. From the System Recover Session toolbar, click Start Restore. Recovery proceeds to completion. Details about the recovery appear in the monitoring window. Full recovery of a distributed SharePoint farm A full recovery of a distributed SharePoint farm requires that each machine in the farm is configured as a Client resource, and each remote machine was backed up before the web front end machine was backed up. These steps are described in Performing a full backup for a distributed SharePoint farm on page 127. 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 SharePoint Services 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 17 on page 131, 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. 130

131 Microsoft SharePoint Server Backup and Recovery Figure 17 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, 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 are displayed in the monitoring window. Performing SharePoint 2007 recovery 131

132 Microsoft SharePoint Server Backup and Recovery Recovery of individual SharePoint content databases One or more content databases can be recovered after the configuration database has been restored. 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 SharePoint Services Writer. 3. Expand the SharePoint Services 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 and 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 window. Recovery of SharePoint Search/Content Indexes 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. 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 window. 132

133 Microsoft SharePoint Server Backup and Recovery Rollback of SharePoint SQL databases 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 a 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 recovery 133

134 Microsoft SharePoint Server Backup and Recovery 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 Internet Information Service (IIS), SQL Servers, and SharePoint Servers that make up the farm, including file systems and registries of each machine. Full disaster recovery requires that the following backups are performed beforehand: NMM backup of SharePoint servers on page 135. NMM full backup of Microsoft Office SharePoint Server 2007 as described in Configuring SharePoint 2007 backups on page 121. Disaster recovery planning Table 23 Table 23 on page 134 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. SharePoint server backups for disaster recovery Server type Web Front End Web Front End without Microsoft Office SharePoint Services 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 conditions 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. 134

135 Microsoft SharePoint Server Backup and Recovery The recovery of the "master" database requires that SQL services are not running at the time of recovery. If SQL services are running and an attempt to recover this database is made, the recovery attempt will fail. To perform a SharePoint Disaster Recovery: 1. Recover/restore the SharePoint servers that were backed up by NMM. Performing a disaster recovery of a NMM Client on page 87 provides more information about recovering the NMM Client. 2. Perform a recovery of the SharePoint farm as described in Full recovery of a stand-alone SharePoint farm on page 130. NMM backup of SharePoint servers The Microsoft Office SharePoint Server 2007 installation directory, web parts, IIS virtual servers, <drive>:\inetpub, and the Registry reside on all web front-end servers, application servers, and database server. To protect these critical components, ensure that you have a backup strategy that includes file system and system state backups of each SharePoint server. You should also back up the Global Assembly Cache (GAC). The GAC contains.net assemblies installed by SharePoint. The following sections describe how to back up these items: Backing up SharePoint critical components on page 135 Backing up the Global Assembly Cache on page 136 Backing up SharePoint critical components Back up the following folders by using NMM: Microsoft Office SharePoint Server 2007 installation directory on all the servers in the farm SQL installation directory on database server Virtual directories of following IIS websites on all servers in the farm: Default website SharePoint Central Admin Web application SSP web application SharePoint 2007 disaster recovery 135

136 Microsoft SharePoint Server Backup and Recovery IIS, Microsoft Office SharePoint Server 2007, and SQL logs: Internet Information Services logs (*.log) at C:\Winnt\System32\Logfiles\W3svc1\ Usage analysis log at C:\Windows\System32\LogFiles\STS\ if usage analysis is enabled Other Windows SharePoint Services logs, STSAdm.log and OWSTimer.log, from the C:\Documents and Settings\Windows_SharePoint_Services_Administrator_Account\Local Settings\Temp directory SharePoint configuration files. The directory at C:\Program Files\Common Files\Microsoft Shared\web server extensions IIS backup Registry backup on all servers Backing up the Global Assembly Cache The.NET assemblies installed in Global Assembly Cache (GAC) are not backed up by any of the SharePoint writers. To back up the GAC, back up the items as regular file system objects. The DLLs located in GAC are installed by applications and can be reinstalled during Disaster Recovery. The GAC includes SharePoint assemblies, and possibly your own custom assemblies. The GAC files are represented in Windows Explorer under C:\WINDOWS\assembly. The actual location can only be navigated to by using the command line. You cannot use GUI navigation such as Windows Explorer. For example, Microsoft.SharePoint.dll assembly is located in the following folder: C:\WINDOWS\assembly\GAC_MSIL\Microsoft.SharePoint\ e9bce111e 9429c 136

137 Microsoft SharePoint Server Backup and Recovery SharePoint 2003 backup and recovery 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. NetWorker Module for Microsoft Applications uses Microsoft SQL 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 and recovery NMM provides these backup features for SharePoint 2003 and where noted, in Windows SharePoint Services 2.0: SharePoint 2003 database backup: Configuration database (also Windows SharePoint Services 2.0) SharePoint Portal Server 2003 portal sites backup, including the following databases: Content database (also Windows SharePoint Services 2.0) User profile database Services database Index databases Windows SharePoint Services database backup Microsoft SQL Server-based Document and Picture Libraries (also Windows SharePoint Services 2.0) After a full backup of a database, individual items can be recovered from the database. Web storage system-based Document Library Store and Document Libraries 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 Components used by NMM for SQL backup and recovery NMM uses the following writers and commands to back up SharePoint 2003 databases hosted on Microsoft SQL Server: Application writers NMM uses the application writers provided by Microsoft SQL Server: MSDEWriter- SQL2000, The writer for SQL 2000/MSDE SqlServerWriter The writer for SQL Server 2005 Specifying save sets for SharePoint 2003 SQL data on page 138 describes how the writer name is used in the save set syntax. SharePoint 2003 backup and recovery 137

138 Microsoft SharePoint Server Backup and Recovery Nsrsnap_vss_save The NMM command to initiate the VSS-based backup Nsrsnap_vss_recover The NMM command to initiate the VSS-based recovery Specifying save sets for SharePoint 2003 SQL data Table 24 on page 138 lists the SharePoint 2003 save set syntax to specify for supported types of SQL data. Specify SQL data save sets in the Save Set attribute of a Client resource. save set syntax: Table 24 SQL save set syntax for SharePoint 2003 Type of data to back up All SQL Server 2005 named instances and databases including express and stand-alone databases. Only the SQL 2005 host instance and database name combination. All SQL 2000 named instances and stand-alone databases. Only the SQL 2000 host instance and database name combination. Save set syntax If the SQL Server VSS Writer service is enabled (it is disabled by default), type the following: APPLICATIONS:\SqlServerWriter If the SQL Server VSS Writer service is disabled, SQL Server 2005 named instances and databases including express and stand-alone databases, can be backed up with the following syntax: APPLICATIONS:\MSDEWriter-SQL2000 APPLICATIONS:\SqlServerWriter\host%5Ci nstance\master For example, to back up the database named test11_site on the SQL Server named instance GALL, type the following: APPLICATIONS:\SqlServerWriter\GALL%5Ct est11_site 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 in SharePoint 2003 backup on page 139 provides more information about URL encoding. APPLICATIONS:\MSDEWriter-SQL2000 APPLICATIONS:\MSDEWriter-SQL2000\host% 5C instance\master For example, to back up the database named test11_serv on the SQL Server named instance GALL, type the following: APPLICATIONS:\MSDEWriter-SQL2000\GALL% 5Ctest11_SERV Some special characters in a SQL Server named instance or database name must be replaced with URL-encoded values. URL encoding for SQL save sets in SharePoint 2003 backup on page 139 provides more information about URL encoding. 138

139 Microsoft SharePoint Server Backup and Recovery 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. 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 Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a Client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. URL encoding for SQL save sets in SharePoint 2003 backup 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. These two parts 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: GALL\test11_PROF would be represented in the Save Set attribute as: GALL%5Ctest11_PROF SharePoint 2003 backup and recovery 139

140 Microsoft SharePoint Server Backup and Recovery To back up only the database named test11_prof in the SQL Server named instance GALL, the complete entry in the Save Set attribute would be: APPLICATIONS:\SqlServerWriter\GALL%5Ctest11_PROF If the database name in the previous example was test#11_prof, the save set entry would be: APPLICATIONS:\SqlServerWriter\GALL%5Ctest%2311_PROF Table 25 on page 140 lists the most commonly used special characters and their URL values. Table 25 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 140

141 Microsoft SharePoint Server Backup and Recovery SQL application information variable settings in SharePoint 2003 backup Table 26 on page 141 lists the variables that can be specified in the Application information attribute of the Client resource. Table 26 SQL variable settings for application information attribute Attribute name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=valuea pplication information attribute Specifies the snapshot service provider name. Specifies the hostname of the NMM client that moves snapshots from the NMM client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This value is required. The local host The proxy client hostname If no value is entered, the local host is used as the data mover. If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the Client resource. For serverless backups, specify a proxy client. If setting up an SQL Client resource, use a proxy client. If a proxy client is specified, SQL 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 SQL Client resource, consistency checks are performed on the Client resource host. Related messages are logged on the Client resource host in both the Replication Manager log files and the nmm.raw file. SharePoint 2003 backup and recovery 141

142 Microsoft SharePoint Server Backup and Recovery Performing SharePoint 2003 backups SharePoint 2003 does not have its own VSS writers. To back up SharePoint 2003 databases follow the tasks for backing up a Microsoft SQL Server database. The first four tasks for scheduling a backup are the same for all VSS writers supported by NMM. Chapter 2, Configuring a Scheduled Backup, describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 The next task is specific to configuring a SQL Server Client Resource for a SharePoint database: Task 5: Configuring a SharePoint 2003 Client resource on page 142 Task 5: Configuring 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. 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. 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. 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. 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. 142

143 Microsoft SharePoint Server Backup and Recovery 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-SQL2000 The SQL Server save set syntax is described in Specifying SharePoint 2007 save sets for application data on page 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 (\), and a table of values is provided in URL encoding for SQL save sets in SharePoint 2003 backup on page Specify SQL application variable settings in the Application information attribute of the Client resource. These settings are described in Table 26 on page Click the Globals (1 of 2) tab. 12. 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 backups 143

144 Microsoft SharePoint Server Backup and Recovery Performing a SharePoint 2003 recovery The SQL Server databases used by SharePoint 2003 are recovered with NMM the same as any other SQL Server databases. Performing SQL Server recovery on page 106 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. To recover the SQL Server databases and restore them in SharePoint, use the method that corresponds to the type of SQL database you are recovering: Recovering SQL Server 2000 stand-alone databases for SharePoint 2003 on page 144 Recovering SQL 2005 databases for SharePoint 2003 on page 144 Recovering SQL Server 2000 stand-alone databases for SharePoint 2003 To recover SQL Server 2000 stand-alone databases: 1. Stop the SQL Server services for the SQL Server 2000 stand-alone database instances. 2. From the navigation tree, 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 for the SQL 2000 stand-alone database instances. 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. 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 SYSTEM COMPONENTS:\ save set. If the SQL Server VSS Writer service was disabled during backup, then SQL Server 2005 Express databases must be recovered from the APPLICATIONS:\MSDEWriter-SQL2000 save set. The SQL Server VSS Writer service is disabled by default when Microsoft SQL Server 2005 is installed. 144

145 Microsoft SharePoint Server Backup and Recovery To recover SQL 2005 stand-alone databases that were backed up to the SQLServerWriter save set: 1. If restoring the master database, stop the SQL Server services for the SQL 2005 database instances. 2. From the navigation tree, expand the Applications folder and the SQLServerWriter 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 for the SQL 2005 database instances. 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. To recover SQL 2005 express databases that were backed up to the SYSTEM COMPONENTS save set: If the SQL Server VSS Writer service was enabled during backup, then SQL 2005 Express databases must be recovered from the SYSTEM COMPONENTS:\ save set. In this case, follow these steps: 1. If restoring the master database, stop the SQL Server services for the SQL 2005 database instances. 2. From the navigation tree, expand the SYSTEM COMPONENTS:\ 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 for the SQL 2005 database instances. 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. To recover SQL Server 2005 stand-alone or express databases that were backed up to the MSDE-Writer-SQL2000 save set: If the SQL Server VSS Writer service was disabled during backup, then SQL Server 2005 express and stand-alone databases must be recovered from the MSDEWriter-SQL2000 save set. In this case, follow these steps: 1. Stop the SQL Server services for the SQL Server 2005 database instances. 2. From the navigation tree, expand the Applications folder and the MSDEWriter-SQL2000 folder. 3. Select the databases to recover. Performing a SharePoint 2003 recovery 145

146 Microsoft SharePoint Server Backup and Recovery 4. From the System Recover Session toolbar, click Start Restore. 5. After the recovery is complete, start the SQL Server services for the SQL Server 2005 database instances. 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. Best practices for SQL Server backup and recovery of SharePoint 2003 databases Table 27 on page 146 lists the best practices and recommendations to follow when using NMM to back up and recover SQL Server. Table 27 SQL Server backup and recovery best practices and considerations (1 of 2) Consideration Different policies for application server data Installation path for application server program Copy-on-write versus mirroring NetWorker modules and the NMM client Microsoft SQL data Best practice For application servers such as SQL servers, consider backing 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, create a separate backup group, snapshot policy, and Client resource for: Server application data Volumes and operating system data 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. Large or fast-changing databases 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 the EMC VSS Provider. If you attempt to use both the NMM client and a NetWorker module such as NetWorker Module for Microsoft SQL Server to back up application data, the module backups will be promoted to full backups. NMM client issues on page 284 provides more information about client issues. If SQL 2005 backups were performed when the SQL Server VSS Writer service was disabled, and you subsequently enable the writer, perform a complete backup of SQL 2005 data. Performing a complete backup enables you to recover all SQL 2005 data from the same application folder, which is named SQLServerWriter. 146

147 Microsoft SharePoint Server Backup and Recovery Table 27 SQL Server backup and recovery best practices and considerations (2 of 2) Consideration CLARiiON limits for the CX500 SQL instances in suspect mode Verify VSS SQL Writer service is running Ignore tempdb database Special Character databases Some SQL service may have to be manually shut down to perform recovery Best practice If the number of snapshots exceeds the limit for number of snapshots supported per CLARiiON, a "VETO" failure will occur 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 SANCopy. 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 the SQL Server, especially SQL 2005, a user needs to verify that the VSS SQL Writer service is up and running in order for the VSS SQL Writer snapshot to be successful. The SQL Writer is installed but is disabled by default. A user must enable it or set it to automatic to use its functionality. 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 will not be 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. Administrators may have to manually shut down some SQL services to restore SQL system databases. For SQL 2000, manually shut down the SQL Server and the SQL Server Agent. For MSDE or SQL 2005, shut down the "master" and "msdb" database only if it is being recovered. Otherwise, do not shut down any MSDE or SQL 2005 database services. SQL restore does not automate this process, and requires VSS Requestors to take responsibility for controlling the SQL services during restore. Performing a SharePoint 2003 recovery 147

148 Microsoft SharePoint Server Backup and Recovery SharePoint 2003 scenario of backup and recovery process The backup and recovery for SharePoint 2003 and WSS 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 SP2/Windows SharePoint Services 2.0 SP2 on Windows Server It uses SQL 2000/SQL 2005 for the database server. The backup and recovery is performed with NMM 2.1. The following steps describe a backup and recovery operation performed by the NMM administrator: 1. Creating a new SharePoint portal with three new databases. 2. Viewing the location and hierarchy of the databases as they appear in SQL Enterprise Manager UI. 3. Configuring and performing a backup of the new databases with NMM savesets. 4. Verifying that all databases are backed up through the NMM UI. 5. Deleting the new databases. 6. Performing an NMM recovery of the databases. 7. Verifying that the databases have been recovered through the SQL Enterprise Manager. 8. Recovering the portal site through SharePoint Portal Server Central Administration. 9. Confirming the creation of the portal site in SharePoint Server Central Administration. 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. 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. 148

149 Microsoft SharePoint Server Backup and Recovery Viewing the databases as they appear in SQL Enterprise Manager UI Figure 18 on page 149 displays the new databases as they appear in SQL Enterprise Manager. Figure 18 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. Displaying valid SQL data save sets on page 100 provides more information about using this command. The syntax for save sets is described in detail in URL encoding for SQL save sets on page 101. 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 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 104. 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 19 on page 150 shows that all of the databases, including the three new test11... databases, were backed up. SharePoint 2003 scenario of backup and recovery process 149

150 Microsoft SharePoint Server Backup and Recovery Figure 19 NMM backups available for 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 20 on page 150 shows test11_prof, test11_serv, and test11_site databases selected by the administrator. Figure 20 SQL databases selected for recovery in NMM The administrator clicks Start Recover. The recovery is successful. 150

151 Microsoft SharePoint Server Backup and Recovery Verifying database recovery through the SQL Enterprise Manager The administrator launches SQL Enterprise Manager and verifies that all three databases have been recovered. Figure 21 on page 151 shows that the three databases were recovered to the SQL Server. Figure 21 Databases recovered to SQL Server Recovering the portal site Recovering the SQL databases does not automatically bring them back into SharePoint. In SharePoint, the administrator launches SharePoint Portal Server Central Administration. Figure 22 on page 151 shows the Portal Site and Virtual Server Configuration window. Figure 22 SharePoint Server Central Administration window SharePoint 2003 scenario of backup and recovery process 151

152 Microsoft SharePoint Server Backup and Recovery The administrator clicks List and manage portal sites. In Figure 23 on page 152, the Manage Portal Sites window does not display the portal site. Figure 23 SharePoint Portal Server Central Administration, Manage Portal Sites page The administrator clicks Recover Portal Site. Figure 24 on page 152 shows the options for creating and restoring the portal. Figure 24 Portal creation and restore options 152

153 Microsoft SharePoint Server Backup and Recovery Figure 25 on page 153 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 25 Portal restore and database names After completing this page, a confirmation page is displayed, as shown in Figure 26 on page 153. Figure 26 Confirmation page for request to create a portal site SharePoint 2003 scenario of backup and recovery process 153

154 Microsoft SharePoint Server Backup and Recovery The administrator clicks OK and portal creation begins. Figure 27 on page 154 shows the status page that is displayed in SharePoint Portal Server Central Administration during portal creation. Figure 27 Status page for portal creation process Figure 28 on page 154 shows the page displayed to indicate that the portal creation was successful. Figure 28 Operation Successful page displayed when portal creation is complete 154

155 Microsoft SharePoint Server 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 29 on page 155. Figure 29 Recovered databases and SharePoint portal visible and available in SharePoint SharePoint 2003 scenario of backup and recovery process 155

156 Microsoft SharePoint Server Backup and Recovery 156

157 6 Microsoft SharePoint 2007 Granular Backup and Recovery This chapter includes the following topics: NMM support for granular backup and recovery of SharePoint items Performing SharePoint 2007 granular backups Configuring a SharePoint 2007 Client resource for granular backup SharePoint 2007 granular recovery SharePoint recovery search Performing a granular recovery of SharePoint items SharePoint prerecovery options SharePoint recovery options Microsoft SharePoint 2007 Granular Backup and Recovery 157

158 Microsoft SharePoint 2007 Granular Backup and Recovery NMM support for granular backup and recovery of SharePoint items NetWorker Module for Microsoft Applications (NMM) supports granular backup of SharePoint 2007 objects and granular recovery of SharePoint 2007 items. SharePoint objects available in NMM granular backup Granular backup of SharePoint 2007 uses a different save set syntax than that used for regular SharePoint 2007 backup. Displaying valid SharePoint 2007 save sets for granular recovery describes how to view and use this syntax to configure a Client resource for NMM backup. The following SharePoint objects are available for NMM granular backup: Farm Application Site collection Site Sub-site Note: NMM does not support backup of SharePoint documents that have not been published or checked in to SharePoint. To back up the documents in a document center site, first publish or check-in the documents, then perform the backup. SharePoint limitations on document metadata recovery Due to limitations in the Microsoft SharePoint APIs, some metadata associated with a document may not be restored when an individual document is recovered in a granular recovery. The document itself is recovered successfully, but some metadata changes that occurred after the last successful data may be lost. This is most likely to occur when a document is deleted from SharePoint, and then it is retrieved in a granular recovery. The metadata that is not recovered is not critical. However, there are several methods for recovering the metadata when the document is recovered: Recover the entire top level web site with NMM, and then retrieve the document from that recovery. This will restore all content in the web site, so all documents and data on that web site will be restored to the state they were in at the time of the last backup. or Within the SharePoint UI, retrieve the lost document from the SharePoint recycle bin. Components used by NMM for SharePoint 2007 granular backup and recovery NMM uses a special command for NMM granular backup. The Nsr_moss_save.exe command is used at the command line to display SharePoint 2007 granular backup options and save sets, and in the Client resource to run the actual backup. The syntax for specifying SharePoint 2007 granular recovery save sets is different from the VSS writer syntax used for other applications in NMM. 158

159 Microsoft SharePoint 2007 Granular Backup and Recovery To display information about SharePoint 2007 Granular Recovery options, operations, and parameters, at the command line type: Nsr_moss_save.exe -? This command can be used to display save set syntax, and to query for the SharePoint farm name, web applications, site-collections, and sub-site collections. SharePoint 2007 granular recover uses the standard NMM User Interface for recovery. Storage requirements and performance impact in SharePoint granular backup NMM performs the backup process in stages, so that you do not need as much free space for the backup as the data in the SharePoint databases. During backup, the objects are staged on the Web front end, and then sent to the NetWorker server. The data staging operations and sending to the NetWorker server operations occur in parallel. Example of staging process In this example, a SharePoint Farm has 8 top level sites, Site 1 to Site 8. Each site has a maximum size of 0.25 TB, so the total database size is 2 TB. To backup this SharePoint farm, only 0.25 TB space is needed on the Web front end: 1. Site 1 is staged to a local disk on the Web front end. This consumes a maximum of 0.25 TB of disk space. 2. Once the staging for Site 1 is completed, the staged data is sent to the NetWorker server. 3. After sending the staged data to the NetWorker server, the consumed space is reclaimed and is free disk space again. 4. Site 2 is staged, and steps 2 and 3 are performed again. This repeats for each site until all are backed up to the NetWorker server. Before staging of any site, the MOSSConnector service calculates the available free disk space and required disk space for the staging. If the available disk free space is less than the space required for staging, MOSSConnector service waits for nsr_moss_save.exe to free the used space. Once nsr_moss_save.exe frees the temporary staging after sending data to the NetWorker Server, MOSSConnector service starts staging the site. SharePoint granular backup performance tips Use frequent incremental backups between full backups, to reduce the need for full backups. Incremental backups require less network, processor, and data storage resources. To decrease wait time for the MOSSConnector service, and increase system performance on the Web front end, provide as much free disk space as you can. A public network is used to transfer data from the SQL Server backend to the Web front end during data extraction. To improve data transfer rates and network performance, install a Web front end and the NMM client on the system where the SQL Server resides, and use this Web front end for backup and restore purposes only. NMM support for granular backup and recovery of SharePoint items 159

160 Microsoft SharePoint 2007 Granular Backup and Recovery Specifying save sets for SharePoint granular backup Table 28 on page 160 lists the SharePoint save set syntax to specify for granular backup of SharePoint objects. Specify SharePoint object save sets in the Save Set attribute of a Client resource. Table 28 SharePoint granular recovery save set syntax for SharePoint 2007 objects Type of data to back up Entire SharePoint farm Single web application A SharePoint object specified by url, such as a site-collection, site, or sub-site Save set syntax NMMOSS:/<FARM_NAME> NMMOSS:/<FARM_NAME>/<WEB_APPLICATION> NMMOSS:/URL=<url> Displaying valid SharePoint 2007 syntax for granular recovery The nsr_moss_save command is used to display valid save sets that are available for granular backup. The save set syntax for a SharePoint object may include the GUID, so when you run this command, the output may wrap to more than one line in the command window for each save set. Figure 30 on page 160 displays the output of the nsr_moss_save command when used with several different switches. Figure 30 Sample output from nsr_moss_save The following example shows the Name and Save Set Syntax displayed at the command line. In a command window, the Save Set Syntax may wrap to two or more lines: nsr_moss_save -f Name Save Set Syntax SharePoint_Config_5e687d39-3cf b88b-1d3ead NMMOSS:/SharePoint_Config_5e 687d39-3cf b88b-1d3ead The save set syntax from the previous example is the following string: NMMOSS:/SharePoint_Config_5e687d39-3cf b88b-1d3ead

161 Microsoft SharePoint 2007 Granular Backup and Recovery Note: When copying Save Set Syntax from a command window, be sure to get the entire string. Always use the full Save Set Syntax for backups. To display a list of the SharePoint 2007 save sets that are available for granular backup: 1. Open a command-prompt on the application server. 2. From the command-prompt, enter one of the following commands to list the valid SharePoint objects available: nsr_moss_save [-f] Displays the current SharePoint farm name and save set syntax. The save set syntax is the type of data to back up combined with the object name. For example: nsr_moss_save -f Name Save Set Syntax SharePoint_Config_5e687d39-3cf b88b-1d3ead776569NMMOSS:/SharePoint_Config_5e 687d39-3cf b88b-1d3ead nsr_moss_save [-w] Displays all web applications and save set syntax. For example: nsr_moss_save -w All Web Applications: Name Save Set Syntax SharePoint - 80 NMMOSS:/SharePoint_Config_5e 687d39-3cf b88b-1d3ead776569/SharePoint - NMMOSS:/SharePoint_Config_5e 687d39-3cf b88b-1d3ead776569/@CentralAdmin SharePoint NMMOSS:/SharePoint_Config_5e 687d39-3cf b88b-1d3ead776569/SharePoint nsr_moss_save [-w webapplication] Displays all site-collections of a web application and save set syntax. For example, the site-collections in the web application SharePoint - 80: nsr_moss_save -w SharePoint - 80 All site-collections for Web Application: SharePoint - 80 Name Save Set Syntax NMMOSS:/Url= NMMOSS:/Url= NMMOSS:/Url= nsr_moss_save [-u site-collectionl url] Displays all sub-sites of a site-collection and save set syntax. For example, the sub-sites for the site-collection nsr_moss_save -u All Sub-sites for Site-Collection: Name Save Set Syntax NMMOSS:/Url= NMMOSS:/Url= NMMOSS:/Url= NMMOSS:/Url= NMM support for granular backup and recovery of SharePoint items 161

162 Microsoft SharePoint 2007 Granular Backup and Recovery NMMOSS:/Url= NMMOSS:/Url= NMMOSS:/Url= Each line of output provides 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. SharePoint 2007 granular application information variable settings Table 29 on page 162 lists the variables that can be specified in the Application information attribute of the Client resource. Table 29 Application information variable settings Attribute name Description Values OPTIMIZED=value Specifies whether to perform a regular backup, OPTIMIZED=true, or a granular backup, OPTIMIZED=false. true false The default value is false. This value is required. Specify false for granular backup. 162

163 Microsoft SharePoint 2007 Granular Backup and Recovery Performing SharePoint 2007 granular backups A SharePoint 2007 granular backup does not use the SQL and SharePoint VSS writers, so it is not necessary to register these writers prior to creating a Client resource for SharePoint 2007 granular backup. The first four tasks for scheduling a backup are the same for all applications and VSS writers supported by NMM. Chapter 2, Configuring a Scheduled Backup, describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 The next task is specific to configuring a SharePoint 2007 Client resource for a granular backup: Configuring a SharePoint 2007 Client resource for granular backup on page 164 Performing SharePoint 2007 granular backups 163

164 Microsoft SharePoint 2007 Granular Backup and Recovery Configuring a SharePoint 2007 Client resource for granular backup To configure a SharePoint 2007 Client resource for granular backup: 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. If you are creating multiple Client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines. To back up the entire SharePoint farm, specify the save set name: NMMOSS:/<FARM_NAME> To back up a single web application, specify the save set name: NMMOSS:/<FARM_NAME>/<WEB_APPLICATION> To back up a SharePoint object by url, such as a site-collection, site, or sub-site, specify the save set name: NMMOSS:/URL=<url> The SharePoint Server save set syntax is described in Specifying save sets for SharePoint granular backup on page For the Group attribute, select the backup group to which this Client resource will be added. 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 backup command. For all types of backup data except for Active Directory conventional backups, type: nsr_moss_save.exe 14. In the Application information attribute, type the following variable and value: OPTIMIZED=false Type SharePoint application variable settings and their values on separate lines. These settings are described in Table 29 on page

165 Microsoft SharePoint 2007 Granular Backup and Recovery 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. Configuring a SharePoint 2007 Client resource for granular backup 165

166 Microsoft SharePoint 2007 Granular Backup and Recovery SharePoint 2007 granular recovery You can individually select SharePoint items for recovery, from a granular SharePoint 2007 object backup. The items can be located and selected by browsing the navigation tree, or by searching for specific items. Note: NMM does not support backup of SharePoint documents that have not been published or checked in to SharePoint. To back up the documents in a document center site, first publish or check-in the documents, then perform the backup. NMM supports granular recovery across a wide variety of items and objects, including: List/Library: Document Library Form Library Picture Library Import Spreadsheet Announcements Contacts Discussion Board Links GenericList XMLForm Calendar Tasks Issue Tracking Survey List Template Gallery Site Template Gallery Reporting Metadata Custom List in Data Sheet View Blogs Wiki Page Library Custom List Translation Management Library Data Connection Library Slide Library Report Library Project Tasks Languages and Translators Site-Collection Template: Team Site Blank Site Document Workspace 166

167 Microsoft SharePoint 2007 Granular Backup and Recovery Basic Meeting Workspace Blank Meeting Workspace Decision Meeting Workspace Social Meeting Workspace MultiPage Meeting Workspace Document Center Record Center Personalization Site Site Directory Report Center My Site Host Collaboration Portal Publishing Portal News Site Publishing Site Publishing Site With WorkFlow Wiki Site Blog Site Search Center with Tabs Search Center Miscellaneous: SharePoint Farms Sites and Workspaces Web Applications Site Collections Sites To locate SharePoint items to recover, NMM provides a navigation tree and advanced search features for SharePoint. SharePoint recovery search on page 168 describes how to use the SharePoint recovery search features. Performing a granular recovery of SharePoint items on page 171 provides detailed information on how to recover SharePoint items. SharePoint 2007 granular recovery 167

168 Microsoft SharePoint 2007 Granular Backup and Recovery SharePoint recovery search NMM provides two methods for locating and selecting SharePoint items for recovery: Browsing through the navigation tree Searching the NetWorker index To support locating and selecting individual items for recovery, NMM s SharePoint advanced search allows you to search backup data by: Document Name Document Type Backup Time Creation Date Modification Date Minimum Size Document Title The items available for recovery depend on the actual items contained in your specific databases. Figure 31 on page 168 provides an example of how items are displayed in the NMM Recover window. You can browse the navigation tree and expand folders. Folders can be selected for recovery in the navigation tree, or individual items can be recovered in the item list. Figure 31 NMM displaying SharePoint 2007 browsing for recovery items If you are looking for a particular item it may be easier to locate the item by searching, instead of browsing folders until you find it. Figure 32 on page 169 shows the search fields available on the Search tab. Table 30 on page 169 describes the search fields that are available. 168

169 Microsoft SharePoint 2007 Granular Backup and Recovery Figure 32 NMM displaying Search tab for SharePoint 2007 recovery Table 30 SharePoint recovery search fields Field Name Object Type Backup Time Creation Date Modification Date Minimum Size Title Description The search criteria. What you are searching for. Select an object type from the list of supported SharePoint 2007 object types. Select the type of range - Before, Between, or After - and then specify the date or date range. If not selected, the default for this field is Before and a range of 90 days back from the current date. Select the type of range - Before, Between, or After - and then specify the date or date range. If not selected, this field is ignored. Select the type of range - Before, Between, or After - and then specify the date or date range. If not selected, this field is ignored. Type a number that represents the minimum size to search for in kilobytes (Kb), megabytes (Mb) or gigabytes (Gb) depending on the selection. This field only accepts integers. Alphabetical or special characters are not valid entries. Type the title of the object. This field is usually associated with list item objects. SharePoint recovery search 169

170 Microsoft SharePoint 2007 Granular Backup and Recovery Searching and marking tips There are several ways you can improve your searching and marking: Each search criteria is treated as an AND item in the search query. Search will only return items that match all criteria specified. For example, if you specify to search for an Object Name Status.doc and Minimum Size 150 kb, search will only return items that match all of the criteria: Status.doc and at least 150 Kb. It will not return any items named Status.doc that are less than 150Kb, or any other.doc files that are at least 150 kb. Marked search items will not appear in the task pane. For list item object type, multiple items may be marked and restored. Multiple versions of the same item may not marked. For all other object type searches, only a single item may be marked at a time. The maximum number of search results returned is If the search item does not appear in the results, reduce the Backup Time range. Searching for a SharePoint item To search for a SharePoint item: 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 SharePoint Recovery. 4. Click the Browse tab. 5. Navigate to the level in the tree you want to search from, or select root if you do not know where the item resides. 6. Right-click the node in the browse tree, and then click Search. 7. Select the check box for each search type to include in the search. 8. Specify what to search for in each field. 9. In the Search Results pane, mark the item to restore. 10. Select recover options. 11. Click Start Recovery. 170

171 Microsoft SharePoint 2007 Granular Backup and Recovery Performing a granular recovery of SharePoint items To recover an SharePoint object: 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 SharePoint Recovery. 4. In the navigation tree, select the SharePoint objects 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. To search for specific items, click the Search tab. 5. Locate and select the items for recovery. To view more information about a SharePoint object, right-click the object and then click Properties. 6. From the SharePoint Recover Session toolbar, click Start Recover. The Pre-Configuration options dialog box appears. This dialog box specifies where to place the restored items, how to update items, and the security permissions required. SharePoint prerecovery options on page 172 describes these options in detail. 7. Specify the Pre-Configuration options and then click OK. 8. The SharePoint Configuration Options dialog appears. This dialog box specifies where to restore items from, the location of the restore log folder, and how to lock the files after the restore job. SharePoint recovery options on page 174 describes these options in detail. 9. Specify the SharePoint Configuration options and then click OK. 10. From the left pane, select Monitor to view the progress of the recovery. Performing a granular recovery of SharePoint items 171

172 Microsoft SharePoint 2007 Granular Backup and Recovery SharePoint prerecovery options The Pre-Recovery Options dialog box specifies where to place the restored items, how to update items, and the security permissions required. Performing a granular recovery of SharePoint items on page 171 describes the recovery process and steps in detail. The default settings for this dialog box are: Recover Type: Recover to Original Location Update Version: Append to existing item Security Permissions: Inherit from parent location Note: A SharePoint web application, site collection, sub-site, list, list item such as a folder or document, or a complete SharePoint farm, cannot be recovered to an alternate location in another SharePoint farm. An alternate recovery location is always within a single SharePoint Farm. Selecting alternate destination options You can choose to restore objects to an alternate web application. However, the alternate location must be within the same farm as the backed up object. Restore to an alternate location is useful for the following: Back up site collection and restore to an alternate web application. Back up website and restore to alternate site collection or subsite. Back up list and restore to subsite or sub-web or root web. Back up list items and restore to same list and same hierarchy in alternate location. To specify Pre-Recovery Options: 1. Specify the Recovery Type. If Restore to Original Location is selected, proceed to step 3 on page 172. If Restore to Alternate Location is selected, proceed to step 2 on page In the Alternate Location group, select the locations in the order the lists are provided. The Web Applications list contains all of the web applications available in this SharePoint farm. If restoring a site object, only the Web Applications must be selected. The Site Collection list contains all of the site collections available from the selected Web Application. If restoring a web object, both the Web Application and Site Collection must be specified. The Web Site list contains all of the web sites available from the selected Site Collection. If restoring a list object, the Web Applications, Site Collection, and Web Site must be specified. 3. Select the Update Version. This specifies how to handle different versions when there are conflicting versions between the recovery version and the current version in the selected original or alternate location: 172

173 Microsoft SharePoint 2007 Granular Backup and Recovery Select Overwrite to overwrite the current version in the original or alternate location with the recovered version. After recovery, only the recovery version will be available. Select Append to add the recovered version to the current version in the original or alternate location. After recovery, the current version and the recovered version will be available. Select Ignore to retain the current version in the original or alternate location, and ignore the recovery version if it is different from the current version. 4. Select the Security Permissions. This specifies whether the SharePoint items will be locked or writable for SharePoint users during recovery. Select one of the following: All to include user memberships, role assignments such as out-of-the-box roles like Web Designer, or any custom roles that extend from the out-of-the-box roles. The ACL for each object is restored. In addition, user information defined in the DAP or LDAP servers is included. Inherit from parent (Default) to use the SharePoint security permissions of the parent container. WSS Only to include user memberships, role assignments such as out-of-the-box roles like Web Designer, or any custom roles that extend from the out-of-the-box roles. The ACL for each object is restored. No user information defined in the DAP or LDAP servers is included. 5. Click OK. The SharePoint Configuration Options dialog box appears. SharePoint recovery options on page 174 describes in detail how to specify these settings. SharePoint prerecovery options 173

174 Microsoft SharePoint 2007 Granular Backup and Recovery SharePoint recovery options The SharePoint Recovery Option dialog box specifies for all recovery jobs where to restore items from, the location of the Restore Log folder, and how to lock the files after the restore job. These settings are applied to every restore job. Performing a granular recovery of SharePoint items on page 171 describes the recovery process and steps in detail. Once a restore starts for a SharePoint Object, NMM automatically enables SharePoint write-protect. This allows you to review the restored SharePoint Object before allowing users to visit and make changes to the SharePoint Object. If a user attempts to use the website while the write-protect is in place, the following message appears, Additions to this website have been blocked. Contact the administrator to resolve this problem. Troubleshoot issues with Windows SharePoint Services. To specify recovery options: 1. In the Restore From box, type the file path or click the Browse button to specify the temporary staging area location. the source for the restore items. The Restore From location is a temporary staging area for the data from the NetWorker Server. MOSSConnector Service picks up this data and sends it to the SharePoint databases. The staging area space is reclaimed after recovery. 2. In the Restore Log Folder type the file path where the restore log file should be placed. When NMM restores SharePoint Objects, a restore log file is created during the restore. 3. In the Lock - Apply lock after restore job group, specify the read and write lock settings for the items after restore is complete. 4. Specify the SharePoint Configuration options and then click OK. 174

175 7 Microsoft Exchange Server Backup and Recovery This chapter includes the following topics: Exchange Server backup and recovery Performing Exchange Server backups Configuring an Exchange Client resource Performing Exchange Server recovery Recovery to an Exchange Recovery Storage Group Microsoft Exchange Server Backup and Recovery 175

176 Microsoft Exchange Server Backup and Recovery Exchange Server backup and recovery This chapter supplements the overall NetWorker Module for Microsoft Applications (NMM) backup procedures in Chapter 2, Configuring a Scheduled Backup, and recovery procedures in Chapter 3, Recovering Data. Microsoft Exchange Server 2003 and Exchange Server 2007 support Volume Shadow Copy Service (VSS) through Microsoft-supplied application writers. Using the VSS writers, you can back up and restore Exchange databases and transaction log files. NMM can restore storage groups or messages quickly, regardless of database size. Previous versions of NetWorker Server did not allow selection of storage groups for backup. The administrator had to restore the entire Exchange system in order to restore single, deleted messages. With NMM, the administrator can restore deleted messages from a particular group by restoring just that group. 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. Exchange Server versions supported by NMM client NMM client supports the following versions of Microsoft Exchange Server: Microsoft Exchange Server 2003 (x86) Microsoft Exchange Server 2007 (x64) SP1 or later Note: NMM does not support Microsoft Exchange Server 2000 or earlier. 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 and Exchange Server support for L18N Microsoft requires Exchange Server 2003 Storage Group names to be in the same locale as the Microsoft Exchange Server. Exchange Server backup and recovery types NMM supports several types of backup and recovery: Backup Level Full only Microsoft Exchange Server 2003: Point-in-time snapshot A backup of exact copies of files and open files. Exchange Server backup Backup of Exchange Server databases, logs, and storage groups. Storage group backup Backup of an individual storage group by creating a save set that specifies just that storage group. 176

177 Microsoft Exchange Server Backup and Recovery 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 mail can be recovered. Rollback restore Also known as a destructive recovery, because all changes that were made after the selected snapshot was 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. Microsoft Exchange Server 2007 NMM supports the backup and recovery options listed for Exchange Server 2003, and in addition supports: Backup in a Cluster Continuous Replication (CCR) environment that is running on the active node or the passive node. Backup in a Local Continuous Replication (LCR) environment of the production data, but not of the replicated data. Recovery to a Recovery Storage Group (RSG). Updating and modifying Exchange credentials Exchange credentials are configured during NMM installation. Usually, you will have a specific account that you run your Exchange Services under. If Exchange Server is installed after NMM is installed, or if the Exchange credentials have changed, NMM must be updated with the new credential information. Modifying Exchange Server 2003 credentials When installing NMM or when running the nwexinfo utility, enter the correct credentials. Otherwise backup of Client resource fails, even when the backup does not include Exchange data. To update Exchange Server 2003 credentials, run the nwexinfo.exe utility. The EMC NetWorker Module for Microsoft Applications Release 2.1 Installation Guide provides more information about initial setup of Exchange credentials during NMM installation. Adding Exchange Server 2007 credentials If Exchange Server 2007 is installed after NMM is installed, then NMM must be reinstalled after Exchange is installed. During NMM installation, add Exchange credentials. The EMC NetWorker Module for Microsoft Applications Release 2.1 Installation Guide provides more information about initial setup of Exchange credentials during NMM installation. Exchange Server backup and recovery 177

178 Microsoft Exchange Server Backup and Recovery Modifying Exchange Server 2007 credentials NMM installation configures your Exchange Server access with the username and account information you specify. If the credentials for the Exchange Server 2007 account change after the initial NMM installation, then NMM must be updated with the new credentials. You can use the following procedure to change the user account or password information for the COM+ component and the Replication Manager Exchange Interface Service. To update Exchange Server 2007 credentials: 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. 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 NetWorker Module for Microsoft Applications. After upgrading to NMM, perform a full backup of Exchange Server in order to use NMM to perform point-in-time restores in the future: To restore Exchange backups created with NetWorker Module for Exchange 5.x, use NetWorker Module for Exchange. After the recovery, perform a full backup of the Exchange server with NMM. To restore backups created with NetWorker VSS Client for Microsoft Windows 1.0, including backups created before the upgrade to NetWorker Module for Microsoft Applications 2.0, use NMM. Note: Upgrades to Microsoft Exchange Server, including Exchange Service Pack upgrades, do not allow 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. Exchange Server data backed up by NMM NetWorker Module for Microsoft Applications supports only full backups. It backs up the following Exchange Server data: Mounted Exchange Server databases Transaction log files Checkpoint files in a storage group 178

179 Microsoft Exchange Server Backup and Recovery Components used by NMM for Exchange Server backup and recovery NMM uses the following commands and Exchange Server -specific attributes to back up Exchange data: Application writers NMM uses the application writers provided by Microsoft Exchange Server. There is one writer for Exchange 2003, and two for Exchange 2007: an Information Store writer and a Replication Service writer. The Replication Service writer is only used in a CCR environment. Nsrsnap_vss_save NMM uses this command to initiate the VSS-based backup. This command can be used with options for consistency and Jet error checking. NSR_CHECK_JET_ERRORS Option used with nsrsnap_vss_save to detect Jet errors in the Exchange backup. NSR_CHECK_JET_ERRORS is run before committing the shadow copy for Exchange. eseutil A program provided by Microsoft Exchange server to check that the database and log files do not contain errors, and that the Exchange server is valid for restore. Nsrsnap_vss_recover The NMM command to initiate the VSS-based recovery. NSR_MOUNT_DB Specifies whether the database should be online or offline after restore. NSR_MOVE_TRANSLOGS Specifies the type of Exchange recovery, either replay logs or replace logs for point-in-time recovery. NSR_VIRT_SERV Specifies the name of the Exchange Virtual Server Client resource in a CCR passive node backup. NSR_INDEX_CLIENT Specifies that the backup is to be indexed under the client name of the Exchange Virtual Server, not the passive node client name in a CCR passive node backup. Exchange Server backup and recovery 179

180 Microsoft Exchange Server Backup and Recovery Specifying Exchange save sets for application data Table 31 on page 180 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. save set syntax: Table 31 Exchange save set syntax Type of data to back up Exchange Server 2003, all Exchange storage groups. Exchange Server 2003, a specific Exchange storage group. For example, a storage group named first_group. Exchange Server 2007 (Information Store), all Exchange storage groups. Exchange Server 2007 (Information Store), a specific storage group. For example, a storage group named first_storage_group. Exchange Server 2007 (Replication Service). all Exchange storage groups. Exchange Server 2007 (Replication Service), a specific storage group. For example, a storage group named second_storage_group. Save set syntax APPLICATIONS:\Microsoft Exchange Writer APPLICATIONS:\Microsoft Exchange Writer\first_group Some special characters in an Exchange storage group name must be replaced with URL-encoded values. URL encoding for Exchange save sets on page 181 provides more information about URL encoding. APPLICATIONS:\Microsoft Exchange 2007 APPLICATIONS:\Microsoft Exchange 2007\first_storage_group Some special characters in an Exchange storage group name must be replaced with URL-encoded values. URL encoding for Exchange save sets on page 181 provides more information about URL encoding. APPLICATIONS:\Microsoft Exchange 2007 APPLICATIONS:\Microsoft Exchange 2007\second_storage_group Some special characters in an Exchange storage group name must be replaced with URL-encoded values. URL encoding for Exchange save sets on page 181 provides more information about URL encoding. Displaying valid Exchange data save sets To display a list of the Exchange 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. 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. In an Exchange 2007 CCR environment, type the following on both the active and passive nodes: nsrsnap_vss_save -c physical_server_name -A NSR_VIRT_SERV=virtual_server_name -? 180

181 Microsoft Exchange Server Backup and Recovery 3. Press Enter. 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" Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a Client resource. Each entry that you add to the Save Set attribute must be typed on a separate line. URL encoding for 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 would be represented in the Save Set attribute as: APPLICATIONS:\Microsoft Exchange 2007\Accounting%5CBellevue Table 32 on page 181 lists the most commonly used special characters and their URL-encoded values. Table 32 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 Exchange Server backup and recovery 181

182 Microsoft Exchange Server Backup and Recovery Exchange Application information variable settings Table 33 on page 182 lists the variables that can be specified in the Application information attribute of the Client resource. Table 33 Exchange application information variable settings (1 of 2) Attribute name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=valuea pplication information attribute NSR_DM_PORT=value NSR_ALT_PATH=value Specifies the snapshot service provider name. Specifies the hostname of the NMM client that moves snapshots from the NMM client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. 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.1 Installation Guide provides more information about RM ports. 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. vss This value is required. The local host The proxy client hostname If no value is entered, the local host is used as the data mover. If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the Client resource. For serverless backups, specify a proxy client. If you are setting up an Exchange Client resource, it is recommended that you use a proxy client. If a proxy client is specified, Exchange consistency checks are performed on the proxy client. Related messages are written to the Replication Manager log files (erm_clientxx.log) on the proxy client. If no proxy client is specified for an Exchange Client resource, consistency checks are performed on the Client resource host. Related messages are logged on the Client resource host in both the Replication Manager log files and the nmm.raw file. The RM client control port number. For example: NSR_DM_PORT=6728 An RM client control port number must be specified. A mount path.for example: NSR_ALT_PATH=G:\mount_replica\ If a proxy client is specified in the NSR_DATA_MOVER attribute, enter the mount path on the proxy client. 182

183 Microsoft Exchange Server Backup and Recovery Table 33 Exchange application information variable settings (2 of 2) Attribute name Description Values NSR_CHECK_JET_ERRORS =value NSR_VIRT_SERV=value NSR_INDEX_CLIENT=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. 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. 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 all. 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. 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. Serverless backup A proxy client is used in conjunction with instant snapshot backups to provide serverless backups. In a typical Exchange setup with production hosts, serverless backups free the application server from much of the processing involved in a nonpersistent or instant snapshot backup. In a serverless backup, a snapshot is created on the application server and then immediately moved to the proxy client for further processing. Serverless backups are particularly useful when there is additional processing involved in a snapshot backup. For example, to help determine whether a snapshot of a Microsoft Exchange database is consistent, the Exchange utility, eseutil, should be run against the snapshot. Running eseutil can be disk intensive. Offloading the work from the Exchange server to a proxy client frees resources on the Exchange server. A serverless backup can be rolled over to a conventional backup and the backup can remain on the mounted storage disk volume as a persistent snapshot. Note: Serverless backup is available only with VSS hardware providers and is subject to the capabilities of the vendor s hardware. The EMC VSS Provider for CLARiiON and Symmetrix provides the capability to perform serverless backup operations for these storage platforms. Exchange Server backup and recovery 183

184 Microsoft Exchange Server Backup and Recovery Snapshot process in an Exchange Server production and proxy client setup Figure 33 on page 185 illustrates a LAN-based Exchange Server configuration with a storage area network and a proxy client. Both the Exchange server and the proxy client have the NetWorker Module for Microsoft Applications client installed. 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 33 on page 185, 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. NMM instructs Exchange to truncate the log files. 7. 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. 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. 184

185 Microsoft Exchange Server Backup and Recovery NetWorker Server or later 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 7.3.x Traditional storage GEN Figure 33 Snapshot process with Exchange production server and proxy client Best practices for Exchange backup and recovery In addition to Best practices and considerations for backing up application data on page 48, this section lists the best practices and recommendations to follow when using NetWorker Module for Microsoft Applications to back up and recover Exchange Server: You should perform a full backup copy of Exchange Server after every successful recovery. Ensure that all databases in a specified storage group are mounted before backing up the Exchange servers. Unmounted databases are not backed up. You should perform a full backup copy after upgrading to NMM from previous releases of NetWorker clients. Ensure that database (mailbox and public folder) files and transaction log files reside on separate volumes for backup, otherwise the backup will fail. If Exchange objects like storage groups and databases are deleted by using Exchange System Manager, 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. Exchange Server backup and recovery 185

186 Microsoft Exchange Server Backup and Recovery 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. The Exchange consistency checker utility (eseutil.exe) must be installed on the proxy host. 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. While performing a rollback restore of the Exchange server, all applications that are used by Exchange should be closed. Also, ensure that the volume that contains the Exchange data is not in use. If a rollback restore of a particular storage group is performed, ensure that this volume is not used by any other storage group that is not part of the recovery. 186

187 Microsoft Exchange Server Backup and Recovery Performing Exchange Server backups NMM supports several types and levels of backup: Point-in-time snapshots, which include exact copies of files and open files. Full backup of Exchange databases, logs, and storage groups, as well as administrator-selected storage groups. Backup in a Cluster Continuous Replication (CCR) environment on the active node and the passive node. Backup in an LCR environment of the production data, but not of the replicated data. Configuring Exchange Server backups The first four tasks for scheduling a backup are the same for all VSS writers supported by NMM. Configuring a Scheduled Backup on page 45 describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 The next task is specific to configuring an Exchange Client resource: Configuring an Exchange Client resource on page 188! CAUTION 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. Performing Exchange Server backups 187

188 Microsoft Exchange Server Backup and Recovery Configuring an Exchange Client resource A Client resource specifies what to include in a snapshot of a NMM Client. Client resources are associated with other backup resources such as groups and snapshot policies. An Exchange Client resource can specify to perform a full backup, or back up a storage group. To create an Exchange Client resource: 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. If you are creating multiple Client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines: To back up all Exchange Server 2003 data, specify the save set name: APPLICATIONS:\Microsoft Exchange Writer To back up all Exchange Server 2007 data, specify the save set name: APPLICATIONS:\Microsoft Exchange 2007 To back up a specific Exchange Server 2003 storage group, for example a storage group named Group_1, specify the save set name: APPLICATIONS:\Microsoft Exchange Writer\Group_1 To back up a specific Exchange Server 2007 storage group, for example a group named Group_1, specify: APPLICATIONS:\Microsoft Exchange 2007\Group_1 To back up all Exchange Server 2007 data in a CCR environment on the active or passive CCR node, specify: APPLICATIONS:\Microsoft Exchange 2007 To back up 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, specify: APPLICATIONS:\Microsoft Exchange 2007\Group_1 To back up all Exchange Server 2007 data on a virtual server, on the active CCR node, specify: APPLICATIONS:\Microsoft Exchange

189 Microsoft Exchange Server Backup and Recovery Note: When backing up an Exchange Server 2007 in a CCR environment on a passive CCR system, you must use the NSR_INDEX_CLIENT attribute. To back up all Exchange Server 2007 data in a LCR environment, specify: APPLICATIONS:\Microsoft Exchange 2007 To back up a specific Exchange Server 2007 storage group in a LCR environment, for example a group named Group_1, specify: APPLICATIONS:\Microsoft Exchange 2007\Group_1 The Exchange Server save set syntax is described in Specifying Exchange save sets for application data on page 180. Note: When backing up data for a Microsoft Exchange application, ensure that all databases in a specified Storage Group are mounted. If at least one database in a selected Storage Group is not mounted, the entire backup of the Storage Group will fail. 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 (\), and a table of values is provided in URL encoding for Exchange save sets on page For the Group attribute, select the backup group to which this Client resource will be added. 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 Backup command attribute, type the backup command. For all types of backup data except for Active Directory conventional backups, type: nsrsnap_vss_save.exe 15. In the Application information attribute, type the following variable and value: NSR_SNAP_TYPE=vss Type Exchange application variable settings and their values on separate lines. These settings are described in Table 33 on page 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 OK. Configuring an Exchange Client resource 189

190 Microsoft Exchange Server Backup and Recovery Performing Exchange Server recovery After the backup is complete, NMM truncates the files. When the files are backed up, administrators can restore: Exchange storage groups Mailbox stores User messages Several types of recovery are available: Point-in-time Rollback Roll forward Recovery to Recovery Storage Group (RSG) from snapshots or conventional save sets. Exchange recovery requirements and limitations The following requirements must be met before recovering Microsoft Exchange data: The APPLICATIONS:\Microsoft Exchange Writer save set (Exchange Server 2003) or APPLICATIONS:\Microsoft Exchange 2007 save set (Exchange Server 2007) must have been backed up. Chapter 2, Configuring a Scheduled Backup, provides more information about backups. For each Exchange database to be recovered, the Exchange checkbox titled This database can be overwritten by a restore must be selected in the Exchange System Manager (Exchange Server 2003) or Exchange Management Console (Exchange Server 2007) application. This is a Microsoft requirement. For information about this checkbox, refer to the Microsoft Exchange documentation. 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. If you are recovering Exchange data that was backed up from a legacy NetWorker client by using the save set VSS USER DATA:\, then the Exchange databases to which data is being recovered must be unmounted before the recovery operation. After the recovery, the databases must be mounted. There are several limitations when backing up and restoring Exchange objects with NMM: 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 of 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 may 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. 190

191 Microsoft Exchange Server Backup and Recovery Exchange recovery options To specify recovery options for Exchange data: 1. Review Performing a recovery on page Follow step 1 through step 6 in To recover system data: on page In System Recover Session Options, click the Exchange tab. 4. 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 191 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). 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 higher. Point-in-time recovery on page 192 describes this type of recovery in detail. 5. To make the Exchange database available after the recovery, select Put databases online after restore. 6. Click OK to close the System Recover Session Options dialog box. 7. 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. 9. From the System Recover Session toolbar, click Start Restore. Roll-forward recovery This option recovers the Exchange data from the last backup, and retains all existing Exchange transactions that occurred after the time of the last backup. This recovery is carried out at the time of failure. A roll-forward recovery can be performed if the current log LUN is available. The administrator restores the database files and transaction logs from backup 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. 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. Performing Exchange Server recovery 191

192 Microsoft Exchange Server Backup and Recovery To perform a roll-forward recovery of an Exchange Server 2007 in a CCR environment: 1. Perform the recovery from the active node, failing over the passive node to the active node if necessary. 2. In the Exchange Management Console application, select the Microsoft Exchange checkbox This database can be overwritten by a restore. 3. 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" 4. Open the NMM Client. 5. In the main toolbar, click the Client list, and then select the client that is the Exchange Virtual Server. 6. From the left pane, select System Recover Session. 7. From the Options menu, select System Recover Session Options, and then click the Exchange tab. 8. In Transaction Log File Replay, make sure 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. 9. From the navigation tree, expand the Applications folder and select the Microsoft Exchange 2007 folder. 10. Select the Exchange Server items you want to restore. 11. From the System Recover Session toolbar, click Start Restore. 12. Restore replication between the nodes with the resume-storagegroupcopy command. For example: resume-storagegroupcopy -Identity "bv-hood-cluse12\first Storage Group Point-in-time recovery This recovery type is useful when log files have been lost. At this level, 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. With this type of recovery the administrator gets back the deleted mail because the transaction logs are restored. In order to perform 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 192

193 Microsoft Exchange Server Backup and Recovery moved to another directory before the restore takes place. They can be manually deleted by the user if they are no longer needed after a successful restore. To perform a point-in-time recovery of an Exchange Server 2007 in a CCR environment: 1. Perform the recovery from the active node, failing over the passive node to the active node if necessary. 2. In the Exchange Management Console application, select the Microsoft Exchange checkbox This database can be overwritten by a restore. 3. 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" 4. Open the NMM Client. 5. In the main toolbar, click the Client list, and then select the client that is the Exchange Virtual Server. 6. From the left pane, select System Recover Session. 7. From the Options menu, select System Recover Session Options, and then click the Exchange tab. 8. In Transaction Log File Replay, select Include only logs from this restore (Point-in-time recovery). 9. From the navigation tree, expand the Applications folder and select the Microsoft Exchange 2007 folder. 10. Select the Exchange Server items you want to restore. 11. From the System Recover Session toolbar, click Start Restore. 12. After restore, on the passive node manually delete log files and database file. 13. 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" 14. Restore replication between the nodes with the resume-storagegroupcopy command. For example: resume-storagegroupcopy -Identity "bv-hood-cluse12\first Storage Group Mounting the database after recovery Certain pre- and post-restore operations 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. The Exchange administrator can decide if Performing Exchange Server recovery 193

194 Microsoft Exchange Server Backup and Recovery restore of a particular Exchange database is required and if automatic mounting of the database must be done after the restore is complete. If this option is specified, then the database is mounted after 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. Select or disable this option with the Put databases online after restore checkbox as described in Exchange recovery options on page 191. Rollback restore of Exchange data by using NMM Rollback recovery returns data to an earlier point in time. This recovery is known as destructive recovery because all changes that were made after the selected snapshot was 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). Exchange rollback operation requirements 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 snapshot must be taken with the proxy host. The administrator must manually mount the Exchange databases after recovery. Automatic mounting of database is not available for rollback restore. Roll back a snapshot on page 269 provides more information about rollback recovery, creating a storage array descriptor file, and the steps to perform a rollback recovery. To perform a rollback recovery of Exchange Server 2003 or 2007, follow the steps in Performing a rollback recovery on page

195 Microsoft Exchange Server Backup and Recovery To perform a rollback recovery of an Exchange Server 2007 in a CCR environment: 1. Make sure 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. 2. Follow the steps in Performing a rollback recovery on page 271 by using the following settings: The Exchange Server 2007 recovery type is Point-in-time. Browse and select the items for recovery from the client type Exchange Virtual Server. Performing Exchange Server recovery 195

196 Microsoft Exchange Server Backup and Recovery Recovery to an Exchange Recovery Storage Group NMM can recover an NMM point-in-time or rollover backup to an Exchange Server 2007 Recovery Storage Group (RSG). 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. 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 196 Recovering to the RSG on page 198 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. Exchange Server 2007 only supports one RSG at a time per server. There are two methods available within Microsoft Exchange to configure an RSG database: Exchange Management Shell at command line. Recommended. Exchange Management Console Database Recovery Management tool. Not recommended.! IMPORTANT There are known recovery failure issues with using the Exchange Management Console Database Recovery Management tool to configure an RSG. Use the Exchange Management Shell to configure an RSG. Microsoft may address this issue in the next release of the Microsoft Exchange Troubleshooting Assistant v1.1. 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 desired RSG name. rsg_path is the path to the RSG directory. The Recovery option is also needed 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 196

197 Microsoft Exchange Server Backup and 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 edb_path where: db_name is the name of the database that will be recovered. -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. 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 4. Repeat the new-mailboxdatabase for each database that will recovered. Be sure 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 will need to 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 6. 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 Recovery to an Exchange Recovery Storage Group 197

198 Microsoft Exchange Server Backup and Recovery 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. To recover to an RSG: 1. Open the NMM client software and select the NetWorker server on which the NMM client software was configured for backup. 2. If the NMM client is part of a cluster, select the virtual client to which you are recovering data. The virtual client can be selected from the Client list attribute in the application toolbar. 3. From the left pane, select Recover > System Recover Session. 4. In the navigation tree, expand the Exchange server you want to recover from. NMM displays the contents of the storage groups that have been backed up. 5. Right-click the storage group that is linked to the RSG. Figure 34 on page 198 shows the context menu with the Restore to RSG command available. Figure 34 Restore to RSG command on context menu 6. Select Restore to RSG. Figure 35 on page 199 shows the RGS Configuration command enabled when Restore to RSG is selected. Also, when a storage group is selected, the other storage groups become unavailable. In this example, the SCG storage group has been selected, so the First Storage Group is unavailable and cannot be selected. This prevents simultaneous restore of one storage group to the RSG and another storage group to the original location. 198

199 Microsoft Exchange Server Backup and Recovery Figure 35 RSG Configuration command on context menu 7. Select RSG Configuration. This verifies that all RSG databases exist and can be overwritten. It checks all databases, in case the adminstrator marks the entire storage group. If an error message like the one in Figure 36 on page 199 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. In the example shown in Figure 36 on page 199, DB1 and DB2 could be restored, but DB3 cannot until the configuration problem is fixed. Figure 36 RSG Configuration error message When a message like the one in Figure 37 on page 200 appears, the RSG configuration is correct. Recovery to an Exchange Recovery Storage Group 199

200 Microsoft Exchange Server Backup and Recovery Figure 37 RSG Configuration correct message 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. 8. Select the storage group linked to the RSG 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. 9. 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 38 on page 200 shows the entire SG2 storage group cannot be selected. Only the Mailbox Database is selectable. Figure 38 Public folders cannot be recovered to an RSG 10. After the restore, the administrator may need to mount the databases if the option to put databases online was automatically selected. 200

201 8 Microsoft Data Protection Manager Backup This chapter includes the following topics: Data Protection Manager backup and recovery Performing DPM Server backups Configuring a DPM Client resource Performing DPM Server recovery Microsoft Data Protection Manager Backup 201

202 Microsoft Data Protection Manager Backup Data Protection Manager backup and recovery NetWorker Module for Microsoft Applications (NMM) provides full backup and recovery of Microsoft System Center Data Protection Manager (DPM) DPM is Microsoft s solution for backing up and recovering Microsoft application and system data and files by using the VSS framework. DPM stores and manages this backup information in its own database. DPM can provide backup and recovery for: Windows file services Microsoft Exchange Server Microsoft SQL Server Microsoft Office SharePoint Server Virtual Server 2005 NMM supports granular and directed granular recovery to DPM-protected clients. This allows you to browse DPM replicas and select individual folders or files for recovery. With directed recovery, data that originated on one NetWorker client host is recovered to another NetWorker client host. Chapter 9, Microsoft Data Protection Manager Granular and Disaster Recovery, provides more information about DPM granular backup and recovery, and directed granular recovery. Figure 39 on page 203 shows how NMM provides support for backup and recovery of DPM data. 202

203 Microsoft Data Protection Manager Backup 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 later: 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 39 NMM protection of DPM This chapter supplements the overall NetWorker Module for Microsoft Application backup procedures in Chapter 2, Configuring a Scheduled Backup. DPM Server versions supported by NMM client NMM client supports Microsoft DPM 2007 running 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 backup and recovery types NMM supports several types of backup and recovery. For DPM, the NMM client supports: DPM configuration database backup Backup of the DPM configuration database Data Protection Manager backup and recovery 203

204 Microsoft Data Protection Manager Backup DPM Replica backup Backup all or selected DPM replicas for DPM-protected servers Backup Level supported Full only Recovery Recovery of DPM Server can include recovery of the DPM configuration database, or recovery of missing replicas in their entirety to their original locations. NMM also supports granular file recoveries of replica data to the DPM-protected client or to the DMP server. DPM data backed up by NMM NetWorker Module for Microsoft Applications supports only full backups for DPM It backs up the following DPM data: DPM configuration database: This is a SQL database. The DPM writer will describe the location of the database, and NMM will use VSS SQL writers to protect it. Note: This version of 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 DPM Server. DPM replicas: These are data containers that DPM uses to store its save sets. NMM will protect these as file system shares. Note: A DPM replica is not a VSS replica, and is not directly manipulated outside of the DPM environment. Transportable backups of DPM Replicas not supported NMM 2.1 does not support transportable backup of DPM replicas. DPM Replica is in a dynamic volume. NMM does not support local nontransportable hardware-based snapshots of dynamic volumes on Windows Server Dynamic volume support on page 30 provides more information about dynamic volume and transportable support in NMM 2.1 Components used by NMM for DPM backup and recovery Table 34 on page 204 describes commands NMM uses to back up and recover DPM data. Table 34 NMM Data Protection Manager commands (1 of 2) Item Application writer nsrsnap_vss_save nsrsnap_vss_recover Description There is one writer for DPM 2007, Microsoft DPM" NMM command initiates the VSS-based backup. NMM command initiates the VSS-based recovery. 204

205 Microsoft Data Protection Manager Backup Table 34 NMM Data Protection Manager commands (2 of 2) Item nsr_ps_single_save_per_sav eset nsr_ps_first_saveset_save dmpsync -restoredb -dbloc [path] \DBMDB2007.mdf dpmsync -sync dpmsync -reallocatereplica Description NMM command specifies that PowerSnap create a separate snapshot for each save set in the client entry. Whether the database should be online or offline after restore. This attribute is required because of DPM writer restrictions that require that the configuration database and each of the DPM Replicas must be separated into separate VSS shadow copy sets. NMM command specifies to save the DPM configuration database before saving any of the DPM Replicas. This is not required by the DPM writer., but is recommended as a best practice by Microsoft. DPM command instructing DPM to use the database at the specified location. DPM command instructing DPM to synchronize itself with the new environment. DPM command run on DPM Server before performing DPM Replica recover. This command instructs DPM Server to verify its replicas and to create the appropriate number and size of partitions to receive the recovered replicas. Note: For replicas using Custom Volumes, you cannot use this command. 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 DPM command that specifies that if the DPM Replica is unavailable for backup because it is in use, wait the specified time (in minutes) before retrying to start the backup. The default value is 10. DPM command that specifies the total number of times (he first try plus retries) to attempt to start the backup. The default value is 3. Data Protection Manager backup and recovery 205

206 Microsoft Data Protection Manager Backup Specifying DPM save sets for application data Table 35 on page 206 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 storage group name must be replaced with URL-encoded values. URL encoding for DPM save sets on page 207 provides more information about URL encoding.save set syntax: Table 35 DPM Server 2007 save set syntax Type of backup data Configuration database There will always be exactly one DPM configuration database. Protection group replica set, of a non-vss datasource 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. Protection group replica set 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. Save set syntax 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. 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. 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 the command from the physical node that is currently hosting the application server. 3. Press Enter. 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 206

207 Microsoft Data Protection Manager Backup 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. Turning the MSDE writer on or off in the registry Although DPM Server may be backed up with either the MSDE writer or the SQL writer, Microsoft recommends that you use the MSDE writer with DPM if it is available. Windows Server 2008 does not include the MSDE writer. To detect which writer is enabled, run nsrsnap_vss_save -? in a command window on the DPM server. Among the writers displayed, you should see either a list of MSDE writer components or a a list of SQL writer components. On a Windows Server 2003 machine, you can enable the MSDE writer through the following procedure: To turn the MSDE writer on or off: 1. Open Registry Editor. 2. Locate the registry key: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Se ttings\msdeversionchecking 3. To enable the MSDE writer, set the value to 0. To disable the MSDE writer set the value to Exit Registry Editor. 5. Restart the VSS service. 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 Table 12 on page 65 lists the most commonly used special characters and their URL values. Data Protection Manager backup and recovery 207

208 Microsoft Data Protection Manager Backup DPM application information variable settings Table 36 on page 208 lists the variables that can be specified in the Application information attribute of the Client resource. Table 36 DPM application information variable settings Attribute name Description Values NSR_SNAP_TYPE=value NSR_PS_SINGLE_SAVE_PE R_SAVESET=value NSR_PS_FIRST_SAVESET_S AVE=value NSR_DPM_RETRY_WAIT=val ue NSR_DPM_RETRY_MAXIMU M=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, as Microsoft recommends that it be saved first. Specifies that if the DPM Replica is unavailable for backup because it is in use, wait the specified time (in minutes) before retrying to start the backup. The default setting is 1. 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_SAVES ET=yes Configuration database save set name For example: NSR_PS_FIRST_SAVESET_SAVE=MY _DPM_CONFIG_DB 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 208

209 Microsoft Data Protection Manager Backup Performing DPM Server 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 storage groups, as well as administrator-selected storage groups. Configuring DPM backups The first four tasks for scheduling a backup are the same for all VSS writers supported by NMM. Chapter 2, Configuring a Scheduled Backup, describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Note: For Data Protection Manager backups the Backup Snapshot policy must be set to All. Backup will fail if any other value is used. Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 The next task is specific to configuring a DPM Client resource: Configuring a DPM Client resource on page 210 Performing DPM Server backups 209

210 Microsoft Data Protection Manager Backup Configuring a DPM Client resource A Client resource specifies what to include in a snapshot of a 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 and 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. Note: This version of 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 DPM Server. To create a DPM Client resource: 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. If you are creating multiple Client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines. To 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 206 describes how to find the save sets available on the DPM Server. Specifying DPM save sets for application data on page 206 describes the DPM Server save set syntax. 10. For the Group attribute, select the backup group to which this Client resource will be added. 210

211 Microsoft Data Protection Manager Backup 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. In the Application information attribute, 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 DPM application information variable settings on page 208 provides information about these variables and their values. 15. If a proxy client is being set up for the NMM, type the hostname of the proxy client in the Remote Access attribute. If the NMM is part of a cluster, type the names of the physical nodes of the cluster in the Remote Access attribute. 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 OK. Configuring a DPM Client resource 211

212 Microsoft Data Protection Manager Backup Performing DPM Server recovery When the files are backed up, administrators can the perform the following types of recovery: Performing a granular recovery of DPM objects on page 214 Performing a disaster recovery of DPM on page

213 9 Microsoft Data Protection Manager Granular and Disaster Recovery This chapter includes the following topics: Performing a granular recovery of DPM objects Performing a granular directed recovery to a DPM-protected server Performing a disaster recovery of DPM Microsoft Data Protection Manager Granular and Disaster Recovery 213

214 Microsoft Data Protection Manager Granular and Disaster Recovery Performing a granular recovery of DPM objects When NetWorker Module for Microsoft Applications (NMM) backs up a Microsoft 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 is not selectable. 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. Figure 40 on page 214 shows NMM set up for directed recovery of a DPM-protected client server. 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 40 Directed granular recovery to a DPM-protected client Performing a granular directed recovery to a DPM-protected server on page 217 provides more information about using directed recovery together with DPM granular recovery. 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. 214

215 Microsoft Data Protection Manager Granular and Disaster Figure 41 on page 215 displays the DPM Recovery modes available. Figure 41 DPM recovery modes 4. In the left pane, select Recover. Figure 42 on page 215 displays the Recover submenu. Figure 42 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 43 on page 215 is an example of a DPM server tree expanded to the file level. Figure 43 DPM granular recovery available to file level Performing a granular recovery of DPM objects 215

216 Microsoft Data Protection Manager Granular and Disaster 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. 8. Click Start Recover to begin the recovery operation. Figure 44 on page 216 displays the options available for DPM Granular Recovery. Figure 44 DPM granular recovery options 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 check box 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. 216

217 Microsoft Data Protection Manager Granular and Disaster Performing a granular directed recovery to a DPM-protected server 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, NMM is installed on the DPM Server, to protect the DPM Server, and the replicas of the DPM-protected servers. In DPM directed recovery, the DPM Server is the NMM client that NetWorker backs up, and the recovery job is run from the DPM Server, but the recovery is directed to the DPM-protected server. DPM directed granular recovery scenario The following scenario describes how DPM directed granular recovery would work with a hypothetical FileServer1 shown in Figure 45 on page 217. 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 45 Directed recovery of FileServer1 Directed recovery in DPM scenario In this scenario, the FileServer 1data 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 FileServer 1 performs the recovery, instead of the NMM client on the DPM Server. 1. The DPM Server protects a Windows Server Client, FileServer1. Performing a granular directed recovery to a DPM-protected server 217

218 Microsoft Data Protection Manager Granular and Disaster Recovery 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 recovery 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. 8. Once DPM Server is an available client, the administrator can select items for recovery from the remote client, the DPM Server, and recover them to the local client, FileServer1. Performing a granular directed recovery To perform a granular directed 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 you want to add in the Available clients on list box, and then click Add. Add or remove clients as needed. 6. Click OK. 7. Click the Client drop down list, 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. 218

219 Microsoft Data Protection Manager Granular and Disaster 12. Select DPM Recover Session. 13. Select Granular. 14. 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. 15. Click Start Recover to begin the recovery operation. 16. In the Recovery path box, specify the folder where the recovered items are to be placed. 17. Select Display these options when initiating a Recovery to show this dialog box when Start Recovery is selected. If this check box is cleared, options must be through the Recover Options button on the main NMM screen. 18. Click OK. 19. From the left pane, select Monitor to view the progress of the recovery. Performing a granular directed recovery to a DPM-protected server 219

220 Microsoft Data Protection Manager Granular and Disaster Recovery Performing a disaster recovery of DPM In DPM disaster recovery, NMM allows the DPM database and replicas to be selectable in the file view pane of NMM. Selecting replicas will select all missing replicas, since they are not selectable individually. Figure 46 on page 220 displays the DPM database and replicas in the file view pane. Figure 46 DPM database and replicas available as selectable items Note: 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 will be displayed as unavailable on the contextual menu. You can browse DPM replicas and select individual folders or files for recovery. In DPM granular recovery, the DPM configuration database is not selectable. In DPM granular recovery, NMM directed recovery is available. Performing a directed recovery on page 92 provides more information about NMM directed recovery. 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. Figure 47 on page 220 displays the DPM Recovery modes available. Figure 47 DPM recovery modes 4. In the left pane, select Recover. Figure 48 on page 221 displays the Recover submenu. 220

221 Microsoft Data Protection Manager Granular and Disaster Figure 48 Recover submenu for DPM recovery 5. Select DPM Recover Session. 6. 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. 7. Select Disaster. 8. Click Start Recover to begin the recovery operation. Figure 49 on page 221 displays the options available for DPM disaster recovery. Figure 49 DPM disaster recovery options 9. In the Recovery path box, specify the folder where the recovered databases are to be placed. 10. Select Run DPM synchronization utilities for NMM to automatically run the DPM sync commands after recovery. 11. 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 created using "custom volumes." Custom DPM volumes must be created manually. See Microsoft DPM documentation for more information regarding custom volumes. Performing a disaster recovery of DPM 221

222 Microsoft Data Protection Manager Granular and Disaster Recovery 12. Select Initiate consistency checks on recovered replicas to specify for recovery to initiate consistency checks on replicas following their recovery. 13. Select Display these options when initiating a Recovery to show this dialog box when Start Recovery is selected. If this check box is cleared, options must be through the Recover Options button on the main NMM screen. 14. Click OK. 15. From the left pane, select Monitor to view the progress of the recovery. 222

223 10 Microsoft Hyper-V Backup and Recovery This chapter includes the following topics: Hyper-V backup and recovery Performing Hyper-V backups Configuring a Hyper-V Client resource Performing Hyper-V recovery Disaster recovery of a Hyper-V parent partition Microsoft Hyper-V Backup and Recovery 223

224 Microsoft Hyper-V Backup and Recovery Hyper-V backup and recovery NetWorker Module for Microsoft Applications (NMM) provides full backup and recovery of Windows Server 2008 Hyper-V. Hyper-V is a Windows Server 2008 role that provides hypervisor-based server virtualization. NMM utilizes the Hyper-V VSS writer to back up and recover the following: Hyper-V host or parent partition Hyper-V Manager Hyper-V Initial Store configuration file Each virtual machine, or child partition This chapter supplements the overall NetWorker Module for Microsoft Application backup procedures in Chapter 2, Configuring a Scheduled Backup, and recovery procedures in Chapter 3, Recovering Data, with the specific details needed to back up and recover Hyper-V. Hyper-V version requirements NMM supports the Microsoft release-to-manufacturing (RTM) release of Hyper-V, which is available only for the x64 edition of Windows Server 2008 RTM. The initial Windows Server 2008 RTM provided a beta or release candidate (RC) version of Hyper-V. If you are using one of these pre-rtm versions of Hyper-V, or did not order Hyper-V with your Windows Server 2008 RTM license, you will need to download the Hyper-V RTM update from Microsoft. Operating system versions supported by NMM client The NMM client supports Hyper-V parent partitions on a full Windows Server 2008 x64 installation. When NMM is running in the Hyper-V parent partition, NMM parent partition support can back up virtual machines that are running the following guest operating systems: Windows Server 2008 (x86 and x64) Windows Server 2003 R2 (x86 and x64) SP2 Windows Server 2003 (x86 and x64) SP2 Windows Vista (x86 and x64) SP1 Windows XP (x86) SP3 SUSE Linux Enterprise Server 10 with SP1 x86 Edition The NMM client also is supported in Hyper-V child partitions (guests). NMM supports the same Windows Server operating systems and applications that are supported on physical servers. 224

225 Microsoft Hyper-V Backup and Recovery Hyper-V parent partition backup and recovery types NMM provides these backup features: Backup types: Backup of Hyper-V server, child partitions, and applications with each child partition Backup level: Full Backup granularity: Hyper-V backup on parent partition. All or each of the following: Hyper-V virtual machine child partitions Hyper-V Initial Store configuration file NMM client provides these recovery features Recovery types: Conventional Restore from snapshot Disaster Recovery Recovery level: Full Hyper-V server (parent partition) Hyper-V role Hyper-V child partitions Individual Hyper-V child partitions Hyper-V parent partitions, child partitions, and applications within child partitions Hyper-V requires a parent partition that is running Windows Server 2008, to host the child partitions. Each child partition is usually a server operating system running applications, such as: Microsoft Exchange Server Microsoft Office SharePoint Server Microsoft SQL Server Microsoft Data Protection Manager Hyper-V runs as a role in Windows Server 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 virtual machine files. Hyper-V backup and recovery 225

226 Microsoft Hyper-V Backup and Recovery Figure 50 on page 226 illustrates a physical server running Windows Server The Hyper-V role has been enabled on the server, and four virtual machines have been created, each running a separate operating system and different Microsoft applications. Hyper-V virtual machines with child partition operating systems and applications Physical server with Windows Server 2008 host operating system and Hyper-V role 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 50 Windows Server 2008 host with Hyper-V virtual machine child partitions 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 virtual machine child partitions and configuration information on the Hyper-V server The applications within each child partition Hyper-V storage and backup options 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 (SAN), and File Servers. Figure 51 on page 227 illustrates Hyper-V storage options. Table 37 on page 227 lists the corresponding configuration types by type of storage and connection. 226

227 Microsoft Hyper-V Backup and Recovery The Microsoft web site 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. 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 51 Hyper-V storage options Table 37 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. The following list describes how these configuration types are supported in NMM: Hyper-V backup and recovery 227

228 Microsoft Hyper-V Backup and Recovery Snapshot support: 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 37 on page 227 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. Check the EMC Information Protection Software Compatibility Guide for 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. Check the EMC Information Protection Software Compatibility Guide for the latest support information. Note: When performing parent partition backups, the Microsoft Hyper-V Writer does not include the passthrough or child-attached iscsi drives for a virtual machine. As such, configurations 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. In addition, NMM supports backup of clustered virtual machines. Backup roadmap for Hyper-V Table 38 on page 229 describes the backup tasks for the Hyper-V parent and child partitions. 228

229 Microsoft Hyper-V Backup and Recovery Table 38 Backup tasks for Hyper-V 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, etc. Other Window system components, as listed in Table 1 on page 29. On the parent partition The Hyper-V role can coexist with other applications, such as: Microsoft SQL Server Microsoft Office SharePoint Server Microsoft Exchange Server Microsoft System Center Data Protection Manager (DPM) Microsoft Windows Server Cluster NetWorker Module features on page 20 lists the specific versions supported for each of these applications. Tasks Complete tasks 1 through 7: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Task 5: Configure a Client resource on page 59 Task 6: Configure privileges on page 66 Task 7: Configure a proxy client on page 67 Configure application backups with the specific instructions for the application in: Performing SQL Server backups on page 104 Performing SharePoint 2007 backups on page 121 Performing Exchange Server backups on page 187 Performing DPM Server backups on page 209 Performing Windows Server Cluster backups on page 246 Hyper-V on parent partition Hyper-V virtual machines and Initial Store configuration file Hyper-V child partition applications Application data, such as: Microsoft SQL Server Microsoft Office SharePoint Server Microsoft Exchange Server Microsoft System Center Data Protection Manager (DPM) Microsoft Hyper-V Microsoft Windows Server Cluster NetWorker Module features on page 20 lists the specific versions supported for each of these applications. Complete tasks 1 through 4: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 Review the information in: This type of backup uses the Hyper-V writer on the parent partition. on page 230 Performing Hyper-V backups on page 234 Complete the tasks in: Configuring a Hyper-V Client resource on page 236 Configure application backups with the specific instructions for the application in: Performing SQL Server backups on page 104 Performing SharePoint 2007 backups on page 121 Performing Exchange Server backups on page 187 Performing DPM Server recovery on page 212 Performing Hyper-V backups on page 234 Performing Windows Server Cluster backups on page 246 Hyper-V backup and recovery 229

230 Microsoft Hyper-V Backup and Recovery Best practices for 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. Disaster recovery of a Hyper-V parent partition on page 240 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 virtual machine guest is backed up. The primary purpose for restoring Initial Store in NMM is for disaster recovery of the Hyper-V server. Back up Data Protection Manager, Exchange, Microsoft SQL Server, or Microsoft 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 virtual machine/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 only are supported only within child partitions. 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 Failover Clustering is supported allows you to configure failover of virtual machines. EMC Storage connected to Fibre Channel or iscsi storage can be used in the parent to host virtual machines. 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, install the NMM client on the child partition, and perform the Share Point backup locally from within the child partition. For more information about using SharePoint and Hyper-V together, check the Microsoft website for recommendations and requirements. 230

231 Microsoft Hyper-V Backup and Recovery Best practices for 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 Microsoft Exchange team recommends using backups within the child partition as the preferred method for Exchange backup and recovery. NMM supports roll-forward recovery for Microsoft 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. 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 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; child partition pass-through disks 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.1 release, Microsoft has not issued a support statement for it. Components used by NMM for Hyper-V backup and recovery Table 39 on page 231 describes commands NMM uses to back up and recover Hyper-V data. Table 39 NMM Hyper-V commands Item Application writer nsrsnap_vss_save nsrsnap_vss_recover Description There is one VSS writer for Hyper-V, Microsoft Hyper-V" NMM command that initiates the VSS-based backup. NMM command that initiates the VSS-based recovery. Specifying Hyper-V save sets for application data Figure 52 on page 232 describes what the NMM client backs up in Hyper-V, using the Microsoft Hyper-V VSS writer and NMM save sets. Hyper-V backup and recovery 231

232 Microsoft Hyper-V Backup and Recovery APPLICATIONS:\Microsoft Hyper-V Save set backs up Hyper-V Manager, 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 52 NMM backup of Hyper-V components Table 40 on page 232 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. save set syntax: Table 40 Hyper-V save set syntax Type of backup data Hyper-V Manager The entire Hyper-V Manager: the Hyper-V configuration file, and each virtual machine 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 virtual machine. There are usually multiple virtual machines on the host operating system. APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name Virtual machines can be included in a proxy backup group. 232

233 Microsoft Hyper-V Backup and Recovery 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 application server. 2. 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 the command from the physical node that is currently hosting the application server. 3. Press Enter. The following example shows the application data save sets that are available on a Hyper-V system with two virtual machines, virtual_machine_name_1 and virtual_machine_name_2: APPLICATIONS:\Microsoft Hyper-V APPLICATIONS:\Microsoft Hyper-V\Initial Store APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_1 APPLICATIONS:\Microsoft Hyper-V\virtual_machine_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 virtual machines if any exist. 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. Hyper-V application information variable settings Table 41 on page 233 lists the variables that can be specified in the Application information attribute of the Client resource. Table 41 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. Hyper-V backup and recovery 233

234 Microsoft Hyper-V Backup and Recovery Performing Hyper-V backups NMM Hyper-V backup provides full backup of Hyper-V Manager, Hyper-V virtual machines, and Hyper-V Initial Store configuration file. Preparing a virtual machine for backup Before NMM can create a backup of a Hyper-V virtual machine, Integration Services must be installed on the virtual machine. These services provide integration between the physical server and the virtual machines, such as time synchronization, guest operating system shutdown messaging, and backup support. Mount may not be captured on remote Hyper-V systems if Integration Services are not installed. Integration Services can only be installed after the guest operating system has been installed on the virtual machine. To install Integration Services, on the virtual machine guest system click the Action menu, click Insert Integration Services Setup Disk, and then click the.exe to run setup. When Windows Server 2008 is installed as the operating system on a guest system, Integration Services are installed by default. Hyper-V configuration requirements for backing up a virtual machine that contains multiple volumes When there are multiple virtual hard disks in the guest, backup of the associated VM 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, use the vssadmin command to force the shadowstorage of each volume to be on the same volume: vssadmin Add ShadowStorage /For=C: /On=C: vssadmin Add ShadowStorage /For=D: /On=D: Repeat as needed for each volume in the VM. NMM support for proxy backup of Hyper-V NMM does not support Storage Area Network (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. Virtual machine-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 234

235 Microsoft Hyper-V Backup and Recovery 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 Configuring Hyper-V backups The first four tasks for scheduling a backup are the same for all VSS writers supported by NMM. Chapter 2, Configuring a Scheduled Backup, describes these tasks in detail: Task 1: Configure a backup pool for snapshot operations on page 50 Task 2: Configure snapshot policies on page 53 Note: Hyper-V Virtual Machine snapshots are not related to NMM or NetWorker snapshots. Hyper-V Virtual Machine snapshots are created, viewed, and applied to the virtual machine through Hyper-V Manager. When NMM backs up a Hyper-V virtual machine, the Hyper-V Virtual Machine snapshots are part of that backup. Task 3: Configure a backup schedule on page 56 Task 4: Configure a backup group on page 57 The next task replaces the general instructions for Task 5 with information specific to configuring a Hyper-V Client resource: Configuring a Hyper-V Client resource on page 236 Performing Hyper-V backups 235

236 Microsoft Hyper-V Backup and Recovery Configuring a Hyper-V Client resource A Client resource specifies what to include in a snapshot of a 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 and 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 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. If you are creating multiple Client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource. 6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access. 7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly. 8. Select the Scheduled Backups attribute. 9. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines. To back up all of Hyper-V the virtual machines and the configuration file (Initial Store) specify: APPLICATIONS:\Microsoft Hyper-V To back up the virtual machines, specify: APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_1 APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_2 To back up the configuration file (Initial Store), specify: APPLICATIONS:\Microsoft Hyper-V\Information Store Note: 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 236

237 Microsoft Hyper-V Backup and Recovery Displaying valid Hyper-V save sets on page 233 describes how to find the save sets available on the Hyper-V host. Specifying Hyper-V save sets for application data on page 231 describes the Hyper-V save set syntax. 10. For the Group attribute, select the backup group to which this Client resource will be added. 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. If a proxy client is being set up for the NMM client, type the hostname of the proxy client in the Remote Access attribute. If the NMM is part of a cluster, type the names of the physical nodes of the cluster in the Remote Access attribute. Note: The Hyper-V writer does not support backup of the configuration file Initial Store to a proxy client. 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. Configuring a Hyper-V Client resource 237

238 Microsoft Hyper-V Backup and Recovery Performing Hyper-V recovery After the backup is complete, NMM truncates the files. When the files are backed up, administrators can recover all of the Hyper-V components, the Initial Store configuration file, or individual virtual machines, depending on what was specified in the backup save set. The following sections describe Hyper-V recovery: Off-line and on-line recovery Hyper-V recovery Off-line and on-line recovery A virtual machine must be offline before recovery can start. If the virtual machine is online at the time recovery is started, the Hyper-V writer will first turn off the virtual machine. Once the virtual machine is offline, the current virtual machine is destroyed, the recovery version is restored, and the virtual machine is registered. The Hyper-V writer automatically handles detecting whether the virtual machine is on-line, and turning it off. There is no action required of the administrator. Hyper-V recovery To recover Hyper-V components: 1. Open the NMM software and select the NetWorker server on which the NMM software was configured for backup. 2. If NMM is part of a cluster, select the virtual client to which you are recovering data. The virtual client can be selected from the Client list attribute in the application toolbar. 3. From the left pane, select Recover > System Recover Session. 4. From the navigation tree, expand the Applications folder and select the Microsoft Hyper-V folder. For example, in Figure 53 on page 239, the configuration file Initial Store and two virtual machines VM3-VM and W2K8-X86-VM are available for recovery. 238

239 Microsoft Hyper-V Backup and Recovery Figure 53 Hyper-V recovery items available 5. From the System Recover Session toolbar, click Start Restore. Performing Hyper-V recovery 239

240 Microsoft Hyper-V Backup and Recovery Disaster recovery of a Hyper-V parent partition Successful disaster recovery starts with good backups at all levels on the Hyper-V physical server. In a Hyper-V system, the following should be backed up on a regular schedule. 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. 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 virtual machine guests. Figure 54 on page 240 describes the order and types of 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 54 Disaster recovery order for a Hyper-V server Full disaster recovery requires that the following backups are performed ahead of time: Physical host: Application data Windows volumes Windows system components Hyper-V on host: Hyper-V virtual machines and Initial Store configuration file Hyper-V in-guest: Application data 240

241 Microsoft Hyper-V Backup and Recovery To perform a Hyper-V host disaster recovery: 1. Review best practices: Best practices for Hyper-V parent partition backup and recovery on page 230 Best practices for Hyper-V child partition applications backup and recovery on page Recover/restore the physical host which was backed up by NMM. Performing a disaster recovery of a NMM Client on page 87 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 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, using the appropriate procedure for the application. Performing a recovery on page 72 provides more information about recovering applications, including links to specific recovery steps for each application. Disaster recovery of a Hyper-V parent partition 241

242 Microsoft Hyper-V Backup and Recovery 242

243 11 Microsoft Windows Cluster Backup and Recovery This chapter includes the following topics: Windows Server Cluster backup and recovery Performing Windows Server Cluster backups Windows Server Cluster recovery Performing a disaster recovery of a clustered client in Windows Server Microsoft Windows Cluster Backup and Recovery 243

244 Microsoft Windows Cluster Backup and Recovery Windows Server Cluster backup and recovery This chapter supplements the overall NetWorker Module for Microsoft Application (NMM) backup procedures in Chapter 2, Configuring a Scheduled Backup, and recovery procedures in Chapter 3, Recovering Data, with the specific details needed to back up and recover clusters in: Microsoft Windows Server 2008 Windows Server Failover Clustering (WSFC) Microsoft Windows Server 2003 Microsoft Cluster Service (MSCS) Cluster support in NMM client NMM client supports Windows Server Clusters running on the following versions of Microsoft Windows Server: Microsoft Cluster Service (MSCS) Microsoft Windows Server 2003 SP2 (x86, x64) and Microsoft Windows Server 2003 R2 with SP2 (x86, x64): Standard Edition Enterprise Edition Datacenter Edition Windows Server Failover Clustering (WSFC) Microsoft Windows Server 2008 (x86, x64): Standard Edition Enterprise Edition Datacenter Edition Compatibility with previous Windows Cluster backups Windows Server 2008 does not support recoveries of Windows Server 2003 backups of the Cluster Writer. Many Windows legacy APIs in Windows Server 2003 are not supported in Windows Server NMM Client does not prevent attempting to recover a Windows Server 2003 Cluster to a Windows Server 2008 Cluster, but recovery will fail. Components used by NMM for Windows Cluster backup and recovery NetWorker Module for Microsoft Applications backs up Windows Cluster data as part of the SYSTEM COMPONENTS save set. There is a Cluster Writer used within SYSTEM COMPONENTS, but it cannot be specified in a save set. The Cluster writer is recovered when one of the following is selected for recover: SYSTEM COMPONENTS As part of recovery of this entire save set SYSTEM COMPONENTS:\Cluster Writer as an authoritative restore in Windows Server 2008 SYSTEM COMPONENTS:\Cluster Writer and SYSTEM COMPONENTS:\BootableSystemState as part of a nonauthoritative restore in Windows Server

245 Microsoft Windows Cluster Backup and Recovery Windows Cluster application information variable settings Table 42 on page 245 lists the variables that can be specified in NetWorker Management Console, in the Application information attribute of the Client resource. Table 42 Windows Cluster application information variable settings Attribute Name Description Values NSR_SNAP_TYPE=value NSR_DATA_MOVER=valuea pplication information attribute Specifies the snapshot service provider name. Specifies the hostname of the NMM client that moves snapshots from the NMM client to primary and secondary (conventional) storage. The host can be either a local host or a proxy client host. vss This value is required. The local host The proxy client hostname If no value is entered, the local host is used as the data mover. If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the Client resource. For serverless backups, specify a proxy client. If setting up an Windows Cluster client resource, it is recommended that you use a proxy client. If a proxy client is specified, Windows Cluster consistency checks are performed on the proxy client. Related messages are written to the Replication Manager log files (erm_clientxx.log) on the proxy client. If no proxy client is specified for an Windows Cluster client resource, consistency checks are performed on the client resource host. Related messages are logged on the client resource host in both the Replication Manager log files and the nmm.raw file. Windows Server Cluster backup and recovery 245

246 Microsoft Windows Cluster Backup and Recovery Performing Windows Server Cluster backups To configure a virtual NMM client for backup, complete all of the tasks required to back up a regular NMM client. There are additional considerations of when setting up a virtual NMM client, which are outlined in Table 43 on page 246. Table 43 Additional steps and considerations for backing up a clustered Client resource Backup task Task 4: Configure a backup group Consideration Configure a Client resource for each virtual server that is being backed up and each physical node in the cluster on which the virtual server may execute. Type the names of the physical nodes of the cluster in the Remote Access attribute of each virtual Client resource. Task 6: Configure privileges Task 7: Configure a proxy client Set up NetWorker administrator privileges for each physical node and proxy client in the cluster. If a hardware provider such as the EMC VSS Provider is being used, a proxy client must be configured for a clustered NMM client Cluster failover and backups If a node within a cluster undergoes failover during a backup operation, the operation will fail. The next scheduled backup operation will be the next valid backup. If you are using a hardware provider such as the EMC VSS Provider, use the disk management utilities provided with the associated hardware to delete any resources that may be left in an indeterminate state as a result of the failed backup. For example, a CLARiiON storage solution may have an InActive snapshot as the result of a failed backup. In this case, use the Navisphere user interface or the NaviCLI command line interface to search for and delete the inactive snapshot. 246

247 Microsoft Windows Cluster Backup and Recovery Windows Server Cluster recovery The Cluster recovery procedures are different for Windows Server 2003 and Windows Server The following sections provide more information: Performing a disaster recovery of a clustered client in Windows Server 2003 on page 248 provides information about cluster recovery in Windows Server Cluster recovery options on page 76 describes the Cluster tab in NMM Recovery options. This tab provides options for authoritative or nonauthoritative restore. Authoritative restores of the Cluster Writer are only supported for Windows Server Windows Server Cluster recovery 247

248 Microsoft Windows Cluster Backup and Recovery Performing a disaster recovery of a clustered client in Windows Server 2003 There are three different cluster recovery scenarios presented: Disaster recovery of a cluster client on page 248 describes how to recover a cluster from a backup created by the NMM client. Disaster recovery from a legacy VSS backup on page 250 describes how to recover a cluster from a VSS backup created before the NMM client was installed. Disaster recovery of a clustered client from a legacy non-vss backup on page 253 provides recommendations for how to handle legacy non-vss backup which does not work with the NMM client.! CAUTION Ensure that your snapshot policies include at least one rollover to conventional backup. Disaster recovery can only be performed from a conventional backup. Chapter 14, Snapshot Management, describes how to roll over a snapshot to a conventional backup. Disaster recovery of a cluster client The following procedure describes how to recover a single node in a two-node cluster. The procedure assumes that you are recovering Node_B and that Node_A is available. To perform a disaster recovery of a cluster client: 1. Use the Cluster Administrator tool on Node_A to evict Node_B from the cluster. For information about evicting a cluster, consult the Microsoft web site or documentation for the Cluster Administrator tool. 2. At the command prompt, type the following to clean up MSCS: cluster node Node_B /forcecleanup! CAUTION After cleaning the Cluster Server, you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform a recovery for each application that was previously installed on the node. 3. Use the Cluster Administrator tool to select Join an existing Cluster and type the cluster name. 4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations. 5. Stop the cluster service in Node_A by using one of the following methods: With the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc 248

249 Microsoft Windows Cluster Backup and Recovery 6. Select the required items to be recovered for Node_B. The procedure differs depending on whether or not the cluster service resides on a domain controller. If the cluster service resides on a member server and is not a domain controller: a. Open the NMM client software on Node_B. b. From the left pane, select Recover > System Recover Session. c. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) installation folder. d. Select the SYSTEM COMPONENTS folder. If recovering a backup created with NetWorker VSS Client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. e. From the System Recover Session toolbar, click Start Restore. If the cluster service resides on a domain controller: a. Boot the NMM client in directory service restore mode. Booting Windows in Directory Service Restore mode on page 89 provides more information about these recovery options. b. Open the NMM client software. c. From the Options menu, select System Recover Configuration Options and click NetWorker. d. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection.! CAUTION Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. e. Click OK to close the dialog box. f. From the left pane, select Recover > System Recover Session. g. Stop the cluster service in Node_B by using one of the following methods: With the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc h. Select all local drives except for the NMM client installation folder and the Replication Manager (RM) installation folder. i. In the navigation tree, select BootableSystemState and Cluster Writer. j. Select the SYSTEM COMPONENTS folder. If recovering a backup created with NetWorker VSS Client 1.0 SP1, under SYSTEM COMPONENTS, clear ASR DISK. k. From the System Recover Session toolbar, click Start Restore. Performing a disaster recovery of a clustered client in Windows Server

250 Microsoft Windows Cluster Backup and Recovery When prompted, restart Node_B. 7. Start the Cluster service on Node_A by using one of the following methods: With the control panel service tool, start the Cluster service. At the command prompt, type the following: net start clussvc 8. Use the Cluster Administrator on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred. If you are performing regular scheduled backups, this will recover the cluster database to a point shortly before the loss of Node_B. 9. Use the Cluster Administrator on Node_A to monitor the cluster "joining" status of node_b. 10. Use the Cluster Administrator on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group. Cluster recovery environment variable settings If a Windows Server 2003 cluster database recover failed because the partition layout of the quorum disk has changed since the backup, or the drive letter of the quorum disk is already being used, the recovery process can be repeated with these environment variables defined as: %NsrClusterForceRecover% should be set to 1. %NsrClusterNewQuorumDrive% should be set to the drive letter of the new quorum disk (for example, R:). There should only be one active node during the recovery. If other nodes are active and the environment variable %NsrClusterForceRecover% is not defined, then the recovery will fail. With %NsrClusterForceRecover% defined, the recover process will attempt to shut down the cluster service on the other active nodes. It will also attempt to change the signature and drive letter (if %NsrClusterNewQuorumDrive% is defined) of the current quorum disk even if its partition layout does not match the one described in the backup. However, the success of the recovery is not guaranteed even with %NsrClusterForceRecover% defined. Disaster recovery from a legacy VSS backup The procedure for disaster recovery of a clustered client from a legacy VSS backup differs depending on whether or not the cluster service resides on a domain controller. For cluster service on a member server This recovery is for a VSS backup created before the NMM Client was installed. This backup would include VSS SYSTEM SERVICES, VSS SYSTEM FILESET, and VSS SYSTEM BOOT. The following procedure describes how to recover a single node in a two-node cluster. The procedure assumes that you are recovering Node_B and that Node_A is available: 1. Use the Cluster Administrator tool on Node_A to evict Node_B from the cluster. 2. At the command prompt, type the following to clean up MSCS: cluster node Node_B /forcecleanup 250

251 Microsoft Windows Cluster Backup and Recovery! CAUTION After cleaning up the Cluster Server, you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform a recovery for each application that was previously installed on the node. 3. Use the Cluster Administrator tool to select Join an existing Cluster and type the cluster name. 4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations. 5. Stop the cluster service in Node_A by using one of the following methods: Using the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc 6. Select the required items to be recovered for Node_B: a. Open the NMM client software on Node_B. b. From the left pane, select Recover > System Recover Session. c. Select all local drives except for the NMM client installation directory. d. Select VSS SYSTEM SERVICES, VSS SYSTEM FILESET, and VSS SYSTEM BOOT. e. From the System Recover Session toolbar, click Start Restore. f. When prompted, restart Node_B. 7. Start the Cluster service on Node_A by using one of the following methods: Use the control panel service tool to start the Cluster service. At the command prompt, type the following: net start clussvc 8. Use the Cluster Administrator tool on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred. If you have been performing regular scheduled backups, this will recover the cluster database to a point in time shortly before the loss of Node_B. 9. Use the Cluster Administrator tool on Node_A to monitor the cluster "joining" status of Node_B. 10. Use the Cluster Administrator tool on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group. Performing a disaster recovery of a clustered client in Windows Server

252 Microsoft Windows Cluster Backup and Recovery For cluster service on a domain controller This recovery is for a VSS backup created before the NetWorker VSS Client was installed. This backup would include VSS SYSTEM BOOT, VSS SYSTEM FILESET, and VSS SYSTEM SERVICE. The following procedure describes how to recover a single node in a two node cluster. The procedure assumes that you are recovering Node_B and that Node_A is available: 1. Use the Cluster Administrator on Node_A to evict Node_B from the cluster. 2. At the command prompt, type the following to clean up MSCS: cluster node Node_B /forcecleanup! CAUTION After cleaning up the Cluster Server, you must reproduce the preexisting application environment on Node_B so MSCS can administer the applications as it did before the node failed. One way to reproduce the preexisting application environment is to perform a recovery for each application that was previously installed on the node. 3. Use the Cluster Administrator to select Join an existing Cluster and type the cluster name. 4. Use the Cluster Administrator tool on Node_A to ensure that Node_B appears available for failover operations. 5. Stop the cluster service in Node_A by using one of the following methods: Use the control panel service tool to stop the Cluster service. At the command prompt, type the following: net stop clussvc 6. Select the required items to be recovered for Node_B: a. Boot the NMM client in directory service restore mode. Booting Windows in Directory Service Restore mode on page 89 provides more information about these recovery options. b. Open the NMM client software. c. From the Options menu, select System Recover Configuration Options and click the NetWorker tab. d. Clear the Use Microsoft best practices for selecting the system state attribute and click Yes when asked to confirm your selection.! CAUTION Do not clear the "Microsoft Best Practices" box except where specifically instructed to do otherwise in this document. For instance, there are some procedures, such as recovering Distributed File System (DFS) data, where you can clear this attribute. Microsoft does not support recovery of portions of the operating system. Attempted recovery of portions of the operating system, with this box cleared, may render the system unbootable. After each recovery operation, this option is automatically selected. e. Click OK to close the dialog box. 252

253 Microsoft Windows Cluster Backup and Recovery f. From the left pane, select Recover > System Recover Session. g. Stop the cluster service in Node_B by using one of the following methods: Using the control panel service tool, stop the Cluster service. At the command prompt, type the following: net stop clussvc h. Select all local drives except for the NMM client installation directory. i. Select VSS SYSTEM SERVICES, VSS SYSTEM FILESET, and VSS SYSTEM BOOT. j. From the System Recover Session toolbar, click Start Restore. When prompted, restart Node_B. 7. Start the Cluster service on Node_A by using one of the following methods: Use the control panel service tool to start the Cluster service. At the command prompt, type the following: net start clussvc 8. Use the Cluster Administrator tool on Node_A to confirm that the cluster resources were recovered to the point in time when the backup occurred. If you have been performing regular scheduled backups, this will recover the cluster database to a point in time shortly before the loss of Node_B. 9. Use the Cluster Administrator tool on Node_A to monitor the cluster "joining" status of Node_B. 10. Use the Cluster Administrator on Node_B to verify that the cluster group can be moved between the nodes by right-clicking the group and selecting Move group. Disaster recovery of a clustered client from a legacy non-vss backup This recovery is for a non-vss backup created before the NMM client was installed. This backup would include SYSTEM STATE, SYSTEM DB, and SYSTEM FILES. Recovery of non-vss backups of the cluster database by using the NMM client does not work. To ensure that backups of the cluster database are available for recovery, perform a full backup of the system directly after updating the system to the NMM client. This creates a postinstallation cluster backup that can be recovered by using the NMM Client. Monitoring a recovery The progress of all recovery operations can be viewed from the Monitor window. Monitor view on page 40 provides more information about the Monitor window. Performing a disaster recovery of a clustered client in Windows Server

254 Microsoft Windows Cluster Backup and Recovery 254

255 12 Active Directory Recovery This chapter includes the following content: Recovering all Active Directory data Performing a granular recovery of AD objects and attributes Active Directory Recovery 255

256 Active Directory Recovery Recovering all Active Directory data The steps in this procedure assume that any damaged hardware has been replaced and that all software has been reinstalled. To ensure the successful disaster recovery of the Active Directory (AD) server, the backup steps described in Chapter 13, Active Directory and ADAM Backups, must have been completed. Note: If you have followed Microsoft best practices, you will have a backup AD server that can be promoted to the primary AD server in the event of a disaster. This is the preferred method to recover an AD server from disaster. If you do not have a backup AD server that can be promoted to the primary AD server, complete the steps in this section to recover from a disaster of the AD server. To recover AD server data from a disaster: 1. If you have not already done so, boot the NMM client in Directory Service Recovery mode. Booting Windows in Directory Service Restore mode on page 89 provides more information about booting in this mode. 2. Open the NMM software and select the NetWorker Server on which the NMM client was configured for backup. 3. In the left pane, select Recover > System Recover Session. 4. 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. 5. Select items to recover: If the AD server is not in a clustered environment, select all of the items under the SYSTEM COMPONENTS folder. If the AD 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. 6. To determine whether any volumes need to be mounted, right-click the selected item and select Required Volumes. 7. From the System Recover Session toolbar, click Start Restore. 256

257 Active Directory Recovery 8. To perform an authoritative recovery of the AD server, complete the procedure for authoritative recovery of NTDS or FRS data. Performing an authoritative recovery of NTDS or FRS data on page 90 provide more information about these types of recovery. 9. After the AD recovery is complete, reboot the host to restart the AD server. 10. If the AD server is part of a cluster environment, select the Cluster Writer for recovery. 11. Recover any remaining volume or application data. Chapter 3, Recovering Data, provides more information about recoveries. Recovering all Active Directory data 257

258 Active Directory Recovery Performing a granular recovery of AD objects and attributes You can individually select deleted AD objects and their attributes for recovery. Note: Due to AD limitations, there are some restrictions on the recovery of objects and attributes. Recovery Restrictions for Active Directory on page 259 provides more information about recovery restrictions. To recover an AD 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 AD objects 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. 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. 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. 7. Click OK. 8. From the left pane, select Monitor to view the progress of the recovery. 258

259 Active Directory Recovery Recovery Restrictions for Active Directory The following restrictions apply when recovering AD objects and attributes: Tombstone lifetime restriction on page 259 System-only attributes cannot be recovered on page 259 Object password attributes on page 260 Attributes with null values on page 260 Schema objects on page 260 Note: After starting an AD recovery, access the Monitor view to verify the status of the recovery. For more information about Active Directory objects and attributes, refer to the Microsoft website. Tombstone lifetime restriction When an AD 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 Identifier (SID) and the Global 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 AD restriction. The tombstone lifetime is a configurable attribute of a Windows domain. For more information, refer to the Microsoft Windows 2003 Server documentation on AD. System-only attributes cannot be recovered Object attributes that are system-only cannot be backed up nor recovered. This is an AD restriction. The following partial list of system-only attributes are not backed up: distinguishedname dscorepropagationdata instancetype objectcategory objectclass objectguid usnchanged usncreated whenchanged whencreated badpasswordtime Performing a granular recovery of AD objects and attributes 259

260 Active Directory Recovery badpwdcount lastlogoff lastlogon logoncount samaccounttype useraccountcontrol 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. 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 AD 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, should never be deleted. 260

261 13 Active Directory and ADAM Backups This chapter includes the following topics: Active Directory backup and recovery Types of supported backup and recovery Performing an AD or ADAM backup Performing a granular AD or ADAM backup Active Directory and ADAM Backups 261

262 Active Directory and ADAM Backups Active Directory backup and recovery This chapter and Chapter 12, Active Directory Recovery, supplement the overall NetWorker Module for Microsoft Applications (NMM) backup procedures in Chapter 2, Configuring a Scheduled Backup, and recovery procedures in Chapter 3, Recovering Data, with the specific details needed to back up and recover Active Directory (AD), Active Directory Application Mode (ADAM), and Active Directory Lightweight Directory Services (AD LDS). Note: In Windows Server 2008, 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. 262

263 Active Directory and ADAM Backups Types of supported backup and recovery NMM supports the following types of backup: Active Directory Backup for Disaster Recovery Backup of entire AD database Utilizes Volume Shadow Copy (VSS) framework to create snapshot of AD data Backup Level: Full only Active Directory Granular Backup Conventional backup of individual AD objects and object attributes Backup Levels: Full and Incremental NMM supports the following types of recovery: Active Directory Recovery for Disaster Recovery Recovery of entire AD database Authoritative or Nonauthoritative Recovery Modes Active Directory Granular Recovery: Recovery of individual AD objects or attributes Types of supported backup and recovery 263

264 Active Directory and ADAM Backups Performing an AD or ADAM backup Performing an AD backup for disaster recovery enables the recovery of the entire AD database in the event of a catastrophic loss such as a hardware failure. AD 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 AD database in one recovery operation. To enable the disaster recovery of AD or ADAM data, create a snapshot-based scheduled backup as described in Chapter 2, Configuring a Scheduled Backup. When specifying save sets for the scheduled backup, follow these guidelines: AD 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 also recommends that a backup AD server be set up so that it can be promoted to the primary AD 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. 264

265 Active Directory and ADAM Backups Performing a granular AD or ADAM backup A granular, or conventional, Active Directory (AD) backup enables you to recover individual objects and object attributes. A granular Active Directory Application Mode (ADAM) backup enables you to recover individual application partitions.! CAUTION Granular recovery should only be performed as a supplement to the full AD database backup described in Types of supported backup and recovery on page 263. A disaster recovery plan requires regular full AD database backups. Unlike other types of NMM client backups, a granular backup does not use snapshot technology. Instead, the backup is routed directly to a granular backup medium. For ADAM backup, complete the tasks in Set up local Windows SYSTEM account as an ADAM administrator on page 265 before performing a granular ADAM backup. Set up local Windows SYSTEM account as an ADAM administrator 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: These steps are not required for AD 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 list box. 4. Type the port number (typically 50000) of the ADAM partition in the Port box and 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. Repeat this procedure for each ADAM instance that you want to back up. Performing a granular AD or ADAM backup 265

266 Active Directory and ADAM Backups Granular backup tasks The tasks involved in setting up a granular AD or ADAM backup are similar to the tasks described in Chapter 2, Configuring a Scheduled Backup. The differences are outlined in Table 44 on page 266. Table 44 Setting up a granular AD or ADAM backup Backup task Configure a backup pool Configure snapshot policies Configure a backup schedule Configure a backup group Configure a Client resource Configure a Client resource, Save Set attribute Configure a Client resource, Backup Command attribute Configure privileges Configure a proxy client Considerations Use backup pools for granular AD or ADAM backups that are different than the pools used for NMM client backups that include snapshots. In this way, you can sort granular AD and ADAM backups from other backups. Do not use a snapshot policy for granular AD or ADAM backups. Full and incremental level backups are supported for granular AD and ADAM backups. Level 1 to 9 backups are not supported. Do not assign a snapshot policy or a snapshot pool to the backup group. Do not use the same Client resource for AD or ADAM granular backups and other NMM client backups including AD or ADAM backups for the purposes of disaster recovery. 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. CN=Users,DC=corp,DC=xyz,DC=com where the backup includes Active Directory User objects for the domain name, corp.xyz.com. CN=user123,CN=Users,DC=domain,DC=com where the backup includes Active Directory user123 objects for the domain name, users.domain.com. AD 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 In addition to the permission set up described in Chapter 2, Configuring a Scheduled Backup, ensure that the steps described in Set up local Windows SYSTEM account as an ADAM administrator on page 265 are completed. Do not configure a proxy client for granular AD backups. 266

267 14 Snapshot Management This chapter includes the following topics: Roll over a snapshot Roll back a snapshot Delete a snapshot Snapshot Management 267

268 Snapshot Management Roll over a snapshot A rollover is the process of creating a conventional backup from a snapshot. Conventional backups include backup to tape, file type, or advanced file type devices. Rollover policies are typically controlled automatically through snapshot policy settings on the NetWorker server. Chapter 2, Configuring a Scheduled Backup, provides more information about scheduling backups. However, you can perform a rollover manually if necessary. For example, before recovering a database that currently exists only as a persistent snapshot, consider rolling over the snapshot to tape to protect the data in case the snapshot becomes corrupted during the recovery process. Another reason to perform a rollover manually, is to roll over only selected save sets from the snapshot. For example, if a snapshot contains two save sets: D:\ and E:\, you can select to roll over only the data in the E:\ save set. To roll over a snapshot: 1. Open the NMM client software and select the NetWorker server on which the NetWorker client was configured for backup. 2. In the left pane, select Snapshot Management. 3. In the navigation tree, select the snapshot and expand the snapshot to view the save sets. Select the snapshot or snapshot save sets to be rolled over. 4. From the Snapshot Management toolbar, click Rollover to begin the rollover operation. 5. In the left pane, select Monitor to view the progress of the rollover operation. 268

269 Snapshot Management Roll back a snapshot A rollback recovery is the process of returning data to an earlier point-in-time. The entire contents of a persistent snapshot is recovered during a rollback recovery. You cannot select individual components in a rollback recovery operation. A rollback recovery is the fastest way to recover the contents of a persistent snapshot. A rollback recovery is known as a "destructive" recovery because all changes that were made after the selected snapshot was taken are overwritten. For example, suppose that a snapshot of a database is taken every hour. At 5:30 P.M., it is determined that the database is corrupt and that the last known consistent database snapshot was taken at 5:00 P.M. When the database host is rolled back to the 5:00 P.M. snapshot, all database transactions between the time of the 5:00 P.M. snapshot and 5:30 P.M. are overwritten. Rollback recovery requirements To perform a rollback operation, the following requirements must be met: The snapshot to be rolled back must reside on a CLARiiON or Symmetrix storage system that is supported with the EMC VSS Provider. EMC NetWorker Module for Microsoft Applications Release 2.1 Installation Guide provides more information. The NMM client to which the snapshot is to be rolled back must be supported with a proxy client and the snapshot must have been created using a proxy client. Chapter 2, Configuring a Scheduled Backup, provides more information about backup using a proxy client. The nested mount points on file systems are dismounted prior to performing the rollback restore. The Microsoft Exchange checkbox titled This database can be overwritten by a restore is selected for each Exchange database that is to be recovered. This checkbox can be found by using the Exchange SYSTEM Manager application. The databases are detached for each Microsoft SQL Server database that is to be recovered. NMM does not support rollback restore for backups performed with EqualLogic or Celerra hardware. Only conventional restore and snapshot restore are supported for those hardware. Distributed Link Tracking Client must be turned off during rollback, or else dismount will fail. Turn off the Distributed Link Tracking Client in Windows Services before starting rollback. The SYSTEM process must not be running during rollback, or else dismount will fail. The SYSTEM process leaves the volume open when there are software shadow copies on the volume. To ensure that the volumes are not open, delete any shadow copies on the volumes that are being rolled back. Storage array descriptor file A storage array descriptor file, sa.ini, contains information about the storage arrays connected to the proxy client data mover. The sa.ini file is created with the nsr_sa_ini.exe utility, and placed in the nsr\res directory on the NMM client host. Nsr_sa_ini.exe prompts you for information about the storage arrays connected to the proxy client. Roll back a snapshot 269

270 Snapshot Management The required inputs are different for CLARiiON and Symmetrix: For a CLARiiON storage array, you must provide an array user name and password. When you complete the entries for a CLARiiON sa.ini file, the password string is encrypted when you save the file. Sample CLARiiON sa.ini file on page 270 provides an example of the entries in this file. For a Symmetrix storage array, the sa.ini file has are fewer parameters - you do not need an account name, password, or IP address. Sample Symmetrix sa.ini file on page 270 provides an example of the entries in this file. To create a storage array descriptor file: 1. At the command line, type: nsr_sa_ini.exe 2. Follow the prompts to provide the array information. Note: Even though the utility appears to allow you to enter credentials for more than one storage array, only the first one will be used by NMM. You must create a separate sa.ini for each storage array. When you have completed entering the array information, the file is saved to the nsr\res directory on the NMM client host.! IMPORTANT Do not edit the sa.ini file with a text editor to make changes in the array parameters. Using a text editor can corrupt the file, or compromise the password entries. Use the nsr_sa_ini.exe tool to edit the sa.ini file if you need to make changes after you create it. Sample CLARiiON sa.ini file A sample sa.ini file for a CLARiiON storage array would look similar to the following: [Storage_Array] Storage_Array_Count=2 Storage_Array_1=APM [APM ] Array_Type=CLARiiON Array_model=CX500 Array_user=sbarma Array_pass=**** Array_pass_confirm=**** Array_SPA= Array_SPB= Sample Symmetrix sa.ini file A sample sa.ini file for a Symmetrix storage array would look similar to the following: 270

271 Snapshot Management [Storage_Array] Storage_Array_Count=1 Storage_Array_1= [ ] Array_type=Symmetrix Array_sid=197 Array_Model=DMX-800 System rollback may fail with CLARiiON if the configuration information is not current If a CLARiiON array is migrated, or the information in the CLARiiON configuration is not up to date, rollback may fail. If there is more than one entry in the CLARiiON clarcnfg file, Replication Manager only uses the first entry. If the clarcnfg file is not current, the first entry may be pointing to a CLARiiON that is no longer connected to the system. Edit the clarcnfg file so that there is only entry, pointing to the current CLARiiON you want to use. Performing a rollback recovery Before performing a rollback recovery, ensure that the rollback requirements have been met. Rollback recovery requirements on page 269 provides more information about these requirements. To perform a rollback recovery: 1. Open the NMM client and select the NetWorker server on which the NetWorker client was configured for backup. 2. In the left pane, select Snapshot Management. 3. If you are performing a rollback for EMC Symmetrix configurations that use RAID5 Business Continuance Volumes (BCVs), perform the following steps: a. Delete all snapshots for the Standard EMC Disk (STD), except for the snapshot to be rolled back. For information about deleting snapshots, see Delete a snapshot on page 273. 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. Note: To prevent the loss of data from a snapshot that is to be deleted, perform a rollover of the snapshot before the deletion operation. Roll over a snapshot on page 268 provides more information about rolling over a snapshot. b. Use the SYMCLI commands to disassociate the BCVs and Virtual Devices (VDEVs) that are in the established state. c. If the snapshot used multiple STDs, perform the previous steps for each STD. 4. In the navigation tree, select the snapshot to be rolled back. 5. Right-click the selected snapshot and select Rollback. 6. In the left pane, select Monitor to view the progress of the rollback operation. Roll back a snapshot 271

272 Snapshot Management 7. When rollback processing has completed, reboot the host to complete the rollback operation. 8. If you performed a rollback on an Exchange or SQL database, remount the database. If you performed a rollback on a file system that had nested mount points, remount the nested mount points. 272

273 Snapshot Management Delete a snapshot Snapshot deletion policies are typically controlled automatically through snapshot policy settings on the NetWorker server. Chapter 2, Configuring a Scheduled Backup, provides more information about policy settings. However, you can delete a snapshot manually. For instance, if space must be made available immediately on the storage system, you can manually roll over and then delete snapshots.! CAUTION If a snapshot is deleted without the use of the NMM client user interface, the snapshot may still appear to be recoverable in the NMM client user interface. If such a snapshot is selected for recovery, the recover operation will fail. A snapshot could by in used by a user in another application. A snapshot could also be deleted by VSS or the storage subsystem if resources are exhausted due to high input/output rates on the volumes. To delete a snapshot: 1. Open the NMM client software and select the NetWorker server on which the NetWorker client was configured for backup. Opening the software and connecting to a NetWorker server on page 41 provides more information about opening NMM and connecting to a NetWorker server. 2. In the left pane, select Snapshot Management. 3. In the navigation tree, select the snapshot to be deleted. 4. Right-click the selected snapshot and select Delete. 5. In the left pane, select Monitor to view the progress of the delete operation. Delete a snapshot 273

274 Snapshot Management 274

275 15 NetWorker Client Management This chapter includes the following topics: Specifying ranges for service and connection ports Specifying a password NetWorker Client Management 275

276 NetWorker Client Management Specifying ranges for service and connection ports A service port is a listener port that provides services to NMM client hosts. The default range for service ports is 7937 to A connection port is used to contact a service, whether it is on a NetWorker server, storage node, or client. The default range for connection ports is To implement an enhanced security environment, it may be necessary to reduce the range of available ports. For more information about determining the size of the port range, refer to the EMC NetWorker Multiplatform Version Administration Guide, release or later. To reduce the range of available ports: 1. From the Options menu, select Configure Options. The Configure Options dialog box appears. 2. In the Service Ports attribute, enter the range of available ports. 3. In the Connection Ports attribute, enter the range of available ports. 4. Click OK. Note: If a firewall exists between the NetWorker client and any NetWorker servers, ensure that the firewall is configured to accept the port ranges entered in the Configure Options dialog box. 276

277 NetWorker Client Management Specifying a password The password is used to protect items that will be backed up with either PW1 password-protection, or PW2 encryption and password-protection. PW1 and PW2 protection is enabled on the NetWorker server with a local or global directive. For more information about PW1 and PW2 protection, refer to the EMC NetWorker Multiplatform Version Administration Guide, release or later.! CAUTION Changing the password does not change the password for files that have already been backed up. To recover PW1 or PW2 password-protected files, you must provide the password that was in effect at the time of the backup. To change the PW1 password: 1. From the Options menu, select Configure Options. The Configure Options dialog box is displayed. 2. In the Old password attribute, type the password that is currently in effect. 3. In the New password attribute, type the new password. 4. In the Confirm password attribute, retype the password. 5. Click OK. The new password will be applied to future scheduled backups for the NMM client where password-protection has been enabled with a global or local directive. Specifying a password 277

278 NetWorker Client Management 278

279 Invisible Body Tag 16 Troubleshooting This chapter includes the following topics: The troubleshooting process NMM client error messages NMM client issues Checking log files Manually stopping and starting services Other troubleshooting resources Troubleshooting 279

280 Troubleshooting The troubleshooting process NetWorker and the NetWorker Module for Microsoft Applications (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 following flowchart, Figure 55 on page 280 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 55 Troubleshooting process 280

281 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 Multiplatform Version Administration Guide, release or later, describes how to set up notifications. Finding errors When a problem occurs, a notification or message might be displayed, or appear in a log file. Table 45 on page 281 describes several ways that NetWorker server, NMM client, and other NetWorker features provide information about problems. Table 45 Notifications and errors Type notification of a NetWorker event Error message windows NetWorker Monitor window 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 Module for Microsoft Applications NetWorker 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. The troubleshooting process 281

282 Troubleshooting 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 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 clones or CLARiiON BCVs 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 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 Stop EMC VSS provider, Microsoft VSS services, and Replication Manager services. Then start those services. Also restart Exchange Information store if it was running and was backed up. 282

283 Troubleshooting 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 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. Solution Retype the words correctly or use the nsrsnap_vss_save -? command, as described in Displaying valid application data save sets on page 63, to display a listing of all valid application save sets on the NMM client. NMM client error messages 283

284 Troubleshooting NMM client issues The following section describes some common problems and possible solutions for NMM client. Check this section first when there appears to be a problem but there is no specific error message in monitoring or event logs. Savegroup failed in scheduled backup A notification appears in the NetWorker Monitor window 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 Multiplatform Version Administration Guide, Release or later, provides information about viewing group backup details. If there is not enough information in the savegroup details, check the NMM client log and other client-side logs. Checking log files on page 291 provides more information about the log names, locations, and details. 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. 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.1 Installation Guide provides information about how to extend the Security Configuration Wizard or manually configure Windows Firewall exceptions. Need to run utility to obtain Exchange Server information The utility nwexinfo.exe runs when NMM client is installed on an Exchange Server. This utility gathers the Exchange username, password, and domain, and then inserts this information in the registry. 284

285 Troubleshooting 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. 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\" and the snapshot of "E:\" would be mounted on the Proxy server as "G:\altpath\E\." 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." Task 5: Configure a Client resource on page 59 provides more information about creating a Client resource. 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, restart the PowerSnap service after restarting the NetWorker service, before running a PowerSnap operation. NMM client issues 285

286 Troubleshooting 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. 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, stop the EMC VSS provider, Volume Shadow Copy Service and Replication Manager services. Then start those services. 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 window. 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." 286

287 Troubleshooting 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 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." Follow the instructions for changing the setting in Exchange System Manager. Incremental backups within NetWorker Module for Exchange Client may be promoted to full backups 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." Incremental backups within NetWorker Module for SQL Server Client may be promoted to full backups 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. NMM client issues 287

288 Troubleshooting 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 When you run the command a message displays the directory 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 an 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 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, you can 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. 288

289 Troubleshooting Save sets may not appear in the recover window 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. Task 5: Configure a Client resource on page 59 provides more information about creating a Client resource. 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 specify the pass phrase used at the time of backup if it is not the default or current pass phrase.provide the passphrase when recovering AES encrypted files, using NMM Security recovery options. Security recovery options on page 85 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. NMM client issues 289

290 Troubleshooting Anti-virus programs block recovery When a recovery is attempted from a save set of all is attempted, anti-virus programs may block NMM recovery. Anti-virus programs are designed to protect their own program files and settings from external threats that may be attempting to disable the program. The anti-virus program cannot always distinguish the recovery from an attack. Solution Prior to recovery, disable the anti-virus programs protection properties. The name and location of the settings varies, but look for a setting like Prevent modification of <Anti-Virus Program Name> command agent files and settings. Clear or disable the setting. Check the anti-virus program s documentation or online help for information about finding and disabling this setting. To recover files to a system protected by an anti-virus program: 1. Disable the anti-virus program s setting for protecting its own files and settings. 2. Perform the recovery. 3. Reset the anti-virus program to protect its files and settings. 290

291 Troubleshooting 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 293 In addition, third party providers generate their own logs in place of the Solutions Enabler log (hwprov.log). For more information, check the third party documentation. NMM client Log file The NMM client log file is named: nmm.raw Location Applogs folder. For example, C:\Program Files\Legato\nsr\applogs\. Description Both save and recover CLIs write to this file. The log file is cumulative, so it is appended with each run. The logging level of the 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. Checking log files 291

292 Troubleshooting 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\. 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\RMSERVICE\RMAgentPS\Client\4.0.0\CC_DEBUG_LEVEL. The default value is 2, but can be changed to 3. To change the value, stop RM Services, change the value in the registry, and then 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. 292

293 Troubleshooting 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 Multiplatform Version Administration Guide, or later. Checking log files 293

294 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 Multiplatform Version Administration Guide, or later, which provides more information about starting and stopping services on Windows and UNIX hosts, Console server, NetWorker Server, Client, or Storage Node. Table 46 on page 294 lists the services for NetWorker, PowerSnap, and Replication Manager that are active on the system. Table 46 Services 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. RMServer.exe Replication Manager Service Provides Replication Manager Server services for executing workflow for creating VSS-based snapshots. 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. 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. winworkr NetWorker Process Provides graphical user interface for NetWorker software. 294

295 Troubleshooting Other troubleshooting resources Does the problem appear to be on the NetWorker server or on a NetWorker client? 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 Multiplatform Version Installation Guide, release or later EMC NetWorker Multiplatform Version Administration Guide, release or later EMC NetWorker Multiplatform Version Error Message Guide, release or later EMC NetWorker PowerSnap Module Installation and Administration Guide EMC Replication Manager Administrator s Guide Other troubleshooting resources 295

296 Troubleshooting 296

297 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) archive archive volume auto media management autochanger autochanger sharing See manual backup. A 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. A 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. Backing up directories or files to an archive volume to free disk space. Archived data is not recyclable. A volume used to store archive data. Archived data cannot be stored on a backup volume or a clone volume. A feature that enables the storage device to automatically label, mount, and overwrite an unlabeled or recyclable volume. See library. See library sharing. B backup backup components metadata document backup group backup level backup volume An operation that saves data to a volume. See also conventional backup and snapshot. See metadata document. See group. See level. A volume used to store backup data. Backup data cannot be stored on an archive volume or a clone volume. See also volume. 297

298 Glossary bootstrap browse policy A 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 a server index. A 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 command line component components metadata document consistent See library. A computer, workstation, or fileserver whose data can be backed up and recovered. A 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. A 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. A 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. An 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. A 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. The line on a display screen, also known as a command prompt or shell prompt, where you type software commands. 1. A 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. See metadata document. The state of a data set that is fully and immediately available to an application view. 298

299 Glossary Console server conventional backup The 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. D data retention policy datawheel datazone DDS (Dynamic Drive Sharing) device DFS (Distributed File System) directed recovery directive disk subsystem DM (data mover) domain controller See retention policy. See library. A group of hosts administered by a NetWorker server. A feature that allows NetWorker software to recognize shared drives. 1. A 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. A Microsoft Windows add-on that allows you to create a logical directory of shared directories that span multiple machines across a network. A method of recovery that recovers data that originated on one client computer and re-creates it on another client computer. An 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. An integrated collection of storage controllers and/or HBAs, disks, and any required control software that provides storage services to one or more hosts, such as CLARiiON arrays. The client system or application, such as NetWorker, that moves the data during a backup, recovery, or snapshot operation. See also proxy client. A computer that stores directory data and manages user interactions within a domain, including logon, authentication, directory searches, and access to shared resources. F file index file system full backup 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. See level. 299

300 Glossary G group A client or group of client computers that are configured to back up files at a designated time of day. H high-available system host ID A system of multiple computers configured as cluster nodes on a network that ensures 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. A serial number that uniquely identifies a host computer. I inactivity timeout incremental backup instant backup instant restore The number of minutes to wait before a client is considered to be unavailable for backup. A backup level in which only files that have changed since the last backup are backed up. See also level. The 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. The 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 level library library sharing local cluster client See library. An electronic header on a volume used for identification by NetWorker or other data mover application. The use of special-case Microsoft APIs to back up and recover operating system components, services, and applications. A 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. A hardware device containing 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. A 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. 300

301 Glossary locale settings LUN (logical unit) LUN address Settings that specify the input and output formats for date and time, based on local language conventions. A logical unit of storage on a CLARiiON system. This refers to a device or set of devices, usually in a CLARiiON storage array. The 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 A 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. The physical storage medium, such as magnetic tape, optical disk, or file system to which backup data is written. A 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) NetWorker administrator NetWorker client NetWorker Console server NetWorker Management Console NetWorker server A TCP/IP-based protocol that specifies how heterogeneous network components communicate for the purposes of backup and recovery. A 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. 301

302 Glossary NetWorker storage node nonclone pool nonpersistent snapshot See storage node. Pools that contain data that has not been cloned. A 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 operator The databases located on the NetWorker server that contain all the information pertaining to the client backups (client file index) and backup volumes (media database). The 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) policy pool PowerSnap provider proxy client A 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. A snapshot that is retained on disk. A persistent snapshot may or may not be rolled over to tape. A fully usable copy of a defined collection of data, such as a consistent filesystem, 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. A 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. A 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. A software component defined by Microsoft VSS, that plugs into the VSS environment. A provider, usually produced by a hardware vendor, enables a storage device to create and manage snapshots. A 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 A 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. 302

303 Glossary R recover Registry requestor replica resource restore retention policy retrieve rollback restore rollover root To recover files from a backup volume to a client disk. A Microsoft Windows database that centralizes all Windows settings and provides security and control over system, security, and user account settings. An interface with the Microsoft VSS infrastructure to initiate the creation and destruction of shadow copy. NetWorker software is a requestor. See shadow copy. A 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. The process of retrieving individual datafiles from backup storage and copying the files to disk. A 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. The 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. The 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. The highest level of the system directory structure. S save set SSID (save set ID) save set recover save set status server index serverless backup A group of files or a file system from a single client computer, which is backed up on storage media. An internal identification number assigned to a save set. To recover data by specifying save sets rather than by browsing and selecting files or directories. A 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. A 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. 303

304 Glossary service port shadow copy shadow copy set shadow copy technology skip snap clone snap ID snap set snapshot snapshot expiration policy snapshot policy snapshot retention policy staging stand-alone device storage device storage node A port used to listen for backup and recover requests from clients through a firewall. A temporary, point-in-time copy of a volume created using VSS technology. See also Volume Shadow Copy Service (VSS). A 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 saveset at recover time. A 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. A backup level in which designated files are not backed up. An 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. The group of files, volumes, or filesystems 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. A point-in-time, read-only copy of data created during an instant backup. The policy that determines how long snapshots are retained before their storage space is made available for the creation of a new snapshot. A 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. The 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. A storage device that contains a single drive for backing up data. Stand-alone devices cannot store or automatically load backup volumes. See device. A storage device physically attached to a computer other than the NetWorker server, whose backup operations are administered from the controlling NetWorker server. V volume volume ID 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. An internal identification that NetWorker software assigns to a backup volume. 304

305 Glossary volume mount point volume name volume pool Volume Shadow Copy Service (VSS) VSS VSS component A 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. The name assigned to a backup volume when it is labeled. See also label. See pool. A Microsoft technology that creates a point-in-time shadow copy of a disk volume. NetWorker software backs up data from the shadow copy. This allows applications to continue to write data during the backup operation, and ensures that open files are not omitted. See Volume Shadow Copy Service (VSS). A subordinate unit of a writer. W writer A database, system service, or application code that provides metadata document information about what to back up and how to handle VSS components and applications during backup and recovery operations. A Writer provides information to requestors to ensure that application data is consistent, application files are closed and ready for a slight pause to make a Shadow Copy. 305

306 Glossary 306

307 Index A Active Directory (AD) backups for disaster recovery 264 backups for object selection granularity 265 disaster backup and recovery 36 granular backup and recovery 36 log files 293 Active Directory Lightweight Directory Services (AD LDS) 78, 262 active node 192 AD LDS backup and recovery 262 AD recovery all objects for a disaster recovery 256 granular recovery 258 individual objects and attributes 258 null value restriction 260 restrictions for 259 schema object restriction 260 system-only attribute restriction 259 tombstone restriction 259 ADAM authoritative restore 79 nonauthoritative restore 79 recovery options 78 AES encryption conflict with EFS encryption 85 All save set considerations for 60 alternate mount path for proxy client 182 application data save sets considerations for 48, 108 considerations for SharePoint application information attribute applications 65 Cluster Writer 245 DPM 208 Exchange 182 Hyper-V 233 SharePoint 2003 SQL data 141 SharePoint SQL 102 Application Specific Module (ASM) pass phrase 85 application writers DPM 204 Exchange 179 Hyper-V 229, 231 SharePoint SharePoint SQL 99 supported 29 authoritative restore ADAM 79 Cluster Writer 247 DFS 80, 81 FRS 82 NTDS 84 B backup Active Directory 265 LCR 177 SharePoint backup and recovery Hyper-V parent partition

308 Index backup client resource configuring 59 configuring DPM 210 configuring Hyper-V 236 configuring multiple 59, 210, 236 backup command attribute applications 61 DPM 211 Exchange 189 Hyper-V 237 SharePoint , 126, 127 SharePoint 2007 granular 164 backup groups configuring 57 backup pool creating for snapshots 50 backup roadmap Hyper-V 226 backup save sets applications 61 DPM 206 Exchange 180 Hyper-V 232, 236 SharePoint 2003 SQL data 138 SharePoint SharePoint 2007 disaster recovery 134 specifying 60, 188, 210 SQL 100 backup schedule configuring 56 backup time selecting for recovery 43 best practices SQL backup and recovery 108 best practices for backup and recovery Exchange 185 Hyper-V child partition 230 Hyper-V parent partition 230 SharePoint SQL in SharePoint browse time selecting for recovery 43 C child partition best practices for backup and recovery 230 Hyper-V configurations 226 child partitions 225 CLARiiON E_VETO_PROVIDER error message 282 error message 282 provider overview 30 replica takes long time 286 client resource configuring for backup 59 configuring for DPM backup 210 configuring for Exchange backup 187 configuring for Hyper-V backup 236 configuring for SharePoint 2003 backup 142 configuring for SharePoint 2007 backup 123 configuring for SQL backup 104 configuring multiple 59, 210, 236 configuring when in a cluster 69, 246 Cluster Continuous Replication (CCR) Exchange backup 177 cluster server entering physical hostname of 61, 211 scheduling backups for 69, 246 Cluster tab 247 Cluster Writer recovery authoritative restore 247 for Windows Server nonauthoritative restore 247 options 76 common provider See EMC VSS Provider 27 component system writers supported 29 configuration database backup 116 SharePoint SharePoint 2007 database backup 126 SharePoint 2007 recovery 129 connection port range specifying 276 connection to NetWorker server 41 consistency checker utility

309 Index conventional recovery overview 34 conventional snapshot policy example 55 D deleting snapshots 273 device configuring for rollover backup 50 DFS recovery options 79 directed recovery DPM-protected server 217 NMM Client 92 directory services restore mode booting in for FRS recovery 89 booting in for NTDS recovery 89 disaster recovery backup 35 DPM 220 Hyper-V 240 planning for active directory 264 recovery for active directory 256 support in NMM 36 DPM configuring client resource for backup 210 directed recovery 217 disaster backup and recovery 36 disaster recovery options 222 granular backup and recovery 36 granular recovery 214 URL encoding for save sets 207 DPM disaster recovery individual objects and attributes 220 E EFS encryption conflict with AES encryption 85 notification NetWorker events 281 EMC VSS Provider overview 27 encryption recovering backup data 72 errors E_VETO_PROVIDER 282 E_VOLUME_NOT_SUPPORTED 282 error code 0x800423f3 282 Microsoft I/O write 286 NMM client 282 replica in a CLARiiON array 286 VSS CLIENT... Invalid Writer Selection 283 VSS_E_VOLUME_NOT_SUPPORTED_BY_P ROVIDER 285 VSS_E_WRITERERROR_RETRYABLE 282 with Exchange 283 Event viewer 281 events notification 284 exceptions Windows Firewall 284 Exchange client resource configuration 187 consistency checker utility 68 disaster backup and recovery 36 errors 283 granular backup and recovery 36 point-in-time recovery 193 proxy client 183 recover to Recovery Storage Group (RSG) 196 roll-forward recovery 192 URL encoding for save sets 181 Exchange backup CCR environment 177 LCR environment 177 Exchange recovery database can be overwritten selection 190 options for 190 Remote Storage Group (RSG) 196 exclusion representation of save sets 38 F failover from the passive node 192 file system disaster backup and recovery 36 granular backup and recovery 36 recovery options 74, 76 FRS recovery booting in directory services restore mode 89 consideration for 73 options 82 full backup level consideration for

310 Index G granular backup SharePoint , 164 granular backup and recovery support in NMM 36 granular recovery Active Directory 258 backup 35 DPM objects 214 SharePoint groups configuring for backup 57 guest. See also child partition H hardware providers 30 host Hyper-V 226 Host. See also Hyper-V parent partition Hyper-V backing up a virtual machine with multiple volumes 234 backup roadmap 226 components used for backup and recovery 231 configuring backups 235 configuring client resource for backup 236 disaster backup and recovery 36 disaster recovery 240 granular backup and recovery 36, 231 host 226 recovery 238 save sets 231 VSS writer 231 Hyper-V best practices child partition backup and recovery 230 parent partition backup and recovery 230 Hyper-V child partition configurations 226 Hyper-V parent partition backup and recovery types 225 Hyper-V storage and backup options 226 I incremental backup level consideration for 56 instant backup overview 32 instant recovery overview 34 instant snapshot policy example 55 interface overview 37 issues NMM client 284 items searching for recovery 42 L label creating for pool 51 LCR 177 Exchange backup 177 LCR backup support 177 level 1 to 9 backups consideration for 56 level for backup considerations for 56 Local Continuous Replication (LCR) 177 log files 281 Active Directory 293 NetWorker Server 293, 294 NMM client 291 PowerSnap client 291 Replication Manager 292 Solutions Enabler 292 troubleshooting with 291 M marking items for recovery 42 Microsoft Cluster Service 244 Microsoft VSS software provider overview 27 Microsoft Windows Server , 62, 76, 78, 204, 207, 244, 262 Microsoft Windows Server 2008 support 76 monitoring a recovery 89, 253 mount path for proxy client

311 Index MSCS 244 MSDE turning writer on or off in registry 207 multiple client resources for backup 59, 210, 236 N NetWorker events notification 281 NetWorker Monitor window 281 Networker recovery options 74, 76 NetWorker Server log files 293, 294 NetWorker server connecting to 41 NMM Client directed recovery 92 NMM client error messages 282 issues 284 log files 291 nonauthoritative restore ADAM 79 Cluster Writer 247 DFS 80, 81 FRS 82 NTDS 84 nonpersistent backup overview 32 notification NetWorker events 284 savegroup failed 284 notifications 281 types 281 NSR_ALT_PATH command 182 NSR_DATA_MOVER command 65 NSR_DM_PORT command 182 nsr_moss_save 160 nsr_sa_ini.exe 269 NTDS recovery booting in directory services restore mode 89 consideration for 73 options 83 O overview conventional recovery 34 Exchange proxy client 183 instant backup 32 instant recovery 34 interface 37 nonpersistent backup 32 persistent backup 32 provider 27 proxy client 32, 103 requestor 27 rollback recovery 34 rollover backup 32 serverless backup 32, 103, 183 software provider 27 VSS writers 28 overwrite prevention error Exchange database recovery 286 P parent partition best practices for backup and recovery 230 pass phrase recovering AES encrypted data 85 passive node 192, 193 password changing 277 consideration for changing 277 restriction for active directory recovery 260 specifying for backup 277 password-protected recovering backup data 72 persistent backup overview 32 physical server Hyper-V 226 policies for snapshots 53 pool creating for snapshots 50 label for 51 ports Exchange proxy client communications 182 service and connection port ranges 276 PowerSnap client log files

312 Index provider overview 27 proxy client configuring 67 mount path 182 overview 32, 103 port number for communicating 182 requirements for 67 SharePoint serverless backup 120 specifying hostname of 65 SQL serverless backup 102 SQL serverless backup in SharePoint R recover.exe 72 recovery active directory 255 ADAM options 78 browse time selection 43 Cluster options 76 Cluster Writer options 76 default method, choosing 74 DFS options 79 encrypted backup data 72 Exchange options 190 FRS options 82 Hyper-V 238 marking items 42 NTDS options 83 password-protected backup data 72 performing for system data 73 searching for items 42 selecting a version 43 SharePoint 2007 granular 157 snapshots that have not been rolled over 86 viewing progress for 89, 253 volumes required for 44 recovery error Exchange database 286 Recovery Storage Group (RSG) Exchange 196 remote access attribute virtual cluster server specification 61, 211 replica error message 282 takes long time in CLARiiON environment 286 Replication Manager error message 282 log files 292 requestor overview 27 resource for backup configuring 59 configuring multiple 59, 210, 236 rollback recovery limitations of 269 overview 34 performing 269, 271 requirements for 269 rollover backup device for 50 overview 32 performing 268 S sa.ini 269, 270 safe mode, booting in 89 save sets applications 61 DPM 206 Exchange 180, 188 exclusion representation 38 Hyper-V 231, 232 SharePoint SharePoint 2003 SQL data 138 SharePoint SharePoint 2007 granular backup 160 specifying for backup 60, 210 specifying for Hyper-V backup 236 SQL 100 SQL databases in SharePoint URL encoding 63 savegroup failed notification 284 Search Index backup in SharePoint searching for a recovery item 42 Security Configuration Wizard 284 selecting items for recovery

313 Index server connecting to NetWorker 41 serverless backup 30, 102, 141 Exchange 183 overview 32 proxy client requirement 67 SharePoint 2007 backup 120 SQL 103 service port range specifying 276 services 294 SharePoint 2003 application save sets 146 backup and recovery process 148 backup and recovery support 137 backups 142 best practices for backup and recovery 146 Client resource 142 configuring Client resource 142 recovery 144 save sets 139 SQL 2005 database recovery 144 SQL Server 2000 recovery 144 SharePoint 2007 configuration database backup 116 configuration database recovery 129 disaster backup and recovery 36 granular backup and recovery 36 granular backup save sets 160 granular backup storage requirements 159 granular recovery 166 granular recovery prerecovery options 171 save sets for granular backup 164 Search Index 116 serverless backup 120 specifying save sets for backup 123, 125, 126 URL encoding 119 URL encoding for save sets 119 SharePoint 2007 configuration database 113 snapshot policies configuring 53 examples of 55 snapshots deleting 273 pool for 50 recovering when not rolled over 86 rollback operation 269 rollover operation 268 software provider overview 27 Solutions Enabler log files 292 SQL database recovery for SharePoint disaster backup and recovery 36 serverless backup 102 serverless backup in SharePoint URL encoding 101 URL encoding for SharePoint SQL proxy client 102 SQL proxy client in SharePoint 2003 backup 141 SQL Server configure client resource 104 storage and backup options Hyper-V 226 storage array creating descriptor 270 descriptor file 269 Exchange rollback requirements 194 storage requirements SharePoint 2007 granular backup 159 Symmetrix provider overview 30 syntax application save sets 61 DPM save sets 206 Exchange save sets 180 Hyper-V save sets 232 SharePoint 2003 SQL data 138 SharePoint SQL 100 system component writers supported 29 system recovery performing 73 T time of backup selecting for recovery 43 troubleshooting checking other documents

314 Index U URL encoding DPM save sets 207 Exchange save sets 181 save sets 63 SharePoint SharePoint 2007 save sets 119 SQL save sets 101 SQL save sets for SharePoint SQL save sets in SharePoint 2003 backup 139 V version selecting for recovery 43 virtual cluster server entering physical hostname of 61, 211 scheduling backups for 69, 246 Volume Shadow Copy Service (VSS) writers 28 volumes required for recovery 44 VSS CLIENT... Invalid Writer Selection 283 VSS_E_VOLUME_NOT_SUPPORTED_BY_PRO VIDER 285 VSS_E_WRITERERROR_RETRYABLE 282 W Windows Encrypting File System (EFS) 85 Windows Firewall NetWorker blocked by 284 Windows Server , 62, 76, 78, 204, 207, 262 Windows Server 2008 Cluster Writer nonauthoritative restore 76 Windows Server Failover Clustering (WSFC) 244 Windows SharePoint Services 2.0 see SharePoint Windows SharePoint Services 3.0 see SharePoint Windows system component writers supported