EMC NetWorker Module for Microsoft Applications Release 2.2. Administration 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.2

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

(3)

EMC NetWorker Module for Microsoft Applications Release 2.2 Administration Guide 3

Preface

Chapter 1 Overview

NetWorker Module for Microsoft Applications ... 20

NetWorker Module features ... 20

Privileged user-level access... 21

Windows and Microsoft application updates ... 21

Supported configurations... 22

Supported NetWorker Server hosts... 22

Windows operating system support ... 22

Simple LAN-based configuration ... 23

LAN-based configuration with a proxy client ... 24

LAN-free configuration ... 25

The VSS snapshot creation process ... 27

Writers... 28

Providers... 30

Dynamic volume support ... 30

Providers and backup performance ... 31

NMM client snapshot backups ... 32

Nonpersistent rollover backup... 32

Instant backup with or without rollover... 32

Serverless backup ... 32

NMM client recoveries... 34

Conventional recovery... 34

Instant recovery ... 34

Rollback recovery ... 34

Disaster and granular backup and recovery for applications... 35

The NMM client interface... 37

Recover view ... 37

Snapshot Management view... 39

Monitor view... 40

NMM client graphical user interface ... 41

Opening the software and connecting to a NetWorker server ... 41

Selecting an item for recovery ... 42

Searching for an item ... 42

Specifying a recovery browse time ... 43

Selecting a backup version for recovery ... 43

(4)

Chapter 2 Configuring a Scheduled Backup

Backup configuration roadmap ... 46

Privileged user-level access ... 47

Name resolution... 48

Best practices and considerations for backing up application data... 48

Task 1: Configure a backup pool for snapshot operations ... 50

Configuring a device ... 50

Configuring a label template... 51

Configuring a backup pool... 51

Labeling the device ... 52

Task 2: Configure snapshot policies ... 53

Snapshot policies for SYSTEM COMPONENTS backup ... 53

Creating a snapshot policy ... 53

Snapshot policy examples... 55

Task 3: Configure a backup schedule ... 56

Task 4: Configure a backup group ... 57

Task 5: Configure a Client resource ... 59

Configuring a Client resource for System volumes, components, and applications ... 59

Specifying save sets for application data... 59

Application information variable settings ... 63

Task 6: Configure privileges ... 64

Task 7: Configure a proxy client... 65

Backing up a clustered NMM Client ... 67

NetWorker pathownerignore cluster functionality is not supported ... 67

Cluster failover and backups... 67

Moving an NMM Client to another NetWorker server ... 68

Chapter 3 Deduplication Backup and Recovery

Data deduplication... 70

Related information about Avamar server and NetWorker server... 71

Avamar integration in NMM ... 71

Windows OS, application, and configuration support ... 72

Unsupported for deduplication ... 72

Avamar and NetWorker server configuration ... 73

Configuring Avamar and the NetWorker server to receive deduplication data and process backups ... 73

Setting DNS resolution for NetWorker Deduplication Node and NMM ... 73

Deduplication backups... 74

Backup levels and schedules for deduplication clients... 74

Retention policies ... 74

Backup configuration notes... 75

Configuring a Client Resource for deduplication ... 76

Configuring a deduplication client ... 76

Recovering deduplicated data ... 78

Deleting deduplication save sets ... 78

Querying deduplication save sets using mminfo ... 78

Additional NetWorker server deduplication operation information ... 78

Chapter 4 System Backup and Recovery

Windows system backup ... 80

(5)

Specifying system save sets for recovery ... 80

NMM System data commands ... 81

Performing system backups ... 82

Task 5: Configure a System Client resource ... 82

Performing a recovery... 84

System recovery in Windows Server 2008 and Windows Server 2003... 85

System Recovery Options Summary ... 86

Recovery options ... 87

General recovery options ... 87

NetWorker recovery options ... 87

Cluster recovery options ... 89

ADAM recovery options ... 91

DFS recovery options ... 92

FRS recovery options ... 95

NTDS recovery options ... 96

Security recovery options... 98

Recovering file system snapshots that have not been rolled over... 99

Booting Windows in Directory Service Restore mode ... 100

Performing an authoritative recovery of NTDS or FRS data ... 101

Performing a directed recovery ... 103

Peforming a directed recovery with NMM ... 103

Recovering the Windows system configuration to an earlier state ... 106

Disaster recovery ... 107

Disaster recovery when the NMM client is not on a domain controller... 108

Disaster recovery when the NMM client is on a domain controller... 109

Chapter 5 Microsoft SQL Server Backup and Recovery

Microsoft SQL Server backup and recovery ... 112

SQL Server versions supported by NMM... 112

Types of supported backup and recovery ... 112

Components used by NMM for SQL data backup and recovery... 113

Specifying save sets for SQL data ... 113

Displaying valid SQL data save sets... 114

URL encoding for SQL save sets ... 115

SQL Server application information variable settings ... 116

Performing SQL Server backups ... 117

Full backup of an SQL Server ... 117

Performing SQL Server recovery... 119

Recovering SQL Server 2005 and 2008 stand-alone databases from the SQLServerWriter save set... 119

Recovering SQL Server 2005 or 2008 express databases from the System Components save set ... 119

Best practices for SQL Server backup and recovery... 119

Performing SQL Server disaster recovery... 121

SQL Server (standalone) disaster recovery on Windows Server 2008.... 121

SQL Server (standalone) disaster recovery on Windows Server 2003.... 121

SQL Server cluster disaster recovery on Windows Server 2008 ... 122

(6)

Chapter 6 Microsoft SharePoint Server Backup and Recovery

Microsoft SharePoint Server backup and recovery ... 126

SharePoint Server versions supported by NMM client... 126

SharePoint Server 2007 backup and recovery ... 127

Types of SharePoint Server 2007 backup and recovery ... 127

Protecting a SharePoint farm... 128

Storage requirements and performance impact in SharePoint backup ... 129

NMM installation requirements for a Microsoft Office SharePoint 2007 system ... 129

SharePoint 2007 data backed up by NMM... 131

Keeping backups and recoveries in sync... 131

Components used by NMM for SharePoint backup and recovery ... 132

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

Displaying valid SharePoint 2007 data save sets ... 133

URL encoding for SharePoint save sets ... 134

SharePoint 2007 application information variable settings ... 135

Performing SharePoint 2007 backups ... 136

Configuring SharePoint 2007 backups... 136

Task 5: Configure a SharePoint 2007 Client resource ... 138

Performing a full backup for a distributed SharePoint farm... 143

Performing SharePoint 2007 recovery... 143

Mandatory order for SharePoint recoveries... 144

Configuration database recovery requirements in full farm recovery ... 144

Selecting valid items for recovery ... 144

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

Full recovery of a distributed SharePoint farm ... 145

Recovery of individual SharePoint content databases ... 146

Recovery of SharePoint Search/Content Indexes ... 146

Rollback of SharePoint SQL databases ... 147

SharePoint 2003 backup and recovery ... 147

Types of supported backup and recovery... 147

Components used by NMM for SQL backup and recovery ... 148

Specifying save sets for SharePoint 2003 SQL data... 148

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

URL encoding for SQL save sets in SharePoint 2003 backup... 150

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

Performing SharePoint 2003 backups ... 152

Task 5: Configuring a SharePoint 2003 Client resource ... 152

Performing a SharePoint 2003 recovery... 154

Recovering SQL Server 2000 stand-alone databases for SharePoint 2003 ... 154

Recovering SQL 2005 databases for SharePoint 2003 ... 154

Best practices for SQL Server backup and recovery of SharePoint 2003 databases ... 156

SharePoint 2003 scenario of backup and recovery process ... 158

SharePoint 2007 disaster recovery ... 165

Disaster recovery planning... 165

(7)

Chapter 7 Microsoft SharePoint 2007 Granular Backup and Recovery

NMM support for granular backup and recovery of SharePoint items ... 170

SharePoint objects available in NMM granular backup ... 170

SharePoint limitations on document metadata recovery ... 170

Better performance for large SharePoint farms ... 171

Performing SharePoint 2007 granular backups... 171

Configuring a SharePoint 2007 Client resource for granular backup ... 172

SharePoint 2007 granular recovery ... 173

SharePoint recovery search ... 175

Searching and marking tips ... 177

Searching for a SharePoint item ... 177

Performing a granular recovery of SharePoint items ... 178

SharePoint prerecovery options... 179

Selecting alternate destination options... 179

SharePoint recovery options ... 181

Commands for SharePoint 2007 granular backup and recovery... 182

nsr_moss_save.exe command... 182

nsr_moss_recover.exe command ... 186

Using administrator account other than that created during installation ... 188

Chapter 8 Microsoft Exchange Server Backup and Recovery

Exchange Server backup and recovery... 190

Microsoft Exchange Server MAPI client and Collaboration Data Objects support... 190

Exchange Server versions supported by NMM client ... 190

NMM and Exchange Server support for L18N ... 190

Exchange Server backup and recovery types... 190

Updating and modifying Exchange credentials ... 191

Compatibility with previous Exchange Server backups ... 192

Exchange Server data backed up by NMM ... 193

Components used by NMM for Exchange Server backup and recovery... 193

Specifying Exchange save sets for application data ... 194

Exchange application information variable settings ... 196

Snapshot process in an Exchange Server production and proxy client setup ... 198

Best practices for Exchange backup and recovery... 199

Performing Exchange Server backups... 202

Configuring Exchange Server backups ... 202

Configuring an Exchange Client resource ... 204

Configuring backup for Microsoft Exchange Server 2007 CCR ... 206

Performing Exchange Server recovery ... 215

Exchange recovery requirements and limitations ... 215

Quick recovery of a deleted mailbox ... 216

Exchange recovery options ... 217

Roll-forward recovery... 218

Point-in-time recovery ... 219

Mounting the database after recovery... 220

Rollback restore of Exchange data by using NMM ... 220

Exchange rollback operation requirements ... 221

(8)

Selecting a storage group restore destination ... 222

Recovery to the original storage group ... 223

Recovery to an Exchange RSG ... 224

Selecting and recovering items in the RSG database... 229

Recovery to an alternate storage group ... 231

Microsoft Exchange Server 2007 directed recovery... 234

Performing a directed recovery ... 234

Microsoft Exchange Server 2007 disaster recovery ... 237

Microsoft Exchange Server 2007 (standalone) disaster recovery... 237

Microsoft Exchange Server 2007 disaster recovery for Exchange CCR to a 2 node cluster in a production environment... 238

Microsoft Exchange Server 2007 disaster recovery for Exchange CCR in a production environment ... 240

Chapter 9 Microsoft Data Protection Manager Backup

Data Protection Manager backup and recovery ... 244

DPM Server versions supported by NMM client... 245

DPM backup and recovery types ... 246

DPM data backed up by NMM... 246

Transportable backups of DPM replicas not supported ... 246

Components used by NMM for DPM backup and recovery ... 247

Specifying DPM save sets for application data ... 248

DPM application information variable settings ... 250

Performing DPM Server backups ... 251

Configuring DPM backups... 251

Configuring a DPM Client resource ... 252

Performing DPM Server recovery ... 254

Chapter 10 Microsoft Data Protection Manager Granular and Disaster Recovery

Performing a granular recovery of DPM objects ... 256

DPM Recovery Options Summary ... 259

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

DPM directed granular recovery scenario ... 260

Performing a granular directed recovery ... 261

DPM disaster recovery ... 263

Chapter 11 Microsoft Hyper-V Backup and Recovery

Hyper-V backup and recovery ... 268

Hyper-V version requirements ... 268

Operating system versions supported by NMM client ... 268

Hyper-V parent partition backup and recovery types ... 269

Hyper-V parent partitions, child partitions, and applications within child partitions... 269

Hyper-V storage and backup options supported by NMM ... 270

Backup roadmap for Hyper-V ... 273

Best practices for Hyper-V parent partition backup and recovery... 275

Best practices for Hyper-V child partition applications backup and recovery ... 276

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

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

Hyper-V application information variable settings ... 279

Performing Hyper-V backups ... 280

(9)

EMC NetWorker Module for Microsoft Applications Release 2.2 Administration Guide 9 Hyper-V configuration requirements for backing up a virtual

machine that contains multiple volumes ... 280

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

Configuring Hyper-V backups ... 281

Configuring a Hyper-V Client resource ... 282

Performing Hyper-V recovery ... 284

Off-line and on-line recovery... 284

Restrictions for backup and recover of Hyper-V virtual machines in a Windows 2008 Failover Cluster ... 284

Hyper-V recovery to the original machine and location ... 285

Hyper-V recovery to a different machine or location ... 285

Hyper-V parent partition disaster recovery ... 288

Chapter 12 Microsoft Windows Cluster Backup and Recovery

Windows Server Cluster backup and recovery... 292

Cluster support in NMM client ... 292

Compatibility with previous Windows Cluster backups... 292

Components used by NMM for Windows Cluster backup and recovery... 292

Windows Cluster application information variable settings ... 293

Performing Windows Server Cluster backups ... 294

Cluster failover and backups ... 294

Windows Server Cluster recovery... 295

Windows Server 2003 clustered client disaster recovery ... 295

Disaster recovery of a cluster client ... 295

Disaster recovery from a legacy VSS backup ... 298

Disaster recovery of a clustered client from a legacy non-VSS backup ... 300

Monitoring a recovery ... 301

Chapter 13 Microsoft Active Directory Backup and Recovery

Active Directory backup and recovery... 304

Types of supported backup and recovery ... 304

Performing an Active Directory or ADAM backup ... 305

Planning backups for disaster recovery ... 305

Performing a granular Active Directory or ADAM backup... 306

Considerations for granular backup... 306

Configuring Active Directory or ADAM granular backups ... 307

Task 1: Set up local Windows SYSTEM account as an ADAM administrator... 307

Task 2: Configure a pool for backup operations ... 308

Task 3: Configure a backup schedule ... 310

Task 4: Configure a backup group... 310

Task 5: Configure a Client resource ... 311

Task 6: Configure privileges ... 313

Recovering all Active Directory data... 314

Performing a granular recovery of Active Directory objects and attributes ... 316

Recovery Restrictions for Active Directory ... 317

(10)

Chapter 14 Snapshot Management

Roll over a snapshot... 322

Roll back a snapshot ... 323

Rollback recovery requirements ... 323

Storage array descriptor file ... 323

System rollback may fail with CLARiiON if the configuration information is not current... 325

Performing a rollback recovery... 325

Delete a snapshot ... 326

Chapter 15 NetWorker Client Management

Specifying ranges for service and connection ports... 328

Specifying a password... 329

Chapter 16 Troubleshooting

The troubleshooting process... 332

Setting up notifications ... 333

Finding errors ... 333

NMM client error messages... 334

E_VOLUME_NOT_SUPPORTED ... 334

E_VETO_PROVIDER ... 334

VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 ... 334

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

access to the path is denied... 335

Object reference not set to an instance of an object... 335

NMM client issues... 336

Savegroup failed in scheduled backup... 336

In progress backup fails ... 336

NetWorker is blocked by Windows Firewall... 336

Need to run utility to obtain Exchange Server information ... 336

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

PowerSnap service must be restarted after the NetWorker service is restarted ... 337

PowerSnap validation for recovery fails ... 338

Snapshot backup may fail with writer errors ... 338

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

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

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

Incremental backups within NetWorker Module for Exchange Client may be promoted to full backups ... 339

Incremental backups within NetWorker Module for SQL Server Client may be promoted to full backups ... 339

Diagnosing VSS Writer Issues... 340

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

Save sets may not appear in the recover window... 341

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

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

(11)

Checking log files... 343

NMM client... 343 PowerSnap client ... 343 Replication Manager ... 344 Solutions Enabler... 344 Active Directory... 345 NetWorker server ... 345

Manually stopping and starting services ... 346

Other troubleshooting resources ... 347

Glossary

(12)

(13)

Title Page

1 Simple LAN-based configuration ... 26

2 LAN-based configuration with a proxy client ... 27

3 LAN-free configuration... 28

4 VSS backup process ... 30

5 NMM client main window ... 39

6 Exclusion representation of recover items ... 40

7 Snapshot Management view ... 41

8 Monitor view ... 42

9 Selected and partially selected items... 44

10 Local client on the taskbar next to Client... 106

11 Configuration Options dialog box... 106

12 Select Viewable Clients dialog box... 107

13 NMM client dropdown list ... 107

14 SharePoint 2007 stand-alone farm configuration ... 134

15 SharePoint 2007 distributed farm configuration ... 135

16 Restore Remote Dependencies dialog box ... 150

17 Newly created databases created in SharePoint... 164

18 NMM backups available for recovery... 165

19 SQL databases selected for recovery in NMM... 165

20 Databases recovered to SQL Server... 166

21 SharePoint Server Central Administration window... 166

22 SharePoint Portal Server Central Administration, Manage Portal Sites page ... 167

23 Portal creation and restore options... 167

24 Portal restore and database names ... 168

25 Confirmation page for request to create a portal site ... 168

26 Status page for portal creation process ... 169

27 Operation Successful page displayed when portal creation is complete... 169

28 Recovered databases and SharePoint portal visible and available in SharePoint ... 169

29 NMM displaying SharePoint 2007 browsing for recovery items... 179

30 NMM displaying Search tab for SharePoint 2007 recovery ... 180

31 Sample output from nsr_moss_save ... 187

32 Snapshot process with Exchange production server and proxy client ... 203

33 Select Storage Group Restore Destination dialog box ... 226

34 Available and unavailable storage groups... 230

35 Restore To command on context menu ... 230

36 RSG Configuration error message ... 231

37 RSG Configuration correct message... 231

38 Public folders cannot be recovered to an RSG ... 232

39 Selected and partially selected items... 234

(14)

44 NMM client dropdown list ... 240

45 NMM protection of DPM ... 249

46 Directed granular recovery to a DPM-protected client... 260

47 DPM recovery modes... 261

48 Recover submenu for DPM Recovery ... 261

49 DPM granular recovery available to file level... 262

50 DPM granular recovery options... 262

51 Directed recovery of FileServer1 ... 264

52 DPM database and replicas available as selectable items... 267

53 DPM recovery modes... 267

54 Recover submenu for DPM recovery ... 268

55 DPM disaster recovery options ... 268

56 Windows Server 2008 host with Hyper-V virtual machine child partitions ... 274

57 Hyper-V storage options ... 275

58 NMM backup of Hyper-V components ... 281

59 Disaster recovery order for a Hyper-V server... 292

(15)

Title Page

1 Currently supported writers ... 31

2 Support for disaster and granular backup and recovery ... 38

3 Backup tasks ... 48

4 Access privileges needed for NMM ... 49

5 Best practices and considerations for application backups ... 50

6 Conventional backup settings ... 57

7 Instant snapshot policy ... 57

8 Instant snapshot with rollover policy ... 57

9 Considerations for NMM Client backup schedules... 58

10 Save set syntax... 62

11 Special characters and their URL-encoded values ... 64

12 Application information variable settings... 65

13 Configuration requirements for a proxy client... 67

14 Additional steps and considerations for backing up a clustered Client resource ... 69

15 NMM System data commands... 83

16 Access privileges needed for NMM ... 86

17 SQL save set syntax... 115

19 SQL variable settings for Application Information attribute ... 118

20 SQL Server backup and recovery best practices and considerations ... 122

21 Comparison of VSS, optimized, and granular backups ... 131

22 SharePoint save set syntax ... 137

24 SharePoint application information variable settings ... 139

25 Save sets for backup... 140

26 SQL save set syntax for SharePoint 2003 ... 153

28 SQL variable settings for application information attribute... 156

29 SQL Server backup and recovery best practices and considerations ... 161

30 SharePoint Server backup list for disaster recovery ... 170

31 SharePoint recovery search fields ... 181

32 SharePoint granular recovery save set syntax for SharePoint 2007 objects... 186

33 Application information variable settings... 189

34 nsr_moss_recover command options... 190

35 Exchange save set syntax ... 198

37 Exchange application information variable settings... 200

38 NMM Data Protection Manager commands... 251

39 DPM Server 2007 save set syntax... 252

(16)

44 Hyper-V save set syntax ... 282

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

46 Windows Cluster application information variable settings ... 297

47 Additional steps and considerations for backing up a clustered Client resource ... 298

48 Considerations for NMM client backup schedules ... 314

49 System-only attributes that are not backed up... 321

50 Retained attributes after object is deleted ... 322

51 Notifications and errors... 337

(17)

EMC NetWorker Module for Microsoft Applications Release 2.2 Administration Guide 17 As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes.

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

Audience 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

NetWorker Module for Microsoft Applications

The EMC®_NetWorker®_{Module for Microsoft Applications (NMM) works with}

Microsoft Volume Shadow Copy Service (VSS) technology to provide snapshot backup and recovery services for file systems, and application, and operating system data.

The NMM client allows for the creation of point-in-time snapshot data. A snapshot can be retained on storage volumes for quick access. One can also perform a rollover of a snapshot to a traditional backup medium such as a tape, file type device, or advanced file type device. Data can be recovered either from a snapshot or from the backup.

NetWorker Module features

This NetWorker Module can be set up in a LAN-based or LAN-free environment. NMM provides the following features:

◆ Support for the following topologies:

• “Simple LAN-based configuration” on page 25

• “LAN-based configuration with a proxy client” on page 26

• “LAN-free configuration” on page 27

◆ Support for several types of backup and recovery, depending on the types available for the given application or operating system:

• “Instant backup with or without rollover” on page 34

• “Nonpersistent rollover backup” on page 34

• “Serverless backup” on page 34

• “Conventional recovery” on page 36

• “Instant recovery” on page 36

• “Rollback recovery” on page 36

◆ Deduplication support for most of the Microsoft applications and Windows operating systems that are supported by NMM:

• “Windows OS, application, and configuration support” on page 74 provides detailed lists of applications and versions supported.

• For the NetWorker server, NetWorker Release 7.5 SP1 or later is required. • For the Avamar server hardware, Avamar Axiom v4.0.2 or later is required.

◆ Application support:

• Microsoft Exchange Server 2007 • Microsoft Exchange Server 2003 • Microsoft SQL Server 2008 • Microsoft SQL Server 2005

• Microsoft Office SharePoint Server 2007 • Microsoft SharePoint Portal Server 2003 • Windows SharePoint Services 3.0 • Windows SharePoint Services 2.0

(23)

NetWorker Module for Microsoft Applications 23 • Windows Server 2008 with Hyper-V

• Windows Server 2008, Server Core Installation, with Hyper-V • Windows volumes and system components

• Windows Cluster support

• Active Directory Application Mode (ADAM) • Active Directory

Note: Application support often requires a minimum specific service pack level. The service pack levels frequently change. The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about which service packs are required for each application.

◆ Support for Windows VSS Provider:

• Microsoft Software Shadow Copy provider for use with most leading hardware arrays

• EMC Symmetrix® and Symmetrix DMXTM arrays with EMC VSS Provider • EMC CLARiiON®_{arrays with EMC VSS Provider}

• Celerra®_{arrays with Celerra VSS Provider}

• EqualLogic PS Series arrays with EqualLogic Integration ToolKit • IBM Storage System DS8000

• IBM Storage System DS6000

The EMC Information Protection Software Compatibility Guide provides the most up-to-date information about hardware array versions supported and NMM compatibility.

Privileged user-level access

All NMM users must have administrator-level privileges for all resources they access:

◆ NetWorker server

◆ Each NetWorker Module for Microsoft Applications (NMM) client machine

◆ All Microsoft applications protected by NMM, such as: • Windows Server

• Data Protection Manager (DPM) • SharePoint Server

• SQL Server • Exchange Server

◆ Network domains

◆ Storage servers

Windows and Microsoft application updates

(24)

Supported configurations

This section describes the basic configurations in which the NMM client is supported.

Supported NetWorker Server hosts

The NMM client supports NetWorker Server 7.3.3 or later and NetWorker Storage Node 7.3.3 or later on the following hosts:

◆ AIX

◆ HP-UX (PA-RISC)

◆ Solaris (SPARC)

◆ Windows

◆ Linux (NetWorker Server 7.4 SP3 or later and NetWorker Storage Node 7.4 SP3 or later)

The NMM client supports Internationalization (I18N).

NetWorker 7.4 SP3 or later is required for Microsoft Office SharePoint 2007 granular protection.

This release of NMM supports NetWorker cloning and staging to create and manage additional copies of save sets. This NMM support requires NetWorker 7.5 or later. The EMC NetWorker 7.5 Administration Guide provides details for cloning and staging. The following NetWorker features are not supported:

◆ Localization (L10N)

◆ Installation of dedicated storage node on NMM client host.

Note: NMM does support proxy storage node, as described in “LAN-free configuration” on page 27.

◆ Manual (adhoc) backups

Windows operating system support

NMM client supports the following versions of Windows and Windows-related features:

◆ Microsoft Windows Server 2008 (x86, x64)—Standard, Enterprise, DataCenter Editions

◆ Microsoft Windows Server 2003 R2 (x86, x64)—Standard, Enterprise, DataCenter Editions

◆ Microsoft Windows Server 2003 (x86, x64)—Standard, Enterprise, DataCenter Editions

◆ Microsoft Windows Storage Server 2003

(25)

Supported configurations 25 ◆ System state recovery, file servers, and operating system roles including Active

Directory, DHCP, and Terminal Services

◆ GUID Partition Table disks:

• No disk size limit on Windows environments with CLARiiON storage (SnapView™ clone, SnapView snap, and SAN Copy™ technologies only) • Disk size limit of less than 2 TB on Windows environments with Symmetrix

storage

Note: The following Windows Server versions are not supported: Windows IA64 editions.

In addition, the following Windows features are not supported:

◆ BitLocker encryption

◆ LAN-based Proxy Client or LAN-free backups, if dynamic disks are used

◆ VSS Hardware Providers with Windows dynamic disks

◆ Microsoft Software Shadow Copy provider to perform persistent snapshots of clustered disks

◆ Windows Automated System Recovery (ASR)

Note: Windows Storage Server Single Instance Storage (SIS) is supported, but recoveries will recover file data for all duplicate files. Data will not be lost if there is sufficient disk space to hold the duplicate copies.

The EMC Information Protection Software Compatibility Guide contains additional and the most up-to-date information about NMM compatibility.

Simple LAN-based configuration

Figure 1 on page 26 shows a simple LAN-based configuration with a storage area network. In a LAN-based configuration, the production data is stored on a storage area network (SAN) or direct-attached storage (DAS). The data path to the

NetWorker storage node devices is over a LAN. The application server that is being protected has the NMM client installed.

The data moves as follows:

1. The NetWorker Server, which must be release 7.3.3 or later, initiates the process by contacting the application server where the NMM client software is installed. 2. The application server with the NMM client software creates a snapshot of the

data on the storage volume.

Note: In Figure 1 on page 26, snapshots are represented by S1 through S5.

(26)

Figure 1 Simple LAN-based configuration

LAN-based configuration with a proxy client

Figure 2 on page 27 shows a LAN-based configuration with a storage area network and a proxy client. Both the application server and the proxy client have the NMM client installed.

Note: The application server and the proxy client must use the same version, NetWorker Module for Microsoft Applications release 2.2. If NMM 2.2 is installed on either the application server or the proxy client machine, then the other machine must also use NMM 2.2. Backup and recovery will fail if NMM 2.2 is used on one of these machines, and an earlier version of NMM is used on the other.

A proxy client is a host that acts as a remote data mover (DM) when snapshots are rolled over to a conventional backup medium. A proxy client frees resources on the application server. When a backup operation uses a proxy client, it is known as a severless backup.

1. The NetWorker server initiates the process by contacting the application server where the NMM client software is installed.

2. The application server with the NMM client software creates a snapshot of the data on the storage volume.

(27)

Supported configurations 27 3. The snapshot is made visible to the proxy client.

4. The proxy client uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, or tape.

Figure 2 LAN-based configuration with a proxy client

LAN-free configuration

Figure 3 on page 28 shows a LAN-free configuration with a storage area network. The NMM client is installed on the application server. The proxy client is installed on the NetWorker storage node.

You can set up a NetWorker storage node release 7.3.3 or later as a proxy client to avoid the network traffic that is generated when a snapshot is rolled over to a conventional backup medium. Network traffic is avoided because both the conventional backup device and the snapshot are directly attached to the storage node.

Note: Install the proxy client software by using the NMM client software package.

1. The NetWorker server initiates the process by contacting the application server where the NMM client software is installed.

2. The application server with the NMM client software creates a snapshot of the data on the storage volume.

LAN NetWorker Storage Node 7.3.x Primary storage (For example, CLARiiON or Symmetrix) Traditional storage S1 S2 S3 S4 S5 NetWorker Server 7.3.3 or later Application server NetWorker Module for Microsoft Applications

Proxy client NetWorker Module for Microsoft Applications

SAN

(28)

3. The snapshot is made visible to the proxy client.

4. The proxy client, in this case the storage node, uses a snapshot in primary storage to transfer the data into a conventional backup medium such as a file type disk, advanced file type disk, or tape.

The NetWorker server and the application server communicate through the LAN. However, the data itself is not transferred across the LAN because the

conventional backup medium is attached directly to the NetWorker storage node.

(29)

The VSS snapshot creation process 29

The VSS snapshot creation process

Microsoft Volume Shadow Copy Service (VSS) acts as a coordinator among the following three components that create, modify, back up, and recover data:

◆ Requestors

Requestors include the NetWorker backup application.

◆ Writers

Including writers for operating system data, application data such as Microsoft Exchange Server 2003 or Microsoft SQL Server data, and file system volumes such as a D:\ data drive.

◆ Providers

Providers include the Microsoft VSS software provider or hardware-based providers such as the EMC VSS Provider.

In VSS, NetWorker software is a requestor—an application that performs the backup and recovery of applications or services. When a requestor performs a backup or recovery, the following occurs:

1. The requestor asks for information from VSS. 2. VSS reviews the request for validity.

3. VSS sends writer data from multiple application and system writers to the requestor.

4. The requestor tells VSS which writers and volumes to include in the snapshot. Each application and service that supports VSS has its own writer, which

understands how the application or service works. After the writer signals that it has prepared the data, the following occurs:

1. The VSS software does the following:

a. Directs the writer to freeze input/output (I/O) to the selected volumes. b. Queues transactions for later processing.

c. Calls a provider to capture the requested data. 2. The provider does the following:

a. Captures the prepared data.

b. Creates a snapshot that exists side-by-side with the live volume. 3. After the snapshot is created:

a. The provider signals VSS, this signal tells the writer to resume activity. b. I/O is released to the selected volumes and any queued writes that arrived

during the provider's work are processed.

(30)

Figure 4 VSS backup process

Writers

Writers provide information about what data to back up, and specific methods for handling components and applications during backup and recovery. They also identify the type of application or service that is being backed up.

If a service or application is present on a system but is not active, information from its writer will not be available. Consequently, a writer can appear or disappear from backup to backup. Writer Writer Writer Writer Writer Requestor 4. Requestor asks VSS to create snapshot.

1. NetWorker software (the requestor) asks VSS to enumerate writers and gether their metadata.

2. Writers provide an XML description of backup components and define the recover method.

5. VSS tells the writers to freeze activity.

7. VSS tells the writers to resume activity.

3. VSS asks which providers can support a snapshot for each of the required volumes.

6. VSS tells the providers to create the snapshot of the current state on disk.

Disk 1 Disk 2 Disk 3

(31)

The VSS snapshot creation process 31

Table 1 on page 31 lists the writers that are supported for the NMM client.

Note: Files located in an FTP directory are not included in a SYSTEM COMPONENTS snapshot. Typically, FTP files are stored by IIS in C:\inetpub. IIS Metabase files are

configuration files, which are backed up as part of SYSTEM COMPONENTS. The FTP files are content files, and must be backed up separately.

Table 1 Currently supported writers

Writer type Writers supported by NMM

Volumes A file system path such as D:\data

Note: NMM only supports NTFS volumes. It does not support FAT16 and

FAT32 volumes. Also, NMM does not support backup of raw volumes.

Applications Microsoft Active Directory Application Mode (ADAM) Microsoft Exchange Server 2003

Microsoft Exchange Server 2007

Microsoft System Center Data Protection Manager 2007 Microsoft Distributed File Replication (Windows Server 2003) Microsoft Active Directory Lightweight Directory Services (AD LDS) Microsoft SharePoint Portal Server 2003

Microsoft Office SharePoint Server 2007 Windows SharePoint Services 2.0 Windows SharePoint Services 3.0 Microsoft SQL Server 2008 Microsoft SQL Server 2005

Windows Server 2008 (Full Installation) with Hyper-V Windows Server 2008 (Server Core Installation) with Hyper-V

Windows system components (Windows Server 2003 and Windows Server 2008 unless otherwise noted)

BITS (Background Intelligent Transfer Service) COM+ REGDB (Registration Database) Certificate Authority

Cluster Database (Windows Server 2003) Cluster Writer (Windows Server 2008)

DHCP (Dynamic Host Configuration Protocol) Jet Event log

FRS (File Replication Server)

FSRM (File Storage Resource Manager)

Microsoft Distributed File Replication (Windows Server 2003) IIS Configuration Writer (Windows Server 2008)

IIS Metabase

MSSearch Service Writer (Windows Server 2008)

NPS VSS Writer (Network Policy and Access Service, Windows Server 2008)

NTDS (Active Directory Schema) Registry

RSM (Removable Storage Manager) Remote Storage Manager

Shadow Copy Optimization Writer (Windows Server 2008) SQL Embedded (SQL 2005 Express, or SQL 2008 Express) Terminal Services Gateway Writer (Windows Server 2008) Terminal Services Licensing

(32)

Providers

A provider is used to capture snapshots. One of the following types of providers are available:

◆ EMC VSS Hardware Provider, which supports EMC Symmetrix, Symmetrix DMX, and CLARiiON arrays

◆ EMC Celerra VSS Hardware Provider, which supports Celerra arrays

◆ Dell EqualLogic VSS Hardware Provider, which supports EqualLogic PS Series arrays

◆ Microsoft Software Shadow Copy provider

◆ IBM SystemStorage DS Open API Package, which supports IBM Storage, which supports IBM Storage System DS6000 and DS8000

The Microsoft Software Shadow Copy provider is a host-based provider that works with any type of storage hardware. The EMC VSS Hardware Provider works with an CLARiiON or a Symmetrix disk array. Some features of the NMM client, such as serverless backup and rollback recovery, are available only with hardware providers such as the EMC VSS Hardware Provider.

The NetWorker Module for Microsoft Applications Release 2.2 Installation Guide provides more information about using NMM with a VSS Hardware Provider, including hardware array installation and configuration, and NMM installation and configuration.

Note: NMM does not support rollback restore for backups performed by EqualLogic or Celerra hardware. Only conventional restore and snapshot restore are supported for backups

performed by EqualLogic or Celerra hardware.

Dynamic volume support

In Windows Server 2003 and Windows Server 2008:

◆ NMM supports snapshots of dynamic volumes that use the Microsoft Software Shadow Copy provider.

◆ NMM provides software-based support for: • Dynamic volume on a single disk.

• Dynamic volume spanning multiple disk.

◆ NMM does not support dynamic volumes in striping.

◆ NMM does not support hardware-based VSS transportable snapshots of dynamic volumes. NMM will attempt to perform a hardware-based VSS transportable snapshot when a proxy backup host is specified by using NSR_DATA_MOVER in the application information field of the Client resource.

For example, hardware-based transportable snapshots are not supported when the dynamic volumes are on CLARiiON storage. NMM will attempt to perform the hardware-based snapshot, but the operation will fail during import of the hardware-based snapshot on the proxy backup host.

IMPORTANT

!

(33)

The VSS snapshot creation process 33 Windows Server 2008 introduces support for local, hardware-based snapshots of dynamic volumes. NMM does not support local, nontransportable, hardware-based snapshots of dynamic volumes on Windows Server 2008. For customer environments where dynamic volumes are provisioned by using a storage array, customers must not install the storage array vendor’s VSS provider on the production host. For example, if a dynamic volume was created on a CLARiiON LUN, customers must not install the EMC VSS Hardware Provider on the production host.

Providers and backup performance

The Microsoft VSS software provider uses a copy-on-write snapshot technology. Some hardware providers, such as the EMC VSS Hardware Provider, support split-mirror snapshot technology and copy-on-write technology. Although

copy-on-write technology requires less hardware resources, split-mirror technology provides better performance.

Large or fast-changing databases should not be saved with copy-on-write snapshot technology. The input/output requirements of these databases can cause the copy-on-write cache to overflow and invalidate the snapshot. Additionally,

(34)

NMM client snapshot backups

Backups are configured as scheduled snapshot backups on a NetWorker server release 7.3.3 or later.

Note: Manual (adhoc) backups, from either the command line or from the NMM client, are not supported. However, one can manually start a scheduled backup at any time.

The NMM client supports three types of snapshot backups:

◆ “Nonpersistent rollover backup” on page 34

◆ “Instant backup with or without rollover” on page 34

◆ “Serverless backup” on page 34

Snapshot backups are specified through a snapshot policy and various settings for the Client resource. Snapshot policies and Client resources are set up on the NetWorker server. Chapter 2, “Configuring a Scheduled Backup,” provides more information about configuring snapshot policies and Client resources.

Nonpersistent rollover backup

A nonpersistent snapshot backup (also referred to as a live backup) creates a point-in-time snapshot of the data and then performs a rollover to a conventional backup medium such as tape, file, or advanced file type device. The original snapshot is automatically deleted from the NMM client.

Instant backup with or without rollover

An instant backup creates and retains a snapshot on a mounted storage disk volume. Depending on how backups are configured, a snapshot that is created during an instant backup may be configured to roll over to a conventional backup. While the snapshot resides on a mounted storage disk volume, it is referred to as a persistent snapshot.

Retention of persistent snapshots on a mounted storage disk volume enables one to perform an instant recovery. The number of persistent snapshots that can be retained on a volume depends on the amount of resources available. Other factors that constrain the number of persistent snapshots include:

◆ Snapshot technology that is used, either copy-on-write or split-mirror.

◆ Input/output patterns of the drive.

◆ Processing involved in running a snapshot backup group.

Serverless backup

A proxy client is used in conjunction with instant snapshot backups to provide

serverless backups. Serverless backups free the application server from much of the processing involved in a nonpersistent or instant snapshot backup. In a serverless backup, a snapshot is created on the application server and then immediately moved to the proxy client for further processing.

(35)

NMM client snapshot backups 35 run against the snapshot. Running eseutil can be disk intensive. Offloading the work from the Exchange Server to a proxy client frees resources on the Exchange Server. A serverless backup can be rolled over to a conventional backup. That backup can then remain on the mounted storage disk volume as a persistent snapshot.

(36)

NMM client recoveries

There are three types of recoveries:

◆ “Conventional recovery” on page 36

◆ “Instant recovery” on page 36

◆ “Rollback recovery” on page 36

By default, recoveries are performed from a conventional backup. If a conventional backup is not available for the selected browse time, an instant recovery is performed. The default recovery method can be specified in the NetWorker recovery options dialog box. “NetWorker recovery options” on page 89 provides more information about these recovery methods.

Conventional recovery

A conventional recovery consists of recovering data from a snapshot that has been rolled over to tape. Conventional recoveries support the same level of item selection as do instant recoveries.

Instant recovery

Instant recoveries are performed with persistent snapshots. An instant recovery can take less time to complete than a conventional recovery because the snapshot is available on a mounted disk storage volume rather than on a conventional backup medium.

Instant recoveries support the selection of individual files in a file system snapshot. Additionally, instant recoveries support the selection of individual components at whatever level of granularity is supported by the system or application writer. If the persistent snapshot is created by using a proxy client, the snapshot file system on the proxy client is read to restore the files. In this way, performance is improved even further because the job of processing the snapshot for recovery is off-loaded from the NMM client production host to the proxy client.

The procedure to perform an instant recovery of file system data differs if only a persistent snapshot is available. Chapter 4, “System Backup and Recovery,” provides more information about performing recoveries.

Note: When performing an instant recovery, the snapshot may become invalidated. This can occur if the snapshot is based on copy-on-write technology. If a large amount of data is recovered to the original volume, the cache may overflow. This is true for the Microsoft VSS software provider and for hardware providers that use copy-on-write technology, such as CLARiiON snapshots and Symmetrix virtual devices.

Rollback recovery

(37)

NMM client recoveries 37 For example, suppose that a snapshot of a database is taken every hour. At 5:30 P.M., it is determined that the database is corrupt and that the last known consistent database snapshot was taken at 5:00 P.M. When the database host is rolled back to the 5:00 P.M. snapshot, all database transactions between 5:00 P.M. and 5:30 P.M. are overwritten.

The following list describes additional requirements and conditions that apply to snapshots and rollback restore:

◆ The snapshot to be rolled back must reside on a CLARiiON or Symmetrix storage system that is supported with the EMC VSS Provider.

◆ The NMM client to which the snapshot is to be rolled back must be supported with a proxy client.

◆ NMM does not support rollback restore for backups performed with EqualLogic or Celerra hardware. Only conventional restore and snapshot restore are

supported for those hardware products.

“Roll back a snapshot” on page 327 provides more information about rollback recoveries.

Disaster and granular backup and recovery for applications

NMM provides disaster and granular backup and recovery for most applications:

◆ Full disaster backup and recovery means the entire volume or database for that application is backed up, and the entire volume or database is recovered as a whole.

◆ In disaster backup and recovery, items cannot be selected at a granular level.

◆ In granular backup, individual items can be selected for backup.

◆ In granular recovery, individual items can be selected for recovery.

(38)

Table 2 on page 38 lists the support provided by NMM for disaster and granular backup and recovery for Microsoft applications and volumes.

Table 2 Support for disaster and granular backup and recovery

(39)

The NMM client interface 39

The NMM client interface

The NMM client interface has three views:

◆ “Recover view” on page 39

◆ “Snapshot Management view” on page 41

◆ “Monitor view” on page 42

Recover view

With the exception of rollback recovery, all recoveries are performed from the Recover view. Rollback recoveries use the Snapshot Management view. Figure 5 on page 39 shows the Recover view.

Figure 5 NMM client main window

Navigation tree

View-specific toolbar Available views

Client selection (clustered client only) Main toolbar

(40)

The summary of selected items can also display exclusions, which shows only those items that are not selected for recovery. This view can be helpful when many items are selected for recovery. Figure 6 on page 40 shows an exclusion representation.

Figure 6 Exclusion representation of recover items

To view an exclusion representation, right-click in the summary pane at the bottom of the window and select Exclusion Representation.

(41)

The NMM client interface 41

Snapshot Management view

Various operations on snapshots are performed from the Snapshot Management view shown in Figure 7 on page 41.

Figure 7 Snapshot Management view

The following operations can be performed on snapshots:

◆ Rollover snapshot

◆ Rollback snapshot

◆ Delete snapshot

(42)

Monitor view

Recovery and snapshot management operations can be monitored in the Monitor view shown in Figure 8 on page 42.

Figure 8 Monitor view

(43)

NMM client graphical user interface 43

NMM client graphical user interface

This section describes how to perform the basic tasks in the NMM client interface.

Opening the software and connecting to a NetWorker server

You must first connect to the NetWorker server on which the backup was configured to recover data.

To connect to a NetWorker server:

1. From the Start menu, open the NMM client software:

• If you have opened the NMM client before, proceed to step 2 on page 43. • If this is the first time you have opened the NMM client, the Change

NetWorker Server dialog box appears, and you can proceed to step 3 on page 43.

2. From the Main toolbar, click the NetWorker Server icon. The Change NetWorker Server dialog box appears.

3. Click Update Server List to browse for NetWorker 7.3.3 or later servers. The discovery process may take a few minutes.

4. When the list is updated, select a server.

The selection appears in the Server field. You can also type a name in the Server field.

5. Click OK.

(44)

Selecting an item for recovery

To select items for recovery, select the checkbox beside a node in the navigation tree. A check mark indicates that the node is selected. By default, all items contained in the node, such as folders and files, will also be selected for recovery.

To clear an item contained in a selected node, expand the node and clear the checkbox beside the item. The check mark disappears.

Figure 9 on page 44 depicts one selected item and several partially selected nodes in the navigation tree.

Figure 9 Selected and partially selected items

Searching for an item

To search for a recovery item:

1. Click Search above the navigation tree. 2. In the Path field, type a directory path.

3. Optionally, in the Name field, type the name of the search item. You can refine your search as follows:

• Literal match (case-insensitive)

Type abc to return abc, ABC, or AbC but not abcd or ABCD. • Literal match (case-sensitive)

Type "abc" to return abc but not ABc or abcd. • Name contains (case-insensitive)

Type %abc% to return abc, abcd, ABCD, or xyzABCde. • Name starts with (case-insensitive)

Type abc% to return abcd or ABCde but not xyzABCde.

Check mark indicates that the item is selected. Solid box indicates that

(45)

NMM client graphical user interface 45 • Name ends with (case-insensitive)

Type %abc to return xyzAbc but not ABCde.

• Single-character match search using the ? wildcard

Type ? to return single character entries and drive volumes, such as C or D. Type WMI?Writer to return WMI Writer.

• Multiple-character match search by using the * wildcard Type *.txt to return all entries with a .txt extension. Type * to return all items within the selected container. Type *writer* to return all writers.

• Search by using both the * and ? wildcard Type *??I*writer* to return WMI Writer. 4. Click Search.

The Details pane displays the results of the search.

Specifying a recovery browse time

To browse for items that were backed up on or before a particular time: 1. From the application toolbar, click the Browse calendar icon. 2. Select the arrows to select the date and time, and then click OK.

The navigation tree displays backup items from the specified date and earlier.

Selecting a backup version for recovery

This topic applies to SharePoint granular recovery, DPM granular recovery, system recovery, or Active Directory recovery operations only. Chapter 14, “Snapshot Management,” provides more information about rollback snapshot recoveries. To view the versions of an item that were backed up prior to the current browse time: 1. In the navigation tree, select a recover item.

“Selecting an item for recovery” on page 44 provides more information about selecting an item.

2. Right-click the selected item and select Versions from the pop-up menu. 3. Select the backup version to recover.

4. Select Use selected item backup time as new browse time to change the browse time to the same date as the selected backup version.

5. Click OK.

(46)

Viewing the volumes required for a recovery

There are no NetWorker volumes associated with a snapshot backup until the snapshot has been rolled over to a NetWorker server. If you select to view the required volumes for a system component or application data snapshot that has not been rolled over, no volumes will be displayed.

To view the volumes that are required for a recovery operation: 1. In the navigation tree, select a recover item.

“Selecting an item for recovery” on page 44 provides more information about selecting an item.

2. Right-click the selected item and select Required Volumes from the pop-up menu.

The Required NetWorker Volumes dialog box appears with a list of the volumes that must be mounted:

• If a volume is already mounted, the device name is shown after the volume name.

• If a required volume is not mounted, the administrator is prompted to mount it after the recovery operation is started.

(47)

Configuring a Scheduled Backup 47 This chapter includes the following topics:

◆ Backup configuration roadmap ... 48

◆ Task 1: Configure a backup pool for snapshot operations ... 52

◆ Task 2: Configure snapshot policies ... 55

◆ Task 3: Configure a backup schedule ... 58

◆ Task 4: Configure a backup group ... 59

◆ Task 5: Configure a Client resource ... 61

◆ Task 6: Configure privileges ... 66

◆ Task 7: Configure a proxy client... 67

◆ Backing up a clustered NMM Client ... 69

◆ Moving an NMM Client to another NetWorker server ... 70

(48)

Backup configuration roadmap

This chapter describes the seven tasks required to configure most types of backups. Review Table 3 on page 48 to determine which tasks are required to configure your backups.

Table 3 Backup tasks (page 1 of 2)

Type of backup Required action

Windows volumes:

• Volume data such as a drive letter, for example: “D:\”

• A file system path, for example “D:\data” Windows system components, such as: • The registration database

• Windows Cluster, etc.

• Other Window system components, as listed in Table 1 on page 31.

Note: Specific Windows system components

do not have individual save sets. The Windows system components are all backed up under the save set “SYSTEM

COMPONENTS:\”

• Complete tasks 1 through 7:

“Task 1: Configure a backup pool for snapshot operations” on page 52

“Task 2: Configure snapshot policies” on page 55 “Task 3: Configure a backup schedule” on page 58 “Task 4: Configure a backup group” on page 59 “Task 5: Configure a Client resource” on page 61 “Task 6: Configure privileges” on page 66 “Task 7: Configure a proxy client” on page 67

Application data, such as: • Microsoft SQL Server • Microsoft SharePoint • Microsoft Exchange Server

• Microsoft System Center Data Protection Manager (DPM)

• Microsoft Hyper-V

• Microsoft Windows Server Cluster For example the save set

"APPLICATIONS:\SqlServerWriter"

“NetWorker Module features” on page 22

lists the specific versions supported for each of these applications.

• Complete tasks 1 through 4:

“Task 1: Configure a backup pool for snapshot operations” on page 52

“Task 2: Configure snapshot policies” on page 55 “Task 3: Configure a backup schedule” on page 58 “Task 4: Configure a backup group” on page 59

• Review the information in

“Best practices and considerations for backing up application data” on page 50.

• Continue configuration with the specific instructions for the application provided in:

“Performing SQL Server backups” on page 119 “Performing SharePoint 2003 backups” on page 157 “Performing SharePoint 2007 backups” on page 141 “Performing Exchange Server backups” on page 206 “Performing DPM Server backups” on page 255 “Performing Hyper-V backups” on page 284