EMC Corporation Corporate Headquarters:
Hopkinton, MA 01748
-
9103 1-
508-
435-
1000 www.EMC.comModule for Microsoft Applications
Release 2.3
Application Guide
P/N 300-011-105 REV A03
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 3
Preface
Chapter 1 Microsoft SQL Server Backup and Recovery
Overview... 20
SQL Server versions supported by NMM... 20
Types of supported backup and recovery ... 21
Writers for SQL data backup and recovery ... 22
Performing SQL Server backups ... 22
SQL Server application information variable settings ... 23
Displaying valid SQL data save sets... 23
URL encoding for SQL save sets ... 24
Specifying save sets for SQL data ... 25
Configuring SQL Server backups... 25
Performing SQL Server recovery... 27
Recovering SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 data in a non-clustered environment from the SQLServerWriter save set ... 27
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 Express databases from the SYSTEM COMPONENTS save set ... 28
Recovering virtual SQL Server for SQL clusters... 28
Performing SQL Server directed recovery ... 28
Steps for SQL Server directed recovery... 29
Selecting the NetWorker server... 30
Selecting a source client ... 30
Selecting the desired SQL databases for directed recovery ... 32
Recover by using the default recover path ... 32
Recover by using a user-defined path ... 33
Examples of log messages in NMM log file and Monitor page... 34
Attaching the recovered SQL databases ... 35
Performing SQL Server disaster recovery... 36
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker version 7.6 SP2... 36
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker version 7.6 SP1 and earlier... 37
SQL Server (stand-alone) disaster recovery on Windows Server 2003 .... 37
Clustered SQL Server disaster recovery on Windows 2008, Windows 2008 R2, or Windows 7 with NetWorker 7.6 SP2... 37 Clustered SQL Server disaster recovery on Windows Server 2008,
2008 R2, or 2003 with NetWorker version 7.6 SP1 and earlier ... 38
Best practices... 39
Chapter 2 Microsoft Active Directory Backup and Recovery
Overview ... 42Types 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 ... 51
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 ... 60Types of supported backup and recovery... 60
Types of DPM data backed up by NMM... 61
DPM database backup writers ... 61
NMM commands required for DPM backup and recovery ... 62
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 ... 65
Specifying DPM save sets for application data ... 66
Configuring DPM backups... 67
Performing a DPM Server recovery ... 70
Performing DPM granular recovery... 72
Reviewing settings before starting recovery... 72
Recovering a folder or file from a DPM replica... 72
Performing a granular directed recovery to a DPM-protected server... 74
Performing DPM disaster recovery ... 75
Chapter 4 Microsoft Hyper-V Server Backup and Recovery
Overview ... 78Operating system versions supported by NMM client ... 78
Integration Components version ... 79
Hyper-V parent partitions, child partitions, and applications within child partitions... 79
Types of supported backup and recovery... 80
Hyper-V configuration... 80
Hyper-V storage configurations supported by NMM... 81
Hyper-V configuration requirements for backing up a child partition that contains multiple volumes... 84
Components used by NMM for Hyper-V backup and recovery ... 84
Performing Hyper-V backups ... 84
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 5
Hyper-V application information variable settings ... 85
Specifying Hyper-V save sets for application data... 85
Displaying valid Hyper-V save sets ... 85
NMM support for proxy backup of Hyper-V ... 86
Preparing a child partition for backup ... 86
Configuring Hyper-V backups ... 87
Configuring a Hyper-V client resource... 88
Performing Hyper-V recovery ... 90
Turning the child partition offline for recovery... 90
Hosting the recovered virtual systems... 91
Specifying the destinations for the Hyper-V configuration files and virtual system... 91
Selecting Hyper-V recovery options... 91
Selecting the destination of Hyper-V recovery... 92
Performing Hyper-V recovery to the original machine and location ... 92
Performing directed Hyper-V recovery to a different machine or location ... 93
Performing Hyper-V parent partition disaster recovery ... 95
Best practices ... 97
Hyper-V parent partition backup and recovery ... 97
Hyper-V child partition applications backup and recovery ... 98
Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 and 2008 R2 failover cluster ... 99
Chapter 5 Microsoft Exchange Server 2003 and 2007 Backup and Recovery
Overview... 102Exchange Server versions supported by NMM client ... 103
NMM and Exchange Server support for I18N ... 103
Microsoft Exchange Server 2007 MAPI client and Collaboration Data Objects support ... 103
Types of supported backup ... 103
Backup levels... 104
Types of supported recovery ... 104
Compatibility with previous Exchange Server backups ... 105
Creation of shadow copy and snapshot process in an Exchange Server production ... 105
Configuring snapshots... 105
LAN-based Exchange Server configuration with a storage area network and a proxy client ... 107
Exchange backup scenarios... 109
Exchange recovery scenarios ... 114
Exchange 2003 and 2007 writers... 116
Commands and attributes for Exchange backup and recovery ... 116
Configuring dedicated storage node for Exchange 2007 CCR environment ... 116
Performing Exchange Server backups... 117
Exchange 2003 and 2007 application information variable settings ... 117
Specifying Exchange 2003 and 2007 save sets for application data ... 119
Displaying valid Exchange data save sets ... 120
URL encoding for Exchange save sets... 121
Consistency check parameters to set threading and throttling for better backup performance ... 121
Configuring Exchange Server backups ... 122
Performing Exchange Server recovery... 134
Exchange recovery requirements ... 134
Exchange recovery options... 135
Configuring Exchange recovery ... 136
Selecting a storage group restore destination ... 150
Performing Exchange Server 2007 directed recovery ... 152
Performing a directed recovery ... 153
Performing Exchange Server 2007 disaster recovery... 154
Performing Exchange Server 2007 disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker version 7.6 SP2... 154
Performing Exchange Server 2007 disaster recovery on Windows 2008 or 2008 R2 with NetWorker version 7.6 SP1 or earlier ... 155
Performing a quick recovery of a deleted mailbox in Exchange 2007... 159
Best practices... 160
Exchange recovery limitations ... 161
Chapter 6 Microsoft Exchange Server 2010 Backup and Recovery
Overview ... 164Supported operating systems... 164
Types of backup and recovery ... 165
Exchange 2010 VSS writers... 165
LAN-based Exchange Server configuration with a storage area network and a proxy client... 165
Backup initiated transaction log file truncation ... 166
Microsoft Exchange Server 2010 MAPI client and Collaboration Data Objects version 1.2.1 for granular recovery in Exchange 2010... 166
Performing Exchange 2010 backups... 166
Backup options ... 167
Specifying Exchange 2010 application data save sets... 167
Displaying save set syntax... 168
URL encoding for SharePoint save sets ... 168
Exchange 2010 application information variable settings... 169
Configuring persistent and non-persistent snapshots... 170
Considerations for backing up Exchange 2010 in non-DAG and DAG environment... 171
Exchange 2010 incremental backup promoted to full backup ... 171
Configuring Exchange Server 2010 backups... 172
Configuring Avamar deduplication backups in a DAG environment... 174
Verifying backups ... 175
Performing Exchange Server 2010 recovery... 175
Performing full recovery... 175
Performing advanced recovery... 175
Performing granular recovery of Mailbox, folder, or e-mail ... 180
Performing a quick recovery of a deleted Mailbox in Exchange 2010... 181
Microsoft Exchange Server 2010 disaster recovery ... 181
Chapter 7 Microsoft SharePoint Server 2003 Backup and Recovery
Overview ... 184Microsoft SharePoint Portal Server 2003 and Windows SharePoint Services 2.0 ... 184
Types of supported backup ... 184
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 7
Writer required for SharePoint Server 2003 backup ... 184
Performing SharePoint Server 2003 backups... 185
Performing SharePoint Server 2003 recovery ... 185
Example of SharePoint Server 2003 backup and recovery process ... 186
Creating a new SharePoint portal with three new databases ... 186
Viewing the location and hierarchy of databases in the SQL Enterprise Manager GUI ... 187
Configuring and performing a backup of the new databases with NMM save sets... 187
Verifying the backup in NMM UI... 187
Deleting the new databases... 188
Performing NMM recovery ... 188
Verifying database recovery through the SQL Enterprise Manager ... 188
Recovering the portal site through SharePoint Portal Server Central Administration... 189
Verifying the recovery of the portal site in SharePoint Server Central Administration... 192
Chapter 8 Microsoft SharePoint Server 2007 Backup and Recovery
Overview... 194NMM solutions for protecting a SharePoint 2007 farm ... 194
Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0... 196
Types of SharePoint Server 2007 backup and recovery ... 196
Backup and recovery levels ... 196
Microsoft Office SharePoint 2007 farm configurations ... 197
SharePoint Server 2007 writers... 201
Performing SharePoint Server 2007 backups... 202
SharePoint Server 2007 application information variable settings ... 202
Specifying SharePoint Server 2007 save sets for application data... 203
Displaying valid SharePoint Server 2007 data save sets... 203
URL encoding for SharePoint save sets... 204
Configuring dedicated web front-end crawling ... 204
Configuring SharePoint Server 2007 backups... 204
Performing SharePoint Server 2007 farm hardware backups ... 209
CLARiiON hardware provider ... 210
Symmetrix hardware provider ... 211
Performing SharePoint Server 2007 recovery ... 212
Full recovery of a stand-alone SharePoint farm... 213
Full recovery of a distributed SharePoint farm... 213
Recovery of individual SharePoint Server content databases ... 214
Recovery of SharePoint Search and Content Indexes ... 215
Performing SharePoint Server 2007 disaster recovery ... 216
Performing SharePoint Server 2007 disaster recovery with NetWorker 7.6 SP1 and earlier ... 216
Performing SharePoint Server 2007 disaster recovery with NetWorker 7.6 SP2 or later... 217
Keeping backups and recoveries in sync ... 217
Best practices ... 218
Backing up SharePoint database by using NMM and NMSQL... 219
Chapter 9 Microsoft SharePoint Server 2010 Backup and Recovery
Overview ... 222
New features in Microsoft SharePoint Server 2010... 222
SharePoint Server 2010 support on Windows Server 2008... 223
Types of SharePoint Server 2010 backup and recovery ... 223
NMM and Microsoft Office SharePoint Server 2010 farm configurations... 223
SharePoint Server 2010 VSS writers ... 224
Performing SharePoint Server 2010 backups ... 224
Specifying SharePoint Server 2010 application data save sets ... 224
Displaying valid SharePoint Server 2010 data save sets ... 225
Performing SharePoint Server 2010 backup... 226
Configuring client resources ... 226
Performing SharePoint Server 2010 recovery ... 227
Performing SharePoint Server 2010 full farm recovery... 227
Performing SharePoint Server 2010 web application recovery... 227
Performing SharePoint Server 2010 disaster recovery... 229
Chapter 10 Windows Disaster Recovery with NetWorker 7.6 SP2 and NMM
Overview ... 232Changes in NetWorker 7.6 SP2 client functionality when NMM 2.3 is installed... 233
Changes in NetWorker 7.6 SP2 client functionality when NMM 2.3 is uninstalled... 234
Performing Windows Disaster Recovery backup and recovery for Microsoft applications ... 234
Performing a Windows DR backup ... 234
Performing a Windows DR recovery ... 235
Chapter 11 Troubleshooting
About the troubleshooting process... 238Setting up notifications ... 239
Finding errors ... 239
NMM Config Checker 1.1.0 ... 239
NMM client error messages... 240
E_VOLUME_NOT_SUPPORTED ... 240
E_VETO_PROVIDER ... 240
VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 ... 241
VSS CLIENT... Invalid Writer Selection... for APPLICATIONS ... 241
Savegroup failed in scheduled backup... 242
Insufficient permission to access mailbox. See documentation for required permission settings. Server MBX is not capable of RSG operations... 242
77108:nsrsnap_vss_save ... 243
NMM validation for NPS writer failed, unable to restore NPS VSS writer data ... 243
NMM client issues... 243
In-progress backup fails... 245
NetWorker is blocked by Windows firewall ... 245
NMM backups might fail where a firewall exists between the NetWorker server and client ... 245
Need to run utility to obtain Exchange server information... 246 Requesting a snapshot for a volume on hardware that is not
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 9
transportable ... 246
The PowerSnap service must be restarted after the NetWorker service is restarted ... 247
PowerSnap validation for recovery fails ... 247
Snapshot backup may fail with writer errors... 248
Microsoft I/O write error when taking a replica in a CLARiiON array... 248
Creating a replica takes a long time in CLARiiON environment... 248
Cannot recover Exchange database due to overwrite prevention error ... 248
Incremental backups may be promoted to full backups ... 249
Diagnosing VSS writer issues ... 250
Modifying the Exchange 2007 or 2010 COM+ component’s user account or password ... 250
Save sets may not appear in the Recover page ... 251
Recovery of AES-encrypted files fails without passphrase... 251
Unable to restore files encrypted with both Microsoft Windows Encrypting File System and AES encryption ... 251
Antivirus programs block recovery... 251
Snapshot cannot include both hardware and software snapshot volumes for clustered NetWorker VSS clients ... 252
Cross-platform directed recovery operations are not supported on NMM ... 252
Recovery of large number of items fails if one or more items in a folder is not selected... 253
Multiple client resources with the same name cannot be combined in the same group ... 253
Backup of two partitions of the same CLARiiON disk fails ... 253
Connection to DPM service lost during DPM recovery ... 253
DPM replica backup is not correctly configured ... 253
Backup fails if Exchange server in is renamed after it is created ... 254
In Exchange 2010, recovery fails for renamed mailbox database, however backup completed successfully for renamed database ... 255
In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of new database name after renamed mailbox database ... 255
Save sets from an Avamar AFTD for NMM backups show retention set to 1/18/2038... 255
Microsoft updates required to fix the vds.exe crash errors during retention on Windows 2008 and Windows 2003 ... 256
Back up of SYSTEM COMPONENTS fails due to missing System Writer... 256
Problems with RMExchangeInterface component ... 257
SharePoint backup fails when host and proxy client do not match... 257
NMM installation issues ... 258
RMAgentPS fails to uninstall when uninstalling NMM... 258
Recovery failure after .NET 3.5 framework installation ... 259
SYSTEM COMPONENTS failure after McAfee uninstall ... 260
If Exchange is installed after NMM, NMM reinstallation is required to get Replication Manager Exchange Interface... 260
NMM uninstall and reinstall required to change the Replication Manager port number... 260
Checking log files... 260
NMM client... 261
PowerSnap client ... 261
Replication Manager ... 261
EMC VSS provider... 262
Active Directory ... 262
NetWorker server... 262
Manually stopping and starting services... 263
Using nsr.dir to skip files for NMM backup and recovery ... 264
Troubleshooting issues during SQL databases directed recovery ... 264
Name resolution ... 264
Other troubleshooting resources... 264
Glossary
Index
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 11
Title Page
1 Writers used by NMM for SQL data backup and recovery... 22
2 SQL variable settings for Application Information attribute ... 23
3 Special characters and their URL-encoded values ... 24
4 SQL save set syntax... 25
5 Tasks for scheduling a backup ... 26
6 Best practices and considerations ... 39
7 Tasks for Active Directory or ADAM granular backup ... 46
8 System-only attributes that are not backed up ... 54
9 Retained attributes after object is deleted... 54
10 DPM application information variable settings ... 65
11 DPM Server 2007 save set syntax... 66
12 Special characters and their URL-encoded values ... 67
13 Tasks for scheduling a backup ... 67
14 Hyper-V child partition configurations ... 82
15 NMM Hyper-V components ... 84
16 Hyper-V application information variable settings ... 85
17 Hyper-V save set syntax... 85
18 Backup tasks for Hyper-V... 87
19 Exchange 2003 and 2007 backup levels... 104
20 Writers used by NMM for Exchange Server backup and recovery... 116
21 Commands and attributes used by NMM for Exchange Server backup and recovery 116 22 Exchange application information variable settings... 117
23 Exchange 2003 and 2007 save set names... 119
24 Tasks for configuring an Exchange Server backup ... 122
25 Different backup procedures for Exchange recovery ... 125
26 Exchange 2010 VSS writers ... 165
27 Exchange 2010 save sets for application data ... 168
28 Exchange application information variable settings... 169
29 Considerations required for backup in non-DAG and DAG environment... 171
30 Tasks for configuring an Exchange Server backup ... 172
31 List of supported SharePoint writers ... 184
32 Example: Minimum required save sets to be backed up ... 201
33 List of supported SharePoint Server 2007 writers ... 201
34 SharePoint Server application information variable settings ... 202
35 SharePoint Server save set syntax... 203
36 Tasks for SharePoint Server 2007 backups ... 205
37 SharePoint Server backup list for disaster recovery ... 216
38 List of supported SharePoint Server 2010 VSS writers... 224
39 SharePoint Server 2010 save set syntax... 225
40 Supported and unsupported system recovery scenarios ... 234 41 Notifications and errors... 239 42 Services and processes used in NMM client... 263
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 13
Title Page
1 Configuration Options dialog box... 31
2 Client menu... 31
3 APPLICATIONS > SqlServerWriter tree nodes... 32
4 System Recover Session Options ... 33
5 NMM Data Protection Manager commands... 62
6 NMM protection of DPM... 63
7 Directed recovery of FileServer1... 64
8 DPM disaster recovery options... 70
9 DPM recovery modes ... 72
10 Recover submenu for DPM recovery ... 73
11 DPM granular recovery available to file level ... 73
12 DPM granular recovery options ... 73
13 DPM database and replicas available as selectable items ... 75
14 Windows Server 2008 or Windows Server 2008 R2 host with Hyper-V child partitions 80 15 NMM backup of Hyper-V components ... 81
16 Hyper-V storage options... 82
17 Disaster recovery order for a Hyper-V Server ... 96
18 Snapshot process with Exchange production server and proxy client ... 108
19 Multiple server roles that coexist on a single computer... 110
20 SCC architecture... 111
21 CCR core architecture... 112
22 Exchange Recovery Options window with Conventional Restore option selected 136 23 Available and unavailable storage groups... 143
24 Restore To command on context menu ... 143
25 RSG Configuration error message ... 144
26 RSG Configuration correct message... 144
27 Public folders cannot be recovered to an RSG ... 144
28 Selected and partially selected items... 147
29 Recovered Items folders in user mailbox ... 148
30 Select Storage Group Restore Destination dialog box ... 151
31 Local client on the taskbar next to Client... 153
32 Select Viewable Clients dialog box... 153
33 Select Exchange 2010 database... 176
34 Advanced Recovery dialog box ... 177
35 Manage RDB window ... 177
36 Create_DB window... 178
37 Exchange Recovery Summary... 179
38 Select Database window ... 179
39 Select Mailbox, folder or e-mail for recovery ... 181
40 Newly created databases created in SharePoint ... 187
41 NMM backups available for recovery ... 188
42 SQL databases selected for recovery in NMM ... 188
43 Databases recovered to SQL Server ... 189
44 SharePoint Server Central Administration page ... 189
45 SharePoint Portal Server Central Administration, Manage Portal Sites window ... 190
46 Portal creation and restore options ... 190
47 Portal restore and database names ... 191
48 Confirmation window to request creation of the portal site... 191
49 Status window for portal recovery process ... 191
50 Operation Successful page displayed when portal recovery is complete... 192
51 Recovered databases and SharePoint portal visible and available in SharePoint 192 52 SharePoint Server 2007 stand-alone farm configuration ... 197
53 SharePoint Server 2007 distributed farm configuration ... 198
54 Dialog box to recover remote components ... 214
55 Troubleshooting process... 238
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 15
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 like SQL, SharePoint, Exchange, Active Directory, Hyper-V, and Data Protection Manager by using EMC NetWorker Module for Microsoft Applications.
IMPORTANT
The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide supplements the NetWorker Module for Microsoft Application backup and recovery procedures described in this guide and must be referred to when
performing application specific tasks in this guide. Ensure to download a copy of the EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide from the EMC Powerlink website http://Powerlink.EMC.com before using this guide.
Audience This guide is part of the EMC NetWorker Module for Microsoft Applications
documentation set, and is intended for use by system administrators during the setup and maintenance of the product.
Readers should be familiar with the following technologies used in backup and recovery:
◆ Storage subsystems, such as EMC CLARiiON or Symmetrix, if used
◆ EMC NetWorker software
◆ EMC NetWorker Snapshot management
◆ Microsoft Volume Shadow Copy Service (VSS) technology
Related documentation
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 Conventions used in
this document
Note: EMC uses the following conventions for special notices:
Note: A note presents information that is important, but not hazard-related.
IMPORTANT
An important notice contains information essential to software or hardware operation.
Typographical conventions
EMC uses the following type style conventions in this document.
Normal Used in running (nonprocedural) text for:
• Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus)
• Names of resources, attributes, pools, Boolean expressions, buttons, DQL statements, keywords, clauses, environment variables, functions, utilities
• URLs, pathnames, filenames, directory names, computer names, filenames, links, groups, service keys, file systems, notifications
Bold Used in running (nonprocedural) text for:
• Names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, man pages Used in procedures for:
• Names of interface elements (such as names of windows, dialog boxes, buttons, fields, and menus)
• What user specifically selects, clicks, presses, or types Italic Used in all text (including procedures) for:
• Full titles of publications referenced in text
• Emphasis (for example a new term)
• Variables
EMC NetWorker Module for Microsoft Applications Release 2.3 Application Guide 17
Where to get help EMC support, product, and licensing information can be obtained as follows.
Product information —For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:
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:
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.
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
Microsoft SQL Server Backup and Recovery 19
This chapter includes the following topics:
◆ Overview ... 20
◆ Performing SQL Server backups... 22
◆ Performing SQL Server recovery ... 27
◆ Performing SQL Server directed recovery... 28
◆ Performing SQL Server disaster recovery ... 36
◆ Best practices... 39
Microsoft SQL Server
Backup and Recovery
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
◆ “Writers 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 Microsoft SQL Server:
◆ SQL Server 2008 R2 (x86, x64):
• Standard
• Enterprise
Note: It is recommended that you use Cumulative Update 4.
◆ SQL Server 2008 SP2 (x86, x64):
• Standard
• Enterprise
◆ SQL Server 2005 (x86, x64) Service Pack 4:
• Standard
• Enterprise
◆ SQL Server 2008 R2 Express edition
◆ SQL Server 2008 Express edition
◆ SQL Server 2005 Express edition
Note: NMM only supports databases in SQL simple recovery mode.
NMM client does not support the following:
◆ SQL Server running on IA64
◆ SQL Server 2000
Overview 21
Types of supported backup and recovery
NMM provides support for the following types of backup:
◆ Snapshot backup, which includes back up of data at that point-in-time.
◆ Full backup for SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2, which includes backup of:
• Default instance and Named instances of SQL sever
• Database level backup
• Writer level backup
• Databases with TDE encryption and file stream for SQL Server 2008 and SQL Server 2008 R2
• Databases with file groups for SQL Server 2005, SQL Server 2008 and SQL Server 2008 R2
“Performing SQL Server backups” on page 22 provides details.
Note: NMM 2.3 does not support:
— SQL log backups for either SQL 2005, SQL 2008, and SQL 2008 R2.
— Incremental backups for SQL application.
— Individual file groups and files backup and recovery.
NMM provides the following types of recovery:
◆ Full recovery of SQL Server 2005, SQL 2008, and SQL 2008 R2 databases, which includes recovery of:
• Recovery of databases with TDE encryption and file stream for SQL 2008 and SQL 2008 R2
• Recovery of databases having file groups for SQL 2005, SQL 2008 and SQL 2008 R2
◆ 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.
Writers for SQL data backup and recovery
Table 1 on page 22 lists the writers used by NMM to back up SQL data.
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 23
◆ “Displaying valid SQL data save sets” on page 23
◆ “URL encoding for SQL save sets” on page 24
◆ “Specifying save sets for SQL data” on page 25
◆ “Configuring SQL Server backups” on page 25 Table 1 Writers used by NMM for SQL data backup and recovery
Writers Description
SqlServerWriter NMM uses the VSS writer for SQL Server 2005, SQL Server 2008, SQL Server 2008 R2.
Performing SQL Server backups 23
SQL Server application information variable settings
Table 2 on page 23 lists the variables that can be specified in the Application Information attribute of the client resource.
Displaying valid SQL data save sets
To display a list of the SQL save sets that are available for backup:
1. Open a command prompt on the application server.
2. Ensure that the SQL Server VSS Writer service is enabled and running.
3. From the command prompt, type the following command to list the valid 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.
Table 2 SQL variable settings for Application Information attribute
Attribute name Description Values
NSR_SNAP_TYPE=value Specifies the snapshot service provider name. vss
This value is required.
NSR_DATA_MOVER=value application information attribute
Specifies the hostname of the NMM client that mounts the snapshot from NMM client to the proxy host. The host can be either a local host or a proxy client host.
Note: This attribute is required for hardware provider backups that are configured to use data mover.
• The local host
• The proxy client hostname Consider the following:
• If no value is typed, the local host is used as the data mover.
• If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the client resource.
• For serverless backups, specify a proxy client.
URL encoding for SQL 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.
◆ 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 3 on page 24 lists the most commonly used special characters and their URL values.
Table 3 Special characters and their URL-encoded values
Special character URL-encoded value Special character URL-encoded value
\ %5C ? %3F
/ %2F ] %5D
" %22 [ %5B
% %25 } %7D
# %23 { %7B
& %26 ^ %5E
< %3C ‘ %60
> %3E | %7C
Performing SQL Server backups 25
Specifying save sets for SQL data
Specify SQL data save sets in the Save Set attribute of a client resource.
Table 4 on page 25 lists the SQL save set syntax for the supported types of SQL data.
IMPORTANT
nsrsnap_vss_save -? does not list APPLICATIONS:\SqlServerWriter as a save set if only SQL Express is installed. The SQL 2005, SQL 2008, and SQL 2008 R2 Express edition databases are backed up from SYSTEM COMPONENTS:\ save set.
Configuring SQL Server backups
To perform a full backup of SQL Server, complete the tasks outlined in Table 5 on page 26.
Table 4 SQL save set syntax
Type of data to back up Save set syntax
Default instance and Named-instances APPLICATIONS:\SqlServerWriter
Note: Ensure that the SQL Server VSS Writer service is started before using this save set.
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: Some special characters in a SQL Server named instance or database name must be replaced with their URL-encoded values. “URL encoding for SQL save sets” on page 24 provides more information about URL encoding.
IMPORTANT
The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details for the first four tasks in Table 5 on page 26.
Configure a SQL Server client resource
To configure a SQL server client resource:
1. In the Administration page of the NetWorker Management Console, click Configuration.
2. In the expanded left pane, select Clients.
3. From the File menu, select New.
4. In the Name attribute, type the hostname, that is the fully qualified name, of the NetWorker client computer.
Note: If backing up a SQL clustered instance, use the virtual SQL Server name here. Create client resources for all physical cluster nodes where the SQL clustered instance is run.
5. In the Comment attribute, type a description.
Note: If you are creating multiple client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource.
6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access.
7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly.
8. In the Scheduled Backups attribute, specify the save set name.
For example, to back up Default instance and Named-instances together for SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2, specify the save set name:
APPLICATIONS:\SqlServerWriter Table 5 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.
Performing SQL Server recovery 27
Table 4 on page 25 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 SQL save sets” on page 24.
9. Specify SQL application variable settings in the Application information attribute of the client resource. These settings are described in Table 2 on page 23.
10. Click the Globals (1 of 2) tab.
11. In the Aliases attribute, check that the NETBIOS and FQDN names 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 SQL Server 2005, SQL Server 2008, and SQL Server 2008 R2 Express databases. Review the sections that are applicable for your setup:
◆ “Recovering SQL Server 2005, SQL Server 2008, 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, SQL Server 2008 R2 data in a non-clustered environment from the SQLServerWriter save set
During the system databases recovery, NMM automatically detects and stops the SQL Server services for the SQL database instances. After the system databases recovery is complete, NMM automatically starts the SQL Server services for the SQL Server database instances.
When user databases are recovered, the SQL Server services are not stopped or started.
To recover SQL Server 2005, SQL Server 2008, and 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.
Recovering SQL Server 2005, SQL Server 2008, or SQL Server 2008 R2 Express databases from the SYSTEM COMPONENTS save set
To recover SQL Server Express databases that were backed up to the SYSTEM COMPONENTS save set:
1. If restoring the master database, stop the SQL Server services for the SQL Server database instances.
2. From the navigation tree, expand the SYSTEM COMPONENTS:\ folder.
3. In the Recovery Options dialog box, clear the option Use Microsoft Best Practices for selecting the System State.
4. Under System Components, browse the writer SQL Embedded and select the required databases for restore.
5. From the System Recover Session toolbar, click Start Restore.
6. After the recovery is complete, start the SQL Server services for the SQL database instances.
Recovering virtual SQL Server for SQL clusters
Note: This procedure is common to all supported SQL versions and Windows platforms.
For instance level recovery on SQL Server cluster, perform the following steps:
1. Using Windows Cluster Management console, make the SQL Server resource under the Cluster Group of SQL Server, offline.
Now the instance is down but the disk is available because the group is up.
2. Perform SQL writer recovery.
Note: When performing SQL writer recovery, manually stop and start of the services.
3. In the Cluster Management console, make the SQL Server resource online.
Ensure that all the other SQL resources that depend on that SQL Server are online.
Performing SQL Server directed recovery
The directed recovery procedure does not use SQL Writer. A restore performed without using SQL Writer guarantees a crash-consistent database, which means that there are no torn or corrupted pages. However, all transactions which were in progress at the time of the snapshot are rolled back. 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 done on a Windows 2003 machine, then the directed recover can be done only to another Windows 2003 machine. All the database files must be recovered to a single drive.
Before performing SQL directed recovery, ensure that:
◆ There are two client machines on the same platform. Where:
• One client is the source machine on which the backup is performed.
Performing SQL Server directed recovery 29
• The other client is the target machine to which recovery is performed. There is no need to install SQL Server 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 is not allowed from SQL system databases.
◆ Directed recovery of filestream database is not supported.
◆ Directed recovery of TDE Encryption database is not supported.
◆ Directed recovery on cross-platform is not supported.
For examples, directed recovery of SQL databases on Windows 2003 cannot be recovered on Windows 2008 and vice versa.
◆ Alternate recovery on the same or separate location is not supported.
◆ Directed recovery to encrypted target is not supported.
◆ Directed recovery to compressed drive is not supported. Although recovery takes place, the database attachment fails.
◆ SQL Data Protection Manager (DPM) directed recovery is not supported.
◆ Directed recovery of SQL express is not supported.
◆ No validation available for restore target paths clustered paths.
When a path is selected, the NMM GUI does not validate if the path is valid. The path validation is done only after recovery is started.
Steps for SQL Server directed recovery
Toperform 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.
5. Recover the SQL databases:
• To the default recovery path, as described in “Recover by using the default recover path” on page 32.
or
• To a user-defined location from the SQL tab, as described in “Recover by using 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 drive or different drive.
b. Use the SQL Management Studio program to manually attach the .mdf and the .ldf files from the respective locations.
“Attaching the recovered SQL databases” on page 35 provides details.
For multiple NMM directed recovery on same recovery farm, use the same procedure for each of the source clients. 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 the Configure Options to add the source client machine to the list of client machines that you can browse.
The Configuration Options dialog box as shown in Figure 1 on page 31 appears.
Performing SQL Server directed recovery 31 Figure 1 Configuration Options dialog box
2. Click the button next to the Client Name field.
The Select Viewable Clients dialog box appears.
3. Select the backed up SQL client from the Selected clients on:
a. List and click Add >> to add the selected client to the list of clients in the Client to list on menu bar: list.
b. Click OK.
The Client menu in the NMM GUI displays the list of selected clients that you can browse.
4. Select the desired SQL client in the Client menu. Figure 2 on page 31 shows the Client menu.
Figure 2 Client menu
5. Select the desired SQL Server for directed recovery as described in “Selecting the desired SQL databases for directed recovery” on page 32.
Selecting the desired SQL databases for directed recovery
To select the desired SQL databases for directed recovery:
1. After the application reloads the current browse tree, ensure that the System Recover Session option is selected.
The Microsoft SQL Server application backups are now displayed for directed recover browsing in the current browse tree.
2. Expand the APPLICATIONS > SqlServerWriter tree nodes as shown in Figure 3 on page 32.
Figure 3 APPLICATIONS > SqlServerWriter tree nodes 3. Select the desired databases.
Note: The SQL system databases are not supported for SQL directed recovery. It is recommended to do directed recovery of one database at a time.
4. Recover the SQL databases:
• To the default recover path, as described in “Recover by using the default recover path” on page 32.
or
• To an user-defined location from the SQL tab, as described in “Recover by using a user-defined path” on page 33.
Recover by using the default recover path
To recover SQL databases by using the default recover path:
1. Select the database to be recovered using directed recovery in System recover Session.
2. Click Recover.
The System Recover Summary dialog box appears.
3. Click Recover Option.
Performing SQL Server directed recovery 33
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 initiate the directed recover.
8. Switch to the Monitor page to view the status and progress of the recover.
Recover by using a user-defined path
To recover SQL databases by using an user-defined path:
1. Select the target database by using directed recovery in System Recover Session.
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.
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 Networker tab because that will lead to recovery failure.
Examples of log messages in NMM log file and Monitor page
Examples of messages for SQL directed recover in both the NMM log file and the UI Monitor page.
Case 1: Restore to original location messages in NMM log Command line:\n C:\Program
Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A
RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A NSR_SQL_TARGET_ORIG=yes -I -
nsrsnap_vss_recover: flag=A arg=NSR_SQL_RECOVER_MODE=alt_location nsrsnap_vss_recover: flag=A arg=NSR_SQL_TARGET_ORIG=yes
NMM .. Performing SQL directed restore.
NMM .. SQL directed restore will relocate database files to their original locations.
Case 2: Restore to alternate location messages in NMM log Command line:\n C:\Program
Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A
RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A NSR_SQL_TARGET_DIR=E:\ -I -
nsrsnap_vss_recover: flag=A arg=NSR_SQL_RECOVER_MODE=alt_location nsrsnap_vss_recover: flag=A arg=NSR_SQL_TARGET_DIR=E:\
NMM .. Performing SQL directed restore.
NMM .. SQL directed restore will relocate database files to path[E:\].
NMM .. SQL directed restore relocating database files for database [APPLICATIONS:\SqlServerWriter\MB-CLNT-3\AcmeBank].
NMM .. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf] to [E:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf].
NMM .. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf] to [E:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf].
NMM .. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf] to [E:\Program Files\Microsoft SQL
Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf].
Performing SQL Server directed recovery 35
Attaching the recovered SQL databases
To manually attach the recovered SQL databases:
1. Start the SQL Management Studio.
2. Start attachment of SQL database from the SQL Management Studio.
3. In the SQL Attach Database dialog box:
a. Locate the primary data file to attach. SQL restores all primary database files (.mdf), logs files (.ldf), and secondary database files (.ndf), if present.
b. The SQL administrator must know which files are the primary data files.
c. Once the primary data file is attached, SQL automatically identifies the other database files, provided the files are all at the same location.
d. If the files are not in the same location, then you must specify the respective locations of the restored files:
– .mdf – .ldf – .ndf
4. Click OK to create the database.
The database is now created and available.
Performing SQL Server disaster recovery
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 25 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:
APPLICATIONS:\SqlServerWriter
Note: You must specify a separate applications save set for each SQL cluster instance when backing up SQL Server cluster.
The following are scenarios and procedures for recovery:
◆ “SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker version 7.6 SP2” on page 36
◆ “SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker version 7.6 SP1 and earlier” on page 37
◆ “SQL Server (stand-alone) disaster recovery on Windows Server 2003” on page 37
◆ “Clustered SQL Server disaster recovery on Windows 2008, Windows 2008 R2, or Windows 7 with NetWorker 7.6 SP2” on page 37
◆ “Clustered SQL Server disaster recovery on Windows Server 2008, 2008 R2, or 2003 with NetWorker version 7.6 SP1 and earlier” on page 38
SQL Server (stand-alone) 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 SQL Server (stand-alone) data.
“Performing Windows Disaster Recovery backup and recovery for Microsoft applications” on page 234 provides details.
Performing SQL Server disaster recovery 37
SQL Server (stand-alone) disaster recovery on Windows Server 2008 or 2008 R2 with NetWorker version 7.6 SP1 and earlier
If you have installed NetWorker 7.6 SP1 and earlier with NMM on Windows 2008 and 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
To perform a SQL Server (stand-alone) disaster recovery on Windows Server 2003:
1. Set up a new Windows 2003 machine, such 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. Reboot the machine.
4. Log in to the machine as local administrator.
5. Unjoin the domain, and then rejoin the domain.
6. Recover the APPLICATIONS:\SqlServerWriter save set.
Clustered SQL Server disaster recovery on Windows 2008, Windows 2008 R2, or Windows 7 with NetWorker 7.6 SP2
If you have installed NetWorker 7.6 SP2 with NMM on Windows 2008, Windows 2008 R2, or Windows 7, 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 Failover Cluster on Windows 2008 SP2.
◆ NMM 2.3 is used to protect the SQL Server.
◆ Node and 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.
2. Perform an instance level backup of the virtual SQL Server by using NMM 2.3.
“Configuring SQL Server backups” on page 25 provides details.
3. Perform a Windows Disaster Recovery backup for Node A. “Performing
Windows Disaster Recovery backup and recovery for Microsoft applications” on page 234 provides details
4. Perform a Windows Disaster Recovery backup for Node B. “Performing
Windows Disaster Recovery backup and recovery for Microsoft applications” on page 234 provides details.
To recover a clustered SQL Server in this example:
1. Perform a Windows Disaster Recovery on Node A first and then on Node B.
“Performing Windows Disaster Recovery backup and recovery for Microsoft applications” on page 234 provides details.
Note: The Failover Cluster should be up and running.
If the host is a virtual machine, first create a new virtual machine with the same configuration as used before the disaster, and then perform the Windows Disaster Recovery operation.
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 NMM UI, and recover system databases.
6. After system databases are restored, recover user-defined databases.
Clustered SQL Server disaster recovery on Windows Server 2008, 2008 R2, or 2003 with NetWorker version 7.6 SP1 and earlier
If you have installed NetWorker 7.6 SP1 and earlier with NMM on Windows 2008, Windows 2008 R2 or Windows 2003, perform the following steps:
1. Set up each new cluster machine, such that its parameters match with those of the corresponding old machine:
• Machine name
• IP address
• Domain name
