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

(1)

EMC Corporation Corporate Headquarters: Hopkinton, MA 01748

-

9103 1

-

508

-

435

-

1000 www.EMC.com

Release 2.0

Administration Guide

P/N 300-006-314

REV A01

(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 listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

For the most up-to-date regulatory document for your product line, go to the Document/Whitepaper Library on EMC Powerlink

(3)

EMC NetWorker Module for Microsoft Applications Release 2.0 Administration Guide 3

Figures

Tables

Preface

Chapter 1 Overview

About the NetWorker Module for Microsoft Applications ... 18

NetWorker Module features ... 18

Privileged user level access ... 19

Supported configurations... 20

Supported NetWorker Server hosts... 20

Windows operating system support ... 20

Simple LAN-based configuration ... 21

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

LAN-free configuration ... 23

Understanding the VSS snapshot creation process ... 25

About writers ... 26

About providers... 28

Dynamic volume support ... 28

Providers and backup performance ... 28

NMM client snapshot backups ... 30

Nonpersistent rollover backup... 30

Instant backup with or without rollover... 30

Serverless backup ... 30

NMM client recoveries... 32

Conventional recovery... 32

Instant recovery ... 32

Rollback recovery ... 32

About the NMM client interface... 34

Recover view ... 34

Snapshot Management view... 36

Monitor view... 37

Using the NMM client graphical user interface ... 38

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

Selecting an item for recovery ... 39

Searching for an item ... 39

(4)

Selecting a backup version for recovery ... 40

Viewing the volumes required for a recovery ... 41

Chapter 2 Configuring a Scheduled Backup

Backup configuration roadmap ... 44

Privileged user level access ... 45

Name resolution... 46

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

Best practices for backing up system volumes ... 47

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

Configuring a device ... 48

Configuring a label template... 49

Configuring a backup pool... 49

Labeling the device ... 50

Task 2: Configure snapshot policies ... 51

Creating a snapshot policy ... 51

Snapshot policy examples... 53

Task 3: Configure a backup schedule ... 54

Task 4: Configure a backup group ... 55

Task 5: Configure a Client resource ... 57

Configuring a Client resource for applications ... 57

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

Cluster failover and backups... 67

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

Chapter 3 Recovering Data

Performing a recovery ... 70

NetWorker recovery options... 72

Cluster recovery options... 73

Authoritative recovery of a Windows Server 2008 cluster database after NMM upgrade, from a NetWorker 7.4 SP2 save set... 74

Non-authoritative recovery of a Windows Server 2008 cluster database, using a save set created with NetWorker 7.4 SP2... 75

ADAM recovery options... 75

DFS recovery options ... 76

FRS recovery options... 79

NTDS recovery options... 80

Security recovery options ... 82

(5)

Chapter 4 Microsoft SQL Server Backup and Recovery

Microsoft SQL Server backup and recovery ... 98

SQL Server versions supported by NMM... 98

Types of Backup and Recovery Supported... 98

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

Specifying save sets for SQL data ... 99

Displaying valid SQL data save sets... 100

URL encoding for SQL save sets ... 101

SQL application information variable settings ... 102

Serverless backup ... 102

Performing SQL Server backups ... 103

Performing SQL Server recovery... 105

Recovering SQL 2000 embedded databases ... 105

Recovering SQL 2000 stand-alone databases ... 106

Recovering SQL 2005 databases ... 106

Best practices for SQL backup and recovery ... 107

Chapter 5 Microsoft Office SharePoint Server Backup and Recovery

Microsoft Office SharePoint Server backup and recovery ... 110

SharePoint Server versions supported by NMM client ... 110

SharePoint backup and recovery types ... 110

Requirements for installing SharePoint service pack... 111

NMM installation requirements for a SharePoint system ... 111

SharePoint 2007 data backed up by NMM ... 113

Keeping backups and recoveries in sync ... 113

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

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

Displaying valid SharePoint 2007 data save sets ... 114

URL encoding for SharePoint save sets... 115

SharePoint 2007 Application information variable settings... 116

Performing SharePoint Server backups... 117

Configuring SharePoint 2007 backups ... 117

Task 5: Configure a SharePoint Client resource ... 118

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

Performing SharePoint 2007 recovery ... 124

Mandatory order for SharePoint recoveries ... 124

Selecting valid items for recovery ... 124

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

Full recovery of a distributed SharePoint farm... 124

Recovery of individual SharePoint Content Databases ... 126

Recovery of SharePoint Search/Content Indexes... 126

Rollback of SharePoint SQL databases... 127

SharePoint disaster recovery... 128

NMM backup of SharePoint servers... 128

Chapter 6 Microsoft Exchange Backup and Recovery

Microsoft Exchange Server backup and recovery... 132

Exchange Server versions supported by NMM client ... 132

Exchange backup and recovery types ... 132

Updating and modifying Exchange credentials ... 133

Compatibility with previous Exchange backups... 134

Exchange data backed up by NMM... 134

(6)

Specifying Exchange save sets for application data... 135

Exchange Application information variable settings ... 138

Serverless backup... 139

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

Best practices for Exchange backup and recovery ... 141

Performing Exchange Server backups ... 143

Configuring Exchange Server backups... 143

Task 5: Configure an Exchange Client resource... 144

Performing Exchange Server recovery... 146

Exchange recovery requirements and limitations... 146

Exchange recovery options... 147

Roll-forward recovery ... 147

Point-in-time recovery... 148

Mounting the database after recovery ... 149

Rollback restore of Exchange data using NMM... 150

Exchange rollback operation requirements ... 150

Chapter 7 Microsoft Data Protection Manager Backup and Recovery

Data Protection Manager backup and recovery ... 154

DPM Server versions supported by NMM client... 155

DPM backup and recovery types ... 155

DPM data backed up by NMM... 155

Transportable backups of DPM Replicas not supported ... 155

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

Specifying DPM save sets for application data ... 157

DPM application information variable settings ... 159

Performing DPM Server backups ... 160

Configuring DPM backups... 160

Task 5: Configure a DPM Client resource... 161

Performing DPM Server recovery ... 163

DPM configuration database recovery ... 163

DPM replica recovery... 163

Chapter 8 Microsoft Windows Cluster Backup and Recovery

Windows Server Cluster backup and recovery ... 166

Cluster support in NMM client... 166

Compatibility with previous Windows Cluster backups ... 166

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

Specifying Windows Cluster save sets for application data... 167

Displaying valid Windows Cluster data save sets... 167

(7)

Chapter 9 Active Directory and ADAM Backups

Active Directory backup and recovery... 178

Types of Backup and Recovery Supported ... 179

Performing an AD or ADAM backup... 180

Performing a granular AD or ADAM backup... 181

Set up local Windows SYSTEM account as an ADAM administrator.... 181

Granular backup tasks ... 182

Chapter 10 Active Directory Recover

Recovering all Active Directory data... 184

Performing a granular recovery of AD objects and attributes ... 186

Recovery Restrictions for Active Directory ... 187

Chapter 11 Snapshot Management

Roll over a snapshot ... 190

Roll back a snapshot... 191

Rollback recovery requirements... 191

Storage array descriptor file... 191

Performing a rollback recovery ... 193

Delete a snapshot ... 194

Chapter 12 NetWorker Client Management

Specifying ranges for service and connection ports ... 196

Specifying a password ... 197

Chapter 13 Troubleshooting

The troubleshooting process ... 200

Setting up notifications ... 201

Finding errors... 202

NMM client error messages ... 203

E_VOLUME_NOT_SUPPORTED ... 203

E_VETO_PROVIDER ... 203

VSS_E_WRITERERROR_RETRYABLE error code 0x800423f3 ... 203

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

NMM client issues ... 205

Savegroup failed in scheduled backup ... 205

In progress backup fails... 205

NetWorker is blocked by Windows Firewall ... 205

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

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

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

PowerSnap validation for recovery fails ... 207

Snapshot backup may fail with writer errors... 207

Microsoft I/O write error when taking a replica in a CLARiiON array 207 Creating a replica takes a long time in CLARiiON environment... 207

Cannot recover Exchange database due to overwrite prevention error 207 Incremental backups within NetWorker Module for Exchange Client may be promoted to full backups... 208

(8)

Incremental backups within NetWorker Module for

SQL Server Client may be promoted to full backups ... 208

Diagnosing VSS Writer Issues... 208

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

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

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

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

Anti-virus programs block recovery ... 211

Checking log files ... 212

NMM client ... 212 PowerSnap client... 212 Replication Manager... 213 Solutions Enabler ... 213 Active Directory ... 214 NetWorker server... 214

Manually stopping and starting services... 215

Other troubleshooting resources... 216

Glossary

(9)

Title Page

1 Simple LAN-based configuration ... 22

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

3 LAN-free configuration... 24

4 VSS backup process ... 26

5 NMM client main window ... 34

6 Exclusion representation of recover items ... 35

7 Snapshot Management view ... 36

8 Monitor view ... 37

9 Selected and partially selected items... 39

10 SharePoint 2007 stand-alone farm configuration ... 112

11 SharePoint 2007 distributed farm configuration ... 112

12 Restore Remote Dependencies dialog box ... 125

13 Snapshot process with Exchange production server and proxy client ... 141

14 NetWorker Module for Microsoft Applications protection of DPM ... 154

(10)

(11)

Title Page

1 Currently supported writers ... 27

2 Backup tasks ... 44

3 Best practices and considerations for application backups ... 46

4 Conventional backup settings ... 53

5 Instant snapshot policy ... 53

6 Instant snapshot with rollover policy ... 53

7 Considerations for NMM Client backup schedules... 54

8 Save set syntax... 60

9 Special characters and their URL-encoded values ... 62

10 Application information variable settings... 63

11 Configuration requirements for a proxy client... 65

12 Additional steps and considerations for backing up a clustered Client resource ... 67

13 SQL save set syntax... 99

15 SQL variable settings for Application information attribute... 102

16 SQL Server backup and recovery best practices and considerations ... 107

17 SharePoint save set syntax ... 114

19 SharePoint application information variable settings ... 116

20 Exchange save set syntax ... 135

22 Exchange application information variable settings... 138

23 NMM Data Protection Manager commands... 156

24 DPM save set syntax ... 157

26 DPM application information variable settings ... 159

27 Windows Cluster save set syntax ... 167

28 Windows Cluster application information variable settings... 168

29 Additional steps and considerations for backing up a clustered Client resource ... 169

30 Setting up a granular AD or ADAM backup ... 182

31 Notifications and errors ... 202

(12)

(13)

EMC NetWorker Module for Microsoft Applications Release 2.0 Administration Guide 13 Audience This guide is part of the 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

Overview

(18)

About the 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 provides the following features:

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

• “Simple LAN-based configuration” on page 21

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

• “LAN-free configuration” on page 23

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

• “Nonpersistent rollover backup” on page 30

• “Serverless backup” on page 30

• “Conventional recovery” on page 32

• “Instant recovery” on page 32

• “Rollback recovery” on page 32 ◆ Application support:

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

• Microsoft Office SharePoint Server 2007

• Microsoft System Center Data Protection Manager 2007 • Windows volumes and system components

• Windows Cluster support

(19)

About the NetWorker Module for Microsoft Applications 19 ◆ Windows VSS Provider support:

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

• DMX/Symmetrix®_{Arrays with EMC VSS Provider v3.4.0.0 or later}

• CLARiiON® Arrays with EMC VSS Provider v3.4.0.0 or later • Celerra® Arrays with Celerra VSS Provider v1.7.15

• EqualLogic PS Series Arrays with EqualLogic Integration ToolKit v3.0 or later The EMC Information Protection Software Compatibility Guide contains additional and the most up-to-date information about NMM compatibility.

Privileged user level access

All NMM users who will be running or configuring NMM backups and recoveries must have administrator-level privileges for all resources they access:

◆ The NetWorker server

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

◆ All applications protected by NMM, such as Microsoft Windows Server, Microsoft Data Protection Manager (DPM), Microsoft Office SharePoint Server, Microsoft SQL Server, and Microsoft Exchange Server

◆ Network domains

(20)

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 on the following hosts:

◆ AIX

◆ HP-UX (PA-RISC)

◆ Solaris (SPARC)

◆ Windows

Note: The NMM Client is not supported from NetWorker Server running on Linux.

The following NetWorker features are not supported:

◆ NetWorker Clone, Staging and Archive.

◆ Directed Recovery.

◆ Internationalization (I18N) or Localization (L10N).

◆ Installation of dedicated Storage Node on NMM client host. NMM does support proxy storage node, as described in “LAN-free configuration” on page 23.

◆ Adhoc/Manual Backups.

◆ De-duplication.

Windows operating system support

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

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

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

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

◆ Microsoft Windows Storage Server 2003

◆ Microsoft Windows Storage Server 2003 R2

(21)

Supported configurations 21 ◆ EMC VSS Hardware Provider with Windows Server 2008.

◆ EMC VSS Provider for Celerra with Windows Server 2008.

◆ VSS Hardware Providers with Windows dynamic disks.

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

◆ Windows Automated System Recovery (ASR).

◆ Windows Storage Server Single Instance Storage (SIS) is supported, but recoveries will recover file data for all duplicate file—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 22 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. 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 the figure, snapshots are represented by S1 through S5.

3. The application server with the NMM client software uses a snapshot in primary storage to transfer the data over the LAN and into a conventional backup medium such as a file type disk, advanced file type disk, or tape.

(22)

Figure 1 Simple LAN-based configuration

LAN-based configuration with a proxy client

Figure 2 on page 23 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.

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

serverless backup.

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

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

(23)

Supported configurations 23 Figure 2 LAN-based configuration with a proxy client

LAN-free configuration

Figure 3 on page 24 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 version 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.

Note: In the figure, snapshots are represented by S1 through S5.

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.

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

(24)

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.

Figure 3 LAN-free configuration LAN 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 Storage Node 7.3.x SAN GEN-000750

(25)

Understanding the VSS snapshot creation process 25

Understanding the VSS snapshot creation process

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

◆ Requestors

Requestors include the NetWorker backup application.

◆ Writers

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

◆ Providers

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

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

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

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

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

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

1. The VSS software does the following:

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

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

a. Captures the prepared data.

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

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

during the provider's work are processed.

(26)

Figure 4 VSS backup process

About 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 Microsoft VSS Software Provider EMC VSS Provider (CLARiiON or Symmetrix) Disk 3 GEN-000188

(27)

Understanding the VSS snapshot creation process 27 Table 1 on page 27 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. 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 ADAM (Active Directory Application Mode)

Microsoft Exchange Server 2003

Microsoft Exchange Server 2007

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

Microsoft SQL Server 2000 Microsoft SQL Server 2005 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 2008) Cluster service

DHCP (Dynamic Host Configuration Protocol) Jet Event log

FRS (File Replication Server)

FSRM (File Storage Resource Manager)

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

IIS Metabase

MSDE (Microsoft SQL Server Desktop Engine for SQL 2000 embedded databases)

MSSearch Service Writer (Windows Server 2008)

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

NTDS (Active Directory Schema) Registry

RSM (Removable Storage Manager) Remote Storage Manager

Shadow Copy Optimization Writer (Windows Server 2008) SQL 2005 Embedded

Terminal Services Gateway Writer (Windows Server 2008) Terminal Services Licensing

WINS (Windows Internet Name Service) WMI (Windows Management Instrumentation)

(28)

About providers

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

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

◆ Celerra VSS Hardware Provider, which supports Celerra arrays

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

◆ Microsoft Software Shadow Copy provider

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 only available with hardware providers such as the EMC VSS Hardware Provider.

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

NMM supports snapshots of dynamic volumes using the Microsoft Software Shadow Copy provider. This support applies to both Windows Server 2003 and Windows Server 2008.

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 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. This condition applies to both Windows Server 2003 and Windows Server 2008.

Windows Server 2008 introduces support for local, hardware-based snapshots of dynamic volumes. NMM does not support local non-transportable hardware-based snapshots of dynamic volumes on Windows Server 2008. For customer environments where dynamic volumes are provisioned 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.

(29)

Understanding the VSS snapshot creation process 29

copy-on-write cache to overflow and invalidate the snapshot. Additionally,

copy-on-write technology cannot match the performance of split-mirror technology. For large or fast-changing databases, use the EMC VSS Hardware Provider in conjunction with EMC hardware to provide a split-mirror storage solution such as a CLARiiON clone or a Symmetrix BCV.

(30)

NMM client snapshot backups

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

Note: Ad hoc (manual) 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 30

◆ “Instant backup with or without rollover” on page 30 ◆ “Serverless backup” on page 30

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

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

(31)

NMM client snapshot backups 31

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

Note: Serverless backup is available only with VSS hardware providers and is subject to the capabilities of the vendor’s hardware. The EMC VSS Provider for CLARiiON and Symmetrix provides the capability to perform serverless backup operations for these storage platforms.

(32)

NMM client recoveries

There are three types of recoveries:

◆ “Conventional recovery” on page 32 ◆ “Instant recovery” on page 32 ◆ “Rollback recovery” on page 32

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 72 provides more information about these recovery methods.

Conventional recovery

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

Instant recovery

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

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

The procedure to perform an instant recovery of file system data differs if only a persistent snapshot is available. Chapter 3, “Recovering Data,” provides more information about performing recoveries.

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

(33)

NMM client recoveries 33

A rollback recovery is known as a "destructive" recovery because all changes that were made to the file systems after the selected snapshot was taken are overwritten. For example, suppose that a snapshot of a database is taken every hour. At 5:30 P.M., it is determined that the database is corrupt and that the last known consistent database snapshot was taken at 5:00 P.M. When the database host is rolled back to the 5:00 P.M. snapshot, all database transactions between the time of the 5:00 P.M. and 5:30 are overwritten.

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

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

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

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

supported for those hardware.

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

(34)

About the NMM client interface

The NMM client interface has three views:

◆ “Recover view” on page 34

◆ “Snapshot Management view” on page 36 ◆ “Monitor view” on page 37

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 34 shows the Recover view.

Navigation tree Client selection

(clustered client only) Main toolbar

(35)

About the NMM client interface 35

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

Items in red are excluded from recovery

(36)

Snapshot Management view

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

Figure 7 Snapshot Management view

The following operations can be performed on snapshots:

◆ Rollover snapshot

◆ Rollback snapshot

◆ Delete snapshot

In most cases, snapshot rollover and delete operations are performed automatically based on snapshot policies, which are set up on the NetWorker server. However, if you need to manually delete or rollover a snapshot, you can do so in the Snapshot Management view. Chapter 2, “Configuring a Scheduled Backup,” provides more information about snapshot policies. Chapter 11, “Snapshot Management,” provides more information about performing manual snapshot operations from the Snapshot Management view.

(37)

About the NMM client interface 37

Monitor view

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

Figure 8 Monitor view

Most messages displayed in the Monitor view are also written to log files. Chapter 13, “Troubleshooting,” provides more information about log files. You can also copy and paste text from the Monitor view to another application.

(38)

Using the NMM client graphical user interface

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

Opening the software and connecting to a NetWorker server

To recover data, you must connect to the NetWorker server on which the backup was configured.

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

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

Note: You can also select Configure Options from the Options menu to connect to a NetWorker server.

(39)

Using the NMM client graphical user interface 39

Selecting an item for recovery

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

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

Figure 9 on page 39 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. • Name ends with (case-insensitive)

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

some items, not all, below this node are selected

(40)

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; click OK.

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

Selecting a backup version for recovery

This topic applies to system recovery or Active Directory recovery operations only.

“Snapshot Management” on page 189 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 39 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.

(41)

Using the NMM client graphical user interface 41

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

(42)

(43)

Configuring a Scheduled Backup 43

This chapter includes the following topics:

◆ Backup configuration roadmap ... 44 ◆ Task 1: Configure a backup pool for snapshot operations ... 48 ◆ Task 2: Configure snapshot policies ... 51 ◆ Task 3: Configure a backup schedule ... 54 ◆ Task 4: Configure a backup group ... 55 ◆ Task 5: Configure a Client resource ... 57 ◆ Task 6: Configure privileges ... 64 ◆ Task 7: Configure a proxy client... 65 ◆ Backing up a clustered NMM Client ... 67 ◆ Moving an NMM Client to another NetWorker server ... 68

Configuring a

Scheduled Backup

(44)

Backup configuration roadmap

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

Table 2 Backup tasks (page 1 of 2)

Type of backup Required action

Windows operating system: • Volume data such as a drive letter. • Windows system components, such as

the registration database.

• Complete tasks 1 through 7:

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

“Task 2: Configure snapshot policies” on page 51 “Task 3: Configure a backup schedule” on page 54 “Task 4: Configure a backup group” on page 55 “Task 5: Configure a Client resource” on page 57 “Task 6: Configure privileges” on page 64 “Task 7: Configure a proxy client” on page 65

Application data, such as: • Microsoft SQL Server

• Microsoft Office SharePoint Server • Microsoft Exchange Server

• Microsoft System Center Data Protection Manager (DPM)

• Microsoft Windows Server Cluster

“NetWorker Module features” on page 18

lists the specific versions supported for each of these applications.

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

• Review the information in

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

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

“Performing SQL Server backups” on page 103

“Performing SharePoint Server backups” on page 117 “Performing Exchange Server backups” on page 143

“Performing DPM Server backups” on page 160

(45)

Backup configuration roadmap 45

Privileged user level access

Because NMM requires access to protected data and system files, make sure all users who will be running or configuring NMM backups and recoveries have

administrator-level privileges for all resources they must access:

◆ The NetWorker server

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

◆ All applications protected by NMM, such as Windows Server, DPM, Microsoft Office SharePoint Server, Microsoft SQL Server, and Microsoft Exchange Server

◆ Network domains

◆ Storage servers

For all other applications and systems supported by NMM

A NMM client that is part of a cluster • Review the information in “Backing up a clustered NMM Client” on page 67

• Complete tasks 1 through 7.

An Active Directory server Complete Chapter 9, “Active Directory and ADAM Backups.”

Table 2 Backup tasks (page 2 of 2)

(46)

Name resolution

NetWorker and the NMM client need proper name resolution to identify and

back-translate computer names, such as from name-to-IP address or IP address-to-name. Also, NMM Client uses the host machine NETBIOS or “short” name when

connecting to the NetWorker server to browse backups. If the NETBIOS name is not found, NMM will not be able to display backups. To ensure clear communication of computer names, make sure to perform the following:

◆ Add the NetWorker server name to either the local hosts file (located in

%SystemRoot%\system32\drivers\etc) or the Domain Name Server that contains

the names of all servers on your network.

◆ When configuring a Client resource, specify the NETBIOS name for the client in the Aliases attribute. “Configuring a Client resource for applications” on page 57

describes how to enter the NETBIOS name in the Aliases attribute.

Best practices and considerations for backing up application data

Table 3 on page 46 lists the considerations for specifying values in the Save Set attribute for a particular Client resource.

Table 3 Best practices and considerations for application backups

Consideration Best practice

Different policies for application server data

For application servers such as SQL or Exchange servers, back up the server application data under a schedule different than the host operating system data and volumes. Typically, application data is backed up several times a day while operating system data and volumes are backed up less frequently. To accomplish this, create a separate backup group, snapshot policy, and Client resource for:

• Server application data

• Volumes and operating system data

Assign the appropriate snapshot policy and Client resource to each backup group.

Installation path for application server program

Do not install application server program files on the same volume as the application’s database files and log files.

Copy-on-write versus mirroring

Large or fast-changing databases should not be saved with Copy-on-write snapshot technology. Instead, use a split-mirror snapshot technology such as a CLARiiON clone or a Symmetrix BCV.

Although copy-on-write technology requires less hardware resources, split-mirror technology can better handle the requirements of large or fast-changing databases.

(47)

Backup configuration roadmap 47

In addition to these best practices for all NetWorker Module for Microsoft Applications(NMM) backups, there are application-specific best practices:

◆ “Best practices for Exchange backup and recovery” on page 141 ◆ “Best practices for SQL backup and recovery” on page 107

Best practices for backing up system volumes

To protect against a disaster, ensure that all volumes and Windows system

components are backed up. Also ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of first, last, or all. Do not specify none. Disaster recovery can only be performed from a conventional backup. “Creating a snapshot policy” on page 51 provides more information about snapshot policies and values.

(48)

Task 1: Configure a backup pool for snapshot operations

Snapshots create metadata that is used in the management of snapshot operations such as an instant recovery operation. Create a snapshot pool to store the save sets that contain snapshot metadata.

Configuring a backup pool is a four-part process: 1. “Configuring a device” on page 48

2. “Configuring a label template” on page 49

3. “Configuring a backup pool” on page 49

4. “Labeling the device” on page 50

Note: All of the procedures in this section must be performed on a NetWorker server release 7.3.3 or later. Access the NetWorker server from the Administration window of the NetWorker Management Console.

The EMC NetWorker Release 7.4 Service Pack 1 Multiplatform Version Administration

Guide provides more detailed information about performing the steps included here.

Configuring a device

Configure a media device for snapshot metadata. Configure a tape, file, or advanced file type device. For best performance, configure a file or advanced file type device so that a snapshot can be recovered without the potential delay associated with

retrieving a tape. To configure a device:

1. In the NetWorker Administration window of the NetWorker Management

Console, click Devices on the taskbar. 2. In the expanded left pane, select Devices. 3. From the File menu, select New.

4. In the Name attribute, replace the default name with the path and name of the device:

• If the device is configured on the NetWorker server’s storage node, the name is the simple device path, such as C:\tmp\d0 for a file type device.

A tape device would have a format similar to \\.\Tape0.

• If the device is configured on a remote storage node, the name must indicate that the storage node is remote, by including rd= and the name of the remote storage node in the device path. For example, if the remote storage node is

(49)

Task 1: Configure a backup pool for snapshot operations 49

Configuring a label template

Labels identify the kind of data that is stored on the volumes in a backup pool. Label templates define a naming convention for labels. Create a label template for volumes that are used to contain snapshot metadata.

To configure a label template:

1. In the Administration window of the NetWorker Management Console, click

Media.

2. In the expanded left pane, select Label Templates. 3. From the File menu, select New.

4. In the Name attribute, type a name that identifies the series of labels as belonging to volumes for snapshot metadata.

5. In the Comment attribute, specify a comment for the label.

6. In the Fields attribute, specify a text name such as Snapshot_Metadata and on a separate line, specify a numeric range such as 001-999 or a text range such as

aa-zz.

These attributes are used to incrementally identify each label. 7. Click OK.

Configuring a backup pool

To configure a backup pool to store snapshot metadata:

Media.

2. In the expanded left pane, select Media Pools. 3. From the File menu, select New.

4. For the Name attribute, type a name that matches the label template. 5. In the Comment attribute, specify a comment for the pool.

6. Select the Enabled attribute.

7. For the Pool type attribute, select the backup pool type.

8. For the Label template attribute, select the matching label template. 9. Do not select a group in the Groups attribute.

Do not associate the pool with a particular group. This pool may be associated with several backup groups, so a single group should not be specified here. 10. Click the Selection Criteria tab.

11. For the Clients attribute, specify a NMM Client. A value must be entered for this attribute because no group was specified.

12. In the Devices attribute, select each device that can accept snapshot rollovers for this pool.

(50)

Labeling the device

Before a device can be used for backup, it must be labeled. To label a device:

Devices.

2. In the right pane, right-click on the name of the device and select Label. 3. In the Pool attribute, select the backup pool that was created.

4. Select the Mount after Labeling attribute. 5. Click OK.

(51)

Task 2: Configure snapshot policies 51

Task 2: Configure snapshot policies

A snapshot policy determines the following:

◆ When and how often snapshots are created

◆ Number of snapshots, and if any are retained as persistent snapshots

◆ Which snapshots, if any, are rolled over to conventional storage

◆ When snapshots expire and become eligible for deletion

Note: Snapshots can also be manually rolled over or deleted. Chapter 11, “Snapshot Management,” describes these procedures in more detail.

You can specify a preconfigured policy or create a custom snapshot policy. The following preconfigured snapshot policies exist:

◆ Serverless

A single snapshot is taken per day. The data is then rolled over to conventional storage and the snapshot is deleted.

◆ Daily

Eight snapshots are taken per day. The data in the first snapshot is rolled over to conventional storage. Each snapshot has 24-hour expiration policy.

CAUTION

!

To protect against a disaster, ensure that all volumes and Windows system components are backed up. Also ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of “first,” “last,” or “all.” Do not specify “none.” Disaster recovery can only be performed from a conventional backup.

Creating a snapshot policy

To create a custom snapshot policy:

Configuration.

2. In the expanded left pane, select Snapshot Policies. 3. From the File menu, select New.

4. In the Name attribute, type a name for the snapshot policy.

(52)

6. In the Number of Snapshots attribute, enter the number of snapshots to be created per day.

The Number of Snapshots attribute works in conjunction with the Group resource Interval and Start Time attributes. The value for the Start Time and Interval attributes must allow the specified number of snapshots to be created in a 24-hour period. For example, to take four snapshots per day and the first snapshot must occur at 4:00 A.M. (Start Time attribute), the Interval attribute must be set to 5 hours or less.

Number of Snapshots < (24:00 - Start Time) / Interval

“Task 4: Configure a backup group” on page 55 provides additional information about Snapshots and policies.

7. In the Retain Snapshots attribute, enter the maximum number of snapshots that can be retained for a specified period of time before being expired. The period of time is specified in the Snapshot Expiration Policy attribute.

Note: Use a minimum Retain Snapshot value of 2. This will insure that the most recent snapshot is retained while the new snapshot is created. A Retain Snapshot value of 1 will delete the only snapshot copy while creating the new snapshot.

8. In the Snapshots Expiration Policy attribute, select a preconfigured expiration policy to determine how long snapshots can be retained before being deleted. 9. In the Backup Snapshots attribute, specify which snapshots will be rolled over to

a conventional storage medium.

Valid values are All, None, First, Last, Every n.

CAUTION

!

To protect against a disaster, ensure that all volumes and Windows system components are backed up. Also ensure that the associated snapshot policy includes at least one rollover to a conventional backup. The snapshot policy for volumes and Windows system components should specify in the Backup Snapshots field a value of “first,” “last,” or “all.” Do not specify “none.” Disaster recovery can only be performed from a conventional backup.

If the Backup Snapshot attribute is set to None, you can still roll over the snapshot manually. Chapter 11, “Snapshot Management,” provides additional information about Snapshots.

10. Click OK.

Note: For Data Protection Manager backups the Backup Snapshot policy must be set to All. Backup will fail if any other value is used.

(53)

Task 2: Configure snapshot policies 53

Snapshot policy examples

Table 4 on page 53 depicts settings for a conventional backup. Four snapshots per day are taken. All snapshots are rolled over to a conventional storage medium. Each snapshot is deleted after it is rolled over.

Table 5 on page 53 depicts settings for an instant backup. Four snapshots per day are taken. Up to 28 snapshots are retained for a maximum period of one week. No snapshots are rolled over.

Table 6 on page 53 depicts settings for an instant backup with rollover to a conventional medium. Four snapshots per day are taken. Up to 28 snapshots are retained for a maximum period of one week. Every first and third snapshots are rolled over.

Table 4 Conventional backup settings

Name Conventional backup

Comment Rollover and then delete.

Number of snapshots 4

Retain snapshots 0

Snapshot expiration policy Day

Backup snapshots All

Table 5 Instant snapshot policy

Name Instant backup

Comment Persistent snapshots with no rollovers.

Retain snapshots 28 Snapshot expiration policy Week

Backup snapshots None

Table 6 Instant snapshot with rollover policy

Name Instant and conventional backup

Comment Persistent snapshots with rollover to tape.

Retain snapshots 28 Snapshot expiration policy Week

Backup snapshots Every 1 (press Enter) Every 3

(54)

Task 3: Configure a backup schedule

Backup schedules determine the days on which full or incremental backups are run. Full backups include all of the data specified in an NMM Client resource save set, while incremental backups include only the data that has changed since the last backup.

Table 7 on page 54 contains the considerations for configuring a backup schedule for an NMM Client. The procedure for creating backup schedules for an NMM Client is the same as for creating a backup schedule for a regular NetWorker client.

Note: The information in Table 7 on page 54 applies only to rollover backup operations. Snapshots are always taken at full level.

Table 7 Considerations for NMM Client backup schedules

Backup levels Consideration

Full level These backups are supported for all types of data. Incremental

backups

These are supported only for backup of volume directories or paths such as E:\ or E:\business_files\.

Level 1 to 9 backups

These are supported only for backup of volume directories or paths such as E:\ or E:\business_files\.