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

(1)

EMC Corporation Corporate Headquarters:

Hopkinton, MA 01748

-

9103 1

-

508

-

435

-

1000 www.EMC.com

Module for Microsoft Applications

Release 2.3

Application Guide

P/N 300-011-105 REV A02

(2)

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.

(3)

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

Commands used by NMM 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 stand-alone databases 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 SQL instance for SQL clusters... 28

Performing SQL server directed recovery to an alternate location ... 29

Steps for SQL server directed recovery... 29

Selecting the NetWorker server... 30

Selecting a client... 30

Selecting the desired SQL databases for directed recovery ... 32

Recover by using the default recover path ... 32

Recover by using an alternate recover 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 ... 35

SQL server (stand-alone) disaster recovery on Windows server 2008 ... 36

SQL server (stand-alone) disaster recovery on Windows server 2003 ... 36

SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003 ... 37

Best practices ... 38

(4)

Chapter 2 Microsoft Active Directory Backup and Recovery

Overview ... 40

Types of supported backup and recovery... 40

Specifying save sets for scheduled backups ... 41

Performing an Active Directory or ADAM full backup... 41

Performing Active Directory or ADAM granular backup ... 42

Considerations for granular backup ... 42

Configuring Active Directory or ADAM granular backups ... 43

Performing an all Active Directory data recovery ... 50

Performing an Active Directory granular recovery ... 51

Recovery restrictions for Active Directory... 51

Recovering an Active Directory object or object attribute ... 53

Selecting Active Directory object attributes ... 54

Performing Active Directory disaster recovery ... 55

Chapter 3 Microsoft Data Protection Manager Backup and Recovery

Overview ... 58

NMM and DPM scenario ... 58

Types of DPM data backed up by NMM... 60

DPM backup writers... 60

NMM commands required for DPM backup and recovery ... 61

Performing DPM server backups ... 61

DPM application information variable settings ... 62

Displaying valid DPM data save sets ... 62

Specifying DPM save sets for application data ... 63

Configuring DPM backups... 64

Performing a granular recovery of DPM objects ... 67

Recovering a folder or file from a DPM replica... 67

Reviewing settings before starting recovery... 69

Performing a granular directed recovery to a DPM-protected server... 69

DPM directed granular recovery scenario ... 70

Performing a directed granular recovery ... 71

Performing DPM writer disaster recovery ... 72

Chapter 4 Microsoft Hyper-V 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

Components used by NMM for Hyper-V backup and recovery ... 82

Performing Hyper-V backups ... 82

Hyper-V application information variable settings ... 83

Specifying Hyper-V save sets for application data ... 83

Displaying valid Hyper-V save sets... 83

NMM support for proxy backup of Hyper-V... 84

Preparing a child partition for backup ... 84

(5)

Configuring Hyper-V backups ... 85

Configuring a Hyper-V client resource... 86

Performing Hyper-V recovery ... 88

Turning the child partition offline for recovery... 88

Hosting the recovered virtual systems... 88

Specifying the destinations for the Hyper-V configuration files and virtual system ... 89

Selecting Hyper-V recovery options... 89

Selecting the destination of Hyper-V recovery... 90

Performing Hyper-V recovery to the original machine and location ... 90

Performing directed Hyper-V recovery to a different machine or location ... 91

Performing Hyper-V parent partition disaster recovery ... 93

Best practices ... 95

Hyper-V parent partition backup and recovery ... 95

Hyper-V child partition applications backup and recovery ... 96

Restrictions for backup and recover of Hyper-V child partitions in a Windows 2008 failover cluster... 97

Chapter 5 Microsoft Exchange Server Backup and Recovery

Overview... 100

Microsoft Exchange server 2007 MAPI client and Collaboration Data Objects support... 100

Exchange server versions supported by NMM client... 101

NMM and Exchange server support for I18N... 101

Types of supported backup ... 101

Backup levels... 102

Types of supported recovery ... 102

Compatibility with previous Exchange server backups... 103

Creation of shadow copy and snapshot process in an Exchange server production ... 103

LAN-based Exchange server configuration with a storage area network and a proxy client ... 104

Exchange backup scenarios... 105

Exchange recovery scenarios ... 110

Exchange 2003 and 2007 writers... 111

Commands and attributes for Exchange backup and recovery ... 112

Configuring dedicated storage node for Exchange 2007 CCR environment ... 112

Performing Exchange server backups ... 113

Exchange 2003 and 2007 application information variable settings ... 113

Specifying Exchange 2003 and 2007 save sets for application data ... 115

Displaying valid Exchange data save sets ... 116

Configuring persistent snapshots ... 117

Configuring Exchange server backups... 119

Configuring Exchange backup schedule... 120

Configuring Exchange client resource ... 121

Performing Exchange server recovery... 131

Exchange recovery requirements ... 131

Exchange recovery options ... 132

Configuring Exchange recovery... 133

Selecting a storage group restore destination... 147

(6)

Performing Microsoft Exchange server 2007 directed recovery... 149

Performing a directed recovery ... 150

Performing Microsoft Exchange server 2007 disaster recovery ... 151

Performing Microsoft Exchange server 2007 (stand-alone) disaster recovery ... 151

Performing Microsoft Exchange server 2007 disaster recovery for Microsoft Exchange CCR to a two-node cluster in a production environment... 152

Performing Microsoft Exchange server 2007 disaster recovery for Exchange CCR in a production environment ... 155

Performing a quick recovery of a deleted mailbox in Exchange 2007... 157

Best practices... 157

Backups should be grouped with no more than 10 storage groups at a time ... 158

Use consistency check parameters to set threading and throttling to handle performance issues ... 158

Additional Exchange backup and recovery best practices ... 159

Exchange recovery limitations ... 160

Chapter 6 Microsoft Exchange 2010 Server Backup and Recovery

Overview ... 164

Supported operating systems... 164

Types of backup and recovery ... 165

Exchange 2010 VSS writers... 166

LAN-based Exchange server configuration with a storage area network and a proxy client... 166

Exchange server 2010 DAG scenario... 166

Backup initiated transaction log file truncation ... 166

Microsoft Exchange server 2010 MAPI client and Collaboration Data Objects version 1.2.1 for Recovery Database item level recovery in Exchange 2010 ... 167

Performing Exchange 2010 backups... 167

Backup options ... 167

Specifying Exchange 2010 application data save sets... 168

Displaying save set syntax... 168

Exchange 2010 application information variable settings... 169

Configuring persistent and non-persistent snapshots... 171

Configurations for backing up Exchange 2010 in non-DAG and DAG environment... 171

Prerequisites before running a backup on the Exchange 2010 system ... 171

Promoting Exchange 2010 incremental backup to full backup... 172

Configuring Exchange server 2010 backups ... 172

Configuring Avamar deduplication backups in a DAG environment... 175

Performing non-persistent backup of Microsoft Exchange 2010 ... 176

Verifying backups ... 176

Performing Exchange server 2010 recovery ... 176

Performing full recovery... 176

Performing advanced recovery... 177

Performing granular recovery of mailbox, folder, or e-mail ... 181

Performing a quick recovery of a deleted mailbox in Exchange 2010... 182

Microsoft Exchange server 2010 disaster recovery... 183

Best practices... 183

(7)

Chapter 7 Microsoft SharePoint Server 2003 Backup and Recovery

Overview... 186

VSS backup support provided by NMM ... 186

Microsoft SharePoint Portal server 2003 and Windows SharePoint Services 2.0... 187

Types of supported backup ... 187

Supported SharePoint 2003 writers ... 187

Commands used SharePoint 2003 backup and recovery ... 187

Performing SharePoint 2003 backups ... 188

SQL application information variable settings in SharePoint 2003 backup ... 188

Displaying valid SQL data save sets for SharePoint 2003 backup ... 188

Configuring SharePoint 2003 backup tasks ... 189

Performing SharePoint 2003 recovery ... 191

Example of SharePoint 2003 backup and recovery process... 192

Creating a new SharePoint portal with three new databases ... 193

Viewing the location and hierarchy of databases as they appear in SQL Enterprise Manager UI... 193

Configuring and performing a backup of the new databases with NMM save sets... 193

Verifying that all databases are backed up through the UI ... 194

Deleting the new databases... 195

Performing an NMM recovery of the databases... 195

Verifying database recovery through the SQL Enterprise Manager ... 195

Recovering the portal site through SharePoint Portal Server Central Administration... 196

Verifying the creation of the portal site in SharePoint Server Central Administration... 200

Chapter 8 Microsoft SharePoint Server 2007 Backup and Recovery

Overview... 202

NMM solutions for protecting a Microsoft SharePoint 2007 farm ... 202

Microsoft Office SharePoint server 2007 and Windows SharePoint Services 3.0... 204

Types of SharePoint server 2007 backup and recovery ... 204

Microsoft Office SharePoint 2007 farm configurations ... 205

SharePoint 2007 writers ... 209

SharePoint 2007 application information variable settings... 210

URL encoding for SharePoint save sets... 210

Specifying SharePoint 2007 save sets for application data ... 212

Displaying valid SharePoint 2007 data save sets ... 212

Configuring SharePoint 2007 backups ... 213

Performing SharePoint 2007 farm hardware backups... 219

Performing SharePoint 2007 recovery ... 225

Full recovery of a stand-alone SharePoint farm... 225

Full recovery of a distributed SharePoint farm... 226

Recovery of individual SharePoint content databases... 227

Recovery of SharePoint Search/Content Indexes... 227

Rollback of SharePoint SQL databases... 228

Performing SharePoint 2007 disaster recovery... 228

Disaster recovery planning ... 228

Performing a disaster recovery... 229

Keeping backups and recoveries in sync ... 230

(8)

Best practices for disaster recovery ... 231

Backing up SharePoint database by using NMM and NMSQL ... 233

Chapter 9 Microsoft SharePoint Server 2010 Backup and Recovery

Overview ... 236

New features in Microsoft SharePoint 2010 ... 236

Microsoft SharePoint 2010 support on Microsoft Windows server 2008 ... 237

Microsoft SharePoint server 2010 and SharePoint Foundation 2010... 237

Types of SharePoint server 2010 backup and recovery... 237

NMM and Microsoft Office SharePoint 2010 farm configurations... 238

SharePoint 2010 writers... 238

Specifying SharePoint 2010 application data save sets ... 238

Displaying valid SharePoint 2010 data save sets ... 239

Prerequisites for SharePoint 2010 backup ... 240

Performing SharePoint 2010 backup ... 240

Performing SharePoint 2010 recovery... 241

Performing SharePoint 2010 disaster recovery ... 241

Chapter 10 Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM

Overview ... 244

Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is installed... 245

Changes in NetWorker 7.6 SP2 core client functionality when NMM 2.3 is uninstalled ... 246

Basic steps for Windows Disaster Recovery backup and recovery ... 246

Performing Windows Disaster Recovery backup and recovery for Microsoft applications ... 247

Perform a Windows DR backup ... 247

Perform a Windows DR recovery... 248

Chapter 11 Troubleshooting

About the troubleshooting process... 252

Setting up notifications ... 253

Finding errors ... 253

NMM client error messages... 253

E_VOLUME_NOT_SUPPORTED ... 254

E_VETO_PROVIDER ... 254

VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 ... 255

VSS CLIENT... Invalid Writer Selection... for APPLICATIONS ... 255

Savegroup failed in scheduled backup... 255

Insufficient permission to access mailbox. See documentation for required permission settings. Server MBX is not capable of RSG operations... 256

77108:nsrsnap_vss_save ... 256

NMM validation for NSP Writer failed, unable to restore NPS VSS Writer data ... 257

NMM client issues... 257

In-progress backup fails... 258

NetWorker is blocked by Windows firewall ... 259 NMM backups might fail where a firewall exists between the

(9)

NetWorker server and client... 259

Need to run utility to obtain Exchange server information ... 260

Requesting a snapshot for a volume on hardware that is not transportable ... 260

The PowerSnap service must be restarted after the NetWorker service is restarted ... 261

PowerSnap validation for recovery fails ... 261

Snapshot backup may fail with writer errors... 261

Microsoft I/O write error when taking a replica in a CLARiiON array... 262

Creating a replica takes a long time in CLARiiON environment... 262

Cannot recover Exchange database due to overwrite prevention error ... 262

Incremental backups may be promoted to full backups ... 263

Diagnosing VSS Writer Issues ... 263

Modifying the Microsoft Exchange 2007 COM+ component’s user account or password... 264

Save sets may not appear in the Recover page ... 264

Recovery of AES-encrypted files fails without passphrase... 265

Unable to restore files encrypted with both Microsoft Windows Encrypting File System and AES encryption ... 265

Antivirus programs block recovery... 265

Snapshot cannot include both hardware and software snapshot volumes for clustered NetWorker VSS clients ... 266

Cross-platform directed recovery operations are not supported on NMM ... 266

Recovery of large number of items fails if one or more items in a folder is not selected... 267

Multiple client resources with the same name cannot be combined in the same group ... 267

Backup of two partitions of the same CLARiiON disk fails ... 267

Connection to DPM service lost during DPM recovery ... 267

DPM replica backup is not correctly configured ... 267

Backup fails if Exchange server in is renamed after it is created ... 268

In Exchange 2010, recovery fails for renamed mailbox database, however backup completed successfully for renamed database ... 269

In Exchange 2010, nsrsnap_vss_save -? is listing old database name instead of new database name after renamed mailbox database ... 269

Save sets from an Avamar AFTD for NMM backups show retention set to 1/18/2038... 269

Microsoft updates required to fix the vds.exe crash errors during retention on Windows 2008 and Windows 2003 ... 270

Back up of SYSTEM COMPONENTS fails due to missing System Writer... 270

Problems with RMExchangeInterface component ... 271

SharePoint backup fails when host and proxy client do not match... 271

NMM installation issues ... 272

RMAgentPS fails to uninstall when uninstalling NMM... 272

Recovery failure after .NET 3.5 framework installation ... 273

SYSTEM COMPONENTS failure after McAfee uninstall ... 274

If Exchange is installed after NMM, NMM reinstallation is required to get Replication Manager Exchange Interface ... 274

NMM uninstall and reinstall required to change the Replication Manager port number... 274

(10)

Checking log files ... 274

NMM client ... 275

PowerSnap client... 275

Replication Manager... 275

Solutions Enabler ... 276

Active Directory ... 276

NetWorker server... 276

Manually stopping and starting services... 277

Configuring dedicated web front-end crawling... 278

Using nsr.dir to skip files for NMM backup and recovery ... 278

Troubleshooting issues during SQL databases directed recovery ... 278

Name resolution ... 278

Other troubleshooting resources... 279

Glossary

Index

(11)

Title Page

1 Writers used by NMM for SQL data backup and recovery... 22

2 Commands used by NMM for SQL data backup and recovery... 22

3 SQL variable settings for Application Information attribute ... 23

4 Special characters and their URL-encoded values ... 24

5 SQL save set syntax... 25

6 Tasks for scheduling a backup ... 26

7 SQL server backup and recovery best practices and considerations... 38

8 Tasks for Active Directory or ADAM granular backup ... 43

9 Considerations for NMM client backup schedules... 46

10 System-only attributes that are not backed up ... 52

11 Retained attributes after object is deleted... 52

12 NMM Data Protection Manager commands... 61

13 DPM application information variable settings ... 62

14 DPM server 2007 save set syntax ... 63

16 Tasks for scheduling a backup ... 64

17 Hyper-V child partition configurations ... 80

18 NMM Hyper-V components ... 82

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

20 Hyper-V save set syntax... 83

21 Backup tasks for Hyper-V... 85

22 Writers used by NMM for Exchange server backup and recovery ... 111

23 Commands and attributes used by NMM for Exchange server backup and recovery 112 24 Exchange application information variable settings... 113

25 Exchange 2003 and 2007 save set names... 115

27 Tasks for configuring an Exchange server backup ... 119

28 Different backup procedures for Exchange recovery ... 121

29 Best practices and considerations for application backups ... 157

30 Exchange 2010 VSS writers ... 166

31 Exchange 2010 save sets for application data ... 168

32 Exchange application information variable settings... 169

33 Configurations required for backup in non-DAG and DAG environment... 171

34 Tasks for configuring an Exchange server backup ... 172

35 SharePoint features and details... 186

36 List of supported SharePoint writers ... 187

37 Backup tasks for SharePoint 2003 ... 189

38 Example: Minimum required save sets to be backed up ... 209

39 List of supported SharePoint 2007 writers ... 209

(12)

40 SharePoint application information variable settings ... 210

41 Special characters and their URL-encoded values... 211

42 SharePoint save set syntax ... 212

43 Tasks for SharePoint 2007 backups ... 213

44 SharePoint server backup list for disaster recovery ... 229

45 List of supported SharePoint 2010 writers... 238

46 SharePoint save set syntax ... 239

47 Supported and unsupported system recovery scenarios ... 247

48 Notifications and errors... 253

49 Services and processes used in NMM client... 277

(13)

Title Page

1 Configuration Options dialog box... 31

2 Client menu... 31

3 APPLICATIONS > SqlServerWriter tree nodes... 32

4 File System Recovery dialog box ... 33

5 NMM protection of DPM... 59

6 DPM recovery modes ... 67

7 Recover submenu for DPM recovery ... 68

8 DPM granular recovery available to file level ... 68

9 DPM granular recovery options ... 68

10 Directed recovery of FileServer1... 70

11 DPM database and replicas available as selectable items ... 72

12 DPM disaster recovery options... 73

13 Windows server 2008 or Windows server 2008 R2 host with Hyper-V child partitions 78 14 NMM backup of Hyper-V components ... 79

15 Hyper-V storage options... 80

16 Disaster recovery order for a Hyper-V server ... 94

17 Snapshot process with Exchange production server and proxy client ... 105

18 SCC architecture... 107

19 CCR core architecture... 108

20 Exchange Recovery Options window with Conventional Restore option selected 133 21 Available and unavailable storage groups... 140

22 Restore To command on context menu ... 140

23 RSG Configuration error message ... 141

24 RSG Configuration correct message... 141

25 Public folders cannot be recovered to an RSG ... 141

26 Selected and partially selected items... 144

27 Recovered Items folders in user mailbox ... 145

28 Select Storage Group Restore Destination dialog box ... 148

29 Local client on the taskbar next to Client... 150

30 Select Viewable Clients dialog box... 150

31 Select Exchange 2010 database... 177

32 Advanced Recovery dialog box ... 178

33 Manage RDB window ... 178

34 Create_DB window... 179

35 Exchange Recovery Summary... 180

36 Select Database window ... 181

37 Select mailbox, folder or e-mail for recovery ... 182

38 Newly created databases created in SharePoint... 193

(14)

39 NMM backups available for recovery ... 194

40 SQL databases selected for recovery in NMM ... 195

41 Databases recovered to SQL server... 196

42 SharePoint Server Central Administration page ... 196

43 SharePoint Portal Server Central Administration, Manage Portal Sites window ... 197

44 Portal creation and restore options ... 197

45 Portal restore and database names ... 198

46 Confirmation page for request to create a portal site... 198

47 Status window for portal creation process ... 199

48 Operation Successful page displayed when portal creation is complete ... 199

49 Recovered databases and SharePoint portal visible and available in SharePoint 200 50 SharePoint 2007 stand-alone farm configuration... 205

51 SharePoint 2007 distributed farm configuration... 206

52 Restore Remote Dependencies dialog box... 226

53 List of Microsoft applications that are supported for Windows DR backups ... 244

54 Troubleshooting process... 252

(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 may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

If a product does not function properly or does not function as described in this document, please contact your EMC representative.

Note: This document was accurate as of the time of publication. However, as information is added, new versions of this document may be released to the EMC Powerlink website 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

(16)

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 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

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)

(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:

[email protected]

If you have issues, comments, or questions about specific information or procedures, please include the title and, if available, the part number, the revision (for example, A01), the page numbers, and any other details that will help us locate the subject that you are addressing.

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

(18)

(19)

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 to an alternate location... 29

◆ Performing SQL server disaster recovery... 35

◆ Best practices... 38

Microsoft SQL Server

Backup and Recovery

(20)

Overview

Backup and recovery of Microsoft SQL server involves the following:

◆ SQL server support for VSS through Microsoft-supplied application writers.

◆ Creation of a point-in-time copy of data in EMC^® NetWorker^® Module for Microsoft Applications (NMM). The snapshot includes point-in-time copy of data and open files, which allows the backup of the SQL server while the SQL

database is online or in use.

Review the following sections before performing SQL server backup and recovery:

◆ “SQL server versions supported by NMM” on page 20

◆ “Types of supported backup and recovery” on page 21

◆ “Writers for SQL data backup and recovery” on page 22

◆ “Commands used by NMM for SQL data backup and recovery” on page 22

SQL server versions supported by NMM

The EMC Information Protection Software Compatibility Guide provides the most up-to-date lists of hardware, operating system, service pack, and application versions supported by the NMM client.

NMM client supports the following versions of Microsoft SQL server:

◆ SQL server 2008 R2 (x86, x64):

• Standard

• Enterprise

Note: It is recommended that you use Cumulative Update 4.

◆ SQL server 2008 SP2 (x86, x64):

• Standard

• Enterprise

◆ SQL server 2005 (x86, x64) Service Pack 4:

• Standard

• Enterprise

◆ SQL server 2008 R2 Express edition

◆ SQL server 2008 Express edition

◆ SQL server 2005 Express edition

Note: NMM only supports databases in SQL simple recovery.

NMM client does not support the following:

◆ SQL server running on IA64

◆ SQL server 2000

(21)

Overview 21

Types of supported backup and recovery

NMM supports database granularity for snapshot backup and restore. This allows you to back up a particular SQL database without having to shut down the database, and then select and restore that database from the backed-up databases.

NMM provides the following types of backup:

◆ Point-in-time snapshots, which include exact copy of data at that time including open files information

◆ Full backups for both SQL server 2005, SQL server 2008, and SQL server 2008 R2:

• Both default and named instances of SQL sever can be backup

• User defined Database level backup can also be performed

◆ Backup of databases with TDE encryption and file stream for SQL server 2008 and SQL server 2008 R2

◆ Backup of databases having file groups for SQL server 2005, SQL server 2008 and SQL server 2008 R2

“Performing SQL server backups” on page 22 provides details.

Note: NMM 2.3 does not support:

— SQL log backups for either SQL 2005, SQL 2008, and SQL 2008 R2.

— Incremental backups for SQL application.

— Individual file groups and files backup.

NMM provides the following types of recovery:

◆ Full recovery of SQL server 2005 , SQL 2008, and SQL 2008 R2 databases

◆ Disaster recovery

◆ Recovery of databases with TDE encryption and file stream for SQL 2008 and SQL 2008 R2

◆ Recovery of databases having file groups for SQL 2005, SQL 2008 and SQL 2008 R2

“Performing SQL server recovery” on page 27 and “Performing SQL server disaster recovery” on page 35 provide details.

(22)

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.

IMPORTANT

When performing SQL writer recovery, manually stop and start of the services.

Commands used by NMM for SQL data backup and recovery

Table 2 on page 22 lists the commands used by NMM to back up SQL data.

Performing SQL server backups

Ensure that:

◆ The SQL server VSS Writer service is enabled during backup.

◆ All databases are mounted when backing up data for a Microsoft SQL

application. Unmounted databases are not backed up, and no warning appears during the backup operation to indicate if any databases are unmounted.

IMPORTANT

As part of disaster recovery plan, back up either of the following on the application hosts:

- The save set All attribute in the save set field of the client resource.

or

- The SYSTEM COMPONENTS:\ save set along with the system volume, for example, C:\.

EMC recommends that no more than 200 databases are backed up at one time. If database sizes are large, this should be less.

Table 1 Writers used by NMM for SQL data backup and recovery

Writers Description

Application writers NMM uses the application writers provided by SQL server.

SqlServerWriter NMM uses the VSS writer for SQL server 2005, SQL server 2008, SQL server 2008 R2.

Table 2 Commands used by NMM for SQL data backup and recovery

Commands Description

nsrsnap_vss_save The NMM command to initiate the VSS-based backup.

nsrsnap_vss_recover The NMM command to initiate the VSS-based recovery.

(23)

Performing SQL server backups 23

This section provides the following information:

◆ “SQL server application information variable settings” on page 23

◆ “Displaying valid SQL data save sets” on page 23

◆ “URL encoding for SQL save sets” on page 24

◆ “Specifying save sets for SQL data” on page 25

◆ “Configuring SQL server backups” on page 25

SQL server application information variable settings

Table 3 on page 23 lists the variables that can be specified in the Application Information attribute of the client resource.

Displaying valid SQL data save sets

To display a list of the SQL save sets that are available for backup:

1. Open a command prompt on the application server.

2. Ensure that the SQL server VSS Writer service is enabled and running.

3. From the command prompt, type the following command to list the valid application data save set names:

• If the application server is not on a virtual host, type:

nsrsnap_vss_save -?

• If the application server is on a virtual host, run this command from the physical node that is currently hosting the application server:

nsrsnap_vss_save -? -c virtual_server_name 4. Press Enter:

• Each line of output corresponds to a save set entry that you can add to the Save Set attribute of a client resource.

• Each entry that you add to the Save Set attribute must be typed on a separate line, without the double quotes.

Table 3 SQL variable settings for Application Information attribute

Attribute name Description Values

NSR_SNAP_TYPE=value Specifies the snapshot service provider name. vss

This value is required.

NSR_DATA_MOVER=value application information attribute

Specifies the hostname of the NMM client that mounts the snapshot from NMM client to the proxy host. The host can be either a local host or a proxy client host.

Note: This attribute is required for hardware provider backups that are configured to use data mover.

• The local host

• The proxy client hostname Consider the following:

• If no value is typed, the local host is used as the data mover.

• If you are setting up a proxy client for a virtual cluster server, you must also type the proxy client hostname in the Remote Access attribute of the client resource.

• For serverless backups, specify a proxy client.

(24)

The save sets that are available for backup are listed in a format similar to the following:

APPLICATIONS:\SqlServerWriter

APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON

APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\master APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\model APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\msdb APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NADATA

URL encoding for SQL save sets

When specifying save set names in the Save Set attribute of the client resource, there are cases where special characters, such as the backslash (\), must be specified by their URL-encoded values.

URL-encoded values are used to represent special characters in the following cases:

◆ SQL server named instances

◆ SQL server database names

Consider the following example of a SQL server named instance:

◆ The name of a SQL server named instance consists of two parts: the hostname and a unique name.

◆ The hostname and a unique name are always separated with a backslash (\) character.

◆ When specifying a SQL server named instance in the Save Set attribute, replace the backslash with its URL-encoded value, which is %5C.

In the following example:

◆ A SQL server named instance that is identified as:

CORPDBSERV1\YUKON

◆ Would be represented in the Save Set attribute as:

CORPDBSERV1%5CYUKON

To back up only the database named NADATA in the SQL server named instance CORPDBSERV1\YUKON:

◆ The complete entry in the Save Set attribute would be:

APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NADATA

◆ If the database name in the previous example was NA#DATA, the save set entry would be:

APPLICATIONS:\SqlServerWriter\CORPDBSERV1%5CYUKON\NA%23DATA Table 4 on page 24 lists the most commonly used special characters and their URL values.

Table 4 Special characters and their URL-encoded values (page 1 of 2) Special character URL-encoded value Special character URL-encoded value

\ %5C ? %3F

/ %2F ] %5D

" %22 [ %5B

(25)

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 5 on page 25 lists the SQL save set syntax to specify for 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 databases are backed up from SYSTEM COMPONENTS:\ save set.

Configuring SQL server backups

To perform a full backup of SQL server for all VSS writers that are supported by NMM, complete the tasks outlined in Table 6 on page 26.

% %25 } %7D

# %23 { %7B

& %26 ^ %5E

< %3C ‘ %60

> %3E | %7C

Table 4 Special characters and their URL-encoded values (page 2 of 2) Special character URL-encoded value Special character URL-encoded value

Table 5 SQL save set syntax

Type of data to back up Save set syntax All default instance SQL data along with SQL Server

named instances and databases.

Ensure that the SQL server VSS Writer service is enabled and running before using this save set.

Only the named instance and database name combination

For instance level backup:

APPLICATIONS:\SqlServerWriter\host%5Cinstance For example, to back up a SQL Server named instance MT11\BU, type the following:

APPLICATIONS:\SqlServerWriter\MT11%5CBU\

Some special characters in a SQL server named instance or database name must be replaced with their URL-encoded values. “URL encoding for SQL save sets” on page 24 provides more information about URL encoding.

(26)

IMPORTANT

The EMC NetWorker Module for Microsoft Applications Release 2.3 Administration Guide provides details for the first four tasks in Table 6 on page 26.

Configure a SQL server client resource

To configure a SQL server client resource:

1. In the Administration page of the NetWorker Management Console, click Configuration.

2. In the expanded left pane, select Clients.

3. From the File menu, select New.

4. In the Name attribute, type the hostname, that is the fully qualified name, of the NetWorker client computer.

Note: If backing up a SQL clustered instance, use the virtual SQL name here. Create client resources for all physical cluster nodes where the SQL clustered instance is run.

5. In the Comment attribute, type a description.

Note: If you are creating multiple client resources for the same NetWorker client host computer, use this attribute to differentiate the purpose of each resource.

6. From the Browse Policy attribute, select a browse policy from the list. The browse policy determines how long rolled-over data is available for quick access.

7. From the Retention Policy attribute, select a retention policy from the list. The retention policy determines how long rolled-over data is available though not necessarily quickly.

8. Select the Scheduled Backups attribute:

• If needed, use URL-encoded values when specifying save set names in the Save Set attribute of the client resource.

Table 6 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.

(27)

Performing SQL server recovery 27

• URL-encoded values are used to represent special characters such as the backslash (\). A table of values is provided in “URL encoding for SQL save sets” on page 24.

• To back up SQL server 2005, SQL server 2008, SQL server 2008 R2 named instances and default instances together, specify the save set name:

The SQL server save set syntax is described in “Displaying valid SQL data 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 3 on page 23.

10. Click the Globals (1 of 2) tab.

11. In the Aliases attribute, type the NETBIOS name for the client.

Note: NMM client uses the host machine NETBIOS or “short” name when connecting to the NetWorker server to browse backups. If the NETBIOS name is not found, NMM will not be able to display backups.

Performing SQL server recovery

Note: Although this release no longer supports SQL server 2000, you can use NMM to recover previous backups of SQL server 2000 data.

The tasks for recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases are different from those for SQL server 2005, SQL server 2008, SQL server 2008 R2 Express databases. Review the following sections that are applicable for your setup:

◆ “Recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases from the SQLServerWriter save set” on page 27

◆ “Recovering SQL server 2005, SQL server 2008, or SQL server 2008 R2 Express databases from the SYSTEM COMPONENTS save set” on page 28

◆ “Recovering SQL instance for SQL clusters” on page 28

Recovering SQL server 2005, SQL server 2008, SQL server 2008 R2 stand-alone databases from the SQLServerWriter save set

When system databases are recovered, the SQL server services for the SQL database instances are automatically detected and stopped by NMM. After the recovery is complete, NMM automatically starts the SQL server services for the SQL server database instances.

When user databases are recovered, the services are not stopped or started as with system databases.

(28)

To recover SQL server 2005, SQL server 2008, and SQL server 2008 R2 stand-alone databases:

1. From the navigation tree, expand the Applications folder and the SQLServerWriter folder.

2. Select the databases to recover.

3. From the System Recover Session toolbar, click Start Restore.

Recovering SQL server 2005, SQL server 2008, or SQL server 2008 R2 Express databases from the SYSTEM COMPONENTS save set

To recover SQL server Express databases that were backed up to the SYSTEM COMPONENTS save set:

1. If restoring the master database, stop the SQL server services for the SQL server database instances.

2. From the navigation tree, expand the SYSTEM COMPONENTS:\ folder.

3. In the Recovery Options dialog box, clear the option Use Microsoft Best Practices for selecting the System State.

4. Under System Components, browse the writer SQL Embedded and select the required databases for restore.

5. From the System Recover Session toolbar, click Start Restore.

6. After the recovery is complete, start the SQL server services for the SQL database instances.

Recovering SQL instance for SQL clusters

Note: This procedure is common to all supported SQL versions and Windows platforms.

For instance level recovery on SQL server cluster, perform the following steps:

1. Using Windows Cluster Management console, make the SQL Server resource under the Cluster Group of SQL Server, offline.

Now the instance is down but the disk is available because the group is up.

2. Perform SQL writer recovery.

Note: When performing SQL writer recovery, manually stop and start of the services.

3. In the Cluster Management console, make the SQL Server resource online.

Ensure that all the other SQL resources that depend on that SQL Server are online.

(29)

Performing SQL server directed recovery to an alternate location 29

Performing SQL server directed recovery to an alternate location

For SQL server directed recovery:

◆ SQL databases can be selected.

◆ The NMM GUI can be started on the machine to which the SQL database is restored. The directed recovery is Pull directed recovery.

◆ Once restore is complete, the SQL Management Studio program can be used to manually attach the SQL database.

The directed recovery procedure does not use SQL Writer. A restore performed without using SQL Writer guarantees a crash-consistent database, which means that there are no torn or corrupted pages. However, all transactions which were in progress at the time of the snapshot are rolled back. You would lose the ability to restore the database with no recovery, and apply log backups to it.

Directed recovery is supported on the same versions of Windows servers. For example, if the backup is done on a Windows 2003 machine, then the directed recover can be done only to another Windows 2003 machine. All the database files must be recovered to a single drive.

“Steps for SQL server directed recovery” on page 29 provides the steps for SQL directed recovery.

The following are not supported:

◆ Directed recovery is not allowed from SQL System database.

◆ Directed recovery of filestream database is not supported.

◆ Directed recovery of TDE Encryption database is not supported.

◆ Directed recovery of cross-SQL platform is not supported.

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

◆ Directed recovery to the same machine is not supported.

◆ Directed recovery to encrypted target is not supported.

◆ Directed recovery to compressed drive is not supported. Although recovery takes place, the database attachment fails.

◆ SQL Data Protection Manager (DPM) directed recovery is not supported.

◆ Directed recovery of SQL express is not supported.

◆ No validation available for restore target paths clustered paths.

When a path is selected, the NMM GUI does not validate if the path is valid. The path validation is done only after recovery is started.

Steps for SQL server directed recovery

Before restoring the SQL database content, ensure that:

◆ The target machine on which NMM GUI is started and the source machines are added as client resource on NetWorker.

◆ The recovery drive is available and has sufficient free disk space to accommodate the data.

(30)

Toperform directed recovery of SQL databases, perform the following steps:

1. Start the NMM GUI on the machine to which the SQL database is recovered.

2. Select the NetWorker server containing the SQL backups, as described in

“Selecting the NetWorker server” on page 30.

3. Select the client whose backup has been taken, from the NMM GUI, as described in “Selecting a 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 an alternate location from the SQL tab, as described in “Recover by using an alternate recover 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. Provided there is no media access conflict, the restores can take place in parallel.

Selecting the NetWorker server

To select the NetWorker server containing the SQL backups:

1. To change the currently selected server, click the Change NetWorker Server icon on the toolbar.

The Change NetWorker Server dialog box appears.

2. In the Change NetWorker Server dialog box:

a. Click the Update Server List button to refresh the list of NetWorker servers.

b. Select the desired NetWorker server and click OK.

3. Select the backed up client machine as described in “Selecting a client” on page 30.

Selecting a client

To select a client:

1. From the Options menu, select the Configure Options to add the backed-up client machine to the list of client machines that you can browse.

The Configuration Options dialog box as shown in Figure 1 on page 31 appears.

(31)

Performing SQL server directed recovery to an alternate location 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.

(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 instance and databases.

Note: The SQL System databases are not supported for SQL directed recovery.

4. Recover the SQL databases:

• To the default recover path, as described in “Recover by using the default recover path” on page 32.

or

• To an alternate location from the SQL tab, as described in “Recover by using an alternate recover path” on page 33.

Recover by using the default recover path

To recover SQL databases by using the default recover path:

1. Select the database to be recovered using directed recovery in System recover Session.

2. Click Recover.

The System Recover Session Options appears.

3. Select the Recover option, and then click the SQL tab.

4. Select the Restore SQL file to local machine using their original directory path option.

5. Click OK.

(33)

Performing SQL server directed recovery to an alternate location 33

The File System Recover Summary form as shown in Figure 4 on page 33 appears.

Figure 4 File System Recovery dialog box

Note: The SQL database recover path is based on the original path. This is the default SQL recover path option.

6. Click Start Recover to initiate the directed recover.

7. Switch to the Monitor page to view the status and progress of the recover.

Recover by using an alternate recover path

There are two alternate ways of navigating to the System Recover Session Options dialog box where an alternate SQL recover path can be specified:

◆ Selecting Recover Options from the toolbar.

◆ Selecting the Recover Options button in the File System Recover Summary dialog box.

This section describes how you can use the Recover Options option from the toolbar to select an alternate recover path to recover SQL databases.

To recover SQL databases by using an alternate recover path:

1. Select the database to be recovered using directed recovery in System Session.

2. Click the SQL tab.

3. Specify the destination path for the SQL databases:

a. Select the Specify the file system path where the SQL database(s) restored option.

This enables the Browse button.

Note: The field is read-only and you cannot manually type a path.

b. Click Browse.

The Browse For Folder dialog box appears.

(34)

4. Select the desired recover location and click OK.

The System Recover Session Options dialog box appears.

5. Click Recover.

The File System Recover Summary dialog box appears.

6. Click Start Recover to initiate the directed recover.

Note: If the SQL alternate recover path is invalid, for example, blank or network share is incorrect, a error message dialog box appears.

7. Switch to the Monitor page to view the status and progress of the recover.

Examples of log messages in NMM log file and Monitor page

Examples of messages for SQL directed recover in both the NMM log file and the UI Monitor page.

Case 1: Restore to original location messages in NMM log Command line:\n C:\Program

Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A

RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A NSR_SQL_TARGET_ORIG=yes -I -

nsrsnap_vss_recover: flag=A arg=NSR_SQL_RECOVER_MODE=alt_location nsrsnap_vss_recover: flag=A arg=NSR_SQL_TARGET_ORIG=yes

NMM .. Performing SQL directed restore.

NMM .. SQL directed restore will relocate database files to their original locations.

Case 2: Restore to alternate location messages in NMM log Command line:\n C:\Program

Files\Legato\nsr\bin\nsrsnap_vss_recover.exe -A

RESTORE_TYPE_ORDER=conventional -A BR_ELEVATED_WARNING=true -s mb-nwsvr-1.baker.legato.com -c mb-clnt-3.belred.legato.com -A NSR_SNAP_TYPE=vss -A NSR_SQL_RECOVER_MODE=alt_location -A NSR_SQL_TARGET_DIR=E:\ -I -

nsrsnap_vss_recover: flag=A arg=NSR_SQL_RECOVER_MODE=alt_location nsrsnap_vss_recover: flag=A arg=NSR_SQL_TARGET_DIR=E:\

NMM .. Performing SQL directed restore.

NMM .. SQL directed restore will relocate database files to path[E:\].

NMM .. SQL directed restore relocating database files for database [APPLICATIONS:\SqlServerWriter\MB-CLNT-3\AcmeBank].

NMM .. SQL directed recover, relocating file [C:\Program Files\Microsoft SQL

Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf] to [E:\Program Files\Microsoft SQL

Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank.mdf].

Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf] to [E:\Program Files\Microsoft SQL

Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank_log.ldf].

Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf] to [E:\Program Files\Microsoft SQL

Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\AcmeBank2.mdf].

(35)

Performing SQL server disaster 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

For SQL disaster recovery on Windows 2008 and Windows 2008 R2 with NetWorker 7.6 SP2, use Windows Disaster Recovery. Chapter 10, “Windows Disaster Recovery by using NetWorker 7.6 SP2 and NMM” provides details.

In cases where the SQL server databases must be completely rebuilt, NMM can facilitate a disaster recovery. Prior to disaster recovery, use NMM to perform regular backups of volumes, system components, and application save sets.

The following save sets should be backed up regularly:

1. Back up the following with the snapshot policy “all.”

C:\

SYSTEM COMPONENTS:\

The backup of C:\ automatically includes the following:

• Windows Boot Volume

• Windows System Volume

Note: If the system has been set up with a separate file system for the Windows

boot\system partition and separate file system for application installation, then along with C:\ drive, back up the file system that includes the Windows Boot Volume, Windows System Volume, and application software.

“Specifying save sets for SQL data” on page 25 provides information for SYSTEM COMPONENTS:\ backup.

Note: Back up Cluster Management when backing up SQL server cluster.

(36)

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” on page 36

◆ “SQL server (stand-alone) disaster recovery on Windows server 2003” on page 36

◆ “SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003” on page 37

SQL server (stand-alone) disaster recovery on Windows server 2008

To perform a disaster recovery of SQL server on a Windows server 2008 machine:

1. Install SQL server and latest service packs, including the SQL server instances that were running on the machine before the disaster.

Note: The instance names must be exactly the same as the previous ones.

2. Perform a recover of the system components and volumes.

3. Perform a recovery of the SQL server data for all previous instances.

Note: In the NMM interface, clear the options for all of the system databases, or the recovery will fail.

SQL server (stand-alone) disaster recovery on Windows server 2003

To perform a SQL server (stand-alone) disaster recovery on Windows server 2003:

1. Set up a new Windows 2003 machine to the following on the old machine:

• Machine name

• IP address

• Domain status

2. Recover SYSTEM COMPONENTS:\ and the local file system volumes.

3. Reboot the machine.

4. Log in to the machine as local administrator.

5. Unjoin the domain, and then rejoin the domain.

6. Recover the APPLICATIONS:\SqlServerWriter save set.

7. Reboot, and then recovery will be complete.

(37)

Performing SQL server disaster recovery 37

SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003

To perform a SQL server cluster disaster recovery on Windows server 2008 and Windows server 2003:

1. Set up each new cluster machine to match the following on the corresponding old machine:

• Machine name

• IP address

• Domain status

2. For only Windows server 2008, on each cluster machine:

a. Install SQL server 2005 and all updates that were installed on the old machines.

b. Install all instances that were installed on the old machines.

3. Recover each node’s SYSTEM COMPONENTS:\ and local file system volumes.

4. Reboot each new machine.

5. On each machine:

a. Log in to the machine as local administrator.

b. Unjoin the domain.

c. Rejoin the domain.

6. For only Windows server 2008, on the active node:

a. Stop SQL Instance Services.

b. Restore APPLICATIONS:\SQLServerWriter save set.

c. Start SQL Instance Services.

7. For only Windows server 2003, on each machine:

a. Recover the APPLICATIONS:\SqlServerWriter save set.

b. Reboot each machine.

Cluster status recovery is complete.