NetWorker Module For Microsoft Applications 2.3 Application Guide

EMC NetWorker
Module for Microsoft Applications

Release 2.3
Application Guide
P/N 300-011-105
REV A04
EMC Corporation
Corporate Headquarters:
Hopkinton, MA 01748-9103
1-508-435-1000
www.EMC.com
Copyright 2007-2010 EMC Corporation. All rights reserved.

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

Overview..................................................................................................................
SQL Server versions supported by NMM.....................................................
Types of supported backup and recovery ....................................................
Writer for SQL data backup and recovery....................................................
Performing SQL Server backups ..........................................................................
SQL Server application information variable settings ................................
Displaying valid SQL data save sets..............................................................
URL encoding for save sets.............................................................................
Specifying save sets for SQL data ..................................................................
Configuring SQL Server backups...................................................................
Performing SQL Server recovery..........................................................................
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2
data in a non-clustered environment from the SQLServerWriter
save set ...............................................................................................................
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2
Express databases from the SYSTEM COMPONENTS save set................
Recovering virtual SQL Server for SQL clusters..........................................
Performing SQL Server directed recovery ..........................................................
Steps for SQL Server directed recovery.........................................................
Selecting the NetWorker server......................................................................
Selecting a source client ...................................................................................
Selecting the desired SQL databases for directed recovery .......................
Recovering to default recover path................................................................
Recovering to a user-defined path .................................................................
Examples of log messages in NMM log file and Monitor page.................
Attaching recovered SQL databases ..............................................................
Performing SQL Server disaster recovery...........................................................
SQL Server (stand-alone) disaster recovery on Windows Server 2008
or 2008 R2 with NetWorker 7.6 SP2 and NMM 2.3 .....................................
or 2008 R2 with NetWorker 7.6 SP1 or earlier, and NMM 2.3 ...................
with NetWorker 7.6 SP1 or earlier, and NMM 2.3.......................................
Clustered SQL Server disaster recovery on Windows 2008 or
Windows 2008 R2 with NetWorker 7.6 SP2 and NMM 2.3 ........................
20
20
21
22
22
22
23
23
24
26
27
27
28
28
28
29
30
30
32
32
33
34
35
36
36
37
37
37
Contents
Clustered SQL Server disaster recovery on Windows Server 2008,

2008 R2, or 2003 with NetWorker 7.6 SP1 or earlier, and NMM 2.3.......... 38
Best practices............................................................................................................ 39
Chapter 2
Microsoft Active Directory Backup and Recovery

Overview .................................................................................................................. 42
Types of supported backup and recovery..................................................... 42
Active Directory objects for granular backup and recovery....................... 43
Performing an Active Directory or ADAM full backup.................................... 43
Configure a client resource for Active Directory or ADAM
full backup ......................................................................................................... 43
Performing Active Directory or ADAM granular backup ................................ 45
Considerations for granular backup .............................................................. 45
Configuring Active Directory or ADAM granular backups ...................... 46
Performing Active Directory database recovery ................................................ 52
Performing an Active Directory granular recovery ........................................... 53
Recovery restrictions for Active Directory.................................................... 53
Recovering an Active Directory object or object attribute .......................... 55
Selecting Active Directory object attributes .................................................. 56
Performing Active Directory disaster recovery .................................................. 57
Chapter 3
Microsoft Data Protection Manager Server Backup and Recovery

Overview .................................................................................................................. 60
Types of DPM data for backup ....................................................................... 61
Writers for DPM database backup and recovery ......................................... 61
NMM and DPM backup and recovery scenario........................................... 62
DPM directed granular recovery scenario .................................................... 63
Performing DPM Server backups ......................................................................... 65
DPM application information variable settings ........................................... 65
Displaying valid DPM data save sets ............................................................ 66
URL encoding for save sets ............................................................................. 66
Specifying DPM save sets for application data ............................................ 66
Configuring DPM backups.............................................................................. 67
Performing a DPM Server recovery ..................................................................... 69
Performing DPM granular recovery..................................................................... 71
Reviewing settings before starting recovery................................................. 71
Recovering a folder or file from a DPM replica............................................ 71
Performing a granular directed recovery to a DPM-protected server............. 73
Performing DPM disaster recovery ...................................................................... 74
Chapter 4
Microsoft Hyper-V Server Backup and Recovery

Overview .................................................................................................................. 76
Operating system versions supported by NMM client ............................... 76
Integration Components version .................................................................... 77
Hyper-V parent partitions, child partitions, and applications within
child partitions................................................................................................... 77
Hyper-V configuration..................................................................................... 78
Hyper-V storage configurations supported by NMM................................. 79
Hyper-V configuration requirements for backing up a child partition
that contains multiple volumes....................................................................... 82
Performing Hyper-V backups ............................................................................... 82
Contents
Hyper-V application information variable settings ....................................

Specifying Hyper-V save sets for application data......................................
Displaying valid Hyper-V save sets ..............................................................
NMM support for proxy backup of Hyper-V ..............................................
Preparing a child partition for backup ..........................................................
Configuring Hyper-V backups .......................................................................
Configuring a Hyper-V client resource.........................................................
Performing Hyper-V recovery ..............................................................................
Turning the child partition offline for recovery...........................................
Hosting the recovered virtual systems..........................................................
Specifying the destinations for the Hyper-V configuration files and
virtual system....................................................................................................
Selecting Hyper-V recovery options..............................................................
Selecting the destination of Hyper-V recovery...................................................
Performing Hyper-V recovery to the original machine and location .......
Performing directed Hyper-V recovery to a different machine or
location ...............................................................................................................
Performing Hyper-V parent partition disaster recovery .................................
Best practices ...........................................................................................................
Hyper-V parent partition backup and recovery ..........................................
Hyper-V child partition applications backup and recovery .....................
Restrictions for backup and recovery of Hyper-V child partitions in a
Windows 2008 and 2008 R2 failover cluster ........................................................
Chapter 5
82
83
83
84
84
85
86
88
88
88
89
89
90
90
91
93
95
95
96
97
Microsoft Exchange Server Backup and Recovery

Overview................................................................................................................
Exchange Server versions supported by NMM client ..............................
NMM and Exchange Server support for I18N ...........................................
Microsoft Exchange Server 2007 MAPI client and Collaboration
Data Objects support......................................................................................
Types of supported backup ..........................................................................
Backup levels...................................................................................................
Types of supported recovery ........................................................................
Compatibility with previous Exchange Server backups ..........................
Creation of shadow copy and snapshot process in an Exchange
Server production ...........................................................................................
Configuring snapshots...................................................................................
LAN-based Exchange Server configuration with a storage area
network and a proxy client ...........................................................................
Exchange backup scenarios...........................................................................
Exchange recovery scenarios ........................................................................
Writers for Exchange 2003 and 2007 backup and recovery......................
Commands and attributes for Exchange backup and recovery ..............
Configuring dedicated storage node for Exchange 2007 CCR
environment ....................................................................................................
Performing Exchange Server backups...............................................................
Exchange 2003 and 2007 application information variable settings .......
Specifying Exchange 2003 and 2007 save sets for application data ........
Displaying valid Exchange data save sets ..................................................
URL encoding for Exchange save sets.........................................................
Setting consistency check parameters for threading and throttling .......
Configuring Exchange Server backups .......................................................
Performing Exchange Server recovery ..............................................................
Exchange recovery requirements .................................................................
100
101
101
101
101
102
102
103
103
104
105
107
112
114
114
114
115
115
117
118
118
119
119
132
132
Contents
Exchange recovery options............................................................................ 133

Configuring Exchange recovery ................................................................... 134
Selecting a storage group restore destination ................................................... 149
Performing Exchange Server 2007 directed recovery ...................................... 150
Performing a directed recovery .................................................................... 151
Performing Exchange Server 2007 disaster recovery....................................... 152
Performing Exchange Server 2007 disaster recovery on Windows
Server 2008 or 2008 R2 with NetWorker version 7.6 SP2 .......................... 153
Performing Exchange Server 2007 disaster recovery on Windows 2008
or 2008 R2 with NetWorker version 7.6 SP1 or earlier .............................. 153
Performing a quick recovery of a deleted mailbox in Exchange 2007........... 158
Best practices.......................................................................................................... 158
Exchange recovery limitations ...................................................................... 159
Chapter 6
Microsoft Exchange Server 2010 Backup and Recovery

Overview ................................................................................................................ 162
Supported operating systems........................................................................ 162
Types of backup and recovery ...................................................................... 163
Exchange 2010 VSS writers............................................................................ 163
LAN-based Exchange Server configuration with a storage area
network and a proxy client............................................................................ 164
Backup initiated transaction log file truncation ......................................... 164
Microsoft Exchange Server 2010 MAPI client and Collaboration
Data Objects version 1.2.1 for granular recovery in Exchange 2010........ 164
Performing Exchange 2010 backups................................................................... 164
Backup options ................................................................................................ 165
Specifying Exchange 2010 application data save sets................................ 165
Displaying save set syntax............................................................................. 166
URL encoding for SharePoint save sets ....................................................... 166
Exchange 2010 application information variable settings......................... 167
Configuring persistent and non-persistent snapshots............................... 168
Considerations for backing up Exchange 2010 in non-DAG and DAG
environment..................................................................................................... 169
Exchange 2010 incremental backup promoted to full backup ................. 169
Configuring Exchange Server 2010 backups............................................... 170
Configuring Avamar deduplication backups in a DAG environment ... 172
Verifying backups ........................................................................................... 173
Performing Exchange Server 2010 recovery...................................................... 173
Performing full recovery................................................................................ 173
Performing advanced recovery..................................................................... 173
Performing granular recovery of Mailbox, folder, or e-mail .................... 178
Performing a quick recovery of a deleted Mailbox in Exchange 2010........... 179
Microsoft Exchange Server 2010 disaster recovery .......................................... 179
Chapter 7
Microsoft SharePoint Server 2003 Backup and Recovery

Overview ................................................................................................................ 182
Microsoft SharePoint Portal Server 2003 and Windows
SharePoint Services 2.0................................................................................... 182
Types of supported backup ........................................................................... 182
Writer required for SharePoint Server 2003 backup .................................. 182
Performing SharePoint Server 2003 backups .................................................... 183
Performing SharePoint Server 2003 recovery ................................................... 183
Example of SharePoint Server 2003 backup and recovery process................ 184
Contents
Creating a new SharePoint portal with three new databases .................. 184
Viewing the location and hierarchy of databases in the SQL Enterprise
Manager GUI................................................................................................... 185
Configuring and performing a backup of the new databases
with NMM save sets....................................................................................... 185
Verifying the backup in NMM UI................................................................ 185
Deleting the new databases........................................................................... 186
Performing NMM recovery .......................................................................... 186
Verifying database recovery through the SQL Enterprise Manager ...... 186
Recovering the portal site through SharePoint Portal Server Central
Administration................................................................................................ 187
Verifying the recovery of the portal site in SharePoint Server Central
Administration................................................................................................ 190
Chapter 8

Overview................................................................................................................
NMM solutions for protecting a SharePoint Server 2007 farm................
Microsoft Office SharePoint Server 2007 and Windows SharePoint
Services 3.0.......................................................................................................
Types of SharePoint Server 2007 backup and recovery ............................
Backup and recovery levels ..........................................................................
Microsoft Office SharePoint 2007 farm configurations .............................
SharePoint Server 2007 writers.....................................................................
Performing SharePoint Server 2007 backups....................................................
SharePoint Server 2007 application information variable settings .........
Specifying SharePoint Server 2007 save sets for application data...........
Displaying valid SharePoint Server 2007 data save sets...........................
URL encoding for SharePoint save sets.......................................................
Configuring dedicated web front-end crawling ........................................
Configuring SharePoint Server 2007 backups............................................
Performing SharePoint Server 2007 farm hardware backups ........................
CLARiiON hardware provider ....................................................................
Symmetrix hardware provider .....................................................................
Performing SharePoint Server 2007 recovery ...................................................
Full recovery of a stand-alone SharePoint farm.........................................
Full recovery of a distributed SharePoint farm..........................................
Recovery of individual SharePoint Server content databases .................
Recovery of SharePoint Server 2010 search and content index ...............
Performing SharePoint Server 2007 disaster recovery ....................................
Performing SharePoint Server 2007 disaster recovery with
NetWorker 7.6 SP1 and earlier .....................................................................
Performing SharePoint Server 2007 disaster recovery with
NetWorker 7.6 SP2 or later............................................................................
Keeping backups and recoveries in sync ..........................................................
Best practices .........................................................................................................
Backing up SharePoint database by using NMM and NMSQL.....................
Chapter 9
192
192
194
194
194
195
199
200
200
201
201
202
202
202
207
208
209
210
210
210
212
212
213
213
215
215
216
217

Overview................................................................................................................
New features in Microsoft SharePoint Server 2010 ...................................
SharePoint Server 2010 support on Windows Server 2008 ......................
Types of SharePoint Server 2010 backup and recovery ............................
220
220
221
221
Contents
NMM and Microsoft Office SharePoint Server 2010 farm

configurations.................................................................................................. 221
SharePoint Server 2010 VSS writers ............................................................. 222
Performing SharePoint Server 2010 backups .................................................... 222
Specifying SharePoint Server 2010 application data save sets ................. 222
Displaying valid SharePoint Server 2010 data save sets ........................... 223
Performing SharePoint Server 2010 backup................................................ 224
Configuring client resources ......................................................................... 224
Performing SharePoint Server 2010 recovery ................................................... 225
Performing SharePoint Server 2010 full farm recovery............................. 225
Performing SharePoint Server 2010 web application recovery................ 226
Performing SharePoint Server 2010 individual content
database recovery............................................................................................ 226
Performing SharePoint Server 2010 search services recovery.................. 227
Performing SharePoint Server 2010 disaster recovery..................................... 227
Chapter 10
Windows Disaster Recovery with NetWorker 7.6 SP2 and NMM

Overview ................................................................................................................ 230
Changes in NetWorker 7.6 SP2 client functionality after NMM 2.3
installation ............................................................................................................... 231
uninstallation .......................................................................................................... 232
Performing Windows Disaster Recovery backup and recovery for
Microsoft applications ........................................................................................... 232
Performing a Windows DR backup ............................................................. 232
Performing a Windows DR recovery ........................................................... 233
Chapter 11
Troubleshooting
About the troubleshooting process..................................................................... 236
Setting up notifications .................................................................................. 237
Finding errors .................................................................................................. 237
NMM Config Checker 1.1.0 ................................................................................. 237
NMM client error messages................................................................................. 238
E_VOLUME_NOT_SUPPORTED ................................................................ 238
E_VETO_PROVIDER ..................................................................................... 238
VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 ................ 239
VSS CLIENT... Invalid Writer Selection... for APPLICATIONS .............. 239
Savegroup failed in scheduled backup........................................................ 240
Insufficient permission to access mailbox. See documentation for
required permission settings. Server MBX is not capable of RSG
operations......................................................................................................... 240
77108:nsrsnap_vss_save ................................................................................. 241
NMM validation for NPS writer failed, unable to restore NPS VSS
writer data........................................................................................................ 241
NMM client issues................................................................................................. 242
In-progress backup fails................................................................................. 243
NetWorker is blocked by Windows firewall .............................................. 243
NMM backups might fail where a firewall exists between the
NetWorker server and client ......................................................................... 243
Running utility to obtain Exchange Server information ........................... 244
Requesting a snapshot for a volume on hardware that is not
transportable.................................................................................................... 245
Contents
The PowerSnap service must be restarted after the NetWorker service

is restarted .......................................................................................................
PowerSnap validation for recovery fails .....................................................
Snapshot backup may fail with writer errors.............................................
Microsoft I/O write error when taking a replica in a CLARiiON
array..................................................................................................................
Creating a replica takes a long time in CLARiiON environment............
Cannot recover Exchange database due to overwrite prevention
error ..................................................................................................................
Incremental backups may be promoted to full backups ..........................
Diagnosing VSS writer issues .......................................................................
Modifying the Exchange 2007 or 2010 COM+ components user
account or password ......................................................................................
Save sets may not appear in the Recover page ..........................................
Recovery of AES-encrypted files fails without pass phrase.....................
Unable to restore files encrypted with both Microsoft Windows
Encrypting File System and AES encryption .............................................
Antivirus programs block recovery.............................................................
Snapshot cannot include both hardware and software snapshot
volumes for clustered NMM VSS clients ....................................................
Cross-platform directed recovery is not supported on NMM.................
Recovery of large number of items fails if one or more items in
a folder is not selected....................................................................................
Multiple client resources with the same name cannot be combined
in the same group ...........................................................................................
Backup of two partitions of the same CLARiiON disk fails ....................
Connection to DPM service lost during DPM recovery ...........................
DPM replica backup is not correctly configured .......................................
Backup fails if Exchange Server in is renamed after it is created ............
In Exchange Server 2010, although backup completed successfully for
renamed database, recovery fails .................................................................
In Exchange 2010, nsrsnap_vss_save -? is listing old database name
instead of new database name after renamed mailbox database ............
Save sets from an Avamar AFTD for NMM backups show retention
set to 1/18/2038..............................................................................................
Microsoft updates required to fix the vds.exe crash errors during
retention on Windows Server 2008 and Windows Server 2003...............
Back up of SYSTEM COMPONENTS fails due to missing
System Writer..................................................................................................
Problems with RMExchangeInterface component ....................................
SharePoint backup fails when host and proxy client do not match........
NMM installation issues ......................................................................................
RMAgentPS fails to uninstall when uninstalling NMM...........................
Recovery failure after .NET 3.5 framework installation ...........................
SYSTEM COMPONENTS failure after McAfee uninstall ........................
If Exchange Server is installed after NMM, NMM reinstallation
is required to get Replication Manager Exchange Interface.....................
NMM uninstall and reinstall required to change the Replication
Manager port number....................................................................................
Checking log files..................................................................................................
NMM client......................................................................................................
PowerSnap client ............................................................................................
Replication Manager ......................................................................................
EMC VSS provider .........................................................................................
Active Directory..............................................................................................
245
246
246
246
247
247
247
248
249
249
249
250
250
250
251
251
251
252
252
252
253
253
253
254
254
254
255
256
256
256
258
258
258
258
259
259
259
260
260
261
Contents
NetWorker server............................................................................................ 261

Manually stopping and starting services........................................................... 261
Using nsr.dir to skip files for NMM backup and recovery ............................. 262
Troubleshooting issues during SQL databases directed recovery ................. 262
Name resolution .................................................................................................... 262
Other troubleshooting resources......................................................................... 263
Glossary
Index
10
Tables
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
Page
SQL variable settings for Application Information attribute ......................................... 22

Special characters and their URL-encoded values ........................................................... 24
SQL save set syntax............................................................................................................... 24
Tasks for scheduling a backup .......................................................................................... 26
Best practices and considerations ....................................................................................... 39
Tasks for Active Directory or ADAM granular backup .................................................. 46
System-only attributes that are not backed up ................................................................. 54
Retained attributes after object is deleted.......................................................................... 54
DPM application information variable settings ............................................................... 65
DPM Server 2007 save set syntax........................................................................................ 66
Tasks for scheduling a backup ............................................................................................ 67
Hyper-V child partition configurations ............................................................................. 80
Hyper-V application information variable settings ......................................................... 82
Hyper-V save set syntax....................................................................................................... 83
Backup tasks for Hyper-V.................................................................................................... 85
Exchange 2003 and 2007 backup levels............................................................................ 102
Writers used by NMM for Exchange Server backup and recovery............................. 114
Commands and attributes used by NMM for Exchange Server backup
and recovery
114
Exchange application information variable settings...................................................... 115
Exchange 2003 and 2007 save set names.......................................................................... 117
Tasks for configuring an Exchange Server backup ........................................................ 120
Different backup procedures for Exchange recovery .................................................... 122
Exchange 2010 VSS writers ................................................................................................ 163
Exchange 2010 save sets for application data ................................................................. 166
Exchange application information variable settings...................................................... 167
Considerations required for backup in non-DAG and DAG environment................ 169
Tasks for configuring an Exchange Server backup ........................................................ 170
Example: Minimum required save sets to be backed up .............................................. 199
List of supported SharePoint Server 2007 writers .......................................................... 199
SharePoint Server application information variable settings ....................................... 200
SharePoint Server save set syntax..................................................................................... 201
Tasks for SharePoint Server 2007 backups ...................................................................... 203
SharePoint Server backup list for disaster recovery ...................................................... 214
List of supported SharePoint Server 2010 VSS writers.................................................. 222
SharePoint Server 2010 save set syntax............................................................................ 223
Changes in NetWorker 7.6 SP2 client functionality after NMM 2.3 installation ....... 231
Supported and unsupported system recovery scenarios .............................................. 232
Notifications and errors ..................................................................................................... 237
Services and processes used in NMM client ................................................................... 261
11
Tables
12
Figures
Title
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
Page
Configuration Options dialog box...................................................................................... 31

Client menu............................................................................................................................ 31
APPLICATIONS > SqlServerWriter tree nodes................................................................ 32
System Recover Session Options ........................................................................................ 33
NMM protection of DPM..................................................................................................... 63
Directed recovery of FileServer1......................................................................................... 64
DPM disaster recovery options........................................................................................... 70
DPM recovery modes ........................................................................................................... 72
Recover submenu for DPM recovery ................................................................................. 72
DPM granular recovery available to file level .................................................................. 72
DPM granular recovery options ......................................................................................... 73
DPM database and replicas available as selectable items ............................................... 74
Windows Server 2008 or Windows Server 2008 R2 host with Hyper-V
child partitions
78
NMM backup of Hyper-V components ............................................................................. 79
Hyper-V storage options...................................................................................................... 80
Disaster recovery order for a Hyper-V Server .................................................................. 94
Snapshot process with Exchange production server and proxy client ....................... 106
Multiple server roles that coexist on a single computer................................................ 108
SCC architecture.................................................................................................................. 109
CCR core architecture......................................................................................................... 110
Exchange Recovery Options window with Conventional Restore option
selected
134
Available and unavailable storage groups...................................................................... 141
Restore To command on context menu ........................................................................... 142
RSG Configuration error message .................................................................................... 142
RSG Configuration correct message................................................................................. 142
Public folders cannot be recovered to an RSG ................................................................ 143
Selected and partially selected items................................................................................ 145
Recovered Items folders in user mailbox ........................................................................ 146
Select Storage Group Restore Destination dialog box ................................................... 149
Local client on the taskbar next to Client......................................................................... 151
Select Viewable Clients dialog box................................................................................... 152
Select Exchange 2010 database.......................................................................................... 174
Advanced Recovery dialog box ........................................................................................ 175
Manage RDB window ........................................................................................................ 175
Create_DB window............................................................................................................. 176
Exchange Recovery Summary........................................................................................... 177
Select Database window .................................................................................................... 177
Select Mailbox, folder or e-mail for recovery.................................................................. 179
13
Figures
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
14
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 page ............................................................
SharePoint Portal Server Central Administration, Manage Portal Sites
window
Portal creation and restore options ...................................................................................
Portal restore and database names ...................................................................................
Confirmation window to request creation of the portal site.........................................
Status window for portal recovery process .....................................................................
Operation Successful page displayed when portal recovery is complete...................
Recovered databases and SharePoint portal visible and available in
SharePoint
SharePoint Server 2007 stand-alone farm configuration ...............................................
SharePoint Server 2007 distributed farm configuration ................................................
Dialog box to recover remote components ......................................................................
Troubleshooting process.....................................................................................................
185
186
186
187
187
188
188
189
189
189
190
190
196
196
211
236
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 might not be supported by all versions of the software or
hardware currently in use. For the most up-to-date information on product features, refer to
your product release notes.
If a product does not function properly or does not function as described in this document,
please contact your EMC representative.
Note: This document was accurate as of the time of publication. However, as information is
added, new versions of this document may be released to the EMC Powerlink website
http://Powerlink.EMC.com. Check the Powerlink website to ensure that you are using the
latest version of this document.
Purpose
This guide contains information for backing up and recovering Microsoft

applications, such as the following by using EMC NetWorker Module for Microsoft
Applications:
Microsoft SQL
Microsoft Active Directory
Microsoft Data Protection Manager
Microsoft Hyper-V
Microsoft Exchange 2003
Microsoft SharePoint 2003
IMPORTANT
The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration
Guide supplements the backup and recovery procedures described in this guide
and must be referred to when performing application-specific tasks. Ensure to
download a copy of the EMC NetWorker Module for Microsoft Applications Release
2.3 Administration Guide from the EMC Powerlink website
http://Powerlink.EMC.com before using this guide.
15
Preface
Audience
This guide is part of the EMC NetWorker Module for Microsoft Applications
documentation set, and is intended for use by system administrators during the setup
and maintenance of the product.
Readers should be familiar with the following technologies used in backup and
recovery:
Related
documentation
Conventions used in
this document
EMC NetWorker software
EMC NetWorker snapshot management
Microsoft Volume Shadow Copy Service (VSS) technology
Storage subsystems, such as EMC CLARiiON or EMC Symmetrix, if used
The following EMC publications provide additional information:
EMC NetWorker Module for Microsoft Applications Release 2.3 Release Notes
EMC NetWorker Module for Microsoft Applications Release 2.3 Installation Guide
EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide
EMC NetWorker Module for Microsoft Applications and EMC CLARiiON

Implementing Proxy Node Backups 2.3 Technical Notes
EMC NetWorker Module for Microsoft Applications and EMC Symmetrix Implementing
Proxy Node Backups 2.3 Technical Notes
EMC NetWorker Licensing Guide
EMC Information Protection Software Compatibility Guide
EMC Solutions Enabler Symmetrix CLI Quick Reference
EMC Technical Advisory (ETA) esg121813
EMC Cloning and Recovery of Expired Save Sets for NetWorker Module for Microsoft
Applications Technical Note
EMC NetWorker Cloning Integration Guide
The NetWorker Procedure Generator
EMC NetWorker Release 7.6 Service Pack 1 documentation
EMC NetWorker Release 7.6 Service Pack 2 documentation
Note: EMC uses the following conventions for special notices:
Note: A note presents information that is important, but not hazard-related.
IMPORTANT
An important notice contains information essential to software or hardware
operation.
16
Preface
Typographical conventions
EMC uses the following type style conventions in this document.
Normal
Used in running (nonprocedural) text for:

Names of interface elements (such as names of windows, dialog boxes,
buttons, fields, and menus)
Names of resources, attributes, pools, Boolean expressions, buttons, DQL
statements, keywords, clauses, environment variables, functions, utilities
URLs, pathnames, filenames, directory names, computer names, filenames,
links, groups, service keys, file systems, notifications
Bold
Used in running (nonprocedural) text for:

Names of commands, daemons, options, programs, processes, services,
applications, utilities, kernels, notifications, system calls, man pages
Used in procedures for:
Names of interface elements (such as names of windows, dialog boxes,
buttons, fields, and menus)
What user specifically selects, clicks, presses, or types
Where to get help
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
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:
http://Powerlink.EMC.com
Technical support For technical support, go to Powerlink and select Support. On

the Support page, you will see several options, including one for making a service
request. Note that to open a service request, you must have a valid support
agreement. Please contact your EMC sales representative for details about obtaining a
valid support agreement or with questions about your account.
Your comments
Your suggestions will help us continue to improve the accuracy, organization, and
overall quality of the user publications. Please send your opinion of this document to:
BSGdocumentation@emc.com
17
Preface
If you have issues, comments, or questions about specific information or procedures,

please include the title and, if available, the part number, the revision (for example,
A01), the page numbers, and any other details that will help us locate the subject that
you are addressing.
18
1
Microsoft SQL Server
Backup and Recovery
This chapter includes the following topics:
Overview ........................................................................................................................
Performing SQL Server backups.................................................................................
Performing SQL Server recovery ................................................................................
Performing SQL Server directed recovery.................................................................
Performing SQL Server disaster recovery .................................................................
Best practices..................................................................................................................
20
22
27
28
36
39
19
Overview
Backup and recovery of Microsoft SQL Server by using EMC NetWorker Module
for Microsoft Applications (NMM) involves the following:
SQL Server support for Microsoft Volume Shadow Copy Service (VSS) through
Microsoft-supplied application writers.
Creation of point-in-time copy of data, which is called a snapshot and allows

backup of the SQL Server while the SQL database is online or in use.
Review the following sections before performing SQL Server backup and recovery:
SQL Server versions supported by NMM on page 20
Types of supported backup and recovery on page 21
Writer for SQL data backup and recovery on page 22
Performing SQL Server backups on page 22
SQL Server versions supported by NMM

The EMC Information Protection Software Compatibility Guide provides the most
up-to-date lists of hardware, operating system, service pack, and application versions
supported by the NMM client.
NMM client supports the following versions of SQL Server:
SQL Server 2008 R2 (x86, x64) Cumulative Update 4:

Standard
Enterprise
SQL Server 2008 SP2 (x86, x64):

Standard
Enterprise
SQL Server 2005 (x86, x64) Service Pack 4:

Standard
Enterprise
SQL Server 2008 R2 Express Edition
SQL Server 2008 Express Edition
SQL Server 2005 Express Edition
Note: NMM only supports databases in SQL simple recovery mode.
NMM client does not support the following:
20
SQL Server running on IA64
SQL Server 2000
Types of supported backup and recovery

NMM provides support for the following types of backup:
Full backup of SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2, which
includes:
Writer-level backup:
Default instance backup
Named instances backup
Database-level backup:
Normal database backup
Transparent Data Encryption (TDE) enabled database backup (for only
SQL Server 2008 and SQL Server 2008 R2)
FILESTREAM enabled database backup (for only SQL Server 2008 and
SQL Server 2008 R2)
Database with filegroup backup
Performing SQL Server backups on page 22 provides details.
Note: NMM 2.3 does not support:
SQL log backup of SQL 2005, SQL 2008, or SQL 2008 R2.
Incremental backup of SQL application.
Backup and recovery of individual filegroups and files.
NMM provides the following types of recovery:
Full recovery of SQL Server 2005, SQL 2008, and SQL 2008 R2 databases, which
includes:
Transparent Data Encryption (TDE) enabled database recovery (for only SQL
Server 2008 and SQL Server 2008 R2)
FILESTREAM enabled database recovery (for only SQL Server 2008 and SQL
Server 2008 R2)
Database with filegroup recovery
Instance-level recovery
Writer-level recovery
Disaster recovery
Performing SQL Server recovery on page 27 and Performing SQL Server disaster
recovery on page 36 provide details.
Overview
21
Writer for SQL data backup and recovery

NMM uses the VSS writer SqlServerWriter for SQL Server 2005, SQL Server 2008, and
SQL Server 2008 R2.
Note: The MSDEWriter for SQL Server 2000 is no longer supported.
Performing SQL Server backups

Before performing SQL Server backup, ensure that:
The SQL Server VSS writer service is started.
All databases are online.

Offline databases are not backed up, and no warning appears during the backup
operation if any database is offline.
IMPORTANT
Microsoft recommends that you create a snapshot backup of fewer than 35
databases at a time. Knowledge Base article KB943471 on the Microsoft Support
website provides more information.
This section provides the following information:
SQL Server application information variable settings on page 22
Displaying valid SQL data save sets on page 23
URL encoding for save sets on page 23
Specifying save sets for SQL data on page 24
Configuring SQL Server backups on page 26
SQL Server application information variable settings

Table 1 on page 22 lists the variables that can be specified in the Application
Information attribute of the client resource.
Table 1
SQL variable settings for Application Information attribute
Attribute name
Description
Values
NSR_SNAP_TYPE=value
Specifies the snapshot service provider name.
vss
This value is required.
NSR_DATA_MOVER=value application
information attribute
Specifies the hostname of the NMM client that

mounts the snapshot from NMM client.
The proxy client hostname

Consider the following:
If no value is typed, the local host is used as the
data mover.
If you are setting up a proxy client for a virtual
cluster server, you must also type the proxy client
hostname in the Remote Access attribute of the
client resource.
For serverless backups, specify a proxy client.
Note: This attribute is required for hardware

provider backups that are configured to use a
data mover.
22
Displaying valid SQL data save sets

To display a list of the SQL save sets that are available for backup:
1. Open a command prompt on the application server.
2. Ensure that the SQL Server VSS writer service is enabled and running.
3. At the command prompt, type the following command to list the valid save set
names:
If the application server is on a non-clustered host, type:
nsrsnap_vss_save -?
If the application server is on a Windows cluster, run this command on the
active node of the SQL cluster that is currently hosting the SQL Server:
nsrsnap_vss_save -? -c virtual_server_name
4. Press Enter:
Each line of output corresponds to a save set entry that you can add to the
Save Set attribute of a client resource.
Each entry that you add to the Save Set attribute must be typed on a separate
line, without the double quotes.
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
Note: Remove the inverted commas when copying the save set name from the output.
URL encoding for save sets

Save set names may have special characters, such as the backslash (\). When
specifying such save set names in the Save Set attribute of the client resource, the
special character must be replaced by its URL-encoded value.
Note: If a save set is copied from the nsrsnap_vss_save - ? output, it will include the URL
encoding.
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

CORPDBSERV1\YUKON:
The name of a SQL Server named instance consists of two parts: the hostname
and a unique name. And the hostname and a unique name are always separated
with a backslash (\) character.
The SQL Server named instance is represented in the Save Set attribute of the
client resource as CORPDBSERV1%5CYUKON. Replace the backslash with its
URL-encoded value, which is %5C.
23
To back up only a database, for example NADATA in the SQL Server named
instance CORPDBSERV1\YUKON:
The complete entry in the Save Set attribute should be:
APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NADATA
To back up only a database, for example NA#DATA in the SQL Server named
instance CORPDBSERV1\YUKON:
The complete entry in the Save Set attribute should be:
APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NA%23DA
TA
Table 2 on page 24 lists the most commonly used special characters and their URL
values.
Note: Special characters in save sets names for all the Microsoft applications must be replaced
with their URL-encoded values.
Table 2
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
Specifying save sets for SQL data

Specify SQL data save sets in the Save Set attribute of a client resource.
Table 3 on page 24 lists the SQL save set syntax for the supported types of SQL data.
Table 3
SQL save set syntax (page 1 of 2)
Type of data to back up
Save set syntax
Default instance and named instances
Note: Ensure that the SQL Server VSS writer service is started before using this save set.
24
Table 3
SQL save set syntax (page 2 of 2)
Save set syntax
Named instances and individual databases
For named instance-level backup:

APPLICATIONS:\SqlServerWriter\host%5Cinstance
For example, to back up a SQL Server named instance MT11\BU, type the following:
APPLICATIONS:\SqlServerWriter\MT11%5CBU\
For individual database-level backup:
APPLICATIONS:\SqlServerWriter\<host name>\<database
name>
For example, to back up an individual database TestDB12, type the following:
APPLICATIONS:\SqlServerWriter\JOY-FLORA\TestDB12
Note: Special characters in a SQL Server named instance or database name must be
replaced with their URL-encoded values. URL encoding for save sets on page 23 provides
more information about URL encoding.
IMPORTANT
The nsrsnap_vss_save -? command does not list
APPLICATIONS:\SqlServerWriter as a save set if only SQL Express is installed.
The SQL 2005, SQL 2008, and SQL 2008 R2 Express Edition databases are backed
up by using SYSTEM COMPONENTS:\ save set.
25
Configuring SQL Server backups

To perform a full backup of SQL Server, complete the tasks outlined in Table 4 on
page 26.
IMPORTANT
Guide provides details for the first four tasks in Table 4 on page 26.
Table 4
Tasks for scheduling a backup

Backup task
Consideration
1. Configure a backup pool for snapshot

operations
Snapshots create meditate that is used in the management

of snapshot operations, such as an instant recovery
operation. Create a snapshot pool to store the save sets that
contain snapshot meditate.
2. Configure snapshot policies
For SQL Server backups, the backup snapshot policy can be

set to All or None.
3. Configure a backup schedule
Backup schedules determine the days on which full backups

are run. Full backups include all of the data specified in an
NMM client resource save set.
4. Configure a backup group
Backup groups enable you to balance backup loads to

reduce the impact on your storage and network resources.
5. Configure a SQL Server client resource on

page 26
This task is specific to configuring a SQL Server client

resource.
Configure a SQL Server client resource

To configure a SQL Server client resource:
1. In the Administration page of the NetWorker Management Console, click
Configuration.
2. In the expanded left pane, select Clients.
3. From the File menu, select New.
4. In the Name attribute, type the fully qualified hostname of the NetWorker client.
If backing up a SQL clustered instance, use the virtual SQL Server name here.
Create client resources for all physical cluster nodes where the SQL clustered
instance is being run.
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. For the Browse Policy attribute, select a browse policy from the list.
The browse policy determines the time period during which the rolled-over data
is available for quick access.
7. For the Retention Policy attribute, select a retention policy from the list.
The retention policy determines the time period during which the rolled-over
data is available, although not necessarily quickly.
8. In the Scheduled Backups attribute, specify the save set name.
26
For example, to back up default instance and named-instances together for SQL
Server 2005, SQL Server 2008, or SQL Server 2008 R2, specify the save set name:
Table 3 on page 24 lists the SQL save set syntax for the supported types of SQL
data.
If needed, replace special characters in the save set name with URL-encoded
values. A table of values is provided in URL encoding for save sets on page 23.
9. Specify SQL application variable settings in the Application Information
attribute of the client resource. These settings are described in Table 1 on page 22.
10. Click the Globals (1 of 2) tab.
11. In the Aliases attribute, check that the NETBIOS and Fully Qualified Domain
Name (FQDN) for the NMM client are available.
The NMM client uses the host machine NETBIOS or short name when
connecting to the NetWorker server to browse backups. If the NETBIOS name is
not found, NMM is unable to display backups.
Performing SQL Server recovery

The procedure for recovering SQL Server 2005, SQL Server 2008, and SQL Server
2008 R2 data in a non-clustered environment is different from the procedure for
recovering SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 Express
Edition databases.
Review the sections that are applicable for your setup:
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 data in a
non-clustered environment from the SQLServerWriter save set on page 27
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 Express
databases from the SYSTEM COMPONENTS save set on page 28
Recovering virtual SQL Server for SQL clusters on page 28
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 data in a non-clustered
environment from the SQLServerWriter save set
During system databases recovery, the SQL Server services for the SQL database
instances are automatically detected and stopped by NMM. After the system
databases recovery is complete, the SQL Server services for the SQL Server database
instances are automatically restarted by NMM.
During user databases recovery, the SQL Server services are not stopped or started
by NMM.
To recover SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 data in a
non-clustered environment:
1. From the navigation tree, expand the Applications folder and the
SQLServerWriter folder.
2. Select the databases to recover.
3. From the System Recover Session toolbar, click Start Restore.
Performing SQL Server recovery
27
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 Express databases from the
SYSTEM COMPONENTS save set
To recover SQL Server Express databases that were backed up with the SYSTEM
COMPONENTS save set:
1. If restoring the master database, stop the SQL Server services for the SQL Server
database instances.
2. From the navigation tree, expand the SYSTEM COMPONENTS:\ folder.
3. In the Recovery Options dialog box, clear the option Use Microsoft Best
Practices for selecting the System State.
4. Under System Components, browse the writer SQL Embedded and select the
required databases for recovery.
6. After the recovery is complete, start the SQL Server services for the SQL database
instances.
Recovering virtual SQL Server for SQL clusters

Note: This procedure is common to all supported SQL Server versions and Windows
platforms.
For instance-level recovery on SQL Server cluster, perform the following steps:
1. Using Windows Cluster Management console, make the SQL Server resource
under the Cluster Group of SQL Server, offline.
Now the instance is offline but the disk is available because the group is online.
2. Perform SQL writer recovery.
Note: When performing SQL writer recovery, manually stop and start of the SQL Server
services.
3. In the Cluster Management console, make the SQL Server resource online. Also,
ensure that all the other SQL resources that depend on the SQL Server are online.
Performing SQL Server directed recovery

The directed recovery procedure does not use SQL writer. A recovery performed
without using SQL writer guarantees a crash-consistent database, which means that
there are no torn or corrupted pages. However, all transactions which were in
progress at the time of the snapshot are rolled back. Directed recovery can only be
performed from full SQL database backup.
Directed recovery is only supported on the same versions of Windows Servers. For
example, if the backup is performed on a Windows 2003 host, then the directed
recover can be performed only to another Windows 2003 host. All the database files
must be recovered to a single drive.
28
Before performing SQL directed recovery, ensure that:
There are two client machines, which are on the same platform:
Source machine This is the client on which the backup is performed.
Target machine This is the client to which recovery is performed. It is not
required that SQL Server be installed on the target machine.
Both the source and target client machines are added as client resources in the
NMC.
The recovery drive is available and has sufficient free disk space to accommodate
the data.
Steps for SQL Server directed recovery on page 29 provides the steps for SQL
directed recovery.
The following are not supported:
Directed recovery of:

Filestream database
Transparent Data Encryption (TDE) enabled database
SQL Data Protection Manager (DPM)
SQL Express
Cross-platform directed recovery

For examples, directed recovery of SQL databases on Windows 2003 cannot be
recovered to Windows 2008 and vice versa.
Directed recovery to:

Encrypted target
Compressed drive
Although recovery takes place, the database attachment fails.
Directed recovery from SQL system databases.
Alternate recovery on the same or separate location.
Also, validation of recovery target paths is not available. When a path is selected, the
NMM GUI does not validate if the path is valid. The path validation is done only
after recovery is started.
Steps for SQL Server directed recovery

To perform directed recovery of SQL databases, perform the following steps:
1. Start the NMM GUI on the target machine.
2. Select the NetWorker server containing the SQL backups, as described in
Selecting the NetWorker server on page 30.
3. Select the source client from the NMM GUI, as described in Selecting a source
client on page 30.
4. Select the desired SQL backups, as described in Selecting the desired SQL
databases for directed recovery on page 32.
29
5. Recover the SQL backups:

To the default recovery path, as described in Recovering to default recover
path on page 32.
or
To a user-defined location from the SQL tab, as described in Recovering to a
user-defined path on page 33.
6. Select Start Recover.
7. When the recovery is complete:
a. Copy the recovered .mdf and .ldf files to the desired location, which may be
on the same or different drive.
b. Use the SQL Management Studio program to manually attach the .mdf and
the .ldf files from the respective locations.
Attaching recovered SQL databases on page 35 provides details.
Note: For multiple NMM directed recovery on same recovery farm, use the same procedure for
each of the source clients. Directed recovery of the same data to the same location again, that is
overwriting, is not allowed.
Selecting the NetWorker server

To select the NetWorker server containing the SQL backups:
1. To select a NetWorker server other than the one that is currently selected, click
either of the following options:
Click the Networker Server icon in the NMM GUI of the target client.
Or
Click Option > Configure Option > Backup Server Name.
The Change NetWorker Server dialog box appears.
2. In the Change NetWorker Server dialog box:
a. Click the Update Server List button to refresh the list of NetWorker servers.
b. Select the desired NetWorker server and click OK.
3. In the NMM GUI of the target machine, select the source client machine, as
described in Selecting a source client on page 30.
Selecting a source client

To select a source client:
1. From the Options menu in the NMM GUI of the target machine, select Configure
Options to add the source client to the list of clients that you can browse.
The Configuration Options dialog box, as shown in Figure 1 on page 31 appears.
30
Figure 1
Configuration Options dialog box
2. Click the button next to the Client Name field.

The Select Viewable Clients dialog box appears.
3. Select the backed up SQL client from the Selected clients on list:
a. Click Add >> to add the selected client to the list of clients in the Client to list
on menu bar: list.
b. Click OK.
The Client menu in the NMM GUI displays the list of selected clients that you can
browse.
4. Select the desired SQL client in the Client menu. Figure 2 on page 31 shows the
Client menu.
Figure 2
Client menu
5. Select the desired SQL Server for directed recovery, as described in Selecting the
desired SQL databases for directed recovery on page 32.
31
Selecting the desired SQL databases for directed recovery

To select the desired SQL databases for directed recovery:
1. After the application refreshes the current browse tree, ensure that the System
Recover Session option is selected.
The SQL Server application backups are now displayed for directed recovery
browsing in the current browse tree.
2. Expand the APPLICATIONS > SqlServerWriter tree nodes, as shown in Figure 3
on page 32.
Figure 3
APPLICATIONS > SqlServerWriter tree nodes
3. Select the desired databases.

Note: Directed recovery of SQL system databases is not supported. It is recommended that
you perform directed recovery of one database at a time.
4. Recover the SQL databases:

To the default recover path, as described in Recovering to default recover
path on page 32.
or
To an user-defined location from the SQL tab, as described in Recovering to a
user-defined path on page 33.
Recovering to default recover path

To recover SQL databases to the default recover path:
1. In System recover Session, select the database to be recovered.
2. Click Recover.
The System Recover Summary dialog box appears.
3. Click Recover Option.
32
The System Recover Session Options dialog box appears.
Figure 4
System Recover Session Options
4. Click the SQL tab.

5. Select the Restore SQL file to local machine using their original directory path
option.
6. Click OK.
The File System Recover Summary form appears.
Note: The SQL database recovery path is based on the original path. This is the default SQL
recovery path option.
7. Click Start Recover to start the directed recovery.

8. Switch to the Monitor page to view the status and progress of the recovery.
Recovering to a user-defined path

To recover SQL databases to a user-defined path:
1. In System recover Session, select the database to be recovered.
2. Click Recover.
The File System Recover Summary dialog box appears.
3. Click Recover Option.
The System Recover Session Options dialog box appears.
4. Click the SQL tab.
5. Select the Specify the file system path where the SQL database(s) should be
restored option.
6. Click Browse.
7. Select a path in the Browse For Folder dialog box, and click OK.
33
8. Click OK in the System Recover Session Options dialog box.

Note: The field is read-only and you cannot manually type a path.
9. Click Start Recover to start the directed recovery.

10. Go to the Monitor page to view the status and progress of the recovery.
IMPORTANT
Do not provide a path in the Networker tab, otherwise recovery will fail.
Examples of log messages in NMM log file and Monitor page

The following are examples of messages for SQL directed recovery in the NMM log
file and the Monitor page:
Recover to original location messages:

Command line:\n C:\Program
Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A
RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s
mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A
NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A
NSR_SQL_TARGET_ORIG=yes -I nsrsnap_vss_recover: flag=A arg=NSR_SQL_RECOVER_MODE=alt_location
nsrsnap_vss_recover: flag=A arg=NSR_SQL_TARGET_ORIG=yes
NMM .. Performing SQL directed restore.
NMM .. SQL directed restore will relocate database files to their
original locations.
Recover to user-defined location messages:

Command line:\n C:\Program
Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A
RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s
mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A
NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A
NSR_SQL_TARGET_DIR=E:\ -I nsrsnap_vss_recover: flag=A arg=NSR_SQL_RECOVER_MODE=alt_location
nsrsnap_vss_recover: flag=A arg=NSR_SQL_TARGET_DIR=E:\
NMM .. Performing SQL directed restore.
NMM .. SQL directed restore will relocate database files to
path[E:\].
NMM .. SQL directed restore relocating database files for database
[APPLICATIONS:\SqlServerWriter\MB-CLNT-3\AcmeBank].
NMM .. SQL directed recover, relocating file [C:\Program
Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf] to
[E:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf].
Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf] to
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf].
Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf] to
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf].
34
Attaching recovered SQL databases

To manually attach the recovered SQL databases:
1. Start the SQL Management Studio.
2. In the SQL Attach Database dialog box:
a. Locate the primary database file to attach.
SQL recovers all primary database files (.mdf), logs files (.ldf), and secondary
database files (.ndf), if present.
b. The SQL Administrator must know which files are the primary database files.
c. Once the primary database file is attached, SQL automatically identifies the
other database files, provided the files are all at the same location.
d. If the other database files are not in the same location, then you must specify
the respective locations of the restored files:
.mdf
.ldf
.ndf
3. Click OK to create the database.
The database is now created and available.
35
Performing SQL Server disaster recovery

In cases where the SQL Server databases must be completely rebuilt, NMM can
facilitate a disaster recovery. Prior to disaster recovery, use NMM to perform regular
backups of volumes, SYSTEM COMPONENTS, and application save sets:
1. Back up the following file system volumes with the snapshot policy All:
C:\
SYSTEM COMPONENTS:\
The back up of file system volumes includes the following:
Windows Boot Volume
Windows System Volume
Note: If the system has been set up with a separate file system for the Windows
boot\system partition and separate file system for application installation, then along with
C:\ drive, back up the file system that includes the Windows Boot Volume, Windows
System Volume, and application software.
Specifying save sets for SQL data on page 24 provides information for
SYSTEM COMPONENTS:\ backup.
Note: Back up Cluster Management when backing up SQL Server cluster.
2. Back up application data for SQL Server with the following save set:
Note: You must specify a separate applications save set for each SQL cluster instance when
backing up SQL Server cluster.
The following are scenarios and procedures for recovery:
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2

with NetWorker 7.6 SP2 and NMM 2.3 on page 36
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2

with NetWorker 7.6 SP1 or earlier, and NMM 2.3 on page 37
SQL Server (stand-alone) disaster recovery on Windows Server 2003 with

NetWorker 7.6 SP1 or earlier, and NMM 2.3 on page 37
Clustered SQL Server disaster recovery on Windows 2008 or Windows 2008 R2

with NetWorker 7.6 SP2 and NMM 2.3 on page 37
Clustered SQL Server disaster recovery on Windows Server 2008, 2008 R2, or
2003 with NetWorker 7.6 SP1 or earlier, and NMM 2.3 on page 38
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker
7.6 SP2 and NMM 2.3
If you have installed NetWorker 7.6 SP2 with NMM 2.3 on Windows 2008 and
Windows 2008 R2, you can leverage the Windows Disaster Recovery capability
provided by NetWorker 7.6 SP2 for disaster recovery of SQL Server (stand-alone)
data. Performing Windows Disaster Recovery backup and recovery for Microsoft
applications on page 232 provides details.
36
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker
7.6 SP1 or earlier, and NMM 2.3
If you have installed NetWorker 7.6 SP1 or earlier with NMM 2.3 on Windows 2008
or Windows 2008 R2, perform the following steps:
1. Install SQL Server and latest service packs, including the SQL Server instances
that were running on the machine before the disaster.
Note: The instance names must be exactly the same as the previous ones.
2. Perform a recover of the SYSTEM COMPONENTS and volumes.

3. Perform a recovery of the complete SQL Server instance from the backup.
SQL Server (stand-alone) disaster recovery on Windows Server 2003 with NetWorker 7.6 SP1 or
earlier, and NMM 2.3
To perform a SQL Server (stand-alone) disaster recovery on Windows Server 2003
with NetWorker 7.6 SP1 or earlier, and NMM 2.3:
1. Set up a new Windows 2003 machine, so that its parameters match with those of
the old machine:
Machine name
IP address
Domain name
2. Recover SYSTEM COMPONENTS:\ and the local file system volumes.
3. Restart the machine.
4. Log in to the machine as local administrator.
5. Unjoin the domain, and then rejoin the domain.
6. Recover the APPLICATIONS:\SqlServerWriter save set.
Clustered SQL Server disaster recovery on Windows 2008 or Windows 2008 R2 with NetWorker
7.6 SP2 and NMM 2.3
If you have installed NetWorker 7.6 SP2 with NMM 2.3 on Windows 2008 or
Windows 2008 R2, you can perform disaster recovery of SQL Server cluster data.
In the procedure provided below, the following conditions are assumed:
SQL Server 2008 R2 is hosted on a Microsoft Failover Cluster on Windows 2008

SP2.
NMM 2.3 is used to protect the SQL Server.
Node & File Share Majority is the quorum setting.
Cluster node A has SQL installed in C:\Program Files\Microsoft SQL Server.
Cluster node B has SQL installed in C:\Program Files\Microsoft SQL Server.
Shared disks that include the SQL databases can be accessed by node A and B.
To protect the clustered SQL Server:

1. Install the NetWorker 7.6 SP2 client and NMM 2.3 on both nodes A and B.
Performing SQL Server disaster recovery
37
2. Perform an instance-level backup of the virtual SQL Server by using NMM 2.3.
Configuring SQL Server backups on page 26 provides details.
3. Perform a Windows Disaster Recovery backup of Node A. Performing Windows
Disaster Recovery backup and recovery for Microsoft applications on page 232
provides details
4. Perform a Windows Disaster Recovery backup of Node B. Performing Windows
Disaster Recovery backup and recovery for Microsoft applications on page 232
provides details.
To recover a clustered SQL Server:
1. Perform a Windows Disaster Recovery on Node A and then on Node B.
Performing Windows Disaster Recovery backup and recovery for Microsoft
applications on page 232 provides details.
Note: The Failover Cluster should be up and running.
If the host is a virtual machine, the ensure that a new virtual machine is created with the
same configuration as the original one, and then perform Windows Disaster Recovery.
2. Export the required shared disks. Ensure that the disks have the same properties
as the original ones, and that the disks are shared between node A and node B.
3. From the Cluster Management interface, delete any disk entries that are listed as
failed disks.
4. Add the newly exported shared disks to the SQL group and assign the same drive
letters as before the disaster.
5. On node A, open the NMM client software, and recover system databases.
6. After system databases are recovered, recover user-defined databases.
Clustered SQL Server disaster recovery on Windows Server 2008, 2008 R2, or 2003 with
NetWorker 7.6 SP1 or earlier, and NMM 2.3
If you have installed NetWorker 7.6 SP1 or earlier with NMM 2.3 on Windows 2008,
Windows 2008 R2 or Windows 2003, perform the following steps:
1. Set up each new cluster machine. Ensure that each new cluster machine has the
same parameters as the corresponding original cluster machine:
Machine name
IP address
Domain name
2. For only Windows Server 2008, on each cluster machine:
a. Install SQL Server and all updates that were installed on the old machine.
b. Install all instances that were installed on the old machine.
3. Recover each nodes SYSTEM COMPONENTS:\ and local file system volumes.
4. Restart each machine.
38
5. On each machine:
a. Log in to the machine as local administrator.
b. Unjoin the domain.
c. Rejoin the domain.
6. On the active node:
a. Stop SQL instance services.
b. Recover APPLICATIONS:\SQLServerWriter save set.
c. Start SQL Instance Services.
Cluster recovery is complete.
Best practices
Table 5 on page 39 lists the best practices and recommendations to follow when using
NMM to back up and recover SQL Server.
Table 5
Best practices and considerations (page 1 of 2)
Consideration
Best practice
Define different schedules for protecting

the following:
The operating system and the file
system
The application that is to be backed
up
For application servers, such as SQL Server or Exchange Server, back up the server application data using a
schedule that is different from the schedule used for the host operating system data and volumes.
Typically, while application data is backed up several times a day, operating system data and volumes are
backed up less frequently.
To accomplish this:
1. Create a separate backup group, snapshot policy, and client resource for:
Server application data
Volumes and operating system data
2. Assign the appropriate snapshot policy and client resource to each backup group.
Installation path for application server

program
Do not install application server program files on the same volume as the applications database files and log
files.
Copy-on-write snapshot technology

against split-mirror snapshot
technology, when using EMC
CLARiiON or EMC Symmetrix.
This applies to the following hardware-based snapshots:

Large databases and databases that are updated frequently should not be saved with copy-on-write
snapshot technology. Instead, use a split-mirror snapshot technology, such as a CLARiiON clone or a
Symmetrix BCV.
Although copy-on-write technology requires less hardware resources, split-mirror technology can better
handle the requirements of large or fast-changing databases.
Split-mirror technology is supported only with a VSS hardware provider, such as the EMC VSS provider. It is
not provided by the built-in Microsoft System Provider.
NetWorker modules and the NMM client Although NMM 2.3 can coexist with NME or NMSQL, the best practice would be to have a backup strategy
with NMM 2.3.
CLARiiON limits for the CX500
If the number of snapshots exceeds the limit for number of snapshots supported per CLARiiON, a "VETO"
failure occurs during snapshot creation.
For a CX500, the limit is 150 snapshots or snapshot sessions system-wide. This includes reserved snapshots
or sessions for SAN Copy. There is also a limit of eight snapshots or snapshot sessions per LUN.
The EMC SnapView Integration Module for SQL Server (SIMS) Administrators Guide provides the limitations
for CLARiiON systems
Verify VSS SQL Writer service is

running
After installing SQL Server, verify that the VSS writer service is running for the VSS writer snapshot to be
successful.
It must be enabled or set to automatic after installation.
Best practices
39
Table 5
40
Best practices and considerations (page 2 of 2)
Consideration
Best practice
Ignore tempdb database
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 VSS writer and is not backed up.
Special character databases
Special character databases are not backed up and the best practice is not use any special characters in the
database name.
SQL Server crash may occur when the

SQL Server executable or the
supporting system components get
corrupted.
Perform the following steps:

1. Restore the system components, which by default has the Windows boot volume and Windows system
volume.
2. Reinstall the SQL Server with its latest software updates and then recover the SQL databases by using
APPLICATIONS:\SqlServerWriter.
Perform a SQL writer-level recovery
To rectify the following:

The SQL Server instance service is not in start state.
When the SQL service is started, an error message about that master database not being available,
appears.
A SQL exception is thrown when the SQL Server Management Studio is started to connect to SQL Server
instance.
2
Microsoft Active
Directory Backup and
Recovery
Overview ........................................................................................................................
Performing an Active Directory or ADAM full backup..........................................
Performing Active Directory or ADAM granular backup ......................................
Performing Active Directory database recovery ......................................................
Performing an Active Directory granular recovery .................................................
Performing Active Directory disaster recovery ........................................................
42
43
45
52
53
57
41
Overview
This chapter provides the information required for backup and recovery of Microsoft
Active Directory by using EMC NetWorker Module for Microsoft Applications
(NMM).
IMPORTANT
In Windows Server 2008, Active Directory Lightweight Directory Services (AD
LDS) includes the ADAM functionality provided in Windows Server 2003. Unless
otherwise noted, assume that all references to ADAM in this chapter also apply to
AD LDS.
Review the following sections before performing Active Directory backup and
recovery:
Active Directory objects for granular backup and recovery on page 43

NMM supports the following types of backup for Active Directory:
Full backup VSS backup of the entire Active Directory database. This type of
backup can only be performed at full level.
Performing an Active Directory or ADAM full backup on page 43 provides
details.
Granular backup Traditional or non-VSS backup of individual Active

Directory objects and object attributes. Granular backups can be performed at
both full and incremental levels.
Performing Active Directory or ADAM granular backup on page 45 provides
details.
NMM supports the following types of recovery for Active Directory:
Full Active Directory database recovery In either of the following recovery

modes:
Authoritative
Or
Nonauthoritative
Performing Active Directory database recovery on page 52 provides details.
Granular recovery Recovery of individual Active Directory objects or object

attributes. Granular recovery should only be performed as a supplement to full
Active Directory database recovery.
Performing an Active Directory granular recovery on page 53 provides details.
Disaster recovery Performing Active Directory disaster recovery on page 57

provides details.
Note: NMM 2.3 does not support deduplication for Active Directory.
42
Active Directory objects for granular backup and recovery

NMM supports granular backup and recovery of the following Active Directory
objects:
Users
Groups
Organizational units
Computer
Contact
InetOrgPerson
Shared folder
MSMQ queue alias
Performing an Active Directory or ADAM full backup

Regularly back up the following file system volumes with the snapshot policy All:
C:\
SYSTEM COMPONENTS:\
The backup of file system volumes automatically includes the following:
Windows Boot Volume
Application software
Note: If the system has been set up with a separate file system for the Windows boot\system
partition and separate file system for application installation, then along with C:\ drive, back
up the file system that includes the Windows Boot Volume, Windows System Volume, and
application software.
Configure a client resource for Active Directory or ADAM full backup

To create a client resource for Active Directory or ADAM full backup:
Configuration.
4. In the Name attribute, type the fully qualified hostname of the NetWorker client.
6. For the Browse Policy attribute, select a browse policy from the list. The browse
policy determines the time period during which the rolled-over data is available
for quick access.
Performing an Active Directory or ADAM full backup
43
7. For the Retention Policy attribute, select a retention policy from the list. The
retention policy determines the time period during which the rolled-over data is
available, although not necessarily quickly.
8. Select the Scheduled Backups attribute.
9. In the Save Set attribute:
For Active Directory full backup, specify:
C:\
SYSTEM COMPONENTS:\
For ADAM writer backup, specify:

APPLICATIONS:\ADAM <instance_name> Writer
10. For the Group attribute, select the backup group to which this client resource will
be added. Ensure that:
The Snapshot attribute is selected.
A snapshot policy is selected in the Snapshot Policy attribute.
A pool is selected in the Snapshot Pool attribute.
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 such
that the backups for the hosts 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 command nsrsnap_vss_save.exe.
14. In the Application Information attribute, type NSR_SNAP_TYPE=VSS.
16. 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. If the NMM client is part of a cluster:
a. Type the names of the physical nodes of the cluster in the Remote Access
attribute.
b. Click OK.
44
Performing Active Directory or ADAM granular backup

A traditional non-VSS granular Active Directory backup enables you to recover
individual objects and object attributes. A granular ADAM backup enables you to
recover individual application partitions.
A granular backup does not use snapshot technology. Instead, the backup is routed
directly to a granular backup medium.
Active Directory objects for granular backup and recovery on page 43 provides the
list of Active Directory objects that can be backed up by using NMM. The Microsoft
website provides more information about Active Directory objects and attributes.
IMPORTANT
Take a full backup after:
Changing the properties or main attributes of an object.
Or
Deleting and then recreating a security group.
Considerations for granular backup

Consider the following guidelines before performing a granular Active Directory
backup:
System-only attributes are not backed up with Active Directory objects. These
attributes are recovered through tombstone reanimation.
Changing the system date and time to an older date in the domain controller is
not recommended.
Each item in Active Directory is marked by time. Active Directory uses time to
resolve any data conflicts. Recovery of a deleted object by the NMM client will fail
if the date and time are changed after the objects have been backed up. If a change
in the system date or time is necessary, immediately take a full backup of the
domain.
The Group Policy object exists in two places:

As an Active Directory object in the Group Policy Container.
In the Windows registry.
Many of the settings that can be edited from the Group Policy Management
Console actually reside in the system registry and not in Active Directory.
Therefore, if these values are changed after a backup, a recovery will not restore
the attribute values and the system values will take precedence. To restore the
attribute values, a recovery of SYSTEM COMPONENTS is required.
A restored user account is automatically disabled and the pwdLastSet attribute is

not recovered for security. A new password must be set after a user account is
recovered.
A change to an objects memberOf attribute is reflected in the owner object of that

group and not in the object itself.
For example, if a user is added to the Guests group, the Guests group object is
modified, not the user object. If an incremental backup is performed, the Guests
object and not the user object, is included in the backup.
45
The rootDSE object is dynamic when created. ADAM lists the connection and the
primary registered partition. When a binding is requested on the rootDSE object,
ADAM returns the value of the default Naming Context. On a domain controller,
this is always the Domain Naming Context. Reserve port 50000 for backups of
ADAM partitions. For Active Directory, use standard LDAP port 389.
Do not modify the msNPAllowDialin attribute directly in Windows Server 2003

SP1. Use the RAS administration function to modify the value. The Active
Directory Users and Computers (ADUC) MMC snap-in uses the RAS API to
modify this attribute and the associated userParameters attribute. If the RAS API
is not used, the userParameters attribute is not modified with the
msNPAllowDialin attribute and the configuration will be incomplete.
Many configuration settings are stored in Active Directory, but LDAP cannot
always be used to modify them. Also, some items stored in Active Directory are
references to objects that are managed by other applications. The appropriate
APIs must be employed to modify them.
Configuring Active Directory or ADAM granular backups

IMPORTANT
Do not configure a proxy client for granular ADAM or Active Directory backups.
To configure an Active Directory or ADAM granular backup, perform the tasks
outlined in Table 6 on page 46.
Table 6
Tasks for Active Directory or ADAM granular backup

Backup task
Considerations
1. Set up local Windows SYSTEM

account as an ADAM administrator on
page 47
The ADAM server, which is also an NMM client, relies on the

NetWorker clients nsrexecd service to spawn the required binaries
to perform a backup. The nsrexecd service and other binaries run
under the Windows SYSTEM account. To ensure that these binaries
can access ADAM data, the Windows SYSTEM account must be
given access rights to each instance on the ADAM server.
Note: This task is required only for granular ADAM backups. Skip
this task for granular Active Directory backups.
46
2. Configure a pool for backup

operations on page 47
First create a backup pool to store the save sets that contain
metadata and then configure the backup pool.
3. Configure a backup schedule on

page 49
Backup schedules determine the days on which full or incremental

backups are run. While full backups include all the data specified in
an NMM client resource save set, incremental backups include only
the data that has changed since the last backup.
4. Configure a backup group on

page 49
Backup groups enable you to balance backup loads to reduce the

impact on your storage and network resources.
5. Configure a client resource for

granular Active Directory or ADAM
backup on page 50
A client resource specifies the components to include in a backup by

NMM client. Client resources are associated with other backup
resources, such as groups.
6. Configure privileges on page 51
NMM client must be granted NetWorker administrator privileges to

perform media database operations during a deletion.
Set up local Windows SYSTEM account as an ADAM administrator

IMPORTANT
These steps are not required for Active Directory backup.
To set up the Windows SYSTEM account with permissions on the local ADAM
server:
1. Open the ADAM ADSI Edit utility.
The ADAM ADSI Edit utility is available with ADAM SP1.
2. Connect to the ADAM instance.
3. In the Connection Settings dialog box, select Well-known naming context and
Configuration from the menu.
4. Type the port number (typically 50000) of the ADAM partition in the Port field
and then click OK.
5. In the left pane, select CN=Roles.
6. In the right pane, right-click 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 ADAM server name.
9. Save your changes.
10. Repeat this procedure for each ADAM instance that you want to back up.
Configure a pool for backup operations
Configuring a backup pool is a four-part process:
Configuring a device on page 47
Configuring a label template on page 48
Configuring a backup pool on page 48
Labeling the device on page 49
The EMC NetWorker Release 7.6 Service Pack 2 Administration Guide provides more
detailed information about performing the steps included in this section.
Configuring a device
Configure a media device for snapshot metadata. Configure a tape, file, or advanced
file type device. For best performance, configure a file or advanced file type device so
that data can be recovered without the potential delay associated with retrieving a
tape.
To configure a device:
1. In the NetWorker Administration page of the NetWorker Management
Console, click Devices on the taskbar.
2. In the expanded left pane, select Devices.
47
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 servers 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 and click OK.
Set this attribute to a value that will speed up the backup. The default value is 4,
and the maximum value is 512.
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:
Media.
2. In the expanded left pane, select Label Templates.
4. In the Name attribute, type a name that identifies the series of labels as belonging
to volumes for metadata.
5. In the Comment attribute, specify a comment for the label.
6. In the Fields attribute, specify a text name such as Metadata and on a separate line,
specify a numeric range such as 001-999 or a text range such as aa-zz.
These attributes are used to incrementally identify each label.
7. Click OK.
Configuring a backup pool
Note: Ensure that the backup pools for granular Active Directory or ADAM backups are
different from the backup pools for NMM client backups that include snapshots. In this way,
you can sort granular Active Directory and ADAM backups from other backups.
To configure a backup pool:

Media.
2. In the expanded left pane, select Media Pools.
48
4. For the Name attribute, type a name that matches the label template.
5. In the Comment attribute, specify a comment for the pool.
6. Select the Enabled attribute.
7. For the Pool type attribute, select the backup pool type.
8. For the Label template attribute, select the matching label template.
9. Perform either of the following steps:
Click the Selection Criteria tab, and specify an NMM client for the Clients
attribute. A value must be typed for this attribute if you choose not to specify
groups in the Groups attribute.
Or
For the Groups attribute, select the applicable backup groups.
10. In the Devices attribute, select each device that can accept backups for this pool.
11. Click OK.
Labeling the device
Before a device can be used for backup, it must be labeled.
To label a device:
Devices.
2. In the right pane, right-click the name of the device and select Label.
3. In the Pool attribute, select the backup pool that was created.
4. Select the Mount after Labeling attribute.
5. Click OK.
Configure a backup schedule
The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide
provides details.
Note: Level 1 to 9 backups are not supported for granular Active Directory and ADAM
backups.
Configure a backup group

Use a backup group to assign the following attributes to a set of client resources:
Backup start times
Schedules
Backup pools
To configure a backup group:

Configuration.
2. In the expanded left pane, select Groups.
4. In the Name attribute, type a name for the backup group.
49
6. For the Start Time attribute, enter the time when the first backup is to be created.
7. For the Autostart attribute, select Enabled.
Note: Unlike most other NMM application backup client resources, snapshot policies are
not applicable to granular Active Directory or ADAM backups.
Do not specify or assign a snapshot policy or a snapshot pool to the backup

group:
Ensure that the Snapshot attribute is clear.
Do not select a snapshot policy in the Snapshot Policy attribute.
Do not select a pool in the Snapshot Pool attribute.
8. Click the Advanced tab.
9. Set the Client Retries attribute to 0 (zero).
10. Click OK to create the backup group.
Configure a client resource for granular Active Directory or ADAM backup
To create a client resource for granular Active Directory or ADAM backup:
1. Perform step 1 through step 8 as in Configure a client resource for Active
Directory or ADAM full backup on page 43.
Specify the components to be backed up.
Specify domain objects in the following format:
CN=<common name>,OU=<OU name>,DC=<domain name>,DC=suffix

For example:
CN=testuser1,OU=OU1,DC=corp,DC=xyz,DC=com
Where the backup saves the entire domain named corp.xyz.com from its root
level.
be added.
6. In the Backup command attribute, type the appropriate command for Active
Directory objects or ADAM objects:
Active Directory objects: Type the following command in the Backup
Command attribute:
nsradsave.exe
Active Directory domain objects and ADAM objects cannot be backed up in

the same client resource. Each ADAM partition must be backed up with a
separate client resource.
50
ADAM objects: To back up ADAM application partitions, type the following

command in the Backup Command attribute, specifying the port number
50000. For example, type the following:
nsradsave.exe -p 50000
7. Perform step 15 through step 18 as in Configure a client resource for Active

Directory or ADAM full backup on page 43.
Configure privileges
For Active Directory and ADAM granular backup, in addition to setting up
permissions as described in Set up local Windows SYSTEM account as an ADAM
administrator on page 47, grant NetWorker administrator privileges to the NMM
client so that media database operations can be performed during a deletion. If you
are setting up an NMM client in a cluster, grant NetWorker administrator privileges
to each cluster node and virtual server.
To add configure privileges:
Configuration.
2. In the expanded left pane, click User Groups.
3. Right-click the Administrators group, and then select Properties.
The Properties dialog box appears.
4. In the Users attribute, add the following values for the NMM client host. Place
each value on a separate line:
user=administrator,host=NMM_client_host
user=system,host=NMM_client_host
Where NMM_client_host is the DNS hostname of the NMM client.
If the NMM client is installed in a cluster, grant NetWorker administrator
privileges to each cluster node and virtual server.
5. Click OK.
51
Performing Active Directory database recovery

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

If the Active Directory server is not in a clustered environment, select all of the
items under the SYSTEM COMPONENTS folder.
If the Active Directory server is part of a cluster environment:
a. From the Options menu, select System Recover Session Options and then
click the NetWorker tab.
b. Clear the Use Microsoft best practices for selecting the system state
attribute. Click Yes, when asked to confirm your selection.
c. Click OK to close the System Recover Session Options dialog box.
d. Select all of the items under the SYSTEM COMPONENTS folder except for
the Cluster Writer.
11. To determine whether any volumes need to be mounted, right-click the selected
item and select Required Volumes.
13. Perform an authoritative recovery of the Active Directory server.
The EMC NetWorker Module for Microsoft Applications, Release 2.3 Administration
Guide provides more information about this type of recovery.
14. After the Active Directory recovery is complete, restart the host to restart the
Active Directory server.
15. If the Active Directory server is part of a cluster environment, select the Cluster
Writer for recovery.
16. Recover any remaining volume or application data.
Performing an Active Directory granular recovery

You can individually select deleted Active Directory objects and their attributes for
recovery.
Active Directory objects for granular backup and recovery on page 43 provides the
list of Active Directory objects that can be recovered by using NMM. The Microsoft
website provides more information about Active Directory objects and attributes.
Due to Active Directory limitations, there are some restrictions on the recovery of
objects and attributes. Recovery restrictions for Active Directory on page 53
provides more information about recovery restrictions.
Recovery restrictions for Active Directory

The following restrictions apply when recovering Active Directory objects and
attributes:
Note: After starting an Active Directory recovery, access the Monitor page to verify the
status of the recovery.
Tombstone lifetime restriction When an Active Directory object is deleted, it is

sent to a special container, named Deleted Objects or tombstone. This object is
now invisible to normal directory operations. It is better to recover a tombstone
object instead of recreating it because data, such as the Security Identifier (SID)
53
and the Globally Unique Identifier (GUID) are stored with the tombstone object.
This data is critical for additional data recoveries, such as assigned group
permissions.
For example, Access Control Lists (ACLs) use the SID of a security identifier
object to store its permissions. A recreated 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. The lifetime age is 180 days for Windows 2003 SP1, Windows 2003
SP2, Windows 2008, and Windows 2008 R2, and is 60 days for Windows 2003 R2.
After an object is deleted from the tombstone, it cannot be recovered. This is an
Active Directory restriction. The tombstone lifetime is a configurable attribute of
a Windows domain.
System-only attributes cannot be recovered Object attributes that are

system-only can neither be backed up nor recovered. This is an Active Directory
restriction.
Table 7 on page 54 provides a sample list of system-only attributes that are not
backed up.
Table 7
System-only attributes that are not backed up

badPwdCount
lastLogon
uSNChanged
badPasswordTime
logonCount
uSNCreated
distinguishedName
objectCategory
userAccountControl
dSCorePropagationData
objectClass
whenChanged
instanceType
objectGUID
whenCreated
lastLogoff
sAMAccountType
Table 8
54
Attributes that are retained for a deleted object Table 8 on page 54 provides a
sample list of attributes that are retained for an Active Directory object when it is
deleted and moved to the tombstone database.
Retained attributes after object is deleted

attributeID
mSMQOwnerID
subClassOf
attributeSyntax
name
systemFlags
distinguishedName
nCName
trustAttributes
dNReferenceUpdate
objectClass
trustDirection
flatName
objectGUID
trustPartner
governsID
objectSid
trustType
groupType
oMSyntax
userAccountControl
instanceType
proxiedObjectName
uSNChanged
Table 8
Retained attributes after object is deleted

IDAPDisplayName
replPropertyMetaData
uSNCreated
legacyExchangeDN
sAMAccountName
whenCreated
mS-DS-CreatorSID
securityIdentifier
These attributes are restored when deleted objects from the tombstone database
are restored. Objects that do not retain all of their mandatory attributes would
cause a constraint violation error during a restore attempt. For example, a
published shared printer has mandatory attributes (printerName, serverName,
shortServerName, uNCName, and versionNumber), which are not retained in the
tombstone database.
Object password attributes An objects password cannot be recovered. After

recovering an object with a password attribute, the Windows administrator must
reset the password.
Moved or renamed objects If objects are moved to another location or

renamed, but not deleted from Active Directory, they cannot be restored even if
they are successfully backed up. This is because the objects are not being stored
in the deleted storage database (tombstone). Only objects stored in that database
can be restored.
However, the attributes for these objects can be restored from the Context menu
of the Active Directory interface, which restores the objects with the specific
attribute sets.
Attributes with null values Attributes with null values are not backed up and
therefore are not recovered. For example, if the attribute Phone Number is empty
(null), then the null Phone Number attribute is not backed up.
This is an Active Directory restriction and is intended to prevent the
unintentional overwriting of valid attribute values.
For example, if a Phone Number attribute is null when a snapshot is taken, but
later a valid phone number is added, subsequent recovery operations will not
overwrite the valid phone number with a null value.
Schema objects Schema objects cannot be recovered and therefore are not
backed up, and should never be deleted.
Recovering an Active Directory object or object attribute

To recover an Active Directory object or object attribute:
1. Start the NMM client program.
2. From the application toolbar, click the NetWorker Server icon to select the
NetWorker server on which the NetWorker client was configured for backup.
3. In the left pane, select Recover > Active Directory Recover Session.
4. In the navigation tree, select the Active Directory objects to be recovered. By
default, the objects displayed in the navigation tree are from the most recent
backup:
To search for an item, click the Search tab.
Guide provides details about searching for a recovery item.
55
To recover objects from a previous backup:

To view all versions of a backup object prior to the selected browse time,
select an object in the navigation tree, right-click and select Versions.
5. To determine whether any volumes need to be mounted for a selected object,
right-click an object and select Required Volumes.
6. Recover the entire object or selected object attributes:
To recover the entire object:
a. Select the object.
b. From the Active Directory Recover Session toolbar, click Start Recover to
begin the recovery operation.
Note: An entire object can only be restore if it is deleted. The attributes are restored to
an existing object.
To recover the selected attributes of an object:

a. Right-click an object and select Restore Item Attributes.
The Active Directory Recover Attributes dialog box appears.
b. Select each attribute that is to be recovered.
c. Click OK.
7. Click Start Recovery.
8. From the left pane, select Monitor to view the progress of the recovery.
Selecting Active Directory object attributes

Use the Active Directory Recovery Attributes dialog box to select the attributes that
you want to recover for an Active Directory object.
To select object attributes for recovery:
1. Select each attribute that is to be recovered. If all attributes are selected or no
attributes are selected, the entire object is recovered.
2. Click OK.
The Active Directory Recovery Attributes dialog box closes.
3. From the Active Directory Recover Session toolbar, click Start Recover.
56
Performing Active Directory disaster recovery

To perform disaster recovery:
When NetWorker 7.6 SP2 or later is installed with NMM 2.3 on Windows Server
2008 or Windows Server 2008 R2, use Windows Disaster Recovery.
Chapter 10, Windows Disaster Recovery with NetWorker 7.6 SP2 and NMM,
provides details about Windows Disaster Recovery.
When NetWorker 7.6 SP1 or earlier is installed with NMM 2.3 on supported
Windows Servers, use application data recovery. The disaster recovery
procedure for Active Directory generally includes a system recovery followed by
a standard Active Directory recovery.
The following sections provide information:
Guide provides information about system component recovery.
Performing an Active Directory or ADAM full backup on page 43 provides
information for backing up data for disaster recovery.
Performing Active Directory database recovery on page 52 and Performing
an Active Directory granular recovery on page 53 provide recovery
information.
Performing Active Directory disaster recovery
57
58
3
Microsoft Data
Protection Manager
Server Backup and
Recovery
Overview ........................................................................................................................
Performing DPM Server backups ...............................................................................
Performing a DPM Server recovery ...........................................................................
Performing DPM granular recovery ..........................................................................
Performing a granular directed recovery to a DPM-protected server ..................
Performing DPM disaster recovery ............................................................................
Microsoft Data Protection Manager Server Backup and Recovery
60
65
69
71
73
74
59
Microsoft Data Protection Manager Server Backup and
Overview
Microsoft System Center Data Protection Manager (DPM) is Microsofts solution for
backing up and recovering Microsoft application and system data and files by using
the VSS framework.
The EMC NetWorker Module for Microsoft Applications (NMM) client supports
DPM Server 2007 that runs on x86 and x64 machines. The EMC Information Protection
Software Compatibility Guide provides the most up-to-date lists of hardware, operating
system, service pack, and application versions supported by the NMM client.
DPM stores and manages backup information in its own database. DPM provides
backup and recovery for:
Microsoft Windows file services
Microsoft Exchange Server
Microsoft SharePoint Server
Microsoft Hyper-V Server 2008
Microsoft Virtual Server 2005
Note: NMM 2.3 does not support deduplication for DPM.
Review the following sections before starting DPM backup and recovery:
Types of DPM data for backup on page 61
Writers for DPM database backup and recovery on page 61
NMM and DPM backup and recovery scenario on page 62
DPM directed granular recovery scenario on page 63

NMM supports full backup of the following types:
DPM configuration database backup Backup of the DPM configuration

database.
DPM replica backup Backup of all or selected DPM replicas for DPM-protected
servers.
Performing DPM Server backups on page 65 provides details.
NMM supports the following types of recovery:
Granular recovery to DPM-protected clients This allows you to browse DPM

replicas and select individual folders or files for recovery. Performing a DPM
Server recovery on page 69 provides details.
In DPM granular recovery, the DPM configuration database cannot be selected.
However, NMM directed recovery is available. Performing a granular directed
recovery to a DPM-protected server on page 73 provides details.
60
DPM Server recovery This includes recovery of the following to their original
locations:
SYSTEM COMPONENTS, which includes the system volume C:\
DPM configuration database
Missing replicas in their entirety
Disaster recovery This includes recovery of the following to their original

locations:
DPM configuration database
Missing replicas in their entirety to their original locations.Performing DPM
disaster recovery on page 74 provides details.
IMPORTANT
NMM 2.3 does not support:
Transportable backup of DPM replicas. DPM replica is in a dynamic volume.
Local nontransportable hardware-based snapshots of dynamic volumes on
Windows Server 2008. The EMC NetWorker Module for Microsoft Applications
Release 2.3 Administration Guide provides more information about dynamic
volume and transportable support in NMM 2.3.
Types of DPM data for backup

NMM can back up the following DPM data:
DPM configuration database This is a SQL database. The DPM writer describes
the location of the database, and NMM uses VSS SQL writers to protect the
database.
The SQL database must be a local instance because NMM does not support
remote instances of SQL. The instance used by DPM Server must be on the same
machine as the DPM Server.
DPM replicas These are data containers that DPM uses to store its save sets.
NMM protects these as file system shares.
A DPM replica is not a VSS replica, and is not directly manipulated outside the
DPM environment.
Writers for DPM database backup and recovery

The DPM Server database can be backed up and recovered by using either of the
following writers:
SQL writer
MSDE writer
IMPORTANT
Microsoft recommends that you use the MSDE writer with DPM, if it is available.
Windows Server 2008 does not include the MSDE writer.
Overview
61
Detecting the enabled writer

To detect the writer that 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 list of SQL writer components.
On a Windows Server 2003 machine, you can enable the MSDE writer.
Enabling and disabling the MSDE writer

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.
4. To disable the MSDE writer, set the value to 1.
5. Exit Registry Editor.
6. Restart the VSS service.
NMM and DPM backup and recovery scenario

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.
In a DPM backup, the NMM software is installed on the DPM Server to protect:
The DPM Server
The replicas of the DPM-protected servers.
Figure 5 on page 63 shows how NMM provides support for backup and recovery of
DPM data.
Note: DPM Server can protect clients attached within the same domain as that of the DPM
Server.
62
NMM
protects items within
DPM Server 2007:
DPM Configuration Database
DPM Replicas
NetWorker Server
7.5.3 or later,
or 7.6.1 or later:
Provides services for
NetWorker clients,
such as NMM
DPM protects items within

Microsoft Servers:
Database files
Storage groups
Volumes
Transaction logs
LAN
Microsoft Servers:
Backup and Recovery
provided by DPM
Server 2007
DPM Server 2007:

Backup and Recovery
provided by NMM client
GEN-000754
Figure 5
NMM protection of DPM
DPM directed granular recovery scenario

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 recover the files in a DPM-protected
server replica, from the DPM Server, and direct the recovery to the DPM-protected
server computer.
The following scenario describes how DPM directed granular recovery would work
with a hypothetical FileServer1 as shown in Figure 6 on page 64.
Overview
63
NetWorker server:
Provides backup
services for
NetWorker clients,
such as NMM
LAN
DPM-protected
servers: Microsoft
Applications
SharePointServer3
SQLServer4
FileServer1
Directed Recovery:
Granular file recoveries
to DPM-protected
servers, directly from
NetWorker server,
through NMM client UI on
the DPM-protected server.
ExchangeServer2
DPM Server 2007:

NMM client provides
backup of DPM
Server and
DPM-protected
server replicas.
GEN-000958
Figure 6
Directed recovery of FileServer1
In this scenario, the FileServer1 data was backed up through the NMM client on the
DPM Server, as part of the backup of DPM replicas. In the directed recovery, an
NMM client installed on FileServer1 performs the recovery, instead of the NMM
client on the DPM Server:
1. The DPM Server protects a Windows Server client, FileServer1.
2. The NMM client on the DPM Server backs up the DPM Server, including the
protected-client replicas for the DPM Server, such as FileServer1.
3. The administrator receives a request to recover a file, LostFile, from FileServer1.
4. The administrator checks DPM to see if DPM has the recoverable data.
DPM no longer has the file that needs to be recovered. But because NMM backs
up the file server replica as part of the DPM backup, the file should exist in a
previous NMM backup of DPM.
5. The NMM client is installed on FileServer1.
6. The NMM client on FileServer1 is configured for directed recovery from the DPM
Server:
Though the file the administrator wants to recover is from FileServer1, and it is
being recovered to FileServer1, the backup was performed through a remote
client on the DPM Server.
The administrator must make the NMM client on the DPM Server available
for recovery through the NMM client on FileServer1.
7. In the NMM client on FileServer1 the administrator adds the DPM Server as an
available client.
8. Once DPM Server is an available client, the administrator can:
a. Select items for recovery from the remote client, and the DPM Server.
b. Recover the items to the local client, FileServer1.
64
Performing DPM Server backups

This section contains the following information:
DPM application information variable settings on page 65
Displaying valid DPM data save sets on page 66
URL encoding for save sets on page 66
Specifying DPM save sets for application data on page 66
Configuring DPM backups on page 67
DPM application information variable settings

Table 9 on page 65 lists the variables that can be specified in the application
information attribute of the client resource.
Table 9
DPM application information variable settings
Attribute name
Description
Values
NSR_SNAP_TYPE=value
Specifies the snapshot service

provider name.
vss
NSR_PS_SINGLE_SAVE_PER_SAVESET=
Specifies the creation of a separate

PowerSnap save set for each save set
in the client entry.
yes
NSR_PS_SINGLE_SAVE_PER_SAVESET=yes
NSR_PS_FIRST_SAVESET_SAVE=value
Specifies the save set that PowerSnap

must operate upon first. This must be
set to the DPM configuration database
save set because Microsoft
recommends that it be saved first.
This attribute should not be used if:
The DPM configuration database is
not one of the save sets.
Or
If the DPM configuration database
is the only save set.
This attribute should only be used if
the DPM configuration database is
one of the multiple save sets that is
being backed up under a single
NetWorker client resource.
Configuration database save set name

For example:
NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS:
\Microsoft DPM\DPM Database.
NSR_DPM_RETRY_WAIT=value
Specifies the wait time before

restarting the backup, if the DPM
replica is unavailable for backup
because it is in use. The default
setting is 10.
A positive integer
For example, to specify a wait time of two minutes:
NSR_DPM_RETRY_WAIT=2
NSR_DPM_RETRY_MAXIMUM=value
Specifies the total number of

timesthe first try plus retriesfor
restarting the backup.
A positive integer
For example, to specify three restart attempts:
nsr_dpm_retry_maximum=3
value
65
Displaying valid DPM data save sets

To display a list of the DPM save sets that are available for backup:
2. If the application server is not on a virtual host, type the following command at
the command prompt to list the valid application data save set names:
nsrsnap_vss_save -?
3. Press Enter:
Ensure to type each save set entry on a separate line.
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
URL encoding for save sets

Save set names may have special characters, such as the backslash (\). When
specifying such save set names in the Save Set attribute of the client resource, the
special character must be replaced by its URL-encoded value. Table 2 on page 24
provides details.
Specifying DPM save sets for application data

Table 10 on page 66 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.
Table 10
66
DPM Server 2007 save set syntax
Type of backup data
Description
Save set syntax
Configuration database
There is always exactly one DPM configuration database.
APPLICATIONS:\Microsoft DPM\DPM
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.
APPLICATIONS:\Microsoft DPM\Non VSS

Datasource Writer component
Computer%2FSystemState on server
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.
APPLICATIONS:\Microsoft
DPM\SqlServerWriter component
Luna%2FAcmeBank on server Pluto SQL
Server.
Configuring DPM backups

For full backup of DPM databases, logs, and protection groups and
administrator-selected protection groups, NMM creates snapshots, which are exact
point-in-time copies of DPM data.
DPM requires a snapshot policy that retains these snapshots. You should only retain
one snapshot and rollover all the remaining snapshots.
To perform a DPM backup, complete the tasks outlined in Table 11 on page 67.
IMPORTANT
Guide provides details for the first four tasks in Table 11 on page 67.
Table 11
Tasks for scheduling a backup

Backup task
Consideration

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.
DPM requires a snapshot policy that retains snapshots. The

backup snapshot policy must be set to All. Backup fails, if
any other value is used.
Backup schedules determine the days on which full

backups are performed. Full backups include all of the data
specified in an NMM client resource save set.

5. Configuring a DPM client resource on page 67 This task is specific to configuring a DPM client resource.
Configuring a DPM client resource

A client resource specifies what to include in a snapshot of an NMM client. Client
resources are associated with other backup resources, such as groups and snapshot
policies. You can create multiple client resources for the same NMM host. In this way,
you can apply different backup attributes to different types of information on the
same host.
When configuring a DPM client resource, it is best practice to:
1. Create a DPM client resource for the backup of the DPM configuration database
and the system database.
2. Perform the database backup before replica backups.
3. For each of the DPM-protected application server replicas, create separate
instances.
4. If creating a separate client resource, also create a separate group.
Note: NMM 2.3 requires a local instance of SQL. It does not support remote instances of SQL.
The instance used by a DPM Server must be on the same machine as the DPM Server.
67
To create a DPM client resource:

Configuration.
4. In the Name attribute, type the hostname of the NetWorker client computer.
6. From the Browse Policy attribute, select a browse policy from the list.
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 66 describes how to find the save
sets available on the DPM Server. Specifying DPM save sets for application
data on page 66 describes the DPM Server save set syntax.
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 such that the
backups for the hosts client resources do not overlap.
13. In the Backup command attribute, type the backup command:
nsrsnap_vss_save.exe
68
14. For Application Information attribute, perform either of the following:

To back up the DPM database and some or all of the replicas through a single
client resource, type the following variables and values, each on a separate
line:
NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS:\Microsoft DPM\DPM
database.
NSR_SNAP_TYPE=vss
Or
To back up only the DPM replicas through a single client resource, type the
following variables and values, each on a separate line:
NSR_SNAP_TYPE=vss
NSR_DPM_RETRY_MAXIMUM=3
Note: Do not specify the NSR_DPM_RETRY_WAIT and the
NSR_DPM_RETRY_MAXIMUM variables if the default values are acceptable. The
default is 10 minutes between attempts and a total of three attempts.
DPM replicas are rolled over one at a time. For example, if there are 10 DPM
replica save sets listed in the client resource, NMM creates 10 snapshots, one
for each replica save set, one at a time, and then rolls over the 10 snapshots,
one for each replica save set, one at a time. Because NMM cannot run multiple
groups in parallel, DPM backups take longer than other application backups.
DPM application information variable settings on page 65 provides
information about these variables and their values.
IMPORTANT
For Microsoft System Center Data Protection Manager 2007, do not check the
deduplication backup option because deduplication backup is not supported.
16. In the Aliases attribute, type the NETBIOS name for the client.
NMM client uses the host machine NETBIOS or short name when connecting to
the NetWorker server to browse backups. If the NETBIOS name is not found,
NMM will not be able to display backups.
17. Click OK.
Performing a DPM Server recovery

To recover a folder or file from a DPM replica:
Performing a DPM Server recovery
69
3. Right-click the NetWorker server in the navigation pane:

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

When NMM backs up a DPM Server, all of the DPM-protected server replicas that are
backed up are indexed to allow granular recovery of individual files in the replica.
This granular recovery of DPM replica files can be completed back to the DPM Server
which is being protected, or to the DPM-protected server. You can browse DPM
replicas and select individual folders or files for recovery.
Reviewing settings before starting recovery

The DPM Recovery Options Summary window lists the DPM recovery and
NetWorker recover options.
To review the settings before starting the recovery:
1. To change the NetWorker and DPM recover options, click Recover Options.
You can also access the settings from the DPM Recover Session view. Click
Recover Options.
2. The NetWorker Recover Options settings are specified on the General,
NetWorker, Security, and DPM tabs.
3. After specifying the options, click Start Recover to validate the options.
If all option settings are valid, the dialog box closes and recovery starts.
Recovering a folder or file from a DPM replica

To recover a folder or file from a DPM replica:
3. Right-click the NetWorker server in the navigation tree.
When performing an NMM recovery of a DPM Server, the default recovery
mode is Disaster Recovery.
When performing an NMM recovery of a non-DPM Server, the default
recovery mode is Granular, and the Disaster Recovery mode is unavailable.
Figure 8 on page 72 displays the DPM recovery modes available.
Performing DPM granular recovery
71
Figure 8
DPM recovery modes
4. In the left pane, select Recover.

Figure 9 on page 72 displays the Recover submenu.
Figure 9
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,
Figure 10 on page 72 is an example of a DPM Server tree expanded to the file
level.
Figure 10
DPM granular recovery available to file level

72

Figure 11 on page 73 displays the options available for DPM granular recovery.
Figure 11
DPM granular recovery options
9. In the Recovery path box, specify the folder where the recovered items are to be
placed.
when Start Recovery is selected. If this checkbox is cleared, options must be
through the Recover Options button on the main NMM screen.
11. Click OK.
Performing a granular directed recovery to a DPM-protected server

To perform a directed granular recovery of a DPM-protected client:
Note: The backup must be a conventional backup or a rolled over snapshot backup.
1. Install NMM on the DPM-protected client, if it is not already installed. The NMM
client on the DPM Server, and the NMM client on the DPM-protected client must
be on the same NetWorker server.
2. Open the NMM client on the DPM-protected client.
3. On the Options menu, click Configure Options.
4. Click the Refresh button, which is to the right of the client name.
5. Click the client that you want to add in the Client name menu, and then click
Add. Add or remove clients as needed.
6. Click OK.
7. Click the Client menu, and select the DPM Server NMM client that created the
backup as the current local client.
8. On the System Recover Sessions bar, select Recover Options.
The NetWorker System Recover Session Options dialog box appears.
9. On the NetWorker tab, specify the destination for the recovery in the Relocate
Recovered Data box, and then click OK.
10. In the left pane, select Recover:
a. Select DPM Recover Session.
b. Select Granular.
Performing a granular directed recovery to a DPM-protected server
73
11. In the navigation tree, select the DPM files or folders to be recovered. By default,
13. In the Recovery path box, specify the folder where the recovered items are to be
placed.
when Start Recovery is selected.
If this checkbox is cleared, options must be through the Recover Options button
on the main NMM screen.
15. Click OK.
Performing DPM disaster recovery

For DPM disaster recovery, back up either of the following on the application hosts:
The save set All attribute in the save set field of the client resource.
Or
The SYSTEM COMPONENTS:\ save set along with the system volume, for
example, C:\.
In DPM writer disaster recovery, NMM allows the DPM database and replicas to be
selectable in the file view pane of NMM. This results in selecting all missing replicas,
because replicas are not selectable individually. You can browse DPM replicas and
select individual folders or files for recovery. Performing a DPM Server recovery
on page 69 provides details.
Disaster recovery mode is not available when doing a directed recovery to a
NetWorker client, other than the DPM Server which was originally backed up. When
a remote client is selected, this mode is displayed as unavailable on the contextual
menu.
Figure 12 on page 74 displays the DPM database and replicas in the file view pane.
Figure 12
74
DPM database and replicas available as selectable items
4
Microsoft Hyper-V
Server Backup and
Recovery
Overview ........................................................................................................................ 76
Performing Hyper-V backups ..................................................................................... 82
Performing Hyper-V recovery .................................................................................... 88
Selecting the destination of Hyper-V recovery ......................................................... 90
Performing Hyper-V parent partition disaster recovery......................................... 93
Best practices.................................................................................................................. 95
Restrictions for backup and recovery of Hyper-V child partitions in a Windows
2008 and 2008 R2 failover cluster................................................................................ 97
75
Overview
EMC NetWorker Module for Microsoft Applications (NMM) provides full backup
and recovery of:
Windows Server 2008 with Hyper-V
Windows Server 2008 R2 with Hyper-V
Windows Server 2008 and Server Core Installation with Hyper-V
Hyper-V is a Windows Server 2008 and 2008 R2 role that provides hypervisor-based
server virtualization. NMM utilizes the Hyper-V VSS writer to back up and recover
the following:
Hyper-V Initial Store configuration file
Each virtual machine or child partition
NMM does not support backup of:
Microsoft Windows Server 2008 R2 cluster shared volumes
Volumes with no file system access path for Hyper-V Cluster configurations that
use this configuration
The following sections provide information that must be reviewed before starting
Hyper-V backup and recovery:
Operating system versions supported by NMM client on page 76
Integration Components version on page 77
Hyper-V parent partitions, child partitions, and applications within child

partitions on page 77
Hyper-V configuration on page 78
Hyper-V storage configurations supported by NMM on page 79
Hyper-V configuration requirements for backing up a child partition that

contains multiple volumes on page 82
Performing Hyper-V backups on page 82
Operating system versions supported by NMM client

The NMM client supports Hyper-V parent partitions that run Windows Server 2008
and Windows Server 2008 R2 installations on 64-bit, virtualization aware, CPUs:
For parent partitions, NMM supports Windows Server 2008 and Windows Server
2008 R2 with the Server Core installation.
When NMM is running in the Hyper-V parent partition, NMM can back up child
partitions that are running the following guest operating systems:
Windows Server 2008 (x86 and x64)
Windows Server 2008 R2 (x64)
Windows Server 2003 R2 (x86 and x64) SP2
Windows Server 2003 (x86 and x64) SP2
76
Windows Vista (x86 and x64) SP1

Windows XP (x86) SP3
SUSE Linux Enterprise server 10 with SP1 x86 Edition
The NMM client is supported in Hyper-V child partitions (guests). NMM

supports the same Windows Server operating systems and applications that are
supported on physical servers.
Integration Components version

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

NMM provides support for the following types of backup:
Disaster recovery backup of parent partition Does not include child partitions
and Initial Store.
Full backup of Hyper-V Writer Includes all child partitions and Initial Store.
Granular backup of Hyper-V Writer Can back up individual child partitions

and Initial Store.
Deduplication backup
Performing Hyper-V backups on page 82 provides details.

NMM provides support for the following types of recovery:
Disaster recovery of Hyper-V Server and role
Operational recovery of individual child partitions and the Initial Store
Performing Hyper-V recovery on page 88 provides details.
Hyper-V configuration
Figure 13 on page 78 illustrates a physical server running Windows Server 2008 or
Windows Server 2008 R2. The Hyper-V role has been enabled on the server, and four
child partitions have been created, each running a separate operating system and
different Microsoft applications.
Hyper-V virtual machines with child partition
operating systems and applications
Physical server with
Windows Server 2008
and 2008 R2
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

Windows Server 2003
Microsoft Office SharePoint Server 2003

Windows Server 2003

Windows Server 2003
Hyper-V configuration file
Configure client resources

on parent partition to back
up parent partition volumes
and system components
Figure 13
78
Configure client resources on parent partition to

back up Hyper-V child partitions and Hyper-V
configuration file
GEN-000959
Windows Server 2008 or Windows Server 2008 R2 host with Hyper-V 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 child partitions and configuration information on the Hyper-V Server
The applications within each child partition
Figure 14 on page 79 describes what the NMM client backs up in Hyper-V, by using
the Microsoft Hyper-V VSS writer and NMM save sets.
Parent Partition:
Windows Server 2008
or Windows Server 2008 R2
OS with Hyper-V Role
APPLICATIONS:\Microsoft Hyper-V
Save set backs up Hyper-V components, which includes
each virtual machine and the Hyper-V configuration file
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-000960
Figure 14
NMM backup of Hyper-V components
Hyper-V storage configurations supported by NMM

There are a wide variety of storage configurations available for Hyper-V child
partitions, such as passthrough disks, direct-attached storage (DAS), storage area
networks (SANs), and file servers.
The following documentation provides more details:
The Microsoft website provides more details and the most up-to-date information
about storage hardware supported by Hyper-V.
up-to-date information about what software and hardware providers are
supported for Hyper-V backup and recovery in NMM.
Figure 15 on page 80 illustrates Hyper-V storage options.
Overview
79
Hyper-V Server
Parent Partition
Child Partition
X:\V1\V1.VHD
-> VHD1
VHD1 -> C:
DAS
Disk1-> X:
passthrough
Disk 2
Disk 2 -> D:
Configuration 1
Configuration 2
SAN
FC or iSCSI
Y:\V2\V2.VHD
-> VHD2
LUN 1 -> Y:
LUN1
FC or iSCSI
passthrough
LUN 2
LUN2
VHD2 -> E:
LUN2 -> F:
iSCSI
LUN 3 -> G:
LUN3
S:
SHARE1
CIFS/SMB/
SMBv2
\\FS\SHARE1
Configuration 3
Configuration 4
Configuration 5
Configuration 6
\\FS\SHARE1\V3\V3.VHD
-> VHD3
VHD3 -> H:
File Server
GEN-000962
Figure 15
Hyper-V storage options
Table 12 on page 80 lists the Hyper-V child partition configurations.

Table 12
Hyper-V child partition configurations

Configuration
Type
VHD1 on DAS
DAS passthrough
VHD2 on LUN
LUN passthrough
iSCSI target attached within child partition
VHD3 on file server
NMM supports Hyper-V snapshots of the child partitions and the parent partition
with the Microsoft Software VSS provider or VSS hardware providers, depending on
the hardware storage type and partition type.
80
The following list describes how these configuration types are supported in NMM:
Snapshot support Snapshot support is provided for both child and parent
partitions:
Child partition NMM is running within the child partition to perform the
backup. The following storage configurations are supported for this
environment:
If using the Microsoft Software VSS provider, all configurations listed in
Table 12 on page 80 are supported.
If using a VSS hardware provider, configuration 5 (LUN exposed directly
to child partition) is supported. Currently, this support includes the EMC
VSS hardware provider with EMC CLARiiON storage. The EMC
Information Protection Software Compatibility Guide provides the latest
support information.
Parent partition NMM is run in the parent to perform the backup. The
following storage configurations are supported for this environment:
If using the Microsoft Software VSS provider, configuration 1 (VHD1) and
configuration 3 (VHD2) are supported.
If using a VSS hardware provider, configuration 3 (VHD2) is supported.
Currently, this support includes the EMC VSS hardware provider with
EMC CLARiiON storage and EMC Symmetrix VMAX storage. The EMC
Information Protection Software Compatibility Guide provides the latest
support information.
Note: When performing child partition backups while executing on the parent
partition, the Microsoft Hyper-V Writer does not include the passthrough or
child-attached iSCSI drives for a child partition. Configurations such as 2, 4, and 5 are
not supported by the Hyper-V Writer. Configuration 6 is not supported because the
VSS framework does not support network shares.
Cluster support In addition to the supported configurations listed for

snapshots, parent and child cluster scenarios support the following storage
configurations:
Child partition clustering NMM is running within the child partition to
perform the backup:
For drives configured as failover resources, configuration 5 (LUN exposed
directly to child partition) is supported as this is the only configuration
Microsoft currently supports for Windows Server 2008 Failover Clustering.
For drives configured for operating system or local drives for the cluster
nodes, the child partition support listed under Snapshot support applies.
Parent partition clustering NMM is run in the parent to perform the
backup. All configurations are supported.
Overview
81
Hyper-V configuration requirements for backing up a child partition that contains multiple
volumes
When there are multiple virtual hard disks in the guest, backup of the associated
child partition from the parent partition may fail because of a Microsoft limitation.
When there are multiple volumes on the guest, VSS determines the shadowstorage
area for the snapshots based on which volume has more space. This can lead to a
condition where volume Cs snapshot and volume Ds snapshot both reside on
volume D since volume D has more space. During the snapshot revert stage in
PostSnapshot, volume Cs snapshot may be lost if volume Ds snapshot is reverted
first.
To prepare a multiple volume guest for backup:
1. Use the vssadmin command to force the shadowstorage of each volume to be on
the same volume:
Note: These commands must be run inside each guest, not the parent physical Hyper-V
Server.
vssadmin Add ShadowStorage /For=C: /On=C:

vssadmin Add ShadowStorage /For=D: /On=D:
2. Repeat as needed for each volume in the child partition.
Performing Hyper-V backups

The following sections describe how to configure and perform a Hyper-V backup:
Hyper-V application information variable settings on page 82
Specifying Hyper-V save sets for application data on page 83
Displaying valid Hyper-V save sets on page 83
NMM support for proxy backup of Hyper-V on page 84
Preparing a child partition for backup on page 84
Configuring Hyper-V backups on page 85
Note: In NMM 2.3, backups of Cluster Shared Volumes in Windows 2008 R2 are skipped at
both file system-level (that is, contents of folder C:\ClusterStorage or
<SystemDrive>\ClusterStorage) or Hyper-V writer-level.
Hyper-V application information variable settings

Table 13
82
Hyper-V application information variable settings

Attribute name
Description
Values
NSR_SNAP_TYPE=value
Specifies the snapshot service

provider name.
vss
Specifying Hyper-V save sets for application data

Table 14 on page 83 lists the Hyper-V save set syntax to specify for supported types
of Hyper-V backup. Specify Hyper-V data save sets in the Save Set attribute of a
client resource.
Table 14
Hyper-V save set syntax
Type of backup data
Save set syntax
Hyper-V Manager
The entire Hyper-V configuration: the Hyper-V configuration file and
each child partition.
Hyper-V configuration file (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.
Hyper-V child partition

There are usually multiple child partitions on the host operating
system.
Hyper-V\virtual_machine_name
Child pertains or virtual machines can be included in a proxy backup group.
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.
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.
Displaying valid Hyper-V save sets

To display a list of the Hyper-V save sets that are available for backup:
1. Open a command prompt on the Hyper-V Server.
names:
If the Hyper-V Server is not on a cluster virtual host, type:
nsrsnap_vss_save -?
If the Hyper-V Server is on a cluster virtual host, type:
nsrsnap_vss_save -? -c cluster_virtual_server_name
Note: If the application server is on a cluster virtual host, run the command from the
physical node that is currently hosting the application server.
3. Press Enter:
line.
The following example shows the application data save sets that are available on
a Hyper-V system with two child partitions, child_partition_name_1 and
child_partition_name_2:
Hyper-V
Hyper-V\Initial Store
Hyper-V\child_partition_name_1
Hyper-V\child_partition_name_2
83
The list of Microsoft Hyper-V save sets will include the top-level entry for
Microsoft Hyper-V, the configuration file, and all the child partitions if any exist.
Note: NMM 2.3 does not support back up of Hyper-V child partitions in Hyper-V 2008 R2
Cluster Shared Volumes (CSV). So, when you run the command nsrsnap_vss_save -? on a
active node of Hyper-V cluster, CSV child partitions are not listed as valid Hyper-V save sets.
NMM support for proxy backup of Hyper-V

NMM does not support SAN boot configurations, where a hardware snapshot of the
system drive is performed. The Microsoft Hyper-V writer requires that the
configuration component Initial Store always reside on the system partition. This path
cannot be changed.
NMM supports proxy backup for child partitions. Child partition-only save sets can
be specified in a proxy backup group:
APPLICATIONS:\Microsoft Hyper-V\virtual_machine_name_1
The Microsoft Hyper-V save set and configuration file (Initial Store) save set cannot
be specified in a proxy backup group:
Preparing a child partition for backup

Before NMM can create a backup of a Hyper-V child partition, Integration Services
must be installed on the child partition. These services provide integration between
the physical server and the child partitions, such as time synchronization, guest
operating system shutdown messaging, and backup support:
84
Integration Services can only be installed after the guest operating system has
been installed on the child partition.
To install Integration Services, on the child partition guest system, click the
Action > Insert Integration Services Setup Disk, and then click the .exe to run
setup.
When Windows Server 2008 or Windows Server 2008 R2 is installed as the

operating system on a guest system, Integration Services are installed by default.
Configuring Hyper-V backups

Table 15 on page 85 describes the backup tasks for the Hyper-V parent and child
partitions.
Table 15
Backup tasks for Hyper-V (page 1 of 2)
Hyper-V parent partition
Tasks
On the parent partition

Windows volumes:
Volume data, such as a drive letter, for example, D:\.
A file system path, such as D:\ data.
Windows system components, such as:
The registration database
Windows Cluster and so on
Other Window system components
The EMC NetWorker Module of Microsoft Applications Release 2.3
Administration Guide provides the list.
Complete tasks 1 through 7:
On the parent partition

The Hyper-V role can coexist with other Microsoft applications, such as:
SQL Server
SharePoint Server
Exchange Server
System Center DPM Server
Windows Server Cluster
Hyper-V on parent partition

Hyper-V child partitions and Initial Store configuration file
Note: The EMC NetWorker Module of Microsoft Applications Release 2.3

Administration Guide provides details about tasks 1 through 7.
1.
2.
3.
4.
5.
6.
7.
Configure a backup pool for snapshot operations

Configure snapshot policies
Configure a client resource
Configure privileges
Configure a proxy client
Note: The NetWorker Module of Microsoft Applications Release 2.3

1. Configure a backup pool for snapshot operations
5. Configure a client resource
6. Configure privileges
7. Configure a proxy client
Configure application backups Specific instructions for the application are
provided in:
Performing Exchange Server backups on page 115
Performing Exchange 2010 backups on page 164
Performing SharePoint Server 2003 backups on page 183
Performing DPM Server backups on page 65
Configure Windows Server cluster backups Specific instructions for the
application are provided in the EMC NetWorker Module of Microsoft
Applications Release 2.3 Administration Guide.
Note: The EMC NetWorker Module of Microsoft Applications Release 2.3
1.
2.
3.
4.
5.
Configure a backup pool for snapshot operations

Configure snapshot policies
Configuring a Hyper-V client resource on page 86
85
Table 15
Backup tasks for Hyper-V (page 2 of 2)
Hyper-V parent partition
Tasks
Hyper-V child partition applications

Microsoft application data, such as:
SQL Server
SharePoint Server
Exchange Server
System Center DPM Server
Windows Server Cluster
Configure application backups Specific instructions for the Microsoft

application are provided in:
Performing Exchange Server backups on page 115
Performing Exchange 2010 backups on page 164
Performing DPM Server backups on page 65
Configure Windows Server cluster backups Specific instructions for the
application are provided in the EMC NetWorker Module of Microsoft
Applications Release 2.3 Administration Guide.
Note: Hyper-V child partition snapshots are not related to NMM or NetWorker snapshots.
Hyper-V child partition snapshots are created, viewed, and applied to the child partition
through Hyper-V Manager. When NMM backs up a Hyper-V child partition, the Hyper-V
child partition snapshots are part of that backup.
Configuring a Hyper-V client resource

policies.
You can create multiple client resources for the same NMM host. In this way, you can
apply different backup attributes to different types of information on the same host.
For example, if the NMM host is an Exchange Server, you can:
Create one client resource to back up the Exchange databases.
Create another client resource to back up Windows system component data.
This allows you to back up Exchange databases many times a day and back up
Windows system component data only once a day.
To create a Hyper-V client resource:
Configuration.
4. In the Name attribute, type the hostname of the NetWorker client computer.
6. From the Browse Policy attribute, select a browse policy from the list.
7. From the Retention Policy attribute, select a retention policy from the list.
86
9. In the Save Set attribute, specify the components to be backed up. Place multiple
entries on separate lines:
To back up all of Hyper-V child partitions and the Initial Store configuration
file, specify:
To back up the child partitions, specify:

To back up the Initial Store configuration file, specify:

Note: The Microsoft Hyper-V save set and Initial Store configuration file save set cannot be
specified in a proxy backup group:
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 such that the
backups for the hosts client resources do not overlap.
13. In the Access area, leave the following fields empty:
Remote user
Password
15. In the Application information attribute:

a. Type the following variable and value:
NSR_SNAP_TYPE=vss
NSR_DATA_MOVER=<proxy_client_name>
b. Type application variable settings and their values on separate lines.

87
19. If a proxy client is being set up for the NMM client, type the hostname of the
proxy client in the Remote Access attribute.
If the NMM is part of a cluster, type the names of the physical nodes of the cluster
in the Remote Access attribute.
20. Click OK.
Performing Hyper-V recovery

After the files are backed up, you can recover all of the Hyper-V components, the
Initial Store configuration file, or individual child partitions, depending on what was
specified in the backup save set.
The following sections describe Hyper-V recovery:
Turning the child partition offline for recovery on page 88
Hosting the recovered virtual systems on page 88
Specifying the destinations for the Hyper-V configuration files and virtual
system on page 89
Selecting Hyper-V recovery options on page 89
Turning the child partition offline for recovery

A child partition must be offline before recovery can start. If the child partition is
online at the time recovery is started, the Hyper-V writer first turns off the child
partition.
Once the child partition is offline, the current child partition is destroyed, the
recovery version is restored, and the child partition is registered.
The Hyper-V writer automatically detects whether the child partition is online, and
turns it off. No action is required by you.
Hosting the recovered virtual systems

The Destination Host page allows you to specify the server on which you want to
host the recovered virtual systems.
To recover to the same location as the original:
1. Select Recover (Overwrite) Virtual System to original location.
The Finish button is available and Next button is unavailable when this option is
selected.
2. Click Finish.
The Finish button validates the server location and displays the Hyper-V
Recovery Options page.
88
Specifying the destinations for the Hyper-V configuration files and virtual system
The Destination Path page allows you to specify the destination for the Hyper-V
configuration files, and the destination for each virtual system.
To change settings on this page:
1. In the Destination for Hyper-V configuration files dialog box, click Browse to
change the destination path.
The Select Virtual System Destination list displays the destinations for each
virtual system VHD.
2. To change a destination:
a. Select a virtual system.
b. Click Change Destination.
The Remote Directory Browser dialog box appears.
3. Click Finish to validate the settings.
If the destinations are valid, the Hyper-V Recovery Options Summary dialog
box appears.
Selecting Hyper-V recovery options

The Recovery Options Summary page lists the Hyper-V Recovery and NetWorker
Recover Options. This allows you to review the settings before starting the recovery.
The Hyper-V Recovery Options page appears when you click Recover in the Hyper-V
Recover Session view or at the end of the Hyper-V Recovery wizard. This page
displays the settings specified in the Destination Host Selection page and Destination
Path page.
To change the Hyper-V recovery options:
If you have reached this page through the Hyper-V Recover Session toolbar:
a. Click Cancel > Advanced Options.
The Hyper-V Recovery Options wizard starts.
b. In the Hyper-V Recovery Options wizard, click Back.
If you have reached this page through the Hyper-V Recover Session view, click
Advanced Options on the Hyper-V Recover Session toolbar.
To change the NetWorker recover options, either:
Click Recover Options.

Or
In the Hyper-V Recover Session view, click Recover Options on the Hyper-V
Recover Session toolbar.
The NetWorker Recover Options settings are specified on the General, NetWorker,
and Security tabs.
To validate all pages, click Start Recover. If all pages are valid, the wizard closes and
recovery starts.
Performing Hyper-V recovery
89
Selecting the destination of Hyper-V recovery

The destination of the Hyper-V recovery can be selected:
To the original machine Performing Hyper-V recovery to the original

machine and location on page 90 provides details.
To a different machine or location Performing directed Hyper-V recovery to a

different machine or location on page 91 provides details.
Note: When a Hyper-V recovery is performed on Windows Server Core 2008 or Windows
Server Core 2008 R2, the recovery is a directed recovery.
Performing Hyper-V recovery to the original machine and location

To recover Hyper-V components to the original machine and location:
1. Open the NMM software and select the NetWorker Server on which the NMM
software was configured for backup.
If NMM is part of a cluster, select the physical client to which you are recovering
data. The physical client can be selected from the Client list attribute in the
application toolbar.
2. From the left pane, select Recover > Hyper-V Recover Session.
3. From the navigation tree, select the Hyper-V writer or individual child partitions
under the Hyper-V writer.
4. From the Hyper-V Recover Session toolbar, click Recover.
The Hyper-V Recover Session Summary dialog box appears.
5. If all the options look correct, go to step 11. If you want to change options, go to
step 7.
6. Click Recover Options.
7. On the General tab, specify the Diagnostic Output Level.
8. On the NetWorker tab, specify the Restore Type, and select or clear Terminate
recover of item, if errors are encountered.
Note: Restore of Hyper-V components requires a Restore Type of Conventional Restore.
9. On the Security tab, specify pass phrases if any are needed.

10. Click OK to close the Hyper-V Recover Session Options dialog box.
11. Click Start Recover.
NMM validates all pages. If all pages are valid, recovery begins.
90
Performing directed Hyper-V recovery to a different machine or location

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

Hyper-V Server, the child partition that is recovered is taken offline and the
data is recovered to the alternate location. The child partition is then
registered pointing to the data in the new location.
You can remove the Virtual Hard Disk (VHD) files of the original child
partition manually after the recovered Hyper-V child components are up and
running.
Selecting the destination of Hyper-V recovery
91
To recover to a different Hyper-V Server:

a. Click Recover Virtual System to a different Hyper-V Server.
b. From the Select Remote Host list click the server you want to recover to.
c. Click Next.
The Destination Path page appears, where you can specify a destination
for each Virtual System.
d. Click Browse to specify the destination location for the configuration files.
After selecting the destination location for the configuration files, you can
change the destination location for the child partitions virtual disks.
e. To change the destination location for a virtual disk, select the child
partitions virtual disk in the list, and then click Change Destination.
Repeat as needed for each virtual disk destination that you want to change.
f. When you have completed changing destinations, go to To perform
validation and start recovery: on page 92.
Note: The destinations provided on this page are Microsoft's default configuration file
locations and may not match your Hyper-V configuration. Change the destination as
needed.
When a directed recovery is attempted to a different Hyper-V Server and the

destination Hyper-V Server has an existing child partition with the same name
as the one being recovered, then this child partition is taken offline and the
data is recovered to the alternate location. The child partition being recovered
is then registered pointing to the data in the new location.
You can remove the VHD files of the original child partition present earlier
with the same name manually after the recovered Hyper-V child components
are up and running.
To perform validation and start recovery:
1. Click Finish.
NMM performs validation:
If the validation is not successful, an error message is displayed.
If the validation is successful, a Summary page is displayed listing the
Hyper-V and NetWorker Recover options specified.
If you need to change any of the options, click the Recover Options or Back
button.
2. Click Start Recover:
NMM validates all pages.
If all pages are valid, recovery begins.
92
Restrictions on relocating and restoring to other locations

Hyper-V has several restrictions on relocating and restoring to other locations:
Directed recover or relocated recover of Hyper-V objects on a Hyper-V Server

cluster is not supported.
Restoring Hyper-V child partitions to non-Hyper-V Servers is not supported.
Relocation recover of Initial Store is not supported.
Relocation or redirection of NMM Hyper-V backups taken before an NMM 2.3

upgrade is not supported.
When a child partition is redirect recovered to a second Hyper-V Server, the user
must update the Network Adapter settings of the child partition with the Hyper-V
Manager before starting the child partition.
Performing Hyper-V parent partition disaster recovery

Successful disaster recovery starts with good backups at all levels on the Hyper-V
physical server. The frequency of these backups depends on your retention policies,
the frequency that the data on your servers and applications changes, and the type of
application.
IMPORTANT
As part of disaster recovery plan, back up either of the following on the application
hosts:
- The save set All attribute in the save set field of the client resource.
or
- The SYSTEM COMPONENTS:\ save set along with the system volume, for
example C:\.
Regardless of the frequency of your backups, disaster recovery must proceed in a
specific order starting with the host machine and ending with the application data on
your child partition guests. Figure 16 on page 94 describes the order and types of
recovery.
Performing Hyper-V parent partition disaster recovery
93
Hyper-V virtual machines with guest

operating systems and applications
Physical server with
Windows Server 2008
and 2008 R2
host operating system

Windows Server 2008 x64
4. On each guest, recover the

applications using the recovery
process appropriate for each
application.

Windows Server 2003
Microsoft Office SharePoint Server 2003

Windows Server 2003

Windows Server 2003
Hyper-V configuration file
1. On the physical server

host, recover the host
volumes and system
components.
2. Re-enable the Hyper-V
role.
Figure 16
3. On the physical server host, recover the

Hyper-V virtual machine guests and
Hyper-V configuration file.
GEN-000961
Disaster recovery order for a Hyper-V Server
Full disaster recovery requires that the following backups are performed ahead of
time on a regular schedule:
Physical host:
Application data
Windows volumes
Windows system components
Hyper-V on host: Hyper-V child partitions and Initial Store configuration file
Hyper-V in-guest: Application data
IMPORTANT
Before starting disaster recovery, ensure the target machine is up to date with the
Hyper-V Update for Windows Server 2008 x64 Edition (KB950050). This article
and download is available from the Microsoft Download Center.
To perform a Hyper-V host disaster recovery:
1. Review best practices:
Best practices on page 95
Windows 2008 and 2008 R2 failover cluster on page 97
2. Recover the physical host that was backed up by NMM.
94
Guide provides more information about recovering the NMM client.
3. Re-enable the Hyper-V role on the host.
Consult Microsoft documentation for information about enabling the Hyper-V
role on Windows Server 2008 and Windows Server 2008 R2.
4. On the host, perform a recovery of Hyper-V as described in Performing Hyper-V
recovery on page 88.
5. From within each guest, perform a recovery of each application by using the
appropriate procedure for the application.
Guide provides more information about recovering applications, including links
to specific recovery steps for each application.
Best practices
This section provides the best practices for:
Hyper-V parent partition backup and recovery on page 95
Hyper-V child partition applications backup and recovery on page 96
Hyper-V parent partition backup and recovery

This type of backup uses the Hyper-V writer on the parent partition:
To get the most benefit from the Hyper-V role, create separate child partitions for
each application, so that the application-type backup and recovery performed at
the host-level is only for Hyper-V.
After disaster recovery of the parent partition, you may need to recover
applications within each child partition:
If you are performing separate child partition backups.
These backups are more recent than the complete parent partition backups.
Performing Hyper-V parent partition disaster recovery on page 93 provides a
complete list of these tasks.
Best use for this type of backup is Bare Metal Recover of a guest and for recovery
of operating system roles.
Best practice for Initial Store backup is to back up when Hyper-V configuration
changes are made. Initial Store does not need to be backed up each time a child
partition guest is backed up.
In NMM, the Hyper-V writer does not support backup of the configuration file
Initial Store to a proxy client.
The primary purpose for restoring Initial Store in NMM is for disaster recovery of
the Hyper-V Server.
Back up DPM Server, Exchange Server, SQL Server, or SharePoint Server

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.
Best practices
95
There is no child partition log management. For example, Exchange logs are
not truncated.
Roll-forward recovery is not available for child partition level disaster scenarios.
From a parent partition, a roll-forward recovery of a child partition is not
possible. Recoveries from a parent partition are point-in-time (disaster recovery).
Child partition pass-through disks are skipped during Hyper-V parent partition
backup.
Basic disks are supported only within child partitions.

Note: Backup of dynamic disks within child partitions is not supported. The guest
snapshot is mounted during the Hyper-V backup process, and this changes the disk
signature on dynamic disks in a guest.
Any VSS hardware or software provider can be used. The hardware provider
must support Windows 2008 extensions for AutoRecoverable snapshots.
Windows Server 2008 and Windows Server 2008 R2 Failover Clustering is

supported Allows you to configure failover of child partition.
EMC storage connected to Fibre Channel or iSCSI storage can be used in the
parent to host child partitions.
Do not take a Hyper-V VSS parent partition snapshot of Hyper-V child partitions
that are part of a SharePoint farm.
To back up SharePoint on the Hyper-V child partition:
a. Install the NMM client on the child partition.
b. Perform the Share Point backup locally from within the child partition.
The Microsoft website provides recommendations and requirements about using

SharePoint and Hyper-V together.
Hyper-V child partition applications backup and recovery

This type of backup and recovery is performed within the child partition, and uses
application and system components writers available on that child partition:
Microsoft recommends using backups within the child partition as the preferred
method for Exchange backup and recovery.
NMM supports roll-forward recovery for Exchange, when Exchange is backed up

within the child partition.
Within child partitions, standard application backup and recovery rules and
capabilities apply, including roll-forward recoveries.
VSS hardware providers for iSCSI storage are supported for iSCSI disks that are
native within the child partition.
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 VMAX is supported. Symmetrix DMXTM 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.
96
The proxy cannot be the host machine, and it must match the operating
system version of the child partition. This requirement is independent of
Hyper-V.
Child partition pass-through disks are skipped in Hyper-V parent partition

backup and are supported by backups within the child partition.
Windows Server 2008 Failover Clustering with iSCSI storage is supported.
Child partition Windows Server 2008 Failover Clustering with Fibre Channel
storage is not supported because SCSI-3 is not supported in Hyper-V child
partitions.
Windows Server 2003 Clustering is supported, but at the time of this NMM 2.3
release, Microsoft has not issued a support statement for it.

Windows 2008 and 2008 R2 failover cluster
When a Hyper-V child partition resides on a physical host, which is part of a
Windows 2008 Failover Cluster, you cannot back up or recover the child partition as
part of the cluster virtual server.
For example, consider the following Failover Cluster setup:
A cluster, Cluster_Virtual_Name, contains two physical machines,

Physical_Machine_1 and Physical_Machine_2.
Physical_Machine_1 contains two child partitions, VM1 and VM2.
You want to back up and recover VM1.

If you create a NetWorker client resource for:
Cluster_Virtual_Name, backup and recovery of VM1 through that client resource is

not supported.
Physical_Machine_1, you can specify:

Backup of the Hyper-V application (APPLICATIONS:\Microsoft Hyper-V).
This includes all child partitions on the physical machine.
An individual child partition VM1 (APPLICATIONS:\Microsoft
Hyper-V\VM1).
You can recover VM1 from the NW client resource of the physical machine,
Physical_Machine_1. This type of recovery is described in Performing Hyper-V
recovery to the original machine and location on page 90.
You can use redirected recover to recover VM1 from the NetWorker client resource of
the physical machine, Physical_Machine_1 to the Physical_Machine_2. This type of
recovery is described in Performing directed Hyper-V recovery to a different
machine or location on page 91.
Restrictions for backup and recovery of Hyper-V child partitions in a Windows 2008 and 2008 R2 failover cluster
97
98
5
Microsoft Exchange
Server Backup and
Recovery
Overview ...................................................................................................................... 100

Performing Exchange Server backups ...................................................................... 115
Performing Exchange Server recovery..................................................................... 132
Selecting a storage group restore destination ......................................................... 149
Performing Exchange Server 2007 directed recovery ............................................ 150
Performing Exchange Server 2007 disaster recovery............................................. 152
Performing a quick recovery of a deleted mailbox in Exchange 2007................. 158
Best practices................................................................................................................ 158
99
Overview
Backup and recovery of Microsoft Exchange Server 2003 and Microsoft Exchange
Server 2007 by using EMC NetWorker Module for Microsoft Applications (NMM)
involves the following:
Exchange Server 2003 and Exchange Server 2007 support for Microsoft Volume
Shadow Copy Service (VSS) through Microsoft-supplied application writers.
Creation of point-in-time copy of data, which is called a snapshot and allows

backup of the Exchange Server while the Exchange database is online or in use.
Review the following sections before starting Exchange Server backup and recovery:
100
Exchange Server versions supported by NMM client on page 101
NMM and Exchange Server support for I18N on page 101
Microsoft Exchange Server 2007 MAPI client and Collaboration Data Objects
support on page 101
Types of supported backup on page 101
Backup levels on page 102
Types of supported recovery on page 102
Compatibility with previous Exchange Server backups on page 103
Creation of shadow copy and snapshot process in an Exchange Server

production on page 103
Configuring snapshots on page 104
LAN-based Exchange Server configuration with a storage area network and a

proxy client on page 105
Exchange backup scenarios on page 107
Exchange recovery scenarios on page 112
Writers for Exchange 2003 and 2007 backup and recovery on page 114
Commands and attributes for Exchange backup and recovery on page 114
Configuring dedicated storage node for Exchange 2007 CCR environment on

page 114
Exchange Server versions supported by NMM client

that are supported by the NMM client.
NMM client supports the following versions of Exchange Server:
Exchange Server 2003 (x86) SP2
Exchange Server 2007 (x64) SP1 or later
Exchange 2007 SP3 Rollup 1 on Windows 2008 R2 (x64)
Note: NMM does not support Exchange Server 2000 or earlier.
NMM and Exchange Server support for I18N

For I18N support, Microsoft requires that the Exchange Server 2003 storage group
names are in the same locale as the Exchange Server.
Microsoft Exchange Server 2007 MAPI client and Collaboration Data Objects support
In Exchange Server 2007, the Messaging API (MAPI) and Collaboration Data Objects
(CDO) kit is required for Recovery Storage Group (RSG) support.
Access to Exchange messaging stores utilized by NMM mailbox backups requires the
MAPI and CDO kit. The MAPI client libraries and CDO are not included with
Exchange Server 2007 and can be downloaded from Microsofts website.
For information on downloading and installing this package, search for Microsoft
Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" on the Microsoft
Download Center website. Download version 6.5.8211.0.
Types of supported backup

NMM supports the following types of backup:
By using Microsoft VSS software provider:

For Exchange Server 2003:
Point-in-time snapshot backup
Single server backup
Virtual server cluster backup
For Exchange Server 2007: Exchange Server 2007 supports all the backup
options listed for Exchange Server 2003. In addition, Exchange Server 2007
provides support for:
Single Copy Cluster (SCC) backup
Local Continuous Replication (LCR) backup of the production data, but
not of the replicated data
Cluster Continuous Replication (CCR) active node and passive node
backup
Overview
101
Note: You can use deduplication for Exchange Server 2007 backup in a CCR
environment. The EMC NetWorker Module for Microsoft Applications Release 2.3
Administration Guide provides in-depth information about deduplication.
Configuring deduplication backups in a CCR environment for a passive node on
page 128 provides steps for configuring an Exchange client resource for
deduplication backups in a CCR environment.
By using EMC hardware providers, EMC CLARiiON or EMC Symmetrix:

Proxy node backup
Proxy storage node backup
Performing Exchange Server backups on page 115 provides information about how
to perform Exchange backups.
Backup levels
Table 16 on page 102 described the backup levels supported by NMM:
Table 16
Exchange 2003 and 2007 backup levels

Level of
backup
Supported in
Description
Full
Exchange Server 2003 and

Exchange Server 2007
A full backup is a complete backup that archives every

selected database and all necessary log files. Log files
older than the checkpoint at the time the backup was
started are deleted after the backup completes. If you
perform a full backup on a daily basis, you can prevent
log files from consuming space on the hard disk.
Incremental
An incremental backup backs up only selected data, and

therefore improves backup performance by reducing the
amount of data that is processed. However, recovery
may take longer because you are recovering the last full
backup plus each incremental backup that was
performed since the full backup.
Note: Incremental backups are not

supported for Exchange Server
2003.
Types of supported recovery

NMM supports the following types of recovery:
For Exchange Server 2003:

Roll-forward recovery This kind of recovery can be performed when the
current log files are available. Roll-forward recovery allows granular selection
down to the individual mailbox database level, and the recovery is performed
on the last backup that was performed. No data is lost with this type of
recovery.
Deleted e-mail is not recovered.
Point-in-time recovery This kind of recovery can be performed when log
files are lost. All new data created after the last backup is lost. Only the
transaction files that were part of the backup set are restored.
Deleted e-mail can be recovered.
102
Rollback recovery This kind of recovery is also known as destructive

recovery, because all changes that are made after the snapshot is created 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 specifies only that storage group for backup.
Exchange Server 2007 Exchange Server 2007 supports all the recovery options
listed for Exchange Server 2003. In addition, Exchange Server 2007 provides
support for:
Database recoveries to Exchange RSG.
Mailbox item-level recoveries from Exchange RSG databases.
Exchange RSG mailbox browsing, mailbox, folder, and message recovery.
Exchange database recoveries to alternate servers and storage groups that are
in the same Exchange domain.
Performing Exchange Server recovery on page 132 provides details about

Exchange 2003 and 2007 recovery.
Compatibility with previous Exchange Server backups

Exchange databases and logs that were backed up by using NMM 2.2 SP1 or earlier,
can be recovered by using NMM 2.3.
If you have upgraded to NMM 2.3 from NME, perform a full backup of Exchange
Server to perform NMM point-in-time recovery in the future. The EMC NetWorker
Module for Microsoft Applications Release 2.3 Installation Guide and EMC NetWorker
Module for Microsoft Applications Release 2.3 Administration Guide provide details.
If you want to upgrade the Exchange Server that you are currently using, including
Exchange Service Pack upgrades, perform a full backup before the upgrade. For
example, if you have Exchange Server 2007 SP2 Rollup 4 installed on Windows
Server 2008 SP2 (x64) CCR environment and want to upgrade to Exchange 2007 SP3
Rollup1:
1. Perform a full backup.
2. Upgrade to Exchange Server 2007 SP3 Rollup1.
3. Perform a recovery on Exchange Server 2007 SP3 Rollup1. The recovery is
successful.
Creation of shadow copy and snapshot process in an Exchange Server production

In NMM 2.3, the creation of shadow copy is separate from the notification to VSS
writers that backup is complete. NMM registers the shadow copy as a snapshot and
backs it up to media successfully before the notification is sent to the VSS writers. If
the backup to media fails, then that failure is reported to the Exchange VSS writer and
log truncation does not occur.
Overview
103
Configuring snapshots
Note: The information in this section is applicable to Exchange Server 2003, Exchange Server
2007, and Exchange Server 2010.
Snapshots can be retained only for full level backups but cannot be retained for
incremental level backups:
Use the NSR_EXCH_RETAIN_SNAPSHOTS=yes attribute to configure persistent

snapshots for full backups.
Use the serverless backup policy for incremental level backups because the data
must be rolled over. The EMC NetWorker Module for Microsoft Applications Release
2.3 Administration Guide provides details about serverless backup policy.
To configure local Exchange snapshot retention on an NMM client for full-level

backup, perform the following configuration tasks on the NetWorker server:
1. In the NMM client, click Properties > Apps & Modules tab.
2. Add the following attribute in the Application Information field:
NSR_EXCH_RETAIN_SNAPSHOTS=yes
A warning message is displayed in the NMM.raw log:

The specified snapshot policy allows snapshots to be stored locally
on the client for a period of time before expiration. Locally
stored snapshots present a risk of data loss if there is a failure
of the local media containing the snapshot, or if a snapshot
rollover fails and the corresponding locally retained snapshot
expires before a manual rollover can be performed. Group: "%s"
Snapshot Policy: "%s" Snapshots Per Day: "%s" Retain: "%s" Backup
Snapshots: "%s" Level: "%s".
3. In the Properties window, for the snapshot policy to be used:

a. Set the number of snapshots that you want to retain on the NMM client in the
Retain Snapshots field.
Note: For both Exchange 2007 and Exchange 2010 incremental backups, set the Retain
Snapshots value as 0. Otherwise, an error will occur and the following error message
will be displayed:
NMM .. Error: Local retention of snapshots is not allowed when snapshot level is not
set to "full". Group: "%s" Snapshot Policy: "%s" Snapshots Per Day: "%s" Retain: "%s"
Backup Snapshots: "%s" Level: "%s".
NMM.. Unable to continue backup. "APPLICATIONS:\Microsoft Exchange 2007"
snapshot policy requirements are not met.
b. Type First, Last, All, every n, or n in the Backup Snapshots field for the
snapshots that you want to rollover to the NetWorker server on a daily basis.
None and 0 are invalid entries for this field.
This configuration results in the most recent x backups being stored locally on
the NMM client, where x is the number added in the snapshot policy's Retain
Snapshots field. If the snapshot policy designates a backup to be rolled over to
the server, it will also be retained locally until there are x newer snapshots
present.
104
The snapshots are stored locally on the NMM client and not on the NetWorker server.
Snapshots that are stored locally only present a risk of data loss in the following
situation:
1. There is a failure of the local media containing the most recent snapshot, which
has not been backed up to a NetWorker server.
2. A need then arises to recover an Exchange database or storage group after the
failure of the snapshot storage media, but before another snapshot is created.
3. Because the most recent snapshot is unavailable, it is necessary to restore from an
older snapshot, and data newer than that snapshot is lost.
LAN-based Exchange Server configuration with a storage area network and a proxy client
Figure 17 on page 106 illustrates LAN-based Exchange Server configuration with a
storage area network and a proxy client:
The NMM client must be installed on both the Exchange Server and the proxy
client, and the NMM client version must be the same on both.
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 NMM client is installed.
2. The Exchange Server with the NMM client creates a snapshot of the data on the
storage volume.
Note: In Figure 17 on page 106, snapshots are represented by S1 through S5.
3. The snapshot is made visible to the proxy client.

4. NMM runs the eseutil consistency check for Exchange on the proxy host.
5. If the consistency check is successful, NMM commits the shadow copy.
6. The proxy client uses a snapshot in primary storage to transfer the data over the
LAN and into a conventional backup medium, such as, a file type disk, advanced
file type disk, or tape.
7. Once backup is complete and successful, a notification is sent by NMM to VSS
about it. VSS in turn notifies the Exchange writer that the backup is complete and
successful. Logs may or may not be truncated and this decision is taken by
Exchange. Exchange also decides which logs to be truncated and when. Logs may
be truncated but not immediately.
The EMC VSS provider is used for the transportable snapshot.
Overview
105
When the shadow copy is moved 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, a SAN storage node
must be configured as a proxy client.
NetWorker server
7.5.3 or later, or 7.6.1 or later
LAN
Proxy client
NMM
Exchange server
NMM
SAN
Primary storage
(For example,
CLARiiON or Symmetrix)
S4
S5
S1
S3
NetWorker
Traditional
storage
storage
node 7.5.3 or later,
or 7.6.1 or later
S2
GEN-000749
Figure 17
106
Snapshot process with Exchange production server and proxy client
Exchange backup scenarios

This section describes the various Exchange backup scenarios and the respective
configurations requirements:
Exchange Server 2003 virtual server cluster on page 107
Exchange Server 2007 single server backup with VSS software provider on
page 107
Exchange Server 2007 SCC backup on page 108
Exchange Server 2007 CCR active node and passive node backup with a VSS
software provider on page 109
Exchange Server 2007 proxy node and proxy storage node backups with EMC
CLARiiON and EMC Symmetrix VSS hardware providers on page 111
IMPORTANT
The Microsoft documentation and Microsoft website provide details about these
backup technologies.
Exchange Server 2003 virtual server cluster
In Exchange 2003, a cluster consists of individual computers, also called nodes, that
function cohesively in a cluster service. These computers act as network service
providers or as reserve computers that assume the responsibilities of failed nodes.
Depending on how you configure your cluster, clustering can simplify the process of
recovering a single server from disasters.
In a clustering environment, the Exchange Server runs as a virtual server and not as a
stand-alone server, because any node in a cluster can assume control of a virtual
server. If the node running the Exchange virtual server experiences problems, the
Exchange virtual server goes offline for a brief period until another node takes
control of the Exchange virtual server.
Configuring a client resource for Exchange virtual server cluster backups on
page 123 provides the steps for configuring standard Exchange client resources for
Exchange Server 2003 virtual server cluster environment.
Exchange Server 2007 single server backup with VSS software provider
Exchange Server 2007 introduces role-based deployment. With this feature, you can
deploy specific server roles that provide messaging functionality. A server role is a
unit that logically groups the required features and components that are required to
perform a specific function in your messaging environment.
Figure 18 on page 108 illustrates how Exchange 2007 provides the following five
distinct server roles that align to how messaging systems are typically deployed and
distributed:
Client access
Edge transport
Hub transport
Mailbox
Unified messaging
Overview
107
Figure 18
Multiple server roles that coexist on a single computer
Configuring a client resource for Exchange stand-alone, LCR, or SCC backups on

page 125 describes the steps for configuring standard Exchange client resources for a
single server backup with a VSS software provider.
Note: Use the NetWorker client to back up the transport servers. NMM is not required for
backing up the transport servers as there are no storage groups to back up.
Exchange Server 2007 SCC backup

Exchange Server 2007 SCC is a clustered mailbox server that uses shared storage in a
failover cluster configuration to allow multiple servers to manage a single copy of the
storage groups. This feature is similar to the clustering features in previous versions
of Exchange. However, some significant changes and improvements that have been
made.
The improvements include the following:
Improved setup experience The setup process for a clustered mailbox server in
a single copy cluster is very different from the setup process used in previous
versions of Exchange:
In previous versions, when Exchange setup was complete there were
additional tasks that were required to be performed by using Cluster
Administrator before a clustered mailbox server (referred to in previous
versions as an Exchange virtual server) was created.
In Exchange 2007, clustered mailbox server installation is integrated into the
Exchange setup. As a result, the clustered and non-clustered setup experience
is similar which reduces the learning curve traditionally associated with
clustered applications. In addition, when setup is complete, a clustered
mailbox server is created.
Optimized default settings In previous versions, after the clustered mailbox

server was created, additional administrative tasks had to be manually
performed to configure the clustered mailbox server for optimal behavior.
In Exchange 2007, each clustered mailbox server is configured with the optimal
settings during setup. Doing so eliminates the need to perform these tasks
manually.
108
Improved management experience In previous versions, Cluster

Administrator was required for several management tasks, such as stopping and
starting a clustered mailbox server and moving a clustered mailbox server
between nodes in the cluster:
In Exchange 2007, these tasks and new clustered mailbox server management
tasks have been integrated into the Exchange management tools. For example,
you can use the Exchange Management Shell to stop, start, and move
clustered mailbox servers.
In Exchange 2007 SP1 or later, you can also use the Exchange Management
Console to stop, start, and move clustered mailbox servers.
SCC architecture
As illustrated in Figure 19 on page 109, SCCs require the use of a shared-nothing

architecture, which includes shared disk storage. In a shared-nothing architecture,
although all nodes in the cluster can access shared data, they cannot access it at the
same time.
For example, if a physical disk resource is assigned to node 1 of a two-node cluster,
node 2 cannot access the disk resource until node 1 is taken offline, fails, or the disk
resource is manually moved to node 2.
Mailbox server
Active Node
Mailbox server
Passive Node
Private Network
Public Network
Shared storage array
DB
Logs
Quorum
Storage connection to Passive Node
Storage connection to Active Node
Figure 19
GEN-001241
SCC architecture

page 125 describes the steps for configuring standard Exchange client resources for
SCC.
Exchange Server 2007 CCR active node and passive node backup with a VSS software provider
CCR is a high-availability feature of Exchange Server 2007. It combines the
asynchronous log shipping and replay technology built into Exchange 2007 with the
failover and management features provided by the Cluster service.
Overview
109
Figure 20 on page 110 illustrates how CCR combines the following elements:
Figure 20
Failover and virtualization features provided by Microsoft failover clusters
A majority-based failover cluster quorum model that uses a file share as a witness
for cluster activity
Transaction log replication and replay features in Exchange 2007
Message queue feature of the Hub Transport server called the transport dumpster
CCR core architecture
In Exchange 2007 SP1 and later, CCR uses two computers, referred to as nodes, joined
in a single failover cluster running either Windows Server 2003 Service Pack 2 or
Windows Server 2008:
110
The nodes in the failover cluster host a single clustered mailbox server.
A node that is currently running a clustered mailbox server is called the active
node.
A node that is not running a clustered mailbox server, but is part of the cluster,
and the target for continuous replication, is called the passive node.
As a result of scheduled, maintained, and unscheduled outages, the designation

of a node as active or passive changes several times throughout the lifetime of the
failover cluster.
Backups in the Exchange CCR environment

The steps for configuring an Exchange client resource for an Exchange CCR
environment vary depending on whether:
The node is active node or passive node. Configuring backup for an Exchange
CCR active node or passive node on page 125 provides the details.
The node is the active node or passive node, and a Data Mover is used, the
following sections provide details:
Configuring backup for an Exchange CCR active node with a Data Mover
on page 127
Configuring backup for an Exchange CCR passive node with a Data Mover
on page 127
The node is passive node and deduplication is required. Configuring

deduplication backups in a CCR environment for a passive node on page 128
provides details.
Exchange Server 2007 proxy node and proxy storage node backups with EMC CLARiiON and EMC
Symmetrix VSS hardware providers
Proxy node and proxy storage backups require the use of VSS hardware providers,
which allow transporting application server snapshots to a proxy node and a proxy
storage node, respectively, for backup services. For example, the EMC VSS provider
supports CLARiiON and Symmetrix disk arrays. NMM supports multiple VSS
hardware providers.
The following sources provide more information:
The EMC Information Protection Software Compatibility Guide provides a complete

list of providers.
Configuring proxy node or proxy storage node backup with the CLARiiON
hardware provider on page 129 provides the procedure for configuring proxy
node and proxy storage node backups with CLARiiON.
Configuring proxy node or proxy storage node backups with the EMC
Symmetrix hardware provider on page 131 provides the procedure for
configuring proxy node and proxy storage node backups with Symmetrix.
Overview
111
Exchange recovery scenarios

This section provides details about the various Exchange recovery scenarios and the
respective configurations requirements:
Conventional recovery from disk, tape, and VTL on page 112
Roll-forward recovery on page 112
Point-in-time recovery on page 112
Rollback recovery on page 113
IMPORTANT
The Microsoft documentation and Microsoft website provide details about these
recovery technologies.
Conventional recovery from disk, tape, and VTL
A conventional recovery consists of recovering data from a snapshot that has been
rolled over to tape, disk, or Virtual Tape Library (VTL). Conventional recoveries
support the same level of item selection as do instant recoveries. Configurations for
traditional recovery from disk, tape, and VTL on page 134 provides configuration
details.
Roll-forward recovery
This option recovers the Exchange databases from the last full backup, and logs from
incremental backups. All existing Exchange transactions that occurred after the time
of the last backup are retained. This recovery is carried out when the Exchange Server
or database fails but the current log LUN is available.
NMM restores the database files and transaction logs from backups and uses the
current logs on the server to roll the database forward. No data is lost by restoring
from backup. A single mailbox database can be marked for this type of recovery in
NMM. While performing the roll-forward recover, all of the mailboxes pertaining to
that storage group are dismounted and once the recovery is successful, all of the
mailboxes are remounted. Configurations for roll-forward recovery on page 135
provides configuration details.
Note: Perform a full backup after a roll-forward recovery. Doing so enables you to perform
point-in-time recovery of data. A roll-forward recovery is not possible after performing a
point-in-time recovery.
Point-in-time recovery
This recovery type is useful when log files are lost or databases must be restored to a
specific backup time. With this option, data can be selected at a storage group level,
but not at an individual database level. Point-in-time recovers Exchange data only up
to the time of the backup that is being recovered, and does not include subsequent
transactions. All new data after that backup is lost.
When point-in-time recovery is used, only the transaction log files that were part of
the backup set are restored. Additional log files generated since the time of backup
are not restored, and the databases are recovered only to the point of the backup.
Configurations for point-in-time recovery of an Exchange 2007 on page 136
112
Note: You must first select the whole storage group and then perform the point-in-time
recovery. The log files currently on disk are moved to another directory before the recovery
takes place. The log files can be manually deleted if they are no longer required after a
successful restore.
Rollback recovery
This recovery is known as destructive recovery because all changes that are made
after the selected snapshot is taken are overwritten. This is a volume-level operation
where any other data on the volume is lost during a rollback.
Note: NMM does not support rollback recovery for backups performed with EqualLogic or
Celerra hardware. Only conventional recovery and snapshot recovery are supported for these
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 recovery of a particular storage group:
The storage group must previously be backed up by itself.
A save set must be specified for that particular storage group.
For example, to perform a rollback recovery of the storage group SG1, the storage
group must be first backed up with the save set APPLICATIONS:\Microsoft
Exchange Writer\SG1 (Exchange Server 2003) or APPLICATIONS:\Microsoft
Exchange 2007\SG1 (Exchange Server 2007).
IMPORTANT
For passive node backups, perform a failover so that passive node becomes active
and then perform rollback recovery on the node.
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 option This database can be overwritten by a restore must be selected for
each Exchange database that is to be recovered. Use the Exchange SYSTEM
Manager application in Exchange Server 2003 or Exchange Management Console
in Exchange Server 2007 for this option.
The Exchange databases must be manually mounted after recovery. Automatic

mounting of database is not available for rollback recovery.
The EMC NetWorker Module for Microsoft Application Release 2.3 Administration Guide
provides more information about rollback recovery, creating a storage array
descriptor file, and the steps to perform a rollback recovery.
Overview
113
Writers for Exchange 2003 and 2007 backup and recovery

Table 17 on page 114 lists the application writers used by NMM for Exchange Server
backup and recovery.
Table 17
Writers used by NMM for Exchange Server backup and recovery

Application writers
Description
Exchange 2003 uses one writer
Information Store writer
Exchange 2007 uses two writers
Information Store writer

Replication Service writer The Replication Service writer is only used
in a CCR environment.
Commands and attributes for Exchange backup and recovery

Table 18 on page 114 lists the commands and attributes used by NMM for Exchange
Server backup and recovery.
Table 18
Commands and attributes used by NMM for Exchange Server backup and recovery
Components
Details
Description
Commands
eseutil.exe
This program, provided by Exchange Server 2003 and Exchange

Server 2007, is used to check that the database and log files do not
contain errors, and that the Exchange Server is valid before
performing the restore.
Attributes
NSR_VIRT_SERV
This attribute is used to specify the name of the Exchange virtual

server client resource in a CCR passive node backup.
NSR_INDEX_CLIENT
This attribute is used to specify the backup to be indexed under the

client name of the Exchange virtual server, but not the passive node
client name in a CCR passive node backup.
NSR_CHECK_JET_ERRORS
This attribute is used with the nsrsnap_vss_save.exe command to

detect Jet errors in the Exchange backup.
NSR_CHECK_JET_ERRORS is run before committing the shadow
copy for Exchange.
NSR_EXCHANGE_LIMIT_SG This attribute is used to set the number of storage groups for a save
set. The option yes or no can be specified for this attribute. If set to
yes, the save set is restricted to a maximum of 10 storage groups.
Configuring dedicated storage node for Exchange 2007 CCR environment

Before performing the steps in this section, review the EMC NetWorker Module for
Microsoft Applications Release 2.3 Installation Guide for details about setting up a
dedicated storage node (DSN) in NMM 2.3.
To configure a DSN for Exchange 2007 CCR with two mailbox servers by using
NetWorker Management Console:
1. Configure CCR setup with two mailbox servers.
2. Create two nodes, for example Node1 and Node2, and virtual client resources.
3. Create a DSN device for Node1.
4. Create a DSN device for Node2.
114
5. Under Node1 client properties, select Globals (2 of 2) > Storage Node column,
specify Node1. This is the Node1 IP or node FQDN.
6. Under Node2 client properties, select Globals (2 of 2) > Storage Node column,
specify Node2. This is the Node2 IP or node FQDN.
7. Now under virtual client properties, select Globals (2 of 2) > Storage Node
column, specify curphyhost.
Performing Exchange Server backups

Exchange 2003 and 2007 application information variable settings on page 115
Specifying Exchange 2003 and 2007 save sets for application data on page 117
Displaying valid Exchange data save sets on page 118
URL encoding for Exchange save sets on page 118
Setting consistency check parameters for threading and throttling on page 119
Configuring Exchange Server backups on page 119
IMPORTANT
As part of a disaster recovery plan, back up either of the following in the Save Set
attribute of the client resource:
- The All save set.
- The SYSTEM COMPONENTS:\ save set, along with the system volume, for
example C:\.
Exchange 2003 and 2007 application information variable settings

Note: If using more than one Exchange attribute at a time, type each entry and its value on a
separate line.
Table 19
Exchange application information variable settings (page 1 of 3)
Attribute name
Description
Values
NSR_SNAP_TYPE=value
Specifies the snapshot service provider

name.
vss
NSR_DM_PORT=value
This attribute:
Specifies the control port number to
use when 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.3 Installation
Guide provides more information about
RM ports.
The RM client control port number. For example:

NSR_DM_PORT=6728
The default value of the RM client control port number that NMM
uses during installation is 6728. If you have specified a different
value during installation, you must use that value here.
115
Table 19
Attribute name
Description
Values
NSR_DATA_MOVER=value
Specifies the hostname of the NMM client

that mounts the snapshot from the NMM
client.
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.
If using NSR_DATA_MOVER when configuring an Exchange
client resource, it is recommended that you use a proxy client.
A proxy client requires hardware for transportable snapshots.
If a proxy client is specified, Exchange consistency checks are
performed on the proxy client. Related messages are written
in the RM log files (erm_clientxx.log) on the proxy client.
If no proxy client is specified for an Exchange client resource,
consistency checks are performed on the Exchange Server.
Related messages are written in both the RM log files and the
nmm.raw file of the client resource host.
NSR_ALT_PATH=value
This attribute specifies the path on which

Exchange snapshots must be mounted
during the backup process.
Exchange snapshots are mounted so that
the database consistency check utility,
eseutil.exe, can be run.
A mount path.
For example, NSR_ALT_PATH=G:\mount_replica\
If a proxy client is specified in the NSR_DATA_MOVER attribute,
type the mount path on the proxy client.
NSR_CHECK_JET_ERRORS=value
Specifies the JET database errors to

check for in the event log before taking a
snapshot.
Note: If errors are found, the snapshot
fails.
NSR_VIRT_SERV=value
Specifies the name of the Exchange virtual

server client resource in a CCR passive
node backup.
Note: If the file system path specified for NSR_ALT_PATH in

Exchange client does not exist, it is automatically created in
NMM.
Values include the following:
447 (Exchange Server 2007 only)
448 (Exchange Server 2007 only)
1018
1019
1022
all
none
Values can be separated with a comma, for example:
NSR_CHECK_JET_ERRORS=1018,1019
The default is none.
The name of the Exchange virtual server.
For example, NSR_VIRT_SERV=virtual_server_name
Note: Do not use this attribute for CCR

active node backup.
NSR_INDEX_CLIENT=value
Specifies that the backup must be indexed

under the client name of the Exchange
virtual server but not the passive node
client name in a CCR passive node
backup.
The name of the Exchange virtual server.

For example, NSR_INDEX_CLIENT=virtual_server_name
Note: Do not use this attribute for CCR

active node backup.
116
Table 19
Attribute name
Description
Values
NSR_EXCHANGE_LIMIT_SG=value
Specifies the number of Exchange storage

groups that are configured for a scheduled
backup.
yes
Sets the number of storage groups for scheduled backup to 10.
NSR_EXCH_RETAIN_SNAPSHOTS=
value
Specifies snapshot retention for only full

backups in Exchange 2003 and Exchange
2007.
yes
Retains snapshots for full backup.
Note: For incremental backups, perform only serverless backup.
NSR_EXCH_CHECK= value
Specifies if consistency check should be

run or not for databases.
yes or no
For Exchange 2007 backups, consistency check is yes, by
default.
Note: If the consistency check is turned off, then the
information is written in the mega.xml file during backup.
Specifying Exchange 2003 and 2007 save sets for application data
Table 20 on page 117 lists the Exchange save set syntax that must be specified for
supported types of Exchange data. Specify Exchange data save sets in the Save Set
attribute of a client resource.
Table 20
Exchange 2003 and 2007 save set names
Exchange Server
Specify the save set name
All Exchange Server 2003 data
APPLICATIONS:\Microsoft Exchange
Writer
A specific Exchange Server 2003 storage group

For example, a storage group named Group_1.
Writer\Group_1
All Exchange Server 2007 data
APPLICATIONS:\Microsoft Exchange 2007
A specific Exchange Server 2007 storage group

For example, a group named Group_2.
2007\Group_2
All Exchange Server 2007 data in a CCR environment on

the active or passive node
A specific Exchange Server 2007 storage group in a CCR

environment on the active or passive node
2007\Group_1
All Exchange Server 2007 data on a virtual server, on the

active CCR node
Note: When backing up an Exchange Server 2007 in a CCR

environment on a passive CCR node, you must use the
NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes.
All Exchange Server 2007 data in a LCR environment
A specific Exchange Server 2007 storage group in a LCR

environment
2007\Group_1
117
Displaying valid Exchange data save sets

After the NMM client is installed on the Exchange Server, you can display a list of
Exchange save sets available for backup.
To display a list of the Exchange save sets that are available for backup:
1. Open a command prompt on the Exchange Server.
names:
If the Exchange Server is a stand-alone node or LCR active node, type:
nsrsnap_vss_save -?
If the Exchange Server is a Exchange 2003 virtual cluster server or Exchange

2007 SCC, type:
nsrsnap_vss_save -c virtual_server_name -?
Note: If the application server is on a virtual host, run this command from the physical
node that is currently hosting the application server.
In an Exchange 2007 CCR environment, type the following on both the active
and passive nodes as one line:
nsrsnap_vss_save -c physical_server_name -A
NSR_VIRT_SERV=virtual_server_name -?
3. Press Enter:
line.
In the Save Set attribute, you can specify either the writer name or the storage
group names, but not both in the same save set.
Exchange
Exchange
Exchange
Exchange
Writer
Writer\first_group
2007
2007\second_group
URL encoding for Exchange save sets

URL encoding for save sets on page 23 provides details about URL-encoded values
for SharePoint save sets.
118
Setting consistency check parameters for threading and throttling

Exchange backup performance is greatly affected by the consistency check utility
eseutil. The larger the databases and logs, the longer it takes to run the consistency
check. NMM provides the options to run the consistency check on multiple storage
groups in parallel.
If multiple consistency checks are run in parallel without setting proper throttle
limits, it may cause performance problems on the proxy system. In extreme cases, this
can cause I/O bottlenecks so severe that consistency checks fail and other operations
with the system are adversely affected.
NMM provides the ability to set threading and throttling to handle performance
issues through the use of the -A attribute values for eseutil configuration settings.
Set the following attributes in the Application Information attribute of the client
resource:
NSR_ESE_UTIL_SEQUENTIAL Set to:

True To specify if eseutil should be run sequentially (single threaded). By
default, it is set to true for sequentially.
Or
False To specify if eseutil should be run in parallel against multiple storage
groups (multi-threaded).
NSR_ESE_UTIL_THROTTLE Set to:

True To specify if eseutil should not be throttled.
Or
False To specify if eseutil should be throttled.
NSR_ESE_THROTTLE_IOS To specify the number of I/Os between pauses

when throttling, in the value range of 100 < 10000. The default value is 100.
NSR_ESE_THROTTLE_DURATION To specify the duration of pause in

milliseconds when throttling, in the value range of 1000 < 60000. The default
value is 1000.
Examples:
A NSR_ESE_UTIL_SEQUENTIAL=false -A NSR_ESE_UTIL_THROTTLE=true
A NSR_ESE_THROTTLE_IOS=500 -A NSR_ESE_THROTTLE_DURATION=5000
Configuring Exchange Server backups

Ensure that the following requirements are taken care of when performing Exchange
Server backups:
After a snapshot of a save group is started, the snapshot process is not interrupted
or halted.
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 NMC will take a long
time to complete.
119
When performing backup of Exchange, the mailbox database files, the mailbox
database files, log files, and system files are on different volumes.
For example:
E:\<For-LogsPath-SystemPath>\
Which is the dedicated volume for log files and system files.
F:\<For-MailboxDatabases>\
Which is the dedicated volume for mailbox database files.
When performing backup of Exchange storage groups residing on mount points,

there is a dedicated drive letter for logs files and system files, and a dedicated
drive letter for mailbox database files.
For example:
E:\MountPoint\<LogsPath_SystemPath>
Where E:\ is dedicated drive letter for logs files and system files.
F:\MountPoint\<MailboxDatabase files>\
Where F:\ is dedicated drive letter for mailbox database files.
When performing a backup of Exchange, all databases are mounted. Unmounted

databases are not backed up, and no warning appears during the backup
operation to indicate if any databases are unmounted. However, the details about
unmounted databases is available in the NMM log files.
To perform an Exchange Server backup, complete the tasks outlined in Table 21 on

page 120.
IMPORTANT
Guide provides details for the first five tasks in Table 21 on page 120.
Table 21
Tasks for configuring an Exchange Server backup
Backup task
Consideration

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 snapshots on page 104 provides details.
Backup schedules determine the days on which full or incremental backups are run.
Backup levels on page 102 and Configuring Exchange backup schedule on page 121 provide
more information.
Backup groups enable you to balance backup loads to reduce the impact on your storage and
network resources.
5. Configure a client group
The Group resource is created so that the client resource can be added to the required group. The
main requirement when configuring the group resource is that the Snapshot checkbox must be
selected. You can also manually select the snapshot policy.
For backups in an Exchange CCR environment, ensure that the virtual and physical clients are
placed on different NetWorker group resources.
6. Configuring Exchange client resource on

page 122
This task is specific to configuring a Exchange client resource.
120
Configuring Exchange backup schedule

It is recommended that no more than 10 Exchange storage groups be configured for
scheduled backs. That is, during a Exchange 2007 scheduled backup there should be
no more than 10 storage groups at a time. This is especially important when parallel
consistency checking has been turned on. Grouping more than 10 storage groups
consumes the available resources of the CPU, I/O, and memory, and can lead to
backup failures. Set the NSR_EXCHANGE_LIMIT_SG attribute to yes to set the
number of storage groups to 10.
To schedule backups for Exchange configurations with more than 10 Exchange
storage groups:
1. Complete the backup configuration that matches your configuration scenario
according to the details provided in Exchange backup scenarios on page 107.
2. Break the Exchange storage groups into sets of 10:
Consider the size of each storage group and the time it takes to back up each
set.
Try to ensure that the size of the data for each set of 10 is roughly the same.
This will ensure predicable backup windows.
3. For the client configuration created in step 1:
a. Create one additional copy of the client for each set of the 10 Exchange storage
groups to back up all the sets. For example, if you have 30 storage groups,
create two additional copies of the client.
b. If you have configured a deduplication backup for the passive node, also
make a copy of the Exchange virtual server client that was created as part of
this configuration.
4. For the original client created:
a. Modify the save set to list the first 10 Exchange storage groups that you want
to back up.
b. If you have configured a deduplication backup for the passive node, also
modify the Exchange virtual server client resource that was created as part of
this configuration. By doing so, you set the save set to list the first 10 Exchange
storage groups that you want to back up.
5. For each subsequent set of 10, repeat step 4 for the copy of the client resource
created.
6. For the group configuration created in step 1:
a. Create one additional copy of the group, without copying clients, for each set
of 10 Exchange storage groups to back up all the sets. For example, if you have
30 storage groups, create two additional copies of the group.
b. For the new groups, disable the autostart.
7. For the clients created in step 3:
a. Add one client to the group that you have just created.
b. If you have configured a deduplication backup for the passive node, also add
the Exchange virtual server client resource with the same save set as the client
that you just added to the same group.
8. Repeat step 6 and step 7 for each remaining set of 10 clients.
121
9. Multiple NetWorker groups cannot run at the same time on the same client for
NMM, so ensure that you schedule the groups to run correctly.
For example, you can schedule the groups to run as follows:
a. Schedule the first group on the first night to see how long it takes.
b. Add the second group to the schedule for the second night.
c. Assign the group a start time based on the run time of the first group from the
night before.
d. Repeat the process until all groups are scheduled.
Configuring Exchange client resource
policies.
Ensure that the following requirements are taken care of when creating client
resources:
For Exchange virtual server cluster and SCC backups, client resources are created
for the virtual client and all the cluster nodes, which are part of the cluster. But
the backups are always done by using the virtual client resource.
For Exchange CCR backups, client resources are created for the virtual client and
all the cluster nodes, which are part of the cluster. Both active and passive node
backups use separate group resources in the NetWorker server for backup.
For Exchange Cluster CCR active node backups, three client resources are
created. One for each physical nodes and one for the Exchange virtual server.
Table 22 on page 122 lists the different procedures of backup for Exchange
stand-alone, LCR, SCC, and CCR backups. Create an Exchange group resource and
an Exchange client resource for each.
Table 22
Different backup procedures for Exchange recovery (page 1 of 2)
Exchange client resource
Details
Exchange 2003 Virtual server cluster
Configuring a client resource for Exchange virtual server cluster backups on page 123
provides the steps for configuring standard Exchange client resources for virtual server
cluster in Exchange 2003.
122
Table 22
Different backup procedures for Exchange recovery (page 2 of 2)
Exchange client resource
Details
Exchange 2007 stand-alone, LCR, or SCC

An Exchange client resource can be specified to perform a
full backup or a storage group backup.

page 125 provides the steps for configuring standard client resources for stand-alone, LCR,
or SCC Exchange 2007.
Note: For Exchange SCC backups, ensure that a client resource is created for the virtual
client because the backups are always done by using the virtual client resource.
Exchange 2007 CCR
The steps vary depending on whether the node is the active node or passive node, and
whether a data mover is used in Exchange 2007:
Configuring backup for an Exchange CCR active node or passive node on page 125
Configuring backup for an Exchange CCR active node with a Data Mover on page 127
Configuring backup for an Exchange CCR passive node with a Data Mover on
page 127
Note: For all Exchange cluster backups, ensure that client resources are created for the
virtual client and all the cluster nodes, which are part of the cluster. Both active and passive
node backups use separate group resources in the NetWorker server for backup.
Exchange 2007 CCR with deduplication
Configuring deduplication backups in a CCR environment for a passive node on page 128
provides additional steps for creating an Exchange client resource for deduplication
backups in a CCR environment in Exchange 2007.
Configuring a client resource for Exchange virtual server cluster backups

To perform backup from an active node, you must configure three client resources:
Client for Physical Node 1
Client for Physical Node 2
Client for Virtual Node
To create a client resource for Exchange 2003 virtual server cluster configuration
backups:
1. In the Administration window of the NetWorker Management Console, click
Configuration.
4. In the Name attribute, type either of the following:
The fully qualified domain name (FQDN) of the NetWorker client computer.
or
The hostname of the NetWorker client computer.
5. In the Comment attribute, type a description. If you are creating multiple client
resources for the same NetWorker client host, use this attribute to differentiate
the purpose of each resource.
6. For the Browse Policy attribute, select a browse policy from the list. The browse
policy determines how long the rolled-over data is available for quick access.
Ensure that the browse policy is long enough for your expected recovery needs. If
your recovery needs are beyond the browse policy, an index recovery can be
performed and should be the preferred first step. If index recovery is not possible,
you can scan tapes to rebuild the index but this should be the last option.
123
Guide provides details about the retention policy for Exchange.
a. Specify the components to be backed up.
b. Place multiple entries on separate lines by using the save set names in Table 19
on page 115.
If required, use URL-encoded values when specifying save set names in the Save
Set attribute of the client resource. Table 2 on page 24 provides the URL-encoded
values for Exchange save sets that are used to represent special characters.
be added.
Note: The backup group must be a snapshot group.
13. In the Access area, leave the Remote user and Password fields empty.
15. In the Application Information attribute, type the following variables and
values:
NSR_SNAP_TYPE=vss
NSR_ALT_PATH=<mount_path_on_local_host>
Create the directory path, for example C:\mount_dir on the client machine by
specifying:
NSR_ALT_PATH=C:\mount_dir
Note: Type Exchange application variable settings and their values on separate lines.
Table 19 on page 115 describes these settings.

17. Verify that the Aliases attribute displays the NETBIOS name for the client. This
name is filled in automatically.
NMM does not display backups.
18. Click OK.
124
Configuring a client resource for Exchange stand-alone, LCR, or SCC backups

To create a client resource for Exchange 2007 stand-alone, LCR, or SCC backups,
follow the steps provided in Configuring a client resource for Exchange virtual
server cluster backups on page 123.
Configuring backup for an Exchange CCR active node or passive node
Note: While backups can be performed from both the active node and the passive node,
recoveries are always done to the active node.
When backing up Exchange from the active or passive node in the Exchange 2007
CCR environment, you must create two client nodes and one virtual client to take
care of failover scenarios.
Review the following configuration examples of failover scenarios:
Scenario 1: Perform backup from passive node
To perform backup from a passive node, you must configure three client resources:
Client for physical node 1 (NSR_INDEX_CLIENT and NSR_VIRT_SERV

attributes are required)
Client for physical node 2 (NSR_INDEX_CLIENT and NSR_VIRT_SERV

attributes are required)
Client for virtual node (NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes

are not required)
Scenario 2: Perform backup from active node

To perform backup from an active node, you must configure three client resources:
Client for Physical Node 1 (NSR_INDEX_CLIENT and NSR_VIRT_SERV

attributes are not required)
Client for Physical Node 2 (NSR_INDEX_CLIENT and NSR_VIRT_SERV

attributes are not required)
Client for Virtual Node (NSR_INDEX_CLIENT and NSR_VIRT_SERV attributes

are not required)
In both the above scenarios, configuring all three client resources takes care of
failover scenario, because NetWorker needs all the client resources the backup is
being performed on.
The steps for creating a Exchange client resource if the backup is performed from an
Exchange CCR active or passive node are similar to that of Configuring a client
resource for Exchange virtual server cluster backups on page 123. However, the
values for two attributes, the Name attribute and Application information attribute,
are different and are described in this section.
To create an Exchange client resource if backup is performed from an Exchange CCR
active or passive node:
1. Perform step 1 through step 3 as in Configuring a client resource for Exchange
virtual server cluster backups on page 123.
125
2. In the Name attribute, create client resources for the virtual server and all
physical machines, which are part of CCR environment.
For example:
For active node:
Type <Exchange Virtual Server hostname>.
For passive node:
Create a client resource for the Exchange virtual server.
Type <Exchange Virtual Server hostname>.
Create a client resource for each physical machine of the CCR
environment.
Type <physical machine hostname>.
For active node, type the following variables and values:
NSR_SNAP_TYPE=vss
Type Exchange application variable settings and their values on separate lines.
For passive node:
These steps should be performed for both the physical nodes as this covers a
failover situation. However, only the current passive node should be enabled
for backups.
a. Type the following variables and values:
NSR_SNAP_TYPE=vss
b. For a passive node client resource, but not the virtual server resource, also
specify the following:
NSR_VIRT_SERV=<Exchange_Virtual_Server_hostname>
NSR_INDEX_CLIENT=<Exchange_Virtual_Server_hostname>
Ensure that you type Exchange application variable settings and their values
on separate lines.
5. Perform step 17 and step 18 as in Configuring a client resource for Exchange
126
Configuring backup for an Exchange CCR active node with a Data Mover
The procedure for creating an Exchange client resource if the backup is performed
from an Exchange CCR active node with a Data Mover is similar to that of
Configuring a client resource for Exchange virtual server cluster backups on
page 123. However, the step for the Application information attribute is different
and is described below.
To create an Exchange client resource if the backup is performed from an Exchange
CCR active node with a Data Mover:
a. Type the following variables and values:
NSR_SNAP_TYPE=vss
NSR_ALT_PATH=<mount_path_on_proxy_client>
NSR_DATA_MOVER=<proxy_client_hostname>
NSR_DM_PORT=6728
Note: The default value in NMM installation is 6728.
b. If you changed the DM Port number to a different value in your NMM client
configuration or installation:
Use that value for NSR_DM_PORT.
Type Exchange application variable settings and their values on separate
lines. Table 19 on page 115 describes these settings.
3. Perform step 17 and step 18 as in Configuring a client resource for Exchange
Configuring backup for an Exchange CCR passive node with a Data Mover
The procedure for creating an Exchange client resource if the backup is performed
from an Exchange CCR passive node with a Data Mover is the same as Configuring
a client resource for Exchange stand-alone, LCR, or SCC backups on page 125.
However, the step for the Name attribute is different and is described below.
To create an Exchange client resource if the backup is performed from an Exchange
CCR passive node with a Data Mover:
2. In the Name attribute, create two client resources:
a. Create a client resource for the Exchange virtual server.
Type <Exchange Virtual Server hostname>
No other configuration is needed.
b. Create a client resource for the passive node of the CCR environment.
Type <passive node client>
127
IMPORTANT
The remaining steps are performed for the client resource for the passive
node of the CCR environment.
Configuring deduplication backups in a CCR environment for a passive node
Before performing these steps, ensure that you have:
The correct save set list, application information, and backup command of the
passive node client resource.
Enabled for deduplication by selecting the deduplication server under Apps &
Modules from the passive node client properties.
IMPORTANT
These steps must be performed in addition to the steps specified in Configuring
backup for an Exchange CCR active node or passive node on page 125 for passive
node backup with deduplication.
To perform deduplication backup of a passive node in a CCR environment:
1. In the servers Administration interface, click Configuration.
2. Select Clients in the navigation tree. The clients table appears. It lists any
deduplication clients that have already been created.
3. Right-click Clients in the navigation tree, or right-click any client in the Clients
table, and select New.
The General tab appears in the Create Client window.
4. On the General tab, specify Exchange virtual name as client name, with the
following exceptions:
a. Clear the Scheduled backup checkbox.
b. In the Save set list, add the same save set list that is in the passive node Client
resource.
5. Click the Apps & Modules tab:
a. In the Access area, leave the Remote user and Password fields empty.
b. In the De-duplication area, select the De-duplication backup attribute to
enable this client for deduplication backups.
c. Select the name of the deduplication node to which this clients backup data
will be sent. This should be the same deduplication node specified for the
passive node. This step links this client with its own deduplication node. Do
not select the name of a replication node here.
IMPORTANT
If the deduplication node for this clients backup data changes, the next backup
performed must be a level 0 (full) backup.
6. Add the new virtual client resource to the backup group that contains the passive
node client resource.
128
Configuring proxy node or proxy storage node backup with the CLARiiON hardware provider
The minimum configurations for proxy node backup and proxy storage node backup
with the EMC CLARiiON hardware provider are the same.
Perform the following configuration steps:
1. Ensure that the proxy node host and the production host have LUNs from the
same CLARiiON box.
2. Ensure that the NMM client is installed on both production and Data Mover
hosts.
3. The following software must be installed on both the production and proxy hosts:
EMC PowerPath with a license
EMC Solution Enabler with the symapi_licenses.dat file copied in
C:\ProgramFiles\EMC\symapi\config
NaviAgent
Note: The version of the NaviAgent must match that of FLARE on the CLARiiON.
NaviCli
Note: When installing NaviCLi, you are prompted to provide the CLARiiON
credentials. Ensure that you provide the correct CLARiiON login details.
Admsnap
4. Run the following commands on the production host:
a. Run this command:
C:\Program Files\EMC\SYMCLI\bin> symcfg authorization add
-host <CLARiiON IP> -user <CLARiiON Username>
-password <CLARiiON Password>
For example:
symcfg authorization add -host 10.31.73.119
-user powersnap -password password
b. Add both the IPs of CLARiiON.

c. Run this command:
C:\Program Files\EMC\Navisphere CLI>NaviSECCli
-user <Username> -Scope 0 -address <CLARiiON IP> -AddUserSecurity
For example:
NaviSECCli -user powersnap -Scope 0 -address 10.31.73.119
-AddUserSecurity
d. After running this command, you are prompted for a password. Ensure to use
the CLARiiON password.
e. Add the second IP of CLARiiON and provide the password again.
For example:
-AddUserSecurity
129
5. Run the following commands on the proxy host:

a. Run this command:
For example:
b. Add both the IPs of CLARiiON.

c. Run this command:
-user <Username> -Scope 0 -address <CLARiiON IP>
-AddUserSecurity
For example:
-AddUserSecurity
d. After running this command, you are prompted for a password. Ensure to use
the CLARiiON password.
e. Add the second IP of CLARiiON and provide the password again.
For example:
-AddUserSecurity
6. For the production host:

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

resource to perform proxy backup.
The attributes are:
NSR_SNAP_TYPE=vss
NSR_DM_PORT=6728 [this value is default]
NSR_ALT_PATH=<temporary path> [specify path here, for
example C:\mount]
7. The EMC NetWorker Module for Microsoft Applications and EMC Symmetrix:
Performing Exchange Server recovery

This section provides information on:
Exchange recovery requirements on page 132
Exchange recovery options on page 133
Configuring Exchange recovery on page 134
IMPORTANT
Perform a full level backup after every restore performed in Exchange 2007.
Exchange recovery requirements

The following requirements must be met before recovering Exchange data:
The writer set or storage group save set must have been backed up:
For Exchange Server 2003 writer:
APPLICATIONS:\Microsoft Exchange Writer
For Exchange Server 2007 writer:

For Exchange Server 2003 storage group:

APPLICATIONS:\Microsoft Exchange Writer\first_group
For Exchange Server 2007 storage group:

APPLICATIONS:\Microsoft Exchange 2007\second_group
Guide provides more information about backups.
132
For each Exchange database to be recovered, you must select the following:
For Exchange Server 2003: The Exchange checkbox titled This database can
be overwritten by a restore must be selected in the Exchange System
Manager ()
Exchange Server 2007: The Exchange checkbox titled This database can be
overwritten by a restore must be selected in the Exchange Management
Console
This is a Microsoft requirement. The Microsoft Exchange documentation provides
more information about this checkbox.
If you are recovering Exchange data that was backed up from a legacy NetWorker
client by using the save set VSS USER DATA:\ in an NMM File System Recovery
Session:
a. While performing recovery by using the NMM client, Exchange databases are
automatically dismounted.
b. After a successful recovery the Exchange databases are mounted
automatically.
Exchange recovery options

To specify recovery options for Exchange data:
1. Open the NMM client GUI.
2. Select the NetWorker Server on which the NMM client software was configured
for backup.
3. If the NMM client is part of a cluster, select the virtual client to which you are
recovering data. The virtual client can be selected from the client list attribute in
the application toolbar.
4. From the left pane, select Exchange Recover Session, and then select one of the
following:
Database Recover (default) to view Exchange database backups.
RSG Mailbox Recover to browse and recover items from existing RSG
databases.
5. In the Exchange Server Session toolbar, click Recover Options.
6. Select the type of recovery to perform:
To recover data for Exchange Server 2003 or 2007 and retain all existing
Exchange transactions that occurred after the time of backup, select Include
existing logs (Roll forward recovery). Roll-forward recovery on page 112
describes this type of recovery in detail.
To recover data for Exchange Server 2003 or 2007 up to the time of backup
only and to not include subsequent transactions, select Include logs only from
this restore (Point-in-time recovery).
Note: A point-in-time recovery must be done at the Exchange Storage Group level and
not at a single database level.
After performing a point-in-time recovery, roll-forward recovery cannot be performed
because the point-in-time recovery replaces the logs that were generated after the
backup.
133
7. Click OK to close the Exchange Recover Options dialog box.

8. From the navigation tree, expand the Applications folder and the appropriate
Exchange writer folder:
Microsoft Exchange Writer for Microsoft Exchange Server 2003
Microsoft Exchange 2007 for Microsoft Exchange Server 2007
9. Select the Exchange storage groups and databases that are to be recovered.
10. From the Exchange Recover toolbar, click Start Restore.
Configuring Exchange recovery

This section provides the procedures required for the various recovery scenarios:
Configurations for traditional recovery from disk, tape, and VTL on page 134
Configurations for roll-forward recovery on page 135
Configurations for rollback recovery of an Exchange 2007 on page 137
Configurations for recovery to storage group on page 138
Configurations for traditional recovery from disk, tape, and VTL

To configure for traditional recovery:
1. In the NMM GUI, in the Exchange Recovery Options window, click the
NetWorker tab, as shown in Figure 21 on page 134.
Figure 21
134
Exchange Recovery Options window with Conventional Restore option selected
2. By default, the Conventional Restore option is selected.

3. Click OK.
Configurations for roll-forward recovery
To perform a roll-forward recovery of an Exchange Server 2007 in a CCR
environment:
IMPORTANT
Perform the recovery from the active node.
1. In the Exchange Management Console application, select the This database can
be overwritten by a restore checkbox.
2. In the Exchange Management shell, stop replication to the passive node with the
suspend-StorageGroupCopy command.
For example:
Suspend-StorageGroupCopy -Identity "bv-hood-cluse12\First
Storage Group"
3. Open the NMM client.
4. In the main toolbar, select the Client menu, and then select the client that is the
Exchange virtual server.
5. From the left pane, select Exchange Recover, and then select one of the following:
Database Recover (default) To view Exchange database backups.
RSG Recover To browse and recover items from existing RSG databases.
6. In Transaction Log File Replay window, ensure that Include existing logs
(Roll-forward recovery) is selected. This is the default setting, but it may have
been changed if the previous recovery was a point-in-time recovery.
7. From the navigation tree, expand the Applications folder and select the
Microsoft Exchange 2007 folder.
8. Select the Exchange Server items that you want to restore.
9. From the Exchange Recover Session toolbar, click Recover.
The Exchange Recovery Options Summary dialog box appears.
10. Review the options:
If you need to change the options, click Recover Options. This opens the
NetWorker Recovery Options dialog box, where you can change settings on
the General, NetWorker, Security, and Exchange tabs.
If the options are okay, click the Start Recover button. This closes the
Exchange Recovery Options dialog box, and starts the recovery.
11. Restore replication between the nodes with the resume-StorageGroupCopy
command.
For example:
resume-StorageGroupCopy -Identity
"bv-hood-cluse12\First Storage Group
135
IMPORTANT
Perform a full backup after performing roll-forward recovery.
Configurations for point-in-time recovery of an Exchange 2007
To perform a point-in-time recovery of an Exchange Server 2007 in a CCR
environment:
IMPORTANT
Perform the recovery from the active node. Failing over the passive node to the
active node if necessary.
1. In the Exchange Management Console application, select the This database can
be overwritten by a restore checkbox.
2. In the Exchange command shell, stop replication to the passive node with the
suspend-StorageGroupCopy command.
For example:
suspend-StorageGroupCopy -Identity "bv-hood-cluse12\First
Storage Group"
3. Open the NMM client.
4. In the main toolbar:
a. Select the Client menu.
b. Select the client that is the Exchange virtual server.
5. From the left pane, select Exchange Recover, and then select one of the following:
Database Recover (default) To view Exchange database backups.
RSG Recover To browse and recover items from existing RSG databases.
6. In Transaction Log File Replay window, select Include only logs from this
restore (Point-in-time recovery).
7. From the navigation tree, expand the Applications folder and select the
Microsoft Exchange 2007 folder.
8. Select the Exchange Server items that you want to restore.
9. From the Exchange Recover Session toolbar, click Start Restore.
10. After restore, on the passive node manually delete log files and database file.
11. On the passive node, in the Exchange command shell, re-seed the passive node
with the Update-StorageGroupCopy command.
For example:
Update-StorageGroupCopy -Identity
"bv-hood-cluse12\First Storage Group"
12. Restore replication between the nodes with the resume-StorageGroupCopy
command.
For example:
resume-StorageGroupCopy -Identity
"bv-hood-cluse12\First Storage Group
136
IMPORTANT
Perform a full backup after performing point-in-time recovery.
Configurations for rollback recovery of an Exchange 2007
Note: Ensure that the current Exchange active node is the node where the files existed at save
time. Failover the virtual Exchange Server to the passive node where the backup was taken, if
necessary.
Use the following settings when performing rollover recovery for and the Exchange
Server:
The Exchange Server 2007 recovery type is Point-in-time.
Browse and select the items for recovery from the client type Exchange Virtual
Server.
To perform a rollback recovery of an Exchange Server 2007 in a CCR environment:

2. Select the NetWorker Server on which the NetWorker client was configured for
backup.
3. In the left pane, select Snapshot Management.
4. If you are performing a rollback for EMC Symmetrix configurations that use
RAID5 BCVs, perform the following steps:
a. Delete all snapshots for the STD, except for the snapshot to be rolled back.
The deletion operation will put the snapshot BCVs in the established state.
Once you have completed the deletions, there should be only one snapshot
BCV in the split state, and that this is the snapshot BCV that is to be rolled
back.
b. Use the SYMCLI commands to disassociate the BCVs and Virtual Devices
(VDEVs) that are in the established state.
c. If the snapshot used multiple STDs, perform the previous steps for each STD.
5. In the navigation tree, select the snapshot to be rolled back.
6. Right-click the selected snapshot and select Rollback.
7. In the left pane, select Monitor to view the progress of the rollback operation.
When rollback processing has completed, reboot the host to complete the rollback
operation.
Mounting the database after recovery
Certain pre- and post-restore operations that are provided for Exchange enable quick
access to e-mail after recovery. Until Exchange databases are remounted, e-mail is not
available for users to browse and verify. NMM provides options to automatically
mount Exchange databases after restore.
137
The Exchange administrator can decide if a restore of a particular Exchange database

is required and if an automatic mounting of the database must be done after the
restore is complete:
If this option is specified, then the database is mounted after the successful restore
of the Exchange Server.
If this option is disabled, then the administrator must manually mount the
database. By default, this option is enabled in NMM.
The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide
describes how to select or disable automatic mounting option.
Configurations for recovery to storage group
This section provides the procedures for recovery to storage groups, depending on
the restore location:
Recovery to the original storage group on page 138
Recovery to an Exchange RSG on page 139
Setting Exchange Server 2007 permissions to enable NMM browsing of RSG

mailboxes on page 143
Additional requirements for browsing RSG mailboxes on page 144
Selecting and recovering items in the RSG database on page 144
Selecting an item for recovery on page 144
Searching for an item on page 145
Recovering selected items on page 146
Recovery to the original storage group

By default, recovery to the original storage group overwrites all of the current content
of the selected databases in the storage group.
To recover to the original storage group:
for backup.
recovering data. The virtual client can be selected from the Client menu in the
4. From the left pane, select Exchange Recover, and then select Database Recover .
5. In the navigation tree, expand the Exchange Server that you want to recover from.
NMM displays the contents of the storage groups that have been backed up.
6. Right-click the storage group that you want to recover, and then click Restore To.
7. In the Select Storage Group Restore Destination dialog box:
a. Verify that Original Storage Group is selected.
b. Click OK.
After the restore, the administrator may need to mount the databases if the option to
put databases online was not automatically selected.
138
Recovery to an Exchange RSG

NMM does not back up the contents of an RSG. The RSG is used only as a location for
restoring backups from normal storage groups.
There are two parts to the recovery process:
Creating an RSG and adding target databases on page 139
Recovering to the RSG on page 141
Setting a different Exchange Server for recovery on page 143
Creating an alternate storage group and adding target databases on page 146
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 supports only one RSG at a time per server.
IMPORTANT
When you use the restore to an RSG feature, always delete the existing RSG and
then create a new clean RSG. If you are performing a directed recovery, delete the
existing RSG on the original server as well as the RSG on the destination server.
The following methods are available within Exchange to configure an RSG database:
Use the Exchange Management Console Database Recovery Management tool for
one storage group mailbox.
Use the Exchange Management Shell for more than one storage group mailbox.
To configure an RSG with Exchange Management Shell:

1. On the Exchange Server, select the Start menu and then select Exchange
Management Shell.
2. Use the new-storage group command to create the Recovery Storage Group:
new-storagegroup server exch_server name rsg_name
LogFolderPath rsg_path SystemFolderPath rsg_path Recovery
where:
exch_server is the Exchange 2007 server name.
rsg_name is the RSG name that you want to create.
rsg_path is the path to the RSG directory.
The Recovery option is also required to specify that an RSG is created.
For example:
new-storagegroup server bv-rmx64-1 name SG2_RSG
LogFolderPath T:\exchsrvr\SG2\SG2_RSG SystemFolderPath
T:\exchsrvr\SG2\SG2_RSG Recovery
139
3. Use the new-mailboxdatabase command to add target databases to the RSG:

new-mailboxdatabase -Name db_name -MailboxDatabaseToRecover
db_name -StorageGroup exch_server\rsg_name -EdbFilePath
rsg_edb_path
where:
db_name is the name of the database that will be recovered.
-EdbFilePath is the path of the database in the RSG, not the original storage
group.
edb_path is the path to the database file in the RSG directory.
4. Use the same name for the RSG database as the original database to avoid
confusion.
For example:
new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1
-StorageGroup bv-rmx64-1\SG2_RSG -EdbFilePath
U:\exchsrvr\SG2\SG2_RSG\DB1.edb
5. Repeat the new-mailboxdatabase for each database that will be recovered.
Note: You must specify the correct database name and edb path.
6. NMM allows the administrator to leave the database offline or have it

automatically put online after the restore:
If you choose to leave the database offline after the restore, it must be
manually mounted. This can be done with the mount-database command:
mount-database Identity exch_server\sg_name\db_name
For example:
mount-database Identity bv-rmx64-1\SG2_RSG\DB1
Databases can be dismounted with the dismount-database command:

dismount-database Identity exch_server\sg_name\db_name
For example:
dismount-database Identity bv-rmx64-1\SG2_RSG\DB1
7. To repeat an RSG restore by using the same database after it has been mounted,
set the database can be overwritten property:
set-mailboxdatabase Identity exch_server\rsg_name\db_name
AllowFileRestore:$true
For example:
set-mailboxdatabase Identity bv-rmx64-1\RSG\DB1
140
Recovering to the RSG
When an RSG has been created and linked to a storage group, it is enabled in NMM
and can be selected as a restore destination. After databases have been recovered to
the RSG, NMM can perform item-level recovery for folders or individual items.
IMPORTANT
then create a new clean RSG. Right-click the RSG and select Delete RSG.
To recover to an RSG:
1. Open the NetWorker User GUI .
for backup.
recovering data. The virtual client can be selected from the Client menu in the
4. From the left pane, select Recover Session > Exchange Recover, and then select
Database Recover. This displays the available Exchange database backups.
5. In the navigation tree, expand the Exchange Server that you want to recover from.
NMM displays the contents of the storage groups that have been backed up.
Figure 22 on page 141 shows the SG2 storage group has been selected, so the First
storage group and Public_SG are unavailable and cannot be selected. This
prevents simultaneous restore of one storage group to the RSG and another
storage group to the original location.
Figure 22
Available and unavailable storage groups
141
6. Right-click the storage group that is linked to the RSG. Figure 23 on page 142
shows the context menu with the Restore To command available.
Figure 23
Restore To command on context menu
7. Select Restore To, and then select RSG Configuration. This verifies that all RSG
databases exist and can be overwritten. It checks all databases, in case the
administrator marks the entire storage group.
If an error message like the one in Figure 24 on page 142 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 24 on page 142, DB1 and DB2 could be restored,
but DB3 cannot until the configuration problem is fixed.
Figure 24
RSG Configuration error message
When a message like the one in Figure 25 on page 142 appears, the RSG
configuration is correct.
Figure 25
RSG Configuration correct message
8. RSG configuration is also checked when a restore is started, but only marked
databases are checked. If a configuration problem is detected, NMM stops the
restore operation.
142
9. Select the storage group linked to the RSG that you want to recover. You can also
select individual mailbox databases in that storage group. Only one storage
group can be selected when Restore to RSG is enabled.
10. Click Start Recover. When Restore to RSG is enabled, Public Folders cannot be
selected because Exchange Server 2007 does not support restoring a public folder
to the RSG.
Figure 26 on page 143 shows the entire SG2 storage group cannot be selected.
Only the Mailbox Database is selectable.
Figure 26
Public folders cannot be recovered to an RSG
11. After the restore, the administrator may need to mount the databases if the option
to put databases online was automatically selected.
Setting a different Exchange Server for recovery
NMM supports restoring to an RSG in a cluster environment. When an Exchange

Server is set up in a cluster, and there are multiple active Exchange Servers, you can
select the RSG that you want to use for an Exchange recover session.
To select an active Exchange Server RSG:
for backup.
3. On the browse tab, right-click the Exchange Server, and then click Change
Exchange Server.
The Change Exchange Server dialog box appears.
Note: If the Exchange Server is a stand-alone installation, this menu item will be
unavailable.
4. In Available Exchange Servers, click the server that you want to browse, and
then click OK. The browse tree is displayed with the RSG that is associated with
the selected Exchange Server.
Setting Exchange Server 2007 permissions to enable NMM browsing of RSG
mailboxes
An Exchange administrator must configure Exchange Server 2007 to enable browsing
of an RSG mailbox.
143
An error message dialog box displays stating that NMM is unable to browse
mailboxes because the required permission is not configured correctly.
This message appears if the following two conditions are met:
If the Send-As and Receive-As permissions are not correctly configured
Browsing the RSG is attempted
To configure permissions for browsing an RSG mailbox:

1. On the Exchange Server, select Start > All Programs > Exchange Management
Shell.
2. Enable Send-As and Receive-As permissions.
For example:
get-ExchangeServer <Exchange Server name> | Add-AdPermission
-user <username> -extendedrights Receive-As, Send-As
where:
<Exchange Server name> is the server where the RSG mailbox is located.
<username> is the name of the user being granted permissions.
Additional requirements for browsing RSG mailboxes
There are other requirements for browsing RSG mailboxes:
An RSG must exist.
The RSG must contain one or more databases.
Databases must be online. NMM does not display mailboxes in offline databases.
The MAPI/CDO kit must be installed.

support on page 101 provides details.
IPV6 must be disabled on Windows Server 2008 and Windows Server 2008 R2.
Exchange System Attendant and Information Store services must be running.
One public folder database should exist in the Exchange domain.
Selecting and recovering items in the RSG database

Once the databases have been recovered to an RSG, you can browse the user
mailboxes, folders, and messages, in the navigation tree, and then select which items
to recover to the user mailboxes. You can also search for items in the navigation tree
through the Search tab.
Selecting an item for recovery
Items can be selected for recovery at the storage group, mailbox, mail folder, and mail
message level:
144
To select items for recovery, select the checkbox beside a node in the navigation
tree. A check mark indicates that the node is selected.
To clear an item contained in a selected node, expand the node and select the
checkbox beside the item to clear it. The check mark disappears.
When you select a node, by default, all items contained in the node such as
mailboxes, mail folders, and messages, will also be selected for recovery. If all
items in the node are selected, the check mark will be green, and the background
of the box will be white.
To select an item without selecting all items at the same level, expand down to the
level that you want, without selecting. When you have located the item, select the
checkbox for the item. The containers above that item are automatically partially
selected.
For example, if Figure 27 on page 145 the mail message Is everybody online? is
selected for recovery, without selecting all the items in the containing mail folder,
user mail box, or storage group, a gray check mark in a checkbox with a gray
background appears. This indicates that the item is partially selected. When Is
everybody online? is selected, the nodes above it are partially selected all the
way up to the server.
Figure 27 on page 145 depicts one selected mail message and several partially
selected nodes in the navigation tree.
Figure 27
Selected and partially selected items
Searching for an item

You can also search for a recovery item. Once you have located an item, you can
select it for recovery.
To search for a recovery item:
1. Click Search above the navigation tree.
2. In the Path field, type a directory path.
3. Optionally, in the Name field, type the name of the search item.
You can refine your search as follows:
Literal match (case-insensitive) Type abc to return abc, ABC, or AbC but not
abcd or ABCD.
Literal match (case-sensitive) Type abc to return abc but not ABc or abcd.
Name contains (case-insensitive) Type %abc% to return abc, abcd, ABCD, or
xyzABCde.
Name starts with (case-insensitive) Type abc% to return abcd or ABCde but
not xyzABCde.
Name ends with (case-insensitive) Type %abc to return xyzAbc but not
ABCde.
145
Single-character match search by using the ? wildcard Type ? to return

single character entries and drive volumes, such as C or D Type
WMI?Writer to return WMI Writer.
Multiple-character match search by using the * wildcard:
Type *.txt to return all entries with a .txt extension.
Type * to return all items within the selected container.
Type *writer* to return all writers.
Search by using both the * and ? wildcard Type *??I*writer* to return WMI
Writer.
4. Click Search. The Details pane displays the results of the search.
Recovering selected items
Once you have completed selecting items through browsing or searching, you can
recover the items to the users mailboxes.
To recover the selected items, from the Exchange Recover Session toolbar, click Start
Recovery.
Note: Recovered items do not overwrite existing items. They are placed in separate folders in
the users mailbox.
When NMM performs an RSG item level recovery, the items are placed in a new
Recovered Items folder created in the users mailbox on the production server.
Figure 28 on page 146 shows an example of two Recovered Items folders in the
mailbox of user Steve M.
Figure 28
Recovered Items folders in user mailbox
The name of the folder begins with a time and date stamp. An example is 14:35:171
3/13/2009 Recovered Items. A new Recovered Items folder is created for each
recovery. This prevents the selected items from overwriting the existing items in the
users mailbox, and allows the user to view and work with existing and recovered
items without overwriting either. When the user completes sorting through the
recovered items, the user can delete the Recovered Items folder.
Recovery to an alternate storage group
Recovery to an alternate storage group allows you to recover the storage group data
to a different Exchange Server from the original source. Before NMM can restore to
an alternate storage group, a new database must be created in the alternate storage
group with the same name as the original database.
Creating an alternate storage group and adding target databases
There are three methods available within Exchange to configure an alternate storage
location database:
146
Exchange Management Shell at the command line, which is the recommended

method
Exchange Management Console Database Recovery Management tool
By using the Select Storage Group Restore Destination dialog box in the NMM
GUI when performing a recovery to an alternate storage group.
To configure an alternate storage group with Exchange Management Shell:

1. On the Microsoft Exchange Server:
a. Select the Start menu.
b. Select Exchange Management Shell.
2. Use the new-storage group command to create the alternate storage group:
new-storagegroup server exch_server name alt_name
LogFolderPath alt_path SystemFolderPath alt_path
where:
exch_server is the Exchange 2007 server name.
alt_name is the required alternate storage group name.
alt_path is the path to the alternate storage group directory.
For example:
new-storagegroup server bv-rmx64-1 name Alternate_SG
LogFolderPath T:\exchsrvr\SG2\Alternate_SG
SystemFolderPath T:\exchsrvr\SG2\Alternate_SG
3. Use the new-mailboxdatabase command to add target databases to the alternate
storage group:
new-mailboxdatabase -Name db_name -MailboxDatabaseToRecover
db_name -StorageGroup exch_server\alt_name -EdbFilePath
edb_path
where:
db_name is the name of the database that will be recovered.
-EdbFilePath is the path of the database in the alternate storage group, not the
original storage group.
edb_path is the path to the database file in the alternate storage group
directory.
Note: The alternate storage group database name must match exactly the original database
name.
For example, the name for the alternate storage group specified in
new-mailboxdatabase -Name: is DB1, the same as the name of the original
database name specified in MailboxDatabaseToRecover, DB1.
new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1
-StorageGroup bv-rmx64-1\Alternate_SG -EdbFilePath
U:\exchsrvr\SG2\Alterenate_SG\DB1.edb
4. Repeat new-mailboxdatabase command for each database that will be recovered.

Ensure to specify the correct database name and edb path.
147
5. NMM allows the administrator to leave the database offline or have it

automatically put online after the restore:
If you choose to leave the database offline after the restore. It must be
manually mounted. This can be done with the mount-database command:
mount-database Identity exch_server\sg_name\db_name
For example:
mount-database Identity bv-rmx64-1\Alternate_SG\DB1
Databases can be dismounted with the dismount-database command:

dismount-database Identity exch_server\sg_name\db_name
For example:
dismount-database Identity bv-rmx64-1\Alternate_SG\DB1
6. To repeat an alternate storage group:

a. Restore by using the same database after it has been mounted.
b. Set the database can be overwritten property:
set-mailboxdatabase Identity exch_server\alt_sg_name\db_name
For example:
set-mailboxdatabase Identity bv-rmx64-1\Alternate_SG\DB1
To recover to an alternate storage group:

1. In the Select Storage Group Restore Destination dialog box, select Alternate
Storage Group.
2. In the Exchange Server list, select the Exchange Server that contains the alternate
storage group.
3. If the alternate recovery storage group is not available, then the No Recovery
Storage Group exists dialog box appears:
a. In the dialog box, click Yes.
The Create Exchange 2007 Recovery Storage Group dialog box appears.
b. Provide details for the new Recovery Storage Group in this dialog box.
c. Click OK. The new Recovery Storage Group is successfully created.
4. In Select Alternate Storage Group select the storage group, and then click OK.
After the restore, the administrator may need to mount the databases if the option to
put databases online was automatically selected.
148
Selecting a storage group restore destination

When restoring from a point-in-time backup, files are copied from a snapshot to the
specified location. When restoring from a rollover, files are copied from a NetWorker
device such as tape, file, or adv_file to the specified location.
Selecting a storage group restore destination on page 149 provides details.
IMPORTANT
then create a new clean RSG. Right-click the RSG and select Delete RSG.
NMM provides several options for selecting the target storage group. These options
are specified in the Select Storage Group Restore Destination dialog box, which is
accessed in the Exchange Recover Session.
Figure 29 on page 149 displays the options available in this dialog box.
Figure 29
Select Storage Group Restore Destination dialog box
The Select Storage Group Restore Destination dialog box provides the following
settings and information:
<Storage Group Name> Storage Group (Source) This box displays the name of
the storage group selected in the Browse tab in the Exchange Recover Session
window.
Restore To (Destination) This specifies where you want the storage group
restored to.
Exchange Server By default, this is the server or virtual server where the
source storage group is located. You can select a different server here if you are
recovering to an RSG or alternate storage group that is not on the source server.
Original Storage Group This specifies to restore the content to the original
storage group, which will overwrite the content currently in that storage group.
Selecting a storage group restore destination
149
Recovery Storage Group This specifies to restore the storage group to a

separate RSG that you have already created:
Recovering to an RSG allows you to browse and select items to restore without
overwriting the entire storage group. When this option is selected, the Check
Recovery Storage Group dialog box appears.
The Check button is used to verify that the Recovery Storage Group exists and
databases are configured properly.
Alternate Storage Group This specifies to restore databases to a different

storage group. When this option is selected, the Select Alternate Storage Group
dialog box provides a menu where you can select from the available storage
groups available on the Exchange Server listed in the Restore To dialog box.
Note: Exchange Server 2007 does not support restoring a public folder to the RSG. If a storage
group contains a public folder, it cannot be selected. Only the mailboxes within that storage
group can be selected.
The steps to specify which location to restore to are described in the separate
procedures for each location type:
Recovery to the original storage group on page 138
Recovery to an Exchange RSG on page 139
Recovery to an alternate storage group on page 146
Configurations for recovery to storage group on page 138 provides configuration

details.
Performing Exchange Server 2007 directed recovery

In the event of a problem recovering to the original Exchange Server host, such as
disk drive failure, you can perform a directed recovery to recover Exchange data to a
different Exchange Server.
The database portability feature in Microsoft Exchange Server 2007 allows a mailbox
to be mounted on any server in the same organization. Microsoft TechNet describes
this feature in more detail.
In the normal NMM backup and recovery process, the backup flows in the following
direction:
1. The NMM client is installed on the computer that will be backed up. For example,
ExchangeServer1.
2. That NMM client is configured to work with a specific NetWorker server on
another computer. For example, NetWorkerServer1.
3. Backups are configured on and performed by the NetWorker server, NetWorker
Server1.
4. Recovery is performed through the NMM client UI on the NMM client computer,
ExchangeServer1, and recovered to the same NMM client computer.
150
In a directed recovery, the NMM client is also installed on another server, for
example Server2. The recovery of ExchangeServer1 is directed from the NMM client
on Server2:
1. The NMM client is installed on the computer that will be backed up. For example,
ExchangeServer1.
2. The NMM client is also installed on another computer that will direct the
recovery. For example, Server2.
3. The NMM client on both machines are configured to work with the same
NetWorker server on another computer. For example, NetWorkerServer1.
4. Backups are configured on and performed by the NetWorker server, NetWorker
Server1.
5. Recovery of ExchangeServer1 is performed through the NMM client UI on another
NMM client computer, Server2, and recovered to another location.
Performing a directed recovery

To perform a directed recovery of an Exchange Server with NMM:
1. In NetWorker, create a backup of the NMM client, the Exchange Server.
2. Run NMM on the machine that will receive the data.
3. Connect to the NetWorker server that hosts the NMM Exchange Server client.
4. Add the NMM Exchange Server client that created the backup as a locally
viewable client.
Figure 30 on page 151 shows the default of only one NMM client available, the
local client.
Figure 30
Local client on the taskbar next to Client
5. On the Options menu, click Configure Options.
Performing Exchange Server 2007 directed recovery
151
6. Click the Refresh button, which is to the right of the Client name. Figure 31 on
page 152 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 31
Select Viewable Clients dialog box
7. Click the client to add in the Available clients on menu, and then click Add. Add
or remove clients as needed.
8. Click OK.
9. Click the Client list, and select the client that created the Exchange Server backup
as the current local client.
10. If the Snapshot Management or Monitor is the active navigation bar item, and
you are prompted with the Navigate Away dialog box, click Yes.
11. On the Exchange Recover Sessions bar, select Recover Options. The Exchange
Recover Session Options dialog box appears.
12. Recover remote client's backup to local Exchange Server.
Performing Exchange Server 2007 disaster recovery

Prior to disaster recovery, use NMM to perform regular backups of volumes, system
components, and application save sets.
The following save sets should be backed up regularly:
1. Back up the following file system volumes with the snapshot policy All:
C:\
SYSTEM COMPONENTS:\
The back up of file system volumes includes the following
Windows Boot Volume
Application software
Note: If the system has been set up with a separate file system for the Windows
boot\system partition and separate file system for application installation, then along with
C:\ drive, back up the file system that includes the Windows Boot Volume, Windows
System Volume, and application software.
152
Guide provides more information about configuring snapshot policies for
SYSTEM COMPONENTS backup.
2. Back up application data for Microsoft Exchange CCR on the NetWorker server
on the passive node by using the following save set with snapshot policy all.
Applications:\Microsoft Exchange 2007
NMM can perform the following types of disaster recovery for Exchange Server 2007:
Performing Exchange Server 2007 disaster recovery on Windows Server 2008 or

2008 R2 with NetWorker version 7.6 SP2 on page 153
Performing Exchange Server 2007 disaster recovery on Windows 2008 or 2008

R2 with NetWorker version 7.6 SP1 or earlier on page 153
Performing Exchange Server 2007 disaster recovery on Windows Server 2008 or 2008 R2 with
NetWorker version 7.6 SP2
If you have installed NetWorker 7.6 SP2 with NMM on Windows 2008 and Windows
2008 R2, you can leverage the Windows Disaster Recovery capability provided by
NetWorker 7.6 SP2 for disaster recovery of Exchange data in a stand-alone or CCR
environment. Performing Windows Disaster Recovery backup and recovery for
Microsoft applications on page 232 provides details.
Performing Exchange Server 2007 disaster recovery on Windows 2008 or 2008 R2 with
NetWorker version 7.6 SP1 or earlier
Perform Exchange Server 2007 (stand-alone) disaster recovery on page 153
Perform Exchange Server 2007 disaster recovery for Microsoft Exchange CCR to
a two-node cluster in a production environment on page 154
Perform Exchange Server 2007 disaster recovery for Exchange CCR in a

production environment on page 156
Perform Exchange Server 2007 (stand-alone) disaster recovery

The process for performing this disaster recovery follows these steps:
1. The Exchange data must have already been backed up with the save set
Applications:\Microsoft Exchange 2007.
2. Rebuild the Exchange Server hardware, following the instructions provided by
Microsoft.
3. After the Exchange Server is rebuilt, ensure with the name, account information,
and configuration, and other information is the same as the old server that is
being replaced.
4. Reinstall NMM.
5. In NMM, perform an Exchange Server point-in-time recovery.
To perform a disaster recovery of a stand-alone installation of Microsoft Exchange
Server 2007:
1. Back up all Exchange data with the save set Applications:\Microsoft Exchange
2007.
153
2. Build new machine hardware for an Exchange Server, following Microsofts

instructions on TechNet:
Moving Exchange Servers to New Hardware and Keeping the Same Server
Name
http://technet.microsoft.com/en-us/library/bb332343.aspx
3. Capture all of your manually set Internet Information Services (IIS) virtual
directory configurations. Use the following Exchange Management Shell
command:
Get-OwaVirtualDirectory "owa (default web site)" | export-clixml
Owa.xml - depth
4. Copy the Owa.xml file to a location that can be accessed by the new server after it
is available and the old server is shut down.
5. Shut down the existing Exchange 2007 server. (The backup should have already
been taken, at step 1 on page 153 of this procedure.)
6. Reset the computer account for the existing Microsoft Exchange 2007 server.
7. Bring the new computer online, and then confirm that the new computer is
running the same operating system that was installed on the existing Microsoft
Exchange 2007 server.
8. Rename the new server to the same name as the original server that you are
replacing, and then join this computer to the domain.
9. For drives that contained Exchange 2007 data, configure drive letters on the new
server to map to or match the configuration of the old server.
10. Verify that the drives have sufficient space to accommodate the restored data.
11. Start the Exchange Server 2007 setup with the following parameter:
Setup.com /M:RecoverServer
12. Reboot the machine.

13. Restore your manually set IIS virtual directory configurations by running the
following Exchange Management Shell script:
Restorevdir.ps1 Owa.xml
Note: The Microsoft Exchange Server should come online with all previous storage groups.
14. Install NMM.

The EMC Module for Microsoft Applications Release 2.3 Installation Guide provides
instructions for installing NMM, including Exchange Server-specific
configuration settings.
15. In NMM, perform an Exchange Server point-in-time recovery. Point-in-time
recovery on page 112 describes these recovery steps in detail.
Perform Exchange Server 2007 disaster recovery for Microsoft Exchange CCR to a two-node cluster in a
production environment
The steps in this disaster recovery scenario are based on the following host details for
the production environment you are recovering, and the isolated environment you
are recovering to.
154
Production environment setup
Domain Controller, one physical machine
CCR setup with an active node and a passive node, two physical machines
Isolated environment setup
Domain Controller setup with the same hardware and software configuration as
the production environment
CCR setup with only a passive node, one physical machine
To perform a disaster recovery of Microsoft Exchange Server 2007 to a two-node

cluster in a CCR environment:
1. Configure an AD domain setup in an isolated environment by using the same
operating system version, machine IP, and machine name as the production
Active Directory Domain setup.
Note: There should not be any communication between the production environment and
the isolated environment.
2. Configure the AD domain on the isolated environment with the same domain
name as the production AD domain name. Ensure that both environments use the
same make and model of hardware.
3. Install all Windows updates, and applications such as Exchange, in the isolated
environment AD domain setup, to match the production Active Directory
Domain setup.
4. Disconnect the NetWorker server from the production environment, and connect
the NetWorker server to the isolated environment.
Note: In this scenario, the backup was taken on the file system, not on tape. Since the
backup is not on tape, to move the backup to the isolated environment you must connect
isolated environment to the NetWorker server which is storing the backup.
5. Install NMM on the isolated environment AD domain machine.

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

Production
156
MC1: Domain controller
CL1: cluster node 1
CL2: cluster node 2
Recovery site (in the same network as the production setups)
CL11: cluster node 1
CL21: cluster node 2
To perform a Microsoft Exchange Server 2007 CCR disaster recovery in production to

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

The procedure to recover a deleted mailbox in Exchange 2007 is performed
independent of NMM backup or recovery operations.
In the event that a user mailbox is deleted, you can quickly recover the mailbox
through the Exchange Management Console.
To recover a deleted mailbox:
1. In Exchange Management Console, ensure that deleted user mailbox entry
appears under Disconnected mailbox under Recipient management.
2. Re-create the user mailbox with same name.
3. Disable the re-created user mailbox.
4. Open Disconnected mailbox under Recipient management; and then select the
user mailbox which was accidentally deleted.
5. Right-click the user mailbox and then select Connect.
6. Select User mailbox radio button, and then click Next.
7. Select Matching user > User mailbox, and then click Next. The deleted user
mailbox is then re-created under Recipient management > Mailbox.
Note: Recreated deleted mailboxes are not always immediately visible. It may take from 15
minutes to an hour before the mailbox is visible and accessible through Outlook.
Best practices
Review the information in Table 5 on page 39 for the list of best practices and
recommendations to follow when using NMM to back up and recover Exchange
Server.
Review the following best practices for Exchange backup and recovery:
Backup time can be reduced by spreading data across different storage groups.
For example, it takes longer to back up a single storage group with 200 GB of
data, than it does to back up 200 GB of data spread across 10 different storage
groups.
In addition to your scheduled full backups, you should also perform a full
backup copy of Exchange Server after:
Every successful recovery.
Upgrading to NMM from previous releases of NetWorker clients.
The database directory path is changed or the storage group Log Path or
System Path are changed.
158
Ensure that all databases in a specified storage group are mounted before backing
up the Exchange Servers. Unmounted databases are not backed up.
Ensure that database (mailbox and public folder) files and transaction log files
reside on separate volumes for backup, otherwise the backup will fail. Also,
ensure that the volume drive letter of the databases files is different from the
volume drive letter of the transaction log files.
If Exchange objects like storage groups and databases are deleted by using
Exchange System Manager in Exchange Server 2003, or Exchange Management
Console in Exchange Server 2007, these objects cannot be recovered until disaster
recovery is performed. Objects from the Exchange Server should not be deleted
unless they no longer need to be recovered.
After upgrading to the NMM client, you cannot recover Exchange backups that
were performed with a previous version of the NetWorker client. To ensure that
all Exchange data can be recovered to the point-in-time of the upgrade, perform a
full backup of Exchange data immediately after upgrading to the NMM client.
After upgrading to the NMM client from the NetWorker Module for Exchange
(NME), you cannot recover Exchange backups that were performed with NME.
To ensure that all Exchange data can be recovered to the point-in-time of the
upgrade, perform a full backup of Exchange data immediately after upgrading to
the NMM client.
In Exchange Server 2003 backups, save sets and backup groups that include the
Exchange writer cannot include other application writers or the system
components writer. The Exchange writer can, however be included in the same
save set with volume components such as D:\.
In Exchange Server 2007, save sets and backup groups that include the Exchange
writer cannot include any other volumes, applications, or non-Exchange items in
the save set.
The Exchange consistency checker utility eseutil.exe must be installed on the

proxy host that has the Exchange Management tools. This is applicable to both
Exchange Server 2003 and 2007.
Ensure that the version of eseutil, including service pack level, installed on the
proxy host is the same as that installed on the Exchange Server. For example, if
Exchange Server 2003 SP1 is installed, then the version of eseutil that is installed
on the proxy host, must be from the Exchange Server 2003 SP1 management
utilities. Otherwise, the consistency checker utility will report errors even when
the database is valid.
Exchange recovery limitations

Review the following limitations when backing up and restoring Exchange objects
with NMM:
Cannot restore a single mailbox database using point-in-time recovery A single

mailbox database cannot be restored by using point-in-time recovery of
Exchange, because it requires both logs and databases to be selected for restore:
VSS-marking semantics do not allow selecting logs for backup or restore.
Logs are included only when the a storage group is selected for either backup
or restore.
Logs are not included when a database is selected.
Roll-forward recovery not be possible after point-in-time restore After you

complete a successful point-in-time restore, perform a full backup of the
Exchange Server so that you can perform roll-forward recovers.
No support for RSG configuration where the RSG system path restore location
and RSG logs restore location can be different Although Microsoft Exchange
Server supports an RSG configuration where the RSG system path restore
Best practices
159
location and RSG logs restore location are different, NMM currently does not
support that configuration. The location for the RSG system path and the RSG log
path must be the same.
MAPI memory errors when recovering mailbox items from RSG databases
There is a known memory error that may occur with Microsoft Exchange MAPI
when recovering mailbox items from RSG databases. The error
MAPI_E_NOT_ENOUGH_MEMORY may be reported in the NMM logs. When
this error occurs, NMM recovers the mailbox item, but may lose properties such
as the original font and formatting.
This is a known problem, but Microsoft has no workaround or fix for this issue at
this time.
IPv6 issues affect browsing RSG mailboxes There is a known issue with IPv6
affecting MAPI calls. NMM uses MAPI calls to browse RSG mailboxes. This may
occur when the NMM client is running Windows Server 2008 (x64) and Exchange
Server 2007, and IPv6 is enabled. IPv6 is enabled by default by Windows Server
2008 installation. When IPv6 is enabled on the client, and there is no IPv6
network present, RSG mailbox browsing will fail. This can prevent you from
viewing and selecting RSG mailboxes. This problem must be fixed through the
registry, not the network connections dialog box.
To fix RSG browsing issue in the registry:
a. Open the registry.
b. Navigate to
HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters.
c. Edit or create the 32-bit DWORD value DisabledComponents, and type the
hex value FFFFFFFF.
d. Reboot the machine.
160
6
Microsoft Exchange
Server 2010 Backup
and Recovery
Overview ......................................................................................................................
Performing Exchange 2010 backups.........................................................................
Performing Exchange Server 2010 recovery............................................................
Performing a quick recovery of a deleted Mailbox in Exchange 2010 ................
Microsoft Exchange Server 2010 disaster recovery ................................................
162
164
173
179
179
161
Overview
EMC NetWorker Module for Microsoft Applications (NMM) supports both Exchange
Server 2010 and Exchange Server 2010 SP1. The details provided in this chapter for
Exchange 2010 are also relevant for Exchange 2010 SP1.
NMM 2.3 provides Exchange Server 2010 backup and recovery support in:
Data Availability Group environment Exchange 2010 has introduced Data

Availability Group (DAG) for high availability of Exchange databases:
Each Exchange database can be replicated to multiple Exchange Servers, the
maximum being 16 copies.
Out of multiple copies of a database, only one copy of the database is active at
a time, the remaining copies are passive.
Back up of active databases, passive databases, or both can be performed.
Back up of databases in DAG environment can be restored only to active
database copies.
Information about Exchange 2010 DAG architecture is available on the Microsoft
Technet website at http://technet.microsoft.com/en-us/library/dd979799.aspx.
Non-DAG environment or stand-alone Exchange Server 2010 environment

Exchange 2010 stand-alone applies to a Exchange 2010 Mailbox server where all
the databases are hosted on one machine and DAG is not configured.
Review the following sections before performing Exchange 2010 server backup and
recovery:
Supported operating systems on page 162
Types of backup and recovery on page 163
Exchange 2010 VSS writers on page 163
LAN-based Exchange Server configuration with a storage area network and a

proxy client on page 164
Backup initiated transaction log file truncation on page 164
version 1.2.1 for granular recovery in Exchange 2010 on page 164
Supported operating systems

NMM 2.3 provides support for Exchange 2010 on:
162
Windows Server 2008 R2 Standard Edition (x64) and Windows Server 2008 R2
Enterprise Edition (x64)
Windows Server 2008 SP2 Standard Edition (x64) and Windows Server 2008 SP2
Types of backup and recovery

NMM 2.3 supports the following backup types in Exchange 2010 DAG and
stand-alone environments:
Full backup You can perform a full backup of Exchange 2010 databases in both
DAG and non-DAG environments. Both database files and logs files can be
backed up.
Incremental backup You can perform incremental backup of Exchange 2010

databases in both DAG and non-DAG environments. Unlike a full backup in
which both database files and logs files are backed up, in an incremental backup
only logs files are backed up.
In a DAG environment, an incremental backup of a passive copy of a database
can be performed after a full backup of the active copy is performed on another
Mailbox server, and vice versa. If a full backup is not found on the Mailbox server
that contains the passive copy of the database, it is required that you manually
perform a full backup on the Mailbox server that contains the passive copy of the
database with the same save set that was used the first time a backup was
performed.
NMM 2.3 supports the following recovery types in Exchange 2010 DAG and
stand-alone environments:
Full recovery
Incremental recovery
Granular recovery for Mailbox, folder, and e-mail
IMPORTANT
Ensure that you have Exchange 2010 SP1 Rollup 2 installed when performing
Recovery Database (RDB) granular or item-level recovery on any Exchange
Mailbox server.
Exchange 2010 VSS writers

Exchange 2010 has two writers for active and passive databases. NMM 2.3 uses these
writers during backup.
Table 23 on page 163 lists the Exchange 2010 VSS writers.
Table 23
Exchange 2010 VSS writers

Writer name
Description
Microsoft Exchange Information Store

writer
In a non-DAG environment, this writer is used for database backup.

In a DAG environment, this writer is used for active database backup.
Microsoft Exchange Replication writer In a DAG environment, this writer is used for passive database backup
on the physical node.
Overview
163
LAN-based Exchange Server configuration with a storage area network and a proxy client
The LAN-based Exchange Server configuration with a storage area network and a
proxy server is the same for Exchange Server 2007 and Exchange Server 2010.
LAN-based Exchange Server configuration with a storage area network and a proxy
client on page 105 provides details.
Backup initiated transaction log file truncation

Backup initiated transaction log file truncation is started based on the type of backup
chosen:
In non-DAG configurations, the Information Store Writer truncates the

transaction log files at the completion of successful full or incremental backups.
In DAG configurations, log truncation is delayed by the Replication service until

all necessary log files are replayed into all other copies. The Replication service
deletes the backed up log files both from the active and the copy log file paths
after the service verifies that the to-be-deleted log files have successfully been
applied to the copy database and both active database and the database copies
checkpoint has passed the log files to be deleted.
http://msdn.microsoft.com/en-us/library/bb204080.aspx provides more details.
Microsoft Exchange Server 2010 MAPI client and Collaboration Data Objects version 1.2.1 for
granular recovery in Exchange 2010
In Exchange Server 2010, the Messaging API (MAPI) and Collaboration Data Objects
(CDO) kit is required for granular recovery support. The MAPI client libraries and
CDO are not included with Exchange Server 2010 and can be downloaded from
Microsofts website.
For information on downloading and installing this package, search for Microsoft
Exchange Server MAPI Client and Collaboration Data Objects 1.2.1" on the Microsoft
Download Center website. Download version 6.5.8211.0.
Performing Exchange 2010 backups

164
Backup options on page 165
Specifying Exchange 2010 application data save sets on page 165
Displaying save set syntax on page 166
URL encoding for SharePoint save sets on page 166
Exchange 2010 application information variable settings on page 167
Configuring persistent and non-persistent snapshots on page 168
Considerations for backing up Exchange 2010 in non-DAG and DAG

environment on page 169
Exchange 2010 incremental backup promoted to full backup on page 169
Configuring Exchange Server 2010 backups on page 170
Configuring Avamar deduplication backups in a DAG environment on

page 172
Verifying backups on page 173
IMPORTANT
If a Exchange 2010 Mailbox server is backed up in a stand-alone environment and
then moved to a DAG environment, the stand-alone backups of the Mailbox server
cannot be browsed and recovered.
Backup options
In NMM 2.3, the following backup options are provided:
Only active databases backup on the server You can back up all the active
database copies residing on a Exchange 2010 Mailbox server in a DAG
environment. You can perform full and incremental backups.
Only passive databases backup on the server You can back up all the passive
database copies residing on a Exchange 2010 Mailbox server in a DAG
environment. You can perform full and incremental backups.
Both active and passive databases backup on the server You can back up both
active and passive databases on Exchange 2010 Mailbox server in the DAG
environment.
Backup from a dedicated storage node You can perform Exchange 2010
database backup by using a NetWorker storage node, where the Exchange 2010
database and the NetWorker storage node are on the same machine in a
non-DAG environment. You can perform full and incremental backups.
Dedicated storage node is not supported in a DAG environment.
Backup from remote storage node You can perform Exchange 2010 database
backup by using a remote NetWorker storage node in a DAG or non-DAG
environment. The Exchange 2010 and NetWorker storage node are on different
machines in the non-DAG environment. You can perform both full and
incremental backups.
Backup from NetWorker proxy node You can perform Exchange 2010 database
backup by using a NetWorker proxy node in both a DAG or non-DAG
environment. You can do both full and incremental backups.
Note: If a Mailbox server is added to a DAG and a database is then backed up:
Refresh the NMM GUI.
Or
Close the NMM GUI and then reopen it.
Specifying Exchange 2010 application data save sets

By using NMM 2.3, you can configure client resources with Exchange 2010 Mailbox
server name. You can provide the save set name in the client resource at writer-level
or database name-level.
Table 24 on page 166 provides the list of Exchange 2010 save sets for application data.
165
Table 24
Exchange 2010 save sets for application data

Type of backup data
Save set syntax
Writer-level
Database name-level
2010\<Database name>
Displaying save set syntax

After the NMM client is installed on the Exchange 2010 server, you can view a list of
Exchange save sets available for backup.
To view a list of the Exchange 2010 save sets that are available for backup:
1. Open a command prompt on the Exchange Server.
names:
For a writer-level backup and to list all the databases on the mailbox server:
nsrsnap_vss_save
-?
For example,
C:\Users\administrator.NMMEXCH2010>nsrsnap_vss_save -?
APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database
0410662886
APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database
1249691110
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
For a writer-level backup and to list all the databases on the mailbox sever
categorized by the active or passive database state on the current node:
nsrsnap_vss_save
-v -?
For example:
C:\Users\administrator.NMMEXCH2010>nsrsnap_vss_save -v -?
"APPLICATIONS:\Microsoft Exchange 2010"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database
0410662886 -- Passive"
"APPLICATIONS:\Microsoft Exchange 2010\Mailbox Database
1249691110 -- Active"
68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success.
Also, do not include - - Passive or - - Active when copying the output. These denote the
database state and are not part of the save set.
URL encoding for SharePoint save sets

166
Exchange 2010 application information variable settings

Table 25
Attribute name
Description
NSR_SNAP_TYPE=value
Specifies the snapshot service provider name. vss

Specifies the hostname of the NMM client that

mounts the snapshot from NMM client.

If no value is entered, the local host is used as the
data mover.
If using NSR_DATA_MOVER when configuring an
Exchange client resource, it is recommended that you
use a proxy client. A proxy client requires hardware for
transportable snapshots. If a proxy client is specified,
Exchange consistency checks are performed on the
proxy client. Related messages are written to the
Replication Manager log files (erm_clientxx.log) on the
proxy client.
If no proxy client is specified for an Exchange client
resource, consistency checks are performed on the
Exchange Server. Related messages are logged in the
client resource host in both the Replication Manager
log files and the nmm.raw file.
NSR_DM_PORT=value
This attribute:
Specifies the control port number to use in
communicating with the data mover client.
This is the control port that the Replication
Manager (RM) client service is running on.
EMC NetWorker Module for Microsoft
Applications Release 2.3 Installation Guide
provides more information about RM ports.
The RM client control port number. For example:

NSR_DM_PORT=6728
The default value of the RM client control port number that
NMM uses during installation is 6728. If you have
specified a different value during installation, you must
specify that value here.
NSR_ALT_PATH=value
This attribute:
Specifies the path on which to mount
Exchange snapshots during the backup
process.
Exchange snapshots are mounted so that
the database consistency check utility,
eseutil.exe, can be run.
A mount path.
For example:
NSR_ALT_PATH=G:\mount_replica\
If a proxy client is specified in the NSR_DATA_MOVER
attribute, type the mount path on the proxy client.
Specifies the JET database errors to check for

in the event log before taking a snapshot.
Values include the following:

1018
1019
1022
all
none
Values can be separated with a comma, for example:
NSR_CHECK_JET_ERRORS=1018,1019
The default value is none.
NSR_CHECK_JET_ERRORS=value
Note: If errors are found, the snapshot fails.
Values
Note: If the file system path specified for

NSR_ALT_PATH in Exchange client does not exist, it is
automatically created in NMM.
167
Table 25
Attribute name
Description
Values
NSR_EXCH2010_BACKUP=active
To back up only active database copies.
active
NSR_EXCH2010_BACKUP=passive
To back up only passive database copies.
passive
NSR_EXCH2010_BACKUP=all
To back up both active and passive

databases.
All
NSR_EXCH_CHECK=value
To specify the consistency check for

databases.
yes or no
By default, the consistency check for:
For backups in a DAG environment is no.
For backups in a Exchange 2010 stand-alone
environment is yes.
Note: If consistency check is turned off, then the
information is logged in the mega.xml file during backup.
NSR_EXCH2010_DAG=<DAG name>
To specify the DAG name for a backup in a

DAG environment.
DAG FQDN name

For example, DAG name.domain name.com
Configuring persistent and non-persistent snapshots

To configure:
Persistent snapshots Configuring snapshots on page 104 provides details

about how to configure persistent snapshots for Exchange Server 2010.
Non-persistent snapshots The steps to configure persistent snapshots and

non-persistent snapshots are similar:
1. Follow step 1 and step 2 provided in Configuring snapshots on page 104.
2. In step 3 , in the Properties > Backup Snapshots field, enter All. All the
snapshots that are created are rolled over to the tape or disk. Also, ensure that
the retain snapshot value is set to zero.
Note: In NMM, conventional recovery is performed. The EMC NetWorker Module for
Microsoft Applications Release 2.3 Administration Guide provides details for conventional
recovery. To recover the non-persistent snapshot backups, in the NMM UI, under Recover
Options > NetWorker, ensure that the Conventional Restore option is selected. By default,
the Conventional Restore option is selected.
168
Considerations for backing up Exchange 2010 in non-DAG and DAG environment

Table 26 on page 169 lists the considerations for backup in a DAG and non-DAG
environment.
Table 26
Considerations required for backup in non-DAG and DAG environment
Type of environment
Considerations
For stand-alone Exchange 2010 server
Use the save set APPLICATIONS:\Microsoft Exchange 2010.
For Exchange 2010 DAG
Configure a client resource for DAG name on the NetWorker server.

Configure a client resource for all the members of the DAG. This is an important requirement even if a
particular Mailbox server is not used for backup. The Exchange 2010 DAG backup will fail if NMM does
not find the client resources for all the Mailbox servers participating in DAG.
You can:
Configure multiple client resources for the same physical host with different database names in
save set field.
Configure multiple client resources for a different physical host with databases residing on those
physical hosts.
For the DAG members, provide the following attributes:
NSR_EXCH2010_DAG=<DAG FQDN>
NSR_EXCH2010_BACKUP = all/active/passive
A DAG resource is required for DAG backup because the data being backed up is indexed on DAG
name.
The databases in the DAG member must be in a healthy and mounted state before running the
backup.
Windows Authentication is enabled and Kernel Mode Authentication is not selected.
Use the following process to check or set Windows authentication:
1. Go to IIS Manager > Your Host > Sites > Default Web Site > Powershell.
2. On the right-hand side pane, double-click Authentication and Enable Windows Authentication.
3. In Windows Authentication, right-click and ensure that the Kernel Mode Authentication is clear.
Exchange 2010 incremental backup promoted to full backup

An incremental backup is promoted to a full backup under the following
circumstances:
If a full backup cannot be found for a database within a specified save set.
If a new Mailbox database is created after a full or incremental backup, then the
next backup is always promoted to full backup.
Log gaps are detected after the last backup. That is, there are gaps between
highest log number retrieved from index and the lowest log number retrieved
from the disk.
IMPORTANT
In Exchange 2010, it is recommended that you perform a full backup after changing
the log and database path. After changing the log and database path, if an
incremental backup is performed without first performing a full backup, then later
a recovery from the incremental backup leads to failures with log gaps.
169
Configuring Exchange Server 2010 backups

To perform an Exchange Server backup, complete the tasks outlined in Table 27 on
page 170.
IMPORTANT
Guide provides details for the first five tasks in Table 27 on page 170.
Table 27
Tasks for configuring an Exchange Server backup

Backup task
Consideration

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 persistent and non-persistent snapshots on

page 168 provides details.
Backup schedules determine the days on which full or

incremental backups are performed:
Full backups include all of the data specified in an NMM
client resource save set.
Incremental backups include only the data that has
changed since the last backup.
Configuring Exchange backup schedule on page 121
provides more information.

5. Configure a client group
The group resource is created so that the client resource

can be added to the required group. The main requirement
when configuring the group resource is that the Snapshot
checkbox must be selected. You can also select the
snapshot policy manually.
6. Configuring Exchange client resource on

page 170
This task is specific to configuring a Exchange client

resource.
Configuring Exchange client resource

Review the considerations listed in Table 26 on page 169 for backup in a DAG and
non-DAG environment.
To create a client resource for Exchange stand-alone or DAG environment:
Configuration.
4. In the Name attribute, type the fully qualified domain name FQDN of the
NetWorker client computer.
Note: Ensure not to use the short name of the NetWorker client computer because only
FQDN is supported.
170
5. In the Comment attribute, type a description. If you are creating multiple client
resources for the same NetWorker client host computer, use this attribute to
differentiate the purpose of each resource.
6. From the Browse Policy attribute list, select a browse policy. The browse policy
determines how long the rolled-over data is available for browsing.
Ensure that the browse policy is long enough for your expected recovery needs.
If your recovery needs are beyond the browse policy, an index recovery can be
performed and should be the preferred first step.
If index recovery is not possible, you can scan tapes to rebuild the index but
this should be the last option.
7. From the Retention Policy attribute list, select a retention policy. The EMC
NetWorker Module for Microsoft Applications Release 2.3 Administration Guide
provides details about the retention policy for Exchange.
a. Specify the components to be backed up.
b. Place multiple entries on separate lines by using the save set names in Table 24
on page 166.
URL encoding for save sets on page 23 provides details about URL-encoded
values for Exchange save sets.
be added.
Note: The backup group must be a snapshot group.
13. In the Access area, leave the Remote user and Password fields empty.
IMPORTANT
Do not select the DSN option under Device properties, otherwise the DAG
backup will fail.
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.
a. Type the following variable and value:
NSR_SNAP_TYPE=vss
b. Type Exchange application variable settings and their values on separate lines.
Table 25 on page 167 describes these settings.
171
c. Create the directory path, for example C:\mount_dir on the client machine
before specifying:
NSR_ALT_PATH=C:\mount_dir
Note: Do not backup an active database and a passive database at the same time when the
databases specified have the same name but are on different physical hosts.

17. Verify that the Aliases attribute displays the NETBIOS name for the client. This
name should have already been filled in automatically.
Note: NMM client uses the host machine NETBIOS or short name when connecting to
the NetWorker server to browse backups. If the NETBIOS name is not found, NMM will
18. Click OK.
Configuring Avamar deduplication backups in a DAG environment

Before performing the steps described in this section, create client resources for all the
DAG member servers and a client resource for the DAG name.
Before starting the DAG backup, perform the following steps in NMC:
1. In the NetWorker server's administration interface, click Configuration.
2. Select Clients in the navigation tree.
The Clients table appears.
3. Right-click on Clients in the navigation tree, or right-click any client in the
Clients table, and select New.
The General tab appears in the Create Client window.
4. In the General tab, specify Exchange DAG name as client name, with the
following exceptions:
a. Clear the Scheduled backup option.
b. In the Save set list, add the same save set list that is in the DAG member server
client resource.
5. In the Apps & Modules tab:
a. In the Access area, leave the Remote user and Password fields empty.
b. In the De-Duplication area:
a. Select the De-Duplication backup attribute to enable this client for
deduplication backups.
b. Select the name of the deduplication node to which this client's backup
data will be sent. This should be the same deduplication node specified for
the DAG member server.
This step links this client with its own deduplication node. Do not select
the name of a replication node.
6. Add this new DAG client resource to the backup group that contains the DAG
member client resource.
172
7. Start DAG backup.
Verifying backups
To verify if a backup is successful, use the following command on the NetWorker
server:
nsrinfo -s <Server> <Client Name>
where, the <Client Name> is the DAG name or Exchange 2010 Mailbox server name.
Performing Exchange Server 2010 recovery

Performing full recovery on page 173
Performing advanced recovery on page 173
Performing granular recovery of Mailbox, folder, or e-mail on page 178
IMPORTANT
Perform a full level backup after every recovery performed in Exchange 2010.
IMPORTANT
Before performing a recovery in Exchange 2010, ensure that the This database can
be overwritten by a restore option in Exchange Management Console is selected.
Performing full recovery

You can recovery the contents of a backed up database to the original database by
performing full recovery.
To perform full recovery:
1. In NMM 2.3, select Exchange 2010 Recover Session > Recover Options >
Recover in the task bar.
2. Select the database in the NMM 2.3 GUI.
3. Select Recover in task bar.
IMPORTANT
Always perform a full backup after performing a point-in-time or roll-forward
recovery.
Performing advanced recovery

In NMM 2.3, by using Exchange 2010 Recover Session > Recover Options >
Advanced Recover you can recover a database to:
A selected Recovery Database (RDB). Exchange Server 2010 supports the ability
to restore data directly to a RDB. Mounting the recovered data as a RDB allows
you to restore individual Mailboxes or individual items in a Mailbox.
An alternate database mounted on the Mailbox server where:

173
Backup was performed.

Backup was not performed.
A remote database. In remote database recovery, a selected Mailbox database is

restored to a remote Mailbox server, in the Exchange 2010 DAG where the active
database resides. The remote database recovery option is only available for
Exchange 2010 DAG and not for Exchange 2010 standalone.
Note: Alternate and remote recovery are supported only in the same domain.
Cross-domain Exchange recovery is not supported. That is, if two hosts are in different
domains, alternate or remote recovery cannot be performed.
To perform recovery of a DAG database:

for backup.
3. Select the DAG database to be recovered as shown in Figure 32 on page 174.
IMPORTANT
You can browse and recover individual Mailboxes and Mailbox items from the
list on the right pane.
Figure 32
Select Exchange 2010 database
4. In the Exchange 2010 Recover Session toolbar, click the Advanced Recover
Option.
The Advanced Recover dialog box appears. This dialog box lists the three steps
for recovery:
Select Recovery
Select DB & Server
174
Summary
Figure 33
Advanced Recovery dialog box

Note: Click Recover Options to skip the steps for Advanced Recovery and perform full
recovery of the database listed in Database (Source).
5. In Select Recovery Type, under Recovery Type, select one of the following:
Recovery Database (RDB) Recovery Recovery to Recovery Database
(RDB) on page 175 provides details.
Alternate Database Recovery Recovery to an alternate database on
page 177 provides details.
Remote Database Recovery Recovery to a remote database on page 178
provides details.
Recovery to Recovery Database (RDB)
To perform recoveries to RDB for Exchange 2010:
1. In the Advanced Recovery window, select Recovery Database (RDB) Recovery
and click Next.
The Manage RDB window appears.
Figure 34
Manage RDB window
175
2. You can create a new RDB or select a RDB from the Recovery Database (RDB)
List. To create a new RDB, click Create.
The Create_DB window appears.
Figure 35
Create_DB window
In the Create_DB window:

a. In the RDB Name field, type a name for the new RDB.
b. In the EBD File Path field, browse and select the file path location for the new
RDB.
c. In the Log File Path field, browse and select the location for the log file.
Note: Backup fails if the logs path and Mailbox database path are in the same volume.
Ensure that the logs path and Mailbox database path are not in the same volume, even
if the logs and database reside on mount point or normal path.
d. Click Create.
The new RDB is created and appears in the Recovey Database (RDB) List.
3. From the Manage RDB window, you can also:
Delete a RDB Select the RDB from the Recovery Database (RDB) List and
click Delete.
Unmount a RDB If a RDB is mounted but you are getting an error during
recovery, you can unmount the RDB and then re-mount the same or another
RDB for recovery. To unmount a RDB, select the RDB from the Recovery
Database (RDB) List and click Unmount.
Mount a RDB Select a RDB from the Recovery Database (RDB) List and
click Mount. Only one RDB can be mounted at a time.
Ensure that the RDB is mounted on the current node of the NMM client for
successful recovery. If the database being recovered is not mounted on the
current node or if replication is on, then the recovery will fail.
Overwrite a RDB Select a RDB from the Recovery Database (RDB) List and
click RDB Overwrite. The RDB is overwritten by the recovery operation.
IMPORTANT
Ensure that the RDB is mounted before proceeding to the next step.
4. Select the created RDB and click Next.
176
The Exchange Recovery Summary window appears. This window lists the
Exchange Server recovery options and the NetWorker recovery options and
allows you to review the details before proceeding with recovery.
Note: Click Back to make changes to the recovery options that were previously selected by
you.
Figure 36
Exchange Recovery Summary
5. To proceed with recovery, click Start Recovery.

Recovery to an alternate database
Alternate database recovery is supported on any Mailbox server. In this type of
recovery, the backed up Mailbox database is recovered to a new database other than
the original Mailbox database. Alternate database recovery is supported in both
Exchange 2010 stand-alone and DAG environments.
To perform recoveries to an alternate database:
1. In the Advanced Recovery window, select Alternate Database Recovery for
recovery to an alternate database.
2. Click Next.
The Select Database window appears with a list of alternate databases.
Figure 37
Select Database window

177
3. Select the database to which you want to perform the recovery and click Next.
Note: Click Back if you want to make changes to the recovery options that were previously
selected by you.

Recovery to a remote database
Remote database recovery is supported only in a Exchange 2010 DAG environment.
Remote recovery to a host that is not a part of DAG cannot be performed.
By performing remote recovery, you can start roll-forward or PIT recovery from a
Mailbox server that is not actually mounted. After remote recovery is started from
DAG member server where Mailbox database is not mounted, that is the Mailbox
database with the passive copy, the recovery service nsrsnap_vss_recover.exe is
automatically started in the DAG member server where the Mailbox database was
originally mounted, that is the Mailbox database with the active copy.
To perform recoveries to a remote database:
1. In the Advanced Recovery window, select Remote Database Recovery for
recovery to an remote database in a Exchange DAG member.
2. Click Next.
The Select Database window appears with a list of remote databases.
3. Select the database to which you want to perform the recovery and click Next.
Note: Click Back if you want to make changes to the recovery options that were previously
selected by you.
Performing granular recovery of Mailbox, folder, or e-mail

Ensure that the following requirements have been taken care of before performing
RDB item-level browsing:
At least one public folder database is created in that Exchange organization.
IPv6 is disabled in the Exchange machine, where RDB item-level browsing is

performed. Disable IPv6 in the registry setting. Include the registry key and value
to disable IPv6.
Exchange Server 2010 permissions for RDB Mailboxes browsing are provided.
To provide the permissions, perform the following steps:
a. On the Microsoft Exchange Server, select the Start > All Programs > Exchange
Management Shell.
b. Enable Send-As and Receive-As permission.
178
For example:
get-ExchangeServer <Exchange Server name> |
Add-AdPermission -user <username> -extendedrights
Receive-As, Send-As
where:
<Exchange Server name> is the server where the RDB Mailbox is located.
<username> is the name of the user being granted permissions.
MAPI/CDO 1.2.1 Kit installed.
To recover a Mailbox, folder, or even an email:

for backup.
3. Select the Mailbox, folder, or email to be recovered as shown in Figure 38 on
page 179.
Figure 38
Select Mailbox, folder or e-mail for recovery
4. Select Recover in task bar.
Performing a quick recovery of a deleted Mailbox in Exchange 2010

The procedure to recover a deleted Mailbox in Exchange 2010 is performed
independent of NMM backup or recovery operations, and is similar to the procedure
followed for Exchange 2007. Performing a quick recovery of a deleted mailbox in
Exchange 2007 on page 158 provides details.
Microsoft Exchange Server 2010 disaster recovery

For Microsoft Exchange Server 2010 disaster recovery on Windows 2008 and
Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery.
Chapter 10, Windows Disaster Recovery with NetWorker 7.6 SP2 and NMM
provides details.
Performing a quick recovery of a deleted Mailbox in Exchange 2010
179
180
7
Microsoft SharePoint
Server 2003 Backup
and Recovery
Overview ......................................................................................................................
Performing SharePoint Server 2003 backups ..........................................................
Performing SharePoint Server 2003 recovery .........................................................
Example of SharePoint Server 2003 backup and recovery process......................
182
183
183
184
181
Overview
SharePoint Server 2003 by using EMC NetWorker Module for Microsoft Applications
(NMM).
This section contains the following:
Microsoft SharePoint Portal Server 2003 and Windows SharePoint Services 2.0
on page 182
Types of supported backup on page 182
Writer required for SharePoint Server 2003 backup on page 182
Microsoft SharePoint Portal Server 2003 and Windows SharePoint Services 2.0
In NMM 2.3, Microsoft SharePoint Portal Server 2003 with Windows SharePoint
Services 2.0 is supported.
SharePoint Portal Server 2003 and Windows SharePoint Server (WSS) 2.0 do not have
their own VSS writers. The SharePoint Server 2003 databases are hosted on a SQL
Server 2005. NMM uses the SQL Server VSS writers to first perform backup and
recovery of the SQL databases. After the SQL databases are recovered, the SharePoint
recovery is performed.
Types of supported backup

NMM provides the following types of backup for SharePoint Server 2003:
SharePoint Server 2003 database backup Configuration database
SharePoint Portal Server 2003 portal sites backup, including the following
databases:
Content database
User profile database
Services database
Index databases
Only full backup level in supported in SharePoint Server 2003.
Writer required for SharePoint Server 2003 backup

SQL Server 2005 provides the application writer SqlServerWriter for SharePoint
Server 2003.
182
Performing SharePoint Server 2003 backups

NMM provides full backup and individual content databases backup, which allows
you to protect your SharePoint farm with individual content database backups
between full backups. It is recommended that you configure separate backup
schedules for full backups and individual content database backups.
Review Chapter 1, Microsoft SQL Server Backup and Recovery, for details on the
following topics for SharePoint Server 2003 backups:
For SQL application information variable settings in SharePoint Server 2003

backup The application information variable settings in SharePoint Server
2003 backup are the same as those for SQL Server. Table 1 on page 22 lists the
application information variable settings.
Displaying valid SQL data save sets for SharePoint Server 2003 backup
Displaying valid SQL data save sets on page 23 provides details about the SQL
save sets that are available for SharePoint Server 2003 backup.
Configure a SharePoint Server 2003 client resource The procedure for

configuring a client resource for SQL and SharePoint Server 2003 are similar.
Follow the procedure in Configuring SQL Server backups on page 26 for
details about configuring a SharePoint Server 2003 client resource.
Performing SharePoint Server 2003 recovery

Performing SQL Server recovery on page 27 provides the steps to recover the SQL
Server databases to the SQL Server. After the databases are recovered, they may need
to be updated and added to the SharePoint portal.
After performing a SQL Server 2005 database recovery:
1. Start the SQL Server services.
2. Launch SQL Enterprise Manager to verify that the databases have been
successfully recovered within SQL Server.
3. Launch SharePoint Server 2003 Central Administration.
4. Click List and Manage Portal Sites.
5. 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.
183
Example of SharePoint Server 2003 backup and recovery process

This descriptive example provides an overview of the interaction between SQL
Server, NMM, and SharePoint Server for SharePoint backup and recovery by using
NMM 2.3.
In this example, an organization is using the following configuration for its
SharePoint backup and recovery process:
Microsoft SharePoint Portal server 2003 Service Pack 2 and Windows SharePoint
Services 2.0 Service Pack 2 on Windows Server 2003.
SQL 2005 Server.
NMM 2.3, which is used for the backup and recovery process.
Note: For detailed information on using SQL Server and SharePoint Server, consult the
respective Microsoft documentation for those products.
The following sections describe the backup and recovery operation performed by the
organizations SharePoint administrator:
Creating a new SharePoint portal with three new databases on page 184
Viewing the location and hierarchy of databases in the SQL Enterprise Manager
GUI on page 185
Configuring and performing a backup of the new databases with NMM save
sets on page 185
Verifying the backup in NMM UI on page 185
Deleting the new databases on page 186
Performing NMM recovery on page 186
Verifying database recovery through the SQL Enterprise Manager on page 186
Recovering the portal site through SharePoint Portal Server Central

Administration on page 187
Verifying the recovery of the portal site in SharePoint Server Central

Administration on page 190
Creating a new SharePoint portal with three new databases

The administrator uses SharePoint Portal Server Central Administration to create a
new portal test11 with three SQL databases on the GAL Server:
test11_SITE
test11_PROF
test11_SERV
The organization puts the portal test11 into use by creating sites, and by uploading
documents, pictures, events, and other items.
184
Viewing the location and hierarchy of databases in the SQL Enterprise Manager GUI
The administrator views the location and hierarchy of the created databases in the
SQL Enterprise Manager GUI. Figure 39 on page 185 displays the new databases in
the SQL Enterprise Manager.
Figure 39
Newly created databases created in SharePoint
Configuring and performing a backup of the new databases with NMM save sets
To configure and perform the backup, the administrator:
Determines the save sets that are available by using the nsrsnap_vss_save -?
command, and follows the steps for creating a SQL Server backup as described in
Performing SQL Server backups on page 22.
Specifies the save set APPLICATIONS:\SqlServerWriter to back up all of the

SharePoint databases.
Specifies the save set APPLICATIONS:\SqlServerWriter\GALL%5Ctest11_PROF

to back up just the test11_PROF database.
Verifying the backup in NMM UI

The administrator verifies the databases that have been backed up by looking at the
available recovery sets in NMM. In the navigation tree, the administrator expands the
Applications folder, the SqlServerWriter folder, and then the GALL Server folder.
Figure 40 on page 186 shows that all of the databases, including the three new
test11... databases, were backed up.
185
Figure 40
NMM backups available for recovery
Deleting the new databases

The administrator deletes the portal from the SharePoint Server. The deletion of the
portal deletes the three new test11... databases from SQL. During deletion,
SharePoint displays a message to confirm that the administrator wants to delete the
databases. The administrator clicks Yes and the databases are deleted.
Performing NMM recovery

The administrator opens NMM again to recover the three databases. The
administrator selects the databases that were just deleted from SharePoint.
Figure 41 on page 186 shows test11_PROF, test11_SERV, and test11_SITE databases
selected by the administrator.
Figure 41
SQL databases selected for recovery in NMM
The administrator clicks Start Recover. The recovery is successful.
Verifying database recovery through the SQL Enterprise Manager

The administrator launches SQL Enterprise Manager and verifies that all three
databases have been recovered. Figure 42 on page 187 shows that the three databases
were recovered to the SQL Server.
186
Figure 42
Databases recovered to SQL Server
Recovering the portal site through SharePoint Portal Server Central Administration
Recovering the SQL databases does not automatically bring them back into
SharePoint.
In SharePoint, the administrator performs the following tasks:
1. Launches SharePoint Portal Server Central Administration. Figure 43 on
page 187 shows the Portal Site and Virtual Server Configuration window.
Figure 43
SharePoint Server Central Administration page
2. Clicks List and Manage Portal Sites.
187
In Figure 44 on page 188, the Manage Portal Sites window does not display the
portal site.
Figure 44
SharePoint Portal Server Central Administration, Manage Portal Sites window
3. Clicks Recover Portal Site.

Figure 45 on page 188 shows the options for creating and restoring the portal.
Figure 45
Portal creation and restore options
4. Selects Restore a portal, and types the Site database name test11_SITE, User
profile database server test11_PROF, and Services database server
test11_SERV.
Figure 46 on page 189 shows the settings specified.
188
Figure 46
Portal restore and database names
After typing information in this window, a confirmation window appears, as

shown in Figure 47 on page 189.
Figure 47
Confirmation window to request creation of the portal site
5. Clicks OK and portal recovery begins. Figure 48 on page 189 shows the status
window that appears in SharePoint Portal Server Central Administration
during portal creation.
Figure 48
Status window for portal recovery process

189
Figure 49 on page 190 shows the window that indicates that the portal recovery
was successful.
Figure 49
Operation Successful page displayed when portal recovery is complete
Verifying the recovery of the portal site in SharePoint Server Central Administration
In SharePoint Portal Server Central Administration, the administrator launches the
Manage Portal Sites window, and the Portal Site is now listed as shown in Figure 50
on page 190.
Figure 50
Recovered databases and SharePoint portal visible and available in SharePoint
IMPORTANT
Table 5 on page 39 lists the best practices and recommendations to follow when
using NMM to back up and recover SQL Server.
190
8
Server 2007 Backup
and Recovery
Overview ......................................................................................................................
Performing SharePoint Server 2007 farm hardware backups...............................
Performing SharePoint Server 2007 disaster recovery...........................................
Keeping backups and recoveries in sync.................................................................
Best practices................................................................................................................
Backing up SharePoint database by using NMM and NMSQL ...........................
192
200
207
210
213
215
216
217
191
Overview
(NMM).
This section contains the following:
NMM solutions for protecting a SharePoint Server 2007 farm on page 192
Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0
on page 194
Types of SharePoint Server 2007 backup and recovery on page 194
Backup and recovery levels on page 194
Microsoft Office SharePoint 2007 farm configurations on page 195
SharePoint Server 2007 writers on page 199
IMPORTANT
NMM 2.3 does not support SharePoint Server 2007 granular backup and recovery.
For SharePoint granular recoveries of SharePoint sites and site components, use
the NMM 2.3 SharePoint VSS writer-level backup capability. Content databases
from a SharePoint VSS writer-level backup can be recovered to alternate locations
for data mining by third-party SharePoint granular recovery tools, such as Kroll
Ontrack PowerControls. However, if you do not want to use the third-party tools, it
is recommended that you use NMM 2.2 SP1 or earlier.
NMM solutions for protecting a SharePoint Server 2007 farm

You can use the SharePoint VSS writer for SharePoint Server 2007 farm backup and
recovery. This method leverages the Windows Server VSS framework to take VSS
snapshots of the SharePoint configuration database, search databases, indexes, and
content databases. These VSS snapshots can be backed up on-host by using the
Windows VSS system provider or off-host by using VSS hardware providers.
Note: The System Provider is the software VSS provider that Microsoft provides as part of the
operating system.
These important notes provide an introduction to using NMM for SharePoint Server
2007 farm protection:
By using the SharePoint VSS writer backup and recovery method, both full farm
and individual content databases can be recovered.
NetWorker and NMM integrate with Microsoft Office SharePoint Server 2007 by
using the SharePoint VSS writer. The SharePoint Server 2007 VSS writer is
dependent on the SQL Server VSS writer.
By using the SharePoint Server VSS writer, NetWorker takes VSS snapshots of the
entire SharePoint farm for data protection.
By using this VSS writer, NMM backs up the following SharePoint components:
Configuration database Which is the SQL configuration database
Content database Which is the SQL content database
192
SharePoint search SharePoint search index and associated SQL databases

Microsoft Office search Microsoft Office search index and associated
databases
This type of data protection allows recovery of an entire farm when there is a
disaster.
NMM leverages the Windows VSS framework and Microsoft Office SharePoint
Server 2007 VSS writer for consistent point-in-time snapshots and backs up the
entire SharePoint farm.
NMM supports off-host or LAN-free backups with supported VSS hardware

providers:
Supported hardware provider arrays include EMC Symmetrix, V-MAX,
Symmetrix DMX, EMC CLARiiON, and EMC Celerra. Third-party arrays are
also supported.
The EMC Software Compatibility Guide provides details.
By using a supported VSS hardware provider, it is possible to take
transportable snapshots of the complete SharePoint farm, which includes the
configuration database, content databases, search databases, and search
indexes.
An NMM proxy node installed on a NetWorker storage node allows off-host
backup of the snapshot data. Off-host backups ensure that there is no backup
load on the SharePoint application servers.
For information about VSS technology, download the Microsoft TechNet article, Best
Practices for Using Volume Shadow Copy Service, available on the Microsoft website.
The advantages of performing backup and recovery through a VSS writer are as
follows:
A single VSS reference writer To successfully back up a full SharePoint farm,

NMM uses a single writer, the SharePoint Server VSS writer, to back up
Microsoft Office SharePoint Server 2007.
Full farm backup and restore for catastrophe The VSS writer allows NMM
easily access to the VSS API, and request a backup or recovery operation for an
entire SharePoint farm, including a system state and web application
configuration.
Database-level granularity The VSS writer allows NMM to select all the
databases or a single database for backup operations.
SharePoint inventory list Before backup, the SharePoint writer generates a flat
inventory list of databases selected for backup within the farm. The list is
returned to NMM so that backup can be performed on the location where the
database is physically located.
Backup content without interruption An application can modify a file while it

is being backed up, causing data corruption or causing an error when the file is
opened. VSS allows a quick snapshot of the file, while allowing the application to
operate at the original location without interruption.
Overview
193
Search index files backup and recovery Because search index files are stored in
the file system, a separate file writer is required to back them up. Microsoft Office
SharePoint Server 2007 includes a separate search writer that handles search
index files.
Microsoft Office SharePoint Server 2007 imposes cross-writer dependencies in
such a way that search index files are backed up or restored when backing up
registered databases in the farm.
Post-recovery synchronization of databases To ensure that all the databases are

synchronized with the farm after a recovery operation is complete, each database
is automatically detached and reattached to the farm after the recovery.
Additional procedures are not required to resynchronize the restored databases.
Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0
Microsoft Office SharePoint Server 2007 with Windows SharePoint Services 3.0 is
supported.
Backup and disaster recovery use both, the SharePoint Server VSS writers and SQL
VSS writers.
Types of SharePoint Server 2007 backup and recovery

NMM provides the following types of backup:
Stand-alone backup To back up all SharePoint data in a single farm.
Farm backup To back up all SharePoint data in a distributed farm, including:

Content and configuration databases
Search index and databases
NMM provides the following types of recovery:
Snapshot recovery
Conventional recovery
Note: Rollback recovery and directed recovery of SharePoint writer are not supported.
Directed recovery of content databases can be performed through SQL Server writer.
Backup and recovery levels

The backup level is:
Full
The recovery levels are:
194
Full
Content
SharePoint search, which includes SharePoint search index and associated SQL
database
Microsoft Office search, which includes Microsoft Office search index and
associated SQL database
Note: Search and Index databases are backed up and recovered as part of farm-level backup
and recovery.
Microsoft Office SharePoint 2007 farm configurations

A Microsoft Office SharePoint 2007 farm can be deployed in a:
Stand-alone farm system The stand-alone configuration runs all the services on
one host, as shown in Figure 51 on page 196.
Distributed farm configuration The distributed farm configuration includes

several servers that host separate services, as shown in Figure 52 on page 196.
IMPORTANT
To back up the entire SharePoint farm, the NMM client must be installed on the
following:
Each server that hosts SharePoint data, including servers that host content index
and search index.
At least one web front-end server.
A SharePoint farm includes the following services and servers:
Central Administration site and shared services These are usually installed on
an application server.
Web front-end server This is the web page-based user interface to manage the
server. A web front-end server can also be configured as a dedicated crawler.
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.
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)
Overview
195
Configuration
database
Content
database
NetWorker server
7.5.3 or later, or 7.6.1 or later:
Administers protection
for NetWorker modules,
such as NMM
Web front-end
Index server
Query server
Microsoft SQL server
NMM
GEN-000751
Figure 51
SharePoint Server 2007 stand-alone farm configuration
Query server
Index server
(If there is more than Query
server, the Query servers
cannot be included on the
Index server)
NMM
Configuration database
(1 per farm)
NetWorker Server
7.5.3 or later,
or 7.6.1 or later:
Administers
protection for
NetWorker module
such as NMM
Web front-end
On an application server
NMM
Content database 1
(1 or more per farm)
Content database 2
Microsoft SQL server

Contains all SharePoint databases
NMM
GEN-000752
Figure 52
196
SharePoint Server 2007 distributed farm configuration
Example 1: SharePoint
Server stand-alone farm
Server distributed farm
A stand-alone farm in which the host contains the SharePoint Server and SQL Server.
The Networker server should backup the following on same client:
APPLICATIONS:\Microsoft Office SharePoint Services
A distributed farm with two servers of which one contains the web front-end and
Central Admin, and the other contains the SQL Server.
The NetWorker server has two client resources, one for each server. Each client
resource has different save sets:
SharePoint web front-end host save set for resource 1:

SQL Server host save set for resource 2:

Server distributed farm
A distributed farm with three servers running the following services:

Server 1
Server 1 runs the following services:
Windows SharePoint Services Incoming E-Mail
Windows SharePoint Services Web Application
Server 1 has the following roles:
Web front-end server
Windows SharePoint Services VSS Writer (registered on this machine)
The output for Server 1 is as follows:

nsrsnap_vss_save -?
APPLICATIONS:\Microsoft Office SharePoint Services\server2%5Csp07inst
APPLICATIONS:\Microsoft Office SharePoint
Services\server2%5Csp07inst\Content Database
WSS_Content_5187234b07fd4d2e9c2a3ab47ca2361c
Ensure NetWorker client 'server2' is part of the snapshot group with
saveset for 'SQL Writer' component 'server2%5CSP07INST
\WSS_Content_5187234b07fd4d2e9c2a3ab47ca2361c'
Services\server2%5Csp07inst\Content Database
SharePoint_AdminContent_c12ae956-3
97a-4ffc-8e2b-b2b10425be06
\SharePoint_AdminContent_c12ae956-397a-4ffc-8e2b-b2b10425be06'
Services\server2%5Csp07inst\Content Database WSS_Content
\WSS_Content'
APPLICATIONS:\Microsoft Office SharePoint Services\server3
APPLICATIONS:\Microsoft Office SharePoint Services\server3\SPSearch
Content Index Catalog
saveset for 'SPSearch VSS Writer' component 'server3\Conte
ntIndex_SPSearch'
Overview
197
APPLICATIONS:\Microsoft Office SharePoint Services\server1

APPLICATIONS:\Microsoft Office SharePoint Services\server1\SPSearch
Content Index Catalog"
Depends on 'SYSTEM COMPONENTS:\Microsoft Office SharePoint
Search\ContentIndex_SPSearch' on Client 'server1'
Server 2
Runs the SQL database service
Maintains the content database server role
The output for Server 2 is as follows:

nsrsnap_vss_save -?
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\master
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\model
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\msdb
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharePoint_Config
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharePoint_AdminCont
ent_c12ae956
-397a-4ffc-8e2b-b2b10425be06
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Content
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Search_WS200
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Content_5187234b
07fd4d2e9c2a
3ab47ca2361c"
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharedServices1_DB
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\SharedServices1_Sear
ch_DB
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Search_WS2
APPLICATIONS:\SqlServerWriter\server2%5CSP07INST\WSS_Search_WS2-temp
Server 3
Central Administration
Document Conversions Launcher Service
Document Conversions Load Balancer Service
Office SharePoint Server Search
Windows SharePoint Services Help Search
Windows SharePoint Services Incoming E-Mail
Windows SharePoint Services Web Application
Server 3 has the following roles:
198
Web front-end server
Windows SharePoint Services Help Search
Office Sharepoint Server Search
Index and Search server
Query server
The output for Server 3 if registered is as follows:

SYSTEM COMPONENTS:\Microsoft Office SharePoint Search
SYSTEM COMPONENTS:\Microsoft Office Search
Conclusion
In this example, the following save sets are backed up on each server.
Table 28
Example: Minimum required save sets to be backed up

Type of backup data
Minimum required save sets to be backed up
Server 1
Take individual backups of all these save sets:

SYSTEM COMPONENTS:\
C:\
D:\
Note: If the client is using a hardware backup with a Data Mover, then this
combination might fail because both hardware and software backup
operations are used.
Note: It is required to register the Windows SharePoint Services VSS writer

on one of the web front servers in the farm. In this example, the Windows
SharePoint Services VSS writer on Server 1 has been registered.
Server 2

SYSTEM COMPONENTS:\
C:\ (All Volumes)
D:\ (All Volumes)
Server 3

C:\ (All Volumes)
D:\ (All Volumes)
SharePoint Server 2007 writers

Table 29 on page 199 list the writers supported by SharePoint Server 2007:
Table 29
List of supported SharePoint Server 2007 writers

SharePoint Server
server
SharePoint Server
2007
Server 2007 provides
VSS writers
Writer
Description
SqlServer Writer
The writer for SQL databases
Windows SharePoint Services

VSS Writer
The writer for SharePoint Server 2007, which runs

on the web front-end
SharePoint Search Writer
The writer for SharePoint Server 2007 search
Office Server Search Writer
The writer for Microsoft Office Server search
Overview
199

This section provides information that is needed to back up SharePoint Server 2007:
SharePoint Server 2007 application information variable settings on page 200
Specifying SharePoint Server 2007 save sets for application data on page 201
Displaying valid SharePoint Server 2007 data save sets on page 201
URL encoding for SharePoint save sets on page 202
Configuring dedicated web front-end crawling on page 202
Configuring SharePoint Server 2007 backups on page 202
IMPORTANT
Any major changes made to the SharePoint configuration or database structure
requires a full backup. For example, if a full farm backup is performed on
Monday, and then a new content database is added on Tuesday, a full backup
needs to be performed to keep the backups up-to-date. The save set list also needs
to be updated to include the new SharePoint objects.
SharePoint Server 2007 application information variable settings

Table 30 on page 200 lists the variables that can be specified in the application
Table 30
SharePoint Server application information variable settings
Attribute name
Description
Values
NSR_SNAP_TYPE=value
Specifies the snapshot service provider name.
vss
Specifies the hostname of the NMM client that mounts

the snapshot from NMM client.

If no value is typed, the local host is used as the
data mover.
If you are setting up a proxy client for a virtual
cluster server, you must also type the proxy client
hostname in the Remote Access attribute of the
client resource.
Note: This attribute should be used only for hardware

backups.
200
Specifying SharePoint Server 2007 save sets for application data

Specify the SharePoint Server 2007 data save sets in the Save Set attribute of a client
resource. Table 31 on page 201 lists the SharePoint Server 2007 save set syntax that
specifies the supported types of SharePoint Server 2007 data.
Table 31
SharePoint Server save set syntax

Type of backup data
Save set syntax
SharePoint databases on SQL Server
Full SharePoint backup

Services
SharePoint content database
APPLICATIONS:\SqlServerWriter\Mars1%5CInsta
ncename\database_name
SharePoint Search Index and

SharePoint Content Index

SYSTEM COMPONENTS:\Microsoft Office Sharepoint Search
IMPORTANT
During SharePoint Server 2007 stand-alone backup and recovery, the
APPLICATIONS:\Microsoft Office SharePoint Services save set automatically
includes all the local dependent SQL save sets, such as
SYSTEM COMPONENTS:\sql embedded\instance\database for embedded SQL
Server and APPLICATIONS:\SqlServerWriter\instance\database for any other
SQL Server.
Displaying valid SharePoint Server 2007 data save sets

To display a list of the SharePoint Server 2007 save sets that are available for backup:
names:
nsrsnap_vss_save -?
3. Press Enter:
line.
201
URL encoding for SharePoint save sets

Configuring dedicated web front-end crawling

To configure a dedicated web front-end by using SharePoint Central Administration:
1. First, back up the existing host file.
2. By using SharePoint Central Administration, configure dedicated web front-end
crawling.
3. Once the configuration is complete, a new host file is created by SharePoint
Central Administration.
4. Append the host file information from backed up host file to the new host file.
5. Configure NMM backup.
Configuring SharePoint Server 2007 backups

Ensure that the following requirements are take care of before configuring SharePoint
Server 2007 backups:
Install the NMM client on each host in the SharePoint farm.
For distributed configurations, register the SharePoint writer on at least 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 recoveries.
Create client resources for each web front-end servers and SQL Servers in the
SharePoint farm.
Set the save set syntax reported by nsrsnap_vss_save.exe -? in the client resources
of each web front-end servers and SQL Servers:
SharePoint save sets:
SQL save set:

202
Based on backup strategies and requirements, include ALL or System Volumes

(C:\, D:\, and so on), and SYSTEM COMPONENTS:\ in the save set list.
Put the SharePoint Server and SQL Server client resources in the same group to
avoid inconsistencies in SharePoint data.
Do not put more than one instance of a client resource in the same group.
SharePoint writer and file system save sets can be in different groups.
To configure a SharePoint Server 2007 backup, perform the following tasks outlined
in Table 32 on page 203.
Table 32
Tasks for SharePoint Server 2007 backups

Tasks
Considerations
1. Enable services for backup on

page 203
Several services must be enabled and started on the hosts where the
VSS writers are run or SharePoint search activities are being performed,
or else backup fails.
2. Schedule backup
NMM provides farm backup and individual content database backup,

which allows you to protect your SharePoint farm with individual content
database backups between farm backups. It is recommended that you
configure separate backup schedules for farm backups and individual
content database backups.
Perform the following tasks for scheduling a backup as described the
EMC NetWorker Module for Microsoft Applications Release 2.3
Administration Guide:
Note: All the SharePoint hosts must be in the same NetWorker group
resource and only one instance of each client must be present in the
group.
3. Configure a SharePoint Server

2007 client resource on
page 204
Create the client resource and then perform the backup.
IMPORTANT
As part of disaster recovery plan, back up either of the following on the application
hosts:
- The save set All attribute in the save set field of the client resource.
Or
- The SYSTEM COMPONENTS:\ save set along with the system volume, for
example C:\.
Enable services for backup
Before starting a backup, ensure that the following services are enabled and running
on the hosts, or else the backup will fail:
Windows SharePoint VSS writer that runs only on the web front-end host
SQL Server VSS writer that runs on any host that contains the configuration
database, or one or more content databases
In addition, ensure that the following services are enabled and started on the host
before any SharePoint search activities are performed:
Microsoft Office SharePoint Server Search
Windows SharePoint Server Search
Note: The service for the writers must be enabled on each host:
On a stand-alone farm, all of these writers and services run on one host.
In a distributed farm, the SQL Server and SharePoint Servers may run on separate hosts.
203
To register the SharePoint writer for distributed configurations:

1. The SharePoint writer must be registered on a web front-end server by using the
command line STSADM.exe. Go to the following location for the STSADM.exe:
C:\Program Files\Common files \Microsoft Shared \Web server
extension\12\BIN
2. Type the following command to register the SharePoint writer:
Run STSADM.EXE -o registerwsswriter
To start the SharePoint Server and SQL Server writers, complete the following steps
on the host where the writers are registered:
IMPORTANT
These steps must be completed on each machine where the VSS writers will be
run.
1. Start Windows Services by using the appropriate steps for your operating system:
a. In Windows Server 2003:
a. Click Start >Control Panel >Administrative Tools.
b. Double-click Services.
b. In Windows Server 2008, click Start > Administrative Tools >Services.
2. Right-click the SQL Server VSS Writer service, and click Properties.
Note: The SQL Server VSS writer is available on any host 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 enabled writer, and click Start.
5. For each of the listed writers present on the host, repeat step 1 to step 4 .
6. Once these writers are registered and started, schedule a backup.
7. After scheduling the backup, configure a SharePoint Server 2007 client resource.
Configure a SharePoint Server 2007 client resource on page 204 describes how
to configure a SharePoint Server 2007 client resource.
Configure a SharePoint Server 2007 client resource
For each host in the SharePoint farm, create a client resource by using the NetWorker
Management Console, and assign the client resource to the same backup group.
The procedure to create the client resource depends on whether the backup is
performed for a stand-alone SharePoint farm or distributed SharePoint farm:
Configuring a SharePoint client resource to back up a stand-alone farm on

page 205
Configuring a SharePoint client resource to perform a full backup of a

distributed farm on page 206
Note: In a distributed SharePoint farm, one or more SharePoint services may be located
remotely on separate hosts from the SharePoint web front-end.
204
For NetWorker to successfully save all client resources in the SharePoint farm:
All the client resources must be in the same NetWorker group.
Backups must be initiated through the client resource on each remote host and
the web front-end. Recovery fails if the backup is only initiated through the web
front-end, because although NMM displays all of the SharePoint farm save sets
on the web front-end, the remote client backups were never performed.
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:
Configuration.
4. In the Name attribute, type the hostname of the NetWorker client.
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:
Note: The SQL system databases are not backed with this save set, only the databases
associated with the SharePoint farm are backed up.
If needed, use URL-encoded values when specifying save set names in the
Save Set attribute of the client resource. A table of values is provided in
Table 2 on page 24.
be added.
8. In the Backup command attribute, type the backup command.
For VSS backups, type the following command:
9. In the Application information attribute, type the following variable and value:
NSR_SNAP_TYPE=vss
Type each SharePoint application variable setting and it values on a separate
line.
These settings are described in Table 30 on page 200.
205
10. Click the Globals (1 of 2) tab:

a. In the Aliases attribute, type the NETBIOS name for the client.
Note: NMM client uses the host machine NETBIOS or short name when connecting
to the NetWorker server to browse backups. If the NETBIOS name is not found, NMM
will not be able to display backups.
b. Click OK.
Configuring a SharePoint client resource to perform a full backup of a
distributed farm
In a distributed configuration, you must set up a client resource for the web front-end
server where the SharePoint VSS writer was enabled.
You do not need a client resource on each web front-end unless you are
implementing a system-level disaster recovery backup schedule for these hosts. The
client resource can specify a full farm backup or a content database backup.
To configure a SharePoint client resource to perform a full backup of a distributed
farm:
1. For each host in the farm:
a. Perform step 1 through step 4 as in Configuring a SharePoint client resource
to back up a stand-alone farm on page 205
b. 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.
c. Select the Scheduled Backups attribute.
For the host where the SharePoint VSS writer is registered:
a. Specify the save set name:
b. Proceed to step 3 .
For the SQL Server host:
a. Specify the save set name:
b. Proceed to step 3 .
For all other SharePoint hosts:
a. Determine the save sets available on a specific host by following the steps
in Displaying valid SharePoint Server 2007 data save sets on page 201.
Note: Each host in a distributed farm requires a separate client resource, and the
client resource for a given host should only contain the SharePoint save sets on that
host.
b. Specify the available save set names for that host.

c. Proceed to step 3 .
Note: The Search and Index databases cannot be backed up by themselves. These
databases are backed up as part of a farm-level SharePoint backup.
206
If needed, use URL-encoded values when specifying save set names in the Save
Set attribute of the client resource. A table of values is provided in Table 2 on
page 24.
be added.
groups, ensure that the Start Time attribute for each backup group is spaced in a
way that the backups for the hosts client resources do not overlap.
5. In the Backup command attribute, type the following command for VSS backups:
6. In the Application information attribute, type the following variable and value:
NSR_SNAP_TYPE=vss
Type each SharePoint application variable setting and its value on a separate
line.
These variables are described in Table 30 on page 200.
9. Click OK.
Performing SharePoint Server 2007 farm hardware backups

VSS hardware providers allow you to create shadows without imposing a load on the
local client or production server. Here the snapshot is referred to as a shadow. You
have an option to make the shadow transportable, which allows you to mount or
import the shadow on another client.
The NMM software uses the default provider to create the shadow. If you have
installed a hardware provider, this becomes the default provider, and the NMM
software uses the hardware provider in place of Microsoft VSS provider. The VSS
hardware provider takes precedence over the Microsoft Software Shadow Copy
provider. The EMC hardware providers are Symmetrix and CLARiiON. Using these
hardware providers allows you to take hardware snapshots of the arrays.
When performing a hardware backup of a SharePoint Server 2007 farm, ensure that
the SQL and the SharePoint application data are placed on the CLARiiON or
Symmetrix LUNs, otherwise the backup will use a software snapshot.
Note: Mixing hardware and software providers causes backups to fail.
This section describes how to configure a proxy node or a proxy storage backup with
CLARiiON and Symmetrix hardware providers:
CLARiiON hardware provider on page 208
Symmetrix hardware provider on page 209
207
CLARiiON hardware provider

The minimum configurations for proxy node and proxy storage node for backups
with CLARiiON hardware provider are the same.
same CLARiiON box.
2. Ensure that the NMM client is installed on both the proxy node and the
production host.
3. Install the following software on both the proxy host and production host:
NaviAgent
Note: The version of the NaviAgent must match that of FLARE on the CLARiiON.
NaviCli
Note: When installing NaviCLi, you are prompted to provide the CLARiiON
credentials. Ensure that you provide the correct CLARiiON login details.
Admsnap
4. Perform the following steps on the production host and the proxy host:
a. Add both the IPs of CLARiiON, by running this command:
For example:
b. Add security privileges for the user for both the CLARiiON IPs by running the
following command:
-user <Username> -Scope 0 -address <CLARiiON IP>
-AddUserSecurity
For example:
-AddUserSecurity
-AddUserSecurity
Each time you will be prompted for a password. Ensure to use the CLARiiON
password.
208
5. For the production host and the proxy host:

For example:
b. Reboot the host.

a. Create a proxy client resource on the NetWorker server.
b. Create client resources for both the production host and the proxy host.
Note: Configuring a SharePoint client resource to back up a stand-alone farm on
page 205 provides the steps for configuring a client resource.
c. After creating client resources for both the production host and the proxy host,
add the following information on both the production host client resource and
proxy host client resource properties:
Access > SYSTEM@proxy host name.
d. Specify the following attributes in Application Information field of the
production host client resource to perform proxy backup:
NSR_SNAP_TYPE=vss
The EMC NetWorker Module for Microsoft Applications and EMC CLARiiON:
Symmetrix hardware provider

with the Symmetrix hardware provider are the same.
same Symmetrix box.
2. Ensure that the NMM client is installed on both the production host and data
mover host.
3. Install the following software on both the proxy host and production host:
4. Create a device and attach both STD and BCV to that device. After attaching both
STD and BCV, establish the connection between STD and BCV.
The EMC NetWorker Module for Microsoft Applications and EMC Symmetrix:
209

For all SharePoint recoveries, it is important that you perform the recovery process in
the following sequence:
1. C:\
2. SYSTEM COMPONENTS:
3. SharePoint writer (for SharePoint databases recovery)
Data loss will occur if this sequence is not followed.
You can perform the following types of recovery in SharePoint Server 2007:
Full recovery of a stand-alone SharePoint farm on page 210
Full recovery of a distributed SharePoint farm on page 210
Recovery of individual SharePoint Server content databases on page 212
Recovery of SharePoint Server 2010 search and content index on page 212
IMPORTANT
It is a Microsoft requirement that if a SharePoint configuration database is
recovered as part of an entire farm recovery, all the content databases in that farm
must also be recovered, for the SharePoint writer to ensure consistency.
However, a content database can be recovered separately, without the recovery
being a part of an entire farm recovery. Recovery of individual SharePoint Server
content databases on page 212 provides steps for recovering individual
SharePoint content databases.
Full recovery of a stand-alone SharePoint farm

In a stand-alone farm environment, recover C:\inetpub, SYSTEM COMPONENTS:\,
and all SharePoint databases, including SQL configuration database and all content
databases.
To perform a full recovery of SharePoint Server 2007 farm in a stand-alone farm:
1. Open the NMM client software.
2. In the navigation tree, expand the APPLICATIONS folder and select Microsoft
Office SharePoint Services.
3. From the System Recover Session toolbar, click Recover.
Recovery proceeds to completion. Details about the recovery are displayed in the
Monitor page.
Full recovery of a distributed SharePoint farm

In distributed farm environment, recover C:\inetpub and SYSTEM
COMPONENTS:\ on all the web front-ends in the farm.
To perform a full recovery of SharePoint Server 2007 in a distributed farm:
1. Open the NMM client software on the web front-end that was used to perform
the backups of the SharePoint Server 2007 writer.
210
2. In the navigation tree, expand the APPLICATIONS folder and select Microsoft
Office SharePoint Services.
A dependency dialog box appears, alerting you to go to the specified remote
hosts and start the recovery processes for the listed components.
Figure 53 on page 211 shows an example of several remote hosts that must be
recovered.
In this example, although 13 service components are displayed, they are located
on three remote hosts. You must go to each of these three hosts to recover all 13
services.
Figure 53
Dialog box to recover remote components
4. Go to each remote host:

a. Open the NMM client software.
b. In the navigation tree, locate and mark the items. Mark all dependent SQL
databases, SharePoint configuration databases, SharePoint content databases,
and SharePoint search databases.
c. Recover the items.
5. Return to the NMM GUI on the web front-end, and click Continue in the dialog
box.
Monitor page.
211
Recovery of individual SharePoint Server content databases

One or more content databases can be recovered after the configuration database has
been recovered. NMM 2.3 provides the ability to select individual SharePoint Server
content databases for recovery.
To perform a recovery of one or more individual SharePoint Server 2007 content
databases:
1. Open the NMM client software on the web front-end that was used to perform
the backups of the SharePoint Server 2007 writer.
2. In the navigation tree, expand the APPLICATIONS folder and select the
Microsoft Office SharePoint Services.
3. Expand the Microsoft Office SharePoint Services folder until you find a
database folder with an entry similar to the following example:
APPLICATIONS:\Microsoft Office SharePoint Services\Mars1\db_1
where:
Mars1 is the name of the server.
db_1 is the name of the database.
4. Select the databases to restore.
A dependency dialog box appears, alerting you to go to the specified remote
hosts and start the recovery processes for the listed SQL content databases.
6. Go to each remote host:
a. Open the NMM client software.
b. In the navigation tree, locate and mark the items.
c. Recover the items.
IMPORTANT
Recover the configuration database to complete the content database recovery.
7. Return to the NMM GUI on the web front-end, and click Continue in the
dependency dialog box.
Monitor window.
Recovery of SharePoint Server 2010 search and content index

Perform the following steps to recover search services:
1. Recover C:\inetpub and SYSTEM COMPONENTS:\.
2. Open the NMM client software on the web front-end where the SharePoint
services writer was registered at the time of backup, and start recovery of
SharePoint writer.
3. Browse the SharePoint save sets.
A dependency dialog box appears, alerting you to go to the specified hosts and
212
start the recovery processes for the listed components.

5. On the SQL Server, recover all the Sharepoint databases that are listed in
dependency dialog box, like all content databases, configuration databases,
search databases, and so on. System databases, like master and model databases,
can be excluded during the recovery.
6. After the recovery is complete, return to the NMM GUI in the web front-end, and
click Continue in the dialog box.
7. Recovery proceeds to completion. Details about the recovery are displayed in the
Monitor page.
8. Restart the machine, if prompted, to finish the recovery.
Recover the registry from bootable system state to perform full search
components recovery.
Performing SharePoint Server 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 databases, content databases, the query, and index servers.
In a disaster recovery, you need to restore the IIS, SQL Servers, and SharePoint
Servers that make up the farm, including file systems and registries of each machine.
Performing SharePoint Server 2007 disaster recovery with NetWorker 7.6 SP1
and earlier on page 213
Performing SharePoint Server 2007 disaster recovery with NetWorker 7.6 SP2 or
later on page 215
Performing SharePoint Server 2007 disaster recovery with NetWorker 7.6 SP1 and earlier
This following sections provide information on how to perform disaster recovery of
SharePoint Server 2007 by using NMM 2.3 on Windows 2008 SP2 and 2008 R2 with
NetWorker 7.6 SP1 and earlier:
SharePoint Server backup list on page 214
Performing a disaster recovery on page 214
213
SharePoint Server backup list

Table 33 on page 214 lists each server type in the SharePoint farm and the items that
must be backed up on that server, as part of your disaster recovery plan.
Table 33
SharePoint Server backup list for disaster recovery

Server type
Items to back up
Web front-end
SYSTEM COMPONENTS:\
All system volumes, for example, C:\, D:\
Web front-end without Microsoft Office Windows

SharePoint Services VSS Writer
SYSTEM COMPONENTS:\
Search server

SYSTEM COMPONENTS:\Microsoft Office Sharepoint
Search
SQL Server
SYSTEM COMPONENTS:\
All SQL databases, including the master database
Stand-alone SharePoint Server
SYSTEM COMPONENTS:\
All system databases, including the master database
Note: 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, first recover the remote host and then the primary
system.
Performing a disaster recovery

To perform a disaster recovery:
1. Back up different server types in the SharePoint farm using the information in
Table 33 on page 214.
2. For Windows 2008 with NetWorker 7.5 SP3 or later, or 7.6 SP1:
a. Prepare a setup similar to the one that is currently being used. Ensure that you
use the same:
OS
Service packs
IP address
Hostname
Domain
b. Install the same versions of SQL Server and SharePoint Server as currently
being used on the new setup.
214
c. Recover the following in the specified order:

a. C:\
b. SYSTEM COMPONENTS:\
c. SQL data
d. Perform a full recovery of the SharePoint writer.
IMPORTANT
Ensure to restart the system after performing a disaster recovery of SharePoint.
Currently, a message about the completion of disaster recovery and the need to
restart the system appears in the Monitor page and the logs. Check the Monitor
page and the logs before restarting the system.
Performing SharePoint Server 2007 disaster recovery with NetWorker 7.6 SP2 or later
To perform disaster recovery of SharePoint Server 2007 by using NMM 2.3 on
Windows 2008 and 2008 R2 with NetWorker 7.6 SP2 or later, use Windows Disaster
Recovery. Chapter 10, Windows Disaster Recovery with NetWorker 7.6 SP2 and
NMM provides details.
Keeping backups and recoveries in sync

Set up a consistent schedule of full farm-level backups. If backing up individual
content databases, schedule these in between the full farm-level backups. However,
whenever there are significant changes to the SharePoint farm, you should
immediately update the NetWorker backup configuration with any new SharePoint
objects, and perform a new full farm-level backup as soon as possible:
Configuration or database structure changes Any major changes made to the

SharePoint configuration or database structure require an update of the save set
lists and a full backup.
For example, if a full farm backup is performed on Monday, and then the user
adds a new content database on Tuesday, a full backup needs to be performed to
keep the backups up-to-date. For the full backup to be up-to-date, the NetWorker
backup configuration must be manually updated to include the new database
save sets.
Out-of-sync expiration policies between clients In a distributed farm, a

snapshot policy is specified at the group level, to apply uniformly to all
SharePoint clients in a group. The snapshot policy is then applied to each client
independently. As long as the farm is working properly in a steady state, the
snapshot expiration policy for the group and for each client stay in sync. But if
one of the clients fails, and you perform a manual rollover or a delete one of the
hosts, the rest of the hosts are 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, perform 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 206 provides details.
Keeping backups and recoveries in sync
215
Best practices
The following best practices can help you get the most out of disaster recoveries:
Check that all services of SharePoint are started, otherwise, backup fails with the
following error:
NMM... ERROR. Writer SharePoint Services Writer with local
dependent writer id {comp Content Index _ SPSearch cannot be found.
CONTINUE PROCESSING.
Start Windows SharePoint Search Services if SharePoint search is configured. This

service is not started automatically.
If the nsrsnap_vss_save -? command does not list the save set, register Windows
SharePoint Services by using the STSADM.exe. NMM backup will not run
unless Windows SharePoint Services is registered.
Ensure to apply SQL Server 2005 SP3, otherwise backup fails.
For proxy backup to work, ensure that the data mover machine has the same
configuration as the source machine.
For example, if farm setup is on Windows Server 2008, then the data mover host
should also have Windows Server 2008.
Group inactivity timeout must be set to zero, especially for farm-based backups
that use a proxy host.
For farm hosts that use the same proxy server, the import, deport, and delete
operations that occur on the proxy are serialized. This introduces additional delay
into the overall group. The actual delay depends on the number of LUNs for each
NMM client that are imported on the proxy. Setting the inactivity timeout to zero
insures that the Group is not canceled during the period when NMM clients are
waiting for their turn to perform proxy operations.
216
Perform a full backup of SharePoint after every successful recovery. Also, a full
backup should be performed after the SharePoint farm has been changed in any
way.
Ensure that all SharePoint databases are mounted before backing up the
application server. Unmounted databases are not backed up.
For copy-on-write versus mirroring, do not save a large or fast-changing database

with copy-on-write snapshot technology. Fast changing data contains more
writes. Instead use split mirror snapshot technology like CLARiiON clones or
Symmetrix business continuance volumes.
Sometimes after recovery of the SharePoint Config database, the Central Admin
local cache is not in sync with the SharePoint Config database. If this occurs, clear
the file system cache on all servers in the server farm on which the Windows
SharePoint Services Timer service is running. The Knowledgebase article
KB939308 on the Microsoft Support website provides steps for clearing the cache.
Backing up SharePoint database by using NMM and NMSQL

The advantages of backing up data using NMM and NMSQL include the use of full,
differential, and incremental backups for SharePoint content databases and directed
recoveries to alternate locations for use with third-party data mining applications.
This procedure also allows direct SAN backups for SharePoint content databases
using NetWorker dedicated storage node capabilities with NMSQL.
For example, you could be using:
One SharePoint Configuration database server, protected by NMM.
One SharePoint Search database or index server, protected by NMM.
One SharePoint or SQL content database cluster, protected by NMSQL and

configured with dedicated storage node, SAN backups, and full or differential
backups. The dedicated storage node can be created by installing NetWorker
storage node and NMSQL on the host.
Use the following procedure for backup:

1. Configure SharePoint web front-end and SharePoint Central Administration in
NMM for backup. Use the command nsrsnap_vss_save -? and provide the save
set from the command for the configuration.
2. Configure a separate group for SQL database backup through NMSQL. Backup is
successful for both groups.
Use the following procedure for recovery:
1. Ensure to stop all SharePoint services because recovery will fail when database is
in use.
2. Start recovery of SharePoint database from the web front-end.
The dependency dialog box to recover SQL databases appears.
3. Recover SharePoint database from SharePoint Central Administration Server.
The dependency dialog box to recover SQL databases appears. You must first
recover SQL.
4. Recover SQL through NMSQL.
5. Recover all SQL databases protected by SharePoint.
6. Now continue to recover NMM SharePoint data on both web front-end and
Central Administration.
Backing up SharePoint database by using NMM and NMSQL
217
218
9
Server 2010 Backup
and Recovery
Overview ......................................................................................................................
Performing SharePoint Server 2010 disaster recovery...........................................
220
222
225
227
219
Overview
(NMM).
The backup and recovery workflows for Microsoft SharePoint Server 2010 are similar
to the backup and recovery workflows for Microsoft SharePoint Server 2007. Review
Chapter 8, Microsoft SharePoint Server 2007 Backup and Recovery, for additional
information.
The disaster recovery procedures for SharePoint Server 2007 and SharePoint Server
2010 are the same.
New features in Microsoft SharePoint Server 2010 on page 220
SharePoint Server 2010 support on Windows Server 2008 on page 221
Types of SharePoint Server 2010 backup and recovery on page 221
NMM and Microsoft Office SharePoint Server 2010 farm configurations on

page 221
SharePoint Server 2010 VSS writers on page 222
New features in Microsoft SharePoint Server 2010

The following new SharePoint Server 2010 features are used for SharePoint data
protection in NMM 2.3:
Services in SharePoint Server 2010 In SharePoint Server 2010, the number of

services and corresponding databases is comparatively more than in previous
releases of SharePoint. In SharePoint Server 2010, services are no longer
contained within a Shared Services Provider (SSP). Instead, the infrastructure for
hosting services moves into SharePoint Foundation 2010 and the configuration of
service offerings is much more flexible. Individual services can be configured
independently and third-party companies can add services to the platform.
The services are selectable and can be deployed individually in a farm:
Web applications can be configured to use only the services that are needed,
rather than the entire set of services that are deployed.
Multiple instances of a service can be deployed in a farm and be assigned
unique names to the resulting service applications.
Services can be shared across multiple web applications within the same farm
and across different SharePoint farms.
Service applications Service applications are services that are shared across
web applications within a farm, for example, Search and Excel Calculation
Services.
Some service applications can be shared across multiple farms. For example:
The Search Service application includes multiple application components and
multiple databases.
The People Service application includes multiple databases.
The Microsoft documentation and the Microsoft Support website provide details
about SharePoint Server 2010.
220
SharePoint Server 2010 support on Windows Server 2008

NMM 2.3 provides supports for SharePoint Server 2010 on:
Windows Server 2008 R2:

Standard Edition (x64)
Windows Server 2008 SP2:

Standard Edition (x64)
Note: SharePoint Server 2010 is not supported on 2008 SP2 (x86).
Types of SharePoint Server 2010 backup and recovery

For SharePoint Server 2010, NMM provides the following backup and recovery
support:
Backup of:
Stand-alone farm
Distributed farm
Performing SharePoint Server 2010 backups on page 222 provides details.
Recovery of:
Farm Performing SharePoint Server 2010 full farm recovery on page 225
provides details.
Full web applicationPerforming SharePoint Server 2010 web application
recovery on page 226 provides details.
Individual content database Performing SharePoint Server 2010
individual content database recovery on page 226 provides details.
Search service applicationPerforming SharePoint Server 2010 search
services recovery on page 227 provides details.
IMPORTANT
NMM 2.3 does not support SharePoint Server 2010 granular backup and recovery.
NMM and Microsoft Office SharePoint Server 2010 farm configurations

The topological configurations for SharePoint Server 2010 farms and SharePoint
Server 2007 farms are similar. Microsoft Office SharePoint 2007 farm configurations
on page 195 provides details.
Overview
221
SharePoint Server 2010 VSS writers

Table 34 on page 222 lists the writers supported by SharePoint Server 2010 VSS:
Table 34
List of supported SharePoint Server 2010 VSS writers

SharePoint Server VSS writer
Description
SPSearch4 VSS Writer
The writer for SharePoint Server 2010 help search
OSearch14 VSS Writer
The writer for Microsoft Office server search
SharePoint Services Writer
The writer for SharePoint Server 2010, which runs on the web
front-end

Specifying SharePoint Server 2010 application data save sets on page 222
Displaying valid SharePoint Server 2010 data save sets on page 223
Performing SharePoint Server 2010 backup on page 224
Specifying SharePoint Server 2010 application data save sets

The application data save sets for SharePoint Server 2007 are applicable for
SharePoint Server 2010 without any change in the syntaxes.
Only the usage type for the SharePoint Server 2010 writers, OSearch14 and SPSearch4
VSS writers, has changed from system data to user data. The save set syntax starts
with APPLICATIONS: \ rather than SYSTEM COMPONENTS:\.
222
Specify the SharePoint Server 2010 data save sets in the Save Set attribute of a client
resource. Table 35 on page 223 lists the SharePoint Server 2010 save set syntax that
specifies the supported types of SharePoint Server 2010 data.
Table 35
SharePoint Server 2010 save set syntax
Type of backup data
Save set syntax
SharePoint databases on SQL Server
APPLICATIONS:\SqlServerWriter\<SQL_server_host_name>
One SharePoint database on SQL Server
APPLICATIONS: \SqlServerWriter\<SQL_database>\<Database_Name>
Full SharePoint backup
SharePoint web front-end

APPLICATIONS:\Microsoft Office SharePoint Services\<WFE_NAME>
Services\<WFE_NAME>\<Component Name>
Search Applications
APPLICATIONS:\Microsoft Office Search

APPLICATIONS:\Microsoft Office SharePoint Search
IMPORTANT
Do not specify SQL save sets separately.
When the APPLICATIONS:\Microsoft Office SharePoint Services save set is used,
all the local dependent SQL save sets, like SYSTEM COMPONENTS:\<SQL
embedded server>\<instance>\<database> and
APPLICATIONS:\SqlServerWriter\<instance>\<database> are
automatically included.
Displaying valid SharePoint Server 2010 data save sets

To display a list of the SharePoint Server 2010 save sets that are available for backup:
names:
To list the save sets for SharePoint Server 2010:
nsrsnap_vss_save -?
For complete details about the save sets:

nsrsnap_vss_save -v -?
3. Press Enter:
line.
223
The save sets that are available for backup are listed in a format similar to the
following:
Performing SharePoint Server 2010 backup

Ensure that the following requirements are taken care of before performing
SharePoint Server 2010 backups:
The NetWorker client and NMM are installed on all the web front-ends,
application servers, and SQL database servers.
The SharePoint services writer is registered, so that the save sets can be browsed
and backed up successfully.
Note: When registering the SharePoint Server 2010 writer with the stsadm.exe -o
registerwsswriter command, ensure that this command is executed on all the web
front-end servers on the farm to backup the entire SharePoint Server 2010 farm.
To register the SharePoint services writer for distributed configurations:

a. The SharePoint VSS writer must be registered on each web front-end server.
b. Use the command line STSADM.exe utility. Go to the following location for
the STSADM.exe:
C:\Program Files\Common files \Microsoft Shared \Web server
extension\14\BIN
c. Type the following command to register the SharePoint writer:

run STSADM -o registerwsswriter
When registering the SharePoint Server 2010 writers by using the stsadm.exe
-o registerwsswriter command:
Ensure that this command is run on each and every web front-end server
in a SharePoint Server 2010 farm.
This requirement is unlike the SharePoint Server 2007 backup workflow,
where it is not necessary to run this command on all the web front-end
servers but only on one web front-end server that is running the services.
To view the search service application component name in NMM GUI, you must
ensure that the SharePoint_Shell_Acces database role membership is enabled on
SharePoint configuration database (SharePoint_Config).
Configuring client resources

To configure the client resources and perform backup:
1. Create client resources with required parameters for all the hosts in the
SharePoint Server 2010 farm by using the NetWorker Management Console. The
procedure to create client resources for SharePoint Server 2010 is similar to that
used for SharePoint Server 2007. Configure a SharePoint Server 2007 client
resource on page 204 provides details.
224
2. In the Save Set attribute, specify the save sets listed for SharePoint Server 2010.
Specifying SharePoint Server 2010 application data save sets on page 222
provides the save sets for SharePoint Server 2010.
3. Ensure that the following are backed up so that web application, service
applications, and farm settings can be later recovered:
C:\inetpub
SYSTEM COMPONENTS:\

This section provides information on:
Performing SharePoint Server 2010 full farm recovery on page 225
Performing SharePoint Server 2010 web application recovery on page 226
Performing SharePoint Server 2010 individual content database recovery on

page 226
Performing SharePoint Server 2010 search services recovery on page 227
Performing SharePoint Server 2010 full farm recovery

You can recover a farm that was completely deleted but for this you must first
recover C:\inetpub and SYSTEM COMPONENTS:\, followed by SharePoint Server
writer recovery.
To perform SharePoint Server 2010 full farm recovery:
services writer was registered at the time of backup, and start recovery of the
SharePoint writer.
3. Browse the SharePoint Server save sets.
4. Click Recover.
Note: On the SQL Server, recover all the SharePoint databases that are listed in
dependency dialog box, like all content databases, configuration databases, search
databases, and so on. System databases, like master and model databases, can be excluded
during the recovery.
5. After the recovery is complete, return to the NMM GUI in the web front-end, and
Note: The configuration database must be first selected and recovered, before recovering
web applications and service applications.
Monitor page.
225
Performing SharePoint Server 2010 web application recovery

Perform the following steps for full recovery of a web application:
1. Recover C:\inetpub, IIS configuration writer, and IIS metabase writer, if the IIS
settings were removed or deleted along with web application on all nodes of
SharePoint farm.
Note: This step is not required when the SharePoint databases are hosted on the SQL
Server.
services writer was registered at the time of backup, and start recovery of the
SharePoint writer.
4. Click Recover.
A dependency dialog box appears, alerting you to go to the specified remote SQL
Server host and start the recovery processes for the listed components.
5. Recover the following:
a. Content databases on SQL Server host, which is hosting the web application.
b. All the databases connected to this web application.
c. Configuration database on the SQL Server host.
Recovery proceeds to completion. Details about the recovery is displayed in the
Monitor page.
Performing SharePoint Server 2010 individual content database recovery

Perform the following steps to recover documents or items that were corrupted:
SharePoint writer.
3. Click Recover.
A dependency dialog box appears, alerting you to go to the specified remote SQL
Server host and start the recovery processes for the listed components.
4. Recover the content databases on SQL Server host.
226
Performing SharePoint Server 2010 search services recovery

Perform the following steps to recover search services:
SharePoint writer.
4. Click Recover.
5. On the SQL Server, recover all the SharePoint databases that are listed in
dependency dialog box, like content databases, configuration databases, search
databases, and so on. System databases, like master and model databases, can be
excluded during the recovery.
6. After the recovery is complete, return to the NMM GUI on the web front-end, and
Recovery proceeds to completion. Details about the recovery is displayed in the
Monitor page.
8. Recover the registry from bootable system state to perform full search
components recovery.

For SharePoint Server 2010 disaster recovery on Windows Server 2008 SP2 and
Windows Server 2008 R2 with NetWorker 7.6 SP2 or later, use Windows Disaster
Recovery. Chapter 10, Windows Disaster Recovery with NetWorker 7.6 SP2 and
NMM provides details.
Performing SharePoint Server 2007 disaster recovery on page 213 provides the
information needed to perform disaster recovery for SharePoint Server 2010 with
NetWorker 7.6 SP1 or earlier. Use the SharePoint Server 2010 save set syntax
provided in Table 35 on page 223.
227
228
10
Windows Disaster
Recovery with
NetWorker 7.6 SP2 and
NMM
Overview ...................................................................................................................... 230

Changes in NetWorker 7.6 SP2 client functionality after NMM 2.3 installation 231
Changes in NetWorker 7.6 SP2 client functionality after NMM 2.3 uninstallation..
232
applications .................................................................................................................. 232
229
Overview
IMPORTANT
It is recommended that you review the EMC NetWorker Release 7.6 Service Pack 2
Administration Guide for details about NetWorker 7.6 SP 2 Windows Disaster
Recovery support before proceeding with the procedures in this chapter.
Successful recovery of system state, to the same or a similar hardware, can only be
achieved through offline disaster recovery on Windows Server 2008 and Windows
Server 2008 R2. Disaster recovery backup must be performed after changes are made
in the system component data, like adding, changing, or removing roles and features,
or installing Windows updates. Online recovery of SYSTEM COMPONENTS save set
is generally not supported on Windows Server 2008 and Windows Server 2008 R2,
and improper online recovery of the SYSTEM COMPONENTS save set leads to
inconsistent state of the system. The save set can only be recovered to the same
Windows operating instance.
Install EMC NetWorker 7.6 SP2 client before installing EMC NetWorker Module for
Microsoft Applications (NMM) 2.3 to leverage the Windows Disaster Recovery
capability provided by the NetWorker 7.6 SP2 client.
NMM 2.3 is compatible with the NetWorker 7.6 SP2 client, which provides a true
Windows Bare Metal Recovery (BMR) capability for Windows Server 2008 R2 and
Windows Server 2008. This capability is built-into the NetWorker client and provides
BMR support to the same or similar hardware. For Windows Disaster Recovery (DR),
a Windows DR ISO image is supplied with NetWorker 7.6 SP2, which provides a
wizard driven BMR recovery for Windows. The NetWorker 7.6 SP2 Windows DR
wizard automatically formats disks, recovers Windows critical volumes from
backup, and reboots to bring server back online.
The NetWorker 7.6 SP2 Windows DR functionality is available on the following
platforms for NMM 2.3:
Windows 2008 and Windows 2008 SP2 (x86 and x64)
Windows 2008 R2 and Windows 2008 R2 SP1 (x64)
You can use the Windows DR feature for the following Microsoft applications:
230
Exchange 2007
Exchange 2010
SharePoint 2007
SharePoint 2010
SQL 2005 SP4
SQL 2008 SP2
SQL 2008 R2 (Cumulative Update 4)
IMPORTANT
For all the Microsoft applications, after performing Windows DR recovery and
rebooting the system, check all the disk and volume configurations. In most cases,
the disks and volumes appear as on the original system.
However it is possible, especially in BMR scenarios where the volume or disk
signatures do not match the original ones, that the noncritical volumes or disks are
offline and not mounted. Use the Microsoft Disk Manager to bring the volumes
and disks online, and then reboot the system for drive letter reassignments. If
there are any issues with the drive letter reassignments, then assign drive letters to
the noncritical volumes and disks, as needed. Noncritical volumes that are
accessed by mount points may have a similar issue.
Changes in NetWorker 7.6 SP2 client functionality after NMM 2.3 installation
Installing NMM 2.3 on NetWorker 7.6 SP2 affects the functioning of the NetWorker
7.6 SP2 client. Table 36 on page 231 lists the differences.
Table 36
Details
Before NMM 2.3 is installed
After NMM 2.3 is installed
Save sets handled
The NetWorker 7.6 SP2 client handles the system file

backups, such as save sets All, DISASTER_RECOVERY,
VSS SYSTEM, and so on.
The NetWorker 7.6 SP2 client is limited to handling only

the DISASTER_RECOVERY:\ save set.
Save sets handledSave sets

displayed in GUI
The NetWorker client GUI is used for any ad-hoc backups,

and shows all the volumes on the system and save sets.
Similarly for recovery, the NetWorker client GUI shows all
the save sets that were backed up on the server.
The NMM 2.3 GUI displays all the backups that were
previously saved by the NetWorker 7.6 SP2 client,
including the DISASTER_RECOVERY:\ save set.
However, these backups cannot be recovered from the
NMM 2.3 GUI.
DISASTER_RECOVERY:\
save set
When the save set All is specified in the NetWorker client

and a full backup is performed, a
DISASTER_RECOVERY:\ backup is automatically
performed.
It is not possible to recover the DISASTER_RECOVERY:\

save set backed up by the NetWorker 7.6 SP2 client by
using NMM 2.3. This backup of the
DISASTER_RECOVERY:\ save set can only be restored
offline by using the NW 7.6 SP2 recovery CD.
IMPORTANT
After NMM 2.3 is installed, running a save set other than
DISASTER_RECOVERY:\ on a NetWorker 7.6 SP2 client, gives error.
231

uninstallation
When NMM 2.3 is uninstalled, the functionality of the NetWorker 7.6 SP2 client is
reverted to what it was before the NMM 2.3 installation:
The NetWorker client now handles file system backups.
The NetWorker client GUI backup window once again shows the available save
sets, including all the volumes and DISASTER_RECOVERY save set for backup.
The NetWorker client GUI recovery window shows all the save sets that were
backed up, including the file system backup that are performed by NMM client.
IMPORTANT
After uninstalling NMM, perform a full backup from NetWorker Management
Console using the save set All.

applications
Table 37 on page 232 lists the supported and unsupported system recovery scenarios.
The Knowledgebase article KB249694 on the Microsoft Support website provides
more details.
Table 37
Supported and unsupported system recovery scenarios

Scenario
Supported
System State Recovery to the same instance of Windows Server 2008
System State Recovery after Windows DR restore to the same hardware
System State Recovery after Windows DR restore to different hardware
System State Recovery after a new installation of Windows Server 2008 on new
hardware or same hardware
Note: Windows DR backs up only critical volumes and can be used for offline disaster
recovery. You must use NMM to backup the file system, which backs up both critical volumes
and noncritical volumes on the system. The noncritical volumes data that is not backed up with
NMM 2.3 is lost.
Performing a Windows DR backup

To perform Windows DR backup:
1. Use NMM to back up the non-application files.
The non-application files that were saved by the DISASTER_RECOVERY:\ save
set on the NetWorker client cannot be recovered by NMM. Use NMM to back up
the non-application files by using the All save set and snapshot policy
1\0\day\all. This backs up the local file system and SYSTEM COMPONENTS.
Guide provides details.
232
2. Use the NMM client to perform a full backup of the SQL Server 2008 R2,
SharePoint Server 2007, SharePoint Server 2010, Exchange Server 2007, and
Exchange Server 2010 application data.
The following chapters provide details:
Chapter 1, Microsoft SQL Server Backup and Recovery
Chapter 5, Microsoft Exchange Server Backup and Recovery
Chapter 6, Microsoft Exchange Server 2010 Backup and Recovery
Chapter 8, Microsoft SharePoint Server 2007 Backup and Recovery
3. Configure the NetWorker client resource to perform a Windows DR backup:
a. Use the DISASTER_RECOVERY:\ save set.
b. Run the NetWorker client save.exe command.
Performing a Windows DR recovery

To perform Windows DR recovery:
1. Use the WinPE wizard to perform a Windows DR recovery:
a. To start the NetWorker Recovery image, you can do either of the following:
Boot the CD containing the Windows Disaster Recovery image (.iso file).
Boot the image from a Network location, for which you will need
Windows Deployment Service (WDS), DNS service, and DHCP service.
The Welcome to NetWorker System Recovery wizard appears.
b. In the Select Network Interface window, select the NIC that will be used to
connect to the NetWorker server, and click Next.
If no NICs are displayed, load the 32-bit drivers needed for the installed NICs.
c. Configure the NetWorker client. Provided the following information and click
Next:
The Host name, which is the source hostname.
The DNS domain, as configured in the source host.
The IP address, as configured in the source host.
The Subnet mask, as configured in the source host.
The Default gateway, as configured in the source host.
The DNS Server IP address, as configured in the source host.
The Available Disks window displays the disks drives on the source host.
These may not all be critical drives. If all the drives are not shown then load
the 32-bit drivers needed by the missing drive or drives.
Click Next.
d. For the NetWorker server, type the IP address, and then click Next.
The Server Configuration Error window with the message Error trying to
validate NetWorker server credentials: appears. Click OK and then Exit.
Performing Windows Disaster Recovery backup and recovery for Microsoft applications
233
e. Open the hosts file and type the notepad

X:\Windows\System32\drivers\etc\hosts command at the command
prompt. Specify the NetWorker server, NetWorker client, Avamar
deduplication node IP (if included), and hostname details in the hosts file.
Save and exit the file.
f. After saving the hosts file, restart the WinPE wizard from the directory
X:\Program Files\Legato\nsr\wizard by using the following command:
X:\Program Files\Legato\nsr\wizard>javaw -jar
WinPEWizard.jar
g. The WinPE wizard displays all the DISASTER_RECOVERY save sets on the
server for this host. Select the desired backup to recover.
h. The WinPE wizard displays the critical volumes and provides you the option
of formatting the disk.
a. Select the Perform a quick format of disks option to format the disks. If
you select this option, all existing data will be lost.
b. Click Next.
The System Recovery Summary window appears. This window displays all
the details for the recovery.
i. Check all the details in the System Recovery Summary window and click
Next.
j. The Windows DR recovery starts.
The System Recovery Status window shows the progress of the recovery.
Wait for the recovery to complete. If you cancel the critical volumes recovery
before it is complete, the disks will be in an undefined state, and you will need
to restart the recovery process.
k. After the Windows DR recovery process is complete, the System Recovery
Results windows displays the details of the successful recovery. You can
reboot the system and recover the application data, as needed.
2. Use the NMM client to perform a recovery of the non-application files.
3. Use the NMM client to recovery SQL Server 2008 R2, SharePoint Server 2007,
SharePoint Server 2010, Exchange Server 2007, and Exchange Server 2010
application data.
The following chapters provide details:
Chapter 1, Microsoft SQL Server Backup and Recovery
Chapter 5, Microsoft Exchange Server Backup and Recovery
Chapter 6, Microsoft Exchange Server 2010 Backup and Recovery
The internal SQL databases, such as master, msdb and models, are not recovered
by the Windows DR recovery.
234
11
Invisible Body Tag
Troubleshooting
About the troubleshooting process...........................................................................

NMM Config Checker 1.1.0 .......................................................................................
NMM client error messages.......................................................................................
NMM client issues.......................................................................................................
NMM installation issues ............................................................................................
Checking log files ........................................................................................................
Manually stopping and starting services.................................................................
Using nsr.dir to skip files for NMM backup and recovery ...................................
Troubleshooting issues during SQL databases directed recovery .......................
Name resolution ..........................................................................................................
Other troubleshooting resources...............................................................................
Troubleshooting
236
237
238
242
256
259
261
262
262
262
263
235
Troubleshooting
About the troubleshooting process

NetWorker and the NMM provide many resources to help discover and isolate
problems. Setting up these resources before problems occur can help if and when
troubleshooting problems occur later.
If the problem is not with the NMM client, there are other NetWorker resources and
documentation that may provide a solution.
The flowchart shown in Figure 54 on page 236 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
Fixed?
Check NMM
Client issues
section
Yes
Finish
No
Try a
different
solution?
No
Contact
Technical
Support
Yes
GEN-000753
Figure 54
236
Troubleshooting process
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 email messages.
The EMC NetWorker Release 7.6 SP2 Administration Guide 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 38 on page 237 describes several ways that NetWorker server, NMM
client, and other NetWorker features provide information about problems.
Table 38
Notifications and errors

Type
Description
Email notification of a
NetWorker event
NetWorker client can be set up to send an e-mail notification about NetWorker

events.
Error message pages
Appear on the NetWorker server when an error occurs during backup or recovery
operations.
NetWorker Monitor page
Displays details of current NetWorker server activities, operations related to

devices and libraries, and events that require user intervention.
Event viewer
Alerts users that user intervention is required on the NetWorker server.
Log files
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:
NMM
NetWorker client or storage node
NetWorker server
NetWorker PowerSnap
Replication Manager
EMC VSS Provider
The logging level of the log file is controlled by the debug level of the process.
NMM Config Checker 1.1.0

The NMM Config Checker version 1.1.0 checks and captures configuration errors that
may lead to failure in NMM 2.3 installation, data backup, or data recovery for:
Application host (operating system environment)

Note: Checks for Microsoft Hyper-V are included in the application host checks.
Microsoft Exchange
Microsoft SQL
EMC CLARiiON
EMC Symmetrix
NMM Config Checker 1.1.0
237
Troubleshooting
After running the Config Checker, save the results in the HTML result file. Review
the HTML result file and take appropriate actions to rectify all the checks that have
failed. Rerun the Config Checker to ensure that all the checks are now successful.
Although the checks run by the Config Checker are extensive, there may be checks
that are not performed. Also, successful execution of all the checks does not mean
that backup and recovery are guaranteed to succeed.
After rectifying all the checks that have failed, if you are still facing issues with your
setup configuration, backup, or recovery, contact EMC Technical Support. It is
recommended that you share the Config Checker HTML results file with EMC
Technical Support for better and faster resolution of setup issues.
The NetWorker Module for Microsoft Applications Config Checker Version 1.1.0
Supplemental Notes provides details.
NMM client error messages

Error messages help identify the product that is having a problem.
The following sections describe error messages that are specific to the NMM client:
E_VOLUME_NOT_SUPPORTED on page 238
E_VETO_PROVIDER on page 238
VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 on page 239
VSS CLIENT... Invalid Writer Selection... for APPLICATIONS on page 239
Savegroup failed in scheduled backup on page 240
Insufficient permission to access mailbox. See documentation for required

permission settings. Server MBX is not capable of RSG operations on page 240
77108:nsrsnap_vss_save on page 241
NMM validation for NPS writer failed, unable to restore NPS VSS writer data
on page 241
E_VOLUME_NOT_SUPPORTED
This error occurs when EMC CLARiiON or EMC Symmetrix is down, an array is
unmanaged, or the CLARiiON or Symmetrix disk is not visible. This error also occurs
when the data mover is used to take a local volume replica. The error message
appears in NMM client and Replication Manager logs.
Solution
Check in the CLARiiON or Symmetrix array for storage allocation.
E_VETO_PROVIDER
There are several possible causes for this error:
238
Storage resources, such as Symmetrix BCVs or CLARiiON clones have been

added, but the Replication Manager service was not recycled to rebuild the
storage resource cache. The provider finds the LUN as hosted by the storage
array, but fails to find storage resources in the storage resource cache.
There is a load on the CLARiiON array, and replica creation fails.
Troubleshooting
A CLARiiON snapshot is performed when there are not enough LUNs in the
reserved LUN pool.
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
1. Stop the following services:

EMC VSS Provider
Microsoft VSS services
Replication Manager
2. Restart these services:
EMC VSS provider
Microsoft VSS services
Replication Manager
3. Restart Exchange Information store if it was running and was backed up.
VSS CLIENT... Invalid Writer Selection... for APPLICATIONS

This error might occur if Microsoft Exchange services are not up or if SQL databases
are offline.
Another cause of this error is if there is a typographical error in writing
APPLICATIONS:\Microsoft Exchange Writer.
Solution
Perform either of the following:
For Microsoft Exchange applications, start the Exchange services. If Exchange

services were already up, dismount and mount the databases and then start the
savegroup.
239
Troubleshooting
For SQL Server applications, bring the databases online.
Retype the words correctly or use the nsrsnap_vss_save -? command, as

described in EMC NetWorker Module for Microsoft Application Release 2.3
Administration Guide, to display a listing of all valid application save sets on the
NMM client.
Savegroup failed in scheduled backup

A notification appears in the Monitor page that a savegroup failed.
Solution
Check the savegroup details for the failed save set. This may provide an exact cause,
or a general error, which should indicate whether it is a client-side or server-side
issue. The EMC NetWorker Release 7.6 SP2 Administration Guide provides information
about viewing group backup details.
If there is not enough information in the savegroup details:
1. Check the NMM client log.
2. Check the other client-side logs.
Checking log files on page 259 provides more information about the log names,
locations, and details.
Insufficient permission to access mailbox. See documentation for required permission settings.
Server MBX is not capable of RSG operations
This error message appears if RSG browsing permissions are not provided when
recovering a storage group to a RSG that was already created.
Solution
Before starting the RSG recovery:

1. Install MAPI Collaboration Data Objects 1.2.1. Microsoft Exchange Server 2007
MAPI client and Collaboration Data Objects support on page 101 provides
details.
2. Provide RSG browsing permissions. This step ensures that the error message does
not appear, and the recovery is performed smoothly.
For example,
get-ExchangeServer <Exchange Server name> | Add-AdPermission
-user <username> -extendedrights Receive-As, Send-As
3. Set registry to disable IPV6.
To fix RSG browsing issue in the registry:
a. Open the registry.
b. Go to:
HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters
240
Troubleshooting
c. Edit or create the 32-bit DWORD value DisabledComponents, and enter the
value FFFFFFFF.
The public folder must be present on the Exchange Server for RSG browsing to
work.
In the CCR or SCC cluster, we should perform all above steps on both nodes of
cluster.
77108:nsrsnap_vss_save
When performing a passive node backup with only a single passive node client
configured for Exchange deduplication backups in a CCR setup, the following error
message appears:
77108:nsrsnap_vss_save:NMM .. Operation unit failed with error
'Traditional save returned error. saverc :-Possible cause:
1)Unsupported file system or 2)write-protected disc or 3)No
space on disc
NMM .. Error backing up one or more of the file system
savesets: NMM .. Operation unit failed with error Traditional
save returned error. saverc :-1.
Solution
Whenever performing a passive node backup for Exchange deduplication backups in

a CCR setup, perform the following steps:
1. Configure a virtual client in same save group where the passive node is
configured.
2. Ensure not to schedule this virtual client for backup in same group.
3. Ensure to enable deduplication settings for this virtual client.
Note: Although the client exists in the same save group, it will not be part of backup.
4. Ensure that a backup device is configured properly for the client.
NMM validation for NPS writer failed, unable to restore NPS VSS writer data
If Network Policy and Access Services (NPS) role is installed, but not configured
properly, the file C:\windows\system32\ias\ias.xml that is in the NPS Writer file
list, is not created. NPS Writer recovery fails, if not configured properly on Windows
Server 2008 and Windows Server 2008 R2 platforms, with the following error
message:
NMM validating for NPS Writer failed, unable to restore NPS VSS
Writer data
Solution
You must configure NPS role data correctly.
241
Troubleshooting
NMM client issues

Check this section first when there is a problem or if no specific error message in
monitoring or event logs appears:
242
In-progress backup fails on page 243
NetWorker is blocked by Windows firewall on page 243
NMM backups might fail where a firewall exists between the NetWorker server
and client on page 243
Running utility to obtain Exchange Server information on page 244
Requesting a snapshot for a volume on hardware that is not transportable on

page 245
The PowerSnap service must be restarted after the NetWorker service

is restarted on page 245
PowerSnap validation for recovery fails on page 246
Snapshot backup may fail with writer errors on page 246
Microsoft I/O write error when taking a replica in a CLARiiON array on

page 246
Creating a replica takes a long time in CLARiiON environment on page 247
Cannot recover Exchange database due to overwrite prevention error on

page 247
Incremental backups may be promoted to full backups on page 247
Diagnosing VSS writer issues on page 248
Modifying the Exchange 2007 or 2010 COM+ components user account or

password on page 249
Save sets may not appear in the Recover page on page 249
Recovery of AES-encrypted files fails without pass phrase on page 249
Unable to restore files encrypted with both Microsoft Windows Encrypting File
System and AES encryption on page 250
Antivirus programs block recovery on page 250
Snapshot cannot include both hardware and software snapshot volumes for
clustered NMM VSS clients on page 250
Cross-platform directed recovery is not supported on NMM on page 251
Recovery of large number of items fails if one or more items in a folder is not
selected on page 251
Multiple client resources with the same name cannot be combined in the same
group on page 251
Backup of two partitions of the same CLARiiON disk fails on page 252
Connection to DPM service lost during DPM recovery on page 252
DPM replica backup is not correctly configured on page 252
Backup fails if Exchange Server in is renamed after it is created on page 253
In Exchange Server 2010, although backup completed successfully for renamed

database, recovery fails on page 253
Troubleshooting
In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of

new database name after renamed mailbox database on page 253
Save sets from an Avamar AFTD for NMM backups show retention set to
1/18/2038 on page 254
Microsoft updates required to fix the vds.exe crash errors during retention on
Windows Server 2008 and Windows Server 2003 on page 254
Back up of SYSTEM COMPONENTS fails due to missing System Writer on

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

Microsoft article provides details: http://support.microsoft.com/kb/324270.
Your operating system documentation provides information on how to set the
TCP keepalive parameter.
2. After the backup failure is resolved, you can increase the KeepAliveTime value if
required based upon your backup environment.
Running utility to obtain Exchange Server information

The nwexinfo.exe utility runs when the 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.
Solution
Rerun the utility, if any of the following conditions occurs:
244
Exchange Server is installed after NMM client is installed.
The Exchange username, password, or domain values change after the NMM
client is installed.
Troubleshooting
To run the utility:

1. Navigate to the following folder: <NetWorker_install_path>\nsr\bin
2. Run nwexinfo.exe.
3. For Exchange 2003, change the Exchange password, username, and domain as
required.
Requesting a snapshot for a volume on hardware that is not transportable

When volumes are added to the NMM client snapshot set, an error might appear if a
transportable hardware snapshot is requested and the volume that is being replicated
is not a volume that resides on special hardware that is transportable.
The following error message might also appear:
VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER.
Solution
The Exchange Server and proxy server (if one is set up for Exchange) must have
matching volumes or alternate mount path in PowerSnap attribute.
An Exchange backup that is mounted on a proxy server needs either matching

volumes or an alternate location to mount Exchange databases and logs:
An example of matching volumes would be D: to D: and E: to E:.
An example of alternate location would be "G:\altpath" on the proxy server.
In this example:
The snapshot of "D:\" would be mounted on the proxy server as "G:\altpath\D\"
The snapshot of "E:\" would be mounted on the proxy server as "G:\altpath\E\."
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."
Chapter 5, Microsoft Exchange Server Backup and Recovery, provides more
information about creating a client resource.
The PowerSnap service must be restarted after the NetWorker service is restarted
After restarting the NetWorker service, if the PowerSnap service is not restarted, the
first retention or rollover will fail.
The following message appears:
RPC send operation failed. A network connection could not be
established with the host.
The PowerSnap service re-establishes the connection on the next operation, so this
failure only occurs once.
NMM client issues
245
Troubleshooting
Solution
To fix this problem:

1. Restart the NetWorker service.
2. Restart the PowerSnap service
3. Run a PowerSnap operation.
PowerSnap validation for recovery fails

When the NetWorker PowerSnap 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 NetWorker PowerSnap 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 while running a backup for a LUN residing on CLARiiON.
Solution
To fix this problem:

1. Stop the following services:
EMC VSS provider
Volume Shadow Copy Service
Replication Manager
2. Restart these services:
EMC VSS provider
Volume Shadow Copy Service
Replication Manager
246
Troubleshooting
Creating a replica takes a long time in CLARiiON environment

Older version of CLARiiON FLARE operating system that is running on CLARiiON
may take a long time to create a replica.
Solution
To fix this problem, update CLARiiON FLARE operating system, Navisphere agent,
Navisphere CLI, and ADMSnap of the same version as FLARE operating system, 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 Monitor page.
For example:
"VSS CLIENT... Database "Mailbox Store 2 (SERVERX)" in Storage Group
"Second Storage Group" does not have the "This database can be
overwritten by a restore." checkbox marked."
"VSS validatation and preprocessing failed for Microsoft Exchange
Writer."
"nsrsnap_vss_recover: Recovery operation failed. Refer to log file(s)
for details."
The following message may be displayed by Microsoft Exchange:

The database files in this store were replaced with older versions by
an offline restore. To use the restored files, open the database
property page for this store, select "this database can be
overwritten by a restore", wait for active directory replication,
and try again.
Error ID: C104173A
Exchange System Manager
Solution
1. The Knowledgebase article KB293324: "XADM: "C104173A" Error Message

Occurs After You Restore the Database" on the Microsoft Support website
provides details.
2. Follow the instructions for changing the setting in Exchange System Manager.
Incremental backups may be promoted to full backups

This section outlines when incremental backups may be promoted to full backups:
NetWorker Module for Exchange client on page 247
NetWorker Module for SQL Server client on page 248
NetWorker Module for Exchange client

If the NMM client is installed, requests for an incremental backup through the
NetWorker Module for Exchange (NME) client are automatically promoted to a full
backup. This does not affect NMM client incremental backups of volumes.
For example:
Suppose that NME client requests an incremental backup for Exchange Server
EXSRV1.
NMM client issues
247
Troubleshooting
If the NMM client is installed, then the NME client promotes its own incremental
backup to a full backup to maintain the integrity of the backup and prevent data
loss.
However, the NMM client can still perform an incremental backup of a volume,
such as D:\ on EXSRV1.
NetWorker Module for SQL Server client

If the NMM client is active and configured to back up the SQL database, requests for
an incremental backup through the NetWorker Module for SQL (NMSQL) 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 NMSQL client incremental backups to full backups. This does not affect
NMM client incremental backups of volumes.
For example:
Suppose that the NMSQL client requests an incremental backup for SQL Server
SQLSRV1.
If the NMM client is installed, and the NMM client performs backups of the SQL
database, then the NMSQL 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 NMSQL 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 VSS writer metadata to XML files. These
XML files detail what each active writer on the system is doing, and may be useful to
support personnel for investigating and analyzing writer issues.
To dump the VSS Writer metadata to XML files, run the nsrsnap_vss_save command
with the -G command switch, for example:
D:\Legato\nsr\bin>nsrsnap_vss_save -G
When you run the command, a message displays the directory that the files were sent
to. For example:
NMM .. requesting of writer metadata completed successfully and
deposited in C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\
The directory contains an .XML for each writer on that system, for example:
Exchange Writer.XML
SQL Writer.XML
etc.
The files will probably be hidden because the directory they are sent to are hidden by
default. You can make the folder visible by using Start > Control Panel > Folder
Options > View > Show Hidden Files and Folders.
248
Troubleshooting
Double-click a XML file to view it in your browser, such as Internet Explorer or

Firefox. You can also copy the files to another folder. For example:
D:\>mkdir xmlfiles
D:\>cd xmlfiles
D:\xmlfiles>copy C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\*.*
C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\ExchangeWriter.xml
C:\Users\ADMINI~1\AppData\Local\Temp\3\xmlfiles\SQL Writer.xml
2 file(s) copied.
Modifying the Exchange 2007 or 2010 COM+ components user account or password
If your user account, your password information, or both change after the COM+
component is registered, use the following procedure to change the user account or
password information for the COM+ component:
1. Start component services.
2. Expand Computers > My Computer > DCOM Configuration.
3. Right-click Replication Manager Exchange Interface and select Properties from
the context menu.
4. Click the Identity tab.
5. Modify the domain user account or password and click OK.
This will also modify the account information for the Replication Manager Exchange
Interface Service.
Save sets may not appear in the Recover page

NMM client uses the host machine NETBIOS or short name when connecting to the
NetWorker server to browse backups. If the NETBIOS name is not found, NMM will
Solution
Add the NETBIOS name to the Aliases attribute of the client resource.
Recovery of AES-encrypted files fails without pass phrase

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 pass phrase,
recovery will fail. The application files will only be partially recovered, and will be
empty or in a corrupted state.
Solution
During data recovery, you must:

1. Specify the pass phrase used at the time of backup if it is not the default or current
pass phrase.
2. Provide the pass phrase when recovering AES encrypted files by using the NMM
Security recovery options. EMC NetWorker Module for Microsoft Applications
Release 2.3 Administration Guide provides more information about specifying pass
phrases in NMM.
NMM client issues
249
Troubleshooting
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 fails and the following message is written to the
NetWorker log file:
recover: Error recovering <filename>. The RPC call completed before
all pipes were processed.
Solution
Do not use AES encryption when backing up files that are encrypted using EFS.
Antivirus programs block recovery

When a recovery from a save set All is attempted, antivirus programs may block
NMM recovery. Antivirus programs are designed to protect their own program files
and settings from external threats that may be attempting to disable the program. The
antivirus program cannot always distinguish the recovery from an attack.
Solution
Prior to recovery:
1. Disable the antivirus programs protection properties. The name and location of
the settings varies, but look for a setting like Prevent modification of <AntiVirus
Program Name> command agent files and settings.
2. Clear or disable the setting.
3. Check the antivirus programs documentation or online help for information
about finding and disabling this setting.
To recover files to a system protected by an antivirus program:
1. Disable the antivirus programs setting for protecting its own files and settings.
2. Perform the recovery.
3. Reset the antivirus program to protect its files and settings.
Snapshot cannot include both hardware and software snapshot volumes for clustered NMM
VSS clients
An NMM VSS client resource running on a cluster cannot include both hardware and
software volumes in the same save set. Additionally, save set All cannot be specified
for such a client resource. If both hardware and software volumes are included in a
save set, then backup fails.
Solution
If an NMM client on a cluster has both hardware and software volumes, create at
least two client resources: one for hardware volumes and one for software volumes.
Additionally, do not specify save set All in any of the client resources for the NMM
client. When using a hardware provider with an NMM client, you must configure a
proxy client and the snapshot volume must be exported to a proxy outside of the
cluster.
250
Troubleshooting
Cross-platform directed recovery is not supported on NMM

NMM does not support cross-platform recovery. A directed recovery operation
might fail if the source and the destination NetWorker client machines are not
running the same operating system.
To perform a directed recovery of an Exchange mailbox, both the source and the
destination NetWorker client machines must be running the same version of the
operating system. Both the NetWorker client machines must be running either
Windows Server 2003 or Windows Server 2008. The recovery will fail if the source
NetWorker client machine is running Windows Server 2003 and the destination
NetWorker client machine is running Windows Server 2008.
Because a directed recovery is performed at the application level, the underlying
differences between the operating systems might not be apparent. Also, the error
message that appears with this failure does not specify the actual cause, for example:
63511:nsrsnap_vss_recover:NMM .. VSS failed to initialize the Backup Component
document for restore -- 0x80042311.
63867:nsrsnap_vss_recover:NMM .. XML file processing failed. Missing or invalid
BCDocument.
63849:nsrsnap_vss_recover:NMM .. failed to process BCDoc in XML file. Cannot
proceed.
63847:nsrsnap_vss_recover:NMM .. error 0x80042310 while processing XML file -C:\temp\vssclient_28141413796.xml.
63421:nsrsnap_vss_recover:NMM .. fatal error during processing of the Metadata file
for savetime -- 1256222175.
50325:nsrsnap_vss_recover:nsrsnap_vss_recover: Recovery operation succeeded.
nsrsnap_vss_recover complete time: 10/28/2009 2:14:24 PM
Recover program exited with status: 0
Restore destination has been reset for storage group W2k8DC-SG
The options specified in the Recover Options Dialog have been reset back to their
safe default values.
Recover end time: 10/28/2009 2:14:24 PM
Recover elapsed time: 0 minutes, 24 seconds.
Recovery of large number of items fails if one or more items in a folder is not selected
If one or more items is not selected in a folder that has been selected for recovery,
then recovery may fail if the number of items in that folder is very large. This scenario
has occurred when testing the recovery of 50,000 items in a folder.
Solution
Select all items or the entire folder, and then perform recovery. After recovery, delete
any unwanted items.
Multiple client resources with the same name cannot be combined in the same group
If two or more client resources with the same name are in the same snapshot group,
then some of the save sets will not be recoverable. NMM does not support combining
multiple client resources with the same name in the same group.
Solution
Either combine the client resources into a single client resource, or create separate
groups and back up the individual clients in separate groups.
NMM client issues
251
Troubleshooting
Backup of two partitions of the same CLARiiON disk fails

Backup of two partitions of one SAN LUN is not supported. The EMC Information
Protection Software Compatibility Guide contains the latest support information. This
limitation only applies to hardware-based snapshot and does not apply to
software-based snapshot. When you try to back up two partitions of one SAN LUN,
the backup fails and the following error appears in nmm.raw:
An error was detected during the replica creation.
Details in nmm.raw on % s. \n 1 0 16 starwar.duke.com
63315 1246425081 5 0 0 8252 8092 0 starwar.duke.com
nsrsnap_vss_save 26
NMM.. Exception caught: %s 1 0 25 Failed to create replica.
Connection to DPM service lost during DPM recovery

During DPM database recovery or DPM replica recovery that uses the NMM client
on a DPM Server, if the DPM management console is open, then a dialog box appears
and the connection to DPM service is lost:
1. Close the dialog box that appears.
The DPM management console is closed.
2. After the recovery operation is complete, reopen the DPM management console.
DPM replica backup is not correctly configured

If not configured properly, DPM replica backups may fail and the following error
message may appear:
49931 12/22/2009 8:16:43 AM 5 0 0 10184 7940 0
es-chl-dpm-001.es.govt.state.ma.us nsrsnap_vss_save RM ..
027114 ERROR:DPM Writer is stable. The error is
VSS_E_WRITERERROR_RETRYABLE. The code is: 0x800423f3. Check the
application event log for more information.
Review the following before starting DPM replica backup:
NSR_PS_FIRST_SAVESET_SAVE attribute should be set to actual database name.

For example:
NSR_PS_FIRST_SAVESET_SAVE=APPLICATIONS:\Microsoft DPM\DPM
database
NSR_PS_FIRST_SAVESET_SAVE attribute should not be used if the DPM

configuration database is not one of the save sets or if the DPM configuration
database is the only save set. This attribute should only be used if the DPM
configuration database is one of the multiple save sets that is being backed up
under a single NetWorker client resource.
The Client Retries attribute of the Group resource must be set to 0.

Note: NMM does not support Group retry.
252
Troubleshooting
Populate the Application Information of the client resource for replica backups
with the following:
NSRSNAP_SNAP_TYPE=vss
NSR_DPM_RETRY_MAXIMUM=3
The default value for NSR_DPM_RETRY_WAIT and
NSR_DPM_RETRY_MAXIMUM are 10 minutes and three attempts
respectively.
Rerun the backup with a single replica in the save set to make sure that the
backup is successful.
Backup fails if Exchange Server in is renamed after it is created

If the name of a Exchange Server 2007 is changed after it is created and then a backup
is performed, the backup fails.
Restart the Microsoft Exchange Information Store Service to successfully backup the
renamed storage group:
1. Click Start, point to Administrative Tools, and then click Services.
2. On the Services window, right-click Microsoft Exchange Information Store, and
then click Restart.
The Microsoft Support website
http://technet.microsoft.com/en-us/library/bb795725.aspx provides more
information.
In Exchange Server 2010, although backup completed successfully for renamed database,
recovery fails
After a successful backup, if a Exchange Server 2010 mailbox database is renamed,
then recovery of renamed mailbox database fails with an error message.
To recover a database that has been renamed:
1. Restart the Microsoft Exchange Information Store Service.
2. Click Start> administrative Tools, and then click Services.
then click Restart.
The Knowledgebase article 795725 on the Microsoft Support website provides more
information.
In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of new database
name after renamed mailbox database
nsrsnap_vss_save -? lists old database name instead of new database name after the
mailbox database is renamed. For example, if the actual mailbox database name is
DB2, rename it to DB21, and back up DB21. The backup fails and the rename database
is not listed when the command nsrsnap_vss_save -? is used.
NMM client issues
253
Troubleshooting
Note: Remove the inverted commas when copying the save set name from the output of
nsrsnap_vss_save -?.
Restart the Microsoft Exchange Information Store Service to successfully backup the
renamed storage group:
1. Click Start, point to Administrative Tools, and then click Services.
then click Restart.
The Knowledgebase article 795725 on the Microsoft Support website provides more
information.
Save sets from an Avamar AFTD for NMM backups show retention set to 1/18/2038
When using mminfo command on media, save sets like VSS:\ display an odd
expiration date, for example, year 2038. This is normal behavior and can be ignored
as these save sets do not affect the browse and retention of the backups. Do not alter
or delete these save sets.
Microsoft updates required to fix the vds.exe crash errors during retention on Windows Server
2008 and Windows Server 2003
On Windows Server 2008 and Windows Server 2003, during NMM backups, Virtual
Disk Service (VDS) crashes while applying retention because VDS incorrectly
accesses some providers that are unloaded, when VDS is in the exit process.
Install the following Microsoft hotfixes on the respective platforms to fix the issue:
For Windows 2008 SP2 (x64) Apply KB978897
For Windows 2003 SP2 (x86) Apply KB949001
The Microsoft Support website provides information about these hotfixes.
Back up of SYSTEM COMPONENTS fails due to missing System Writer

If the System Writer is missing, the backup of SYSTEM COMPONENTS fails with the
following error message:
"63472 1298327394 5 0 0 1620 1984 0
win-geui5lp5gei.nmm23.emc.com nsrsnap_vss_save 85 ERROR : Found
'System Writer' missing which is required for SYSTEM COMPONENTS
backup. 0"
Solution
The System Writer runs in the context of Cryptographic Services (CryptSvc service)
on Windows Server 2003, Windows Server 2008, or Windows Server 2008 R2.
The System Writer may be missing due to several reasons. To identify and rectify this
problem, perform the following steps:
1. Open the Services console and verify that the Cryptographic Services log in has
the Network Service account credentials.
2. On the Windows Server:
a. Click Start >Run.
254
Troubleshooting
b. Type msconfig and press Enter.

c. Click the Services tab and select Hide All Microsoft Services and Disable All
Third Party Services.
d. Click the Startup tab and Disable All startup Items.
e. Click OK and select Restart.
f. Reboot the server.
g. Run vssadmin list writers command to check if the System Writer is
displayed.
h. If the issue still persists: open a command prompt as Run As Administrator,
and type the CD c:\windows\system32 Takeown /f command to see if it the
System Writer is displayed.
For example,
CD c:\windows\system32 Takeown /f %windir%\winsxs\filemaps\* /a
icacls %windir%\winsxs\filemaps\*.* /grant "NT
AUTHORITY\SYSTEM:(RX)" icacls %windir%\winsxs\filemaps\*.*
/grant "NT Service\trustedinstaller:(F)" icacls
%windir%\winsxs\filemaps\*.* /grant "BUILTIN\Users:(RX)" it has
been reported that there is some permissions issue which can cause
this kind of issue. Please follow the steps below and check if it
can be helpful.
3. On domain controller:
a. Open Active Directory Users > Computers.
b. Click View and then Advanced features.
c. Right-click Builtin and click Properties.
d. Click Security tab.
e. Grant read permission to the authenticated users.
Note: By default, authenticated users should have read permission for the system to take
system state backup.
f. Click Apply and OK.

g. Restart Cryptographic Services.
Problems with RMExchangeInterface component

If there are problems with the RMExchangeInterface component, try one or more of
the following:
Check that the service is installed.
Check service account. It should not be local system. It should be an account that
has Exchange Administrator privileges.
Note: The service is not running by default, it runs on demand.
NMM client issues
255
Troubleshooting
Check the Install.log in C:\Program

Files\EMC\rmagentps\client\bin\Install.log. The file itself does not contain
much information. The existence of this log confirms that the COM component
was registered and the service was installed.
Validate COM entry is present by using the Component Services manager.
Check the event log for any errors.
SharePoint backup fails when host and proxy client do not match
When using data mover to perform a SharePoint backup, the application host and
proxy client must use the same operating system release, patch level and processor
architecture:
The application host and proxy client must be same operating system release.
For example, both are Windows Server 2003 or both are Windows Server 2008.
The application host and proxy client must be same operating system patch or
service pack level.
For example, both are Windows Server 2003 R2 or both are Windows Server 2003
SP3.
The application host and proxy client must have the same processor architecture.
For example, both are x86 or both are amd64/x64.
NMM installation issues

The following sections describe some common problems and possible solutions for
NMM installation:
RMAgentPS fails to uninstall when uninstalling NMM on page 256
Recovery failure after .NET 3.5 framework installation on page 258
SYSTEM COMPONENTS failure after McAfee uninstall on page 258
RMAgentPS fails to uninstall when uninstalling NMM

During NMM uninstallation, the Replication Manager is not uninstalled completely.
Solution
On non-server core machines:
1. From the Add or Remove Programs, uninstall RMAPI. This removes the RMAPI
binaries.
2. Check the installation folder and delete the files, if any.
3. Go to services.msc .
256
Troubleshooting
4. Check if the RMAgentPS service and Replication Manager Exchange interface

service are shown as registered. If yes, delete the required registry keys:
RMAgentPS under the following:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\RMAgentPS
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RMAge
ntPS
RM_ExchangeInterface under the following:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\
RM_ExchangeInterface
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
RM_ExchangeInterface
Note: The RM_ExchangeInterface key exists only when Exchange is installed in the
setup.
5. Ensure that the services are no longer shown in services.msc.

6. Rerun the PowerSnap installer to see if RM installs fine.
On server core machines:
1. Go to the path where NMM binary is copied.
2. To uninstall Replication Manager manually, use the command:
\networkr\ps\setup.exe /s /v "/qn /L*v
"""%temp%\PSuninstall.log""" " /x
This removes the RMAPI binaries.
3. Check the installation folder and delete the files, if any.
4. To see the status of the RM service, if it still exists, use the following command:
>sc queryex RMAgentPS
5. If the service exists, use the following command to stop the service:
>taskkill /F RMAgentPS
Ensure that the service is also stopped from registry in the locations:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
6. Check for the entry of RMAgentPS.
7. Open the registry by typing regedit.exe at command prompt and go to the
location:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\U
ninstall\ to check if the RM binaries are still installed.
8. Under Uninstall, look for the key {9E5ED863-C18B-4BAB-8248-C0D443837D4F}.
If found, delete this key.
9. Rerun the PowerSnap installer to see if RM installs fine.
NMM installation issues
257
Troubleshooting
Recovery failure after .NET 3.5 framework installation

Volume and SYSTEM COMPONENTS recovery fails if the system previously had
.NET Framework 3.5 installed, and the operating system was reinstalled but the .NET
Framework 3.5 was not re-installed before attempting recovery. When recovery fails,
an error is displayed: The directory is not empty...
Solution
To restore the Volume and SYSTEM COMPONENTS on a system that previously had
.NET Framework 3.5 installed at the time of the backup:
1. Reinstall the operating system.
2. Reinstall .NET Framework 3.5.
3. Install NMM.
4. Recover the volume and SYSTEM COMPONENTS.
SYSTEM COMPONENTS failure after McAfee uninstall

If a program does not uninstall cleanly, some program files may still remain after
uninstallation. This may cause SYSTEM COMPONENTS:\ backups to fail. This has
been known to occur with McAfee VirusScan 8.5i, but may occur with other
programs.
Solution
Microsoft has identified this as an issue with the VSS System Writer. The
Knowledgebase article KB955078 on the Microsoft Support website describes this
issue and provides several solutions.
If Exchange Server is installed after NMM, NMM reinstallation is required to get Replication
Manager Exchange Interface
If Exchange Server 2010 stand-alone is installed on Windows Server 2008 R2 after
NetWorker client and NMM have been installed, snapshots fail. If changes are made
for NMM from Programs and Features, the window to identify domain, and add
username and password appears, but Replication Manager is not updated.
Solution
Uninstall and reinstall NMM 2.3.
NMM uninstall and reinstall required to change the Replication Manager port number
The Replication Manager port number can be changed after NMM is installed.
Solution
Uninstall and reinstall NMM 2.3. During the reinstallation process, change the
required Replication Manager port settings.
258
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 259
2. PowerSnap client on page 259
3. Replication Manager on page 260
4. EMC VSS provider on page 260
5. Active Directory on page 261
6. NetWorker server on page 261
In addition, third-party providers generate their own logs in place of the Solutions
Enabler log (hwprov.log). The third-party documentation provides more
information.
NMM client
Log files
The NMM client log files are named:
nmm.raw
nsrcscd.raw
Location
Applogs folder. For example, C:\Program Files\Legato\nsr\applogs\.

Description
Both save and recover CLIs write to these files. The log files are cumulative, so they
are appended with each run. The logging level of each log file is controlled by the
debug level of the process (-D).
PowerSnap client
Log files
NMM 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
259
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\EMC\RMService\RMAgentPS\Client\CC_DEBUG_LEVEL.
The default value is 2, but can be changed to 3.
To change the default value:
1. Stop RM Services.
2. Change the value in the registry.
3. Restart RM Services.
Error messages in Replication Manager log files also appear in the standard user
EMC VSS provider

Log files
To get more debug information for EMC VSS provider log, change the registry
value to Debug in HKLM\SOFTWARE\emc\ShadowCopy\LogLevel
To get more debug information for Solutions Enabler, set the following
environment variables:
SYMAPI_DEBUG=-1
SYMAPI_DEBUG_FILENAME=<Drive:\FileName>
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
260
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 Release 7.6 SP2 Administration Guide.
Manually stopping and starting services

NMM client processes may need to be manually stopped and started in conjunction
with configuration and troubleshooting activities. The NetWorker server creates
several log files. These log files are documented in the EMC NetWorker Release 7.6 SP2
Administration Guide, which provides more information about starting and stopping
services on Windows hosts, Console server, NetWorker server, client, or storage
node.
Table 39 on page 261 lists the services for NetWorker, PowerSnap, and Replication
Manager that are active on the system.
Table 39
Services and processes used in NMM client (page 1 of 2)
Executable
Product
Category
Function
nsrexecd
NetWorker
Service
Authenticates and processes the NetWorker servers remote execution requests

and executes the save programs on the client.
nsrpsd
PowerSnap
Service
Provides PowerSnap client services, including snapshot consistency check

function, to apply retention policy and backup functions to rollover snapshots.
irccd.exe
Replication
Manager
Service
Provides Replication Manager client application and storage services for creating
VSS-based snapshots and for rollback of VSS-based snapshots for EMC storage.
RM_ExchangeInterface.exe
Replication
Manager
Service
Provides Replication Manager Server Exchange Interchange services to handle

Exchange Server 2007-specific commands for Replication Manager.
rm_api.dll
Replication
Manager
Library
Library that provides Replication Manager client interface library for NetWorker,
used by NetWorker backup and recover processes.
nsrsnap
PowerSnap
Process
Temporary process active during snapshot groups that provides client-side

workflow for snapshot groups, including applying retention policy, spawning
process to create the snapshot, and spawning process to rollover the snapshot.
nsrsnap_vss_save
NetWorker
Process
Temporary process active during snapshot groups that is responsible for executing
the client-side workflow to create the snapshot for the save sets specified in the
client resource. It is spawned by nsrsnap and will communicate with irccd.exe to
create the VSS-based snapshot, and then will communicate with PowerSnap
services to register the snapshot.
Manually stopping and starting services
261
Troubleshooting
Services and processes used in NMM client (page 2 of 2)
Table 39
Executable
Product
Category
Function
nsrcscd.exe
NetWorker
Service
This service acts as an agent to provide details about a system environment to the
NMM user interface.
A log file named nsrcscd.raw is generated in nsr\applogs folder.
Libpsvssclnt.dll
PowerSnap
Library
Library that provides PowerSnap client Interface for NetWorker backup and
recover processes.
nsrsnapagent
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.
nsrsnapbwragent
Temporary
Service
Temporary service active during snapshot backup and file system snapshot
browse operations that provides the ability to read the file system on the snapshot.
Process
Provides graphical user interface for NetWorker software.
winclient
NetWorker
Using nsr.dir to skip files for NMM backup and recovery

Use nsr.dir, which is the NMM directive for exclusion of files for NMM backup and
recovery. The files can be skipped both at file level, as well as directory level. Ensure
that both nsr.dir and the files that are to be skipped are at the same location.
Troubleshooting issues during SQL databases directed recovery

Review the following to troubleshoot issues that may come up during directed
recovery of SQL databases:
Ensure that the client machine where directed recovery browsing is performed
has NMM 2.3 installed, otherwise the SQL databases are not displayed for
directed recover browsing.
Recover one database at a time. For directed recovery of multiple databases,

separate paths cannot be provided for each database. All the selected databases
are recovered to a single target path.
Name resolution
NetWorker server and the NMM client machines need proper name resolution to
identify and back-translate computer names, such as from name-to-IP address or IP
address-to-name. Also, the NMM client uses the host machine NETBIOS or short
name when connecting to the NetWorker server to browse backups. If the NETBIOS
name is not found, NMM will not be able to display backups.
To ensure clear communication of computer names:
1. Add the NetWorker server name to either of the following:
The local hosts file, which is located in %SystemRoot%\system32\drivers\etc.
The Domain Name server that contains the names of all servers on your
network.
262
Troubleshooting
2. When configuring a client resource for solutions like Exchange, SharePoint, and
so on, specify the NETBIOS name for the client in the Aliases attribute.
The sections in EMC NetWorker Module for Microsoft Application Release 2.3
Administration Guide describe how to enter the NETBIOS name in the Aliases
attribute.
The EMC NetWorker Release 7.6 SP2 Administration Guide provides details about
network and server communication errors.
Other troubleshooting resources

Determine where the problem appears:
If the problem appears on the NetWorker server, or otherwise seems to be on the

server side, check to make sure that the NetWorker server is installed and
configured correctly. Also, check the log files and error message documentation
for the NetWorker server.
If the problem appears to be with PowerSnap or Replication Manager, and is not

unique to NMM client, check other documentation.
The following documents provide specific error message, troubleshooting, or other

documentation outside of NMM client:
EMC NetWorker Installation Guide Release 7.6 SP2
EMC NetWorker Administration Guide Release 7.6 SP2
EMC NetWorker Error Message Release 7.6 SP2
EMC NetWorker PowerSnap Module Installation and Administration Guide
EMC Replication Manager Administrators Guide
Other troubleshooting resources
263
Troubleshooting
264
Glossary
This glossary contains terms related to disk storage subsystems. Many of these terms
are used in this manual.
A
ad hoc backup
See manual backup.
administrators group
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.
Application Specific
Module (ASM)
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.
ASR writer
archive
archive volume
auto media
management
autochanger
autochanger sharing
The VSS writer, which is responsible for identifying critical data that is needed to
perform an offline restores.
Backing up directories or files to an archive volume to free disk space. Archived data
is not recyclable.
Volume used to store archive data. Archived data cannot be stored on a backup
volume or a clone volume.
Feature that enables the storage device to automatically label, mount, and overwrite
an unlabeled or recyclable volume.
See library.
See library sharing.
B
backup
Operation that saves data to a volume.

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

Software program that is used to manage NetWorker servers and clients. The
Console server also provides reporting and monitoring capabilities for all NetWorker
processes.
See nonpersistent snapshot.
Any volume containing system state files or files for an installed service, including
volumes mounted as NTFS directories which contain such files. The volume where a
critical volume is mounted is also considered to be critical. This is required to
perform an offline restore, however maybe optional for this release depending upon
the difficulties of implementing this feature.
D
domain controller
Data Mover (DM)
data retention policy

datawheel
datazone
Dynamic Drive
Sharing (DDS)
device
Computer that stores directory data and manages user interactions within a domain,
including logon, authentication, directory searches, and access to shared resources.
Client system or application, such as NetWorker, that moves the data during a
backup, recovery, or snapshot operation. See also proxy client.
See retention policy.
See library.
Group of hosts administered by a NetWorker server.
Feature that allows NetWorker software to recognize shared drives.
1. Storage unit that reads from and writes to backup volumes. A storage unit can be a
tape device, optical drive, autochanger, or file connected to the server or storage
node.
2. When dynamic drive sharing (DDS) is enabled, refers to the access path to the
physical drive.
Distributed File System

(DFS)
Microsoft Windows add-on that allows you to create a logical directory of shared
directories that span multiple machines across a network.
directed recovery
Method of recovery that recovers data that originated on one client computer and
re-creates it on another client computer.
directive
disk subsystem
Instruction that directs NetWorker software to take special actions on a given set of
files for a specified client during a backup or recovery operation. Directives are
ignored in manual (unscheduled) backups.
Integrated collection of storage controllers or HBAs, disks, and any required control
software that provides storage services to one or more hosts, such as CLARiiON
arrays.
267
Glossary
F
file index
file system
See client file index.

1. The software interface used to save, retrieve, and manage files on storage media by
providing directory structures, data transfer methods, and file association.
2. The entire set of all files.
full backup
See level.
G
group
granular recovery
Client or group of client computers that are configured to back up files at a

designated time of day.
Granular recovery provides the ability to recover specific files in seconds from a
single backup. This dramatically reduces the recovery time and the footprint of the
backup on storage resources.
H
high-available system
host ID
System of multiple computers configured as cluster nodes on a network that ensures

that the application services continue despite a hardware or software failure. Each
cluster node has its own IP address with private resources or disks that are available
only to that computer.
Serial number that uniquely identifies a host computer.
I
inactivity timeout
incremental backup
instant backup
instant restore
Number of minutes to wait before a client is considered to be unavailable for backup.

Backup level in which only files that have changed since the last backup are backed
up. See also level.
Process of creating a point-in-time copy (snapshot) of data from a single client and
saving it on a primary storage volume, which can be immediately recovered as a
backup copy.
Process of copying data created during an instant backup to its original location, or to
an alternate location, during a recover operation.
J
jukebox
label
legacy method
268
See library.
Electronic header on a volume used for identification by NetWorker or other Data
Mover application.
Use of special-case Microsoft APIs to back up and recover operating system
components, services, and applications.
Glossary
level
library
library sharing
local cluster client
locale settings
LUN (logical unit)
LUN address
Backup configuration option that specifies how much data is saved during a
scheduled or manual backup. A full (f) backup backs up all files, regardless of
whether they have changed. Levels one through nine [1-9] backup files that have
changed since the last lower numbered backup level. An incremental (incr) backup
backs up only files that have changed since the last backup.
Hardware device that contains one or more removable media drives, as well as slots
for pieces of media, media access ports, and a robotic mechanism for moving pieces
of media between these components. Libraries automate media loading and
mounting functions during backup and recovery. The term library is synonymous
with autochanger, autoloader, carousel, datawheel, jukebox, and near-line storage.
Shared access of servers and storage nodes to the individual tape drives within a
library.
NetWorker client that is not bound to a physical machine, but is instead managed by
a cluster manager. It is also referred to as a logical or virtual client.
Settings that specify the input and output formats for date and time, based on local
language conventions.
Logical unit of storage on a CLARiiON system. This refers to a device or set of
devices, usually in a CLARiiON storage array.
SCSI identifier of a logical unit number (LUN) within a device target. Each LUN
address identifies a device on a SCSI bus that can perform input/output (I/O)
operations.
M
manual backup
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.
media
Physical storage medium, such as magnetic tape, optical disk, or file system to which
backup data is written.
media database
media index
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.
metadata document
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.
mount
To make a database available for use or to place a removable tape or disk volume into
a drive for reading or writing.
mount point
See volume mount point.
269
Glossary
N
Network Data
Management
Protocol (NDMP)
NetWorker
administrator
NetWorker client
TCP/IP-based protocol that specifies how heterogeneous network components

communicate for the purposes of backup and recovery.
User who can add to or change the configuration of the NetWorker server, media
devices, and libraries. NetWorker administrators must have their usernames
included in the NetWorker server Administrator list.
See client.
NetWorker Console
server
See console server.
NetWorker
Management
Console
See console server.
NetWorker server
NetWorker storage
node
nonclone pool
noncritical volume
nonpersistent
snapshot
Computer on a network running the NetWorker software, containing the online

indexes, and providing backup and recover services to the clients on the same
network.
See storage node.
Pools that contain data that has not been cloned.

A volume containing files that are not part of the system state or an installed service.
The backup of non-critical volumes is not supported by either product for their initial
releases.
Snapshot backup that is moved to secondary storage on the NetWorker server or
storage node and is no longer available for instant restore from a supported type of
primary storage.
O
online indexes
Databases located on the NetWorker server that contain all the information
pertaining to the client backups (client file index) and backup volumes (media
database).
online restore
A restore operation performed using the normal recover UI, and the computer has
been booted from an installed operating system.
offline restore
A restore operation performed from the Windows PE environment.
operator
Person who monitors the server status, loads backup volumes into storage devices,
and executes day-to-day NetWorker tasks.
P
pathname
270
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.
Glossary
persistent snapshot
Snapshot that is retained on disk. A persistent snapshot may or may not be rolled
over to tape.
point-in-time copy
(PiT)
Fully usable copy of a defined collection of data, such as a consistent file system,
database, or volume, which contains an image of the data as it appeared at a single
point in time. A PiT copy is also called a shadow copy or a snapshot.
policy
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.
pool
PowerSnap
provider
proxy client
Feature to sort backup data to selected volumes.

EMC technology that provides point-in-time snapshots of data to be backed up.
Applications that are running on the host system continue to write data during the
snapshot operation, and data from open files is included in the snapshots.
Software component defined by Microsoft VSS, that plugs in to the VSS environment.
A provider, usually produced by a hardware vendor, enables a storage device to
create and manage snapshots.
Surrogate client that performs the NetWorker save operation for the client that
requests the backup. A proxy client is required to perform a serverless backup.
Q
quiescing
Process in which all writes to disk are stopped and the file system cache is flushed.
Quiescing the database prior to creating the snapshot provides a transactionally
consistent image that can be remounted without file system checks or database
consistency checks. Quiescing a database is the most common way of creating a
database snapshot.
R
recover
To recover files from a backup volume to a client disk.
Registry
Microsoft Windows database that centralizes all Windows settings and provides
security and control over system, security, and user account settings.
requestor
replica
resource
restore
retention policy
Interface with the Microsoft VSS infrastructure to initiate the creation and destruction
of shadow copy. NetWorker software is a requestor.
See shadow copy.
Component that describes the NetWorker server or its clients. Clients, devices,
schedules, groups, and policies are all NetWorker resources. Each resource has
attributes that define its properties.
Process of retrieving individual datafiles from backup storage and copying the files
to disk.
NetWorker policy that specifies the minimum period of time that must elapse before
backed-up data is eligible to be overwritten on the backup media. Backed-up data
that has not exceeded its browse policy time can be recovered more quickly than data
that has exceeded its browse policy time but not its retention policy time. See also
browse policy.
271
Glossary
retrieve
rollback restore
rollover
root
To locate and recover archived files and directories.

Process by which a specific point-in-time copy (snapshot) of data is restored to the
source location by using the hardware's particular capabilities. A rollback restore is a
destructive save set restore.
Process of backing up a snapshot to a conventional backup medium such as tape.
Whether or not the snapshot is retained on disk depends on the snapshot policy.
Highest level of the system directory structure.
S
save set
save set ID (SSID)

save set recover
save set status
server index
serverless backup
service port
shadow copy
shadow copy set
shadow copy
technology
skip
272
Group of files or a file system from a single client computer, which is backed up on
storage media.
Internal identification number assigned to a save set.
To recover data by specifying save sets rather than by browsing and selecting files or
directories.
NetWorker attribute that indicates whether a save set is browsable, recoverable, or
recyclable. The save set status also indicates whether the save set was successfully
backed up.
See client file index.
Backup method that uses a proxy client to move the data from primary storage on the
application server host to secondary storage on another host. Serverless backups free
up resources on the application server by offloading the work of processing
snapshots to a secondary host.
Port used to listen for backup and recover requests from clients through a firewall.
Temporary, point-in-time copy of a volume created using VSS technology. See also
Volume Shadow Copy Service (VSS).
Complete roadmap of what was backed up at a single instant in time. The shadow
copy set contains information about the writers, their components, metadata, and the
volumes. A backup components metadata document containing that information is
created and returned to the requestor after the snapshot is complete. NetWorker uses
this document with the corresponding save set at recover time.
Defined and standard coordination between business application, file system, and
backup application that allows a consistent copy of application and volume data to
exist for replication purposes.
Backup level in which designated files are not backed up.
snap clone
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.
snap ID
Also known as a snapid, a unique 64-bit internal identification number for a snap set.
snap set
Group of files, volumes, or file systems from a single client, describing the collection
of data for which a point-in-time copy is created on an external disk subsystem, such
as a storage array.
Glossary
snapshot
snapshot expiration
policy
snapshot policy
Point in time, read-only copy of data created during an instant backup.

Policy that determines how long snapshots are retained before their storage space is
made available for the creation of a new snapshot.
Set of rules that control the lifecycle of a snap set. The snapshot policy specifies the
frequency of snapshots, and how long snapshots are retained before recycling.
snapshot retention
policy
Policy that determines how many PIT copies are retained in the media database and
thus are recoverable.
staging
Moving data from one storage medium to a less-costly medium, and later removing
the data from its original location.
stand-alone device
Storage device that contains a single drive for backing up data. Stand-alone devices
cannot store or automatically load backup volumes.
storage device
storage node
system state
See device.
Storage device physically attached to a computer other than the NetWorker server,
whose backup operations are administered from the controlling NetWorker server.
All files that belong to VSS writers with a usage type of BootableSystemState or
SystemService. This is required to perform an offline restore.
V
volume
1. A unit of physical storage medium, such as a magnetic tape, optical disk, or file
system to which backup data is written.
2. An identifiable unit of data storage that may reside on one or more host disks.
volume ID
volume mount point
volume name
volume pool
Volume Shadow Copy
Service (VSS)
VSS
VSS component
Internal identification that NetWorker software assigns to a backup volume.

Disk volume that is grafted into the namespace of a host disk volume. This allows
multiple disk volumes to be linked into a single directory tree, and a single disk or
partition to be linked to more than one directory tree.
Name assigned to a backup volume when it is labeled. See also label.
See pool.
Microsoft technology that creates a point-in-time shadow copyof a disk volume.
NetWorker software backs up data from the shadow copy. This allows applications
to continue to write data during the backup operation, and ensures that open files are
not omitted.
See Volume Shadow Copy Service (VSS).
Subordinate unit of a writer.
273
Glossary
W
writer
274
Database, system service, or application code that provides metadata document

information about what to back up and how to handle VSS component and
applications during backup and recovery operations. A Writer provides information
to requestors to ensure that application data is consistent, application files are closed
and ready for a slight pause to make a Shadow Copy.
Index
A
Active Directory (AD)
backups for object selection granularity 45
log files 261
Active Directory Lightweight Directory Services (AD LDS)
42
active node 135
AD LDS backup and recovery 42
AD recovery
individual objects and attributes 53
null value restriction 55
restrictions for 53
schema object restriction 55
system-only attribute restriction 54
tombstone restriction 54
alternate mount path for proxy client 116, 167
alternate storage group, Exchange recovery to 146
application information attribute
DPM 65
Exchange 115, 126, 167
Hyper-V 82
SharePoint 2007 200
SQL 22
application writers
Hyper-V 85
B
backup
Active Directory 45
backup client resource
configuring DPM 67
configuring Hyper-V 86
configuring multiple 67, 86
backup command attribute
DPM 68
Exchange 124, 171
Hyper-V 87
SharePoint 2007 205, 207
Backup content without interruption 193
backup groups
configuring 49
backup roadmap
Hyper-V 79
backup save sets

DPM 66
Exchange 117
Hyper-V 83, 87
SharePoint 2007 disaster recovery 214
specifying 50, 68
SQL 24
best practices
SQL backup and recovery 36
best practices for backup and recovery
Exchange 115
Hyper-V child partition 95
Hyper-V parent partition 95
SQL in SharePoint 2003 184
C
child partition
best practices for backup and recovery 95
Hyper-V configurations 79
child partitions 77
CLARiiON
E_VETO_PROVIDER error message 238
error message 238
replica takes long time 246
client resource
configuring for DPM backup 67
configuring for Hyper-V backup 86
configuring for SharePoint 2007 backup 204
configuring for SQL backup 26
configuring when in a cluster 26, 46, 67, 120, 170
cluster server
entering physical hostname of 51
scheduling backups for 26, 46, 67, 120, 170
critical volumes 232
D
database level granularity 193
device
configuring for rollover backup 47
directed recovery
275
Index
DPM-protected server 73
Exchange Server 2007 150
disaster recovery
DPM 74
Hyper-V 93
Hyper-V parent partition 93
Microsoft Exchange Server 2007 152
SharePoint 2007 213
SQL 36
DPM
configuring client resource for backup 67
directed recovery 73
disaster recovery options 71
DPM disaster recovery
individual objects and attributes 74
E
email notification
NetWorker events 237
errors
E_VETO_PROVIDER 238
E_VOLUME_NOT_SUPPORTED 238
error code 0x800423f3 239
Microsoft I/O write 246
NMM client 238
replica in a CLARiiON array 246
VSS CLIENT... Invalid Writer Selection 239
VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDE
R 245
VSS_E_WRITERERROR_RETRYABLE 239
with Exchange 239
Event viewer 237
events
notification 240
exceptions
Windows Firewall 243
Exchange
errors 239
point-in-time recovery 136
roll-forward recovery 135
URL encoding for save sets 118
Exchange backup scenarios 107
Exchange recovery
alternate storage group 146
database can be overwritten selection 133
options for 132
directed recovery 150
F
failover from the passive node 135
five distinct server roles
Exchange 107
full farm backup and restore for catastrophe 193
G
groups
configuring for backup 49
guest. See also child partition
276
H
host
Hyper-V 78
Hyper-V
backing up a virtual machine with multiple volumes
82
backup roadmap 79
configuring backups 85
configuring client resource for backup 86
disaster recovery 93
granular backup and recovery 96
host 78
parent partition disaster recovery 93
recovery 88
save sets 83
Hyper-V best practices
child partition backup and recovery 95
parent partition backup and recovery 95
Hyper-V child partition
configurations 79
Hyper-V storage and backup options 79
I
improved management experience
Exchange 108
improved setup experience
Exchange 108
items
searching for recovery 145
L
label
creating for pool 48
log files 237
Active Directory 261
NetWorker Server 261
NMM client 259
PowerSnap client 259
Replication Manager 260
troubleshooting with 259
M
marking items for recovery 144
disaster recovery 152
Microsoft Windows Server 2008 42, 61
mount path for proxy client 116, 167
MSDE
turning writer on or off in registry 62
multiple client resources for backup 67, 86
N
NetWorker events
email notification 237
NetWorker Monitor window 237
NetWorker Server
log files 261
NMM client
Index
error messages 238

log files 259
notification
NetWorker events 240
savegroup failed 240
notifications 237
types 237
NSR_ALT_PATH command 116, 167
NSR_DM_PORT command 115, 167
O
optimized default settings
Exchange 108
OSearch14 VSS Writer 222
overwrite prevention error
Exchange database recovery 247
P
parent partition
passive node 136
password
restriction for active directory recovery 55
physical server
Hyper-V 78
pool
label for 48
ports
Exchange proxy client communications 115, 167
post-restore synchronization of databases 194
PowerSnap client
log files 259
proxy client
mount path 116, 167
port number for communicating 115, 167
SharePoint serverless backup 200
SQL serverless backup 22
R
recovery
Exchange options 132
Hyper-V 88
marking items 144
searching for items 145
recovery error
Exchange database 247
remote access attribute
virtual cluster server specification 51
replica
error message 239
takes long time in CLARiiON environment 246
Replication Manager
error message 238
log files 260
resource for backup
rollover backup
device for 47
S
save sets
DPM 66
Exchange 117
Hyper-V 83
SharePoint 2003 183
specifying for backup 50, 68
specifying for Hyper-V backup 87
SQL 24
SQL databases in SharePoint 2007 214
savegroup failed notification 240
search index files backup and recovery 194
searching for a recovery item 145
Security Configuration Wizard 243
selecting items for recovery 144
serverless backup 22
SharePoint 2007 backup 200
Service application 220
services 261
Services in SharePoint 2010 220
SharePoint 2003
recovery 183
save sets 183
SharePoint 2007
specifying save sets for backup 205, 206
URL encoding 199
URL encoding for save sets 199
SharePoint inventory list 193
SharePoint Services Writer 222
single VSS reference writer 193
SPSearch4 VSS Writer 222
SQL
URL encoding 25
SQL proxy client 22
SQL Server
configure client resource 26
storage and backup options
Hyper-V 79
storage array
Exchange rollback requirements 113
syntax
DPM save sets 66
Exchange save sets 117
Hyper-V save sets 83
SharePoint2007 201, 223
SQL 24
T
troubleshooting
checking other documents 263
U
URL encoding
Exchange save sets 118
SharePoint 2007 199
277
Index
SharePoint 2007 save sets 199

SQL save sets 25
V
virtual cluster server
entering physical hostname of 51
scheduling backups for 26, 46, 67, 120, 170
VSS CLIENT... Invalid Writer Selection 239
VSS_E_VOLUME_NOT_SUPPORTED_BY_PROVIDER
245
VSS_E_WRITERERROR_RETRYABLE 239
W
Windows DR backup 232
Windows DR recovery 233
Windows Firewall
NetWorker blocked by 243
Windows Server 2008 42, 61
Windows SharePoint Services 2.0
see SharePoint 2003 182
278

NetWorker Module For Microsoft Applications 2.3 Application Guide

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NetWorker Module For Microsoft Applications 2.3 Application Guide

Hochgeladen von

Copyright:

Verfügbare Formate

EMC NetWorker

Module for Microsoft Applications

Copyright 2007-2010 EMC Corporation. All rights reserved.

Microsoft SQL Server Backup and Recovery

Clustered SQL Server disaster recovery on Windows Server 2008,

Microsoft Active Directory Backup and Recovery

Microsoft Data Protection Manager Server Backup and Recovery

Microsoft Hyper-V Server Backup and Recovery

Hyper-V application information variable settings ....................................

Microsoft Exchange Server Backup and Recovery

Exchange recovery options............................................................................ 133

Microsoft Exchange Server 2010 Backup and Recovery

Microsoft SharePoint Server 2003 Backup and Recovery

Microsoft SharePoint Server 2007 Backup and Recovery

Microsoft SharePoint Server 2010 Backup and Recovery

NMM and Microsoft Office SharePoint Server 2010 farm

Windows Disaster Recovery with NetWorker 7.6 SP2 and NMM

The PowerSnap service must be restarted after the NetWorker service

NetWorker server............................................................................................ 261

SQL variable settings for Application Information attribute ......................................... 22

Configuration Options dialog box...................................................................................... 31

Newly created databases created in SharePoint .............................................................

This guide contains information for backing up and recovering Microsoft

Microsoft Active Directory

Microsoft Data Protection Manager

Microsoft Exchange 2003

Microsoft Exchange 2007

Microsoft Exchange 2010

Microsoft SharePoint 2003

Microsoft SharePoint 2007

Microsoft SharePoint 2010

EMC NetWorker software

EMC NetWorker snapshot management

Microsoft Volume Shadow Copy Service (VSS) technology

Storage subsystems, such as EMC CLARiiON or EMC Symmetrix, if used

The following EMC publications provide additional information:

EMC NetWorker Module for Microsoft Applications and EMC CLARiiON

EMC NetWorker Licensing Guide

EMC Information Protection Software Compatibility Guide

EMC Solutions Enabler Symmetrix CLI Quick Reference

EMC Technical Advisory (ETA) esg121813

EMC NetWorker Cloning Integration Guide

The NetWorker Procedure Generator

EMC NetWorker Release 7.6 Service Pack 1 documentation

EMC NetWorker Release 7.6 Service Pack 2 documentation

Note: EMC uses the following conventions for special notices:

Note: A note presents information that is important, but not hazard-related.

Used in running (nonprocedural) text for:

Used in running (nonprocedural) text for:

Where to get help

Used in all text (including procedures) for:

Used in procedures for:

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

EMC support, product, and licensing information can be obtained as follows.

Technical support For technical support, go to Powerlink and select Support. On

If you have issues, comments, or questions about specific information or procedures,

This chapter includes the following topics:

Microsoft SQL Server Backup and Recovery

Microsoft SQL Server Backup and Recovery