for Exchange Server VSS NetWorker Module for Microsoft · PDF fileExchange Server 2010 and 2013 DAGs ... Mounting the database after recovery ... l NetWorker Module for Microsoft for

EMC® NetWorker® Module for Microsoftfor Exchange Server VSSVersion 8.2 Service Pack 1

User Guide302-001-233

REV 04

Copyright © 2007-2016 EMC Corporation All rights reserved.

Published November 2016

Dell believes the information in this publication is accurate as of its publication date. The information is subject to changewithout notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS ORWARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLYDISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE,COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES ANAPPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property oftheir respective owners. Published in the USA.

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC NetWorker Module for Microsoft for Exchange Server VSS 8.2 Service Pack 1 User Guide

7

9

11

Introduction 15Overview.....................................................................................................16Microsoft Exchange Server environments.................................................. 16

Stand-alone and single Exchange Servers...................................... 16Exchange Server 2007 clusters...................................................... 17Exchange Server 2010 and 2013 DAGs........................................... 18Supported high availability configurations...................................... 19

Using NMM in an Exchange Server environment........................................24Exchange Server 2007 and Exchange Server 2010 VSS Writers....24Exchange Server 2013 VSS Writer................................................ 25Compatibility with previous Exchange backups............................. 25Backup initiated transaction log file truncation.............................. 26Backup types and levels.................................................................26Federated backup.......................................................................... 27Recovery types..............................................................................27

Configuration 29Supported Exchange server deployment scenarios and limitations.............30

Supported Exchange server versions.............................................30Supported high-availability deployments........................................ 31Windows Small Business Server..................................................... 31Single server Microsoft Exchange Server and Microsoft SharePointServer installations.........................................................................31Exchange Server 2007 storage groups.......................................... 32Delivery status notifications (DSNs) for Exchange server DAGenvironments.................................................................................32Backup and recover limitation to standalone mailbox server in aDAG...............................................................................................32

NMM prerequisites.....................................................................................32Exchange server hardware requirements.......................................32Required permissions.....................................................................33MAPI client and Collaboration Data Objects.................................. 34Exchange backup prerequisites..................................................... 35Exchange recovery prerequisites...................................................36Exchange Server 2007 CCR requirements.....................................36Additional requirements for recovering databases in a DAG...........37Additional requirements for browsing mailboxes............................ 37Exchange Consistency Check........................................................38Configuring a DSN for Exchange Server........................................39

Figures

Tables

Preface

Chapter 1

Chapter 2

CONTENTS

EMC NetWorker Module for Microsoft for Exchange Server VSS 8.2 Service Pack 1 User Guide 3

Backup 41Planning backups........................................................................................42

Backup requirements.....................................................................42Backup considerations...................................................................43Planning DAG and non-DAG backups.............................................43Exchange Information Store backup..............................................46Backing up highly available Exchange server..................................47Backing up circular logging-enabled databases.............................. 47Achieving the maximum number of save sessions..........................48Persistent and non-persistent snapshots.......................................48Shadow copy and log truncation....................................................48Using NMM with Client Direct to AFTD or Data Domain Booststorage devices............................................................................. 48

Configuring Exchange backups...................................................................49Backup configuration options........................................................ 50Configuring a backup pool..............................................................51Configuring snapshot policies........................................................ 52Configuring a backup schedule...................................................... 53Configuring a backup group...........................................................54Configuring Exchange client resources..........................................56Configuring NetWorker administrator privileges............................ 70Configuring a non-federated or federated DAG backup..................71Excluding Exchange databases from backup..................................72Configuring Exchange 2007 storage groups.................................. 73Configuring Avamar deduplication backups in a CCR Passive nodebackup or DAG environment.......................................................... 74Complete list of Exchange Server Application Information attributes...................................................................................................... 75Viewing a valid application data save set........................................79Circumstances that promote incremental backup to full backup....82

Performing an Exchange Server scheduled backup.................................... 82Using federated DAG backups on Exchange Server 2010 andExchange Server 2013................................................................... 83

Verifying a backup......................................................................................85

Mail Item Recovery 87Overview.................................................................................................... 88

Recovery types..............................................................................88Restoring Exchange data...............................................................88Recovering individual mailboxes, mailbox folders, and messages... 90

Exchange recovery prerequisites................................................................94Additional requirements for browsing mailboxes............................94Additional requirements for recovering databases in a DAG.......... 95

Configuring Exchange Server recovery...................................................... 95Specifying Exchange recovery options.......................................... 95Configuring roll-forward recovery of an Exchange Server 2010 orExchange Server 2013 server in a DAG environment..................... 96Configuring roll-forward recovery in an Exchange Server 2007 CCRenvironment.................................................................................. 98Configuring for point-in-time recovery in an Exchange Server 2007CCR environment.......................................................................... 99

Recovery procedures................................................................................ 100Recovering NetWorker Module for Microsoft Exchange backups....100Mounting the database after recovery......................................... 100

Chapter 3

Chapter 4

CONTENTS


Performing Exchange 2007 recovery........................................... 100Performing Exchange Server 2010 and 2013 recovery.................. 112Recovering a deleted Exchange Server mailbox database or publicfolder database............................................................................. 118Performing a quick recovery of a deleted mailbox.........................119Recovering Exchange Server mailbox, public folder, or public foldermailbox database files.................................................................. 120

Best practices and recommendations........................................................122Exchange recovery limitations......................................................122

Granular Level Recovery 125Recovering Mailbox items with Granular Level Recovery (GLR)............... 126

GLR considerations...................................................................... 126Recovering individual mailbox items using Granular Level Recovery(GLR)........................................................................................... 127Performing a GLR to an alternate mailbox.................................... 129Performing a GLR on an archive user mailbox.............................. 130Performing a GLR to a PST.......................................................... 130

Troubleshooting 133Troubleshooting general errors................................................................. 134Troubleshooting backups.......................................................................... 135Troubleshooting recovery......................................................................... 138

143

Chapter 5

Chapter 6

Glossary

CONTENTS


CONTENTS


NetWorker and NMM installation in a single Exchange Server environment................17NetWorker and NMM installation in an Exchange Server 2007 cluster environment....................................................................................................................................18NetWorker and NMM installation with a DAG in Exchange Server 2010 or 2013environment................................................................................................................ 19A typical LCR deployment.......................................................................................... 20CCR deployment......................................................................................................... 21CCR combined with SCR deployment.........................................................................22Windows cluster (Exchange SCC) deployment...........................................................22Exchange Server DAG environment............................................................................23NMM installation in an Exchange Server 2007 cluster................................................24Group Properties dialog..............................................................................................55Initial screen of Client Backup Configuration wizard...................................................63Example of an Exchange Server 2010 and 2013 Federated backup.............................85Recovery in a stand-alone Exchange Server environment.......................................... 89Recovery to an alternate location in a stand-alone Exchange Server environment..... 90Recover using NMM granular level recovery.............................................................. 92Recover to an RSG/RDB, and then recover data from the RSG/RDB to a user mailbox................................................................................................................................... 93Selecting an Exchange storage group....................................................................... 103Recovery storage group configuration error..............................................................104Selecting mail messages and nodes...........................................................................106Select Viewable Clients dialog................................................................................... 110Select Storage Group Restore Destination dialog.......................................................111Advanced Recovery dialog......................................................................................... 113Exchange Recovery Summary dialog......................................................................... 115Manage RDB dialog....................................................................................................115Create RDB dialog..................................................................................................... 115Delete confirmation dialog box...................................................................................116Select Database dialog box........................................................................................ 117Select Server dialog...................................................................................................118Individual mailbox databases..................................................................................... 128Sample mailbox......................................................................................................... 129

12

3

45678910111213141516

1718192021222324252627282930

FIGURES


FIGURES


Revision history...........................................................................................................12Exchange Server Storage types.................................................................................. 16Writers used by NMM for Exchange Server backup and recovery.............................. 24Exchange Server 2013 VSS writer.............................................................................. 25Exchange Server backup levels...................................................................................27Supported Microsoft Exchange server versions and operating systems ................... 30NMM support for highly available Exchange server.....................................................31Exchange server hardware requirements ..................................................................32Permissions for Exchange Backup and Recovery........................................................33Exchange Server GLR MAPI/CDO requirements........................................................35Exchange application information variables for threading and throttling ....................39Considerations required for backup in a non-DAG and DAG environment................... 43Configuration Tasks for an Exchange Server backup .................................................49Backup options for Exchange Server 2010 and Exchange Server 2013 ......................50Considerations for NMM client backup schedules...................................................... 53Procedures for backing up Exchange Server 2010 and 2013 DAGs............................. 56Procedures for backing up Exchange 2007databases.................................................56Exchange Server name attributes ..............................................................................58Exchange Server 2007 save set names ......................................................................59Exchange 2010 save set names.................................................................................. 59Exchange 2013 save set names.................................................................................. 60Application Information attributes for Exchange Server ............................................ 60Exchange Application Information attribute settings.................................................. 75Commands for displaying valid application data save sets...........................................79Special characters and their URL-encoded values.......................................................81PowerShell cmdlets for restored mailboxes...............................................................135

1234567891011121314151617181920212223242526

TABLES


TABLES


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions ofits software and hardware. Therefore, some functions described in this documentmight not be supported by all versions of the software or hardware currently in use.The product release notes provide the most up-to-date information on productfeatures.

Contact your EMC technical support professional if a product does not functionproperly or does not function as described in this document.

Note

This document was accurate at publication time. Go to EMC Online Support (https://support.emc.com) to ensure that you are using the latest version of this document.

PurposeThis guide contains information about using the NetWorker Module for Microsoft(NMM) software to back up and recover Microsoft Exchange Server using the VolumeShadow Copy Service (VSS) technology.

Note

The NetWorker Module for Microsoft Administration Guide supplements the backup andrecovery procedures described in this guide and must be referred to when performingapplication-specific tasks. Ensure to download a copy of the NetWorker Module forMicrosoft Administration Guide from EMC Online Support (https://support.emc.com)before using this guide.

AudienceThis guide is part of the NetWorker Module for Microsoft documentation set, and isintended for use by system administrators during the setup and maintenance of theproduct. Readers should be familiar with the following technologies used in backupand recovery:

l EMC NetWorker software

l EMC NetWorker snapshot management

l Microsoft Volume Shadow Copy Service (VSS) technology


https://support.emc.com/



Revision historyThe following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

04 November, 2016 Updated the following sections:

l Updated the "Troubleshooting Recovery" sectionto document the procedure to verify that ClientDirect is enabled

l Updated the "Troubleshooting Backups" section.

03 July, 2016 Updated the following sections:

l "MAPI client and Collaboration Data Objects"

l "Troubleshooting recovery"

02 March 3, 2016 Removed content on Client Direct file Access (DFA)backups from the "Exchange Server 2010 and 2013DAGs" section. The restriction is not applicable forNMM 8.2 and later.

01 January 2015 First release of this document for EMC NetWorkerModule for Microsoft release 8.2 SP1

Related documentationThe NMM documentation set includes the following publications:

l NetWorker Module for Microsoft Release Notes

l NetWorker Module for Microsoft Administration Guide

l NetWorker Module for Microsoft Installation Guide

l NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide

l NetWorker Module for Microsoft for SQL VDI User Guide

l NetWorker Module for Microsoft for Exchange VSS User Guide

l NetWorker Module for Microsoft for Hyper-V VSS User Guide

l NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution UserGuide

l NetWorker Module for Microsoft Advanced Recovery Guide

l NetWorker Performing backup and recovery of SharePoint Server by using NetWorkerModule for Microsoft SQL VDI solution Technical Notes

l NetWorker Performing Exchange Server Granular Recovery by using NetWorkerModule for Microsoft with Ontrack PowerControls Technical Notes

l NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module forMicrosoft and Metalogix StoragePoint Technical Notes

Special notice conventions used in this documentEMC uses the following conventions for special notices:

NOTICE

Addresses practices not related to personal injury.

Preface


Note

Presents information that is important, but not hazard-related.

Typographical conventionsEMC uses the following type style conventions in this document:

Italic Use for full titles of publications referenced in text

Monospace Use for:

l System code

l System output, such as an error message or script

l Pathnames, file names, prompts, and syntax

l Commands and options

Monospace italic Use for variables

Monospace bold Use for user input

[ ] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{ } Braces enclose content that the user must specify, such as x or y orz

... Ellipses indicate non-essential information omitted from the example

Where to get helpEMC support, product, and licensing information can be obtained as follows:

Product informationFor documentation, release notes, software updates, or information about EMCproducts, go to EMC Online Support at https://support.emc.com.

Technical supportGo to EMC Online Support and click Service Center. You will see several options forcontacting EMC Technical Support. Note that to open a service request, you musthave a valid support agreement. Contact your EMC sales representative for detailsabout obtaining a valid support agreement or with questions about your account.

Online communitiesVisit EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engageonline with customers, partners, and certified professionals for all EMC products.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, andoverall quality of the user publications. Send your opinions of this document to [email protected]

Preface


https://support.emc.com

https://community.emc.com

mailto:[email protected]

Preface


CHAPTER 1

Introduction

This chapter includes the following sections:

l Overview............................................................................................................ 16l Microsoft Exchange Server environments.......................................................... 16l Using NMM in an Exchange Server environment............................................... 24

Introduction 15

OverviewThis topic summarizes the NMM support for Exchange server.

The EMC® NetWorker® Module for Microsoft (NMM) version 8.2 SP1 softwaresupports several types of Microsoft Exchange Server environments and versions ofExchange Server. Though Exchange Server 2007, Exchange Server 2010, andExchange Server 2013 are similar, they also differ in many ways such as clustering,high availability, recovery databases, and storage groups. These differences affecthow you configure and run NMM backup and restore operations.

NOTICE

You are recommended to download a copy of the EMC NetWorker Online SoftwareCompatibility Guide from EMC Online Support (http://support.emc.com). The EMCNetWorker Online Software Compatibility Guide lists the most up-to-date informationabout supported Windows Server versions.

This guide provides combined procedures for NMM features that are the same acrossExchange Server 2007, Exchange Server 2010, and Exchange Server 2013, exceptwhere noted.

Microsoft Exchange Server environmentsThis topic describes the Exchange server support for recovery storage groups (RSG)and recovery databases (RDB).

Exchange Server 2007 supports recovery storage groups (RSG) and Exchange Server2010 and Exchange Server 2013 support recovery databases (RDB) as noted in thetable.

Table 2 Exchange Server Storage types

Exchange Server Version Recovery Storage Groups (RSG)

Recovery Databases (RDB)

2007 supported --

2010 -- supported

2013 -- supported

Exchange Server 2007, Exchange Server 2010, and Exchange Server 2013 supportstand-alone and clustered configurations.

NMM supports backup and recovery for all of these configurations.

Stand-alone and single Exchange ServersThis topic describes the relationship between Stand-alone and single ExchangeServers to NMM.

In a stand-alone or single Exchange Server environment, all mailbox databases, logfiles, and checkpoint files reside on one server such as:

l Exchange Server 2007 stand-alone

l Exchange Server 2007 Local Continuous Replication (LCR)

Introduction


http://support.emc.com



The following figure illustrates the relationship between the NetWorker Server,NetWorker Management Console (NMC), and NMM client installation in a singleExchange server environment. Install the Exchange Granular Level Recovery (GLR)option when you install the NMM client.

Figure 1 NetWorker and NMM installation in a single Exchange Server environment

Exchange Server 2007 clustersThis topic describes the relationship of NMM to an Exchange Server cluster.

For an Exchange Server 2007 cluster, install the NMM client on each Exchange Serverthat has the mailbox role installed.

The following figure illustrates an NMM client installation in an Exchange Server 2007cluster environments such as:

l Cluster continuous replication (CCR)

l Standby continuous replication (SCR)

l Single copy cluster (SCC)

Introduction

Exchange Server 2007 clusters 17

Figure 2 NetWorker and NMM installation in an Exchange Server 2007 cluster environment

Configuring Exchange backup, provides detailed steps for configuring a cluster backupafter you install the NMM client on each Exchange Server in the cluster.

Exchange Server 2010 and 2013 DAGsThis topic describes the relationship between Exchange server Database AvailabilityGroups (DAG) and NMM.

NMM supports Database Availability Groups (DAG) for high availability of ExchangeServer 2010 and 2013 databases, with the following considerations:

l Install the NMM client on each Exchange server that has the mailbox role installed.

l You can replicate each Exchange database to multiple Exchange servers, with amaximum of 16 copies.

l When there are multiple copies of a database, only one copy of the database isactive at a time. The remaining copies are passive.

l You can back up active databases, passive databases, or both.

l You can only restore backups of databases in a DAG environment to activedatabase copies.Information about Exchange DAG architecture is available on the MicrosoftTechNet website at http://technet.microsoft.com/en-us/library/dd979799.aspx.

Due to a Microsoft limitation, NMM does not support backups of Exchange DAGswith cross-domain servers. The following Microsoft technical note provides moreinformation about this limitation: http://technet.microsoft.com/en-us/library/dd979802.aspx.

The Exchange Server 2010 equivalent for this limitation is available on theMicrosoft TechNet website at http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx.

Introduction


http://technet.microsoft.com/en-us/library/dd979799.aspx



http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx

http://technet.microsoft.com/en-us/library/dd979799(v=exchg.141).aspx

Figure 3 NetWorker and NMM installation with a DAG in Exchange Server 2010 or 2013environment

l For Exchange Server 2010 and Exchange Server 2013, “stand-alone” applies to anExchange Server 2010 or 2013 mailbox server where one server hosts all thedatabases and you have not configured a DAG.

Configuring Exchange backup, provides information on configuring a DAG backupafter you install the NMM client on each Exchange server in the cluster.

Supported high availability configurations

Most larger enterprises typically deploy Exchange Server in some form of high-availability configuration. Exchange Server 2007 typically includes the use of Windowsclusters, Exchange Server 2007 replication, or both. Exchange Server 2010 andExchange Server 2013 typically includes the use of DAGs.

High availability and clustering in Exchange Server 2007

To create an Exchange Server 2007 cluster, install and configure Windows failoverclustering before installing Exchange Server. Exchange Server 2007 typically includesthe use of Windows clusters, Exchange Server 2007 replication, or both.

For Exchange Server 2007 clustered environments such as CCR and Windowsclusters, configure the NMM client on each node of the server. The NMM client allowsyou to configure backup for all passive nodes in the cluster.

Introduction

Supported high availability configurations 19

Exchange Server 2007 replication

Exchange Server 2007 includes built-in data features that enable replication ofExchange data from one Exchange server to another.

Exchange Server 2007 offers three levels of data replication, as described in thefollowing topics.

Local Continuous Replication (LCR)This topic describes Exchange Server Local Continuous Replication (LCR)

LCR is a single-server solution that uses built-in asynchronous log shipping and logreplay technology to create and maintain a copy of a storage group on a second set ofdisks that are connected to the same server as the production storage group. Theproduction storage group is referred to as the active copy, and the copy of thestorage group maintained on a separate set of disks is referred to as the passive copy.

The following figure illustrates a typical LCR deployment.

Figure 4 A typical LCR deployment

An LCR deployment does not require any special NMM setup or configuration. Installthe NMM client on the active storage group using the normal (non-cluster) installationprocedure.

Cluster Continuous Replication (CCR)This topic describes Exchange Server Cluster Continuous Replication (CCR).

CCR combines the asynchronous log shipping and replay technology built in toExchange Server 2007 with the failover and management features provided by theWindows Cluster Service. CCR provides an Exchange Server 2007 high availabilitysolution that:

l Has no single point of failure.

l Has no special hardware requirements.

l Has minimal shared storage requirements.

l You can deploy in one or two data center configurations.

CCR uses the database failure recovery functionality in Exchange Server 2007 toupdate asynchronously a second copy of a database with the changes made to theactive copy of the database. When you install a passive node in a CCR environment,each storage group and its database is copied from the active node to the passive

Introduction


node. This operation is called seeding, and it provides a baseline of the database forreplication. After the initial seeding is performed, the CCR log continuously copies andreplays the logs.

CCR integrates the replication capabilities with the Cluster Service to deliver a high-availability solution. In addition to providing data and service availability, CCR alsoprovides scheduled outages. When you install updates or perform maintenance, youcan manually move a clustered mailbox server to a passive node. After the moveoperation is complete, you can perform the needed maintenance.

The following figure illustrates a typical Exchange CCR configuration.

Figure 5 CCR deployment

Standby Continuous Replication (SCR)This topic describes the deployment of Exchange server Cluster ContinuousReplication (CCR) with Standby Continuous Replication (SCR).

You can combine CCR with SCR to replicate storage groups locally in a primary datacenter (using CCR for high availability) and remotely in a secondary or backup datacenter (using SCR for site resilience). The secondary data center could contain apassive node in a failover cluster that hosts the SCR targets. This type of cluster iscalled a standby cluster because it does not contain any clustered mailbox servers, butyou can quickly provision it with a replacement clustered mailbox server in a recoveryscenario. If the primary data center fails or is otherwise lost, you can quickly activatethe SCR targets hosted in this standby cluster on the standby cluster.

The following figure illustrates a CCR combined with SCR.

Introduction


Figure 6 CCR combined with SCR deployment

Single Copy Cluster (SCC)

This topic describes the deployment of Exchange server Single Copy Cluster (SCC).

SCC is a more typical Windows cluster configuration. Exchange stores the databasesand logs on one disk that both nodes of the cluster share. In the example deploymentillustrated in the figure below, Exchange servers MBX-01 and MBX-02 share Exchangedatabases and logs on external storage.

Figure 7 Windows cluster (Exchange SCC) deployment

High availability in Exchange Server 2010 and 2013This topic describes the advantages of using Exchange Server 2010 and 2013 for highavailability.

Exchange Server 2010 and 2013 use DAG and mailbox database copies. You do notneed to install and configure any Windows clustering before you install ExchangeServer 2010 or 2013. You can add high availability to the Exchange Server 2010 or2013 environment after you deploy Exchange Server without having to uninstallExchange Server and then reinstall in a high-availability configuration.

Introduction


These improvements in high availability and site resilience functionality also simplifyinstallation and configuration of the NMM client for backup and recovery.

Active and passive nodes and databasesThe following topic describes NMM installations with Exchange server clusteredenvironments.

In a clustered environment, there are active and passive copies of the databases. Thisallows the server to constantly update a copy, or replica, as the passive copy, andminimize the impact on performance of the active copy. For backups, the passive copyallows you to back up the databases without affecting the performance or data of theactive copy. With Exchange Server 2007, a node is either all active or all passive, asdescribed in the Cluster Continuous Replication (CCR) topic. With Exchange Server2010 and 2013, you designate individual databases, not nodes, as active or passive.This allows you to have a mix of active and passive databases on each node.

The following figure shows an Exchange Server 2010 or 2013 DAG environment withfour mailbox databases (DB1, DB2, DB3, and DB4). There are active and passivecopies of these databases spread over three nodes (servers MBX1, MBX2, andMBX3).

Figure 8 Exchange Server DAG environment

The following figure illustrates an NMM installation in Exchange Server 2007 clusterenvironments such as:

l Cluster continuous replication (CCR)

l Standby continuous replication (SCR)

l Single copy cluster (SCC)

Introduction


Figure 9 NMM installation in an Exchange Server 2007 cluster

Configuring Exchange backups provides detailed steps for configuring the NMM clienton the active node after installation of the NMM client on each Exchange server in thecluster.

Using NMM in an Exchange Server environment

The following section contains information you should be aware of when using NMM inan Exchange Server environment.

Exchange Server 2007 and Exchange Server 2010 VSS WritersThis topic describes the Exchange server writers for active and passive databases.

Exchange Server 2007 and Exchange Server 2010 have two writers for active andpassive databases. NMM uses these writers during backup. The following tableprovides details.

Table 3 Writers used by NMM for Exchange Server backup and recovery

Applicationwriters

Description

Information StoreWriter

This writer is built into the Exchange store, is available on any mailboxserver, and is responsible for backup and recovery of activedatabases.

Replication ServiceWriter

This writer is built into the Replication Service. The ReplicationService Writer is available on the passive node of DAGs and CCRclusters and on any mailbox server that has at least one storage groupconfigured with LCR.

Introduction


Table 3 Writers used by NMM for Exchange Server backup and recovery (continued)

Applicationwriters

Description

The Replication Service Writer supports backup functionality for aselected database or storage group where the shadow copy is takenagainst the replicated instance of the database and transaction logfiles. You can use the Information Store Writer to restore ReplicationWriter backups to the active database location.

Exchange Server 2013 VSS WriterThis topic describes the Exchange Server 2013 writer used for active and passivedatabases.

Exchange Server 2013 has one writer for active and passive databases. NMM uses thiswriter during backup. The following table provides details.

Table 4 Exchange Server 2013 VSS writer

Application writer Description

Microsoft ExchangeServer Writer

This writer is used by Exchange Server-aware VSS-based applicationsto backup active and passive database copies, and to restore backedup database copies. Although the new writer runs in the MicrosoftExchange Replication service, it requires the Microsoft ExchangeInformation Store service to be running in order for the writer to beadvertised. As a result, both services are required in order to backupor restore Exchange Server databases.

Compatibility with previous Exchange backupsThis topic describes the version support for backups created with earlier versions ofNMM.

You can use NMM to recover Exchange databases and logs that were backed up byusing NMM 2.3 or later.

You cannot recover data from an NetWorker Module for Exchange (NME) backup byusing NMM. If you have upgraded to NMM from NME, perform a full backup ofExchange to perform NMM point-in-time recovery in the future.

The NetWorker Module for Microsoft Installation Guide and the NetWorker Module forMicrosoft Administration Guide provide details.

If you want to upgrade the Exchange server version you are currently using, includingExchange Service Pack upgrades, perform a full backup before the upgrade. You mustdo a full backup after upgrading. You cannot recover data from a previous Exchangeservice pack to an Exchange server that runs a later service pack version.

For example, if you have Exchange Server 2007 SP2 Rollup 4 installed on a WindowsServer 2008 SP2 (x64) CCR environment and you want to upgrade to ExchangeServer 2007 SP3 Rollup1:

1. Perform a full backup on Exchange Server 2007 SP2 Rollup 4

Introduction

Exchange Server 2013 VSS Writer 25

2. Upgrade to Exchange Server 2007 SP3 Rollup1.

3. Perform a full backup on Exchange Server 2007 SP3 Rollup1.

4. Verify that you are able to perform a recovery by restoring data to the RSG.

Backup initiated transaction log file truncationThis topic describes the behavior of Exchange transaction log files as part of a backup.

The time that the Exchange writer starts backup-initiated log file truncation differs foreach backup type.

l In non-DAG configurations, the Exchange Writer truncates the transaction log filesat the completion of successful full or incremental backups.

l In DAG configurations, the Replication service delays the log truncation until allnecessary log files are replayed into all other copies. The Replication servicedeletes the backed up log files both from the active and the passive copy log filepaths after the Replication service verifies that the to-be-deleted log files havesuccessfully been applied to the copy database and both active database and thedatabase copies checkpoint has passed the log files to be deleted.

Backup types and levelsThis topic describes the types of Exchange server backups that NMM supports usingMicrosoft Volume Shadow Copy Service (VSS).

You can use the Microsoft Volume Shadow Copy Service (VSS) with NMM to performfull and incremental backups for stand-alone and clustered databases. Ensure that theuser account for the Replication Manager Exchange Interface service is a member ofthe Organization Management Exchange security group.

NMM supports the following backup types when you use the Microsoft VSS softwareprovider:

l Point-in-time snapshot backup for FULL Level backups, with the Snapshot PolicyBackup Snapshot option set to ALL

l Single server backup

l Virtual server cluster backup

l SCC backup

l LCR backup of the production data, but not of the replicated data

l CCR active node and passive node backup

l DAG

NOTICE

You can use data deduplication for an Exchange Server 2007 backup in a CCRenvironment.The NetWorker Module for Microsoft Administration Guide provides in-depthinformation about data deduplication.

The following table describes the backup levels that NMM supports.

Introduction


Table 5 Exchange Server backup levels

Level of backup Description

Full A full backup is a complete backup that archives every selecteddatabase and all necessary log files. After the backup completes, logfiles older than the checkpoint taken at backup start time are deleted.If you perform a full backup on a daily basis, you can prevent log filesfrom consuming space on the hard disk.You can perform a full backup of Exchange Server 2007, 2010, and2013 databases in both clustered and non-clustered environments. Afull backup includes both database files and logs files.

Incremental An incremental backup backs up only selected data, and thereforeimproves backup performance by reducing the amount of data thatNMM processes. However, recovery might take longer because NMMrecovers the last full backup plus each incremental backup that wasperformed after the full backup.You can perform incremental backups of Exchange Server 2007, 2010,and 2013 databases in both clustered and non-clusteredenvironments. Unlike a full backup in which NMM backs up bothdatabase files and logs files, an incremental backup only backs up logsfiles. You can include public folders in incremental backups.

In a clustered or DAG environment, you can perform an incrementalbackup of a passive copy of a database after you perform a fullbackup of the active copy on another Mailbox server, and vice versa.If a full backup is not found on the Mailbox server, you must manuallyperform a full backup of the active copy of the database on theMailbox server with the same save set that you used the first time youperformed a backup.

Federated backupThis topic describes NMM support of Federated Exchange server deployments.

NMM supports Federated backups for Exchange Server 2010 and 2013 DAGs.Federated backups allow you to back up all databases in a DAG with a single save setacross all Exchange Server nodes in the DAG. NMM does not require you to perform aseparate backup of each node.

Recovery typesThis topic describes the types of Exchange recoveries supported by NMM.

NMM supports the following types of recovery:

l Roll-forward recovery

l Point-in-time recovery

l Database recovery to Exchange RSG or RDB

l Remote database recovery for Exchange Server 2010 and 2013 DAG

l Mailbox item level recovery from Exchange RSG or RDB databases

l Exchange RSG or RDB mailbox browsing, mailbox, folder, and message recovery

Introduction

Federated backup 27

l Recovery to alternate storage group or alternate mailbox database

l Recovery to alternate Mailbox

l Granular Level Recovery (GLR) to an alternate Mailbox

l Granular Level Recovery (GLR) of an archive Mailbox

l Granular Lever Recovery (GLR) to PST files for Exchange 2010 and 2013

Introduction


CHAPTER 2

Configuration


l Supported Exchange server deployment scenarios and limitations.................... 30l NMM prerequisites............................................................................................ 32

Configuration 29

Supported Exchange server deployment scenarios andlimitations

The following section describes supported and unsupported Exchange serverdeployment scenarios.

Note

The NetWorker Online Software Compatibility Guide, available on the EMC onlinesupport website at http://compatibilityguide.emc.com:8080/CompGuideApp/Networker8.2.jsp, provides the most up-to-date and accurate listing of hardware,operating system, service pack, and application versions that the NMM clientsupports.

Supported Exchange server versionsThis topic describes the versions of Exchange server that are supported by NMM.

Table 6 Supported Microsoft Exchange server versions and operating systems

Exchange Server version Supported Operating systems

2013 SP1 l Windows 2012 R2

2013 CU2 and later l Windows Server 2008 x64 R2 SP1

l Windows Server 2012

2010 SP3 l Windows Server 2008 x64 R2 SP1

l Windows Server 2012

2010 SP2 Rollup 4 and later l Windows Server 2008 x64 SP2

l Windows Server 2008 x64 R2 SP1

2007 SP3 l Windows Server 2008 x64 SP2


Configuration


http://compatibilityguide.emc.com:8080/CompGuideApp/Networker8.2.jsp

http://compatibilityguide.emc.com:8080/CompGuideApp/Networker8.2.jsp

Supported high-availability deploymentsThis topic describes the operating system requirements needed for a highly availableExchange server deployment that is supported by NMM.

Table 7 NMM support for highly available Exchange server

Exchange Serverversion

Operating system Supported highavailabilitydeployment

2007 SP3 l Windows Server 2008 x64 R2

l Windows Server 2008 x64 SP2Enterprise/ DC Edition

l Single-copycluster (SCC)

l LCR

l CCR

l SCR

2010 SP1 DAG l Windows Server 2008 x64 SP2


l DAGs

l Passive andactive

2010 SP3 l Windows Server 2012

l Windows Server 2012 R2

l DAGs

l Passive andactive

2013 CU2 l Windows Server 2012


l DAGs

l Passive andactive

2013 l Windows Server 2012 R2 l DAGs

l Passive andactive

The Exchange Server 2010 and 2013 documentation recommends two networks: onefor public traffic and one for replication traffic. Although a DAG with a single networkis a supported configuration, it is not recommended. Using only one networkconnection can lead to unstable operations, such as databases that fail over to othersystems when they experience network connection time outs.

Windows Small Business Server

NMM does not support backup and recovery of Windows Small Business Server.

Single server Microsoft Exchange Server and Microsoft SharePoint Serverinstallations

NMM does not support Microsoft Exchange Server and Microsoft SharePoint Serverinstalled on the same computer. Microsoft does not support this configuration.Instead, Microsoft best practices recommend that you install these server products onseparate computers.

Configuration

Supported high-availability deployments 31

Exchange Server 2007 storage groupsThis topic describes the recommended limitations to Exchange Server 2007 storagegroups.

EMC recommends that you configure no more than 10 Exchange concurrent storagegroups for scheduled backups, particularly when you enable parallel consistencychecking. Grouping more than 10 storage groups consumes the available resources ofthe CPU, I/O, and memory, and can lead to backup failures. Set theNSR_EXCHANGE_LIMIT_SG attribute to yes to set the number of storage groups to10.

For a workaround for Exchange servers with more than 10 storage groups, refer to thetopic Configuring_Exchange_2007_storage_groups.

Delivery status notifications (DSNs) for Exchange server DAG environments

NMM does not support delivery status notifications (DSNs) for Exchange Server 2010or Exchange Server 2013 DAG environments.

For a workaround to perform DSN backups for Exchange Server 2010 or ExchangeServer 2013 DAG environments, refer to Planning DAG and non-DAG backups in theNetWorker Module for Exchange User Guide.

Backup and recover limitation to standalone mailbox server in a DAG

When you join a standalone Exchange 2010 or 2013 mailbox server to a DAGconfiguration, you cannot browse and recover data from the standalone backups.

NMM prerequisitesThe following section describes the system and configuration prerequisites for NMM.

Ensure that the following prerequisites are met before performing backup andrecovery procedures.

Exchange server hardware requirementsThis topic describes the additional hardware and system resources required forExchange server.

Exchange places additional demands on computer hardware and resources beyond thebase requirements for NMM. Ensure that the computer running Exchange servermeets or exceeds Microsoft hardware recommendations.

The table below describes the recommended hardware requirements for Exchangeserver.

Table 8 Exchange server hardware requirements

Requirement Description

Memory (RAM) Exchange server requires additional memory (RAM). Start with 8 GBof RAM. The amount of additional or total memory required dependson current system performance with existing memory:

Configuration


Table 8 Exchange server hardware requirements (continued)

Requirement Description

l If the memory resources are strained and performance is slowwith regular operations of NMM, then add significantly morememory to support Exchange operations.

l If the memory performance is adequate with regular operations ofNMM, then additional memory might not be required to supportExchange operations.

Disk staging area Exchange server requires additional disk space for a disk staging areato hold writes to the Exchange database and log files.

Required permissionsThis topic describes the minimum user account permissions required to performbackup and recovery with NMM.

To perform backup and recovery, the administrative account must have the followingpermissions:

Table 9 Permissions for Exchange Backup and Recovery

Exchange 2007 Exchange 2010 Exchange 2013

Security groupmemberships onNMM Clientcomputer

Local Administrator Local Administrator Local Administrator

Security groupmemberships onDomain Controller

Backup OperatorsRemote DesktopUsers



If the Exchangeserver is also aDomain Controller

Add theadministrativeaccount to theExchangeOrganizationAdministrators group.

Add theadministrativeaccount to theOrganizationManagement group.

Add theadministrativeaccount to theOrganizationManagement group.

Exchange SecurityGroup memberships

Exchange Servers

ExchangeOrganizationAdministrators

Exchange View-OnlyAdministrators

Exchange Servers

OrganizationManagement

View-OnlyOrganizationManagement

Exchange Servers

OrganizationManagement

View-OnlyOrganizationManagement

Minimum ExchangeSecurity Groupmemberships(As an alternative tousing theOrganization

n/a Exchange Roles:

Database Copies

Databases

Disaster Recovery

Exchange Roles:

Database Copies

Databases

Disaster Recovery

Configuration

Required permissions 33

Table 9 Permissions for Exchange Backup and Recovery (continued)

Exchange 2007 Exchange 2010 Exchange 2013

Management SecurityGroup membership)

Mailbox Import Export

Mail RecipientCreation

Mail Recipients

View-OnlyConfiguration

View-Only Recipients

Mailbox Import Export

Mail RecipientCreation

Mail Recipients

View-OnlyConfiguration

View-Only Recipients

Networker server-side permissionsAdd entries using theNMC

Configuration >

User Groups >

ApplicationAdministrators >

Configuration >

Users

user=<administrative accountname>,host=<NMMclient name>user=system,host=<NMM client name>


Note

If the ExchangeServer hosts a DAGthen add abovepermission to all DAGnodes and DAGclients.


Note

If the ExchangeServer hosts a DAGthen add abovepermission to all DAGnodes and DAGclients.

In order to export to PST files in GLR or RDB recoveries, the administrative accountmust be a member of the Organization Management group and have the followingprivileges:

l By user:New-ManagementRoleAssignment -user <administrative account name> -role"Mailbox Import Export"

l By group:New-ManagementRoleAssignment -SecurityGroup <group name> -role "MailboxImport Export"

Note

The NetWorker Module for Microsoft Installation Guide provides additional informationabout configuring required permissions.

MAPI client and Collaboration Data ObjectsThis topic describes the Exchange Server requirements for the Microsoft ExchangeServer MAPI Client and Collaboration Data Objects 1.2.1 Kit for granular levelrecovery.

Note

MAPI and Outlook cannot be installed on the same host.

Configuration


Table 10 Exchange Server GLR MAPI/CDO requirements

Exchange Server version Required MAPI/CDO version

Exchange Server 2010 MAPI/CDO 1.2.1 version 6.5.8244.0 or earlier

Exchange Server 2013 MAPI/CDO 1.2.1 version 6.5.8320.0 or later

Exchange Server 2016 Not applicable

The Exchange Server 2010 and 2013 software does not include the MAPI clientlibraries and CDO. You can download these applications from Microsoft’s website. Forinformation about downloading and installing this package, search for "MicrosoftExchange MAPI Client and Collaboration Data Objects" on the Microsoft DownloadCenter website.

The EMC NetWorker Online Software Compatibility Guide contains information aboutthe latest version of the MAPI and CDO kit that NMM supports.

Exchange backup prerequisitesThis topic describes the required prerequisites for backup of Exchange server usingNMM.

Ensure that the following prerequisites are met before performing backup procedures:

l NMM does not support DAGs configured without a cluster Administrative AccessPoint.

l Verify that the correct version of the Messaging API (MAPI) and CollaborationData Objects (CDO) kit is installed. Exchange Server 2010 and 2007 requires6.5.8244.0 or later. Exchange Server 2013 requires version 6.5.8320.0 or later.

l Install .NET Framework 4.0.

l Install the hotfixes and cumulative updates listed in the NetWorker Module forMicrosoft Installation Guide.

l Verify that all servers use the same version of Exchange Server.

l Install the NetWorker client and NMM software on all Exchange servers that are apart of a backup. Select the GLR option if you want to perform GLR.

l For Exchange Server 2007 backups:

n Consider the requirement that you configure no more than 10 Exchangestorage groups for a scheduled backup.

n Verify that the mailbox log file and system files are located on differentvolumes than the database. Beginning with NMM 3.0, Exchange Server 2010and 2013 database and log files can reside on the same volume and in the samefolder.

l For CCR or DAG environments:

n Create a client resource for all Exchange clients that are members of the CCRor DAG.

n Create a NetWorker client resource for the CCR or DAG name using the FQDN.

n For Federated backups, add the NSR_FEDERATED_BACKUP ApplicationInformation attribute and specify “yes” as the value.

l Run the System Configuration Checker.

Configuration

Exchange backup prerequisites 35

Exchange recovery prerequisitesThis topic describes the required prerequisites for a recovery of Exchange data usingNMM.

The following requirements must be met before you can recover Exchange Server2007, Exchange Server 2010, or Exchange Server 2013 data:

l For each Exchange database to be recovered, you must select the Exchangecheck box titled “This database can be overwritten by a restore” in the ExchangeManagement Console.This is a Microsoft requirement. In PowerShell, the flag is called AllowFileRestoreand must be set to true. The Microsoft Exchange documentation provides moreinformation about this checkbox.

l If you are recovering Exchange data that was backed up from a legacy NetWorkerclient by using the save set VSS USER DATA:\ in an NMM File System RecoverySession:

1. While performing recovery by using the NMM client, Exchange databases areautomatically dismounted.

2. After a successful recovery, the Exchange databases are mountedautomatically.

l Exchange does not support restoring a public folder database to RSGs or RDBs.

l To perform an Exchange database recovery as a non-administrative user, open theNMM user interface using Run as administrator.

l During recovery, when recovering mailbox items to a production database, ensurethat the user mailbox is not full. If the allowed mailbox space is exceeded, then theitem level recovery fails.

l When you overwrite an existing databases with the recovery, perform a full levelbackup after every recovery performed in Exchange Server 2010 and ExchangeServer2013. This does not apply to RSG, RDB or granular restores.

Exchange Server 2007 CCR requirementsThis topic provides information on how to configure the Windows cluster for ExchangeServer 2007 with the CCR high-availability feature.

If you intend to use Exchange Server 2007 with the CCR high-availability feature, youmust configure the Windows cluster in accordance with the information presented inthe following articles:

l “Installing Cluster Continuous Replication on Windows Server 2008,” which isavailable on the Microsoft TechNet website at the following URL:http://technet.microsoft.com/en-us/library/bb629714.aspx

l “Using Backup to Back Up and Restore Exchange Data,” which is available on theMicrosoft TechNet website at the following URL:http://technet.microsoft.com/en-us/library/aa998870.aspx

This article discusses the exact conditions under which log files are removed, sincelog truncation with Exchange Server 2007 CCR depends on the state of thereplication.

l “Event ID 214 is logged when you run a backup operation on a passive node afteryou install Exchange Server 2007 SP3 in an Exchange Server 2007 CCRenvironment”, which is available on the Microsoft Support website at the followingURL:http://support.microsoft.com/kb/2297394

Configuration


http://technet.microsoft.com/en-us/library/bb629714.aspx

http://technet.microsoft.com/en-us/library/aa998870.aspx

http://support.microsoft.com/kb/2297394

l To resolve the issue described in the article, install Exchange Server 2007 SP3Update Rollup 1 on all affected servers. You can download the update rollup at thefollowing URL:http://www.microsoft.com/downloads/details.aspx?FamilyID=ae45d06e-dcb7-43d8-b1ff-d3953836425b

Ensure that the server nodes are in the correct state. You must perform the recoveryof the CCR server to an active node. The restored databases must be in active state.Passive copies of the databases must be in Exchange replication suspended state. Ifthe copies are not in suspended state, then you must manually suspend passive copiesbefore a recovery is performed.

In addition, the account that you use to browse and select items for backup in anExchange Server 2007 CCR environment requires the following user accountpermissions on the passive nodes:

l Administrator

l Domain Administrator

l Domain User

l Exchange Install Domain Servers

Additional requirements for recovering databases in a DAGThe following topic provides requirement details for recovering an Exchange DAGdatabase.

For Exchange Server 2010 and 2013 DAG recovery, ensure that the database recoverynode and state are correct. You must perform the recovery to the DAG member serveron an active node. The restored databases must be in active state. Passive copies ofthe databases must be in Exchange replication suspended state. If the copies are notin suspended state, then you must manually suspend passive copies before a recoveryis performed.

You can suspend replication in three ways:

l By using the Exchange Shell command and calling Suspend-MailboxDatabaseCopycmdlet

l For Exchange Server 2010, through the Exchange Management Console usingSuspend Database Copy

l For Exchange Server 2013, through the Exchange Admin Center using Suspend

Resume the passive database copies after the restore. The Microsoft documentationprovides details.

Additional requirements for browsing mailboxes

The following topic describes the requirements for browsing Exchange RSG and RDBmailboxes.

l Databases must be online. NMM does not display mailboxes in offline databases.

l The MAPI/CDO kit must be installed.

l Exchange System Attendant and Information Store services must be running.

l The logged in user must have a configured mailbox with at least one mail sent orreceived.

Configuration

Additional requirements for recovering databases in a DAG 37

http://www.microsoft.com/downloads/details.aspx?FamilyID=ae45d06e-dcb7-43d8-b1ff-d3953836425b

http://www.microsoft.com/downloads/details.aspx?FamilyID=ae45d06e-dcb7-43d8-b1ff-d3953836425b

l The user defined to be logged in for the Replication Manager Interface forExchange service must be a member of the Organization Management Exchangesecurity group.

l You must have backed up the writer set, database or storage group save set:

n For Exchange Server 2007 writer:APPLICATIONS:\Microsoft Exchange 2007

n For Exchange Server 2007 storage group:APPLICATIONS:\Microsoft Exchange 2007\second_group


n For Exchange Server 2010 database:APPLICATIONS:\Microsoft Exchange 2010\Database



Exchange Consistency CheckThe following topic describes how the Exchange consistency check improves thequality of a backup.

The Exchange consistency check verifies that the database and its corresponding setof transaction logs do not contain errors, and validates Exchange before performing arestore. A consistency check can be done on the database only, without thetransaction logs. While a consistency check of only the database does not ensurecomplete consistency of the backup, it does offer the advantage of a shorter time toperform a consistency check. Exchange automatically runs a consistency checkagainst stand-alone databases and public folders before NMM restores the data.

Consistency check parameters for threading and throttlingThe topic describes the effects of Exchange consistency check on NetWorkerperformance. Included is information about the Application Information attributes.

The consistency check impacts Exchange backup performance. The larger thedatabases and associated transaction logs, the longer it takes to run a consistencycheck. NMM provides the option to run the consistency check on multiple storagegroups in parallel.

If you run multiple consistency checks in parallel without setting the proper throttlelimits, performance problems might appear on the proxy system. In extreme cases,this can cause I/O bottlenecks so severe that consistency checks fail and othersystem operations are adversely affected.

In NMM, you can configure threading and throttling by using the -A attribute values inthe Application Information attribute of the NMM client. You can use these values toprevent performance issues during backup.

The table below lists the Application Information attributes that you can specify in theclient resource to set threading and throttling.

Configuration


Table 11 Exchange application information variables for threading and throttling

Attribute name Value

NSR_ESE_UTIL_SEQUENTIAL Set to either of the following:

l True — To run eseutil sequentially (singlethreaded).Or

l False — To run eseutil in parallel againstmultiple storage groups (multi-threaded).The default value is True.

For example,

A NSR_ESE_UTIL_SEQUENTIAL=False -A NSR_ESE_UTIL_THROTTLE=True

NSR_ESE_UTIL_THROTTLE Set to either of the following:

l True — To allow eseutil throttling.Or

l False — To prevent eseutil throttling.The default value is False.

NSR_ESE_THROTTLE_IOS Specify the number of I/Os between pauseswhen throttling, in the value range of 100–10000.The default value is 100.

For example,

A NSR_ESE_THROTTLE_IOS=500 -ANSR_ESE_THROTTLE_DURATION=5000

NSR_ESE_THROTTLE_DURATION Specify the duration of pause in millisecondswhen throttling, in the value range of 1000–60000.The default value is 1000.

NSR_ESE_UTIL_DB_ONLY Specify wether to only perform theconsistency check on the database and skipthe transaction logs.The default value is False.

Configuring a DSN for Exchange ServerThis topic describes how to configure a DSN.

The following procedure applies only to Exchange Server 2007, 2010, and 2013 stand-alone environments. Before performing the steps in this section, review the NetWorkerModule for Microsoft Installation Guide for details on setting up a DSN.

Procedure

1. Install a NetWorker server 7.6 SP2 or later, or NetWorker storage node 8.0 SP2or later.

Configuration

Configuring a DSN for Exchange Server 39

NOTICE

This step is required before installing the NMM software.

2. For a DSN, install the NMM software on the same host.

3. Create a remote backup device on the NetWorker server and on the DeviceProperties, Configuration tab, set the Dedicated Storage Node attribute toYes.

Configuration


CHAPTER 3

Backup


l Planning backups............................................................................................... 42l Configuring Exchange backups.......................................................................... 49l Performing an Exchange Server scheduled backup............................................82l Verifying a backup............................................................................................. 85

Backup 41

Planning backups

This section contains information to help you plan an Exchange backup.

Backup requirements

When performing Exchange server backups, keep the following requirements in mind:

l When creating an RDB, do not use symbols in the folder name. RDB item levelrecovery fails with an error if the folder name contains a symbol.For example, the folder name used is “Recovered Data - sec77 - 04/03/201318:28:45”.

l When browsing an RDB, the log-in user mailbox or the user mailbox that youprovided during NMM installation should reside on the mailbox server you arebrowsing. Otherwise, you might encounter browsing errors.

l Transaction logs cannot be located at the root level of a mount point. This resultsin transactions logs that are not backed up at all.

Exchange server version specific requirements:

l For Exchange 2007 backups, store the logs and system path files in the samefolder on a single volume. Store mailbox database files in a different volume.For example:

E:\<LogsPath_SystemPath>

Where E:\ is the dedicated drive letter for logs and system files.

F:\<MailboxDatabase files>

Where F:\ is the dedicated drive letter for mailbox database files.

Note

Beginning with NMM 3.0, the Exchange Server 2010 and Exchange Server 2013database and log files can reside on the same volume and in the same folder.

l For backups of Exchange Server 2007 database and log files residing on differentmount points under the same volume, add NSR_E2K7_VOL_CHECK=NO to theApplication Information field on the Apps & Modules tab of the ClientProperties dialog.This attribute is required for successful backups.

You should only use the parameter when the database and log files reside underdifferent volumes but different mount points located on the same volume point tothem.

When you set NSR_E2K7_VOL_CHECK to YES, NMM checks the ExchangeServer 2007 data and volume locations. By default, NSR_E2K7_VOL_CHECK isset to YES.

When you set NSR_E2K7_VOL_CHECK to NO, NMM does not check ExchangeServer 2007 data and volume locations.

Backup


Backup considerations

When performing Exchange server backups, keep the following in mind:

l After a snapshot of a save group starts, you cannot interrupt or halt the snapshotprocess.For example, in Exchange backup, the process on the production server and the process on the proxy resource might continue to run after you halt the snapshot.Any attempt to stop a save group in NMC takes a long time to complete.

l NMM only backs up mounted databases.NMM does not display during the backup operation to indicate if any databases areunmounted. The NMM log files provide details about unmounted databases.

l If a Mailbox server is added to a DAG and one of the databases is then backed up,either refresh the NMM user interface, or close the NMM user interface and thenreopen it.

Planning DAG and non-DAG backups

DAG and non-DAG environments require certain settings and considerations aredescribed in the following sections.

Backup in non-DAG and DAG environments

The following table provides information on creating backups of non-DAG and DAGenvironments.

Table 12 Considerations required for backup in a non-DAG and DAG environment

Type of environment Considerations

For stand-alone ExchangeServer 2010 or 2013

Use the save set APPLICATIONS:\Microsoft Exchange 2010or APPLICATIONS:\Microsoft Exchange 2013.

For non-Federated DAGExchange Server 2010 and2013

Install NMM on only those DAG members that are part of thebackup. It is not necessary to install the NMM client on allDAG members to create the client resource.

Do not modify dummy client resources that are created:

l The Client Configuration wizard creates a client resourcefor one node of the DAG. For this client resource, youmust type the name of the node from which backups areperformed. The Client Configuration wizard then createsclient resources for all the other nodes of the DAG, andthe DAG name. However, these client resources aredummy client resources. If you want to perform a backupfrom a different node in the DAG other than the one thatwas previously used, use the Client Configuration wizardto configure a client resource for this backup node. Donot modify the dummy client resource that is created bythe Client Configuration wizard for this node in theprevious instance.

Backup

Backup considerations 43

Table 12 Considerations required for backup in a non-DAG and DAG environment (continued)

Type of environment Considerations

For example:An Exchange Server 2010 DAG consists of four ExchangeServer 2010 servers: exch2010a, exch2010b, exch2010c,exch2010d, and a Mailbox database myMailBoxABD. TheMailbox database myMailBoxABD is active on exch2010abut passive on exch2010b and exch2010d. The Mailboxdatabase myMailBoxABD is not present on exch2010c. Ina DAG environment, because the Client Configurationwizard can configure a client resource for only one nodeof the DAG, you must select Exchange Server from whichto back up myMailBoxABD.

If you want to back up myMailBoxABD from only one ofthe passive server exch2010b and not from exch2010d orexch2010a, you must use the Client Configuration wizardto create a client resource for exch2010b and dummyclient resources for exch2010d or exch2010a. If you nowdecide to back up myMailBoxABD from exch2010d,restart the Client Configuration wizard to create a clientresource for exch2010d. Do not modify the dummy clientresource that was created when myMailBoxABD wasbacked up from exch2010b.

l When creating client resources manually, create a clientresource for the node from which backups are performed,and create dummy client resources for the otherparticipating nodes in the DAG and the DAG name. Createdummy client resources by using the save set ALL, but donot assign them to a group, because without the dummyclients the backup will not be scheduled correctly.For the DAG members, provide the following attributes:

For NetWorker Server 8.1 and newer:

NSR_EXCH_DAG=<DAG FQDN>

NSR_EXCH_BACKUP = all/active/passive

For backups of Exchange Server 2010 and 2013 databasesusing older versions of NetWorker Server:

NSR_EXCH2010_DAG=<DAG FQDN>

A DAG resource is required for DAG backups because thedata that is backed up is indexed on the DAG name.

The DAG member databases that are backed up must bein a healthy and mounted state before running thebackup.

Backup


Federated backups in DAG environments

A Federated backup allows you to back up all DAG members with a single save setwithout running a separate backup of each node. Running a Federated DAG backup issimilar to a standard backup, except for a few key differences:

l Before you perform a Federated DAG backup, you must configure the clientresource.

l When you select which client to back up, you select the cluster client resource,not individual servers in the DAG, for backup.

To configure a client resource for a Federated DAG backup, you must do the following:

l Select the client resource for the DAG name and not individual servers in the DAG.

l Specify the parameters for the client resource. The topic on Configuring Exchangebackups in this chapter provides more information.

l When you configure the backup, you can specify a preferred server order list(PSOL), which tells NMM the order to poll each server in the DAG to back up. Thetopic on Preferred Server Order List found in this chapter provides moreinformation.

The topic on Using federated DAG backups on Exchange Server 2010 and ExchangeServer 2013 provides more information about Federated backups.

Configuring backups to use a remote storage node in a DAG environmentThis topic describes the steps for configuring remote storage in an Exchange DAGenvironment.

You can configure remote storage for an Exchange DAG environment where:

l The data goes to the respective storage nodes.

l The dummy save sets for the mailbox servers go to their respective storage nodes.

l The VSS save sets go to the storage node specified in the DAG client resource.

For example:

For a 2-node DAG with four databases... 2957375603 1413871552vF full 10/20/2014 11:05:52 PM 4 APPLICATIONS:\MicrosoftExchange 2013 belrednode1.e2013dev.com 2940598388 1413871553vF full 10/20/2014 11:05:53 PM 4 APPLICATIONS:\MicrosoftExchange 2013 belrednode2.e2013dev.com2923821173 1413871555vF full 10/20/2014 11:05:55 PM 4 APPLICATIONS:\MicrosoftExchange 2013 belrednode1.e2013dev.com2907043957 1413871556vF full 10/20/2014 11:05:56 PM 4 APPLICATIONS:\MicrosoftExchange 2013 belrednode2.e2013dev.com 3158702053 1413871582vKF full 10/20/2014 11:06:22 PM 500 APPLICATIONS:\MicrosoftExchange 2013 belreddag.e2013dev.com 3141924838 1413871585vKF full 10/20/2014 11:06:25 PM 500 APPLICATIONS:\MicrosoftExchange 2013 belreddag.e2013dev.com 3125147625 1413871592vF incr 10/20/2014 11:06:32 PM 198297208 APPLICATIONS:\Microsoft Exchange 2013 belreddag.e2013dev.com31083704101413871593 vF incr 10/20/2014 11:06:33 PM 171018304APPLICATIONS:\Microsoft Exchange 2013 belreddag.e2013dev.com3091593205 1413871603 vKF full 10/20/2014 11:06:43 PM 428APPLICATIONS:\Microsoft Exchange 2013 belreddag.e2013dev.com3074815993 1413871608 vF incr 10/20/2014 11:06:48 PM156317988 APPLICATIONS:\Microsoft Exchange 2013

Backup

Planning DAG and non-DAG backups 45

belreddag.e2013dev.com 3058038780 1413871610 vKF full10/20/2014 11:06:50 PM 432 APPLICATIONS:\Microsoft Exchange2013 belreddag.e2013dev.com3041261568 1413871615 vF incr10/20/2014 11:06:55 PM 171006524 APPLICATIONS:\MicrosoftExchange 2013 belreddag.e2013dev.com 3024484397 1413871661vF full 10/20/2014 11:07:41 PM 1941324 C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT2023337192.xmlbelreddag.e2013dev.com 3007707188 1413871668 vF full10/20/2014 11:07:48 PM 1871876 C:\ProgramData\EMC\NetWorker\LG_VSS_CLIENT2023332922.xml belreddag.e2013dev.com2990929978 1413871673 vKF full 10/20/2014 11:07:53 PM 9384VSS:/ belreddag.e2013dev.com 2974152770 1413871679 vKF full10/20/2014 11:07:59 PM 9392 VSS:/ belreddag.e2013dev.com

Procedure

1. On each mailbox server to back up, install a NetWorker storage node followedby the NMM client software.

2. In the DAG client resource properties field, define the storage node asnsrserverhost.

3. In each of the client node resource property fields, provide the storage nodename as their respective host names.

4. Create a backup pool and select the proper backup groups and devices underthe pool properties.

5. Configure a device for each node separately in NetWorker server and label thisdevice with the newly created pool.

6. Create one local device on the NetWorker server and label this device with thenewly created pool.

NMM does not support DSNs. Do not select the DSN device property.

7. Run the backups for DAG nodes and verify that NMM saves the backup to theremote storage node.

Exchange Information Store backup

The Exchange data is stored in the Information Store.

The Information Store contains the following data:

l The Exchange database (.edb) files include mailbox databases and public folderdatabases.

l The Transaction log (.log) files store database operations such as creating ormodifying a message. When the operations are committed, they are written tothe .edb file.

l The Checkpoint (.chk) files store information about successful operations whenthey are saved to the database on the hard disk.

When you select a storage group (Exchange 2007) or database (Exchange 2010 and2013) for backup, NMM backs up the database file and accompanying .log and .chkfiles. As part of your backup strategy for a Microsoft Exchange environment, makesure to back up the following components with NMM:

Microsoft Exchange Server 2010 and 2013 environments

l Stand-alone (non-DAG) databases

Backup


l Active or passive databases in a DAG environment

Microsoft Exchange Server 2007 environments

l Storage groups on the active or passive nodes in a CCR or SCR environment

l Storage groups on stand-alone (non-CCR) Exchange servers

Perform these backups regularly on either an on-demand or scheduled basis.

Backing up highly available Exchange server

In a high-availability environment, such as Exchange Server 2007 cluster continuousreplication (CCR), standby continuous replication (SCR), or single copy cluster(SCC), you must schedule one of the following:

l Active node backup

l Passive node backup

Because the role of a node might change from active to passive, this scheduledbackup strategy ensures that NMM backs up each physical server when it is thepassive node.

In an Exchange Server 2010 or Exchange Server 2013 DAG environment, you canschedule Federated backups using the DAG client and non-Federated backup usingthe DAG node client

Backing up circular logging-enabled databases

You can use circular logging to limit the transaction logs stored on the system.However, incremental backups are not supported with circular logging enabled. Whenthere are circular logging enabled databases, only full backups are valid.

To enable circular logging, add the CIRCULAR_PROMOTION_POLICY parameter tothe Application Information field in the Apps & Modules tab of the ClientProperties dialog for each client resource. This parameter indicates one of threedirectives to follow when backing up circular logging enabled databases or storagegroups.

The CIRCULAR_PROMOTION_POLICY parameter directives are:

l Promote: Back up all databases, promoting incremental backups to full backups ifany database in the save set has circular logging enabled. Selecting this optionbacks up all databases whether they have circular logging enabled or not. If one ormore databases have circular logging enabled, all databases in the save set have allincremental backups promoted to a full backup. If the flag is not specified, alldatabases in the save set have all incremental backups promoted to a full backup.

l Circular: Back up only those databases with circular logging enabled, promotingthem to full. Selecting this option promotes all incremental backups of alldatabases with circular logging enabled to a full backup and skip any databasesthat do not have circular logging enabled.

l Skip: Skip backup of databases with circular logging enabled, allowing incrementalbackups. Selecting this option performs an incremental backup (depending onwhat has been specified) of all databases that have circular logging disabled andskip any database that has circular logging enabled.

You can use the Promote directive by itself. Circular and Skip are mutually exclusive,and you must create a separate client resource for each directive.

If you switch a database from circular logging to noncircular logging, you must run afull backup. Incremental backups that have occurred since the database has been

Backup

Backing up highly available Exchange server 47

switched to noncircular logging are not recoverable until you perform a new fullbackup.

Achieving the maximum number of save sessions

To achieve the maximum number of save sessions for Exchange backups, you canconfigure backups using the following recommendations:

l Perform database level backups by specifying individual database level save setsinstead of the writer level save set.

l Store mailbox database log files and databases on different volumes.

l When using a single backup device, determine the correct Target session and Maxsession values. The Target session value is the number of simultaneous streamsthat a device will accept before the NetWorker server looks for another device.For more information on Target session and Max session, refer to the EMCNetWorker Administration Guide.

l When using multiple backup devices, it is best to have an equal number of backupdevices and snapshots for the backups.

Persistent and non-persistent snapshotsYou can use persistent and non-persistent snapshots to back up your data, dependingon the desired retention time and the available disk space. Persistent snapshots enablequick recovery because recovering from a snapshot that is already available on thedisk is much faster than recovering from a backup. However, retaining persistentsnapshots consumes disk space. Non-persistent snapshots allow the backups to beretained much longer, but recoveries are slower. The topic Configuring_snapshot_policies provides details about persistent and non-persistentsnapshots.

Shadow copy and log truncation

The creation of shadow copy is separate from the notification to VSS writers that thebackup is complete. NMM registers the shadow copy as a snapshot and backs it up tomedia successfully before the notification is sent to the VSS writers. If the backup tomedia fails, then that failure is reported to the Exchange VSS writer and log truncationdoes not occur.

Using NMM with Client Direct to AFTD or Data Domain Boost storage devices

You can store Exchange Server backups on the NetWorker server, on an AFTD device,or on an EMC Data Domain® system. By default, NMM stores backups on theNetWorker server. The NMM software supports the NetWorker Client Direct feature.

The NetWorker client software enables clients with network access to AFTD or DataDomain Boost storage devices to send their backup data directly to the devices,bypassing the NetWorker storage node. The storage node manages the devices forthe NetWorker clients, but does not handle the backup data. The Client Direct featurereduces bandwidth usage and bottlenecks at the storage node, and provides highlyefficient backup data transmission.

Destination devices must specify their complete paths in their Device AccessInformation attribute. If the Client Direct backup is not available, a traditional storagenode backup is performed instead. The Client Direct feature is enabled by default, butcan be disabled on each client by the Client Direct attribute.

Backup


The NetWorker Administration Guide provides details about the Client Direct to AFTD orData Domain Boost storage devices.

Configuring Exchange backupsTo perform an Exchange Server backup, complete the tasks that are outlined in thefollowing table.

The NetWorker Module for Microsoft Administration Guide provides additional detailsabout configuring backups with NMM.

Table 13 Configuration Tasks for an Exchange Server backup

Configuration topic Description

Configuring a backup pool You must create a backup snapshot pool tostore the save sets that contain snapshotmetadata. Snapshots create metadata that isused in the management of snapshotoperations such as an instant recoveryoperation.

Configuring snapshot policies You can either use a preconfigured policy orcreate a custom policy to determine howsnapshots are managed.The topic Persistent and nonpersistentsnapshots and the NetWorker Module forMicrosoft Administration Guide provideadditional details.

A snapshot policy is not required for RolloverOnly backups.

Configuring a backup schedule Backup schedules determine the days onwhich NMM performs full or incrementalbackups:

l Full backups include a backup of everyselected database and all necessary logfiles.

l Incremental backups back up logs filesand only data that has changed since thelast backup. Only nonpersistentsnapshots (Retain=0) supportincremental backups.The topic Backup types and levels and theNetWorker Module for MicrosoftAdministration Guide provide additionaldetails.

Configuring a backup group Backup groups enable you to balance backuploads to reduce the impact on the storage andnetwork resources. If you have configured apool for this group, return to the Pool datasource properties and attach it to this group.You must clear the Force Incrementalcheckbox in the Backup Group properties.

Backup

Configuring Exchange backups 49

Table 13 Configuration Tasks for an Exchange Server backup (continued)

Configuration topic Description

You must create a group resource so that youcan add the client resource to the requiredgroup. You must select the Snapshotcheckbox when configuring the groupresource. You can also select the snapshotpolicy manually. You must not specify groupoverrides for the browse and retentionpolicies. These overrides are only supportedat the client level.

For backups in an Exchange CCR or DAGenvironment, add the virtual and physicalclients to different NetWorker groupresources.

Configuring Exchange client resources To configure an Exchange client resource, youcan use either of the following methods:

l Client Configuration wizard — Toconfigure client resources for the entiresetup at one time.

l NetWorker Management Console — Toconfigure the client resource for eachresource on the setup individually.

Configuring NetWorker administratorprivileges

You must grant NetWorker administratorprivileges for the NMM client to performmedia database operations during snapshotdeletion.

Backup configuration options

Table 14 Backup options for Exchange Server 2010 and Exchange Server 2013

Backup configuration Details

Only active databases backup on the server You can back up all the active database copiesresiding on an Exchange Server 2010 or 2013Mailbox server in a DAG environment. You canperform full and incremental backups. Activenode backups include stand-alone servers andpublic folder databases.

Only passive databases backup on the server You can back up all the passive databasecopies residing on an Exchange Server 2010or 2013 Mailbox server in a DAG environment.You can perform full and incremental backups,including incremental backups of publicfolders. Passive node backups do not includepublic folder databases.

Backup


Table 14 Backup options for Exchange Server 2010 and Exchange Server 2013 (continued)

Backup configuration Details

Both active and passive databases backup onthe server

You can back up both active and passivedatabases on Exchange Server 2010 or 2013Mailbox servers in the DAG environment. Youcan perform both full and incrementalbackups.

Backup to a local storage node in a stand-alone environment

You can configure a virtual client to direct itsbackups to the storage node on the physicalhost on which it resides. To configure a virtualclient, type curphyhost in the Storage Nodesattribute of the virtual client. This variable isnot supported for DAG environments. TheNetWorker Administration Guide provides moreinformation about curphyhost.

Backup to a remote storage node in a DAG ornon-DAG environment

You can perform Exchange Server 2010 and2013 database backups by using a remoteNetWorker storage node. The Exchangeserver and NetWorker storage node are ondifferent computers in the non-DAGenvironment. You can perform both full andincremental backups.NMM does not support server-baseddedicated storage nodes in a DAGenvironment. Select No for the Dedicatedstorage node option in the Device propertiesdialog when configuring the storage node in aDAG environment. Refer to Configuringbackups to use a remote storage node in aDAG environment to use a remote storagenode in a DAG environment.

A regular storage node license is required forDAG LAN-free backups. The NetWorkerAdministration Guide provides details.

Configuring a backup pool

First, you must create a backup pool to store the save sets that contain metadata andthen configure the backup pool.

Procedure

1. Open the NetWorker Administration GUI.

2. Click Media.

3. In the expanded left pane, select Media Pools.

4. From the File menu, select New.

5. In the Name field, type a name that matches the label template.

6. In the Comment field, specify a comment for the pool.

Backup

Configuring a backup pool 51

7. Select the Enabled field.

8. For the Pool type field, select the backup pool type.

9. For the Label template field, select the matching label template.

10. Perform either of the following steps:

l Click the Selection Criteria tab, and specify an NMM client for the Clientsfield. A value must be typed for this attribute if you choose not to specifygroups in the Groups field.

l In the Groups field, select the applicable backup groups.

11. In the Devices attribute, select each device that can accept backups for thispool.

12. Click OK.

Configuring snapshot policiesThe NetWorker Module for Microsoft Administration Guide provides the information thatyou need to create snapshot policies. In addition, review the following Exchange-specific information on snapshot policies:

l You can retain snapshots only for full level backups, not for incremental levelbackups. Use the NSR_EXCH_RETAIN_SNAPSHOTS=yes attribute to configurepersistent snapshots for full backups. Add this attribute in the Client Properties >Apps & Modules tab > Application Information field when configuring the clientresource. In the snapshot policy, the Backup Snapshot field should list FULL. Clearthe Force Incremental check box in the Backup Group properties.The Client Configuration wizard does not insert theNSR_EXCH_RETAIN_SNAPSHOTS=yes parameter into the ApplicationInformation field. You must enter this parameter manually after completing thewizard.

The specified snapshot policy allows snapshots to be stored locally on the clientfor a period of time before expiration. Locally stored snapshots present a risk ofdata loss if there is a failure of the local media containing the snapshot, or if asnapshot rollover fails and the corresponding locally retained snapshot expiresbefore a manual rollover can be performed.

l Follow these steps when you create the snapshot policy in the Client Propertiesdialog in the NetWorker Management Console:

1. Set the number of snapshots that you want to retain on the NMM client in theRetain Snapshots field.For incremental backups, set the Retain Snapshots attribute to “0.” Otherwise,an error occurs and the following error message appears in NMM.raw:

NMM .. Error: Local retention of snapshots is not allowedwhen snapshot level is not set to "full". Group: "%s"Snapshot Policy: "%s" Snapshots Per Day: "%s" Retain: "%s"Backup Snapshots: "%s" Level: "%s".NMM.. Unable to continue backup. "APPLICATIONS:\MicrosoftExchange 2007" snapshot policy requirements are not met.

2. Type First, Last, All, every n, or n in the Backup Snapshots field for thesnapshots that you want to roll over to the NetWorker server on a daily basis.Backup Snapshots should always be All if you plan to only retain snapshots forfull level backups.None and 0 are invalid entries for this field.

This configuration results in the most recent n backups that are stored locallyon the NMM client, where n is the number added in the snapshot policy's

Backup


Retain Snapshots field. If the snapshot policy designates a backup to be rolledover to the server, it is also be retained locally until there are n newersnapshots present.

l When using a snapshot policy on an Exchange Server 2010, perform only oneExchange Server 2010 client backup at a time with a particular backup group.Multiple Exchange 2010 client backups using same backup group must not beperformed.

l Use the Rollover Only backup policy for Federated backups. Persistent snapshotsare not supported for Federated backup.

The snapshots are stored locally on the NMM client and not on the NetWorker server.Snapshots that are stored locally present a risk of data loss in the event that themedia has failed.

Configuring 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, whileincremental backups include only the data that has changed since the last backup.

The procedure for creating a backup schedule for an NMM client is the same as forcreating a backup schedule for a normal NetWorker client.

The following table contains the considerations for configuring a backup schedule forrollover backup operations.

Table 15 Considerations for NMM client backup schedules

Backup levels Considerations

Full Full level backups are supported for all types of data.Snapshot backups must be set to full level where the Retainsnapshots property is not 0.

Incremental Incremental level backups are supported for the following:

l Backup of Microsoft Exchange Server 2007



1 to 9 Level 1 to 9 backups are not supported by NMM.

Creating a backup scheduleProcedure

1. In the Administration window, click Protection.

2. In the expanded left pane, select Schedules.


The Create Schedule dialog box appears.

4. In the Name box, type a name for the schedule.

5. From the Period list, select Week or Month to control whether the schedulerepeats on a weekly or monthly basis.

6. (Optional) Specify a description of the schedule in the Comment box.

Backup

Configuring a backup schedule 53

7. Set the backup level for each day by right-clicking the day, selecting Set Leveland then the backup level.

8. (Optional) Set the override backup level for a day by right-clicking the day,selecting Override Level and then the backup level.

For example, to prevent a full backup from running on a holiday, override theschedule so that the full backup runs on the day before or the day after theholiday. An asterisk (*) next to a backup level indicates that an override hasbeen set for that day.

Note

If you override backup levels by using the nsradmin command line program,you can also specify relative date values such as full first fridayevery 2 week. The nsr_schedule man page or the EMC NetWorkerCommand Reference Guide contain more information about overriding backuplevels.

9. Click OK.

Configuring a backup group

Backup groups enable you to balance backup loads to reduce the impact on thestorage and network resources.

To associate a backup group with a pool resource, go to the pool resource, right-clickand select Properties, and select the newly created group listed under Basic > DataSource > Groups.

Use a backup group to assign the following attributes to a set of client resources:

l Backup start times

l Backup pools

l Schedules

l Snapshot policy

Review the following information when creating a group resource:

l Do not create multiple instances of the same client in one backup group whenconfiguring a backup. Two backups on one client in parallel cannot be performed.

l When creating a backup group, consider the impact of the NMM and groupresources on the browse and retention policies.For example, if client resource A has save set X, and client A belongs to twogroups, group_1 for a full backup and group_2 for an incremental backup, the fullbackup of save set X expires before the incremental backup of save set X. Thisoccurs because the client resource A and the save set belong two differentgroups. Create only one group resource for a client resource even when both fulland incremental level backups are performed.

l When the Retain Snapshots property is set to a value greater than 0, ensure thatthe Force Incremental option is clear (this option is selected by default).Otherwise, the backup fails.

You must complete the required steps to configure a backup group.

Procedure


Backup


2. Click Configuration.

3. In the expanded left pane, select Groups.


The Group Properties dialog box appears, as shown in the following figure.

Figure 10 Group Properties dialog

5. Click the Setup tab.

6. In the Name field, type a name for the backup group.

7. In the Comment field, type a description.

8. In the Start Time field, type the time at which the first snapshot must becreated. The value for Start Time must specify the number of snapshots thatmust be created in a 24-hour period.

For example, to take four snapshots per day and for the first snapshot creationto occur at 4:00 a.m. (Start Time value), the Group Resource Interval valuemust be set to 5 hours or less:

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

9. In the Autostart field, select Enabled.

10. Select the Snapshot field for VSS-based (snapshot) backups.

11. In the Snapshot Policy field, select a snapshot policy.

The Number of Snapshots value works with the Group Resource Interval andStart Time values. The values for Start Time and Group Resource Interval mustspecify the number of snapshots that must be created in a 24-hour period.

12. In the Snapshot Pool field, select a pool that was created for the snapshot.

13. Click the Advanced tab.

14. For the Interval field, specify how often a snapshot must be created. TheInterval value works with the following values:

l The backup group Start Time value.

l The snapshot policy Number of Snapshots value.

Backup

Configuring a backup group 55

15. Ensure that Restart Window value is set to 00:01.

16. Set the Client Retries value to 0 (zero). This value specifies the number oftimes NetWorker tries to back up a failed client.

17. Click OK to create the backup group.

NOTICE

After starting a snapshot of a save group, do not interrupt or halt the snapshotprocess. For example, in an Exchange Server backup, thensrsnap_vss_save.exe process on the production server and the eseutil processon the proxy server may continue to run after the snapshot process is halted.

The process to stop a group in the NetWorker Administration GUI takes a longtime to complete.NMM does not support Group Properties specifications for browse andretention policies that override the client specifications.

Configuring Exchange client resources

A client resource specifies what to include in a snapshot of an NMM client. NMMassociates client resources with other backup resources, such as groups and snapshotpolicies. NMM treats public folders as stand-alone databases.

Table 16 Procedures for backing up Exchange Server 2010 and 2013 DAGs

Exchange clientresource

Examples

Exchange DAG While you can perform backups on active database copies or passivedatabase copies, you can only perform recovery to the Exchangeserver that is hosting the active database copy.When backing up active or passive database copies in the ExchangeDAG environment, use the Federated backup solution in order to besthandle fail over scenarios. Using the Federated solution allowsbackups of passive database copies to continue even when thepassive database copies move among Exchange servers. Refer to Using federated DAG backups on Exchange Server 2010 andExchange Server 2013, or use the Client Configuration wizard toconfigure the client resources necessary for a Federated backup.

Table 17 Procedures for backing up Exchange 2007databases

Exchange client resource Details Examples

Exchange 2007 stand-alone,LCR, or SCC

An Exchange client resourcecan be specified to perform afull backup or a storage groupbackup.

For Exchange virtual servercluster and SCC backups,client resources are createdfor the virtual client and allthe cluster nodes, which arepart of the cluster. But thebackups are always done by

Backup


Table 17 Procedures for backing up Exchange 2007databases (continued)


using the virtual clientresource.For example, to performbackup from an active nodewith two physical nodes andone virtual node, you mustconfigure three clientresources:

l Client for Physical Node 1

l Client for Physical Node 2

l Client for Virtual Node

Exchange 2007 CCR The steps vary depending onwhether the node is theactive node or passive node.For all Exchange clusterbackups, ensure that clientresources are created for thevirtual client and all thecluster nodes, which are partof the cluster. Both active andpassive node backups useseparate group resources inthe NetWorker server forbackup.

While you can performbackups from both the activenode and the passive node,you can only performrecoveries to the active node.When backing up Exchangefrom the active or passivenode in the Exchange 2007CCR environment, you mustcreate two client nodes andone virtual client to take careof fail over scenarios.

Configuration examples of failover scenarios:

l Scenario 1: Performbackup from passive node— To perform backupfrom a passive node, youmust configure threeclient resources:— Client for physicalnode 1 (T and attributesare required)

— Client for physicalnode 2(NSR_INDEX_CLIENTand NSR_VIRT_SERVattributes are required)

— Client for virtual node(NSR_INDEX_CLIENTand NSR_VIRT_SERVattributes are notrequired)

Public folders are notincluded in backups fromthe passive node.

Backup

Configuring Exchange client resources 57

Table 17 Procedures for backing up Exchange 2007databases (continued)


l Scenario 2: Performbackup from active node— To perform backupsfor an active node, youmust perform the backupfrom the virtual nodeclient resource.Configure:— Client for PhysicalNode 1(NSR_INDEX_CLIENTand NSR_VIRT_SERVattributes are notrequired)

— Client for PhysicalNode 2(NSR_INDEX_CLIENTand NSR_VIRT_SERVattributes are notrequired)

— Client for Virtual Node(NSR_INDEX_CLIENTand NSR_VIRT_SERVattributes are notrequired)

In both of thesescenarios, configuring allthree client resourcesincludes a fail overscenario becauseNetWorker requires abackup all of the clientresources of the server.

Public folders areincluded in backups of theactive node.

The table below describes how to determine the name to specify for the clientresource.

Table 18 Exchange Server name attributes

Type of backup Requirement

For Exchange stand-alone,LCR, or SCC backups

Type one of the following:

l The FQDN of the NetWorker client computer.

l The hostname of the NetWorker client computer.

Backup


Table 18 Exchange Server name attributes (continued)

Type of backup Requirement

For an Exchange CCR activenode or passive node

For the virtual server and all the physical computers in theCCR environment, type the host name.For active nodes, type the Exchange virtual server hostname.

For passive nodes, type both of the following:

l For the Exchange virtual server, type the Exchange virtualserver hostname.

l For each physical computer of the CCR environment,type the physical computer host name.

For an Exchange 2010 or 2013DAG

l For a Federated or non-Federated backup, type theExchange DAG name.

l For each physical computer of the DAG environment,type the physical computer host name.

The table below provides the list of Exchange 2007 save sets for application data.

Table 19 Exchange Server 2007 save set names

Type of backup data Save set syntax

All Exchange Server 2007 data APPLICATIONS:\Microsoft Exchange 2007

A specific Exchange Server 2007 storagegroup

APPLICATIONS:\Microsoft Exchange2007\<Storage group name>

All Exchange Server 2007 data in a CCRenvironment on the active or passive node

APPLICATIONS:\Microsoft Exchange 2007

A specific Exchange Server 2007 storagegroup in a CCR environment on the active orpassive node


All Exchange Server 2007 data on a virtualserver, on the active CCR node.

APPLICATIONS:\Microsoft Exchange 2007When backing up an Exchange Server 2007 ina CCR environment on a passive CCR node,you must use the NSR_INDEX_CLIENT andNSR_VIRT_SERV attributes.

All Exchange Server 2007 data in a LCRenvironment.


A specific Exchange Server 2007 storagegroup in a LCR environment.


The table below provides the list of Exchange Server 2010 save sets for applicationdata.

Table 20 Exchange 2010 save set names


Writer level APPLICATIONS:\Microsoft Exchange 2010

Backup


Table 20 Exchange 2010 save set names (continued)


Database name level APPLICATIONS:\Microsoft Exchange 2010\<Database name>

The table below provides the list of Exchange Server 2013 save sets for applicationdata..

Table 21 Exchange 2013 save set names


Writer level APPLICATIONS:\Microsoft Exchange 2013

Database name level APPLICATIONS:\Microsoft Exchange 2013\<Database name>

Exclude Exchange database NSR_EXCLUDE_COMPONENTS=db1,db2…

The table below lists the Application Information attributes for various backup types.

Table 22 Application Information attributes for Exchange Server

Type of backup Application variable to be used

For Exchange stand-alone, LCR, or SCCbackups

NSR_SNAP_TYPE=vssNSR_ALT_PATH=<mount_path_on_local_host>

Create a new directory path, for example C:\mount_dir on the client computer byspecifying NSR_ALT_PATH=C:\mount_dir.

Before performing a backup, empty thecontents of the specified alternate path forthe NSR_ALT_PATH attribute. Any datapreviously stored in that location will bedeleted.

For an Exchange CCR or DAG active node NSR_SNAP_TYPE=vssNSR_ALT_PATH=<mount_path_on_local_host>

The NSR_ALT_PATH attribute should specifya directory path for a folder on a local disk,not a shared cluster disk.


Exclude Exchange database NSR_EXCLUDE_COMPONENTS=db1,db2…

For an Exchange CCR passive node Perform these steps for both the physicalnodes as to cover a failover situation.

Backup


Table 22 Application Information attributes for Exchange Server (continued)


However, only enable the current passivenode for backups:Type the following variables and values:

NSR_SNAP_TYPE=vss

NSR_ALT_PATH=<mount_path_on_local_host>



For a passive node client resource, but not thevirtual server resource, also specify thefollowing:

NSR_VIRT_SERV=<Exchange_Virtual_Server_hostname>

NSR_INDEX_CLIENT=<Exchange_Virtual_Server_hostname>

For an Exchange DAG passive node Perform these steps for both the physicalnodes as to address failover requirements.However, only enable the current passivenode for backups:Type the following variables and values:

NSR_SNAP_TYPE=vss




For a passive node client resource, but not thevirtual server resource, also specify thefollowing:

NSR_EXCH_DAG or NSR_EXCH2010_DAGset to one of the following values:

l All: Back up all passive, active and stand-alone databases

Backup


Table 22 Application Information attributes for Exchange Server (continued)


l Passive: Back up only passive databasesin the DAG.

l Active: Back up only active and stand-alone databases in the DAG.

For an Exchange 2010 or 2013 Federated DAGbackup

Type the following variables and values:NSR_SNAP_TYPE=vss

NSR_EXCH_DAG=<dagname>orNSR_EXCH2010_DAG=<dagname>



NSR_FEDERATED_BACKUP=yes

NSR_FEDERATED_PSOL: Type a comma-separated list of the order in which to back upthe databases on each server in the DAG. Ifyou do not specify a list, the coordinatingnode distributes the backups based on anunordered list of Exchange servers in theDAG.

NSR_EXCH_INCL_SA: Type False to excludepublic folders and stand-alone databases. Thedefault setting is True.

NSR_EXCH _BACKUP orNSR_EXCH2010_BACKUP: Type one of thefollowing:

l Preferred: To back up the passive copy orreplica of each database if one exists. TheExchange server on which each passivedatabase is backed up is determined bythe preferred server order list. If nopassive database exists, then the activedatabase is backed up.

l Passive: To back up only passivedatabases in the DAG.

l Active: To back up only active databasesin the DAG.

To create a client resource, you can use either of the following methods from theNetWorker Management Console:

l Creating a client resource using the Client Configuration wizard.

Backup


l Creating a client resource for Exchange backups by using the NetWorkerManagement Console

Creating a client resource using the Client Backup Configuration wizardThis describes the Client Backup Configuration wizard procedure.

To use the Client Backup Configuration wizard option from the NetWorkerManagement Console, you must install the NMM client on the Exchange server.

NOTICE

Do not use the Client Configuration wizard to configure client resources for ExchangeServer LCR or SCC configurations. Follow the procedure in Creating a client resourcefor Exchange backups by using the NetWorker Management Console to manuallycreate client resources for Exchange Server LCR or SCC configurations.

Procedure

1. In the Administration view of the NetWorker Management Console, select theConfiguration tab, and then from the menu bar, select Configuration > NewClient wizard.

Figure 11 Initial screen of Client Backup Configuration wizard

2. On the Specify the Client Name and Type screen:

a. In the Client name field, type the name of the client where NMM is installed.

Note

Do not use the IP address for the client name because it can cause errors.

l For stand-alone configurations, type the name of the client where NMMis installed.

l For CCR configurations, type the virtual server name to configure anactive node backup, or type the physical host name to configure apassive node backup.

Backup


l For federated backup client backup configurations, type the DAG name.

l For non-federated backup client backup configurations, type the DAGnode name.

Note

If you created the client using the short name, provide the short name in theClient name field. If you created the client using the FQDN, provide theFQDN in the Client name field.

b. Select the Traditional NetWorker Client option.

c. Click Next.

3. On the Select the Backup Application Type screen, click on the MicrosoftExchange Server listed under Available Applications and then click Next.

4. On the Specify the Client Backup Options screen:

a. If you use Client Direct, then select the Client Direct checkbox.

The default setting is checked.

b. If you use parallel save streams per save set, then select Parallel savestreams per save set.

c. Leave the Target Pool field blank.

d. Select one of the following deduplication options:

l None if you have not configured data deduplication.

l Data Domain backup if you are using a Data Domain device for datadeduplication. After selecting this option, enter the IP address of theData Domain device.

l Avamar deduplication backup if you are using an Avamar device fordata deduplication. After selecting this option, select the Avamar nodefrom the available list.

e. Click Next.

5. On the Select the Exchange Server Objects screen, verify that the storagegroups and databases to back up are selected and then click Next.

By default, all of the storage groups and databases are selected for the entireserver backup. Clear the checkbox for any items that need to be excluded fromthe backup.

6. On the Exchange Backup Options screen:

a. In the Database Backup Options group, select one of the following:

Note

The Database Backup Options group is not displayed for Exchange 2007CCR or Exchange stand-alone servers.

l For federated backup client backup configurations:

n Preferred Passive Backup to back up passive or replica copies of thedatabases.If no replica copy exists for the database, the active copy is backedup.

Backup


n Passive Only Backup to back up only passive copies or replicas ofdatabases.

n Active Only Backup to back up only active copies of databases.

l For non-federated backup client backup configurations:

n Active Backup to back up only active copies of databases.

n Passive Backup to back up only passive copies or replicas ofdatabases.

n Passive and Active Backup to back up passive or replica copies ofdatabases.

Note

When you select Active Backup or Passive and Active Backup, thebackup fails if the selected type of database does not exist.

b. For non-federated backup client backup configurations and stand-aloneservers, the Data Mover Options group is visible but disabled.

c. For federated backup client backup configurations, in the FederatedOptions group:

a. Select Use Preferred Server Order List to specify the order in which toback up servers.By default, the Use Preferred Server Order List is selected.

b. Select a server from the Available Servers list and then click the rightarrow to move it to the Preferred Server List.To adjust the order of servers:

a. Select a server in the Preferred Server List.

b. Click the up and down arrows to change the order.

c. Select Include Standalone and Public Folder databases to back upstand-alone and public folders.By default, the Include Standalone and Public Folder checkbox isselected.

d. In the Mount Location field, type the path where you want to mount theExchange snapshots during the backup process. This field is required.

Specify a path name that does not contain any files.

NMM creates the Mount Location when the path name specified does notexist on the client.

e. In the Consistency Check Options group, enable consistency checks byselecting the Perform a consistency check during backup option andconfigure the following settings:

a. Select the Perform consistency check only on databases option toonly validate Exchange databases and exclude transaction log files.

b. Select the Sequential consistency check option to validate theExchange files sequentially instead of in parallel.

c. Select the Throttle Consistency Check option and then choose theThrottle I/O Operations and Throttle Duration options to manage theperformance of the Consistency Check operation.

Backup


You can configure the number of consistency check I/O operations toperform before pausing and the length of time to pause between I/Ooperation cycles.

d. Select the Include JET Errors option to validate the event log for errorsbefore taking a snapshot.

f. Click Next.

7. On the Specify circular logging options screen:

a. Choose one of the following circular logging options:

l Promote to back up all databases and promote incremental backups tofull backups.

l Circular to back up only circular logging-enabled databases and promoteincremental backups to full backups.

l Skip to skip circular logging-enabled databases and allow incrementalbackups.

b. Click Next.

8. On the Select the NetWorker Client Properties screen:

a. If needed, reconfigure the browse policy by selecting an interval for theBrowse policy option.

To create a custom Browse policy interval:

a. Select the + to the right of the Browse policy interval list box.

b. In the Create Policy dialog box, type a name in the Policy name field.

c. In the Period spin control, enter the number of period intervals.

d. In the Period list box, select a period type.

e. Click OK.

b. If needed, reconfigure the retention policy by selecting an interval for theRetention policy option.

To create a custom Retention policy interval:

a. Select the + to the right of the Retention policy interval list box.

b. In the Create Policy dialog box, type a name in the Policy name field.

c. In the Period spin control, enter the number of period intervals.

d. In the Period list box, select a period type.

e. Click OK.

Note

Do not set the Browse policy and Retention policy to the same value.Doing so can result in data loss.

c. If needed, reconfigure the backup schedule by selecting an interval for theBackup schedule option.

d. Optionally, type a comment for the client in the Client Comment field.

e. For DAG and CCR environments, you must update the Remote access listfor each DAG or CCR node by doing one of the following:

l Manually add all of the DAG or CCR nodes by typing the following foreach node:

Backup


System@DAG_node or System@CCR_nodel Manually add all of the virtual client resource by typing the following:

System@DAG_resource or System@CCR_VIRTUAL_CLIENT

f. Click Next.

9. On the Specify the NetWorker Backup Group screen:

a. Do one of the following:

l Select the Add to an existing group option to select an existing savegroup and choose a save group from the provided list.Only save groups with valid snapshot policies are available for selection.

l Select the Create a new group option to create a new save group andconfigure the new group as follows:

a. In the Group Name field, type the name of the new save group.

b. On the Client Retries menu, select 0.

c. In the Scheduled Options group, in the Scheduled Backup StartTime field, type a valid 24-hour time.

d. Select the Automatically start the backup at the scheduled timeoption to automatically start the scheduled backup at the designatedtime.

e. In Advanced Options, select a snapshot pool from the SnapshotPool drop-down list.

f. In the Interval field, set the interval time.

g. In the Restart Window field, set the restart window to 0:01.

If you choose to create a new group, the Specify the NetWorker SnapshotPolicy screen appears in the wizard.

If the setup includes a storage node, the Specify the Storage NodeOptions screen appears in the wizard.

Note

Changing the storage node option changes the configuration for allconfigurations for the client.

b. Click Next.

10. If the Specify the NetWorker Snapshot Policy screen appears:

a. Perform one of the following options:

l To use an existing policy, select Select an existing snapshot policy andselect the snapshot policy to use for this group.

l To create a new snapshot policy, select Create a new snapshot policyand do the following:

a. In the Name field, type a name for the snapshot policy.

b. In the Number of Snapshots field, select the number of snapshots totake.

c. In the Retain Snapshots field, select the number of snapshots toretain.

d. In the Snapshot Expiration Policy drop-down list, choose anexpiration policy.

Backup


e. In the Backup Snapshot Options group, select an option for backingup snapshots.

b. Click Next.

11. On the Specify the Storage Node Options screen:

a. In the Backup Storage Nodes group, select one of the following options:

l Automatically select the storage node and devices for the client toautomatically select client storage nodes and devices.

l Backup to the NetWorker server only when the setup does not includea NetWorker storage node.

l Backup to the following storage nodes to select a specific NetWorkerstorage node. Select one of the storage nodes listed.

b. Click Next.

12. On the Backup Configuration Summary screen, review the details and do oneof the following:

l Click Back to revisit the previous pages.

l Click Create to configure the client resources.

13. On the Client Configuration Results screen, review the output of theconfiguration wizard and do one of the following:

l Click Back to modify the configuration data and rerun the Client BackupConfiguration wizard.

l Click Finish.

14. Optionally, to verify the configuration settings for the client:

a. Open the NetWorker Management Console and click the Configuration tab.

b. Right-click the client and select Modify Client Properties.

c. Click OK to close the Client Properties dialog box.

After you finish

If you specified a Retain Snapshots value greater than 0 in the Specify theNetWorker Snapshot Policy screen, after you complete the wizard you mustmanually add the Application Information attribute valueNSR_EXCH_RETAIN_SNAPSHOTS=yes in order to retain snapshots.

To add the attribute value:

1. Open the NetWorker Management Console and click the Configuration tab.

2. Right-click the client and select Modify Client Properties.

3. In the Client Properties dialog box, select the Apps & Modules tab.

4. In the Backup group, in the Application Information field, type the following:NSR_EXCH_RETAIN_SNAPSHOTS=yes.

5. Click OK.

Creating a client resource for Exchange backups by using the NetWorker Management Console

Review the considerations listed in the topic Planning DAG and non-DAG backupsbefore performing this procedure.

Backup


Procedure

1. In the Administration dialog of the NetWorker Management Console, clickConfiguration.

2. In the expanded left pane, select Clients.


4. Click the General tab.

5. In the Name attribute, type the Exchange Server name.

6. In the Comment attribute, type a description.

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

7. For the Browse Policy attribute, select a browse policy from the list.

The browse policy determines how long NetWorker makes the rolled-over dataavailable for browsing.

Ensure that the browse policy is long enough for the expected recovery needs.

8. For the Retention Policy attribute, select a retention policy from the list.

The NetWorker Module for Microsoft Administration Guide provides details aboutthe retention policy for Exchange.

9. Confirm that the Scheduled Backups attribute is selected.

10. In the Save Set attribute, specify the components to be backed up.

Place multiple entries on separate lines.

11. For the Group attribute, select the backup group to which this client resource isadded.

The backup group must be a snapshot group.

If you specify client resources for the same NMM client host to differentbackup groups, then ensure that you specify a Start Time attribute value thatdoes not cause the backups for the host client resources to overlap.

12. For the Schedule attribute, select a backup schedule.

Verify that the schedule obeys the conditions of the snapshot policies asdescribed in Configuring Exchange backups.

13. Click the Apps & Modules tab.

14. In the Access area, leave the Remote user and Password fields empty.

15. In the Backup command attribute, type the backup command:

nsrsnap_vss_save.exe

16. In the Application Information attribute, type the required variables andvalues. If you specify more than one Exchange attribute at a time, then typeeach entry and its value on a separate line.

Provide the appropriate application variables and values for your ExchangeServer environment.

17. In the Deduplication group, configure deduplication backups in a CCR or DAGenvironment for a passive node:

Backup


l If the pool configured for the NMM Exchange backups uses Data DomainBoost devices, select the Data Domain backups option to enable client-sideData Domain Boost deduplication backups.

l To enable Avamar deduplication backups, select the Avamar deduplicationbackup option, and choose the deduplication node to which this client'sbackup data is sent from the Avamar deduplication node menu. For DAGconfigurations, select the same deduplication node for the DAG memberserver client resource.

l Do not select the name of a replication node here. This step links this clientwith its own deduplication node.

l If the deduplication node for this client’s backup data changes, the nextbackup done must be a level 0 (full) backup. If the deduplication node forthis client’s backup data changes, the next backup performed must be alevel 0 (full) backup.

18. Click the Globals (1 of 2) tab and complete verify that the Aliases attributedisplays the NETBIOS name for the client.

This name is filled in automatically.

The NMM client uses the host computer NETBIOS or “short” name whenconnecting to the NetWorker server to browse backups. If the NETBIOS nameis not found, NMM does not display backups.

19. If using a NetWorker storage node, when configuring a client resource for theMailbox server and a DAG resource, click the Globals (2 of 2) tab and type thestorage node name in the Storage node name field.

20. Click OK.

21. For CCR or DAG environments, create a NetWorker client resource for thefollowing items:

l All remaining Exchange clients that are members of the CCR or DAG.

l The CCR or DAG name using the FQDN.

a. In the expanded left pane, select Clients.

b. From the File menu, select New.

c. In the Name attribute, type the Exchange Server name or FQDN.

d. In the Comment attribute, type a description.

Use this attribute to differentiate the purpose of each resource.

e. For the Browse Policy attribute, select a browse policy from the list.

f. For the Retention Policy attribute, select a retention policy from the list.

g. Confirm that the Scheduled Backups attribute is selected.

h. In the Save Set attribute, specify the components to be backed up.

i. Deselect the default group.

No additional configuration is needed; the client resource only must exist.

Configuring NetWorker administrator privileges

The NMM client must be manually granted NetWorker administrator privileges toperform media database operations during snapshot deletion.

Backup


NOTICE

If you set up a proxy client for the NMM client, grant the proxy client NetWorkeradministrator privileges. If you are setting up a NMM client in a cluster, grantNetWorker administrator privileges to each cluster node and virtual server.

You must complete the required steps to manually configure privileges.

Procedure


2. Click Configuration.

3. In the expanded left pane, click User Groups.

4. Right-click the Application Administrators group, and then select Properties.

The Properties dialog box appears.

5. In the Users field, add the following values for the NMM client host. Place eachvalue on a separate line:

user=administrator,host=NMM_client_hostuser=system,host=NMM_client_hostwhere NMM_client_host is the DNS hostname of the NMM client.

Place each value on a separate line.

6. If a proxy client is set up for the NMM client:

l Where a single user is granted administrator rights to perform all theNetWorker functionality for a host, add the following values:

user=administrator,host=NMM_calientproxy_hostuser=system,host=NMM_clientproxy_host

l Where multiple users are configured and added to an administrator groupand that group is added on the NetWorker privilege list, all the users underthis group have administrator rights.

To perform all the NetWorker functionality for a host, add the followingvalues:

group=administrator,host=NMM_clientproxy_hostgroup=system,host=NMM_clientproxy_host

7. If the NMM client is installed in a cluster, grant NetWorker administratorprivileges to each of the following nodes:

l Cluster node (both active and passive nodes)

l Virtual server

8. Click OK.

All NMM users must have administrator level privileges.

Configuring a non-federated or federated DAG backup

You can configure a Federated or non-Federated DAG environment by using the ClientConfiguration wizard or by manually configuring the NetWorker client resources. Tomanually configure the client resources, you must specify the Application Information

Backup

Configuring a non-federated or federated DAG backup 71

attribute and provide a backup command for the virtual DAG name or the physicalDAG nodes.

Manually configuring NetWorker client resources for a non-federated Exchange Server backupProcedure

1. Create a NetWorker client resource for each physical DAG node and the virtualDAG name.

2. Specify save set and Application Information for the NetWorker client resourceof each physical DAG node.

3. Enable the scheduled backup option for the physical DAG nodes.

4. Assign backup groups to the NetWorker client resources of each physical DAGnode which you back up.

5. Verify that the virtual DAG name is not part of any backup group.

Manually configuring NetWorker client resources for a federated Exchange Server backup

Verify that the NetWorker client resources of the physical DAG nodes are not part ofany backup group.

Procedure

1. Create a NetWorker client resource for each physical DAG node and the virtualDAG name.

2. Specify save set and Application Information attributes and add a backupcommand under the virtual DAG name.

3. Enable the scheduled backup option for the NetWorker client resource of thevirtual DAG name.

4. Assign a backup group to the NetWorker client resource of the virtual DAGname which you back up.

Excluding Exchange databases from backup

NMM provides the user the option to exclude certain Exchange databases from thebackup. The user specifies the writer-level save set and components that are notrequired for backup. The specified components are excluded from the backup and thedetails are logged in the NMM.raw log file. This feature ensures that any new databaseadded to the deployment are automatically backed up.

Use the parameter NSR_EXCLUDE_COMPONENTS=vm1,vm2… in the ApplicationInformation field when configuring the client resource. This parameter is optional andcan be applied only when a user specifies a writer-level save set. This parameter doesnot apply to item-level save sets.

NSR_SKIP_OFFLINE_COMPONENTS is used to skip components, which are offlinefrom the backup. This parameter applies only to Hyper-V backups and does not applyto Exchange backups.

Backup


Configuring Exchange 2007 storage groupsThis topic provides information on how to schedule backups for Exchangeconfigurations including those with more than 10 Exchange storage groups.

Procedure

1. Complete the backup configuration that matches your configuration scenarioaccording to the details provided in Backup configuration options.

2. Divide the Exchange storage groups into sets of 10:

l Consider the size of each storage group and the time it takes to back upeach set.

l Try to ensure that the size of the data for each set of 10 is roughly the same.This ensures predicable backup windows.

a. For the existing exchange client that contains more than 10 storage groups,create one additional copy of the client for each set of the 10 Exchangestorage groups to back up all the sets.

For example, if you have 30 storage groups, create two additional copies ofthe client.

b. If you configured a data deduplication backup for the passive node, then alsomake a copy of the Exchange virtual server client that was created as part ofthis configuration.

3. For the existing exchange client that contains more than 10 storage groups,modify the save set attributes to list the first 10 Exchange storage groups thatyou want to back up. If you configured a deduplication backup for the passivenode, then also modify the Exchange virtual server client resource that youcreated as part of this configuration. By doing so, you set the save set to listthe first 10 Exchange storage groups that you want to back up.

4. For each subsequent set of 10, repeat the above step for the copy of the clientresource created.

5. For the group resource that contains the Exchange clients:

a. Create one additional copy of the group, without copying clients, for eachset of 10 Exchange storage groups to back up all the sets.

For example, if you have 30 storage groups, create two additional copies ofthe group.

b. On the General tab of the Group properties dialog, disable Autostart forthe new groups and then click OK.

6. For any additional clients created to accommodate more than 10 storagegroups, add one client to each group that you have just created. If you haveconfigured a deduplication backup for the passive node, also add the Exchangevirtual server client resource with the same save set as the client that you justadded to the same group.

7. Repeat the previous two steps for each remaining set of 10 clients.

8. Schedule the groups to run.

Multiple NetWorker groups cannot run at the same time on the same client forNMM, so ensure that you schedule the groups to run sequentially.For example, you can schedule the groups to run as follows:

Backup

Configuring Exchange 2007 storage groups 73

a. Schedule the first group on the first night to determine how long a backuptakes.

b. Add the second group to the schedule for the second night.

c. Assign the group a start time based on the run time of the first group fromthe night before.

d. Repeat the process until all groups are scheduled.

Configuring Avamar deduplication backups in a CCR Passive node backup orDAG environment

You must configure passive node clients (Exchange 2007 CCR) or DAG memberclients (Exchange Server 2010 and 2013) with the regular Avamar Storage nodebackup settings. In addition, follow the extra steps below, to perform passive node orDAG backups with the Avamar storage Node.

For Exchange 2010 and 2013, ensure that you complete the following prerequisitesbefore starting a DAG backup:

l Create client resources for all DAG member servers.

l Create a client resource with the DAG name.

Before you start a CCR passive node or DAG backup, you must perform the followingsteps in NMC:

Procedure

1. In the NetWorker server's administration interface, click Configuration.

2. Select Clients in the navigation tree.

The Clients table appears.

3. Right-click Clients in the navigation tree, or right-click any client in the Clientstable, and select New.

The General tab appears in the Create Client dialog.

4. Specify the Exchange CCR virtual server name or DAG name in the Nameattribute.

5. Clear the Scheduled backup option.

6. In the Save set list, add the same save set list that is in the passive node clientresource.

7. Click the Apps & Modules tab.

8. In the Access area, leave the Remote user and Password fields empty.

9. In the De-Duplication area, select the Avamar deduplication backup attributeto enable this client for deduplication backups.

10. In the Avamar deduplication node drop-down, select the name of thededuplication node to which this client's backup data is sent. Use the samededuplication node specified for the Passive node server client resource or theDAG member server.

This step links this client with its own deduplication node. Do not select thename of a replication node.

11. Click OK.

Backup


12. Add this new CCR Virtual Client or DAG client resource to the backup groupthat contains the CCR Passive node or DAG member client resource.

13. Start the passive node or DAG backup.

Complete list of Exchange Server Application Information attributes

The table below provides the complete list of Application Information attributes forExchange Server client resource configurations.

Table 23 Exchange Application Information attribute settings

Attribute name Description Values

NSR_SNAP_TYPE=value Specifies the snapshotservice provider name.

vssThis value is required.

NSR_ALT_PATH=value Exchange snapshots aremounted so that the databaseconsistency check can be run.Create the directory path, forexample C:\mount_dir on theclient computer by specifying:NSR_ALT_PATH=C:\mount_dir

A mount path.For example,NSR_ALT_PATH=G:\mount_replica\

If the file system pathspecified for NSR_ALT_PATHin Exchange client does notexist, then NMMautomatically creates thedirectory.

Before performing a backup,empty the contents of thespecified alternate path forthe NSR_ALT_PATHattribute. Any data previouslystored in that location will bedeleted.

NSR_VIRT_SERV=value Specifies the name of theExchange virtual server clientresource in a CCR passivenode backup.This attribute only applies toExchange Server 2007 CCRpassive node backups.

The name of the Exchangevirtual server.For example,NSR_VIRT_SERV=virtual_server_name

NSR_INDEX_CLIENT=value Specifies that the backupmust be indexed under theclient name of the Exchangevirtual server but not thepassive node client name in aCCR passive node backup.This attribute only applies toExchange Server 2007 CCRpassive node backups.

The name of the Exchangevirtual server.For example,NSR_INDEX_CLIENT=virtual_server_name

NSR_CHECK_JET_ERRORS=value

Used to detect Jet errors inthe Exchange backup.NSR_CHECK_JET_ERRORS

Values include the following:

Backup

Complete list of Exchange Server Application Information attributes 75

Table 23 Exchange Application Information attribute settings (continued)


is run before committing theshadow copy for Exchange.If the backup encounters JETerrors, then the snapshotfails.

l 447 (Exchange Server2007 only)

l 448 (Exchange Server2007 only)

l 1018

l 1019

l 1022

l all

l noneSeparate values with acomma. For example:

NSR_CHECK_JET_ERRORS=1018,1019

The default value is All.

NSR_EXCHANGE_LIMIT_SG=value

This attribute is used to setthe number of storage groupsfor a save set. The option yesor no can be specified for thisattribute. If set to yes, thesave set is restricted to amaximum of 10 storagegroups.This attribute only applies toExchange Server 2007.

yes or noDefault value is yes.

Sets the number of storagegroups for scheduled backupto 10.

NSR_EXCH_RETAIN_SNAPSHOTS=value

Specifies snapshot retentionfor only full backups.

yes or noDefault value is no.

Retains snapshots for fullbackup.

Must be manually specified;this attribute can not bespecified in the ClientConfiguration wizard.

For incremental backups,perform only RolloverOnlybackup. NMM promotes tofull if an incremental backup isattempted with this value set.

NSR_EXCH_CHECK=value Specifies if consistency checkshould be run or not fordatabases.

yes or noIf you do not specify a value,NMM applies the followingdefault values:

l Exchange Server 2010and 2013 DAG backup: no

Backup


Table 23 Exchange Application Information attribute settings (continued)


l Exchange Server 2010and 2013 stand-alonebackups: yes

l Exchange 2007 backups:yesIf the value is no, thenNMM writes informationto the nmm.raw fileduring a backup.

NSR_EXCH_DAG=<DAG name>or NSR_EXCH2010_DAG=<DAG name>

To specify the DAG name fora backup in a DAGenvironment.Federated backup do notrequire this attribute.

FQDN of the DAG.For example,NSR_EXCH_DAG=mydag.domainname.com

NSR_EXCH_BACKUP=active/passive/preferred orallor

NSR_EXCH2010_BACKUP =active/passive/preferred orall

To back up only activedatabase copies.

l active - back up onlyactive database copies.

l passive - back up onlypassive database copies.

l preferred - back up onlypassive copy or replica ofeach database if oneexists. If no passivedatabase exists, then theactive database is backedup.This attribute applies toExchange Server 2010and 2013 non-FederatedDAG backups.

l all - back up both activeand passive databases.This attribute applies toExchange Server 2010and 2013 non-FederatedDAG backups.

NSR_E2K7_VOL_CHECK=yes

To back up Exchange Server2007 databases and logs thatare on different mount pointsbut residing under same drive.

yes or no

NSR_EXCLUDE_COMPONENTS =db1,db2…

Excludes specified databasesfrom backup

name of database

The following application variables are examples for Exchange Server 2007 CCRpassive-node backups:

l NSR_SNAP_TYPE=vss

Backup

Complete list of Exchange Server Application Information attributes 77

l NSR_ALT_PATH=<e:\mountpath>

l NSR_EXCH_CHECK=<yes/no>

l NSR_INDEX_CLIENT=<CCR Virtual machine>

l NSR_VIRT_SERV=< CCR Virtual machine>

l NSR_EXCH_RETAIN_SNAPSHOTS=<yes/no>

l NSR_ESE_UTIL_SEQUENTIAL=<True/False>

l NSR_ESE_UTIL_THROTTLE=<True/False>

l NSR_CHECK_JET_ERRORS=<all/none/specific value>

The following application variables are examples for Exchange Server 2007 LCRbackups, Exchange Server 2007 active node backups, Exchange Server 2007 SCCbackups, Exchange Server 2010 stand-alone backups, and Exchange Server 2013stand-alone backups:

l NSR_SNAP_TYPE=vss







The following application variables are examples for Exchange Server 2010 and 2013non-Federated DAG backups:

l NSR_SNAP_TYPE=vss



l NSR_EXCH2010_BACKUP=<active/passive/all>

l NSR_EXCH2010_DAG=<DAG FQDN>





The following application variables are examples for Exchange Server 2010 and 2013Federated DAG backups:

l NSR_SNAP_TYPE=vss



l NSR_FEDERATED_BACKUP=yes

l NSR_FEDERATED_PSOL=<DAG Node1>,<DAG node2>,…,<DAG NodeN>

l NSR_EXCH_INCL_SA=<TRUE/FALSE>

l NSR_EXCH2010_BACKUP=<Preferred/active/passive/all>

l NSR_EXCH2010_DAG=<DAG FQDN>

Backup






Viewing a valid application data save set

When configuring a client resource, you must type the save sets in the Save Setattribute of the client resource.

To display a list of the application data save sets that are available for backup, open acommand prompt on the Exchange server and type the required command as providedin the following table:

Table 24 Commands for displaying valid application data save sets

Application server Command

l Exchange Server 2007, 2010, or 2013stand-alone node

l Exchange Server 2007 LCR active node

l Exchange Server 2010 and 2013 DAGserver client node (non-Federated)

At the command prompt, type:nsrsnap_vss_save -?

Example output:

“APPLICATIONS:\Microsoft Exchange 2010”

“APPLICATIONS:\Microsoft Exchange2010\Database 1”

“APPLICATIONS:\Microsoft Exchange2010\Database 2”

“APPLICATIONS:\Microsoft Exchange 2010\Database 3”

“APPLICATIONS:\Microsoft Exchange 2010\Database 4”

68150:nsrsnap_vss_save:nsrnsap_vss_save:Exiting with success.

This command only provides a list ofdatabases on the Exchange server from whichyou run the command.

To include the state of the database (verboseoutput), type:

nsrsnap_vss_save –v -?

Example output:


“APPLICATIONS:\Microsoft Exchange2010\Database1 -- Passive”

“APPLICATIONS:\Microsoft Exchange2010\Database2 -- Active”

68150:nsrsnap_vss_save:nsrnsap_vss_save:Exiting with success.

Exchange Server 2007 SCC At the command prompt, type the followingas one line:

Backup

Viewing a valid application data save set 79

Table 24 Commands for displaying valid application data save sets (continued)


nsrsnap_vss_save –c physical_server_name–A NSR_VIRT_SERV=virtual_server_name -?

Example output:


“APPLICATIONS:\Microsoft Exchange2007\SG1”



If the application server is on a virtual host,run this command from the physical node thatis currently hosting the application server.

Exchange Server 2007 CCR or SCR At the command prompt, type the followingon either the active or passive nodes as oneline:nsrsnap_vss_save –c physical_server_name–A NSR_VIRT_SERV=virtual_server_name -?

Example output:





Federated Exchange 2010 or 2013 DAG node At the command prompt, type the followingon any node in the DAG:nsrsnap_vss_save -ANSR_EXCH_DAG=dag_name -?

Example output:


“APPLICATIONS:\Microsoft Exchange2010\DB1”





Backup


Table 24 Commands for displaying valid application data save sets (continued)


The output contains all databases in the DAG.The -v option does not apply.

Remove the quotation marks when copying the save set name from the output.

Each line of output corresponds to a save set entry that you can add to the save setattribute of a client resource. Type each entry on a separate line.

URL encoding for Exchange save sets

When specifying save set names in the save set attribute of the client resource, youmust specify some special characters, such as the backward slash (\), by their URL-encoded values.

The following table lists the most commonly used special characters and their URLvalues.

Table 25 Special characters and their URL-encoded values

Special character URL-encodedvalue

Special character URL-encodedvalue

\ %5C ? %3F

/ %2F ] %5D

" %22 [ %5B

% %25 } %7D

# %23 { %7B

& %26 ^ %5E

< %3C ‘ %60

> %3E | %7C

When configuring a client resource, you must type the save sets in the save setattribute of the client resource. This section describes how to find the exact name of aparticular database, or Exchange Server instance and database combination thatneeds to be backed up during a scheduled backup.

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

1. Open a command prompt on the application server.

2. Type the required command.You can refer to Table 24 Commands for displaying valid application data save setsfor a list of valid commands.

l If this is an Exchange Server 2010 or 2013 stand-alone server and ExchangeServer 2010 or 2013 DAG server client node, type:nsrsnap_vss_save -?

l For an Exchange Server 2010 or 2013 DAG server client node, and you want toinclude the state of the database, type:

Backup

Viewing a valid application data save set 81

nsrsnap_vss_save -v -?

Remove the quotation marks when copying the save set name from the output.Also, do not include --Passive or -- Active when copying the output. Thesedenote the database state and are not part of the save set.

3. Press Enter.Each line of output corresponds to a save set entry that you can add to the SaveSet attribute of a client resource. Type each entry on a separate line.

Viewing volumes to back up for recovery

To view the volumes that you must back up in order to perform an Exchange Serverrecovery, perform either of the following steps using the NMM GUI:

l Right-click on the Exchange Writer level save set for which you want to view therequired volumes, and select Required volumes.The Required NetWorker Volumes dialog with details about the volume appears.

l Select any of the backed up storage groups and select Required volumes.The Required NetWorker Volumes dialog with details about the volume appears.

Circumstances that promote incremental backup to full backup

The following rules apply for incremental backups:

l When NMM cannot find a full backup for the database within the specified saveset, NMM promotes an incremental backup to a full backup.

l If you add a new Mailbox database to an existing save set, then NMM promotesthe next backup to a full backup.

l If NMM detects log gaps between the last backup and the current set of logs,NMM promotes an incremental backup to a full backup. For example, there aregaps between highest log number retrieved from index and the lowest log numberretrieved from the disk.

l If you change the database or the logs path after the last full backup, then NMMpromotes the next incremental backup to a full backup.

l If NMM detects any circular logging enabled databases on the system, then NMMpromotes backups depending upon the setting specified in theCIRCULAR_PROMOTION_POLICY parameter.

Performing an Exchange Server scheduled backupA thorough discussion of groups, group policy, data sets, schedules, and retentionpolicies is beyond the scope of this guide. The NetWorker Module for MicrosoftAdministration Guide provides additional information.

Procedure

1. Create a data set for the backups.

2. Create a schedule for backups.

3. Create a group for the backups. During the group creation process, you:

a. Assign the new data set to the new group.

b. Assign a schedule to the new group.

c. Assign a retention policy to the new group.

Backup


d. Add the Exchange server to the new group.

4. Enable scheduling for the group.

Using federated DAG backups on Exchange Server 2010 and Exchange Server2013

In a DAG environment, there can be multiple passive copies of databases distributedamong multiple Exchange servers. In order to back up a single passive copy of eachdatabase, you can perform a federated backup. NMM determines the Exchangeservers on which to perform the backups and ensure all databases within the DAG getbacked up

Databases within the DAG can be split up among multiple save groups. You can specifydifferent schedules to distribute the workload within the backup window.

NMM supports federated backups through a user-defined client resource that acts asa Coordinating Node. This client resource manages and monitors the backup of alldatabases in its DAG. The client resource points to the virtual DAG Exchange server inthe DAG which acts as the Coordinating Node.

Application Information attributes for federated backups

The following Application Information attributes are specific to federated backups:

l NSR_FEDERATED_BACKUP: Type yes to enable Federated backups.

l NSR_FEDERATED_PSOL: Type a comma-separated list of the order in which toback up the databases on each server in the DAG. If you do not specify a list, thecoordinating node distributes the backups based on an unordered list of Exchangeservers in the DAG.

l NSR_EXCH_INCL_SA: Type False to exclude public folder databases and stand-alone databases. The default setting is True.

l NSR_EXCH_BACKUP: Type one of the following:

n Passive--To back up only passive databases in the DAG.

n Active--To back up only active databases in the DAG.

n Preferred--To back up the passive copy or replica of each database if oneexists. The Exchange server on which each passive database are backed up isdetermined by the preferred server order list. If no passive database exists(either there is no replica or if the current replicas are all suspended), then theactive database is backed up.

Preferred Server Order List

When you perform a backup through the DAG resource using NSR_EXCH_BACKUPset to Passive or Preferred, NMM selects an Exchange server to back up the passivecopies of the databases. Because multiple Exchange servers can host replicas orpassive copies of the same database, you can specify a preferred server order list(PSOL) to tell NMM which Exchange servers to use to back up the Exchangedatabases. When the backup starts, NMM backs up the passive or replica copies ofeach database, running the backups from the Exchange servers in the order specifiedin the PSOL.

You create the PSOL in the Client Configuration wizard, and the PSOL is associatedwith a single DAG client resource. This list contains an ordered list of Exchange 2010or Exchange 2013 servers in the DAG and represents the order each is evaluated forpassive databases to be backed up.

Backup

Using federated DAG backups on Exchange Server 2010 and Exchange Server 2013 83

If you choose to include public folder databases or stand-alone databases, thecoordinating node determines if each exists on that server and if so, adds it to thesave set list as well. The coordinating node then goes to the second server in the list,skipping already listed databases and repeats the check for passive databases, publicfolder databases and stand-alone databases.

Once the coordinating node has gone through the ordered list of servers then it mustvalidate that there are no databases within the DAG that have been left out of the listof save sets. The coordinating node starts the backup work list on each of the serversidentified.

Circular logging in federated backups

NMM does not support circular logging-enabled databases in federated backups. Ifcircular logging-enabled databases exist within a DAG, you must be perform a non-federated backup.

Additional federated backup considerations

When configuring and managing federated backups, keep the following considerationsin mind:

l You must install NMM and NetWorker on each Exchange server within the DAG.This is because the virtual DAG resource can fail over to any of those Exchangeservers. NMM must be installed on any of the servers that the DAG resource failsover to so that it is able to start a federated backup.

l Each Exchange server for which a backup job is sent performs their backups inparallel with the other Exchange servers.

l Persistent snapshots are not supported for a federated backup. If theCoordinating Node discovers a request for a persistent snapshot, that backuprequest is not valid and fails immediately. All snapshots are required to be rolledover immediately, that is, Retain Snapshots must be 0.

l When configuring federated backups in the configuration wizard, you must givethe DAG name on the Specify the Client Name and Type dialog. This is differentfrom NMM 2.4 SP1 and earlier. In NMM 3.0 and later, if you provide a physicalserver name, an error appears.

Example of a federated backup

The following figure illustrates an example of a Federated backup of a DAG clusterwith three Exchange servers: MBX1, MBX2, and MBX3. The cluster contains fourExchange databases: DB1, DB2, DB3, and DB4. Each database can only have oneactive copy, but can have multiple passive or replica copies. In this example, there aretwo passive copies of DB1: one copy on two different Exchange servers (MBX2 andMBX3). The other databases (DB2, DB3, and DB4) only have one passive copy each inthe cluster. Only one copy of each database needs to be backed up. The preferredserver order list specifies to back up databases from the DAG in this order: MBX2,MBX3, and MBX1.

The figure below illustrates an example Exchange Server 2010 and Exchange Server2013 Federated backup.

Backup


Figure 12 Example of an Exchange Server 2010 and 2013 Federated backup

Verifying a backup

To verify if a backup is successful, use the following command on the NetWorkerclient:

nsrinfo_nmm -s <Server> <Client Name>

where the <Client Name> is the DAG name or Exchange Server 2010 or 2013 mailboxserver name.

Backup

Verifying a backup 85

Backup


CHAPTER 4

Mail Item Recovery


l Overview............................................................................................................88l Exchange recovery prerequisites....................................................................... 94l Configuring Exchange Server recovery..............................................................95l Recovery procedures........................................................................................100l Best practices and recommendations............................................................... 122

Mail Item Recovery 87

Overview

An Exchange recovery can serve many different purposes. The smallest unit ofgranularity of a backup is an Exchange database, log files, and checkpoint files. Thosebackups can be used to recover entire servers, individual databases, or mailbox items.

When you perform backups of a Microsoft Exchange environment with NMM, thefollowing recovery options are available for stand-alone and high-availabilityenvironments:

l Recover to the original location on the original Exchange server

l Recover to the Exchange Server 2010 or 2013 RDB or Exchange Server 2007 RSGon the original Exchange server

l Recover to an Exchange Server 2010 or 2013 RDB or Exchange Server 2007 RSGon a different Exchange server

l Message-level recovery using the Exchange GLR option

Recovery types

NMM provides many levels of recovery, such as recovering databases or recoveringindividual messages in a user mailbox.

Database level recovery

When you recover a storage group (Exchange Server 2007) or database (ExchangeServer 2010 and 2013), it generally overwrites the current database unless yourecover to an RSG or RDB.

Message level and granular level recoveryWhen you need to retrieve individual user mailboxes, user mail folders, or messages,you can do so without overwriting entire mail databases. You can recover a storagegroup to an Exchange RSG or recover a database to an Exchange RDB, and then useExchange server management tools or NMM Granular Level Recovery (GLR) to selectand recover individual mailboxes, folders, or messages. Those recovery procedures areprovided in the Message and Granular Level Recovery section.

DAG federated backup recovery

A federated DAG backup provides access to backups of all Exchange databasesthrough one NMM client, even though they came from multiple Exchange servers inthe DAG. The recovery process to recover from a DAG Federated backup is the sameas a normal DAG recovery.

Public mailbox recovery

Public mailboxes are new with Exchange Server 2013. You can recover a publicmailbox just as you would any other user mailbox.

Restoring Exchange dataThis topic provides an overview of an Exchange database recovery.

In a conventional Exchange recovery, entire databases are replaced or recovered. Thisis most useful for disaster recovery-level recovery or for moving Exchange databases

Mail Item Recovery


to another Exchange server or computer. At this level of recovery, it is all or nothing.When you recover entire databases, it overwrites the current content at that locationwith the recovered data. If you do not want to overwrite the current content, you canrecover the databases to an alternate location or server, a recovery storage group(RSG), or a recovery database (RDB). This allows you to use Exchange serveradministration tools to browse mail folders and locate individual messages.

The figure below illustrates a simple recovery of the Exchange databases in a stand-alone Exchange Server 2007, 2010, or 2013 environment.

Figure 13 Recovery in a stand-alone Exchange Server environment

In a stand-alone environment, you can also recover data to an alternate location, suchas a different directory on the same server, or to a different server, such as a backup(non-clustered) Exchange server, as shown in the following figure. This enables you touse NMM to recover content without directly overwriting existing content on theproduction Exchange server databases. This can be useful for migrating an Exchangeserver to a different computer, as shown in the following figure.

Mail Item Recovery

Restoring Exchange data 89

Figure 14 Recovery to an alternate location in a stand-alone Exchange Server environment

Recovering individual mailboxes, mailbox folders, and messages

Retrieving and restoring large backups can use a lot of network, memory, processor,and storage resources. Depending on the topology and architecture a site ororganization uses, the recovery operations might also affect production serverperformance, which can impact mail users.

NMM provides several methods for recovering individual items from within anExchange database, such as individual user mailboxes, mailbox folders, and messages.These methods offer several advantages over full server or database recovery:

l You can recover backup data to an alternate location without overwriting theexisting databases or servers.

l You can browse and select individual items from the recovered data, and thenrecover the items to the individual’s mailbox.

With NMM, you can recover individual items by using one the following methods:

l Granular level recovery: NMM mounts the backup set to a virtual drive, where youcan browse the contents of the backup without actually moving or copying thedata. NMM creates this virtual drive in minutes and does not require significantdisk storage space. You can browse and select the data from this virtual drive, as ifyou were looking at the actual database, down to the message level. Only whenyou send the recovery request to the NMM server are actual items copied out ofthe backup set to the user’s mailbox. The recovered items are placed in a newRecovered items folder in the user’s mailbox.The user can browse and select the items to keep, just like any other folder in theirmailbox. Using GLR saves you the time and space needed to browse the actual

Mail Item Recovery


database, and saves you time and resources by only retrieving the items that youselect, not entire databases.

l Recover to RDB or RSG: You can also recover databases to an RDB or RSG, andthen browse those databases to select mailboxes, user folders, or messages forrecovery. When you restore to an RDB or RSG, you can browse the databaseoffline, on a separate server, or from in a folder location that is separate from youronline production Exchange server. While this method allows you to browse andretrieve items without overwriting your live Exchange databases or user mailbox,recovery to a RDB or RSG does require disk space, network resources, andprocessor resources to stage the databases in the RDB or RSG. When you recoverto an RDB or RSG, it takes time to copy gigabytes or terabytes of data from onelocation to another. NMM recovers the backup to the RDB or RSG, and then youcan browse and retrieve individual items.

Compare the following figures, which illustrate:

l Recover using NMM Granular Level Recovery.

l Recover to an RSG/RDB, and recover data from the RSG/RDB to a user mailbox.

Mail Item Recovery

Recovering individual mailboxes, mailbox folders, and messages 91

Figure 15 Recover using NMM granular level recovery

Mail Item Recovery


Figure 16 Recover to an RSG/RDB, and then recover data from the RSG/RDB to a user mailbox

Mail Item Recovery

Recovering individual mailboxes, mailbox folders, and messages 93

NOTICE

An RDB or RSG can only be used for recovering mailbox database data. It cannot beused to recover public folders.

Exchange recovery prerequisitesThis topic describes the required prerequisites for a recovery of Exchange data usingNMM.

The following requirements must be met before you can recover Exchange Server2007, Exchange Server 2010, or Exchange Server 2013 data:

l For each Exchange database to be recovered, you must select the Exchangecheck box titled “This database can be overwritten by a restore” in the ExchangeManagement Console.This is a Microsoft requirement. In PowerShell, the flag is called AllowFileRestoreand must be set to true. The Microsoft Exchange documentation provides moreinformation about this checkbox.

l If you are recovering Exchange data that was backed up from a legacy NetWorkerclient by using the save set VSS USER DATA:\ in an NMM File System RecoverySession:

1. While performing recovery by using the NMM client, Exchange databases areautomatically dismounted.

2. After a successful recovery, the Exchange databases are mountedautomatically.

l Exchange does not support restoring a public folder database to RSGs or RDBs.

l To perform an Exchange database recovery as a non-administrative user, open theNMM user interface using Run as administrator.

l During recovery, when recovering mailbox items to a production database, ensurethat the user mailbox is not full. If the allowed mailbox space is exceeded, then theitem level recovery fails.

l When you overwrite an existing databases with the recovery, perform a full levelbackup after every recovery performed in Exchange Server 2010 and ExchangeServer2013. This does not apply to RSG, RDB or granular restores.

Additional requirements for browsing mailboxes

The following topic describes the requirements for browsing Exchange RSG and RDBmailboxes.

l Databases must be online. NMM does not display mailboxes in offline databases.

l The MAPI/CDO kit must be installed.

l Exchange System Attendant and Information Store services must be running.

l The logged in user must have a configured mailbox with at least one mail sent orreceived.

l The user defined to be logged in for the Replication Manager Interface forExchange service must be a member of the Organization Management Exchangesecurity group.

l You must have backed up the writer set, database or storage group save set:

Mail Item Recovery








Additional requirements for recovering databases in a DAGThe following topic provides requirement details for recovering an Exchange DAGdatabase.

For Exchange Server 2010 and 2013 DAG recovery, ensure that the database recoverynode and state are correct. You must perform the recovery to the DAG member serveron an active node. The restored databases must be in active state. Passive copies ofthe databases must be in Exchange replication suspended state. If the copies are notin suspended state, then you must manually suspend passive copies before a recoveryis performed.

You can suspend replication in three ways:

l By using the Exchange Shell command and calling Suspend-MailboxDatabaseCopycmdlet

l For Exchange Server 2010, through the Exchange Management Console usingSuspend Database Copy

l For Exchange Server 2013, through the Exchange Admin Center using Suspend

Resume the passive database copies after the restore. The Microsoft documentationprovides details.

Configuring Exchange Server recoveryThis section provides the required procedures for configuring an Exchange Serverrecovery.

Specifying Exchange recovery optionsProcedure

1. Open the NMM client user interface.

2. Select the NetWorker Server on which the NMM client software wasconfigured for backup.

3. If the NMM client is part of a cluster, select the virtual client to which you arerecovering data. You can select the virtual client from the client list attribute inthe application toolbar.

4. From the left pane, select Exchange Recover Session, and then select one ofthe following:

Mail Item Recovery

Additional requirements for recovering databases in a DAG 95

l Database Recover (default) to view Exchange database backups.

l RSG Mailbox Recover to browse and recover Exchange 2007 items fromexisting RSG databases.

l RDB Mailbox Recover to browse and recover Exchange 2010 and 2013items from existing RDB databases.

l Granular Level Recover to browse and recover items from databaseswithout first having to restore the database to an RSG or RDB.

5. In the Exchange Server Session toolbar, click Recover Options.

6. Select the type of recovery to perform:

l To recover data for Exchange Server and retain all existing Exchangetransactions that occurred after the time of backup, select Include existinglogs (Roll forward recovery).

l To recover data for Exchange Server up to the time of backup only and tonot include subsequent transactions, select Include logs only from thisrestore (Point-in-time recovery).

For Exchange Server 2007, you must perform a point-in-time recovery atthe storage group level and not at a single database level.

After performing a point-in-time recovery, roll-forward recovery cannot beperformed because the point-in-time recovery replaces the logs that weregenerated after the backup.

l To mount the database after the restore, select Put database online afterrestore.

l To recover the database and transaction logs from the backup withoutattempting to replay the transaction logs, select Do not replay thetransaction logs. The database also cannot be mounted after the restore. Ifyou select this option, you must manually replay the transaction logs byrunning the Exchange utility eseutil.exe.

l To specify the number of retries when attempting to mount the database,select a number from the Number of attempts to try before failing onmount dropdown list.

7. Click OK to close the Exchange Recover Options dialog box.

8. From the navigation tree, expand the folder Microsoft Exchange 2007,Microsoft Exchange 2010, or Microsoft Exchange 2013.

9. Select the Exchange storage groups and databases that are to be recovered.

10. From the Exchange Recover Session toolbar, click Recover.

Configuring roll-forward recovery of an Exchange Server 2010 or ExchangeServer 2013 server in a DAG environment

NOTICE

Perform the recovery from the node where the recovered database is currently active.

Procedure

1. To identify the Exchange database that must be recovered:

l Use the Exchange Management Console (EMC), the or ExchangeAdministrative Console (EAC), or a shell script to determine the DAGmember where the active copy of the database to log on to the Exchange

Mail Item Recovery


member that is running the active copy of the database that is to berecovered.

The topic Additional requirements for recovering databases in a DAG providesadditional details.

2. In the Exchange Management Console or Exchange Administrative Consoleapplication, select the This database can be overwritten by a restorecheckbox.

3. In the Exchange Management shell, stop replication of any passive copies of thedatabase with the suspend-MailboxDatabaseCopy command.

The topic Additional requirements for recovering databases in a DAG providesadditional details.

For example:

Suspend-MailboxDatabaseCopy -Identity "bv-e15svr1\First Database"

4. Open the NMM client.


6. On the main toolbar, select the Client drop-down menu, and then select theclient that is the Exchange DAG.

7. From the left pane, select Exchange Recover, and then select DatabaseRecover (default) — To view Exchange database backups.

8. Click View and then click Refresh.

9. From the navigation tree, expand theMicrosoft Exchange 2010 or theMicrosoft Exchange 2013 folder.

10. Select the Exchange Server items that you want to restore.

You can select more than one database for recovery. You can select backups ofactive or passive databases for recovery.


The Exchange Recovery Options Summary dialog box appears.

12. Review the options:

l If you need to change the options, click Recover Options. This opens theExchange Recover Options dialog box, where you can change settings onthe General, NetWorker, Security, and Exchange tabs.

l If the summary does not show that it is a Roll-forward recovery, then clickRecover Options, go to the Exchange tab, and in the Transaction Log FileReplay dialog, verify that Include existing logs (Roll-forward recovery) isselected. This is the default setting, but it might have been changed if theprevious recovery was a point-in-time recovery.

l If the options are okay, click the Start Recover button. This closes theExchange Recover Options dialog box and starts the recovery.

13. Click Restore.

14. After the restore operation completes, restore replication between the nodeswith the resume-MailboxDatabaseCopy command.

For example:

resume-MailboxDatabaseCopy -Identity "bv-hood-e15svr1\First Database"

Mail Item Recovery

Configuring roll-forward recovery of an Exchange Server 2010 or Exchange Server 2013 server in a DAG environment 97

NOTICE

Perform a full backup after performing a roll-forward recovery.

Configuring roll-forward recovery in an Exchange Server 2007 CCRenvironment

NOTICE

Perform the recovery from the active node.

Procedure

1. In the Exchange Management Console application, select the This databasecan be overwritten by a restore checkbox.

2. In the Exchange Management shell, stop replication to the passive node withthe suspend-StorageGroupCopy command.

For example:

Suspend-StorageGroupCopy -Identity "bv-hood-cluse12\First StorageGroup"


4. In the main toolbar, select the Client menu, and then select the client that isthe Exchange virtual server.

5. From the left pane, select Exchange Recover, and then select DatabaseRecover (default), to view Exchange database backups.

6. From the navigation tree, expand the Microsoft Exchange 2007 folder.




9. Review the options:

l If you need to change the options, click Recover Options. This opens theNetWorker Recovery Options dialog box, where you can change settingson the General, NetWorker, Security, and Exchange tabs.

l If the summary does not show that it is a Roll-forward recovery, clickRecover Options, go to the Exchange tab, and then in Transaction LogFile Replay dialog, ensure that Include existing logs (Roll-forwardrecovery) is selected. This is the default setting, but it might have beenchanged if the previous recovery was a point-in-time recovery.

l If the options are okay, click the Start Recover button. This closes theExchange Recovery Options dialog box and starts the recovery.

10. In Transaction Log File Replay dialog, ensure that Include existing logs (Roll-forward recovery) is selected. This is the default setting, but it might havebeen changed if the previous recovery was a point-in-time recovery.

11. Click Start Recover.

12. After recovery completes, restore replication between the nodes with theresume-StorageGroupCopy command.

For example:

Mail Item Recovery


resume-StorageGroupCopy -Identity"bv-hood-cluse12\First StorageGroup”

NOTICE

Perform a full backup after performing roll-forward recovery.

Configuring for point-in-time recovery in an Exchange Server 2007 CCRenvironment

NOTICE

Perform the recovery from the active node, failing over the passive node to the activenode if necessary.

Procedure

1. In the Exchange Management Console application, select the This databasecan be overwritten by a restore checkbox.

2. In the Exchange command shell, stop replication to the passive node with thesuspend-StorageGroupCopy command.

For example:

suspend-StorageGroupCopy -Identity"bv-hood-cluse12\First StorageGroup"


4. In the main toolbar, select the Client menu and select the client that is theExchange virtual server.

5. From the left pane, select Exchange Recover, and then select DatabaseRecover (default) to view Exchange database backups.

6. From the navigation tree, expand the Microsoft Exchange 2007 folder.




9. Click Recover Options, select the Exchange tab, select Include only logsfrom this restore (Point-in-time recovery).

10. From the Exchange Recover Session toolbar, click Start Restore.

11. After restore, on the passive node manually delete the log files and databasefile.

12. On the passive node, in the Exchange command shell, re-seed the passive nodewith the Update-StorageGroupCopy command.

For example:

Update-StorageGroupCopy -Identity "bv-hood-cluse12\First StorageGroup"

Mail Item Recovery

Configuring for point-in-time recovery in an Exchange Server 2007 CCR environment 99

Recovery procedures

The following topics describe the procedures on methods to perform a recovery usingNMM.

Recovering NetWorker Module for Microsoft Exchange backups

NetWorker Module for Microsoft Exchange (NME) and NMM can not be installed onthe same client. NME and NMM use some of the same binaries for item level browsingand recovery, so running both NME and NMM on the same client causes versioningconflicts for the common binaries.

To recover NME data after migrating from NME to NMM, perform the following steps:

Procedure

1. Uninstall NMM, leaving the NetWorker client software running.

2. Install NME.

3. Recover the NME data.

4. Uninstall NME.

5. Re-install NMM.

Mounting the database after recovery

Certain Exchange pre- and post-restore operations enable quick access to email afterrecovery. Until you remount Exchange databases, email is not available for users tobrowse and verify. NMM provides options to automatically mount Exchange databasesafter restore.

The Exchange administrator can decide if a restore of a particular Exchange databaseis required and if an automatic mounting of the database must be done after therestore is complete:

l If this option is specified, then the database is mounted after the successfulrestore of the Exchange Server.

l If this option is disabled, then the administrator must manually mount thedatabase. By default, this option is enabled in NMM.

The NetWorker Module for Microsoft Administration Guide describes how to select ordisable the automatic mounting option.

Performing Exchange 2007 recovery

This section provides the procedures for recovery to storage groups, depending onthe restore location.

Performing a recovery to the original storage group

By default, recovery to the original storage group overwrites all of the current contentof the selected databases in the storage group.

Procedure


Mail Item Recovery




4. From the left pane, select Exchange Recover, and then select DatabaseRecover.

5. In the navigation tree, expand the Exchange Server that you want to recoverfrom. NMM displays the contents of the storage groups that have been backedup.

6. Select the storage group you would like to recover.

7. Click Recover from the Exchange Recover Session menu.

Results

After the restore, the administrator might need to mount the databases if the optionto put databases online was not automatically selected.

Performing a recovery to an Exchange RSG

NMM does not back up the contents of an RSG. The RSG is used only as a location forrestoring backups from normal storage groups.

Creating an RSG and adding target databases

Before NMM can restore to an RSG, an RSG must be created and linked to a storagegroup. Exchange Server 2007 supports only one RSG per server.

NOTICE

When you use the restore to an RSG feature, always delete the existing RSG and thencreate a new RSG. If you are performing a directed recovery, delete the existing RSGon the original server and the RSG on the destination server.

The following methods are available within Exchange to configure an RSG database:

l Use the Exchange Management Console Database Recovery Management tool forone storage group mailbox.

l Use the Exchange Management Shell for more than one storage group mailbox.

To configure an RSG with Exchange Management Shell:

Procedure

1. On the Exchange Server, select the Start menu and then select ExchangeManagement Shell.

2. Use the new-storagegroup command to create the Recovery StorageGroup:

new-storagegroup –server exch_server –name rsg_name –LogFolderPathrsg_path –SystemFolderPathrsg_path –Recoverywhere:

l exch_server is the Exchange 2007 server name.

l rsg_name is the RSG name that you want to create.

Mail Item Recovery

Performing Exchange 2007 recovery 101

l rsg_path is the path to the RSG directory.

The –Recovery option is also required to specify that an RSG is created.

For example:

new-storagegroup –server bv-rmx64-1 –name SG2_RSG –LogFolderPath T:\exchsrvr\SG2\SG2_RSG –SystemFolderPathT:\exchsrvr\SG2\SG2_RSG –Recovery

3. Use the new-mailboxdatabase command to add target databases to theRSG:

new-mailboxdatabase -Name db_name -MailboxDatabaseToRecoverdb_name -StorageGroup exch_server\rsg_name -EdbFilePathrsg_edb_path

where:

l db_name is the name of the database that to be recovered.

l -EdbFilePath is the path of the database in the RSG, not the original storagegroup.

l edb_path is the path to the database file in the RSG directory.

4. Use the same name for the RSG database as the original database to avoidconfusion.

For example:

new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1 -StorageGroup bv-rmx64-1\SG2_RSG -EdbFilePath U:\exchsrvr\SG2\SG2_RSG\DB1.edb

5. Repeat the new-mailboxdatabase command for each database that isrecovered.

You must specify the correct database name and edb path.

6. NMM allows the administrator to leave the database offline or have itautomatically put online after the restore:

l If you choose to leave the database offline after the restore, you mustmanually mount it. You can do this with the mount-database command:

mount-database –Identity exch_server\sg_name\db_nameFor example:

mount-database –Identity bv-rmx64-1\SG2_RSG\DB1l You can dismount databases with the dismount-database command:

dismount-database –Identity exch_server\sg_name\db_nameFor example:

dismount-database –Identity bv-rmx64-1\SG2_RSG\DB17. To repeat an RSG restore by using the same database after you have mounted

it, set the database can be overwritten property:

set-mailboxdatabase –Identity “exch_server\rsg_name\db_name” –AllowFileRestore:$trueFor example:

Mail Item Recovery


set-mailboxdatabase –Identity “bv-rmx64-1\RSG\DB1” –AllowFileRestore:$true

Recovering to the RSG

When an RSG has been created and linked to a storage group, it is enabled in NMMand can be selected as a restore destination. After databases have been recovered tothe RSG, NMM can perform item level recovery for folders or individual items.

NOTICE

When you use the restore to an RSG feature, always delete the existing RSG and thencreate a new RSG. Right-click the RSG and select Delete RSG.

To recover to an RSG:

Procedure

1. Open the NetWorker user interface.



4. From the left pane, select Recover Session > Exchange Recover, and thenselect Database Recover. This displays the available Exchange databasebackups.

5. In the navigation tree, NMM displays the contents of the storage groups thatare backed up.

The figure below shows that the SG2 storage group has been selected. TheFirst storage group and Public_SG are unavailable and cannot be selected. Thisprevents simultaneous restore of one storage group to the RSG and anotherstorage group to the original location.

Figure 17 Selecting an Exchange storage group

6. Select the storage group that you want to restore.

Mail Item Recovery


7. Click Advanced Restore on Exchange Recover Session menu.

8. Select the Restore To menu item, and then select RSG Configuration.

This verifies that all RSG databases exist and can be overwritten. It checks alldatabases, in case the administrator marks the entire storage group.

If an error message appears, there is a configuration problem. You must fix theproblem before you can restore the database with the configuration problem.Then the RSG restore operation can be started.

In the example shown below, DB1 and DB2 could be restored, but DB3 cannotuntil the configuration problem is fixed.

Figure 18 Recovery storage group configuration error

If no RSG currently exists, a message appears stating that "The RecoveryStorage Group does not exist. Would you like to create a new Recovery StorageGroup?"

If you click yes, you are presented with the Create Exchange 2007 RecoveryStorage Group dialog which allows you to specify the parameters to create anRSG.

9. Select the storage group linked to the RSG that you want to recover. You canalso select individual mailbox databases in that storage group. Only one storagegroup can be selected when Restore to RSG is enabled.

Note

RSG configuration is checked when a restore is started, but only markeddatabases are checked. If NMM detects a configuration problem, NMM stopsthe restore operation.

10. Click Start Recover. When Restore to RSG is enabled, public folder databasescannot be selected because Exchange Server 2007 does not support restoring apublic folder to the RSG.

11. After the restore, the administrator might need to mount the databases if theoption to put databases online was automatically selected.

Setting a different Exchange server for recovery

NMM supports restoring to an RSG in a cluster environment. When you set up anExchange cluster, and there are multiple active Exchange Servers, you can select theRSG that you want to use for an Exchange recover session.

Procedure



Mail Item Recovery


3. On the browse tab, right-click the Exchange Server, and then click ChangeExchange Server.

If the Exchange Server is a stand-alone installation, this menu item isunavailable.

4. In Available Exchange Servers, click the server that you want to browse, andthen click OK. NMM displays the browse tree with the RSG that is associatedwith the selected Exchange Server.

Setting Exchange Server 2007 permissions to enable NMM browsing of RSG mailboxes

An Exchange administrator must configure Exchange Server 2007 to enable browsingof an RSG mailbox.

An error message dialog box displays stating that NMM is unable to browse mailboxesbecause the required permission is not configured correctly.

This message appears if the following two conditions are met:

l If the Send-As and Receive-As permissions are not correctly configured

l Browsing the RSG is attempted

To configure permissions for browsing an RSG mailbox:

Procedure

1. On the Exchange Server, select Start > All Programs > ExchangeManagement Shell.

2. Enable Send-As and Receive-As permissions.

For example:

get-mailboxserver <Exchange Server name> | Add-AdPermission -user <username> -accessrights ExtendedRight -extendedrightsSend-As, Receive-As, ms-Exch-Store-Adminwhere:

l <Exchange Server name> is the server where the RSG mailbox is located.

l <username> is the name of the account that is granted permissions.

Selecting and recovering items in the RSG database

Once you have recovered the databases to an RSG, you can browse the usermailboxes, folders, and messages in the navigation tree, and then select which itemsto recover to the user mailboxes. You can also search for items in the navigation treethrough the Search tab.

Selecting an item for recovery

You can select items for recovery at the storage group, mailbox, mail folder, and mailmessage level:

l To select items for recovery, select the checkbox beside a node in the navigationtree. A check mark indicates that the node is selected.

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

l When you select a node, by default, all items contained in the node such asmailboxes, mail folders, and messages, are selected for recovery. If all items in the

Mail Item Recovery


node are selected, the check mark is green, and the background of the box iswhite.

l To select an item without selecting all items at the same level, expand down to thelevel that you want, without selecting. When you have located the item, select thecheckbox for the item. The containers above that item are automatically partiallyselected.For example, if the mail message “Is everybody online?” is selected for recovery,without selecting all the items in the containing mail folder, user mail box, orstorage group, a gray check mark in a check box with a gray background appears.This indicates that the item is partially selected. When “Is everybody online?” isselected, the nodes above it are partially selected all the way up to the server.

The following figure depicts one selected mail message and several partially selectednodes in the navigation tree.

Figure 19 Selecting mail messages and nodes

Recovering selected items

Once you have completed selecting items through browsing or searching, you canrecover the items to the user’s mailboxes.

To recover the selected items, from the Exchange Recover Session toolbar, click StartRecovery.

When NMM performs an RSG item level recovery, NMM places the items in a new“Recovered Items” folder created in the user’s mailbox on the production server.Because NMM places them in separate folders in the user's mailbox, recovered itemsdo not overwrite existing items.

The name of the folder begins with a time and date stamp. An example is 14:35:173/13/2009 Recovered Items. NMM creates a new Recovered Items folder foreach recovery. This prevents the selected items from overwriting the existing items inthe mailbox, and allows you to view and work with existing and recovered itemswithout overwriting either. When you complete sorting through the recovered items,you should delete the Recovered Items folder.

Mail Item Recovery


Recovering to an alternate storage group

Recovery to an alternate storage group allows you to recover the storage group datato a different Exchange Server from the original source. Before NMM can restore toan alternate storage group, you must create a new database in the alternate storagegroup with the same name as the original database.

Creating an alternate storage group and adding target databases

There are three methods available within Exchange to configure an alternate storagelocation database:

l Exchange Management Shell at the command line, which is the recommendedmethod

l Exchange Management Console Database Recovery Management tool

l By using the Select Storage Group Restore Destination dialog box in the NMMuser interface when performing a recovery to an alternate storage group.

Configuring an alternate storage group with Exchange ManagementShell

Procedure

1. On the Microsoft Exchange Server, select the Start menu.

2. Select Exchange Management Shell.

3. Use the new-storagegroup command to create the alternate storage group:

new-storagegroup –server exch_server –name alt_name –LogFolderPath alt_path –SystemFolderPath alt_pathwhere:

l exch_server is the Exchange 2007 server name.

l alt_name is the required alternate storage group name.

l alt_path is the path to the alternate storage group directory.

For example:

new-storagegroup –server bv-rmx64-1 –name Alternate_SG –LogFolderPath T:\exchsrvr\SG2\Alternate_SG –SystemFolderPathT:\exchsrvr\SG2\Alternate_SG

4. Use the new-mailboxdatabase command to add target databases to thealternate storage group:

new-mailboxdatabase -Name db_name -MailboxDatabaseToRecoverdb_name -StorageGroup exch_server\alt_name -EdbFilePath edb_pathwhere:

l db_name is the name of the database that is recovered.

l edb_path is the path to the database file in the alternate storage groupdirectory.

The alternate storage group database name must match exactly the originaldatabase name.

Mail Item Recovery


For example, the name for the alternate storage group specified in new-mailboxdatabase -Name: is DB1, the same as the name of the originaldatabase name specified in MailboxDatabaseToRecover, DB1.

new-mailboxdatabase -Name DB1 -MailboxDatabaseToRecover DB1 -StorageGroup bv-rmx64-1\Alternate_SG -EdbFilePath U:\exchsrvr\SG2\Alterenate_SG\DB1.edb

Note

-EdbFilePath is the path of the database in the alternate storage group, notthe original storage group.

5. Repeat the new-mailboxdatabase command for each database that isrecovered. Ensure to specify the correct database name and edb path.

6. NMM allows the administrator to leave the database offline or have itautomatically put online after the restore:

l If you choose to leave the database offline after the restore, you mustmanually mount the database with the mount-database command:

mount-database –Identity exch_server\sg_name\db_nameFor example:

mount-database –Identity bv-rmx64-1\Alternate_SG\DB1l You can dismount databases with the dismount-database command:

dismount-database –Identity exch_server\sg_name\db_nameFor example:

dismount-database –Identity bv-rmx64-1\Alternate_SG\DB17. To repeat an alternate storage group:

l Restore by using the same database after you have mounted it.

l Set the database can be overwritten property:

set-mailboxdatabase –Identity “exch_server\alt_sg_name\db_name” –AllowFileRestore:$trueFor example:

set-mailboxdatabase –Identity “bv-rmx64-1\Alternate_SG\DB1” –AllowFileRestore:$true

Recovering to an alternate storage group

After the restore, the administrator might need to mount the databases if the optionto put databases online was automatically selected.

Procedure

1. In the Select Storage Group Restore Destination dialog box, select AlternateStorage Group.

2. In the Exchange Server list, select the Exchange Server that contains thealternate storage group.

3. In Select Alternate Storage Group select the storage group, and then clickOK.

4. Click Start Recover.

Mail Item Recovery


Performing Exchange Server 2007 directed recovery

If a problem occurs when recovering to the original Exchange Server host, such asdisk drive failure, you can perform a directed recovery to recover Exchange data to adifferent Exchange Server.

The database portability feature in Microsoft Exchange Server 2007 allows a mailboxto be mounted on any server in the same organization. Microsoft TechNet describesthis feature in more detail.

In the normal NMM backup and recovery process, the backup flows in the followingdirection:

Procedure

1. The NMM client is installed on the computer that is backed up. For example,ExchangeServer1.

2. That NMM client is configured to work with a specific NetWorker server onanother computer. For example, NetWorkerServer1.

3. Backups are configured on and performed by the NetWorker server, NetWorkerServer1.

4. Recovery is performed through the NMM client UI on the NMM clientcomputer, ExchangeServer1, and recovered to the same NMM client computer.

In a directed recovery, the NMM client is also installed on another server, forexample Server2. The recovery of ExchangeServer1 is “directed” from theNMM client on Server2:

5. The NMM client is installed on the computer that is backed up. For example,ExchangeServer1.

6. The NMM client is also installed on another computer that directs the recovery.For example, Server2.

7. The NMM client on both computers are configured to work with the sameNetWorker server on another computer. For example, NetWorkerServer1.

8. Backups are configured on and performed by the NetWorker server, NetWorkerServer1.

9. Recovery of ExchangeServer1 is performed through the NMM client UI onanother NMM client computer, Server2, and recovered to another location.

Performing a directed recovery

Procedure

1. In NetWorker, create a backup of the NMM client, the Exchange Server.

2. Run NMM on the computer that receives the data.

3. Connect to the NetWorker server that hosts the NMM Exchange Server client.

4. Add the NMM Exchange Server client that created the backup as a locallyviewable client.

The figure below shows the default of only one NMM client available, the localclient.

Mail Item Recovery


5. On the Options menu, click Configure Options.

6. Click the Refresh button, which is to the right of the Client name. The clientsavailable on the NetWorker server that you are attached to are listed underAvailable clients on.

Figure 20 Select Viewable Clients dialog

7. Click the client to add in the Available clients on menu, and then click Add.

Add or remove clients as needed.

8. Click OK.

9. In the Client list, select the client that created the Exchange Server backup asthe current local client.

10. If Snapshot Management or Monitor is the active navigation bar item, and youare prompted with the Navigate Away dialog box, click Yes.

11. On the Exchange Recover Sessions toolbar, select Recover Options.

Results

Recover the remote client backup to local the Exchange Server.

Selecting a storage group restore destination

When restoring from a point-in-time backup, NMM copies files from a snapshot to thespecified location. When restoring from a rollover, NMM copies files from aNetWorker device such as tape, file, or adv_file to the specified location.

Mail Item Recovery


The topic Performing Exchange Server 2007 directed recovery provides additionaldetails.

NOTICE

When you use the restore to an RSG feature, always delete the existing RSG and thencreate a new RSG. Right-click the RSG and select Delete RSG.

NMM provides several options for selecting the target storage group. You specifythese options in the Select Storage Group Restore Destination dialog box, whichyou access in the Exchange Recover Session.

The figure below displays the options available in this dialog box.

Figure 21 Select Storage Group Restore Destination dialog

The Select Storage Group Restore Destination dialog box provides the followingsettings and information:

l <Storage Group Name> Storage Group (Source) — This box displays the name ofthe storage group selected in the Browse tab in the Exchange Recover Sessiondialog.

l Restore To (Destination) — This specifies where you want to restore the storagegroup.

l Exchange Server — By default, this is the server or virtual server where thesource storage group is located. You can select a different server here if you arerecovering to an RSG or alternate storage group that is not on the source server.

l Original Storage Group — This specifies to restore the content to the originalstorage group, which overwrites the content currently in that storage group.

l Recovery Storage Group — This specifies to restore the storage group to aseparate RSG that you have already created:

n Recovering to an RSG allows you to browse and select items to restore withoutoverwriting the entire storage group. When this option is selected, the CheckRecovery Storage Group dialog box appears.

n The Check button verifies that the Recovery Storage Group exists anddatabases are configured correctly.

Mail Item Recovery


n Exchange Server 2007 does not support restoring a public folder database tothe RSG. If a storage group contains a public folder database, it cannot beselected. Only the mailboxes within that storage group can be selected.

l Alternate Storage Group — This specifies to restore databases to a differentstorage group. When you select this option, the Select Alternate Storage Groupdialog box provides a menu where you can select from the available storage groupsavailable on the Exchange Server listed in the Restore To dialog box.

Performing Exchange Server 2010 and 2013 recovery

This section provides information on performing a recovery on Exchange Server 2010and 2013.

Performing a full recovery

You can recover the contents of a backed up database to the original database byperforming full recovery.

Procedure


l Database Recover (default) to view Exchange database backups.

l RDB Mailbox Recover to browse and recover Exchange 2010 and 2013items from existing RDB databases.

l Granular Level Recover to browse and recover items from databaseswithout first having to restore the database to an RSG or RDB.

2. If no databases appear, click View > Refresh.

3. Select the database in the NMM user interface.

4. If the database is not listed, select a browse time that includes the desiredbackup. The NetWorker Administration Guide provides details.

5. Select Recover in the taskbar.

NOTICE

Always perform a full backup after performing a point-in-time or roll-forwardrecovery.

Performing an advanced recovery

In NMM, you can click Recover Session > Advanced Recover to recover a databaseto one of the following:

l A selected Recovery Database (RDB) — Exchange Server 2010 Service Pack 1,Rollup 6 or later, and Exchange 2013 support the ability to restore data directly toa RDB. Mounting the recovered data as a RDB allows you to restore individualmailboxes or individual items in a mailbox. Public folders cannot be recovered to anRDB.

l An alternate database mounted on the mailbox server.

l A remote database — In remote database recovery, a selected mailbox database isrestored to a remote mailbox server, in the Exchange DAG where the activedatabase resides. The remote database recovery option is only available forExchange Server DAGs and not for Exchange Server stand-alone.

Mail Item Recovery


Alternate and remote recovery are supported only in the same domain. Cross-domainExchange recovery is not supported. That is, if two hosts are in different domains,alternate or remote recovery cannot be performed.

Performing a DAG database recovery

Procedure

1. Identify the Exchange database that must be recovered.

a. Use the Exchange Management Console (EMC), the or ExchangeAdministrative Console (EAC), or a shell script to determine the DAGmember where the active copy of the database resides.

b. Log on to the Exchange member that is running the active copy of thedatabase that is to be recovered.

c. From the EMC, open the database properties and select the This databasecan be overwritten by a restore checkbox.

2. Suspend all passive copies of the database that are to be recovered.

The topic Additional requirements for recovering databases in a DAG providesdetails.

3. From the left pane, select Exchange Recover Session, and then selectDatabase Recover (default).

4. Select the DAG name for the client on which the NMM client software wasconfigured for backup.


6. Select the DAG database to be recovered.

You can browse and recover individual mailboxes and mailbox items from the liston the right pane.

7. In the Exchange Recover Session toolbar, click the Advanced Recover option.

The Advanced Recovery dialog box appears. The Steps group lists the threesteps for recovery:

l Select Recovery

l Select DB & Server

l Summary

Figure 22 Advanced Recovery dialog

Select Recover Options to skip the steps for Advanced Recovery and performfull recovery of the database listed in Database (Source).

Mail Item Recovery

Performing Exchange Server 2010 and 2013 recovery 113

8. In the Select Recovery Type group, under Recovery Type, select one of thefollowing choices and click Next:

l Recovery Database (RDB) Recovery — Recovering to a recovery database(RDB) provides the remaining steps of the procedure.

l Alternate Database Recovery — Recovering to an alternate databaseprovides the remaining steps of the procedure.

l Remote Database Recovery — Recovering to a remote database providesthe remaining steps of the procedure.

Recovering to a Recovery Database (RDB)

RDB recovery is possible only when Exchange 2010 Service Pack 1, Rollup 6 or later,or Exchange Server 2013 is installed. The following recovery configurations arepossible:

l An RDB can be created and recovered on a DAG member server that has a passivecopy of the database.

l An RDB recovery can be done from any DAG node for any DAG Mailbox databases.

l An RDB recovery can be performed from other mailbox server which is not part ofthe DAG but part of the same Exchange organization.

To browse the Exchange Server Recovery Database (RDB) for mailbox, folder, andmessage recovery, it is no longer necessary to install both the CAS and mailbox roleson the same server.

In a multi-tenant environment, an administrator is created for each tenant. But whenthe user logs in as a domain administrator and performs RDB browsing, there is aconflict in names due to existence of more than one administrator. To work aroundthis issue, create a new user (for example, NMMBackupUser) and add this user asmember of the Organization Management group to each of the tenants.

RDB browsing fails if the user credentials used for the operation have an Alias inActive Directory. In this situation, you must create a user (without an Alias) and installNMM with the credentials of the new user. Provide the necessary permissions and usethe user account for RDB browsing operations.

Performing an RDB recovery

Procedure

1. The Exchange Recovery Summary dialog box appears. This dialog lists theExchange Server Recovery options, the NetWorker Recovery Options andallows you to review the details before proceeding.

Mail Item Recovery


Figure 23 Exchange Recovery Summary dialog

To proceed with recovery, click Start Recovery.

2. In the Advanced Recovery dialog, select Recovery Database (RDB) Recoveryand click Next.

The Manage RDB dialog appears, as shown in the figure below.

Figure 24 Manage RDB dialog

3. To create an RDB, click Create.

The Create RDB dialog box appears.

Figure 25 Create RDB dialog

Mail Item Recovery


4. In the RDB Name field, type a name for the new RDB.

5. In the EBD File Path field, browse and select the file path location for the newRDB.

6. In the Log File Path field, browse and select the location for the log file.

Previously, due to a Microsoft requirement, the Exchange Server 2010 databaselogs path and Mailbox databases that reside on the same volume could not bestored in the same file path location. This restriction has been lifted.

7. Click Create.

The new RDB is created and appears in the Recovery Database (RDB) List.

8. From the Manage RDB dialog, you can also:

l Delete a RDB — Select the RDB from the Recovery Database (RDB) Listand click Delete.

Figure 26 Delete confirmation dialog box

l Unmount a RDB — If a RDB is mounted but you are getting an error duringrecovery, you can unmount the RDB and then re-mount the same or anotherRDB for recovery.

To unmount a RDB, select the RDB from the Recovery Database (RDB)List and click Unmount.

l Mount a RDB — Select an RDB from the Recovery Database (RDB) Listand click Mount.

Note

Only one RDB can be mounted at a time.

Ensure that the RDB is mounted on the current node of the NMM client forsuccessful recovery. If the recovered database is not mounted on thecurrent node or if replication is on, then the recovery fails.

l Overwrite a RDB — Select an RDB from the Recovery Database (RDB) Listand click RDB Overwrite.

The RDB is overwritten by the recovery operation.

Ensure that the RDB is mounted before proceeding to the next step.

9. Select the created RDB and click Next.

Recovering to an alternate database

Alternate database recovery is supported on any Mailbox server. In this type ofrecovery, the backed up Mailbox database is recovered to a new database other thanthe original Mailbox database. Alternate database recovery is supported in bothExchange 2010 and 2013 stand-alone and DAG environments.

Mail Item Recovery


Procedure

1. In the Advanced Recovery dialog, select Alternate Database Recovery forrecovery to an alternate database and click Next.

The Select Database dialog with a list of alternate databases appears, as shownbelow.

Figure 27 Select Database dialog box

2. Select the database which you want to recover to and click Next.

The Exchange Recovery Summary dialog appears. This dialog lists theExchange Server recovery options, the NetWorker recovery options and allowsyou to review the details before proceeding with recovery.

3. To proceed with recovery, click Start Recovery.

Recovering to a remote database

By performing remote recovery, you can start roll-forward or PIT recovery from amailbox server that is not actually mounted. After remote recovery is started fromDAG member server where the Mailbox database is not mounted (the Mailboxdatabase with the passive copy) the recovery service nsrsnap_vss_recover.exe isautomatically started in the DAG member server on the Mailbox database with theactive copy.

Note

Remote database recovery is supported only in an Exchange 2010 or 2013 DAGenvironment. You cannot perform a remote recovery to a host that is not a part ofDAG.

1. In the Advanced Recovery dialog, select Remote Database Recovery forrecovery to an remote database in an Exchange DAG member and click Next.The Select Server dialog appears with a list of remote databases.

Mail Item Recovery


Figure 28 Select Server dialog

2. Select the database to which you want to perform the recovery and click Next.The Exchange Recovery Summary dialog appears. This dialog lists the ExchangeServer recovery options and the NetWorker recovery options and allows you toreview the details before proceeding with recovery.

3. To proceed with recovery, click Start Recovery.

Accessing archive mailboxes in Recovery Databases

Microsoft does not support access to archive mailboxes in the RDB through MAPI. AMAPI_E_FAILONEPROVIDER (0x8004011d) error occurs when a MAPI applicationattempts to log on.

You can work around this by using the Restore-Mailbox cmdlet to restore data fromthe archive mailbox in the Recovery Database. For Exchange Server 2010 andExchange Server 2013, you must use the New-MailboxRestoreRequest cmdlet

Procedure

1. Get the archive mailbox GUID from the get-mailbox cmdlet for the user whosearchive mailbox you want to restore. For example, in PowerShell:

C:\>Get-Mailbox <alias> | Fl Name, Archive*...ArchiveGuid : <GUID>

2. Run the New-MailboxRestoreRequest cmdlet. For example, in PowerShell:

C:\>New-MailboxRestoreRequest -RecoveryDatabase <RecoveryDatabase Name> -RecoveryMailbox <GUID> -TargetFolder<Target Folder Name> -Identity <alias>

Results

This restores the mailbox data back to a live mailbox, where the user can work with it.

The Microsoft TechNet article “Restore-Mailbox” http://technet.microsoft.com/en-us/library/bb125218.aspx provides more information about using this cmdlet.

Recovering a deleted Exchange Server mailbox database or public folderdatabase

NMM supports recovering the following Exchange Server databases outside of theExchange VSS process:

Mail Item Recovery




l Exchange Server 2007, 2010, or 2013 mailbox databases

l Exchange Server 2007 and 2010 public folder databases to the Windows filesystem

This capability allows you to recover mailbox databases that have been removed fromthe Exchange server and the Active Directory. You can also recover these items sothat you can perform data mining for Exchange public folders or public mailboxdatabases with third-party tools.

Procedure

1. For Exchange 2007, verify that the storage group exists.

If the original storage group was deleted, create a new storage group using thesame name.

2. In the NMM user interface, select the NMM client and then use the Recover >Exchange Recover Session > Database Recover option to recover thedeleted database.

If the database is not listed, select a browse time that includes the desiredbackup. The NetWorker Administration Guide provides details.

Although the job summary does not note that the recovery is to a Windows filesystem, as long as the database itself is online, there is no danger of over-writing the live database.

3. Select the mailbox database you want to recover and click Recover Options.

4. Click the Exchange tab and click Select Destination.

5. Select the Restore Deleted Database Files on File System checkbox.

6. Browse to the target location where NMM recovers the mailbox database files.

7. Click OK.

8. To recover deleted Exchange databases, refer to the Microsoft documentation: http://technet.microsoft.com/en-us/library/bb124040(v=EXCHG.65).aspx

9. To perform data mining using third-party tool such as Kroll OntrackPowerControls, refer to the PowerControls for Exchange documentation.

Performing a quick recovery of a deleted mailbox

The procedure to recover a deleted mailbox is performed independent of NMM backupor recovery operations.

In the event that a user mailbox is deleted, you can quickly recover the mailboxthrough the Exchange Management Console.

Procedure

1. In Exchange Management Console, ensure that deleted user mailbox entryappears under Disconnected mailbox under Recipient management.

2. Re-create the user mailbox with same name.

3. Disable the re-created user mailbox.

4. Open the Disconnected mailbox under Recipient management and thenselect the user mailbox which was accidentally deleted.

5. Right-click the user mailbox and then select Connect.

6. Select the User mailbox radio button, and then click Next.

Mail Item Recovery

Performing a quick recovery of a deleted mailbox 119

http://technet.microsoft.com/en-us/library/bb124040(v=EXCHG.65).aspx

7. Select Matching user > User mailbox, and then click Next.

The deleted user mailbox is then re-created under Recipient management >Mailbox.

NOTICE

Recreated deleted mailboxes are not always immediately visible. It might takefrom 15 minutes to an hour before the mailbox is visible and accessible throughOutlook.

Recovering Exchange Server mailbox, public folder, or public folder mailboxdatabase files

You can use NMM and third-party software, such as Ontrack PowerControls, toperform a granular recovery of Exchange Server mailbox, public folder, or public folderdatabases or mailbox database items. NMM supports recovery for Exchange Server2007, 2010, and 2013.

Procedure

1. Use NMM to back up the database.

2. Use NMM to perform a flat file recovery of the database by performing one ofthe following procedures:

l To recover files from a network location: Recovering Exchange Servermailbox, public folder, or public mailbox databases from a network location. .

l To recover files to a remote computer: Recovering Exchange Servermailbox, public folder or public mailbox databases to a remote computer. .

3. Use third-party software, such as Ontrack PowerControls, to perform agranular recovery of the Exchange flat files.

The third-party tool documentation provides information about Exchange flatfiles.

Results

The procedure varies depending on the method you use.

The recovery process is the same for all supported versions of Exchange Server,although the backup save sets and application information vary depending on theversion Exchange Server you use.

Recovering Exchange Server mailbox, public folder, or public mailbox databases from a networklocation

With a third-party tool, such as Ontrack PowerControls, you can use the files in thesefolders to perform an item-level recovery to a target user mailbox that is inproduction.

Procedure

1. Log onto the DAG node client where you performed the backup.

2. In the NMM user interface, start a recovery session.

3. On the main toolbar, select the Client drop-down menu, and then select theDAG client where you performed the backup.

Mail Item Recovery


4. Click View and then click Refresh.

5. Click Recover > Exchange 2010 Recover Session > Database Recover.

The NMM user interface shows the mailbox databases that are available forrecovery.


7. Click the Exchange tab.



10. Click OK.

11. Start the flat file recovery of the database by selecting the mailbox, publicfolder, or public folder mailbox database you want to recover.

12. From the Exchange Recover toolbar, click Recover.

13. After the flat file recovery completes, verify that the logs and .edb filesrecovered as expected in the mapped network drive.

Recovering Exchange Server mailbox, public folder, or public mailbox databases to a remotecomputer

To recover the Exchange Server mailbox, public folder, or public folder mailboxdatabase flat file to a remote computer, you must map a network drive and specifythat network drive path as the value for a new registry entry namedExchangeDataFilePath.

With a third-party tool, such as Ontrack PowerControls, you can use the files in thesefolders to perform item-level recovery to a target user mailbox that is in production.

Procedure

1. On the remote computer that you’ll recover the database to, create a folder.

For example: E:\folder.

2. On the DAG node where you performed the backup, map a network drive to thefolder you created on the remote computer. For example, Z:\ is a mappednetwork drive on the DAG node, and Z:\ points to E:\folder on the remotecomputer.

3. On the remote computer, open the NMM client user interface.

4. On the main toolbar, click Options > Configure Options.

5. In the Configuration Options dialog, next to the Client name field, click theRefresh button.

6. In the Select Viewable Clients dialog, click the client where you performed thebackup and then click Add.

7. Click OK.

8. On the main toolbar, select the Client drop-down menu, and then select theDAG client where you performed the backup.

9. Click Recover > Exchange 2010 Recover Session > Database Recover.

The NMM user interface shows the mailbox databases that are available forrecovery.


Mail Item Recovery

Recovering Exchange Server mailbox, public folder, or public folder mailbox database files 121

11. Click the Exchange tab.



14. Click OK.

15. After the flat file recovery completes, verify that NMM recovered the logsand .edb files to the folder you created.

Best practices and recommendations

Review the following best practices for Exchange backup and recovery.

l If you are using Exchange Server 2007, you can reduce backup time by spreadingdata across different storage groups. For example, it takes longer to back up asingle storage group or database with 200 GB of data, than it does to back up 200GB of data spread across 10 different storage groups or databases.

l In addition to your scheduled full backups, you should also perform a full backup ofExchange Server after:

n Every successful recovery.

n Upgrading to NMM from previous releases of NetWorker clients.

n Upgrading to a new Exchange version or Service Pack.

n You change the database directory path or the Log Path or System Path.

l Ensure that you have mounted all databases before backing up the ExchangeServers. Unmounted databases are not backed up.

l For Exchange Server 2007, ensure that database (mailbox and public folder) filesand transaction log files reside on separate volumes for backup, otherwise thebackup fails. Also, ensure that the volume drive letter of the databases files isdifferent from the volume drive letter of the transaction log files.

l If you delete Exchange objects like storage groups and databases in ExchangeServer 2007 or databases in Exchange Server 2010 or 2013, you cannot recoverthese objects until you perform disaster recovery. Objects from the ExchangeServer should not be deleted unless they no longer need to be recovered.

l After upgrading to the NMM client from the NetWorker Module for Exchange(NME), you cannot recover Exchange backups that were performed with NME. Toensure that you can recover all Exchange data to the point-in-time of the upgrade,perform a full backup of Exchange data immediately after upgrading to the NMMclient.

l Save sets and backup groups that include the Exchange writer cannot include anyother volumes, applications, or non-Exchange items in the save set.

Exchange recovery limitations

Review the following limitations when backing up and restoring Exchange objects withNMM.

l For Exchange Server 2007, you cannot restore a single mailbox database in astorage group containing multiple databases using point-in-time recovery — Asingle mailbox database cannot be restored by using point-in-time recovery ofExchange, because it requires both logs and databases to be selected for restore:

Mail Item Recovery


VSS-marking semantics do not allow selecting logs for backup or restore.

Logs are included only when you select a storage group for backup or restore.

Logs are not included when you select a database.

l Roll-forward recovery is not possible after point-in-time restore — After youcomplete a successful point-in-time restore, perform a full backup of theExchange Server so that you can perform roll-forward recovers.

l There is no support for RSG configuration where the RSG system path restorelocation and RSG logs restore location are different. Although Microsoft ExchangeServer supports an RSG configuration where the RSG system path restorelocation and RSG logs restore location are different, NMM currently does notsupport that configuration. The location for the RSG system path and the RSG logpath must be the same.

l There are MAPI memory errors when recovering mailbox items from RSGdatabases. There is a known memory error that might occur with MicrosoftExchange MAPI when recovering mailbox items from RSG databases. The errorMAPI_E_NOT_ENOUGH_MEMORY might be reported in the NMM logs. Whenthis error occurs, NMM recovers the mailbox item, but might lose properties suchas the original font and formatting.This is a known problem, but Microsoft has no workaround or fix for this issue atthis time.

Mail Item Recovery

Exchange recovery limitations 123

Mail Item Recovery


CHAPTER 5

Granular Level Recovery


l Recovering Mailbox items with Granular Level Recovery (GLR)....................... 126

Granular Level Recovery 125

Recovering Mailbox items with Granular Level Recovery(GLR)

In a conventional Exchange database restore, entire databases are replaced orrestored. Retrieving large backups and restoring them can use significant network,memory, processor, and storage resources and might also affect production serverperformance.

NMM supports Granular Level Recovery (GLR) so that you can restore individualitems from within an Exchange database, such as individual user mailboxes, mailboxfolders, and messages. Individual folders can be browsed and selected from therestored data, and then restored to the individual’s mailbox.

NMM mounts the backup set to a virtual drive, where you can browse the contents ofthe backup without actually moving or copying the data. During the mount process,NMM copies required log files from the server. The virtual drive is created quickly anddoes not require any significant amount of disk storage space. You can browse andselect the recovered data from this virtual drive as if you were looking at an actualrecovery database, down to the folder level.

Only when you send the restore request are actual items copied out of the backup setto the user’s mailbox. The items are placed in a folder in the user’s mailbox calledRestored Items, where the user can browse and select the items to keep - just like anyother folder in their mailbox. Using GLR saves you the time and resources needed tobrowse the actual database and retrieves only the items you selected.

You can restore to an Exchange Server RDB or RSG without disrupting the activeproduction databases and servers. After you restore to the RDB or RSG, you canbrowse and select individual mailboxes to restore to the production server while it isonline.

After a successful GLR, until you perform another GLR or a different type of a restoreoperation, the GLR RDB or RSG remains mounted and maintains a Read connectionwith the original device. You must delete the GLR RDB or RSG before you can performa Stage operation. Closing the NMM GUI should remove the GLR RDB.

The NetWorker Module for Microsoft Administration Guide provides more informationabout GLR.

GLR considerations

The following requirements must be met to recover granular Exchange data throughGLR.

l One of the following be must installed on the NetWorker server:

n NetWorker 7.6.5.1 or higher



n NetWorker 8.1.0 or higher

n NetWorker 8.1. SP1 or higher

l You must have backed up the writer set or the database or storage group save setwith a GLR-compatible version of NMM 3.0 or later:

n For Exchange Server 2007 writer:









The NetWorker Module for Microsoft Administration Guide provides moreinformation about backups.

l The backup must be a full backup. Incremental backups are incompatible withExchange GLR.

l Public folders or objects cannot be recovered using GLR. For this reason, they arenot displayed in the list of folders available for GLR.The GLR can be performed on backups residing on GLR-compatible devices, suchas AFTD or Data Domain devices.

l When browsing folders with more than 10,000 items, NMM might take asignificant amount of time to display these items. In this case, do one of thefollowing:

n Restore the entire folder using Exchange GLR without browsing into it.

n Restore the database to the RDB and then browse from there.

l In firewall-enabled environments, you must provide firewall exceptions for theWindows Remote Management services:

1. Click Start, point to Administrative Tools, click Windows Firewall withAdvanced Security, and then click Inbound Rules.

2. On the Inbound Rules dialog, right-click Windows Remote Management -Compatibility Mode (HTTP-In) and then click Disable Rule.

3. Right-click Windows Remote Management (HTTP-In) and then click DisableRule.

Recovering individual mailbox items using Granular Level Recovery (GLR)

The items are placed in a new Restored Items folder in the user’s mailbox.

You can mount only one virtual drive at a time and browse one RDB or RSG at a time.To recover a different version of the selected database, repeat step 5 through step 11on page 106. Changing to a different version dismounts the currently mounted virtualdrive. NMM creates a new virtual drive with data from the newly selected database.

Procedure


2. In the host menu, select the NetWorker client on which the NMM clientsoftware was configured for backup.

3. If the NMM client is part of a cluster or DAG, select the virtual client name ofthe cluster or DAG to which you are recovering data. You can select the virtualclient from the client list attribute in the application toolbar.


Recovering individual mailbox items using Granular Level Recovery (GLR) 127

4. From the left pane, select Recover, select Exchange Recover Session, andthen select Granular Recover.

5. If you want to recover items to a PST file, select the location and name of thePST file in the Exchange Recover Options dialog.

Due to a Microsoft restriction, NMM does not support PST recovery for a singlemail item.

If no PST file is specified, then the items selected for recovery are recovered tothe production server.

Once a recover to the PST file has completed, the field containing the locationand name of the PST file is cleared.

6. Select the mailbox database to recover.

Figure 29 Individual mailbox databases

Only full backups are compatible with GLR.

7. In the Exchange Server Session toolbar, click Recover.

l If the backup is GLR-compatible, the recovery proceeds.

l If the backup is not GLR-compatible, you are prompted to select a version ofthe save set that is GLR-compatible. To select a GLR-compatible save set:

a. Click Yes.

b. Select a backup from the list of backups.

c. Check the Use selected item backup time as new browse timecheckbox and then click OK.NMM creates an RDB (for Exchange Server 2010 and 2013) or RSG (forExchange Server 2007) and performs the recovery.

8. In the Exchange Recovery Summary dialog box, click Start Recover.

9. Click OK to clear the Recovered RDB Mailbox Items dialog box.

10. Expand the database to find user mailboxes and folders.

Stop here if you want to restore items to an alternate mailbox, and follow theinstructions in the topic Performing a GLR to an alternate mailbox.

For example, if you want to restore items from Steve’s mailbox to John’smailbox.



Figure 30 Sample mailbox

11. Click Recover and then Start Recover to recover the selected folders.

Performing a GLR to an alternate mailbox

You can recover of individual mailbox items, including folders, from any number ofactive users to any other active user in the Exchange organization. Recovery is notsupported for deleted users.

NOTICE

Folder names containing / and \ are not recovered.

When you recover to an alternate mailbox, NMM creates a Recovered Items folderunder the root of the alternate mailbox. Inside this Recovered Items folder, NMMcreates sub folders that contain the contents of each user’s recovered mailbox items.

For example, you want to recover some of UserYY and UserZZ’s mail items to UserA’smailbox. NMM creates a folder in UserA’s mailbox called Recovered Items YYYY-MM-DD hh:mm:ss, where YYYY-MM-DDD hh:mm:ss indicate the date and time of therecovery. Inside that folder, NMM creates sub-folders for each user, for exampleUserYY and UserZZ, and recreates each user’s respective folder structure and mailitems.

Procedure

1. Follow the steps in the procedure Performing a directed recovery up tomounting the backup to a virtual drive.

NOTICE

Do not click Recover in the last step.

2. In the Advanced Recovery dialog, select Alternate Mailbox User.

3. Select the user account for the mailbox.

l To search for a specific user:

a. In the Name dialog bog, type a name.

b. Click Search.

c. Confirm the user.


Performing a GLR to an alternate mailbox 129

l To list all users in the Exchange organization:

a. Click List All Users.

b. Select the user from the list that appears.

4. Click Next.

The recovery starts.

Performing a GLR on an archive user mailbox

The NMM software does not support the Exchange Server 2010 and 2013 archivemailbox feature. To perform an item level recovery of an archive user mailbox, use theNew-MailboxRestoreRequest cmdlet to recover personal PST information from anRDB, which is recovered by NMM.

Procedure

1. Create an archive mailbox with a folder, and add a few emails in to the folder.

2. Back up the mailbox database that contains the archive mailbox.

3. Perform RDB recovery.

4. Run the following command to retrieve the ArchiveGuid for the archivemailbox using Exchange Management Shell.

[>] C:\Windows\system32>get-mailbox arch2 | Fl Name, Archive*Name : arch2ArchiveDatabase : ArchiveDB2ArchiveGuid : 3daa752d-a77c-47b7-ad6e-5a2aa6ee2579ArchiveName : {Personal Archive - arch2}ArchiveQuota : 50 GB (53,687,091,200 bytes)ArchiveWarningQuota : 45 GB (48,318,382,080 bytes)ArchiveDomain :ArchiveStatus : None

5. Run the following cmdlet to recover Archive PST information using ExchangeManagement Shell.

[>] C:\Windows\system32>New-MailboxRestoreRequest -RecoveryDatabase RDB-arch -RecoveryMailbox 3daa752d-a77c-47b7-ad6e-5a2aa6ee2579 -TargetFolder arch-folder -Identity arch2

6. Confirm that you want to perform the recovery.

Performing a GLR to a PST

You can recover a user mailbox from any active user in the Exchange organization andplace the recovered mailbox items in a PST.

Recovery is not supported for deleted users.

Procedure





Option Description

RDB MailboxRecover(default)

Browse and recover Exchange 2010 and 2013 items froman existing RDB database. Select this option to perform aPST export from an existing RDB.

Granular LevelRecover

Browse and recover items from databases without firsthaving to restore the database to an RSG or RDB. Selectthis option if no RDB currently exists.

Note

Database Recover overwrites existing production mailboxes, which does notproduce the correct results.


4. Select the database in the NMM user interface.

If the database is not listed, select a browse time that includes the desiredbackup. The NetWorker Administration Guide provides details.

5. Select Recover in the taskbar.

6. In the Recover Options dialog, select the Exchange tab.

7. In the PST Target field, enter a UNC filespec for the target PST file.

The UNC filespec should include a path and file name ending in .PST. The PSTfile does not have to exist, but the NMM GUI must be able to write to the targetlocation.

8. Click OK.

9. Click Start Recover from the Recover dialog.

10. To recover items to a PST file, select the location and name of the PST file inthe Exchange Recover Options dialog.

Due to a Microsoft restriction, NMM does not support PST recovery for a singlemail item.If no PST file is specified, then the items selected for recovery are recovered tothe production server.


Performing a GLR to a PST 131



CHAPTER 6

Troubleshooting


l Troubleshooting general errors......................................................................... 134l Troubleshooting backups.................................................................................. 135l Troubleshooting recovery................................................................................. 138

Troubleshooting 133

Troubleshooting general errorsThe following topics explain how to resolve general issues you might encounter whileusing NMM with Exchange Server.

In an Exchange Server DAG environment, if the browse and retention periods forthe nodes and the DAG are not the same, then different parts of the backupexpire at different timesBecause the browse and retention periods are applied separately for each client, if thebrowse and retention periods for the nodes and the DAG are not the same, thendifferent parts of the backup expire at different times. This creates index records withno backup data or backup data with no index records, leading to confusion over whatis available for recovery.

Solution:

Ensure that the browse and retention periods for the DAG nodes are one backup cyclelonger than the browse and retention periods for the DAG client when configuring aclient resource for the DAG client and the client resources for the DAG nodes.

The NMM user interface stops responding when an empty folder is opened onExchange ServerFrom the NMM user interface, if you browse and open an empty folder on ExchangeServer, the user interface stops responding.

Solution:

Do the following:

1. Start Windows Task Manager.

2. Under the Processes tab, end the winclient.exe process.The NMM user interface exits.

3. Open the NMM user interface.

4. Ensure that you browse and open a folder that contains data.

For Exchange Server 2007 and Exchange Server 2010, CPb entries are notdeleted from volumes after retentionAfter passive node backups are performed with 1/1/Day All policy, CPb entries are notproperly deleted from volumes after retention. Although the snapshots are deletedbased on the snapshot policy, at least one extra CPb entry is present apart from theCPb entries for the snapshots.

Solution:

Clean up snapshots and associated flags properly after successful retention.

RM_ExchangeInterface service does not start if a long password is used duringuser login, and backups failIf a long password or a password with space, for example, B@ckup Lottery Network,is used during user login, the RM_ExchangeInterface.exe service does not start andbackups fail.

Solution:

Do not use a long password or a password containing a space.

PST export operations become stalledSome versions of Exchange Server 2013 do not create all the necessary ExchangeSecurity Groups in Active Directory, which can cause PST export operations to stall ineither the "Queued" or "InProgress" state.

Troubleshooting


Solution:

Manually create a group called "ContentSubmitters" (no spaces) under MicrosoftExchange Security Groups, and to assign unlimited rights to both Administrators andNETWORK SERVICE.

If the PST export operation remains stalled, perform the following steps:

1. Stop the Exchange Search and Exchange Search Host Controller services.

2. Dismount the database that contains the NMM Backup User's mailbox.

3. Delete the Content Index folder from the database.This folder is located in the same folder as the database, and its name will be theGUID assigned to the database. For verification, you can obtain the GUID by usingthis PowerShell command:

Get-MailboxDatabase [database name] -status | fl guid4. Restart the Exchange Search and Exchange Search Host Controller services.

5. Wait for the content indexing status to become "Healthy" or "Crawling".You can view the content indexing status by using the following PowerShellcommand:

Get-MailboxDatabaseCopyStatus [database name]\[server name] | flContentIndexState

6. Retry the PST export.

Troubleshooting backupsThe following topics explain issues that might occur during the backup process for anExchange environment, as well as steps to resolve or work around the issues.

Unable to browse mailbox items from a recovered databaseIf you are unable to browse mailbox items from a recovered database, you mustrestore the original (source) mailbox to an alternate (target) mailbox by running theNew-MaiboxRestoreRequest or Restore-Mailbox PowerShell cmdlet. Microsoftprovides a full list of syntax and parameters for these cmdlets.

Solution:

Table 26 PowerShell cmdlets for restored mailboxes

Exchange version PowerShell cmdlet Microsoft website

Exchange 2010 SP1 or laterExchange 2013 CU1 or later

New-MailboxRestoreRequest http://technet.microsoft.com/en-us/library/ff829875.aspx

Exchange 2010 Restore-Mailbox http://technet.microsoft.com/en-us/library/bb125218.aspx

Exchange 2007 Restore-Mailbox http://technet.microsoft.com/en-us/library/aa997694(v=exchg.80).aspx

The following examples show the New-MaiboxRestoreRequest and Restore-Mailboxcmdlets with sample parameters:

Troubleshooting

Troubleshooting backups 135

http://technet.microsoft.com/en-us/library/ff829875.aspx



http://technet.microsoft.com/en-us/library/bb125218.aspx.



http://technet.microsoft.com/en-us/library/aa997694(v=exchg.80).aspx




l Exchange Server 2010 SP1 or later and Exchange Server 2013 CU1 or later:New-MaiboxRestoreRequest -SourceDatabase <RDBNAME> -SourceStoreMailbox <GUID_OF_MAILBOX_YOU_WANT_TO_RESTORE> -TargetMailbox <ORIGINAL_USER_MAILBOX> -Targetrootfolder<Folder_to_restore_into> allowlegacydnmismatch $true

l Exchange Server 2010:Restore-Mailbox -Identity <ALTERNATE_USER_MAILBOX> -RecoveryDatabaseGLR20120320131224 -RecoveryMailbox <ORIGINAL_USER_MAILBOX> -IncludeFolders \Inbox -TargetFolder RECOVERY

l Exchange Server 2007:Restore-Mailbox -Identity <ALTERNATE_USER_MAILBOX> -RSGDatabaseGLR20120320131224 -RSGMailbox <ORIGINAL_USER_MAILBOX> -IncludeFolders \Inbox -TargetFolder RECOVERY

Alternate mount pathIf the file system path specified for NSR_ALT_PATH in the Exchange client does notexist, it is automatically created in NMM. Before performing a backup, delete thespecified alternate path for the NSR_ALT_PATH attribute.

Before performing a backup, empty the contents of the specified alternate path forthe NSR_ALT_PATH attribute. Any data previously stored in that location will bedeleted.

Unmounted or offline databases are skippedIf a database is unmounted or offline when a backup is performed, the backup processskips that database. Generally, this is not an issue because databases that are notmounted are not in production.

Event log error: Microsoft Exchange Replication service VSS Writer failedA failed or canceled backup of a passive copy might produce an error in the Event logthat the Microsoft Exchange Replication service VSS Writer failed. However, thiscondition might be temporary. If this backup failure and error occur, there are twosolutions.:

Solution:

l If you need to perform an immediate backup, stop and then restart the MicrosoftExchange Replication Service writer.

l If you wait about 15 minutes, the Exchange server automatically corrects thiscondition.

NTFS softlinks are skipped by default in Windows VSS backupsNMM Windows File System backups using the NMM Windows VSS client skips NTFSsoftlinks (also known as symbolic links or symlinks). In addition, if an Exchange Serveris configured to save either database files or log files to a softlink path, backups fail.EMC plans to fix this in a future release.

Backups might time out for large Exchange databases when using the defaulttime out valueThe default time out for how long to wait for snapshot creation, before failing thebackup is 20 minutes. For large Exchange servers or databases, backups might failbecause VSS snapshot creation might require more than 20minutes. To specify moretime to wait for VSS snapshot creation before timing out and failing the backup, youcan add the registry key CC_VSS_ASYNC_TIME_OUT in HKEY_LOCAL_MACHINE\SOFTWARE\emc\RMService\RMAgentPS\Client. You must add this registry key ineach DAG node where the DAG client is installed.

Solution:

If the firewall causes the connection to shut down:

Troubleshooting


1. Set the TCP keepalive parameter to a low value, such as 5 minutes on thefollowing:

l NetWorker server

l NetWorker storage node

l NetWorker client (NMM host)For example, on Microsoft Windows, create a registry key:

\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Tcpip\ParametersValue name: KeepAliveTimeValue Type: REG_DWORDValue Data: 300000 (Decimal)

NOTICE

Exercise caution when modifying the Windows registry. The followingMicrosoft article provides details: http://support.microsoft.com/kb/324270.

Your operating system documentation provides information on how to set theTCP keepalive parameter.

2. After the backup failure is resolved, you can increase the KeepAliveTime value ifrequired based upon your backup environment.

MAPI browsing fails in Client Access Server (CAS) array or Network LoadBalancing (NLB) setupSometimes MAPI browsing fails in Client Access Server (CAS) array or Network LoadBalancing (NLB) setup where the CAS server is set to an CAS array or NLB in theNMM user interface. The failure might be due to the NLB configuration, NLB type,firewall setup, or other error.

Solution:

Set up the individual CAS servers to directly communicate with CAS server in suchsetups, instead of creating an CAS Array or NLB through the NMM user interface.

“New page map is wrong size” error is displayed while configuring DAG clientresource on an Exchange Server 2013 DAG in Windows 2012 operating systemThe following error message is displayed while configuring Exchange Server 2013 DAGclient resource using the Configuration wizard for Federated backup on WindowsServer 2012: “New page map is wrong size”

Solution:

Create the client resource manually by using the NetWorker Management Console.

Unhandled exception occurs during item-level recovery for Exchange Server 2010GLR RDBWhen performing item-level recovery to an alternate user mailbox for ExchangeServer 2010 GLR, an unhandled exception might occur.

Solution:

Perform the following steps:

1. Close and reopen the NMM UI.

2. Perform GLR.

3. Perform item-level recovery.

Troubleshooting

Troubleshooting backups 137

http://support.microsoft.com/kb/324270

Exchange Server 2010 backups are not using Data Domain Boost device and thebackups are instead directed to the storage node (NW148692)The NMM and NetWorker client do not recognize the AFTD or Data Domain (DD)device and direct their backups to the storage node instead of the AFTD or DD device.

Solution:

If the NetWorker device for the AFTD or DD device is configured using its name only,and not the IP address, ensure that the NMM client has name resolution for the DataDomain host. You must add entries for both the AFTD or DD device name and IPaddress to the host file on the NMM client.

For Exchange Server 2010, backup fails if a logs volume and a database mountpoint volume are the same and in the same save setBackup fails if a logs volume and a database mount point volume are the same (forexample, D:\) and are in the same save set.

Backup fails with the following message:

RM .. 026420 ERROR:An unexpected internal error occurred:IRD:mountRestoreState::handleFinalStatusMsg() :validateState::runState() failed.

Solution:

Don't configure the log volume and the database mount point volume to be the samelocation.

Troubleshooting recoveryThe following topics explain issues that might occur while performing an Exchangerecovery, as well as steps to resolve or work around the issues.

Exchange GLR failing to establish a Client Direct sessionThe Client Direct feature must be enabled to perform GLR. To verify that theenvironment has Client Direct enabled, perform the following steps:

1. Validate that the NetWorker device is enabled for Client Direct.This verification must only be performed for AFTD devices. Data Domain isautomatically enabled for Client Direct. The EMC NetWorker Administration Guideprovides more information about Client Direct.

2. Validate that the client has name resolutions for the systems.If Data Domain is being used, ensure the client has name resolution for the DataDomain device. If an AFTD storage node is being used, ensure the client has nameresolution for the storage node.

3. Check the application logs directory in the NetWorker Virtual File System (NWFS)log file, nwfs.raw, and look for messages confirming that a Client Direct sessionwas established.

l The message "Performing Direct File Access Restore" confirmsthat a Client Direct session is successfully established.

l The following messages indicate that a Client Direct session could not beestablished:

n Configured to perform Immediate recover, exitingn Configured to perform Non-Immediate recover, exiting

4. Run the following save command from the command prompt:

Troubleshooting


PS C:\Program Files\EMC NetWorker\nsr\bin> save -D1 -aDIRECT_ACCESS=yes -b networker_pool 'C:\Windows\System32\drivers\etc\hosts'Where networker_pool is the NetWorker pool containing the volumes where thesavesets for recovery reside.

5. Check the output for messages indicating the Client Direct session is established:

10/16/16 23:59:27.094472 Default DFA handling by client is 'Fallback'10/16/16 23:59:27.094472 DIRECT_ACCESS=yes: Client direct set to 'Yes'10/16/16 23:59:27.129477 Device attribute block size is 26214410/16/16 23:59:29.185589 libDDBoost version: major: 3, minor: 3, patch: 0, engineering: 2, build: 54505410/16/16 23:59:29.197590 load ddp_get_file_segment_type129292:save: Successfully established Client direct save session for save-set ID '889485007' (mb-vm-sql-2.dpsg-sea.emc.com:C:\Windows\System32\drivers\etc\hosts) with Data Domain volume 'ddveselssemccom.002'.10/16/16 23:59:29.299596 using DFA save for ssid = 88948500710/16/16 23:59:29.299596 ssid 889485007 using DFA save to `mb-vm-nw-2'10/16/16 23:59:29.299596 Successfully setup direct saves

6. (Optional) If the save command fails:

a. Run the save command again after replacing -D1 to -D3:PS C:\Program Files\EMC NetWorker\nsr\bin> save -D3 -aDIRECT_ACCESS=yes -b networker_pool 'C:\Windows\System32\drivers\etc\hosts'Where networker_pool is the NetWorker pool containing the volumes wherethe savesets for recovery reside.

b. Check for output messages indicating the Client Direct session is established.

c. If a Client Direct session is not established, find the messages indicating thecause of the failure, and fix the problem as required.

Exchange Server GLR failing due to error with registry keysIf you try to perform GLR after upgrading to a newer version of NMM, the operationmay fail. To resolve this issue, delete the following MAPI profile registry keys in thefollowing order:

1. HKEY_LOCALMACHINE\Software\Legato\NetWorker\RecoverOptions\MapiProfile

2. HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\LegatoNetWorker

After deleting these registry keys, GLR operations should complete successfully.

Exchange Server 2010 RDB alternate mailbox item-level recovery is failing witherrorAlternate mailbox item-level recovery for Exchange Server 2010 RDB is failing witherror:

An unspecified error has occurred. 1 0 19 E_FAIL.SolutionThe target user must log in to the mailbox through the Outlook Web Application andsend a few test mails, and then perform item-level recovery to target user mailbox.

Troubleshooting

Troubleshooting recovery 139

Unhandled exception occurs during item-level recovery for Exchange Server 2010GLR RDBWhen performing item-level recovery to an alternate user mailbox for ExchangeServer 2010 GLR, an unhandled exception might occur.

SolutionPerform the following steps:

1. Close and reopen the NMM UI.

2. Perform GLR.

3. Perform item-level recovery.

In Exchange Server 2010, unhandled exception occurs when mounting RDB afterfailed recoverySometimes, after an RDB recovery failure, when the RDB is dismounted and the NMMuser interface is left open for a few days without use, and the RDB is then remounted,unhandled exception occurs.

SolutionClose and reopen the NMM user interface.

In Exchange Server 2010, RDB item level recovery fails with “insufficientpermissions to access mailbox” errorIf the mailbox database where the currently logged in user mailbox resides isnotmounted, then an RDB item-level recovery might fail with the following errormessage:

Insufficient permissions to access mailbox

SolutionTo browse the contents in RBD, ensure that the mailbox database where the currentlylogged in user mailbox resides is mounted. MAPI communicates with the RDB mailboxthrough the currently logged in user mailbox.

For example, if the user is logged in as Administrator, the mailbox database thatcontains the Administrator mailbox should be mounted.

Cannot browse Exchange Server 2010 RDB on a stand-alone serverExchange Server 2010 must have an administrative mailbox to browse an RDB withNMM. This mailbox is created by default. Sometimes, the Active Directory entry forthis mailbox becomes corrupt and leads Exchange to believe the following:

l The mailbox does not exist.

l The user (administrator) already has a mailbox and does not let you create amailbox.

SolutionPerform the following steps:

1. Manually remove all Exchange Active Directory entries for the administrator byusing ADSI edit.The administrator is visible.

2. Re-create a mailbox for the administrator.After the new mailbox is created, you can browse the RDB.

Recovery fails if new mailbox database is createdAfter backing up a storage group, if you create a mailbox database in the same storagegroup and then try to recover the storage group, the recovery fails.

Troubleshooting


SolutionDismount the newly created database, back up the storage group, and then recoverthe backup.

Alternate storage group directed recovery with different Exchange versionsdisplays error message while mounting the databaseYou must use the same version of Exchange Server for both backup and recovery. Ifyou back up an Exchange database from one version of Exchange Server (forexample, a database from Exchange Server 2010), but perform recovery of the samedatabase from another Exchange Server version (for example, using Exchange Server2013), the recovery is successful. However, while mounting the database, thefollowing error message is displayed:

Database "<Storage Group\Database>" is too new to be upgraded.SolutionEnsure that the same version of Exchange database is used for both backup andrecovery.

Troubleshooting

Troubleshooting recovery 141

Troubleshooting


GLOSSARY

This glossary contains terms related to disk storage subsystems. Many of these termsare used in this manual.

A

ad hoc backup See manual backup.

administrator The person normally responsible for installing, configuring, and maintaining NetWorkersoftware.

administrators group Microsoft Windows user group whose members have the rights and privileges of usersin other groups, plus the ability to create and manage the users and groups in thedomain.

advanced file typedevice (AFTD)

Device that supports concurrent backup and restore operations. AFTD storage isdesigned for large disk storage systems that use a volume manager to dynamicallyextend available disk space if the disk runs out of space during backup.

Application SpecificModule (ASM)

Program that is used in a directive to specify how a set of files or directories is to bebacked up or recovered. For example, compressasm is a NetWorker directive used tocompress files.

archive Backing up directories or files to an archive volume to free disk space. Archived data isnot recyclable.

archive volume Volume used to store archive data. Archived data cannot be stored on a backup volumeor a clone volume. See backup volume. See clone volume.

ASR writer The VSS Writer, which is responsible for identifying critical data that is needed toperform an offline restores.

autochanger See library.

autochanger sharing See library sharing.

auto media management Feature that enables the storage device to automatically label, mount, and overwrite anunlabeled or recyclable volume.

B

backup Operation that saves data to a volume. See conventional backup. See snapshot.

backup components See metadata document.

backup group See group.

backup level See level.


backup volume Volume used to store backup data. Backup data cannot be stored on an archive volumeor a clone volume. See archive volume. See clone volume. See volume.

Boot Configuration Data(BCD)

The ASR Writer component that identifies the location of the boot configurationdatabase. This is required to perform an offline restore.

bootstrap Save set that is essential for NetWorker disaster recovery procedures. The bootstrapconsists of three components that reside on the NetWorker server. The mediadatabase, the resource database, and the server index.

browse policy NetWorker policy that specifies how long backed-up data is readily available forrecovery. Backed-up data that has not exceeded its browse policy time can berecovered more quickly than data that has exceeded its browse policy time but not itsretention policy time. See retention policy.

C

carousel See library.

circular logging An option that deletes the inactive transaction log files to reduce the disk space thatthe log files consume on a server.

client Computer, workstation, or fileserver whose data can be backed up and recovered.

client file index Database that tracks every database object, file, or file system that is backed up. TheNetWorker server maintains a single client index file for each client. See file system.

client-initiated backup See manual backup.

client resource NetWorker server resource that identifies the save sets to be backed up on a client.The client resource also specifies information about the backup, such as the schedule,browse policy, and retention policy for the save sets. See client, See resource.

clone Reliable copy of backed up data. Unlike volumes created with a simple copy command,clone volumes can be used in exactly the same way as the original backup volume.Single save sets or entire volumes can be cloned.

clone volume Exact duplicate of a backup volume. One of four types of volumes that NetWorkersoftware can track (backup, archive, backup clone, and archive clone). Save sets ofthese different types might not be intermixed on one volume.

cluster 1. Two or more independent network servers that operate and appear to clients as ifthey are a single unit. The cluster configuration enables work to be shifted from oneserver to another, providing "high availability" that allows application services tocontinue despite most hardware or software failures. Also known as an agent (Sun),logical server (HP TruCluster), package (HP-UX), and virtual server (Microsoft).

2. Group of disk sectors. The operating system assigns a unique number to each clusterand keeps track of files according to which clusters they use.

command line Line on a screen, also known as a command prompt or shell prompt, where you typesoftware commands.

Glossary


component 1. Group of related data that must be treated as a single unit for backup and recovery.

2. In Microsoft VSS terminology, a component is a subordinate unit of a See writer.

components metadatadocument

See metadata document.

consistent State of a dataset that is fully and immediately available to an application view.

console server Software program that is used to manage NetWorker servers and clients. The Consoleserver also provides reporting and monitoring capabilities for all NetWorker processes.

conventional backup See nonpersistent snapshot.

critical volume Any volume containing system state files or files for an installed service, includingvolumes mounted as NTFS directories which contain such files. The volume where acritical volume is mounted is also considered to be critical. This is required to performan offline restore, however maybe optional for this release depending upon thedifficulties of implementing this feature.

D

database availabilitygroup (DAG)

A group of mailbox servers that hosts a set of databases and enables database or serverlevel recovery. Each DAG can host up to 16 mailbox servers.

data retention policy See retention policy.

datawheel See library.

datazone Group of hosts administered by a NetWorker server.

device 1. Storage unit that reads from and writes to backup volumes. A storage unit can be atape device, optical drive, autochanger, or file connected to the server or storage node.See autochanger. See storage node.

2. When dynamic drive sharing (DDS) is enabled, refers to the access path to thephysical drive.

directed recovery Method of recovery that recovers data that originated on one client computer and re-creates it on another client computer.

directive Instruction that directs NetWorker software to take special actions on a given set offiles for a specified client during a backup or recovery operation. Directives are ignoredin manual (unscheduled) backups.

disk subsystem Integrated collection of storage controllers or HBAs, disks, and any required controlsoftware that provides storage services to one or more hosts.

Distributed File System(DFS)

Microsoft Windows add-on that allows you to create a logical directory of shareddirectories that span multiple computers across a network.

domain controller Computer that stores directory data and manages user interactions within a domain,including logon, authentication, directory searches, and access to shared resources.

Glossary


Dynamic Drive Sharing(DDS)

Feature that allows NetWorker software to recognize shared drives.

F

failover A safeguard capability that automatically switches the focus of activity from a failed orabnormally terminated computer server, disk drive, or network to a redundant standbyserver, drive, or network, with little or no disruption of service. Failover is a feature ofsystems that require high reliability and continuous availability.

file index See client file index.

file system 1. The software interface used to save, retrieve, and manage files on storage media byproviding directory structures, data transfer methods, and file association.

2. The entire set of all files.

full backup See level.

G

granular recovery Granular recovery provides the ability to recover specific files in seconds from a singlebackup. This dramatically reduces the recovery time and the footprint of the backup onstorage resources.

group Client or group of client computers that are configured to back up files at a designatedtime of day.

H

high-available system System of multiple computers configured as cluster nodes on a network that ensuresthat the application services continue despite a hardware or software failure. Eachcluster node has its own IP address with private resources or disks that are availableonly to that computer.

host ID Serial number that uniquely identifies a host computer.

I

inactivity timeout Number of minutes to wait before a client is considered to be unavailable for backup.

incremental backup Backup level in which only files that have changed since the last backup are backed up.See level.

instant backup Process of creating a point-in-time copy (snapshot) of data from a single client andsaving it on a primary storage volume, which can be immediately recovered as a backupcopy.

instant restore Process of copying data created during an instant backup to its original location, or toan alternate location, during a recover operation.

Glossary


J

jukebox See library.

L

label Electronic header on a volume used for identification by NetWorker.

legacy method Use of special-case Microsoft APIs to back up and recover operating systemcomponents, services, and applications.

level level

A backup configuration option that specifies how much Exchange data is saved duringthe backup. The Microsoft Exchange level options are:

Full — Backs up databases and transaction logs, and truncates committed logs.

Incremental — Backs up transaction logs created since the last backup, and truncatescommitted logs.

library Hardware device that contains one or more removable media drives, as well as slots forpieces of media, media access ports, and a robotic mechanism for moving pieces ofmedia between these components. Libraries automate media loading and mountingfunctions during backup and recovery. The term library is synonymous withautochanger, autoloader, carousel, datawheel, jukebox, and near-line storage.

library sharing Shared access of servers and storage nodes to the individual tape drives within alibrary.

local cluster client NetWorker client that is not bound to a physical computer, but is instead managed by acluster manager. It is also referred to as a logical or virtual client.

locale settings Settings that specify the input and output formats for date and time, based on locallanguage conventions.

LUN (logical unit) Logical unit of storage on a computer. This refers to a device or set of devices, usuallyin a storage array.

LUN address SCSI identifier of a logical unit number (LUN) within a device target. Each LUN addressidentifies a device on a SCSI bus that can perform input/output (I/O) operations.

M

mailbox database The part of the Exchange Server IS that maintains information in user mailboxes. Amailbox database consists of a rich text .edb file, a streaming native Internetcontent .stm file, and associated transaction log files.

manual backup Backup that a user performs from the client, also known as an unscheduled backup oran ad hoc backup. The user specifies the files, file systems, and directories to back up.

MAPI (Microsoftmessaging API)

A Microsoft API that enables applications to use messaging through MicrosoftExchange.

Glossary


media Physical storage medium, such as magnetic tape, optical disk, or file system to whichbackup data is written.

media database Database that contains indexed entries of storage volume location and the life cyclestatus of all data and volumes managed by the NetWorker server. See also See volume.

media index See media database.

metadata document VSS Information stored in an XML document that is passed from the writer to therequestor. Metadata includes the writer name, files, and components to back up, a listof components to exclude from the backup, and the methods to use for recovery. Seewriter. See requestor. See shadow copy set.

mount To make a database available for use or to place a removable tape or disk volume into adrive for reading or writing.

mount point See volume mount point.

N

Network DataManagement Protocol

(NDMP)

TCP/IP-based protocol that specifies how heterogeneous network componentscommunicate for the purposes of backup and recovery.

NetWorker administrator User who can add to or change the configuration of the NetWorker server, mediadevices, and libraries. NetWorker administrators must have their usernames included inthe NetWorker server Administrator list.

NetWorker client See client.

NetWorker Consoleserver

See console server.

NetWorker ManagementConsole

See console server.

NetWorker server Computer on a network running the NetWorker software, containing the online indexes,and providing backup and recover services to the clients on the same network.

NetWorker storage node See storage node.

nonclone pool Pools that contain data that has not been cloned.

noncritical volume A volume containing files that are not part of the system state or an installed service.The backup of non-critical volumes is not supported by either product for their initialreleases.

nonpersistent snapshot Snapshot backup that is moved to secondary storage on the NetWorker server orstorage node and is no longer available for instant restore from a supported type ofprimary storage.

Glossary


O

offline restore A restore operation performed from the Windows PE environment.

online indexes Databases located on the NetWorker server that contain all the information pertainingto the client backups (See client file index) and backup volumes (See media database).

online restore A restore operation performed using the normal recover UI, and the computer has beenbooted from an installed operating system.

operator Person who monitors the server status, loads backup volumes into storage devices, andexecutes day-to-day NetWorker tasks.

P

pathname Set of instructions to the operating system for accessing a file. An absolute pathnameindicates how to find a file starting from the root directory. A relativepathnameindicates how to find the file starting from the current directory.

persistent snapshot Snapshot that is retained on disk. A persistent snapshot might or might not be rolledover to tape.

point-in-time copy (PiT) Fully usable copy of a defined collection of data, such as a consistent file system,database, or volume, which contains an image of the data as it appeared at a singlepoint in time. A PiT copy is also called a shadow copy or a snapshot. See shadow copy,See snapshot.

policy Set of constraints that specify how long the save sets for a client are available forrecovery. Each client has a browse policy and a retention policy. When the retentionpolicy expires, the save sets associated with that policy are marked recyclable.

pool Feature to sort backup data to selected volumes.

PowerSnap EMC technology that provides point-in-time snapshots of data to be backed up.Applications that are running on the host system continue to write data during thesnapshot operation, and data from open files is included in the snapshots.

provider Software component defined by Microsoft VSS, that plugs in to the VSS environment.A provider, usually produced by a hardware vendor, enables a storage device to createand manage snapshots.

Q

quiescing Process in which all writes to disk are stopped and the file system cache is flushed.Quiescing the database prior to creating the snapshot provides a transactionallyconsistent image that can be remounted without file system checks or databaseconsistency checks. Quiescing a database is the most common way of creating adatabase snapshot.

Glossary


R

recover To recover files from a backup volume to a client disk.

Recovery Storage Group(RSG)

A Microsoft Exchange Server feature that enables mounting a copy of an Exchangemailbox database on the same server as the original database, or on any other Exchangeserver in the same Exchange administrative group.

Registry Microsoft Windows database that centralizes all Windows settings and providessecurity and control over system, security, and user account settings.

replica See shadow copy.

requestor Interface with the Microsoft VSS infrastructure to initiate the creation and destructionof See shadow copy. NetWorker software is a requestor.

resource Component that describes the NetWorker server or its clients. Clients, devices,schedules, groups, and policies are all NetWorker resources. Each resource hasattributes that define its properties.

restore Process of retrieving individual datafiles from backup storage and copying the files todisk.

retention policy NetWorker policy that specifies the minimum period of time that must elapse beforebacked-up data is eligible to be overwritten on the backup media. Backed-up data thathas not exceeded its browse policy time can be recovered more quickly than data thathas exceeded its browse policy time but not its retention policy time. See browsepolicy.

retrieve To locate and recover archived files and directories.

rollover Process of backing up a snapshot to a conventional backup medium such as tape.Whether or not the snapshot is retained on disk depends on the snapshot policy.

root Highest level of the system directory structure.

S

save set Group of files or a file system from a single client computer, which is backed up onstorage media.

save set ID (SSID) Internal identification number assigned to a save set.

save set recover To recover data by specifying save sets rather than by browsing and selecting files ordirectories.

save set status NetWorker attribute that indicates whether a save set is browsable, recoverable, orrecyclable. The save set status also indicates whether the save set was successfullybacked up.

save stream The data and save set information is written to a storage volume during a backup.

server index See client file index.

Glossary


service port Port used to listen for backup and recover requests from clients through a firewall.

shadow copy Temporary, point-in-time copy of a volume created using VSS technology. See VolumeShadow Copy Service (VSS).

shadow copy set Complete roadmap of what was backed up at a single instant in time. The shadow copyset contains information about the Writers, their components, metadata, and thevolumes. A backup components metadata document containing that information iscreated and returned to the requestor after the snapshot is complete. NetWorker usesthis document with the corresponding save set at recover time.

shadow copy technology Defined and standard coordination between business application, file system, andbackup application that allows a consistent copy of application and volume data to existfor replication purposes.

skip Backup level in which designated files are not backed up. See level.

snap clone Exact copy of a snap set data backup. The clone operation is an archive operationwithout the deletion of the source data. A new snap ID is assigned to the cloned copy.

snap ID Also known as a snapid, a unique 64-bit internal identification number for a snap set.

snap set Group of files, volumes, or file systems from a single client, describing the collection ofdata for which a point-in-time copy is created on an external disk subsystem, such as astorage array.

snapshot Point in time, read-only copy of data created during an instant backup.

snapshot expirationpolicy

Policy that determines how long snapshots are retained before their storage space ismade available for the creation of a new snapshot.

snapshot policy Set of rules that control the lifecycle of a snap set. The snapshot policy specifies thefrequency of snapshots, and how long snapshots are retained before recycling.

snapshot retentionpolicy

Policy that determines how many PIT copies are retained in the media database andthus are recoverable.

staging Moving data from one storage medium to a less-costly medium, and later removing thedata from its original location.

stand-alone device Storage device that contains a single drive for backing up data. Stand-alone devicescannot store or automatically load backup volumes.

storage device See device.

storage group A collection of mailbox databases and public folder databases that share a set oftransaction log files. Exchange manages each storage group with a separate serverprocess.

storage node Storage device physically attached to a computer other than the NetWorker server,whose backup operations are administered from the controlling NetWorker server.

system state All files that belong to VSS Writers with a usage type of BootableSystemState orSystemService. This is required to perform an offline restore.

Glossary


T

Transaction logs Files that Exchange uses to commit data (e- mail messages, user additions, creation offolders, and so forth) to the corresponding database file on disk. Used for incrementalbackups.

V

volume 1. A unit of physical storage medium, such as a magnetic tape, optical disk, or filesystem to which backup data is written.

2. An identifiable unit of data storage that might reside on one or more host disks.

volume ID Internal identification that NetWorker software assigns to a backup volume.

volume mount point Disk volume that is grafted into the namespace of a host disk volume. This allowsmultiple disk volumes to be linked into a single directory tree, and a single disk orpartition to be linked to more than one directory tree.

volume name Name assigned to a backup volume when it is labeled. See label.

volume pool See pool.

Volume Shadow CopyService (VSS)

Microsoft technology that creates a point-in-time shadow copy of a disk volume.NetWorker software backs up data from the shadow copy. This allows applications tocontinue to write data during the backup operation, and ensures that open files are notomitted. See shadow copy

VSS See Volume Shadow Copy Service (VSS).

VSS component Subordinate unit of a writer. See writer.

W

writer Database, system service, or application code that provides metadata documentinformation about what to back up and how to handle VSS components and applicationsduring backup and recovery operations. A writer provides information to requestors toensure that application data is consistent, application files are closed and ready for aslight pause in order to make a Shadow Copy. See metadata document. See VSScomponent.

Glossary


Documents

for Exchange Server VSS NetWorker Module for Microsoft · PDF fileExchange Server 2010 and 2013 DAGs ... Mounting the database after recovery ... l NetWorker Module for Microsoft for