EMC NetWorker Module for Microsoft for Exchange … NetWorker Module for Microsoft for Exchange...

EMC NetWorker Module for Microsoft forExchange Server VSSVersion 9.0.1

User Guide302-002-937

REV 03

Copyright © 2007-2017 Dell Inc. or its subsidiaries. All rights reserved.

Published March 2017

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

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS-IS.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND

WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED

IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their 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 9.0.1 User Guide

7

9

11

Introduction 15Overview.....................................................................................................16

NMM 9.0.1 compatibility with NetWorker 8.2.3 or later servers .... 16Stand-alone or single Exchange Servers........................................ 16Exchange Server DAGs.................................................................. 17High availability in Exchange Server............................................... 18Federated IP-less DAG backup.......................................................18DAG AutoReseed............................................................................18Active and passive databases......................................................... 19Shadow copy and log truncation.................................................... 19Client Direct................................................................................... 19

Using NMM in an Exchange Server environment........................................20Exchange Server 2010 VSS Writers...............................................20Exchange Server 2013 and 2016 VSS Writer..................................20Compatibility with previous Exchange backups............................. 20Backup-initiated transaction log file truncation.............................. 21Backup types and levels................................................................. 21Federated DAG backups................................................................ 22Recovery types..............................................................................22

Configuration 23Supported Exchange server deployment scenarios and limitations............. 24

Supported Exchange Server versions............................................ 24Microsoft Exchange Server and Microsoft SharePoint Serverinstallation on the same host......................................................... 24

NMM Exchange Admin Configuration tool..................................................24Configuring an Admin user.............................................................26Validating an existing Admin.......................................................... 30

MAPI Client and Collaboration Data Objects............................................... 31Exchange consistency check...................................................................... 31

Consistency check parameters for threading and throttling.......... 32

Backup 35Planning backups........................................................................................36

Backup considerations...................................................................36Exchange backup prerequisites..................................................... 36Circumstances that promote incremental or subsequent backups tofull backup..................................................................................... 36

Roadmap of configuring Exchange backups................................................37

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

CONTENTS

EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0.1 User Guide 3

Backup configuration options........................................................ 37Configuring backups of a stand-alone server..............................................39

By using the Client Backup Configuration wizard.......................... 39By using the Client Properties window.......................................... 42

Configuring federated backups of a DAG................................................... 45Performing backups in a DAG environment................................... 45Preferred server order list............................................................. 46Configuring federated backups of a DAG with an IP...................... 46Configuring federated backups of an IP-less DAG......................... 57Configuring backups to use a remote storage node in a DAGenvironment.................................................................................. 68Example of a federated backup..................................................... 69

Configuring NetWorker privileges...............................................................70Modifying a client resource by using the Client Properties window afterupgrading from NMM version 8.2.x or earlier.............................................. 71Verifying a backup...................................................................................... 72

Mail Item Recovery 73Overview.................................................................................................... 74

Recovery types..............................................................................74Recovering Exchange data............................................................ 75Recovering individual mailboxes, mailbox folders, and messages... 76

Exchange recovery prerequisites................................................................80Additional requirements for browsing mailboxes............................80Additional requirements for recovering databases in a DAG........... 81

Configuring Exchange Server recovery....................................................... 81Specifying Exchange recovery options...........................................81Configuring roll-forward recovery of an Exchange server in a DAGenvironment.................................................................................. 82

Recovery procedures..................................................................................83Viewing volumes to back up for recovery.......................................84Recovering NetWorker Module for Microsoft Exchange backups....84Mounting the database after recovery...........................................84Performing Exchange Server recovery.......................................... 84Recovering deleted Exchange Server mailboxes, public folderdatabases, or public folder mailboxes............................................. 91Performing a quick recovery of a deleted mailbox......................... 92Recovering Exchange Server mailbox, public folder database, orpublic folder mailbox files...............................................................93

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

Granular Level Recovery 97Recovering Mailbox items with GLR........................................................... 98

GLR considerations....................................................................... 98Options for Exchange GLR............................................................ 99

Exchange server GLR using ItemPoint for Microsoft Exchange Server.....100Recovering individual mailbox items by using ItemPoint forMicrosoft Exchange Server..........................................................100Unmounting backups after ItemPoint for Microsoft ExchangeServer GLR.................................................................................. 102Using the BBB Mount system tray icon........................................ 103

Exchange server GLR using the NMM UI.................................................. 103

Chapter 4

Chapter 5

CONTENTS


GLR considerations for the NMM UI............................................ 103Recovering individual mailbox items using GLR through the NMM UI.....................................................................................................103Performing a GLR to an alternate mailbox using the NMM UI...... 105Performing a GLR on an archive user mailbox using the NMM UI....106Performing a GLR to a PST using NMM UI.................................. 106

Troubleshooting 109Troubleshooting general errors.................................................................. 110Troubleshooting backups........................................................................... 110Troubleshooting recovery.......................................................................... 112Troubleshooting granular level recovery.................................................... 113

Chapter 6

CONTENTS


CONTENTS


NetWorker and NMM installation in a stand-alone or single Exchange Serverenvironment................................................................................................................ 17NetWorker and NMM installation with a DAG in an Exchange Server environment..... 18Exchange Server DAG environment............................................................................ 19NMM Exchange Admin Configuration tool..................................................................25Configuring a user with Organization Management rights.......................................... 28Configuring a user without Organization Management rights..................................... 29Initial view of the Client Backup Configuration wizard................................................ 40Initial view of the Client Backup Configuration wizard................................................ 48Initial view of the Client Backup Configuration wizard................................................ 58Adding the DAG name as an alias to a client resource................................................. 61Adding the DAG name as an alias to a client resource.................................................67Example of an Exchange Server federated backup..................................................... 70Recovery in a stand-alone Exchange Server environment.......................................... 75Recovery to an alternate MailboxDatabase in a stand-alone Exchange Serverenvironment............................................................................................................... 76Recover using NMM granular level recovery...............................................................78Recover to an RDB, and then recover data from the RDB to a user mailbox............... 79Advanced Recovery dialog box................................................................................... 86Exchange Recovery Summary dialog box....................................................................87Manage RDB dialog box..............................................................................................88Create RDB dialog box................................................................................................88Delete confirmation dialog box................................................................................... 89Select Database dialog box.........................................................................................90Select Server dialog box.............................................................................................90Exchange Recovery Options window for ItemPoint GLR........................................... 101Mounting the backup for ItemPoint GLR................................................................... 101Successful mount operation output in the Monitor page........................................... 102Individual mailbox databases..................................................................................... 104Sample mailbox......................................................................................................... 105

1

234567891011121314

1516171819202122232425262728

FIGURES


FIGURES


Revision history...........................................................................................................12Style conventions........................................................................................................13Writers used by NMM for Exchange Server backup and recovery..............................20Exchange backup types and levels.............................................................................. 21Permissions configured by the Exchange administrator configuration tool ................ 25Exchange Server GLR MAPI/CDO requirements.........................................................31Exchange application information variables for threading and throttling ....................32Exchange Server 2010 save set names....................................................................... 43Exchange Server 2013 save set names....................................................................... 43Exchange Server 2016 save set names....................................................................... 43Special characters and their URL-encoded values...................................................... 44Exchange Application Information attribute settings.................................................. 44Exchange Server 2010 save set names........................................................................51Exchange Server 2013 save set names....................................................................... 52Exchange Server 2016 save set names....................................................................... 52Special characters and their URL-encoded values......................................................52Exchange Application Information attribute settings.................................................. 53Exchange Application Information attribute settings.................................................. 54Examples for application variables..............................................................................55Exchange Server 2010 save set names....................................................................... 63Exchange Server 2013 save set names....................................................................... 63Exchange Server 2016 save set names....................................................................... 63Special characters and their URL-encoded values......................................................64Exchange Application Information attribute settings.................................................. 64Examples for application variables.............................................................................. 66User group privileges for NMM operations................................................................. 70Options for Exchange GLR......................................................................................... 99Performing a GLR to a PST recover options..............................................................107PowerShell cmdlet for restored mailboxes................................................................. 111

1234567891011121314151617181920212223242526272829

TABLES


TABLES


Preface

As part of an effort to improve its product lines, EMC periodically releases revisions ofits software and hardware. Therefore, some functions that are described in thisdocument might not be supported by all versions of the software or hardwarecurrently in use. The product release notes provide the most up-to-date informationon product features.

Contact your EMC technical support professional if a product does not functioncorrectly 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 EMC NetWorker Module for Microsoft(NMM) Release 9.0.1 software to back up and recover Microsoft Exchange Serverusing the Volume Shadow Copy Service (VSS) technology.

Note

The EMC NetWorker Module for Microsoft Administration Guide supplements the backupand recovery procedures described in this guide and must be referred to whenperforming application-specific tasks. Download a copy of the EMC NetWorker Modulefor Microsoft Administration Guide from EMC Online Support (https://support.emc.com) before using this guide.

AudienceThis guide is part of the NMM documentation set, and is intended for use by systemadministrators during the setup and maintenance of the product. Readers should befamiliar with the following technologies used in backup and recovery:

l EMC NetWorker software

l EMC NetWorker data protection policy 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

03 March 27, 2017 The following changes are included in this revision:

l Updated all client configuration procedures withinformation about using AFTDs with NetWorkerserver 8.2.3 and NMM 9.0.1

l Updated the "Troubleshooting general errors"section with information about mailbox structureappearing distorted in Outlook Web Access after anExchange 2016 PIT restore operation

02 July 15, 2016 The "Related documentation" section in the Prefacehas been updated.

01 June 29, 2016 First release of this document for EMC NetWorkerModule for Microsoft release 9.0.1. The followingchanges are included:

l Information about the following new features isadded:

n NMM 9.0.1 compatibility with NetWorker 8.2.3and later servers

n Support for federated IP-less DAG backup andrecovery

n Support for DAG AutoReseed configurations

n Support for granular level recovery by usingEMC® ItemPoint™ for Microsoft ExchangeServer

n Support for granular level recovery by usingNMM Support Tool

l Incorporated technical review commentsthroughout the guide for improved usability

l Added more information about the NMM ExchangeConfiguration tool to the Configuration chapter:

n Configuring an Admin user

n Example Admin user configurations

n Validating an existing Admin

Related documentationThe NMM documentation set includes the following publications:

l EMC NetWorker Module for Microsoft Release Notes

l EMC NetWorker Module for Microsoft Administration Guide

l EMC NetWorker Module for Microsoft Installation Guide

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

Preface


l EMC NetWorker Module for Microsoft for SQL VDI User Guide

l EMC NetWorker Module for Microsoft for Exchange VSS User Guide

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

l EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery SolutionUser Guide

l EMC ItemPoint for Microsoft SharePoint Server User Guide

l EMC ItemPoint for Microsoft Exchange Server User Guide

l NetWorker documentation set

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

NOTICE

Identifies content that warns of potential business or data loss.

Note

Contains information that is incidental, but not essential, to the topic.

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

Table 2 Style conventions

Bold Used for names of interface elements, such as names of buttons,fields, tab names, and menu paths (what the user specifically selectsor clicks)

Italic Used for full titles of publications that are referenced in text

Monospace Used 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 Used for variables

Monospace bold Used 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 that is omitted from theexample

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.

Preface


https://support.emc.com

Technical supportGo to EMC Online Support and click Service Center. Several options for contactingEMC Technical Support appear on the site. Note that to open a service request, youmust have a valid support agreement. Contact your EMC sales representative fordetails about obtaining a valid support agreement or with questions about youraccount.

Online communitiesGo to 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 help to improve the accuracy, organization, and overall quality of theuser publications. Send your opinions of this document to [email protected].

Preface


https://community.emc.com

mailto:[email protected]

CHAPTER 1

Introduction

This chapter includes the following sections:

l Overview............................................................................................................ 16l Using NMM in an Exchange Server environment............................................... 20

Introduction 15

OverviewThe EMC

® NetWorker

® Module for Microsoft (NMM) software supports backup and

recovery for Exchange Server 2010, 2013, and 2016 databases in stand-alone and DAGconfigurations.

Note

EMC recommends that you 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.

NMM 9.0.1 compatibility with NetWorker 8.2.3 or later serversNMM supports backup and recovery with NetWorker client version 9.0.1 andNetWorker server version 8.2.3 or later.

The EMC NetWorker Module for Microsoft Release 9.0.1 Installation Guide contains theNMM support matrix for NetWorker server and client versions. Refer to the individualNMM release sections of the EMC NetWorker Online Software Compatibility Guide formore specific details.

Note the following limitations when configuring NMM backup and recovery withNetWorker 9.0.1 client and NetWorker 8.2.3 server or later:

l Dedicated Storage Node—NetWorker server 8.2.3 does not support theNetWorker storage node 9.0.1. As a result, a dedicated storage node cannot beconfigured when using NetWorker client version 9.0.1 with NetWorker server8.2.3.

l Volume affinity—NetWorker server 8.2.3 does not support the volume affinityfeature. NetWorker server 9.0 and later support the volume affinity feature. ForNMM Exchange and Hyper-V, an incremental level backup is promoted to level fullif the same volume, or a volume from the same Data Domain device, from priorbackup cannot be obtained.

l New backup levels—NetWorker server 8.2.3 does not support NetWorker serverversion 9.0 and later new backup levels. NetWorker server 8.2.3 uses NetWorkerserver 8.x backup level definitions.

Stand-alone or single Exchange ServersThis section describes the relationship between the stand-alone or single ExchangeServers and NMM.

In a stand-alone or single Exchange Server environment, all mailbox databases, logfiles, and checkpoint files exist on one server. NMM is installed on the Exchangeserver.

The following figure illustrates the relationship between the NetWorker Server,NetWorker Management Console (NMC), and NMM client installation in a singleExchange server environment. NMM is installed on the Exchange server.

Introduction


http://support.emc.com

Figure 1 NetWorker and NMM installation in a stand-alone or single Exchange Serverenvironment

Exchange Server DAGsThis section describes the relationship between Exchange server database availabilitygroups (DAGs) and NMM.

NMM supports DAGs for high availability of Exchange Server databases, with thefollowing considerations:

l Install the NetWorker and NMM clients on each Exchange server that has themailbox role installed.

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 copy mailbox databases, passive copy mailbox databases,and stand-alone databases.

l “Stand-alone” applies to an Exchange Server mailbox database that is notreplicated across multiple servers, including public folder mailboxes and publicfolder databases.

l You can only restore backups of databases in a DAG environment to activedatabase copies.The Microsoft TechNet website provides additional information about theExchange DAG architecture.

Introduction

Exchange Server DAGs 17

Figure 2 NetWorker and NMM installation with a DAG in an Exchange Server environment

The topic Roadmap of configuring Exchange backups on page 37 providesinformation on configuring a DAG backup after you install the NetWorker and NMMclients on each Exchange server in the cluster.

High availability in Exchange ServerMost larger enterprises typically deploy Exchange Server in some form of high-availability configuration. Exchange Server 2010, 2013, and 2016 typically includes theuse of DAGs and mailbox database copies. You are not required to install and configureany Windows clustering before you install Exchange Server. You can add highavailability to the Exchange Server environment after you deploy Exchange Serverwithout uninstalling Exchange Server and then reinstalling in a high-availabilityconfiguration. These improvements in high availability and site resilience functionalityalso simplify installation and configuration of the NetWorker and NMM clients forbackup and recovery.

Federated IP-less DAG backupNMM supports backups of Exchange DAG databases with no administrative accesspoint.

This DAG type is not linked to any physical or virtual IP that can be connected on thenetwork. An existing DAG (IP-based) cannot be converted to an IP-less DAG. Refer tothe Backup chapter for more information on IP-less DAG backup configuration.

DAG AutoReseedNMM supports AutoReseed configuration on Exchange server 2013 SP1 and later.

AutoReseed is a DAG feature that quickly restores database redundancy after a diskfailure, database corruption, or other event that requires reseeding of a databasecopy. If the database is compromised, the database copies stored on the diskautomatically reseed to a pre-configured spare disk on the mailbox server.

For more information about the AutoReseed feature, and how to configure a DAG withAutoReseed, refer to the following article:

https://technet.microsoft.com/en-us/library/dn789209(v=exchg.150).aspx

Introduction


https://technet.microsoft.com/en-us/library/dn789209(v=exchg.150).aspx

Active and passive databasesThis topic describes NMM installations with Exchange Server 2010 and later clusteredenvironments.

In a clustered environment, there are active and passive copies of the databases. TheExchange Server constantly updates a copy or a replica as the passive copy. Forbackups, the passive copy enables you to back up the databases without affecting theperformance or data of the active copy. You must designate individual databases aseither active or passive. This enables you to have a mix of active and passivedatabases on each node.

The following figure shows an Exchange Server DAG environment with four mailboxdatabases (DB1, DB2, DB3, and DB4). There are active and passive copies of thesedatabases spread over three nodes (servers MBX1, MBX2, and MBX3).

Figure 3 Exchange Server DAG environment

Configuring Exchange backups provides detailed steps for configuring the NMM clienton the active node after installation of the NMM client on each Exchange Server inthe cluster.

Shadow copy and log truncationThe 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.

Client DirectThe Client Direct feature enables clients that have a direct network or a DD Boostover Fibre Channel (DFC) connection to the Data Domain system to send and receivedata directly to Data Domain AFTD and DD Boost devices. Client Direct supportsmultiple concurrent backup and restore operations that bypass the NetWorker storagenode, which eliminates a potential bottleneck. The storage node manages the devices

Introduction

Active and passive databases 19

that the clients use but does not handle the backup data. Client Direct was previouslyknown as Direct File Access (DFA).

When the connection is available, NMM enables Client Direct by default and also usesClient Direct to recover duplicated backups that NMM had performed with a storagenode.

Using NMM in an Exchange Server environmentThis section provides information for using NMM in an Exchange Server environment,for example supported backup and recovery types, VSS writers, and compatibility withprevious Exchange backups.

Exchange Server 2010 VSS WritersExchange Server 2010 has two writers for active and passive databases. NMM usesthese writers during backup and recovery. The following table provides details.

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

Applicationwriters

Description

Information StoreWriter

This writer is built into the Exchange Information Store, is available onany mailbox server, and is responsible for backup and recovery ofactive databases.

Replication ServiceWriter

This writer is built into the Replication Service. The ReplicationService Writer is available on the passive node of DAGs.

The Replication Service Writer supports backup functionality for aselected database where the shadow copy is taken against thereplicated instance of the database and transaction log files. You canuse the Information Store Writer to restore Replication Writerbackups to the active database location.

Exchange Server 2013 and 2016 VSS WriterExchange Server 2013 and 2016 have one writer for active and passive databases:Microsoft Exchange Server Writer. NMM uses the Microsoft Exchange Server Writerduring backup and recovery. This writer is used by Exchange Server-aware VSS-basedapplications to backup active and passive database copies, and to restore backed updatabase copies. Although this new writer runs in the Microsoft Exchange Replicationservice, it requires the Microsoft Exchange Information Store service to be running inorder for the writer to be advertised. As a result, both services are required to backupor restore Exchange Server databases.

Compatibility with previous Exchange backupsTo perform recovery from NMM version 8.2.x or earlier, select the Restore of NMM8.2.x and Earlier Backups (VSS workflows) option in the NMM installer. The EMCNetWorker Module for Microsoft Installation Guide provides more information.

NME uses VDI technology and NMM uses VSS technology. As a result, you cannotdirectly recover data from an NetWorker Module for Exchange (NME) backup by

Introduction


using NMM. If you have upgraded to NMM from NME, perform a full backup of theExchange Server by using NMM to perform point-in-time recovery in the future.

Note

To ensure successful recovery, EMC recommends that you perform a full backupbefore and after upgrading the Exchange Server, including service pack upgrades.

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

It is the responsibility of the Exchange writer (and hence the Exchange server) totruncate transaction logs. NMM notifies the Exchange writer that a backup hascompleted successfully, which allows the Exchange writer to continue with logtruncation.

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

l In stand-alone configurations, the Exchange Writer truncates the transaction logfiles at 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 thepassive database copies checkpoint has passed the log files to be deleted.

Backup types and levelsThe Exchange Server block based backup is the default and only method to back up anExchange Server by using NMM.

NMM uses NetWorker block based backup technology to perform backups of stand-alone and DAG Exchange environments. NetWorker block based technology trackschanged blocks of the Exchange database and log files. When a level incrementalbackup is started, only the changed blocks are backed up. When a level full backup isstarted, each selected Exchange database and log files are backed up.

The following table provides information about NetWorker backup levels and theresulting backup levels for Exchange Server backups:

Table 4 Exchange backup types and levels

Target devicetype

Supported backup levels Resulting save set level

Data Domaindevice

Full Full

Incremental Full

AFTD Full Full

Incremental Incremental

Introduction

Backup-initiated transaction log file truncation 21

Note

Logs only and synthetic incremental backup levels are not supported with Exchangeserver backups.

The EMC NetWorker Module for Microsoft Administration Guide provides more detailsabout backup levels and block based backup.

Federated DAG backupsNMM supports federated backups for Exchange Server DAGs and IP-less DAGs,including stand-alone and public folder databases.

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.

NMM does not support backing up individual mailbox servers within a DAG. You canconfigure the DAG backup to include stand-alone and public folder databases.

Recovery typesNMM supports the following types of recovery:

l Roll-forward recovery

l Point-in-time recovery

l Database recovery to Exchange RDB

l Remote database recovery for Exchange Server DAG

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

l Recovery to alternate mailbox database

l Recovery to alternate Mailbox

l Granular Level Recovery (GLR) to/from RDB

l Granular Level Recovery (GLR) to alternate mailbox

l Granular Lever Recovery (GLR) to PST files

Note

Recovery databases are not supported with Exchange Server 2016. Granular levelrecovery of Exchange Server 2016 is only supported by using EMC® ItemPoint™ forMicrosoft Exchange Server. See the Granular Level Recovery chapter for moreinformation on GLR.

Introduction


CHAPTER 2

Configuration


l Supported Exchange server deployment scenarios and limitations.....................24l NMM Exchange Admin Configuration tool......................................................... 24l MAPI Client and Collaboration Data Objects.......................................................31l Exchange consistency check.............................................................................. 31

Configuration 23

Supported Exchange server deployment scenarios andlimitations

The Microsoft Exchange Server documentation provides a complete and updated listof system requirements and supported configurations for the Exchange server.

The EMC NetWorker Online Software Compatibility Guide, available on the EMC OnlineSupport website, provides the most up-to-date and accurate listing of hardware,operating system, service pack, and application versions that NMM supports.

Supported Exchange Server versionsThe latest EMC NetWorker Online Software Compatibility Guide provides the latestinformation about the versions of Exchange Server and Windows Server that NMMsupports for stand-alone, DAG, and passive/active highly available deployments.

Microsoft Exchange Server and Microsoft SharePoint Server installation onthe same host

Microsoft does not support the installation of Microsoft Exchange Server andMicrosoft SharePoint Server on the same host. So, NMM also does not support thisinstallation.

NMM Exchange Admin Configuration toolThe NMM Exchange Admin Configuration tool enables you to create or reset thepermissions of an account with the necessary privileges to perform backup andrecovery operation on an Exchange Server. After installing NMM, use the tool tocreate an account, modify, validate, and update the existing account privileges.

You can use the NMM Exchange Admin Configuration tool to perform the followingtasks:

l Configure Admin User—Perform one of the following actions:

n Create an NMM Exchange Admin user and configure the permissions that arerequired for Exchange backup and recovery (both database and GLR), and setthe user account in the registry.

n Update an existing Exchange Admin user's permissions that are required forExchange backup and recovery (both database and GLR), and set the NMMExchange administrator account in the registry.

n Set an existing user as an NMM Exchange Admin account in the registry.

l Update Admin Password—Modify the NMM Exchange administrator accountpassword and update the registry.

l Validate an existing Admin—Verify that an existing NMM Exchangeadministrator account is correctly configured.

Configuration


Note

NMM uses the user account that is set in the registry by the NMM Exchange AdminConfiguration tool to perform backup, database, or granular level recovery.

To use NMM Exchange Admin Configuration tool, you must be logged in with DomainAdministrator permissions.

The NMM Exchange Admin Configuration tool runs automatically and you mustconfigure a user directly after installing NMM.

The following figure shows the Exchange administrator configuration tool landingpage.

Figure 4 NMM Exchange Admin Configuration tool

You can use the Exchange NMM Admin Tool to create users, configure existing users,and assign correct permissions to existing users. You can assign a user to theOrganization Management role, or assign them to the EMC NMM Exchange AdminRole group.

If you assign a user to the EMC NMM Exchange Admin Role group, then they areremoved from the Organization Management role. Conversely, if you assign a user tothe Organization Management role, they are removed from the EMC NMM ExchangeAdmin Role group.

The EMC NMM Exchange Admin Role group is not created unless at least one user isconfigured using the tool without Organization Management rights.

NMM Exchange Admin Configuration tool operationsThe NMM Exchange Admin Configuration Tool simplifies the process of configuringsecurity group memberships by ensuring that the user has all the required ActiveDirectory security group memberships and Powershell Management Roles.

To create an NMM Exchange Administrator account, the tool performs the followingsteps:

l Creates an Active Directory user account.

l Creates a custom Exchange security group.

l Adds the user account to the groups listed in the following table.

Table 5 Permissions configured by the Exchange administrator configuration tool

User group Exchange Server role

Security group memberships on NMM Clientcomputer

Local Administrator

Configuration

NMM Exchange Admin Configuration tool 25

Table 5 Permissions configured by the Exchange administrator configuration tool (continued)

User group Exchange Server role

Security group memberships on DomainController

n Backup Operators

n Remote Desktop Users

Exchange Security Group memberships n Exchange Servers

n Organization Management or EMC NMMExchange Admin Roles

n EMC NMM Exchange Admin Rolesincludes:

– Database Copies

– Databases

– Disaster Recovery

– Mailbox Import Export

– Mail Recipient Creation

– Mail Recipients

– View-Only Configuration

– View-Only Recipients

l Assigns the "Mailbox Import Export" management role to the user.

l Creates an Exchange mailbox.

l Assigns Send-As and Receive-As rights.

l Registers the user account for backup and recovery on Exchange servers whereNMM is installed.

Configuring an Admin userYou can configure an Admin user with the NMM Exchange Admin Configuration toolby creating an account, or by using an existing account.

Procedure

1. Click Configure Admin User on the NMM Exchange Admin Configurationwindow.

2. Select one of the following under Action:

l Create new admin—Create an Exchange user account for NMM backupand recovery operations.

l Configure existing user—Use an existing Exchange user account for NMMbackup and recovery operations.

3. Type the User Name and Password.

4. If you are creating an account:

a. Re-type the password in the Confirm Password field.

b. Select the Exchange database the user performs backup and recovery of inthe Database drop-down list.

Configuration


5. (Optional) Select the Assign Organization Management rights checkbox.

Members of the Organization Management role group have permissions tomanage Exchange objects and their properties in the Exchange organization.Members can also delegate role groups and management roles in theorganization.

Note

If you select Assign Organization Management rights, NMM adds the user tothe Organization Management group. The tool does not create an NMMExchange Admin Roles security group.

If you do not select this option and also do not select the Skip Active DirectoryAuthentication option, NMM will create an Active Directory security groupcalled EMC NMM Exchange Admin Roles and add the user to that group.

6. (Optional) Select the Create ContentSubmitters security group checkbox.

This option creates a ContentSubmitters Active Directory security group. Thisoption is unavailable if a ContentSubmitters group is already created in theActive Directory. This option is only available on Exchange Server 2013 and2016.

7. (Optional) If you are configuring an existing user, optionally select the SkipActive Directory Authentication checkbox.

This option skips the Active Directory authentication and authorizationoperations for the user, and only sets the user as the NMM Exchange useraccount in the registry for backup and recovery operations.

Note

This option should be selected when configuring an existing user in a parent andchild domain environment. See the section Example Admin user configurationson page 27 for more information about this configuration.

8. Click Configure to start the configure operation.

The output window shows the status of the operation including any warning orerror messages.

9. To verify that all the configurations are correctly set, run the SystemConfiguration Checker.

Results

The user is assigned permissions to perform backup and restores of the Exchangedatabase. View the configured user in the Members tab in the Properties window ofthe Exchange Servers security group.

Example Admin user configurationsThis section provides examples of configuring an Admin user with the NMM ExchangeAdmin Configuration tool.

Example 1 Configuring or modifying an Admin user with Organization Management rights

Configuration

Configuring an Admin user 27

Example 1 Configuring or modifying an Admin user with Organization Management rights (continued)

The user will be a member of the Organization Management group. The user will notbe a member of the EMC Exchange NMM Admin Roles group.


2. Complete the Configure Admin User page and select the Assign OrganizationManagement rights checkbox.

3. Click Configure.

4. Run the System Configuration Checker to verify that all the configurations arecorrectly set.

Figure 5 Configuring a user with Organization Management rights

Example 2 Configuring or modifying an Admin user without Organization Management rights

Configuration


Example 2 Configuring or modifying an Admin user without Organization Managementrights (continued)

The user will be a member of the EMC Exchange NMM Admin Roles group. The userwill not be a member of the Organization Management group.


2. Complete the Configure Admin User page. Ensure that the Assign OrganizationManagement rights checkbox is not selected.

3. Click Configure.


Figure 6 Configuring a user without Organization Management rights

Example 3 Configuring an existing user in a parent and child domain environment

Configuration

Configuring an Admin user 29

Example 3 Configuring an existing user in a parent and child domain environment

The NMM Exchange Admin Configuration Tool fails to create a new user object orconfigure an existing user object in a parent and child domain configuration. You mustuse the following steps for this configuration.

1. Configure the user manually in Active Directory, and ensure that the user has theappropriate roles and rights, as described in NMM Exchange Admin Configurationtool on page 24.


3. In the Configure Admin User page, select the Configure Existing User option,enter the User Name and Password, and select the Skip Active DirectoryAuthentication option.


Validating an existing Admin

Note

Validating an existing Admin user in a parent and child domain environment may failbecause the tool may try to contact Active Directory to validate credentials fromregistry.

Procedure

1. Click Validate an existing Admin on the NMM Exchange AdminConfiguration window.

2. Type the User Name and Password.

3. Click Validate.

A window opens listing the Exchange servers in your environment.

4. Select each server that the user must perform backup or recovery of and clickOK.

The window closes and the validate operation starts. The output window showsthe status of the operation including any warning or error messages.

Results

The output window shows the results of the validate Admin operation.

Configuration


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

NMM also supports GLR of Exchange Servers by using EMC ItemPoint® for MicrosoftExchange Server. EMC recommends using ItemPoint for Microsoft Exchange Serverfor GLR instead of performing GLR through the NMM UI. See the section "Exchangeserver GLR using ItemPoint" in the EMC NetWorker Module for Microsoft for ExchangeVSS User Guide for the required Outlook version. MAPI is not required for GLR byusing EMC ItemPoint for Microsoft Exchange Server.

MAPI and Outlook cannot be installed on the same host.

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

GLR of Exchange Server 2016 is onlysupported through EMC ItemPoint forMicrosoft Exchange Server.

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 consistency checkExchange consistency checks improve the quality and performance of a backup.

The Exchange consistency check verifies that the database and its corresponding setof transaction logs do not contain errors (such as on-disk data corruption), andvalidates the Exchange backup is viable and can be restored. A consistency check canbe configured to check the database and log files, database files only, or log files only.While a consistency check of only the database does not ensure complete consistencyof the backup, it does offer the advantage of a shorter time to perform a consistencycheck.

Configuration

MAPI Client and Collaboration Data Objects 31

Consistency check parameters for threading and throttlingThis topic describes the effects of the Exchange consistency check on the NetWorkerbackup performance.

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 databasesin parallel.

NMM provides throttling parameters to govern the usage of system resources duringconsistency check. Set the throttle limits according to the setup. The default value is1000 ms. Running simultaneous consistency checks without correctly setting thethrottle limits affects the performance of the Exchange Server. In extreme cases, younotice that the I/O bottlenecks are so severe that consistency checks fail and othersystem operations are adversely affected.

You can configure threading and throttling by using the corresponding attribute valuesfrom the following table, in the Application Information field of the NMM client. Youcan use these values to prevent performance issues during backup.

Table 7 Exchange application information variables for threading and throttling

Attribute name Description Default and valid values

NSR_ESE_UTIL_SEQUENTIAL Optional, specifieswhether to run Eseutil inparallel against multiplestorage groups (multi-threaded) or sequentially(single threaded).

l False (default)—To run

eseutil in parallel

against multiple storagegroups (multi-threaded)with a default maximumof 4 parallel threads.

l True—To run eseutilsequentially (singlethreaded).

l number_of_threads—

To specify the number ofparallel threads to use.For example:NSR_ESE_UTIL_SEQUENTIAL=6

NSR_ESE_UTIL_THROTTLE Optional, specifieswhether to allowthrottling.

l False (default)—To

prevent eseutilthrottling, ignoring allother throttlingparameters.

l True—To allow

eseutil throttling.

NSR_ESE_THROTTLE_IOS Optional, specifies thenumber of I/Os betweenpauses when throttling.This attribute is useful tolimit disk utilization.

l Undefined (default)—Thedefault value is 100.

l Valid defined values are inthe range between 100–10000. For example:

Configuration


Table 7 Exchange application information variables for threading and throttling (continued)


NSR_ESE_THROTTLE_IOS=500

NSR_ESE_THROTTLE_DURATION Optional, specifies theduration of pause inmilliseconds whenthrottling. This attributeis useful to limit CPUutilization.

l Undefined (default)—Thedefault value is 1000.

l Valid defined values are inthe range between 1000–60000.

NSR_ESE_CC_METHOD Optional, specifieswhether to perform theconsistency check on thedatabase and log filesonly, database file only,or log files only.

l DB_AND_LOGS (default)

l DB_ONLYl LOGS_ONLY

Configuration

Consistency check parameters for threading and throttling 33

Configuration


CHAPTER 3

Backup


l Planning backups............................................................................................... 36l Roadmap of configuring Exchange backups....................................................... 37l Configuring backups of a stand-alone server..................................................... 39l Configuring federated backups of a DAG........................................................... 45l Configuring NetWorker privileges...................................................................... 70l Modifying a client resource by using the Client Properties window after

upgrading from NMM version 8.2.x or earlier......................................................71l Verifying a backup..............................................................................................72

Backup 35

Planning backupsThis section helps you to plan an Exchange backup.

Backup considerationsConsider the following information when you perform Exchange Server backups:

l In a stand-alone environment, schedule backups by using the FQDN or hostnameof the NetWorker client computer.

l In a traditional DAG environment with an IP, schedule federated backups by usingthe DAG name.

l In an IP-less DAG environment, schedule federated backups by using a physicalmailbox server in the DAG.

l You cannot interrupt or halt the Exchange backup process.For example, in Exchange backup, the nsrnmmsv.exe process on the productionserver and the Eseutil process on the proxy resource might continue to run afteryou halt the backup. If you try to stop the backup in NMC may take a long time tocomplete.

l NMM only backs up mounted databases. If any databases are unmounted, NMMdoes not display notifications during the backup operation but the backupoperation will be reported as successful. The NMM log files provide details aboutunmounted databases.

Exchange backup prerequisitesEnsure that you meet the following prerequisites before you perform backupprocedures:

l Install the required .NET Framework version. The EMC NetWorker Module forMicrosoft Release Notes provides more information about the required .NETFramework version.

l Install the hotfixes and cumulative updates.

l When configuring backup and recovery of a DAG, ensure that each DAG node usesthe same version of Exchange Servers, Windows Servers, and service packs orcumulative updates.

l Install the NetWorker client and NMM software on all Exchange servers beingbacked up.

Circumstances that promote incremental or subsequent backups to fullbackup

Incremental or subsequent backups promote to block based backup level full duringthe following circumstances:

l NMM cannot find a full backup for the database within the specified save set.

l You add a Mailbox database to an existing save set.

l NMM detects log gaps between the last backup and the current set of logs.For example, there are gaps between highest log number retrieved from index andthe lowest log number retrieved from the disk.

Backup


l You change the database or the logs path after the last full backup.

l You reinstall NMM.

l You restart the backup client (Exchange Server).

l You expand the disk size, where an Exchange mailbox database resides.

Roadmap of configuring Exchange backupsTo perform an Exchange Server backup, complete the following tasks:

1. Configure the backup storage resources.

2. Review the Exchange Server backup options described in Backup configurationoptions on page 37.

3. Configure one or more client resources for each client by using either the ClientBackup Configuration Wizard or the Client Properties dialog box.

4. Configure a data protection policy for scheduled backups, including a group,policy, policy workflow, and backup action.

Note

If you are using NetWorker server 8.2.3, configure a regular NetWorker backupgroup instead of configuring a data protection policy. Do not enable the Snapshotoption.

5. Configure privileges as described in Configuring NetWorker administratorprivileges.

The EMC NetWorker Module for Microsoft Administration Guide and the EMC NetWorkerAdministration Guide provide details on how to perform these tasks.

Backup configuration optionsThis section describes the backup configuration options for Exchange Server backupsbased on the environment.

Backup using the Client Direct featureNMM supports the Client Direct feature, which enables client backups to bypass theNetWorker storage node and perform one of the following operations:

l Send deduplicated backup data directly to Data Domain Boost (DD Boost™)devices.

l Send backup data directly to advanced file type device (AFTD).

The Client Direct feature, also known as direct file access or DFA, reduces bandwidthusage and bottlenecks at the storage node, and provides highly efficient transmissionof backup data. Client Direct is the default and preferred backup method. If an NMMbackup cannot use the Client Direct feature due to the permissions or accessibility tothe target device, the backup uses the storage node instead. For NMM 9.0 and higher,if an NMM backup cannot use the Client Direct feature, the backup will fail.

Backup

Roadmap of configuring Exchange backups 37

Note

NMM does not support dedicated storage nodes in a DAG environment when usingNMM 9.0.1 with a NetWorker 8.2.3 server. Select No for the Dedicated storage nodeoption in the Device properties dialog box when configuring the storage node in aDAG environment. Refer to "Configuring backups to use a remote storage node in aDAG environment" for information about how to use a remote storage node in a DAGenvironment.

Only active databases backup on the serverYou can back up all the active database copies residing on an Exchange Server mailboxserver in a DAG environment. You can perform full and incremental backups. Activenode backups include stand-alone servers, public folder mailboxes (Exchange Server2013 and 2016), and public folder databases (Exchange Server 2010).

Only passive databases backup on the serverYou can back up all the passive database copies residing on an Exchange Servermailbox server in a DAG environment. You can perform full and incremental backups,including incremental backups of public folders. Passive node backups do not includepublic folder mailboxes or public folder databases.

Both active and passive databases backup on the serverYou can back up both active and passive databases on Exchange Server mailboxservers in the DAG environment. You can perform both full and incremental backups.

Backup to a local storage node in a stand-alone environmentYou can configure a client to direct its backups to the local storage node on thephysical host on which it resides. To configure a stand-alone client, type curphyhostin the Storage Nodes attribute of the stand-alone client. This variable is not supportedfor DAG environments. The EMC NetWorker Cluster Integration Guide provides moreinformation about the curphyhost command.

Backup to a remote storage node in a DAG or stand-alone environmentYou can perform Exchange Server database backups by using a remote NetWorkerstorage node. You can perform both full and incremental backups.

Note

You cannot configure a dedicated storage node between a NetWorker 8.2.3 serverand NetWorker 9.0 and later storage node. NMM does not support dedicated storagenodes in a DAG environment when using NMM 9.0.1 with a NetWorker 8.2.3 server.Select No for the Dedicated storage node option in the Device properties dialog boxwhen configuring the storage node in a DAG environment. Refer to "Configuringbackups to use a remote storage node in a DAG environment" for information abouthow to use a remote storage node in a DAG environment.

Backup


Configuring backups of a stand-alone serverYou can configure a backup of a stand-alone server by using the Client BackupConfiguration wizard or by using the Client Properties window.

By using the Client Backup Configuration wizardTo use the Client Backup Configuration wizard, you must first install the NMM clienton the Exchange server and run the NMM Exchange administration configuration tool.

Note

If you are using NetWorker server 8.2.3 or later and NMM 9.0.1:

l Configure a regular NetWorker backup group instead of configuring a dataprotection policy. Do not enable the Snapshot option.

l Ensure that JRE 8 is installed on the system where NMC is used for the ClientBackup Configuration wizard to function properly. While the NetWorkerManagement Console (NMC) for NetWorker 8.2.3 and later is compiled with JRE7, NMM 9.0.1 Java plugin for NMC is compiled with JRE 8.

l If you are using an advanced file type device (AFTD) with NetWorker server 8.2.3,ensure that the Block based backup checkbox is cleared in the client resource. Ifyou do not clear this setting, incremental backups are promoted to level full.

l The procedure used to create a client resource when using NetWorker server 8.2.3and later is different from the procedure used to create a client resource whenusing NetWorker server 9.0.1. Follow the procedure provided in the ScheduledBackup chapter of each application user guide.

l Prior to running the NMM 9.0.1 Client Backup Configuration wizard to modify aclient resource that was created by using NMM 8.2.x, ensure that the Snapshotattribute of the NetWorker group that this client resource belongs to is clear. Ifthe Snapshot attribute is left selected, the NetWorker group cannot be selected inthe wizard and you are prompted to create or select another group.

Note

This requirement does not apply to SQL Server VDI and Active Directory.

Procedure

1. Open NMC and launch the EMC NetWorker Administration UI.

2. On the left navigation pane of the Protection tab, right-click Clients and selectNew Client Wizard.

Backup

Configuring backups of a stand-alone server 39

Figure 7 Initial view of the Client Backup Configuration wizard

3. On the Specify Client Information page:

a. In the Client Name field, type one of the following:

l The FQDN of the NetWorker client computer.

l The hostname of the NetWorker client computer.

b. Optionally, in the Comment field, type a description of the client.

c. Optionally, in the Tag field, type one or more tags to identify this clientresource for the creation of dynamic client groups for data protectionpolicies. Place each entry on a separate line.

d. Optionally, in the Group field, select a group to assign the client resource to.

The group to which the client belongs determines the workflow that is usedto back up the client.

e. In the Type box, select Traditional.

f. Click Next.

4. On the Specify the Backup Configuration Type page, select MicrosoftExchange Server, and then click Next.

5. Specify client properties on the Select the NetWorker Client Properties pageand click Next:

l Priority—Enables you to control the order in which the NetWorker servercontacts clients for backup.

l Parallelism—Specifies the maximum number of data streams that a clientcan send simultaneously during a backup action.

Backup


l Remote Access—Specifies a list of the users that have access to performremote access operations.

l Data Domain Interface—Specifies the protocol to use if you send thebackup data to a Data Domain Device. Available selections are IP, FiberChannel, or Both.

l Block based backup (BBB)—Enables Block Based Backups for the host.This option is selected by default. You cannot clear this option as it is grayedout for Exchange client resources.

l Client direct—Allows the client to attempt to directly connect to thebackup storage device, instead of connecting to a NetWorker storage node.This option is selected by default. You cannot clear this option as it is grayedout for Exchange client resources.

6. On the Select the Exchange Server Objects page, verify that the databases toback up are selected, and then click Next.

By default, all the databases are selected for the entire server backup. Clear thecheckbox for any items that must be excluded from the backup.

7. The Specify Federated Exchange Backup Options page appears. In theConsistency Check Options group, enable consistency checks by selecting thePerform a consistency check during backup option and configure thefollowing settings:

a. To validate Exchange databases and logs, databases only, or logs only, selectthe Perform database consistency check during backup option.

In a stand-alone environment, this option is selected by default.

b. To validate the Exchange files sequentially instead of in parallel, select theSequential consistency check option.

c. To manage the performance of the Consistency Check operation, select theThrottle Consistency Check option and then choose the Throttle I/OOperations and Throttle Duration options.

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.

8. On the Client Configuration Summary page, review the details and do one ofthe following:

l Click Back to revisit the previous pages.

l Click Create to configure the client resources.

9. On the Check Results page, review the output of the Client BackupConfiguration wizard, and click Finish.

Results

The client resource appears in the Clients window pane.

Backup

By using the Client Backup Configuration wizard 41

By using the Client Properties windowThis section describes configuring a client resource for a stand-alone server by usingthe Client Properties window in the NMC.

Note

The procedure used to create a client resource when using NetWorker server 8.2.3 isdifferent from the procedure used to create a client resource when using NetWorkerserver 9.0.1. Follow the procedure provided in the "Creating a client resource forExchange backups by using the NetWorker Management Console" section in the EMCNetWorker Module for Microsoft for Exchange Server VSS Release 8.2 SP1 User Guidewhen using NetWorker server 8.2.3. Keep the following considerations in mind whenfollowing the NMM 8.2 SP1 procedure:



l Type nsrnmmsv.exe in the Backup Command field.

Procedure

1. In the Administration view of the NetWorker Management Console, select theProtection tab.

2. In the expanded left pane, select Clients.

3. From the File menu, select New.

4. In the General tab:

a. In the Name attribute, type one of the following:

l The FQDN of the NetWorker client computer.

l The hostname of the NetWorker client computer.

b. In the Comment attribute, type a description.

c. Ensure that the Block based backup option is selected.

d. Determine a list of save sets that must be included in the backup.

To display a list of the application data save sets that are available forbackup, open a command prompt on the Exchange server and type thefollowing command. Before using this command, use the NMM Exchangeadministrator configuration tool to create an NMM Exchange administratoraccount.

nsrnmmsv -PThe following is example output:

“APPLICATIONS:\Microsoft Exchange 2010”“APPLICATIONS:\Microsoft Exchange 2010\DB1”“APPLICATIONS:\Microsoft Exchange 2010\DB2”“APPLICATIONS:\Microsoft Exchange 2010\DB3”“APPLICATIONS:\Microsoft Exchange 2010\DB4”

Backup


“APPLICATIONS:\Microsoft Exchange 2010\DB5”The output contains all databases in the DAG. The -v option is notsupported for DAGs. Each line of output corresponds to a save set entrythat you can add to the save set attribute of a client resource. Type eachentry on a separate line.

Note

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

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

The following table provides the list of Exchange Server 2010 save sets forapplication data.

Table 8 Exchange Server 2010 save set names

Type of backup data Save set syntax

Writer level APPLICATIONS:\MicrosoftExchange 2010

Database name level APPLICATIONS:\MicrosoftExchange 2010\<Database name>











When specifying save set names in the Save Set attribute of the clientresource, you must specify some special characters, such as the backwardslash (\), by their URL-encoded values.

The following table lists the most commonly used special characters andtheir URL values.

Backup

By using the Client Properties window 43

Table 11 Special characters and their URL-encoded values

Specialcharacter

URL-encodedvalue

Specialcharacter

URL-encodedvalue

\ %5C ? %3F

/ %2F ] %5D

" %22 [ %5B

% %25 } %7D

# %23 { %7B

& %26 ^ %5E

< %3C ‘ %60

> %3E | %7C

f. Select the appropriate option in the Protection group list field.

5. Click the Apps & Modules tab and do the following:

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

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

nsrnmmsv.exe

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

The following table provides the application variables and values for theExchange Server environment.

Table 12 Exchange Application Information attribute settings


NSR_EXCH_CHECK=value

Optional, to specifyif a consistencycheck should be runfor databases.

l Yes—Run a consistency check. This is

the default value for Exchange Serverstand-alone backups.

l No—Do not run a consistency check.

If the value is no, NMM indicates that the

consistency check is skipped in thebackup log.

NSR_EXCH_BACKUP=active/passive/preferred/ all

Optional, to back upactive, passive,preferred, or all thedatabase copies.The default settingis preferred.

l Preferred (default)—Back up onlypassive copy or replica of eachdatabase if one is available. If nopassive database exists, then theactive database is backed up.

l Active—Back up only active databasecopies.

Backup


Table 12 Exchange Application Information attribute settings (continued)


l Passive—Back up only passivedatabase copies.

l All—Back up both active and passivedatabases.

NSR_EXCLUDE_COMPONENTS=db1,db2…

Optional, excludesspecified databasesfrom backup

l Undefined (default).

l To exclude databases, type a comma-separates list of the database namesto exclude from the backup.

The following are examples of application variables:

l NSR_ESE_UTIL_SEQUENTIAL=<True/False>l NSR_EXCH_CHECK=<yes/no>l NSR_ESE_UTIL_THROTTLE=<True/False>

6. Ensure that the Client Direct featured is enabled.

Exchange backups require Client Direct.

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

8. If you are using a NetWorker storage node that is different from the NetWokerserver, when configuring a client resource for the Exchange Server, click theGlobals (2 of 2) tab and type the storage node name in the Storage nodename field.

9. Click OK.

Results

The client resource appears in the Clients window pane of NMC.

Configuring federated backups of a DAGThis section describes how to configure and perform federated DAG backups.

NMM supports backup configurations of IP DAG (with an administrative access point)and IP-less DAG (with no administrative access point).

Performing backups in a DAG environmentIn a highly available DAG environment, you can schedule the federated backups byusing the DAG name or the DAG node name as the client instance.

To backup an IP-less DAG, use a physical mailbox server in the DAG to configure aclient resource, then add the DAG short name and FQDN as an alias to the clientresource. Use this client to schedule federated backups of the IP-less DAG.

Backup

Configuring federated backups of a DAG 45

When backing up active or passive database copies in the Exchange DAGenvironment, all DAGs use the federated backup method to best handle fail overscenarios. The federated backup method provides the following benefits:

l Allows backups of passive database copies to continue even when the passivedatabase copies move among Exchange servers.

l Enables you to back up all DAG members, including stand-alone and public foldermailbox databases, with a single save set without running a separate backup ofeach node. Each Exchange server for which a backup job is sent performs theirbackups in parallel with the other Exchange servers, resulting in faster backups.

Preferred server order listWhen you perform a backup through the DAG resource using NSR_EXCH_BACKUP setto 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 from the Exchange Servers that are listed in the PSOL parameter. Youcreate the PSOL parameter in the Client Configuration wizard, and the PSOLparameter is associated with a single DAG client resource.

If stand-alone databases (including public folder databases or public folder mailboxes)reside in the DAG, the coordinating node determines whether they exist on that serverand, if so, adds them to the save set list. The coordinating node then goes to anotherserver in the list and repeats the check for passive and stand-alone databases. Duringthis process, the node skips databases that are already listed.

Once the coordinating node has gone through the list of servers, then it validates thatthere are no databases within the DAG that have been left out of the list of save sets.Then the coordinating node starts the backup on each of the servers identified.

If you want to exclude stand-alone databases (including public folder databases orpublic folder mailboxes) from the backup, you must set the NSR_EXCH_INCL_SAparameter to false. Refer to the section "Exchange Server Application Informationattributes" for more information about setting the NSR_EXCH_INCL_SA parameter.

Configuring federated backups of a DAG with an IPYou can configure backups of a DAG with an IP (administrative access point) by usingthe Client Backup Configuration wizard or by using the Client Properties window.

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

The physical client resources should have the Scheduled backup checkbox cleared.

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. Assign the DAG client resource to the policy.

Backup


By using the Client Backup Configuration wizardThis section describes configuring a client resource for a DAG with an IP by using theClient Backup Configuration wizard.

To use the Client Backup Configuration wizard, you must first install the NMM clienton the Exchange server and run the NMM Exchange administration configuration tool.

Note

If using NetWorker server 8.2.3 and NMM 9.0.1:


l Ensure that JRE 8 is installed on the system where NMC is used for the ClientBackup Configuration wizard to function properly. While NetWorker ManagementConsole (NMC) for NetWorker 8.2.3 is compiled with JRE 7, the NMC ClientBackup Configuration wizard for NMM 9.0.1 is compiled with JRE 8 and requiresJRE 8 to run properly.


l This procedure used to create a client resource when using NetWorker server8.2.3 is different from the procedure used to create a client resource when usingNetWorker server 9.0.1. Follow the procedure provided in the "Creating a clientresource by using the Client Backup Configuration wizard" section in the EMCNetWorker Module for Microsoft for Exchange Server VSS Release 8.2 SP1 UserGuide when using NetWorker server 8.2.3.

Procedure



Backup

Configuring federated backups of a DAG with an IP 47



a. In the Client Name field, type the DAG name.






f. Click Next.






Backup







7. On the Specify Federated Exchange Backup Options page:

a. For federated backup client backup configurations, in the Database BackupOptions group, select one of the following:

l Preferred Passive Backup to back up passive or replica copies of thedatabases.If no replica copy is available or healthy for the database, the active copyis backed up.

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

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

l Use Exclude Component List to select which databases to exclude fromthe backup.

Note

When you select Active Backup or Passive Backup, the backup fails if theselected type of database does not exist.The Database Backup Options box is not displayed for Exchange stand-alone servers.

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

a. Select Use Preferred Server Order List to specify the order in which tobackup 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 databases and public folder mailboxes (Exchange Server2013 and 2016), or public folder databases (Exchange Server 2010).By default, the Include Standalone and Public Folder checkbox isselected.

Backup


Note

This option is only supported for federated DAG backup configurations.

c. 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 database consistency check during backup optionto validate Exchange databases and logs, databases only, or logs only.In a stand-alone environment, the option is selected by default. In a DAGenvironment, performing the database consistency check is optional.

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.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. Click Next.





Results

The client resource appears in the Clients window pane.

By using the Client Properties windowThis section describes configuring a client resource for a DAG with an IP by using theClient Properties window in the NMC.

Note





Backup


Procedure





a. In the Name attribute, type the DAG name.




To display a list of the application data save sets that are available forbackup, open a command prompt on the Exchange server and type thefollowing command. Before using the following command, use the NMMExchange administrator configuration tool to create an NMM Exchangeadministrator account.

At the command prompt, type the following on any node in the DAG:

nsrnmmsv -A NSR_FEDERATED_BACKUP=yes -A NSR_EXCH_DAG=<DAGclient> -PThe following is example output:

“APPLICATIONS:\Microsoft Exchange 2010”“APPLICATIONS:\Microsoft Exchange 2010\DB1”“APPLICATIONS:\Microsoft Exchange 2010\DB2”“APPLICATIONS:\Microsoft Exchange 2010\DB3”“APPLICATIONS:\Microsoft Exchange 2010\DB4”“APPLICATIONS:\Microsoft Exchange 2010\DB5”The output contains all databases in the DAG. The -v option is notsupported for DAGs. Each line of output corresponds to a save set entrythat you can add to the save set attribute of a client resource. Type eachentry on a separate line.

Note







Backup


Table 13 Exchange Server 2010 save set names (continued)
















Specialcharacter

URL-encodedvalue

Specialcharacter

URL-encodedvalue

\ %5C ? %3F

/ %2F ] %5D

" %22 [ %5B

% %25 } %7D

# %23 { %7B

& %26 ^ %5E

< %3C ‘ %60

> %3E | %7C

Backup


Table 16 Special characters and their URL-encoded values (continued)





nsrnmmsv.exe

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




NSR_EXCH_CHECK=value Optional, to specify if aconsistency check should berun for databases.

l Yes—Run a consistency check.

l No—Do not run a consistency check. This is the default

value for Exchange Server DAG backups.

If the value is no, NMM indicates that the consistency check

is skipped in the backup log.

NSR_EXCH_DAG=<DAGname>

Optional, to specify the DAGname for a backup in a DAGenvironment.


l FQDN of the DAG.

For example, NSR_EXCH_DAG=mydag.domainname.com

NSR_EXCH_BACKUP=active/passive/preferred/all

Optional, to back up active,passive, preferred, or all thedatabase copies. The defaultsetting is preferred.

l Preferred (default)—Back up only passive copy or replicaof each database if one is available. If no passive databaseexists, then the active database is backed up.

l Active—Back up only active database copies.

l Passive—Back up only passive database copies.

l All—Back up both active and passive databases.


Optional, excludes specifieddatabases from backup.


l To exclude databases, type a comma-separates list of thedatabase names to exclude from the backup.

NSR_EXCH_INCL_SA Optional, includes stand-alonedatabases and public foldermailboxes (Exchange Server2013 and 2016), or publicfolder databases (ExchangeServer 2010) in the backup inthe backup.

l True (default)—Includes stand-alone databases and

public folder mailboxes in the backup.

l False—Excludes stand-alone databases and public folder

mailboxes from the backup.

Backup




NSR_FEDERATED_PSOL Optional, list of the order inwhich to back up thedatabases on each server inthe DAG.

l Undefined (default)—The coordinating node distributesthe backups based on an unordered list of Exchangeservers in the DAG.

l To define a list, type a comma-separated list of the orderin which to back up the databases on each server in theDAG.

NSR_USE_CLIENT_SN_LIST Optional, to backup eachmailbox server in the DAG toa specific storage node, basedon what is specified in the

Storage Node attribute ofeach mailbox server clientresource.

l No (default)—The storage node is assigned according to

the backup policy.

l Yes—The storage node used is obtained from the client

resource for the mailbox server where the secondaryNMM backup process is run.







This is the default value for ExchangeServer DAG backups.



NSR_EXCH_DAG=<DAG name>

Optional, to specifythe DAG name for abackup in a DAGenvironment.


l FQDN of the DAG.

For example,NSR_EXCH_DAG=mydag.domainname.com

NSR_EXCH_BACKUP=active/passive/preferred/ all

Optional, to back upactive, passive,preferred, or all thedatabase copies.The default settingis preferred.

l Preferred (default)—Back up onlypassive copy or replica of eachdatabase if one is available. If nopassive database exists, then theactive database is backed up.




Backup





Optional, excludesspecified databasesfrom backup.



NSR_EXCH_INCL_SA

Optional, includesstand-alonedatabases andpublic foldermailboxes(Exchange Server2013 and 2016), orpublic folderdatabases(Exchange Server2010) in the backupin the backup.

l True (default)—Includes stand-alone

databases and public folder mailboxesin the backup.

l False—Excludes stand-alone

databases and public folder mailboxesfrom the backup.

NSR_FEDERATED_PSOL

Optional, list of theorder in which toback up thedatabases on eachserver in the DAG.

l Undefined (default)—Thecoordinating node distributes thebackups based on an unordered list ofExchange servers in the DAG.

l To define a list, type a comma-separated list of the order in which toback up the databases on each serverin the DAG.

NSR_USE_CLIENT_SN_LIST

Optional, to backupeach mailbox serverin the DAG to aspecific storagenode, based onwhat is specified in

the Storage Nodeattribute of eachmailbox serverclient resource.

l No (default)—The storage node is

assigned according to the backuppolicy.

l Yes—The storage node used is

obtained from the client resource forthe mailbox server where thesecondary NMM backup process isrun.

Table 19 Examples for application variables

Configuration Examples for application variables

Exchange ServerDAG backups

l NSR_FEDERATED_BACKUP=<yes>l NSR_FEDERATED_PSOL=<DAG Node1>,<DAG

node2>,<DAG NodeN>

l NSR_EXCH_INCL_SA=<TRUE/FALSE>l NSR_EXCH_DAG=<DAG FQDN>l NSR_EXCH_CHECK=<yes/no>

Backup


Table 19 Examples for application variables (continued)


l NSR_ESE_UTIL_SEQUENTIAL=<True/False>l NSR_ESE_UTIL_THROTTLE=<True/False>l NSR_ESE_CC_METHOD=<db_and_logs/db_only/

logs_only>

Exchange Serverfederated DAGbackups

l NSR_EXCH_DAG=<dagname>l NSR_FEDERATED_BACKUP=yesl NSR_FEDERATED_PSOL=<List of the order>l NSR_EXCH_INCL_SA=<True/False>l NSR_EXCH_BACKUP=<active/passive/preferred/all>l NSR_EXCLUDE_COMPONENTS=<db1,db2… >







9. Click OK.

10. Create additional client resources for each physical mailbox server in the DAG:

a. In the Administration view of the NetWorker Management Console, selectthe Protection tab.

b. In the expanded left pane, select Clients.

c. From the File menu, select New.

d. In the Name attribute, type the Exchange server name or FQDN.

e. In the Comment attribute, type a description.

Use this attribute to differentiate the purpose of the resource for eachmailbox server.

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

g. Confirm that the Scheduled Backups field is selected.

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

This is all the configuration needed for the clients within the DAG.

Backup


Configuring federated backups of an IP-less DAGYou can configure backups of an IP-less DAG (with no administrative access point) byusing the Client Backup Configuration wizard or by using the Client Propertieswindow.

Consider the following before configuring a backup of an IP-less DAG:

l Exchange 2013 SP1 and later supports IP-less DAG.

l Exchange 2016 defaults to IP-less DAG.

l IP-less DAG requires Windows Server 2012 R2 or later.

l An existing DAG (IP-based) cannot be converted to an IP-less DAG.

By using the Client Backup Configuration wizardThis section describes configuring a client resource for an IP-less DAG by using theClient Backup Configuration wizard.

Note

For stand-alone databases that are part of an IP-less DAG, use the Client Propertieswindow to configure the backup. You cannot use the configuration wizard to configurestand-alone databases in an IP-less DAG.

To use the Client Backup Configuration wizard, first install the NMM client on theExchange server and run the NMM Exchange administration configuration tool.

Note



l Ensure that JRE 8 is installed on the system where NMC is used for the ClientBackup Configuration wizard to function properly. While NetWorker ManagementConsole (NMC) for NetWorker 8.2.3 is compiled with JRE 7, the NMC ClientBackup Configuration wizard for NMM 9.0.1 is compiled with JRE 8 and requiresJRE 8 to run properly.


l This procedure used to create a client resource when using NetWorker server8.2.3 is different from the procedure used to create a client resource when usingNetWorker server 9.0.1. Follow the procedure provided in the "Creating a clientresource by using the Client Backup Configuration wizard" section in the EMCNetWorker Module for Microsoft for Exchange Server VSS Release 8.2 SP1 UserGuide when using NetWorker server 8.2.3.

Procedure



Backup

Configuring federated backups of an IP-less DAG 57



a. In the Client Name field, type the FQDN or hostname of a physical servernode in the DAG that will be used as the access point.






f. Click Next.






Backup







7. On the Specify Federated Exchange Backup Options page:

a. For federated backup client backup configurations, in the Database BackupOptions group, select one of the following:

l Preferred Passive Backup to back up passive or replica copies of thedatabases.If no replica copy is available or healthy for the database, the active copyis backed up.

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

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

l Use Exclude Component List to select which databases to exclude fromthe backup.

Note

When you select Active Backup or Passive Backup, the backup fails if theselected type of database does not exist.The Database Backup Options box is not displayed for Exchange stand-alone servers.

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

a. Select Use Preferred Server Order List to specify the order in which tobackup 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 databases and public folder mailboxes (Exchange Server2013 and 2016), or public folder databases (Exchange Server 2010).By default, the Include Standalone and Public Folder checkbox isselected.

Backup


Note

This option is only supported for federated DAG backup configurations.

c. 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 database consistency check during backup optionto validate Exchange databases and logs, databases only, or logs only.In a stand-alone environment, the option is selected by default. In a DAGenvironment, performing the database consistency check is optional.

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.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. Click Next.





10. Open the Protection tab of the Administration window in NMC.

11. Locate the newly created client from the navigation tree or right-click the clientin the Clients table, and open the Client Properties window.

12. On the Globals (1 of 2) tab, type the DAG name into the Aliases attribute ofthe client resource.

Include both the short name and full name of the DAG. For example, ifbuexch13.net is the domain name and DAG2 is the DAG name, type both DAG2and DAG2.buexch13.net.

Backup


Figure 10 Adding the DAG name as an alias to a client resource

This step ensures that NetWorker recognizes that the IP-less DAG name is analias of the chosen physical mailbox server.

Note

Once the DAG name is added as an alias to a client, do not remove the alias oradd the DAG name to another client resource. If the DAG node configured asthe client resource is unavailable and you must configure a new client, you arenot required to add the DAG name as an alias to the new client.

13. Click OK to close the Client Properties window.

14. Assign the client resource to a backup group.

Results

You can use the client resource to perform federated backups of the IP-less DAG.

Backup


By using the Client Properties windowThis section describes configuring a client resource for an IP-less DAG by using theClient Properties window in the NMC.

Note





Procedure





a. In the Name attribute, type the FQDN or hostname of a physical server nodein the DAG that will be used as the access point.




To display a list of the application data save sets that are available forbackup, open a command prompt on the Exchange server and type thefollowing command. Before using the following command, use the NMMExchange administrator configuration tool to create an NMM Exchangeadministrator account.

At the command prompt, type the following on any node in the DAG:

nsrnmmsv -A NSR_FEDERATED_BACKUP=yes -A NSR_EXCH_DAG=<DAGclient> -PThe following is example output:

“APPLICATIONS:\Microsoft Exchange 2010”“APPLICATIONS:\Microsoft Exchange 2010\DB1”“APPLICATIONS:\Microsoft Exchange 2010\DB2”“APPLICATIONS:\Microsoft Exchange 2010\DB3”“APPLICATIONS:\Microsoft Exchange 2010\DB4”

Backup


“APPLICATIONS:\Microsoft Exchange 2010\DB5”The output contains all databases in the DAG. The -v option is notsupported for DAGs. Each line of output corresponds to a save set entrythat you can add to the save set attribute of a client resource. Type eachentry on a separate line.

Note




















Backup



Specialcharacter

URL-encodedvalue

Specialcharacter

URL-encodedvalue

\ %5C ? %3F

/ %2F ] %5D

" %22 [ %5B

% %25 } %7D

# %23 { %7B

& %26 ^ %5E

< %3C ‘ %60

> %3E | %7C





nsrnmmsv.exe

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








This is the default value for ExchangeServer DAG backups.



NSR_EXCH_DAG=<DAG name>

Optional, to specifythe DAG name for abackup in a DAGenvironment.


l FQDN of the DAG.

For example,NSR_EXCH_DAG=mydag.domainname.com

NSR_EXCH_BACKUP=active/

Optional, to back upactive, passive,

l Preferred (default)—Back up onlypassive copy or replica of each

Backup




passive/preferred/ all

preferred, or all thedatabase copies.The default settingis preferred.

database if one is available. If nopassive database exists, then theactive database is backed up.





Optional, excludesspecified databasesfrom backup.



NSR_EXCH_INCL_SA

Optional, includesstand-alonedatabases andpublic foldermailboxes(Exchange Server2013 and 2016), orpublic folderdatabases(Exchange Server2010) in the backupin the backup.

l True (default)—Includes stand-alone

databases and public folder mailboxesin the backup.

l False—Excludes stand-alone

databases and public folder mailboxesfrom the backup.

NSR_FEDERATED_PSOL

Optional, list of theorder in which toback up thedatabases on eachserver in the DAG.

l Undefined (default)—Thecoordinating node distributes thebackups based on an unordered list ofExchange servers in the DAG.

l To define a list, type a comma-separated list of the order in which toback up the databases on each serverin the DAG.

NSR_USE_CLIENT_SN_LIST

Optional, to backupeach mailbox serverin the DAG to aspecific storagenode, based onwhat is specified in

the Storage Nodeattribute of eachmailbox serverclient resource.

l No (default)—The storage node is

assigned according to the backuppolicy.

l Yes—The storage node used is

obtained from the client resource forthe mailbox server where thesecondary NMM backup process isrun.

Backup


Table 25 Examples for application variables


Exchange ServerDAG backups

l NSR_FEDERATED_BACKUP=<yes>l NSR_FEDERATED_PSOL=<DAG Node1>,<DAG

node2>,<DAG NodeN>

l NSR_EXCH_INCL_SA=<TRUE/FALSE>l NSR_EXCH_DAG=<DAG FQDN>l NSR_EXCH_CHECK=<yes/no>l NSR_ESE_UTIL_SEQUENTIAL=<True/False>l NSR_ESE_UTIL_THROTTLE=<True/False>l NSR_ESE_CC_METHOD=<db_and_logs/db_only/

logs_only>

Exchange Serverfederated DAGbackups

l NSR_EXCH_DAG=<dagname>l NSR_FEDERATED_BACKUP=yesl NSR_FEDERATED_PSOL=<List of the order>l NSR_EXCH_INCL_SA=<True/False>l NSR_EXCH_BACKUP=<active/passive/preferred/all>l NSR_EXCLUDE_COMPONENTS=<db1,db2… >






8. On the Globals (1 of 2) tab, type the DAG name into the Aliases attribute ofthe client resource.

Include both the short name and full name of the DAG. For example, ifbuexch13.net is the domain name and DAG2 is the DAG name, type both DAG2and DAG2.buexch13.net.

Backup


Figure 11 Adding the DAG name as an alias to a client resource

This step ensures that NetWorker recognizes that the IP-less DAG name is analias of the chosen physical mailbox server.

Note

Once the DAG name is added as an alias to a client, do not remove the alias oradd the DAG name to another client resource. If the DAG node configured asthe client resource is unavailable and you must configure a new client, you arenot required to add the DAG name as an alias to the new client.


10. Click OK.

11. Create additional client resources for each physical mailbox server in the DAG:

a. In the Administration view of the NetWorker Management Console, selectthe Protection tab.

b. In the expanded left pane, select Clients.

c. From the File menu, select New.

d. In the Name attribute, type the Exchange server name or FQDN.

e. In the Comment attribute, type a description.

Use this attribute to differentiate the purpose of the resource for eachmailbox server.

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

Backup


g. Confirm that the Scheduled Backups field is selected.

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

This is all the configuration needed for the clients within the DAG.

Reconfiguring an IP-less DAG backup to a different nodeIf the DAG node that is configured as the client resource is unavailable, the backupfails and you must configure a new client resource. If you are reconfiguring an IP-lessDAG client resource, there are additional steps you must follow.

Procedure

1. Reconfigure a new client resource from an available physical mailbox serverwithin the DAG.

2. Remove the old DAG client resource from the backup group.

3. Add the new DAG client resource to the backup group.

Note

Do not delete the old client resource. Do not remove the DAG alias from the oldclient resource.

Configuring backups to use a remote storage node in a DAG environmentThis topic describes the steps for configuring remote storage in an Exchange DAGenvironment. This procedure allows you to specify a storage node for the physicalclients in the DAG, which can differ from the storage node defined in the Policy forthe federated backup.

Note




l This procedure used to create a client resource when using NetWorker server8.2.3 is different from the procedure used to create a client resource when usingNetWorker server 9.0.1. Follow the procedure provided in the "Configuringbackups to use a remote storage node in a DAG environment" section in the EMCNetWorker Module for Microsoft for Exchange Server VSS Release 8.2 SP1 UserGuide when using NetWorker server 8.2.3.

Procedure

1. On each mailbox server to back up, install the NetWorker client software withthe Storage Node option.

2. Open the NMC and create a storage node for each client:

a. On the Devices tab, right-click Storage Nodes and select New.

b. Type the name of the client. For example, node1.domain.com.

Backup


c. Right-click Devices, select New, and create the device for the storage node.

d. Label and mount the storage node device.

3. To configure the client to use the storage node:

a. Right-click Client and select Modify client.

b. On the Globals (2 of 2) tab, type the storage node name in the StorageNodes field. For example, node1.domain.com.

4. For federated backups, also do the following:

a. In the application information parameters for each DAG client resource, addNSR_USE_CLIENT_SN_LIST=yes.

b. Add each physical client to the same group as the DAG client, and mark eachas disabled from the backup (clear the selection the Scheduled Backupcheckbox).

c. Add a name to the Storage Nodes field on each physical client in the DAG.

d. In the data protection policy for the federated backup, ensure the selectedpool contains the storage node that is used for backup.

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

Example of a federated backupThe following figure illustrates an example of a federated backup of a DAG cluster withthree Exchange servers: MBX1, MBX2, and MBX3. The cluster contains four Exchangedatabases: DB1, DB2, DB3, and DB4. Each database can only have one active copy,but can have multiple passive or replica copies. In this example, there are two passivecopies of DB1: one copy is on two different Exchange servers (MBX2 and MBX3). Theother databases (DB2, DB3, and DB4) only have one passive copy each in the cluster.Only one copy of each database must be backed up. The preferred server order listspecifies to back up databases from the DAG in this order: MBX2, MBX3, and MBX1.

The following figure shows an example Exchange Server federated backup.

Backup

Example of a federated backup 69

Figure 12 Example of an Exchange Server federated backup

Configuring NetWorker privilegesNMM requires user group privileges to perform certain operations.

Table 26 User group privileges for NMM operations

Operation Required user group privilege

Federated backup Operate NetWorker

Backup deletion Changed Application Settings

Complete the following steps to configure NetWorker user group privileges manually.

Procedure

1. Open the NetWorker Administration GUI.

2. Click Server.

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

4. Right-click the appropriate user group, and then select Properties.

The Properties dialog box appears.

Backup


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

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

6. Click OK.

7. For DAG backups, configure the user group privilege as described in theprevious steps to the Exchange backup admin and system users on each ofnodes within the DAG.

Modifying a client resource by using the Client Propertieswindow after upgrading from NMM version 8.2.x or earlier

You can edit a client resource by using the Client Backup Configuration wizard or theClient Properties window. When using the Client Backup Configuration Wizard toupgrade an NMM 8.2.x backup configuration for the first time, you must configure anew backup group and remove the prior backup group.

This procedure explains how to use modify a client by using the Client Propertieswindow.

Procedure


2. In the Administration window, click Protection.

3. Select Clients from the navigation tree or right-click the required client in theClients table.

4. Select the Apps & Modules tab from the Client Properties window.

5. Select Modify Client Properties.

6. In the Backup Command field, delete the nsrsnap_vss_save command andtype the nsrnmmsv.exe command. This change must be performed for all theexisting client resources.

7. In the Application Information field, make the following changes:

l If the optional NSR_EXCH2010_BACKUP attribute is set, perform one of thefollowing:

n Delete the NSR_EXCH2010_BACKUP entry. NMM will use the defaultsetting of backing up preferred database copies.

n Replace the entry with NSR_EXCH_BACKUP=active/passive/preferredor all.

l If the optional NSR_EXCH_2010_DAG attribute is set, replace it withNSR_EXCH_DAG= <DAG_name>.

The NSR_EXCH2010_BACKUP and NSR_EXCH_2010_DAG attributes are no longersupported, and if either attributes are specified the backup will fail.

8. Make other changes, if required.

9. Click OK.

Backup

Modifying a client resource by using the Client Properties window after upgrading from NMM version 8.2.x or earlier 71

Verifying a backupTo verify that a backup is successful, type the following at a command prompt on theNetWorker client:

mminfo -Sot -s NW server -c NMM clientwhere:

l NW server is the name of the NetWorker server.

l NMM Client is the DAG name or Exchange Server mailbox server name.

Backup


CHAPTER 4

Mail Item Recovery


l Overview............................................................................................................74l Exchange recovery prerequisites....................................................................... 80l Configuring Exchange Server recovery...............................................................81l Recovery procedures......................................................................................... 83l Best practices and recommendations................................................................ 95

Mail Item Recovery 73

OverviewAn 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 RDB on the original Exchange server

l Recover to an Exchange Server RDB on a different Exchange server

l Granular level recoveries for individual mail items and foldersThe Granular Level Recovery chapter and the EMC NetWorker PerformingExchange Server Granular Recovery by using NetWorker Module for Microsoft withEMC ItemPoint Technical Notes provide information about how to perform granularlevel recoveries.

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

Database level recoveryWhen you recover a database, you generally overwrite the current database unlessyou recover to an RDB. See Recovering Exchange Server mailbox, public folderdatabase, or public folder mailbox files on page 93.

Message level and granular level recoveryWhen you must retrieve individual user mailboxes, user mail folders, or messages, youcan do so without overwriting entire mail databases. You can recover a database to anExchange RDB, and then use NMM GUI to select and recover individual mailboxes,folders, or messages. Message and Granular Level Recovery provides the recoveryprocedures. You can also use the PowerShell cmdlets to recover the data.

DAG recoveryA DAG backup provides access to backups of all Exchange databases through oneNMM client, although they came from multiple Exchange servers in the DAG. Youperform the recovery to the Exchange server that is hosting the active database copy.The recovery process to recover from a DAG backup is the same as a normal DAGrecovery.

Public mailbox folder and database recoveryYou can recover public folder mailboxes (Exchange Server 2013 and 2016) and publicfolder databases (Exchange Server 2010) just as you would any other mailboxdatabase.

Mail Item Recovery


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

In a conventional Exchange recovery, entire databases are replaced or recovered.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 on the same Exchange Server. You canrecover the RDB and GLR data to a different Exchange Server. Use NMM GUI tobrowse mail folders and locate individual messages.

The following figure illustrates a simple recovery of the Exchange databases in astand-alone Exchange Server environment.

Figure 13 Recovery in a stand-alone Exchange Server environment

In a stand-alone environment, you can recover the data to an alternateMailboxDatabase on the same Exchange Server. You can recover the RDB and GLRdata to a different Exchange Server. Use NMM GUI to browse mail folders and locateindividual messages.

Mail Item Recovery

Recovering Exchange data 75

Figure 14 Recovery to an alternate MailboxDatabase in a stand-alone Exchange Serverenvironment

Recovering individual mailboxes, mailbox folders, and messagesRetrieving and restoring large backups can use much 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 within an Exchangedatabase, such as individual user mailboxes, mailbox folders, and messages. Thesemethods 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, whereyou can 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 viewing the actual database, down to the message level. Only when yousend the recovery request to the NMM server are actual items copied out of thebackup 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 the time and space that is needed to browse the actualdatabase, and saves time and resources by only retrieving the items that areselected, not entire databases.

Mail Item Recovery


l Recover to RDB—You can also recover databases to an RDB, and then browsethose databases to select mailboxes, user folders, or messages for recovery. Whenyou restore to an RDB, you can browse the database offline, on a separate server,or from in a folder location that is separate from the online production Exchangeserver. While this method allows you to browse and retrieve items withoutoverwriting the live Exchange databases or user mailbox, recovery to an RDB doesrequire disk space, network resources, and processor resources to stage thedatabases in the RDB. When you recover to an RDB, it takes time to copygigabytes or terabytes of data from one location to another. NMM recovers thebackup to the RDB, then you can browse and retrieve individual items.

Compare the following figures, which illustrate:

l Recover using NMM Granular Level Recovery.

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

Mail Item Recovery

Recovering individual mailboxes, mailbox folders, and messages 77

Figure 15 Recover using NMM granular level recovery

Mail Item Recovery


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

Mail Item Recovery

Recovering individual mailboxes, mailbox folders, and messages 79

NOTICE

An RDB can only be used for recovering mailbox database data. It cannot be used torecover 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 Serverdata:

l Verify that the correct version of the Messaging API (MAPI) and CollaborationData Objects (CDO) kit is installed. MAPI Client and Collaboration Data Objects onpage 31 provides details.

l For each Exchange database to be recovered, you must select the This databasecan be overwritten by a restore Exchange checkbox in the ExchangeManagement Console.This step is a Microsoft requirement. In PowerShell, the flag is called Get-MailboxDatabase -Identity <DATABASE NAME>|selectAllowFileRestore and must be set to true. The Microsoft Exchangedocumentation provides more information about this checkbox.

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 that is used is “Recovered Data - sec77 -04/03/2013 18:28:45”.

l Exchange does not support restoring public folder mailboxes (Exchange Server2013 and 2016), or public folder databases (Exchange Server 2010) to RDBs.

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 existing databases with the recovery, perform a full levelbackup after every recovery performed in Exchange Server. This does not apply toRDB or granular restores.

Additional requirements for browsing mailboxesl Databases must be online. NMM does not display mailboxes in offline databases.

l For Exchange Server 2010 and 2013, the MAPI/CDO 1.21 kit must be installed.

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

l Log in with the user you created with the NMM Exchange Admin Configurationtool. The logged in user must have a configured mailbox with at least one mail sentor received.

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

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

Mail Item Recovery




Additional requirements for recovering databases in a DAGFor DAG recovery, ensure that the database recovery node and state are correct. Youmust perform the recovery to the DAG member server on an active node. Therestored databases must be in active state. Passive copies of the databases must be inExchange replication suspended state. If the copies are not in suspended state, thenyou must manually suspend passive copies before a recovery is performed.

You can suspend replication in the following three ways:

l By using the Exchange Shell command and calling Suspend-MailboxDatabaseCopy cmdlet

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

l For Exchange Server 2013 and 2016, through the Exchange Admin Center usingSuspend

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 2010 Recover Session, Exchange 2013Recover Session, or Exchange 2016 Recover Session and then select one ofthe following:

l Database Recover to view Exchange database backups and recover to RDBand perform either in-place recovery or alternate recovery from databasebackups. This is the default option for Exchange Server 2010 and 2013 andthe only available option for Exchange Server 2016.

l RDB Mailbox Recover to browse and recover mailbox items from existingRDB databases.

l Granular Level Recover to browse and recover items from databaseswithout first having to restore the database to an RDB.

Mail Item Recovery

Additional requirements for recovering databases in a DAG 81

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).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 withouttrying to replay the transaction logs, select Do not replay the transactionlogs. The database also cannot be mounted after the restore. If you selectthis option, you must manually replay the transaction logs by running theExchange utility eseutil.exe.

l To specify the number of retries when trying to mount the database, select anumber from the Number of attempts to try before failing on mountdrop-down list.

7. Click OK to close the Exchange Recover Options dialog box.

8. From the navigation tree, expand the folder Microsoft Exchange 2010,Microsoft Exchange 2013, or Microsoft Exchange 2016.

9. Select the Exchange databases that are to be recovered.

10. From the Exchange 2010 Recover Session, Exchange 2013 Recover Session,or Exchange 2016 Recover Session toolbar, click Recover.

Configuring roll-forward recovery of an Exchange server in a DAGenvironment

NOTICE

Perform the recovery from the node where the recovered database is active.

Procedure

1. To identify the Exchange database that must be recovered, use the ExchangeManagement Console (EMC), the Exchange Administrative Console (EAC), or ashell script to determine the DAG member where the active copy of thedatabase resides.

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.

Mail Item Recovery


For example:

Suspend-MailboxDatabaseCopy -Identity "bv-e15svr1\First Database"

4. Open the NMM client.

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

6. On the main toolbar, select the Client drop-down list, and then select the clientthat is the Exchange DAG.

7. From the left pane, select the Recover option.

8. Select Exchange Recover, and then select Database Recover to viewExchange database backups.

9. Click View and then click Refresh.

10. From the navigation tree, expand the or the Microsoft Exchange folder.

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

12. From the Exchange Recover Session toolbar, click Recover.

The Exchange Recovery Options Summary dialog box appears.

13. Review the options:

l If you must 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 box, verify 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 action closesthe Exchange Recover Options dialog box and starts the recovery.

14. Click Restore.

15. After the restore operation completes, restore replication between the nodeswith the resume-MailboxDatabaseCopy command.

For example:

resume-MailboxDatabaseCopy -Identity "bv-hood-e15svr1\First Database"

NOTICE

Perform a full backup after performing a roll-forward recovery.

Recovery proceduresThe following topics describe the procedures on methods to perform a recovery usingNMM.

Mail Item Recovery

Recovery procedures 83

Viewing volumes to back up for recoveryTo view the volumes that you must back up to perform an Exchange Server recovery,perform either of the following steps using the NMM GUI:

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

l Select any of the backed up databases and click Required volumes.The Required NetWorker Volumes dialog box with details about the volumeappears.

Recovering NetWorker Module for Microsoft Exchange backupsNetWorker Module for Microsoft Exchange (NME) and NMM cannot 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.

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 recoveryCertain 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 EMC NetWorker Module for Microsoft Administration Guide describes how to selector disable the automatic mounting option.

Performing Exchange Server recoveryThis section provides information on performing an Exchange Server recovery.

Performing a full recovery

You can recover the contents of a backed up database to the original database byperforming full recovery.

Mail Item Recovery


Procedure

1. From the left pane, select Exchange Recover Session, and then select one ofthe following:

l Database Recover (default)—Select to view Exchange database backups.

l RDB Mailbox Recover—Select to browse and recover Exchange Serveritems from existing RDB databases.

l Granular Level Recover—Select to browse and recover items fromdatabases without first having to restore the database to an 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 wantedbackup. The EMC 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 recoveryIn 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 1Rollup 6 or later, Exchange Server 2013, and Exchange Server 2016 support theability to restore data directly to an RDB. Mounting the recovered data as an RDBallows you to restore individual mailboxes or individual items in a mailbox. Publicfolders cannot be recovered to an RDB.

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.

Alternate and remote recoveries 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 ExchangeAdministrative Console (EAC), or a shell script to determine the DAGmember where the active copy of the database resides.

b. Log in 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.

Mail Item Recovery

Performing Exchange Server recovery 85

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 for recovery:

l To recover normal DAG backups—Select the DAG name for the client onwhich the NMM client software was configured for backup.

l To recover IP-less DAG backups—Select the hostname of the physicalmailbox server in the DAG for the client on which the NMM client softwarewas configured for backup.

5. Select the DAG database to be recovered.

You can browse and recover individual mailboxes and mailbox items from the liston the right pane.

Note

If no databases appear, click View > Refresh.

6. 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 17 Advanced Recovery dialog box

Select Recover Options to skip the steps for Advanced Recovery and performfull recovery of the database listed in Database (Source).

7. In the Select Recovery Type group, under Recovery Type, select one of thefollowing choices and click Next:

l Recovery Database (RDB) Recovery—The topic Recovering to a recoverydatabase (RDB) provides the remaining steps of the procedure.

l Alternate Database Recovery—The topic Recovering to an alternatedatabase provides the remaining steps of the procedure.

Mail Item Recovery


l Remote Database Recovery—The topic Recovering to a remote databaseprovides the remaining steps of the procedure.

8. The Exchange Recovery Summary dialog box appears. This dialog box lists theExchange Server Recovery options, the NetWorker Recovery Options andallows you to review the details before continuing.

Figure 18 Exchange Recovery Summary dialog box

9. To continue with recovery, click Start Recovery.

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 user (for example, NMMBackupUser) and add this user as memberof the Organization Management group to each of the tenants.

RDB browsing fails if the user credentials that are used for the operation have an Aliasin Active Directory. In this situation, you must create a user (without an Alias) andinstall NMM with the credentials of the new user. Provide the necessary permissionsand use the user account for RDB browsing operations.

Performing an RDB recoveryProcedure

1. In the Exchange Recover Session toolbar, click the Advanced Recover option.

2. In the Advanced Recovery dialog box, select Recovery Database (RDB)Recovery and click Next.

The Manage RDB dialog box appears, as shown in the following figure.

Mail Item Recovery


Figure 19 Manage RDB dialog box

3. To create an RDB, click Create.

The Create RDB dialog box appears.

Figure 20 Create RDB dialog box

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 box, you can also:

l Delete a RDB — Select the RDB from the Recovery Database (RDB) Listand click Delete.

Mail Item Recovery


Figure 21 Delete confirmation dialog box

l Unmount a RDB—If an 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 an 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) List andclick 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 continuing 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 Server stand-alone and DAG environments.

Procedure

1. In the Advanced Recovery dialog box, select Alternate Database Recovery forrecovery to an alternate database and click Next.

The Select Database dialog box with a list of alternate databases appears, asshown in the following figure.

Mail Item Recovery


Figure 22 Select Database dialog box

2. Select the database which you want to recover to and click Next.

The Exchange Recovery Summary dialog box appears. This dialog box lists theExchange Server recovery options, the NetWorker recovery options and allowsyou to review the details before continuing with recovery.


Recovering to a remote databaseBy 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 nsrnmmrc.exe is started in theDAG member server on the Mailbox database with the active copy.

Note

Remote database recovery is supported only in a DAG environment. You cannotperform a remote recovery to a host that is not a part of DAG.

1. In the Advanced Recovery dialog box, select Remote Database Recovery forrecovery to a remote database in an Exchange DAG member and click Next.The Select Server dialog box appears with a list of remote databases.

Figure 23 Select Server dialog box

2. Select the database to which you want to perform the recovery and click Next.

Mail Item Recovery


The Exchange Recovery Summary dialog box appears. This dialog box lists theExchange Server recovery options and the NetWorker recovery options and allowsyou to review the details before continuing with 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 applicationtries to log in. You can work around this by using the New-MailboxRestoreRequest cmdlet to restore data from the archive mailbox in theRecovery Database.

Procedure

1. Get the archive mailbox GUID from the get-mailbox cmdlet for the userwhose archive 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 <TargetFolder 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” available at http://technet.microsoft.com/en-us/library/bb125218.aspx provides more information aboutusing this command.

Recovering deleted Exchange Server mailboxes, public folder databases, orpublic folder mailboxes

NMM supports recovering the following Exchange Server databases outside of theExchange VSS process:

l Exchange Server mailbox databases.

l Exchange Server public folder mailboxes (Exchange Server 2013 and 2016) andpublic folder databases (Exchange Server 2010).

This capability allows you to recover mailbox databases and mailboxes that have beenremoved from the Exchange server and the Active Directory. You can also recoverthese items so that you can perform data mining for Exchange public folder mailboxesor public folder databases with third-party tools.

Procedure

1. 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 wantedbackup. The EMC NetWorker Administration Guide provides details.

Mail Item Recovery

Recovering deleted Exchange Server mailboxes, public folder databases, or public folder mailboxes 91

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

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

Although the job summary does not note that the recovery is to a Windows filesystem, if the database itself is online, there is no danger of over-writing thelive database.

2. Select the mailbox database that you want to recover and click RecoverOptions.

3. Click the Exchange tab and click Select Destination.

4. Select the Restore Deleted Database Files on File System checkbox.

5. Browse to the target location where NMM recovers the mailbox database files.

6. Click OK.

7. Recover the deleted Exchange databases.

Microsoft documentation provides information.

8. Perform data mining by using tools such as ItemPoint for Microsoft ExchangeServer.

EMC NetWorker Performing Exchange Server Granular Recovery by usingNetWorker Module for Microsoft with EMC ItemPoint Technical Notes and theEMC ItemPoint for Microsoft Exchange Server User Guide provide information.

Performing a quick recovery of a deleted mailboxThe procedure to recover a deleted mailbox is performed independent of NMM backupor recovery operations.

If a user mailbox is deleted, you can quickly recover the mailbox through the ExchangeManagement Console.

Procedure

1. In the 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.

7. Select Matching user > User mailbox, and then click Next.

The deleted user mailbox is then re-created under Recipient management >Mailbox.

NOTICE

Re-created deleted mailboxes are not always immediately visible. It might takefrom 15 minutes to an hour before the mailbox is visible and accessible throughOutlook.

Mail Item Recovery


Recovering Exchange Server mailbox, public folder database, or public foldermailbox files

You can use NMM or ItemPoint for Microsoft Exchange Server to perform a granularlevel recovery (GLR) of Exchange Server mailbox or public folder databases or mailboxdatabase items.

The procedure varies depending on the method you use. The recovery process is thesame for all supported versions of Exchange Server, although the backup save setsand application information vary depending on the version Exchange Server you use.

The Granular level recovery chapter provides more details on performing GLR.

Procedure

1. Backup the database by using NMM.

2. Recover the files by using one of the following methods:

l Use NMM to perform a flat file recovery of the database by using one of thefollowing procedures:

n To recover files from a network location: Recovering Exchange Servermailboxes, public folder databases, or public folder mailboxes from anetwork location on page 93.

n To recover files to a remote computer: Recovering Exchange Servermailboxes, public folder databases, or public folder mailboxes to a remotecomputer on page 94.

l Use ItemPoint for Microsoft Exchange Server to perform a granular levelrecovery of the Exchange flat files.The EMC ItemPoint for Microsoft Exchange Server User Guide providesinformation about Exchange flat files.

Recovering Exchange Server mailboxes, public folder databases, or public folder mailboxes froma network location

With ItemPoint for Microsoft Exchange Server or a third-party tool, you can use thefiles in these folders to perform an item-level recovery to a target user mailbox that isin production. The Granular level recovery chapter provides more details.

Procedure

1. Log in to 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 list, and then select the DAGclient where you performed the backup.

4. Click View and then click Refresh.

5. Click Recover > Exchange Recover Session > Database Recover.

The NMM user interface shows the mailbox databases that are available forrecovery.

6. Select the mailbox database that you want to recover and click RecoverOptions.

7. Click the Exchange tab.


Mail Item Recovery

Recovering Exchange Server mailbox, public folder database, or public folder mailbox files 93

9. Browse to the target location where NMM recovers the mailbox database files.

10. Click OK.

11. Start the flat file recovery of the database by selecting the mailbox, publicfolder, public folder mailbox, or public folder 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 mailboxes, public folder databases, or public folder mailboxes to aremote computer

To recover the Exchange Server mailboxes, public folder database, or public foldermailbox flat file to a remote computer, you must map a network drive and specify thatnetwork drive path as the value for a new registry entry namedExchangeDataFilePath.

With ItemPoint for Microsoft Exchange Server or a third-party tool, you can use thefiles in these folders to perform item-level recovery to a target user mailbox that is inproduction. The Granular level recovery chapter provides more details.

Procedure

1. On the remote computer that you will 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 box, next to the Client name field, clickthe Refresh button.

6. In the Select Viewable Clients dialog box, click the client where you performedthe backup and then click Add.

7. Click OK.

8. On the main toolbar, select the Client drop-down list, and then select the DAGclient where you performed the backup.

9. From the left pane, select Recover, select Exchange 2010 Recover Session,Exchange 2013 Recover Session, or Exchange 2016 Recover Session andthen select Database Recover.

The NMM user interface shows the mailboxes, public folder databases, or publicfolder mailboxes that are available for recovery.

10. Select the mailboxes, public folder databases, or public folder mailboxes youwant to recover and click Recover Options.

11. Click the Exchange tab.


13. Browse to the target location where NMM recovers the files.

14. Click OK.

Mail Item Recovery


15. After the flat file recovery completes, verify that NMM recovered the logsand .edb files to the folder you created.

Best practices and recommendationsReview the following best practices for Exchange backup and recovery.

l Also, as well as scheduled full backups, you should 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 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.

l If you delete Exchange objects like storage groups and databases in ExchangeServer, you cannot recover these objects until you perform disaster recovery.Objects from the Exchange Server should not be deleted unless they no longermust 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 limitationsReview the following limitation when backing up and restoring Exchange objects withNMM.

Roll-forward recovery is not possible after point-in-time restore. After you complete asuccessful point-in-time restore, perform a full backup of the Exchange Server so thatyou can perform roll-forward recovers.

Mail Item Recovery

Best practices and recommendations 95

Mail Item Recovery


CHAPTER 5

Granular Level Recovery


l Recovering Mailbox items with GLR...................................................................98l Exchange server GLR using ItemPoint for Microsoft Exchange Server............ 100l Exchange server GLR using the NMM UI..........................................................103

Granular Level Recovery 97

Recovering Mailbox items with GLRIn 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 within an Exchange database, such as individual user mailboxes, mailbox folders,and messages. Individual folders can be browsed and selected from the restored 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 backup device. The virtual drive is created 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 viewing 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. If you use the NMM UI for GLR, the items are placed in a folderin the user’s mailbox that is called Restored Items, where you can browse and selectthe items to keep. This Restored Items folder is similar to any other folder in themailbox.

The NetWorker Module for Microsoft Administration Guide provides more informationabout GLR.

GLR considerationsThe following requirements must be met to recover granular Exchange data by usingGLR.

l If you are using EMC ItemPoint for Microsoft Exchange Server GLR, you mustselect the Exchange GLR (includes EMC ItemPoint) option when installing theNMM software.

l NetWorker 9.0 or later must be installed on the NetWorker server for Exchangeserver 2010 and 2013.

l NetWorker 9.0.1 or later must be installed on the NetWorker server for Exchangeserver 2016.

l You must backup the writer set, or database or storage group save set with aGLR-compatible version of NMM:

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

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


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




n For Exchange Server 2016 database:APPLICATIONS:\Microsoft Exchange 2016\DatabaseThe EMC NetWorker Module for Microsoft Administration Guide provides moreinformation about backups.

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 box, 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.

Options for Exchange GLRThere are two methods available for performing Exchange GLR. EMC recommendsthat you use ItemPoint for Microsoft Exchange Server to perform GLR.

You can use one of the following methods to perform Exchange server GLR:

l GLR using ItemPoint for Microsoft Exchange Server.

l GLR using the NMM UI.

If you are unable to use the NMM UI or ItemPoint for Microsoft Exchange Server forgranular level recovery, you can use the NMM Support Tools for recovery. The EMCNetWorker Module for Microsoft Administration Guide provides details about these tools.

The following table describes which methods can be used for GLR depending on theExchange server.

Table 27 Options for Exchange GLR

Exchange Server GLR methods available

Exchange Server 2010 l GLR using ItemPoint for MicrosoftExchange Server

l GLR using the NMM UI


l GLR using the NMM UI



Options for Exchange GLR 99

Exchange server GLR using ItemPoint for MicrosoftExchange Server

This section contains information on how to perform a GLR using ItemPoint forMicrosoft Exchange Server.

Before using ItemPoint for Microsoft Exchange Server GLR, consider the followingrequirements:

l The Exchange GLR (includes EMC ItemPoint) option must be selected duringNMM installation.

l You can use Exchange Server 2010 and above with ItemPoint for MicrosoftExchange Server.

l You can use Windows Server 2008, Windows Server 2008 RS, Windows Server2012, or Windows Server 2012 R2 with ItemPoint for Microsoft Exchange Server.

l ItemPoint for Microsoft Exchange Server requires Microsoft .Net Framework 3.5SP1 and 4.0.

l You must have Microsoft Outlook 2010 or later x86 (32-bit) version installed.

Note

MAPI/CDO and Microsoft Outlook 2010 or later cannot be installed on the samemachine.

For more information on installing ItemPoint for Microsoft Exchange Server, refer tothe EMC NetWorker Module for Microsoft Installation Guide. For more information onusing ItemPoint for Microsoft Exchange Server, refer to the EMC ItemPoint forMicrosoft Exchange Server User Guide.

Recovering individual mailbox items by using ItemPoint for MicrosoftExchange Server

Use this procedure to perform GLR on individual mailbox items using ItemPoint forMicrosoft Exchange Server.

The EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorkerModule for Microsoft with EMC ItemPoint Technical Notes provides additionalinformation about GLR procedures.

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 DAG, select the virtual client name of the DAG towhich you are recovering data. You can select the virtual client from the clientlist attribute in the application toolbar.

4. From the left pane, select Recover > Exchange Recover Session > GranularLevel Recover.

5. In the browse tree, select the checkbox next to the mailbox database thatcontains the items for recovery.

6. Optional: To change the database mount options:



a. Select the Recover Options... button from the taskbar.

The Exchange Recover Options window appears.

b. In the Exchange Recover Options window, you can specify the followingvalues in the Mount Option pane:

l The mount path. The default mount path is the folder that is specifiedduring installation.

l The amount of time the backup is mounted. You can set the timeoutperiod to 2, 4, 8, 16, or 24 hours. The default timeout period for mountedbackups is 8 hours.

Figure 24 Exchange Recovery Options window for ItemPoint GLR

7. Right-click the selected mailbox database and click Mount backup.

Figure 25 Mounting the backup for ItemPoint GLR

8. Open the Monitor page to verify the mount operation was successful.

A successful mount operation displays output similar to the following on theMonitor page.


Recovering individual mailbox items by using ItemPoint for Microsoft Exchange Server 101

Figure 26 Successful mount operation output in the Monitor page

9. Launch the ItemPoint GUI:

l On Windows 2008—From the start menu, select Programs > EMCItemPoint > EMC ItemPoint for Microsoft Exchange Server.

l On Windows 2012—Select the EMC ItemPoint for Microsoft Exchange

Server icon .

Note

The NMM UI can be left open or closed after the mounting is successful.The ItemPoint GUI does not require the NMM UI after the mounts arecreated.

10. Point to the mount path locations for the backup.

You can find the mount paths on the output on the Monitor page aftermounting the backup, or by right-clicking the database in the Browse tree ofthe Recover page and selecting Mount details.

11. Browse the mount path and mark items to recover, then proceed with recovery.

The EMC ItemPoint for Microsoft Exchange Server User Guide provides moreinformation.

Unmounting backups after ItemPoint for Microsoft Exchange Server GLRAfter performing GLR using ItemPoint for Microsoft Exchange Server, unmount thebackup by using one of the following methods.

l For standard restore operations, the backup is unmounted after the restore iscompleted.

l If you changed the mount time in the Exchange Recover Options window, thebackup is unmounted based on the specified timeout setting. The default timeoutperiod for mounted backups is 8 hours.

l You can manually unmount the backup by right-clicking the BBB Mount systemtray icon and clicking Unmount Backups.



Note

You can unmount at any time after initiating GLR, even if the database is in use byItemPoint for Microsoft Exchange Server.

Using the BBB Mount system tray iconThe BBB Mount system tray icon appears when a backup is mounted.

Click the BBB Mount system tray icon to choose from a menu of available actions.

The following actions are available through the BBB Mount system tray icon:

l Unmount a backup.

l Extend timeout period for which the backup is mounted.

l View mount details.

Exchange server GLR using the NMM UIThis section contains the following procedures for using the NMM UI to perform GLRon Exchange Server 2010 or Exchange Server 2013.

You can restore to an Exchange Server RDB without disrupting the active productiondatabases and servers. After you restore to the RDB, you can browse and selectindividual mailboxes to restore to the production server while it is online.

After a successful GLR, until you perform another GLR or a different type of a restoreoperation, the GLR RDB remains mounted and maintains a Read connection with theoriginal device. You must delete the GLR RDB before you can perform a Stageoperation. Closing the NMM GUI should remove the GLR RDB.

GLR considerations for the NMM UIConsider the following requirements before performing GLR by using the NMM UI.

l NMM does not support GLR in an Exchange Server 2016 environment by using theNMM UI. If you are using Exchange Server 2016, perform GLR by using ItemPointfor Microsoft Exchange Server.

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.GLR is only supported for backups residing on GLR-compatible devices, such asAFTD 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.

Recovering individual mailbox items using GLR through the NMM UIThe 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 at a time. Torecover a different version of the selected database, repeat step 5 through step 10.


Using the BBB Mount system tray icon 103

Changing to a different version dismounts the currently mounted virtual drive. NMMcreates a 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 DAG, select the virtual client name of the DAG towhich you are recovering data. You can select the virtual client from the clientlist attribute in the application toolbar.

4. From the left pane, select Recover > Exchange Recover Session > GranularLevel Recover.

5. Select the mailbox database to recover.

Figure 27 Individual mailbox databases

Only full backups are compatible with GLR.

6. In the Exchange Server Session toolbar, click Recover.

l If the backup is GLR-compatible, the recovery continues.

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 and performs the recovery.

7. In the Exchange Recovery Summary dialog box, click Start Recover.

8. Click OK to clear the Recovered RDB Mailbox Items dialog box.

9. 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 28 Sample mailbox

10. Click Recover and then Start Recover to recover the selected folders.

Performing a GLR to an alternate mailbox using the NMM UIYou 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.

Note

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 re-creates each user’s respective folder structure and mailitems.

Procedure

1. Mount the backup to a virtual drive.

Note

Do not click Recover in the last step.

2. In the Advanced Recovery dialog box, select Alternate Mailbox User.

3. Select the user account for the mailbox.

l To search for a specific user:

a. In the Name dialog box, type a name.

b. Click Search.

c. Confirm the user.


Performing a GLR to an alternate mailbox using the NMM UI 105

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 using the NMM UIThe NMM software does not support the Exchange Server archive mailbox feature. Toperform an item level recovery of an archive user mailbox, use the New-MailboxRestoreRequest command 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 email messages in to thefolder.

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 command 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 using NMM UIYou 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 deletedusers.

Before you begin

The PST role is not available by default. To configure the role, run the followingPowerShell cmdlet:

New-ManagementRoleAssignment –Role "Mailbox Import Export" –<Exchangeadministrator>

where <Exchange administrator> is the Exchange administrator username.



Procedure


2. From the left pane, select Exchange Recover Session, and then select one ofthe following:

Table 28 Performing a GLR to a PST recover options

Option Description

RDB Mailbox Recover(default)

Browse and recover Exchange 2010 and 2013 items from anexisting RDB database. Select this option to perform a PSTexport from an existing RDB.

Granular Level Recover Browse and recover items from databases without first havingto restore the database to an RDB. Select this option if noRDB currently exists.

Note

Database Recover overwrites existing production mailboxes, which does notproduce the correct results.

3. If no databases appear, click View > Refresh.

4. Select the database in the NMM user interface.

If the database is not listed, select a browse time that includes the wantedbackup. The EMC NetWorker Administration Guide provides details.

5. Select Recover in the taskbar.

6. In the Recover Options dialog box, select the Exchange tab.

7. In the PST Target field, type 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 box.

10. To recover items to a PST file, select the location and name of the PST file inthe Exchange Recover Options dialog box.

Due to a Microsoft restriction, NMM does not support PST recovery for a singlemail item.If no PST file is specified, then the items that are selected for recovery arerecovered to the production server.

Once a recover to the PST file has completed, the field containing the locationand name of the PST file is cleared.


Performing a GLR to a PST using NMM UI 107

CHAPTER 6

Troubleshooting


l Troubleshooting general errors..........................................................................110l Troubleshooting backups.................................................................................. 110l Troubleshooting recovery..................................................................................112l Troubleshooting granular level recovery............................................................ 113

Troubleshooting 109

Troubleshooting general errorsThis section explain how to resolve general issues you might encounter while usingNMM with Exchange Server.

User mailbox structure is distorted in Outlook Web Access after an Exchange2016 PIT restore operationAfter a point-in-time (PIT) restore operation of an Exchange Server 2016, when youview a user mailbox with Outlook Web Access, the mailbox structure appearsdistorted.

SolutionClear the cache of the web browser you are using, and then reconnect to OutlookWeb Access. After you clear the cache, the mailbox structure will appear correctly.

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.

SolutionRun the Exchange administrator configuration tool to update the administratoraccount.

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, obtain the GUID by using thisPowerShell cmdlet:

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.View the content indexing status by using the following PowerShell cmdlet:

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 PowerShell cmdlet. Microsoft provides a full list ofsyntax and parameters for this cmdlet.

Troubleshooting


Solution

Table 29 PowerShell cmdlet for restored mailboxes

Exchange version PowerShell cmdlet Microsoft website

l Exchange Server 2010SP1 or later

l Exchange Server 2013CU1 or later

l Exchange Server 2016

New-MailboxRestoreRequest

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

The following example shows the New-MaiboxRestoreRequest cmdlet with sampleparameters:

New-MaiboxRestoreRequest -SourceDatabase <RDBNAME> -SourceStoreMailbox<GUID_OF_MAILBOX_YOU_WANT_TO_RESTORE> -TargetMailbox<ORIGINAL_USER_MAILBOX> -Targetrootfolder <Folder_to_restore_into>allowlegacydnmismatch $true

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 must 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). Also, if an Exchange Server isconfigured to save either database files or log files to a softlink path, backups fail.EMC plans to fix this in a future release.

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 a CAS array or NLB in the NMMuser interface. The failure might be due to the NLB configuration, NLB type, firewallsetup, or other error.

SolutionSet up the individual CAS servers to directly communicate with CAS server in suchsetups, instead of creating a CAS Array or NLB through the NMM user interface.

Troubleshooting

Troubleshooting backups 111




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.

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

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.


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

Troubleshooting


SolutionTo browse the contents in RDB, 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.


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.

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 granular level recoveryTroubleshooting ItemPoint for Microsoft Exchange Server GLRTo verify ItemPoint for Microsoft Exchange Server configuration, run the NMMConfiguration Checker on the NMM client. The EMC ItemPoint User Guide providesinformation about troubleshooting ItemPoint GLR.

Troubleshooting

Troubleshooting granular level recovery 113

Troubleshooting NMM UI GLRIf 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.

Troubleshooting


Copyright © 2015 EMC Corporation. All rights reserved. Published in USA. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).


EMC NetWorker Module for Microsoft for Exchange … NetWorker Module for Microsoft for Exchange...

Documents

Transcript of EMC NetWorker Module for Microsoft for Exchange … NetWorker Module for Microsoft for Exchange...