emc networker module for microsoft for exchange · pdf fileemc networker module for microsoft...

EMC® NetWorker® Module forMicrosoft for Exchange ServerVSSVersion 9.0

User Guide302-001-753

REV 04

Copyright © 2007-2016 EMC Corporation. All rights reserved. Published in the USA.

Published July 2016

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

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. 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 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 User Guide

5

7

9

Introduction 13

Overview....................................................................................................... 14Stand-alone or single Exchange Servers........................................... 14Exchange Server DAGs..................................................................... 14High availability in Exchange Server................................................. 15Active and passive databases.......................................................... 16

Using NMM in an Exchange Server environment............................................ 16Exchange Server 2010 VSS Writers...................................................16Exchange Server 2013 and 2016 VSS Writer.....................................17Compatibility with previous Exchange backups................................ 17Backup initiated transaction log file truncation................................ 17Backup types and levels...................................................................18Federated backups...........................................................................18Recovery types................................................................................. 18Exchange Server block based backup.............................................. 19

Configuration 21

Supported Exchange server deployment scenarios and limitations................22Supported Exchange Server versions................................................22Single server Microsoft Exchange Server and Microsoft SharePointServer installations.......................................................................... 22

Exchange backup prerequisites.....................................................................22NMM Exchange Admin Configuration tool......................................................22

Configuring an Admin user............................................................... 24Validating an existing Admin............................................................28

MAPI client and Collaboration Data Objects...................................................28Exchange Consistency Check........................................................................ 29

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

Backup 31

Planning backups..........................................................................................32Backup considerations.....................................................................32Backups in DAG environments......................................................... 32Configuring backups to use a remote storage node in a DAGenvironment.................................................................................... 32Backing up highly available Exchange server....................................33Shadow copy and log truncation...................................................... 33

Preferred Server Order List.............................................................................33Configuring Exchange client resources.......................................................... 34

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

CONTENTS

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

Creating a client resource by using the Client Backup Configurationwizard..............................................................................................35Creating a client resource for Exchange backups by using theNetWorker Management Console..................................................... 38

Configuring Exchange backups......................................................................42Backup configuration options.......................................................... 43Configuring NetWorker administrator privileges................................44Configuring a federated DAG backup................................................44Complete list of Exchange Server Application Information attributes........................................................................................................ 45Viewing a valid application data save set......................................... 46Circumstances that promote incremental or subsequent backups tofull backup.......................................................................................48

Example of a federated backup..................................................................... 48Verifying a backup.........................................................................................49

Mail Item Recovery 51

Overview....................................................................................................... 52Recovery types................................................................................. 52Recovering Exchange data................................................................53Recovering individual mailboxes, mailbox folders, and messages....54

Exchange recovery prerequisites................................................................... 58Additional requirements for browsing mailboxes..............................58Additional requirements for recovering databases in a DAG............. 59

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

Recovery procedures..................................................................................... 61Recovering NetWorker Module for Microsoft Exchange backups....... 61Mounting the database after recovery.............................................. 62Performing Exchange Server recovery............................................... 62Recovering deleted Exchange Server mailboxes, public folderdatabases, or public folder mailboxes..............................................68Performing a quick recovery of a deleted mailbox.............................69Recovering Exchange Server mailbox, public folder database, or publicfolder mailbox files.......................................................................... 70

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

Granular Level Recovery 73

Recovering Mailbox items with GLR............................................................... 74GLR considerations.......................................................................... 74

Recovering individual mailbox items using GLR............................................. 75Performing a GLR to an alternate mailbox...................................................... 76Performing a GLR on an archive user mailbox................................................ 77Performing a GLR to a PST..............................................................................78

Troubleshooting 81

Troubleshooting general errors......................................................................82Troubleshooting backups..............................................................................82Troubleshooting recovery.............................................................................. 84

Chapter 4

Chapter 5

Chapter 6

CONTENTS


NetWorker and NMM installation in a stand-alone or single Exchange Server environment......................................................................................................................................14NetWorker and NMM installation with a DAG in an Exchange Server environment.......... 15Exchange Server DAG environment................................................................................ 16NMM Exchange Admin Configuration tool...................................................................... 23Configuring a user with Organization Management rights...............................................26Configuring a user without Organization Management rights......................................... 27Initial page of Client Backup Configuration wizard......................................................... 35Example of an Exchange Server federated backup......................................................... 49Recovery in a stand-alone Exchange Server environment............................................... 53Recovery to an alternate MailboxDatabase in a stand-alone Exchange Server environment......................................................................................................................................54Recover using NMM granular level recovery................................................................... 56Recover to an RDB, and then recover data from the RDB to a user mailbox..................... 57Advanced Recovery dialog box.......................................................................................64Exchange Recovery Summary dialog box........................................................................64Manage RDB dialog box.................................................................................................65Create RDB dialog box................................................................................................... 66Delete confirmation dialog box...................................................................................... 66Select Database dialog box........................................................................................... 67Select Server dialog box................................................................................................ 68Individual mailbox databases........................................................................................75Sample mailbox.............................................................................................................76

1

2345678910

1112131415161718192021

FIGURES


FIGURES


Revision history............................................................................................................. 10Style conventions.......................................................................................................... 11Writers used by NMM for Exchange Server backup and recovery.................................... 17Permissions configured by the Exchange administrator configuration tool .................... 24Exchange Server GLR MAPI/CDO requirements...............................................................28Exchange application information variables for threading and throttling ....................... 29Exchange Server name attributes ..................................................................................34Exchange Server 2010 save set names.......................................................................... 34Exchange Server 2013 save set names.......................................................................... 34Exchange Server 2016 save set names.......................................................................... 35Exchange Application Information attribute settings...................................................... 39Examples for application variables................................................................................ 40Exchange Server backup options................................................................................... 43Exchange Application Information attribute settings...................................................... 45Commands for displaying valid application data save sets............................................ 46Special characters and their URL-encoded values.......................................................... 47PowerShell cmdlets for restored mailboxes....................................................................82

1234567891011121314151617

TABLES


TABLES


Preface

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

Contact your EMC technical support professional if a product does not function correctlyor 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) software to back up and recover Microsoft Exchange Server using the VolumeShadow 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 when performingapplication-specific tasks. Download a copy of the EMC NetWorker Module for MicrosoftAdministration Guide from EMC Online Support (https://support.emc.com) before usingthis 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

04 July, 2016 l Updated the following sections:

n Stand-alone or single Exchange Servers on page14

n MAPI Client and Collaboration Data Objects onpage 28

n Troubleshooting recovery on page 84

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

n Configuring an Admin user on page 24

n Example Admin user configurations on page 26

n Validating an existing Admin on page 28

03 December, 2015 Incorporated the technical review comments throughoutthe guide.

02 October, 2015 Updated the following sections:Section "Compatibility with previous Exchange backups"in the Introduction chapter.

Section "Creating a client resource using the ClientBackup Configuration wizard" in the Backup chapter.

01 September, 2015 First release of this document for EMC NetWorker Modulefor Microsoft release 9.0.

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

l EMC NetWorker Module for Microsoft for SQL VDI User Guide

l EMC NetWorker Module for Microsoft for Exchange VSS User Guide

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

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

l EMC NetWorker Performing Backup and Recovery of SharePoint Server by using NetWorkerModule for Microsoft SQL VDI solution Technical Notes

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

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

Preface


l NetWorker documentation set

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

NOTICE

Addresses practices that are not related to personal injury.

Note

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

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 selects orclicks)

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

... 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 EMC products,go to EMC Online Support at https://support.emc.com.

Technical supportGo to EMC Online Support and click Service Center. Several options for contacting EMCTechnical Support appear on the site. Note that to open a service request, you must havea valid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Preface


https://support.emc.com

Online communitiesGo to EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith 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............................................................................................................... 14l Using NMM in an Exchange Server environment.................................................... 16

Introduction 13

OverviewThe EMC

® NetWorker

® Module for Microsoft (NMM) release 9.0 software supports backup

and recovery for Exchange Server 2010, 2013, and 2016 recovery databases (RDBs) instand-alone and DAG configurations.

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 information aboutsupported Windows Server versions.

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, log files,and checkpoint files exist on one server. NMM is installed on the Exchange server.

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

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

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 the mailboxrole installed.

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

Introduction


http://support.emc.com

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 not replicatedacross multiple servers, including and public folder mailboxes and public folderdatabases.

l You can only restore backups of databases in a DAG environment to active databasecopies.The Microsoft TechNet website provides information about the Exchange DAGarchitecture.

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

The topic Configuring Exchange backups on page 42 provides information onconfiguring a DAG backup after you install the NetWorker and NMM clients on eachExchange server in the cluster.

High availability in Exchange ServerMost larger enterprises typically deploy Exchange Server in some form of high-availabilityconfiguration. Exchange Server 2010, 2013, and 2016 typically includes the use of DAGsand mailbox database copies. You do not need to install and configure any Windowsclustering before you install Exchange Server. You can add high availability to theExchange Server environment after you deploy Exchange Server without having touninstall Exchange Server and then reinstall in a high-availability configuration. Theseimprovements in high availability and site resilience functionality also simplifyinstallation and configuration of the NetWorker and NMM clients for backup and recovery.

Introduction

High availability in Exchange Server 15

Active and passive databasesThe following topic describes NMM installations with Exchange Server 2010 and laterclustered environments.

In a clustered environment, there are active and passive copies of the databases. Theserver constantly updates a copy or a replica as the passive copy, and minimizes theimpact on performance of the active copy. For backups, the passive copy enables you toback up the databases without affecting the performance or data of the active copy. Youmust designate individual databases as either active or passive. This enables you to havea mix of active and passive databases 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 on page 42 provides detailed steps for configuring theNMM client on the active node after installation of the NMM client on each ExchangeServer in the cluster.

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

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

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

Introduction


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

Application writers Description

Information StoreWriter

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

Replication ServiceWriter

This writer is built into the Replication Service. The Replication ServiceWriter 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 Writer backups tothe active database location.

Exchange Server 2013 and 2016 VSS WriterThis topic describes the Exchange Server 2013 and 2016 writer used for active andpassive databases.

Exchange Server 2013 and 2016 have one writer for active and passive databases:Microsoft Exchange Server Writer. NMM uses the Microsoft Exchange Server Writer duringbackup 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 backup orrestore Exchange Server databases.

Compatibility with previous Exchange backupsWhen you install NMM, select the Restore of NMM 8.2.x and Earlier Backups (VSSworkflows) and Restore from previous NMM backups options in the NMM installer toperform recoveries later. The EMC NetWorker Module for Microsoft Installation Guideprovides information.

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

For the recoveries to succeed after you upgrade the Exchange Server that includes servicepacks also, perform a full backup before the upgrade and after the upgrade.

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) to truncatetransaction logs. NMM notifies the Exchange writer that a backup has completedsuccessfully, which allows the Exchange writer to continue with log truncation.

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 log filesat the completion of successful full or incremental backups.

Introduction

Exchange Server 2013 and 2016 VSS Writer 17

l In DAG configurations, the Replication service delays the log truncation until allnecessary log files are replayed into all other copies. The Replication service deletesthe backed up log files both from the active and the passive copy log file paths afterthe Replication service verifies that the to-be-deleted log files have successfully beenapplied to the copy database and both active database and the database copiescheckpoint has passed the log files to be deleted.

Backup types and levelsNMM 9.0 and later supports block based full and incremental backups of stand-aloneand DAG Exchange Server setups. A block based full backup backs up every selecteddatabase and all necessary log files. After the backup completes, log files older than thecheckpoint that is taken at backup start time are deleted. A block based incrementalbackup backs up only the changed blocks of every selected database and all necessarylogs. Like a block based full backup, log files older than the checkpoint are deleted oncethe backup completes. The EMC NetWorker Module for Microsoft Administration Guideprovides details.

Federated backupsNMM supports only federated backups for Exchange Server DAGs. Federated backupsallow you to back up all databases in a DAG with a single save set across all ExchangeServer nodes in the DAG. NMM does not require you to perform a separate backup ofeach node.

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

NMM supports the following types of recovery:

l Roll-forward recovery

l Point-in-time recovery

l Database recovery to Exchange RDB

l Remote database recovery for Exchange Server DAG

l Mailbox item level recovery from Exchange RDB databases

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

l Granular Level Recovery (GLR) to alternate mailbox

l Granular Lever Recovery (GLR) to PST files

Note

Exchange Server 2016 does not support GLR and RDB.The EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorkerModule for Microsoft with Ontrack PowerControls Technical Notes provides informationabout how to perform GLR of Exchange Server 2016.

Introduction


Exchange Server block based backupThe Exchange Server block based backup is the default and only method to back up anExchange Server by using NMM 9.0 and later. The EMC NetWorker Module for MicrosoftAdministration Guide provides information about block based backups and recoveries.

Introduction

Exchange Server block based backup 19

Introduction


CHAPTER 2

Configuration


l Supported Exchange server deployment scenarios and limitations........................22l Exchange backup prerequisites.............................................................................22l NMM Exchange Admin Configuration tool..............................................................22l MAPI client and Collaboration Data Objects...........................................................28l Exchange Consistency Check.................................................................................29

Configuration 21

Supported Exchange server deployment scenarios andlimitations

The Microsoft Exchange Server documentation provides a complete and updated list ofsystem requirements and supported configurations.

The EMC NetWorker Online Software Compatibility Guide, available on the EMC OnlineSupport website at http://compatibilityguide.emc.com:8080/CompGuideApp, providesthe most up-to-date and accurate listing of hardware, operating system, service pack,and application versions that the NMM client 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.

For DAG environments, the Exchange Server documentation recommends two networks:one for public traffic and one for replication traffic. Although a DAG with a single networkis a supported configuration, it is not recommended. Using only one network connectioncan lead to unstable operations, such as databases that fail over to other systems whenthey experience network connection time outs.

Single server Microsoft Exchange Server and Microsoft SharePoint Serverinstallations

Microsoft does not support the installation of Microsoft Exchange Server and MicrosoftSharePoint Server on the same host. So, NMM also does not support this installation.

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

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

l Install the .NET Framework.

l Install the hotfixes and cumulative updates that are listed in the EMC NetWorkerModule for Microsoft Installation Guide.

l Ensure that you use the same version of Exchange Servers, Windows Servers, andservice packs or cumulative updates.

l Install the NetWorker client and NMM software on all Exchange servers that are a partof a backup.

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 and recoveryoperation on an Exchange Server. After installing NMM, use the tool to create an account,modify, validate, and update the existing account privileges.

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

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

Configuration


http://compatibilityguide.emc.com:8080/CompGuideApp

n Create an NMM Exchange Admin user and configure the permissions that arerequired for Exchange backup and recovery (both database and GLR), and set theuser 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 Exchange administratoraccount is correctly configured.

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 must configurea user directly after installing NMM.

The following figure shows the Exchange administrator configuration tool landing page.

Figure 4 NMM Exchange Admin Configuration tool

You can use the Exchange NMM Admin Tool to create users, configure existing users, andassign correct permissions to existing users. You can assign a user to the OrganizationManagement role, or assign them to the EMC NMM Exchange Admin Role group.

If you assign a user to the EMC NMM Exchange Admin Role group, then they are removedfrom the Organization Management role. Conversely, if you assign a user to theOrganization Management role, they are removed from the EMC NMM Exchange AdminRole 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 following steps:

l Creates an Active Directory user account.

Configuration

NMM Exchange Admin Configuration tool 23

l Creates a custom Exchange security group.

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

Table 4 Permissions configured by the Exchange administrator configuration tool

User group Exchange Server role

Security group membershipson NMM Client computer

Local Administrator

Security group membershipson Domain Controller

n Backup Operators

n Remote Desktop Users

Exchange Security Groupmemberships

n Exchange Servers

n Organization Management or EMC NMM Exchange AdminRoles

n EMC NMM Exchange Admin Roles includes:

– 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 where NMMis installed.

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

Procedure

1. Click Configure Admin User on the NMM Exchange Admin Configuration window.

2. Select one of the following under Action:

l Create new admin—Create an Exchange user account for NMM backup andrecovery operations.

l Configure existing user—Use an existing Exchange user account for NMM backupand 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.

Configuration


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

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

Members of the Organization Management role group have permissions to manageExchange objects and their properties in the Exchange organization. Members canalso delegate role groups and management roles in the organization.

Note

If you select Assign Organization Management rights, NMM adds the user to theOrganization Management group. The tool does not create an NMM Exchange AdminRoles 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 group called EMCNMM 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. This option isunavailable if a ContentSubmitters group is already created in the Active Directory.This option is only available on Exchange Server 2013 and 2016.

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

This option skips the Active Directory authentication and authorization operations forthe user, and only sets the user as the NMM Exchange user account in the registry forbackup and recovery operations.

Note

This option should be selected when configuring an existing user in a parent and childdomain environment. See the section Example Admin user configurations on page26 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 or errormessages.

9. To verify that all the configurations are correctly set, run the System ConfigurationChecker.

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 of theExchange Servers security group.

Configuration

Configuring an Admin user 25

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

The user will be a member of the Organization Management group. The user will not be amember 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

Configuration


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

The user will be a member of the EMC Exchange NMM Admin Roles group. The user willnot 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

Configuration

Configuring an Admin user 27

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


3. In the Configure Admin User page, select the Configure Existing User option, enterthe User Name and Password, and select the Skip Active Directory Authenticationoption.


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

Procedure

1. Click Validate an existing Admin on the NMM Exchange Admin Configuration 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 click OK.

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

Results

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

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

Note

MAPI and Outlook cannot be installed on the same host.

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

Configuration


Table 5 Exchange Server GLR MAPI/CDO requirements (continued)

Exchange Server version Required MAPI/CDO version

Exchange Server 2013 MAPI/CDO 1.2.1 version 6.5.8320.0 or later

Exchange Server 2016 Not applicable

The Exchange Server 2010 and 2013 software does not include the MAPI client librariesand CDO. You can download these applications from Microsoft’s website. For informationabout downloading and installing this package, search for "Microsoft Exchange MAPIClient and Collaboration Data Objects" on the Microsoft Download Center website.

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

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

The Exchange consistency check verifies that the database and its corresponding set oftransaction logs do not contain errors, and validates Exchange before performing arestore. A consistency check can be configured to check the database and log files,database files only, or log files only. While a consistency check of only the database doesnot ensure complete consistency of the backup, it does offer the advantage of a shortertime to perform a consistency check. Exchange automatically runs a consistency checkagainst stand-alone databases and public folders before NMM restores the data.

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

The consistency check impacts Exchange backup performance. The larger the databasesand associated transaction logs, the longer it takes to run a consistency check. NMMprovides the option to run the consistency check on multiple databases in parallel.

Set the throttle limits according to the setup. The default value is 1000 milliseconds.Running simultaneous consistency checks without correctly setting the throttle limitsaffects the performance of the Exchange Server. In extreme cases, you notice that the I/Obottlenecks are so severe that consistency checks fail and other system operations areadversely affected.

In NMM, you can configure threading and throttling by using the corresponding -Aattribute values from the following table, in the Application Information field of the NMMclient. You can use these values to prevent performance issues during backup.

Table 6 Exchange application information variables for threading and throttling

Attribute name Value

NSR_ESE_UTIL_SEQUENTIAL Set to either of the following:

l True—To run Eseutil sequentially (singlethreaded).

l False—To run Eseutil in parallel againstmultiple storage groups (multi-threaded).

Configuration

Exchange Consistency Check 29

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

Attribute name Value

The default value is False with a value of 4maximum parallel threads. For example:NSR_ESE_UTIL_SEQUENTIAL=FalseYou can also specify the number of threads touse with the syntax. For example:NSR_ESE_UTIL_SEQUENTIAL=6.

NSR_ESE_UTIL_THROTTLE Set to either of the following:

l True—To allow Eseutil throttling.

l False—To prevent Eseutil throttling.

The default value is False.

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

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

NSR_ESE_CC_METHOD Specify whether to only perform the consistencycheck on the database and log files, databasefile only, or log files only.Set to one of the following:

l DB_AND_LOGSl DB_ONLYl LOGS_ONLYThe default value is DB_AND_LOGS.

Configuration


CHAPTER 3

Backup


l Planning backups..................................................................................................32l Preferred Server Order List.....................................................................................33l Configuring Exchange client resources.................................................................. 34l Configuring Exchange backups..............................................................................42l Example of a federated backup............................................................................. 48l Verifying a backup.................................................................................................49

Backup 31

Planning backupsThis section contains information to help you plan an Exchange backup.

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

l In a highly available DAG environment, schedule federated backups by using the DAGclient.

l After a backup of a data protection policy starts, you cannot interrupt or halt thebackup 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 after youhalt the backup. Any try to stop a backup in NMC takes a long time to complete.

l NMM only backs up mounted databases. If any databases are unmounted, NMMdoes not display notifications during the backup operation. The NMM log filesprovide details about unmounted databases.

Exchange backup prerequisites on page 22 provides details about backup prerequisites.

Backups in DAG environmentsWhen backing up active or passive database copies in the Exchange DAG environment,all DAGs use the federated backup method to best handle fail over scenarios. Thefederated 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 with a single save set without running aseparate backup of each node. Each Exchange server for which a backup job is sentperforms their backups in parallel with the other Exchange servers, resulting in fasterbackups.

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 physical clientsin the DAG, which can differ from the storage node defined in the Policy for the federatedbackup.

To configure remote storage for an Exchange DAG environment:

Procedure

1. On each mailbox server to back up, install the NetWorker client software with theStorage 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.

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:

Backup


a. Right-click Client and select Modify client.

b. On the Globals (2 of 2) tab, type the storage node name in the Storage Nodes 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 each asdisabled from the backup (clear the selection the Scheduled Backup checkbox).

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 selected poolcontains the storage node that is used for backup.

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

Backing up highly available Exchange serverIn a highly available DAG environment, you can schedule the federated backups by usingthe DAG name or the DAG node name as the client instance.

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.

Preferred Server Order ListWhen you perform a backup through the DAG resource using NSR_EXCH_BACKUP set toPassive or Preferred, NMM selects an Exchange server to back up the passive copiesof the databases. Because multiple Exchange servers can host replicas or passive copiesof the same database, you can specify a preferred server order list (PSOL) to tell NMMwhich Exchange servers to use to back up the Exchange databases. When the backupstarts, NMM backs up the passive or replica copies of each database from the ExchangeServers that the PSOL lists. You create the PSOL in the Client Configuration wizard, andthe PSOL is associated with a single DAG client resource.

If you choose to include stand-alone databases (including public folder databases orpublic folder mailboxes), the coordinating node determines whether they exist on thatserver and, if so, adds them to the save set list as well. The coordinating node then goesto another server in the list and repeats the check for passive and stand-alonedatabases. During this 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.

Backup

Backing up highly available Exchange server 33

Configuring Exchange client resourcesA client resource specifies what to include in a backup of an NMM client.

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

l Creating a client resource by using the Client Backup Configuration wizard on page35

l Creating a client resource for Exchange backups by using the NetWorker ManagementConsole on page 38

The following table describes how to determine the name to specify for the clientresource for DAG and stand-alone setups.

Table 7 Exchange Server name attributes

Type of backup Requirement

Stand-alone (including publicfolder databases andmailboxes)

Type one of the following:

l The FQDN of the NetWorker client computer.

l The hostname of the NetWorker client computer.

DAG Type the DAG name.

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

Table 8 Exchange Server 2010 save set names

Type of backup data Save set syntax

Writer level APPLICATIONS:\Microsoft Exchange2010

Database name level APPLICATIONS:\Microsoft Exchange2010\<Database name>







Backup






Creating a client resource by using the Client Backup Configuration wizardThis section describes how to create a client resource using the Client BackupConfiguration wizard.

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

Procedure

1. In the Administration view of NMC, select the Protection tab, and then from the menubar, right-click Clients and select New Client wizard.

Figure 7 Initial page of Client Backup Configuration wizard

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

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

l For stand-alone configurations, type the name of the client where NMM isinstalled.

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

Note

The DAG instance must have a cluster Administrative Access Point, that is, astatic IP address.Do not specify an IP address for a backup client name.

In the Client Name field, type either the short name or the FQDN that you usedto create the client.

Backup

Creating a client resource by using the Client Backup Configuration wizard 35

b. Select the Traditional type.

c. Click Next.

3. On the Select the Backup Application Type page, click the Microsoft Exchange Serverlisted under Available Applications and then click Next.

4. On the Specify the Client Backup Options page:

a. To use the Client Direct feature, then select the Client Direct checkbox.

The default setting is checked.

b. Leave the Target Pool field blank.

c. Select one of the following deduplication options:

l None if you have not configured data deduplication.

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

d. Click Next.

5. On the Select the Exchange Server Objects page, verify that the databases to back upare 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.

6. On the 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 copy isbacked up.

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

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

Note

When you select Active Backup or Passive Backup, the backup fails if the selectedtype of database does not exist.

Note

The Database Backup Options group is not displayed for Exchange stand-aloneservers.

b. For federated backup client backup configurations, in the Federated Optionsgroup:

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

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

Backup


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 up stand-alonedatabases and public folder mailboxes (Exchange Server 2013 and 2016), orpublic folder databases (Exchange Server 2010).By default, the Include Standalone and Public Folder checkbox is selected.

c. In the Consistency Check Options group, enable consistency checks by selectingthe Perform a consistency check during backup option and configure the followingsettings:

a. Select the Perform database consistency check during backup option tovalidate 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 the Exchange filessequentially instead of in parallel.

c. Select the Throttle Consistency Check option and then choose the Throttle I/OOperations and Throttle Duration options to manage the performance of theConsistency Check operation.You can configure the number of consistency check I/O operations to performbefore pausing and the length of time to pause between I/O operation cycles.

d. Click Next.

7. On the Select the NetWorker Client Properties page, optionally, type a comment forthe client in the Client Comment field. Click Next.

8. On the Specify the NetWorker Backup Group page:

a. Do one of the following:

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

l Select the Create a new group option to create a savegroup and configure thenew group as follows:

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

b. On the Client Retries menu, select 0.

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

d. Select the Automatically start the backup at the scheduled time option toautomatically start the scheduled backup at the designated time.

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

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

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

If you choose to create a group, the Specify the NetWorker Snapshot Policy pageappears in the wizard.

If the setup includes a storage node, the Specify the Storage Node Options pageappears in the wizard.

Backup

Creating a client resource by using the Client Backup Configuration wizard 37

Note

Changing the storage node option changes the configuration for all configurationsfor the client.

b. Click Next.

9. On the Specify the Storage Node Options page:

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

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

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

l Backup to the following storage nodes to select a specific NetWorker storagenode. Select one of the storage nodes listed.

b. Click Next.

10. On the Backup Configuration Summary page, review the details and do one of thefollowing:

l Click Back to revisit the previous pages.

l Click Create to configure the client resources.

11. On the Client Configuration Results page, review the output of the Client BackupConfiguration wizard and do one of the following:

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

l Click Finish.

Editing a client resource that was created by using an NMM 8.2.x or earlier releaseProcedure

1. In the Administration window, click Protection.

2. Right-click Clients in the navigation tree or right-click the required client in the Clientstable.

3. Select Modify Client Properties.

4. In the Backup Command field, delete the nsrsnap_vss_save command and type thensrnmmsv.exe command. This change must be performed for all the existing clientresources.

5. Make other changes, if required.

6. Click OK.

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

You can manually create an Exchange Server client resource by using the NetWorkerManagement Console.

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

Backup


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. Click the General tab.

5. In the General tab:

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

b. In the Comment attribute, type a description.

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

c. Clear the Block based backup option.

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

Place multiple entries on separate lines.

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

6. 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 and values. Ifyou specify more than one Exchange attribute at a time, then type each entry andits value on a separate line.

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

Table 11 Exchange Application Information attribute settings

Attribute name Description Values

NSR_EXCH_CHECK=value Specifies ifconsistencycheckshould berun or not fordatabases.

yes or noIf you do not specify a value, NMM applies thefollowing default values:

l Exchange Server DAG backup: no

l Exchange Server stand-alone backups: yes

If the value is no, then NMM indicates that theconsistency check is skipped in the backuplog files.

NSR_EXCH_DAG=<DAG name>

Optional, tospecify theDAG namefor a backupin a DAGenvironment.

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

Backup

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

Table 11 Exchange Application Information attribute settings (continued)


NSR_EXCH_BACKUP=active/passive/preferred or allNSR_EXCH2010_BACKUP==active/passive/preferred or all

To back upactive,passive,preferred, orall thedatabasecopies.

l Active—Back up only active databasecopies.

l Passive—Back up only passive databasecopies.

l Preferred—Back up only passive copy orreplica of each database if one isavailable. If no passive database exists,then the active database is backed up.

l All—Back up both active and passivedatabases.

NSR_EXCLUDE_COMPONENTS=db1,db2…

Excludesspecifieddatabasesfrom backup

Type the database name to exclude it from thebackup.

NSR_EXCH_INCL_SA Type False to exclude stand-alone databases

and public folder mailboxes (Exchange Server2013 and 2016), or public folder databases(Exchange Server 2010). The default setting isTrue.

NSR_FEDERATED_PSOL List of theorder inwhich toback up thedatabaseson eachserver in theDAG

Type a comma-separated list of the order inwhich to back up the databases on eachserver in the DAG. If you do not specify a list,the coordinating node distributes the backupsbased on an unordered list of Exchangeservers in the DAG.

Table 12 Examples for application variables

Configuration Examples for application variables

Exchange Serverstand-alonebackups

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

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>

Backup


Table 12 Examples for application variables (continued)

Configuration Examples for application variables

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 or

NSR_EXCH2010_BACKUP=<active/passive/preferred/all>

l NSR_EXCLUDE_COMPONENTS=<db1,db2… >

Note

Consistency check cannot be performed for incremental backups. Whenperforming consistency checks for Exchange logs during incremental backups, donot use the variable NSR_ESE_UTIL_DB_ONLY=yes in the Application Informationfield. Only use the NSR_EXCH_CHECK=yes variable.

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

Note

Consistency check cannot be performed for incremental backups. Whenperforming consistency checks for Exchange logs during incremental backups, donot use the variable NSR_ESE_UTIL_DB_ONLY=yes in the Application Informationfield. Only use the NSR_EXCH_CHECK=yes variable.

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

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

l If the deduplication node for this client’s backup data changes, the next backupthat is done must be a level 0 (full) backup. If the deduplication node for thisclient’s backup data changes, the next backup that is performed must be a level 0(full) backup.

7. Click the Globals (1 of 2) tab and complete verify that the Aliases attribute displaysthe NETBIOS name for the client.

This name is filled in automatically.

The NMM client uses the host computer NETBIOS or “short” name when connecting tothe NetWorker server to browse backups. If the NETBIOS name is not found, NMMdoes not display backups.

Backup

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

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

9. Click OK.

10. For DAG environments, create a NetWorker client resource for the following items:

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

l The DAG name that uses the FQDN.

Note

The DAG instance must have a cluster Administrative Access Point, that is, a static IPaddress.Do not specify an IP address for a backup client name.

In the Name field, type either the short name or the FQDN that you used to create theclient.

a. In the expanded left pane, select Clients.

b. From the File menu, select New.

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

d. In the Comment field, type a description.

Use this attribute to differentiate the purpose of each resource.

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

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.

i. Clear the selection for the default group.

No additional configuration is needed. The client resource only must exist.

Configuring Exchange backupsTo perform an Exchange Server backup, complete the following tasks:

1. Configure the backup storage resources.

2. Configure one or more client resources for each client by using either the ClientBackup Configuration Wizard or the Client Properties dialog box. ConfiguringExchange client resources on page 34 provides details.

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

4. Configure privileges as described in Configuring NetWorker administratorprivileges on page 44.

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

Backup


Backup configuration options

Table 13 Exchange Server backup options

Backup configuration Details

Only active databases backup on the server You can back up all the active database copiesresiding on an Exchange Server mailbox serverin a DAG environment. You can perform full andincremental backups. Active node backupsinclude stand-alone servers, public foldermailboxes (Exchange Server 2013 and 2016),and public folder databases (Exchange Server2010).

Only passive databases backup on the server You can back up all the passive databasecopies residing on an Exchange Server mailboxserver in a DAG environment. You can performfull and incremental backups, includingincremental backups of public folders. Passivenode backups do not include public foldermailboxes or public folder databases.

Both active and passive databases backup onthe server

You can back up both active and passivedatabases on Exchange Server mailbox serversin the DAG environment. You can perform bothfull and incremental backups.

Backup to a local storage node in a stand-aloneenvironment

You can configure a virtual client to direct itsbackups to the storage node on the physicalhost on which it resides. To configure a virtualclient, type curphyhost in the Storage Nodes

attribute of the virtual client. This variable is notsupported for DAG environments. The EMCNetWorker Administration Guide provides moreinformation about curphyhost.

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

You can perform Exchange Server databasebackups by using a remote NetWorker storagenode. The Exchange server and NetWorkerstorage node are on different computers in thenon-DAG environment. You can perform bothfull and incremental backups.NMM does not support server-based dedicatedstorage nodes in a DAG environment. Select Nofor the Dedicated storage node option in theDevice properties dialog box when configuringthe storage node in a DAG environment. Referto Configuring backups to use a remote storagenode in a DAG environment to use a remotestorage node in a DAG environment.

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

Backup

Backup configuration options 43

Configuring NetWorker administrator privilegesThe NMM client must be manually granted NetWorker administrator privileges to performmedia database operations during snapshot deletion.

NOTICE

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

You must complete the required steps to manually configure privileges.

Procedure

1. Open the NetWorker Administration GUI.

2. Click Server.

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

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

The Properties dialog box appears.

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

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

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

l Where a single user is granted administrator rights to perform all the NetWorkerfunctionality for a host, add the following values:user=administrator,host=NMM_calientproxy_hostuser=system,host=NMM_clientproxy_host

l Where multiple users are configured and added to an administrator group and thatgroup is added on the NetWorker privilege list, all the users under this group haveadministrator rights.To perform all the NetWorker functionality for a host, add the following values:

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

7. If the NMM client is installed in a cluster, grant NetWorker administrator privileges toeach of the following nodes:

l Cluster node (both active and passive nodes)

l Virtual server

8. Click OK.

All NMM users must have administrator level privileges.

Configuring a federated DAG backupYou can configure a federated DAG environment by using the Client Configuration wizardor by manually configuring the NetWorker client resources. To manually configure the

Backup


client resources, you must specify the Application Information attribute and provide abackup command for the virtual DAG name or the physical DAG nodes.

Manually configuring NetWorker client resources for a federated Exchange Server backup

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

The physical client resources of the DAG should be in the same protection Group as theDAG client resource. The physical client resources should have the Scheduled backupcheckbox cleared.

Procedure

1. Create a NetWorker client resource for each physical DAG node and the virtual DAGname.

2. Specify save set and Application Information attributes and add a backup commandunder the virtual DAG name.

3. Assign DAG client resource to the policy.

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

Table 14 Exchange Application Information attribute settings


NSR_EXCH_CHECK=value Specifies ifconsistencycheck shouldbe run or notfordatabases.

Yes or noIf you do not specify a value, NMM applies thefollowing default values:

l Exchange Server DAG backup: no

l Exchange Server stand-alone backups: yes

If the value is no, then NMM indicates that theconsistency check is skipped in the backup logfiles.

NSR_EXCH_DAG=<DAG name>

Optional, tospecify theDAG name fora backup in aDAGenvironment.

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

NSR_EXCH_BACKUP=active/passive/preferred or all

To back uponly activedatabasecopies.

l Active—Back up only active databasecopies.

l Passive—Back up only passive databasecopies.

l Preferred—Back up only passive copy orreplica of each database if one is available.If no passive database exists, then theactive database is backed up.

l All—Back up both active and passivedatabases.

Backup

Complete list of Exchange Server Application Information attributes 45

Table 14 Exchange Application Information attribute settings (continued)


NSR_EXCLUDE_COMPONENTS=db1,db2…

Excludesspecifieddatabasesfrom backup

Name of database

Viewing a valid application data save setWhen configuring a client resource, you must type the save sets in the Save Set attributeof the client resource.

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

Table 15 Commands for displaying valid application data save sets

Application server Command

Exchange Server stand-alone node At the command prompt, type:nsrnmmsv -PExample output:

“APPLICATIONS:\MicrosoftExchange 2010”“APPLICATIONS:\MicrosoftExchange 2010\Database 1”“APPLICATIONS:\MicrosoftExchange 2010\Database 2”“APPLICATIONS:\MicrosoftExchange 2010\ Database 3”“APPLICATIONS:\MicrosoftExchange 2010\ Database 4”68150:nsrnmmsv:nsrnmmsv:Exiting with success.This command only provides a list of databaseson the Exchange server from which you run thecommand.

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

nsrnmmsv -P

Exchange Server DAG At the command prompt, type the following onany node in the DAG:nsrnmmsv -ANSR_FEDERATED_BACKUP=yes -ANSR_EXCH_DAG=<DAG client> -P

Backup


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

Application server Command

Example output:

“APPLICATIONS:\MicrosoftExchange 2010”“APPLICATIONS:\MicrosoftExchange 2010\DB1”“APPLICATIONS:\MicrosoftExchange 2010\DB2”“APPLICATIONS:\MicrosoftExchange 2010\DB3”“APPLICATIONS:\MicrosoftExchange 2010\DB4”“APPLICATIONS:\MicrosoftExchange 2010\DB5”The output contains all databases in the DAG.The -v option does not apply.

Note

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

Note

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

URL encoding for Exchange save sets

When specifying save set names in the save set attribute of the client resource, you mustspecify some special characters, such as the backward slash (\), by their URL-encodedvalues.

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

Table 16 Special characters and their URL-encoded values

Special character URL-encoded value Special character URL-encoded value

\ %5C ? %3F

/ %2F ] %5D

" %22 [ %5B

% %25 } %7D

# %23 { %7B

& %26 ^ %5E

Backup

Viewing a valid application data save set 47

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

Special character URL-encoded value Special character URL-encoded value

< %3C ‘ %60

> %3E | %7C

When configuring a client resource, you must type the save sets in the save set attributeof the client resource. This section describes how to find the exact name of a particulardatabase, or Exchange Server instance and database combination that must be backedup during a scheduled backup.

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 the requiredvolumes, and select Required volumes.The Required NetWorker Volumes dialog box with details about the volume appears.

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

Circumstances that promote incremental or subsequent backups to full backupThe incremental or subsequent backups promote to full backups during the followingcircumstances:

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 and thelowest log number retrieved from the disk.

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

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, butcan have multiple passive or replica copies. In this example, there are two passive copiesof DB1: one copy is on two different Exchange servers (MBX2 and MBX3). The otherdatabases (DB2, DB3, and DB4) only have one passive copy each in the cluster. Only onecopy of each database must be backed up. The preferred server order list specifies toback up databases from the DAG in this order: MBX2, MBX3, and MBX1.

The figure below illustrates an example Exchange Server federated backup.

Backup


Figure 8 Example of an Exchange Server federated backup

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

Verifying a backup 49

Backup


CHAPTER 4

Mail Item Recovery


l Overview............................................................................................................... 52l Exchange recovery prerequisites........................................................................... 58l Configuring Exchange Server recovery................................................................... 59l Recovery procedures............................................................................................. 61l Best practices and recommendations....................................................................72

Mail Item Recovery 51

OverviewAn Exchange recovery can serve many different purposes. The smallest unit of granularityof a backup is an Exchange database, log files, and checkpoint files. Those backups canbe 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 Message-level recovery using the Exchange GLR option

Note

Exchange Server 2016 does not support GLR and RDB.The EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorkerModule for Microsoft with Ontrack PowerControls Technical Notes provides informationabout how to perform GLR of Exchange Server 2016.

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 unless yourecover to an RDB. See Recovering Exchange Server mailbox, public folder database, orpublic folder mailbox files on page 70.

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 on page 52 provides therecovery procedures. You can also use the PowerShell cmdlets to recover the data.

DAG recoveryA DAG backup provides access to backups of all Exchange databases through one NMMclient, although they came from multiple Exchange servers in the DAG. You perform therecovery to the Exchange server that is hosting the active database copy. The recoveryprocess to recover from a DAG backup is the same as a normal DAG recovery.

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

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. Whenyou recover entire databases, it overwrites the current content at that location with therecovered data. If you do not want to overwrite the current content, you can recover thedatabases to an alternate location on the same Exchange Server. You can recover theRDB and GLR data to a different Exchange Server. Use NMM GUI to browse mail foldersand locate individual messages.

The figure below illustrates a simple recovery of the Exchange databases in a stand-aloneExchange Server environment.

Figure 9 Recovery in a stand-alone Exchange Server environment

In a stand-alone environment, you can recover the data to an alternate MailboxDatabaseon the same Exchange Server. You can recover the RDB and GLR data to a differentExchange Server. Use NMM GUI to browse mail folders and locate individual messages.

Mail Item Recovery

Recovering Exchange data 53

Figure 10 Recovery to an alternate MailboxDatabase in a stand-alone Exchange Server environment

Recovering individual mailboxes, mailbox folders, and messagesRetrieving and restoring large backups can use much network, memory, processor, andstorage resources. Depending on the topology and architecture a site or organizationuses, the recovery operations might also affect production server performance, which canimpact 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 the existingdatabases or servers.

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

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

l Granular level recovery—NMM mounts the backup set to a virtual drive, where youcan browse the contents of the backup without actually moving or copying the data.NMM creates this virtual drive in minutes and does not require significant diskstorage space. You can browse and select the data from this virtual drive, as if youwere viewing the actual database, down to the message level. Only when you sendthe recovery request to the NMM server are actual items copied out of the backup setto the user’s mailbox. The recovered items are placed in a new Recovered itemsfolder in the user’s mailbox.The user can browse and select the items to keep, just like any other folder in theirmailbox. Using GLR saves you the time and space that is needed to browse the actualdatabase, and saves you time and resources by only retrieving the items that youselect, not entire databases.

Mail Item Recovery


l Recover to RDB—You can also recover databases to an RDB, and then browse thosedatabases to select mailboxes, user folders, or messages for recovery. When yourestore to an RDB, you can browse the database offline, on a separate server, or fromin a folder location that is separate from the online production Exchange server.While this method allows you to browse and retrieve items without overwriting thelive Exchange databases or user mailbox, recovery to an RDB does require diskspace, network resources, and processor resources to stage the databases in theRDB. When you recover to an RDB, it takes time to copy gigabytes or terabytes of datafrom one location to another. NMM recovers the backup to the RDB, then you canbrowse 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 55

Figure 11 Recover using NMM granular level recovery

Mail Item Recovery


Figure 12 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 57

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 Server data:

l Verify that the correct version of the Messaging API (MAPI) and Collaboration DataObjects (CDO) kit is installed. MAPI client and Collaboration Data Objects on page 28provides details.

l For each Exchange database to be recovered, you must select the This database canbe overwritten by a restore Exchange checkbox in the Exchange ManagementConsole.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 Server 2013and 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 level backupafter every recovery performed in Exchange Server. This does not apply to RDB orgranular restores.

Additional requirements for browsing mailboxesThe following topic describes the requirements for browsing Exchange RDB mailboxes.

l 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 Configuration tool.The logged in user must have a configured mailbox with at least one mail sent orreceived.

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

n For Exchange Server 2013:Writer: APPLICATIONS:\Microsoft Exchange 2013

Mail Item Recovery


Database: APPLICATIONS:\Microsoft Exchange 2013\Databasen For Exchange Server 2016:

Writer: APPLICATIONS:\Microsoft Exchange 2016Database: APPLICATIONS:\Microsoft Exchange 2016\Database

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

For DAG recovery, ensure that the database recovery node and state are correct. You mustperform the recovery to the DAG member server on an active node. The restoreddatabases must be in active state. Passive copies of the databases must be in Exchangereplication suspended state. If the copies are not in suspended state, then you mustmanually 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 was configured forbackup.

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 in theapplication toolbar.

4. From the left pane, select Exchange 2010 Recover Session, Exchange 2013 RecoverSession, or Exchange 2016 Recover Session and then select one of the following:

l Database Recover to view Exchange database backups and recover to RDB andperform either in-place recovery or alternate recovery from database backups. Thisis the default option for Exchange Server 2010 and 2013 and the only availableoption for Exchange Server 2016.

l RDB Mailbox Recover to browse and recover mailbox items from existing RDBdatabases.

l Granular Level Recover to browse and recover items from databases without firsthaving to restore the database to an RDB.

Mail Item Recovery

Additional requirements for recovering databases in a DAG 59

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 Exchange transactionsthat occurred after the time of backup, select Include existing logs (Roll forwardrecovery).

l To recover data for Exchange Server up to the time of backup only and to notinclude subsequent transactions, select Include logs only from this restore (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 after restore.

l To recover the database and transaction logs from the backup without trying toreplay the transaction logs, select Do not replay the transaction logs. Thedatabase also cannot be mounted after the restore. If you select this option, youmust manually replay the transaction logs by running the Exchange utilityeseutil.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 mount drop-downlist.

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

8. From the navigation tree, expand the folder Microsoft Exchange 2010, MicrosoftExchange 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, orExchange 2016 Recover Session toolbar, click Recover.

Configuring roll-forward recovery of an Exchange server in a DAG environment

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 a shellscript to determine the DAG member where the active copy of the database resides.

The topic Additional requirements for recovering databases in a DAG on page 59provides additional details.

2. In the Exchange Management Console or Exchange Administrative Consoleapplication, select the This database can be overwritten by a restore checkbox.

3. In the Exchange Management shell, stop replication of any passive copies of thedatabase with the suspend-MailboxDatabaseCopy command.

The topic Additional requirements for recovering databases in a DAG providesadditional details.

For example:

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

Mail Item Recovery


4. Open the NMM client.

5. Select the NetWorker Server on which the NMM client software was configured forbackup.

6. On the main toolbar, select the Client drop-down list, and then select the client that isthe Exchange DAG.

7. From the left pane, select Exchange Recover, and then select Database Recover toview Exchange database backups.

8. Click View and then click Refresh.

9. From the navigation tree, expand the Microsoft Exchange 2010 or the MicrosoftExchange 2013 folder.

10. Select the Exchange Server items that you want to restore.

You can select more than one database for recovery. You can select backups of activeor passive databases for recovery.

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

The Exchange Recovery Options Summary dialog box appears.

12. Review the options:

l If you must change the options, click Recover Options. This opens the ExchangeRecover Options dialog box, where you can change settings on the General,NetWorker, Security, and Exchange tabs.

l If the summary does not show that it is a Roll-forward recovery, then click RecoverOptions, go to the Exchange tab, and in the Transaction Log File Replay dialogbox, verify that Include existing logs (Roll-forward recovery) is selected. This is thedefault setting, but it might have been changed if the previous recovery was apoint-in-time recovery.

l If the options are okay, click the Start Recover button. This closes the ExchangeRecover Options dialog box and starts the recovery.

13. Click Restore.

14. After the restore operation completes, restore replication between the nodes with theresume-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.

Recovering NetWorker Module for Microsoft Exchange backupsNetWorker Module for Microsoft Exchange (NME) and NMM cannot be installed on thesame client. NME and NMM use some of the same binaries for item level browsing andrecovery, so running both NME and NMM on the same client causes versioning conflictsfor the common binaries.

Mail Item Recovery

Recovery procedures 61

To recover NME data after migrating from NME to NMM, perform the following steps:

Procedure

1. Uninstall NMM, leaving the NetWorker client software running.

2. Install NME.

3. Recover the NME data.

4. Uninstall NME.

5. Re-install NMM.

Mounting the database after 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 database isrequired and if an automatic mounting of the database must be done after the restore iscomplete:

l If this option is specified, then the database is mounted after the successful restoreof the Exchange Server.

l If this option is disabled, then the administrator must manually mount the database.By default, this option is enabled in NMM.

The EMC NetWorker Module for Microsoft Administration Guide describes how to select ordisable 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.

Procedure

1. From the left pane, select Exchange Recover Session, and then select one of thefollowing:

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

l RDB Mailbox Recover—Select to browse and recover Exchange Server items fromexisting RDB databases.

l Granular Level Recover—Select to browse and recover items from databaseswithout 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 wanted backup.The EMC NetWorker Administration Guide provides details.

5. Select Recover in the taskbar.

Mail Item Recovery


NOTICE

Always perform a full backup after performing a point-in-time or roll-forward recovery.

Performing an advanced recoveryIn NMM, you can click Recover Session > Advanced Recover to recover a database to oneof the following:

l A selected Recovery Database (RDB)—Exchange Server 2010 Service Pack 1, Rollup 6or later, Exchange Server 2013, and Exchange Server 2016 support the ability torestore data directly to an RDB. Mounting the recovered data as an RDB allows you torestore individual mailboxes or individual items in a mailbox. Public folders cannotbe 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 active databaseresides. The remote database recovery option is only available for Exchange ServerDAGs 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 Exchange AdministrativeConsole (EAC), or a shell script to determine the DAG member where the activecopy of the database resides.

b. Log in to the Exchange member that is running the active copy of the database thatis to be recovered.

c. From the EMC, open the database properties and select the This database can beoverwritten by a restore checkbox.

2. Suspend all passive copies of the database that are to be recovered.

The topic Additional requirements for recovering databases in a DAG on page 59provides details.

3. From the left pane, select Exchange Recover Session, and then select DatabaseRecover (default).

4. Select the DAG name for the client on which the NMM client software was configuredfor backup.


6. Select the DAG database to be recovered.

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

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

The Advanced Recovery dialog box appears. The Steps group lists the three steps forrecovery:

Mail Item Recovery

Performing Exchange Server recovery 63

l Select Recovery

l Select DB & Server

l Summary

Figure 13 Advanced Recovery dialog box

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

8. In the Select Recovery Type group, under Recovery Type, select one of the followingchoices and click Next:

l Recovery Database (RDB) Recovery—The topic Recovering to a recovery database(RDB) on page 64 provides the remaining steps of the procedure.

l Alternate Database Recovery—The topic Recovering to an alternate database onpage 67 provides the remaining steps of the procedure.

l Remote Database Recovery—The topic Recovering to a remote database on page67 provides the remaining steps of the procedure.

9. The Exchange Recovery Summary dialog box appears. This dialog box lists theExchange Server Recovery options, the NetWorker Recovery Options and allows you toreview the details before continuing.

Figure 14 Exchange Recovery Summary dialog box

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, orExchange Server 2013 is installed. The following recovery configurations are possible:

Mail Item Recovery


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 of theDAG 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 roles onthe same server.

In a multi-tenant environment, an administrator is created for each tenant. But when theuser logs in as a domain administrator and performs RDB browsing, there is a conflict innames due to existence of more than one administrator. To work around this issue, createa user (for example, NMMBackupUser) and add this user as member of the OrganizationManagement group to each of the tenants.

RDB browsing fails if the user credentials that are used for the operation have an Alias inActive Directory. In this situation, you must create a user (without an Alias) and installNMM with the credentials of the new user. Provide the necessary permissions and usethe user account for RDB browsing operations.

Performing an RDB 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 andclick Next.

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

Figure 15 Manage RDB dialog box

3. To create an RDB, click Create.

The Create RDB dialog box appears.

Mail Item Recovery


Figure 16 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 new RDB.

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 database logspath and Mailbox databases that reside on the same volume could not be stored inthe 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) List and clickDelete.

Figure 17 Delete confirmation dialog box

l Unmount a RDB—If an RDB is mounted but you are getting an error during recovery,you can unmount the RDB and then re-mount the same or another RDB forrecovery.

To unmount an RDB, select the RDB from the Recovery Database (RDB) list andclick Unmount.

l Mount a RDB—Select an RDB from the Recovery Database (RDB) List and clickMount.

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 the current nodeor if replication is on, then the recovery fails.

l Overwrite a RDB—Select an RDB from the Recovery Database (RDB) List and clickRDB Overwrite.

Mail Item Recovery


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 of recovery,the backed up Mailbox database is recovered to a new database other than the originalMailbox database. Alternate database recovery is supported in both Exchange Serverstand-alone and DAG environments.

Procedure

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

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

Figure 18 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 allows you toreview the details before continuing with recovery.

3. To continue with recovery, click Start Recovery.

Recovering to a remote databaseBy performing remote recovery, you can start roll-forward or PIT recovery from a mailboxserver that is not actually mounted. After remote recovery is started from DAG memberserver where the Mailbox database is not mounted (the Mailbox database with thepassive copy) the recovery service nsrsnap_vss_recover.exe is automaticallystarted in the DAG member server on the Mailbox database with the active copy.

Note

Remote database recovery is supported only in a DAG environment. You cannot perform aremote recovery to a host that is not a part of DAG.

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

Mail Item Recovery


Figure 19 Select Server dialog box

2. Select the database to which you want to perform the recovery and click Next.The Exchange Recovery Summary dialog box appears. This dialog box lists theExchange Server recovery options and the NetWorker recovery options and allows youto review the details before continuing with recovery.

3. To continue with recovery, click Start Recovery.

Accessing archive mailboxes in Recovery Databases

Microsoft does not support access to archive mailboxes in the RDB through MAPI. AMAPI_E_FAILONEPROVIDER (0x8004011d) error occurs when a MAPI applicationtries to log in. You can work around this by using the New-MailboxRestoreRequestcmdlet to restore data from the archive mailbox in the Recovery Database.

Procedure

1. Get the archive mailbox GUID from the get-mailbox cmdlet for the user whosearchive mailbox you want to restore. For example, in PowerShell:

C:\>Get-Mailbox <alias> | Fl Name, Archive*...ArchiveGuid : <GUID>

2. Run the New-MailboxRestoreRequest cmdlet. For example, in PowerShell:

C:\>New-MailboxRestoreRequest -RecoveryDatabase <Recovery DatabaseName> -RecoveryMailbox <GUID> -TargetFolder <Target Folder Name> -Identity <alias>

Results

This restores the mailbox data back to a live mailbox, where the user can work with it.

The Microsoft TechNet article “Restore-Mailbox” 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, or publicfolder mailboxes

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

l Exchange Server mailbox databases

Mail Item Recovery


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

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

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 recover theseitems so that you can perform data mining for Exchange public folder mailboxes or publicfolder databases with third-party tools.

Procedure

1. In the NMM user interface, select the NMM client and then use the Recover > ExchangeRecover Session > Database Recover option to recover the deleted database.

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

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

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

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 the third-party tools such as, Kroll OntrackPowerControls.

EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorker Modulefor Microsoft with Ontrack PowerControls Technical Notes provides information.

Performing a quick recovery of a deleted mailboxThe procedure to recover a deleted mailbox is performed independent of NMM backup orrecovery 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 then select theuser 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.

Mail Item Recovery

Performing a quick recovery of a deleted mailbox 69

NOTICE

Re-created deleted mailboxes are not always immediately visible. It might take from15 minutes to an hour before the mailbox is visible and accessible through Outlook.

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

You can use NMM and third-party software, such as Ontrack PowerControls, to perform agranular recovery of Exchange Server mailbox or public folder databases or mailboxdatabase items. The procedure varies depending on the method you use. The recoveryprocess is the same for all supported versions of Exchange Server, although the backupsave sets and application information vary depending on the version Exchange Serveryou use.

Procedure

1. Use NMM to back up the database.

2. Use NMM to perform a flat file recovery of the database by performing one of thefollowing procedures:

l To recover files from a network location: Recovering Exchange Server mailboxes,public folder databases, or public folder mailboxes from a network location onpage 70.

l To recover files to a remote computer: Recovering Exchange Server mailboxes,public folder databases, or public folder mailboxes to a remote computer on page71.

3. Use third-party software, such as Ontrack PowerControls, to perform a granularrecovery of the Exchange flat files.

The third-party tool documentation provides information about Exchange flat files.

Recovering Exchange Server mailboxes, public folder databases, or public folder mailboxes from anetwork location

With a third-party tool, such as Ontrack PowerControls, you can use the files in thesefolders to perform an item-level recovery to a target user mailbox that is in production.

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 DAG clientwhere 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 for recovery.

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

7. Click the Exchange tab.


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

Mail Item Recovery


10. Click OK.

11. Start the flat file recovery of the database by selecting the mailbox, public folder,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 files recovered asexpected 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 named ExchangeDataFilePath.

With a third-party tool, such as Ontrack PowerControls, you can use the files in thesefolders to perform item-level recovery to a target user mailbox that is in production.

Procedure

1. On the remote computer that you 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 the folderyou created on the remote computer. For example, Z:\ is a mapped network drive onthe DAG node, and Z:\ points to E:\folder on the remote computer.

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, click theRefresh button.

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

7. Click OK.

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

9. From the left pane, select Recover, select Exchange 2010 Recover Session, Exchange2013 Recover Session, or Exchange 2016 Recover Session and then select DatabaseRecover.

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 you want torecover and click Recover Options.

11. Click the Exchange tab.


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

14. Click OK.

15. After the flat file recovery completes, verify that NMM recovered the logs and .edb filesto the folder you created.

Mail Item Recovery

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

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 Exchange Server,you cannot recover these objects until you perform disaster recovery. Objects fromthe Exchange Server should not be deleted unless they no longer must 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. To ensure thatyou can recover all Exchange data to the point-in-time of the upgrade, perform a fullbackup of Exchange data immediately after upgrading to the NMM client.

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 that youcan perform roll-forward recovers.

Mail Item Recovery


CHAPTER 5

Granular Level Recovery


l Recovering Mailbox items with GLR....................................................................... 74l Recovering individual mailbox items using GLR..................................................... 75l Performing a GLR to an alternate mailbox.............................................................. 76l Performing a GLR on an archive user mailbox........................................................ 77l Performing a GLR to a PST......................................................................................78

Granular Level Recovery 73

Recovering Mailbox items with GLRIn a conventional Exchange database restore, entire databases are replaced or restored.Retrieving large backups and restoring them can use significant network, memory,processor, and storage resources and might also affect production server performance.

NMM supports Granular Level Recovery (GLR) so that you can restore individual itemswithin an Exchange database, such as individual user mailboxes, mailbox folders, andmessages. Individual folders can be browsed and selected from the restored data, andthen restored to the individual’s mailbox.

NMM mounts the backup set to a virtual drive, where you can browse the contents of thebackup without actually moving or copying the data. During the mount process, NMMcopies required log files from the server. The virtual drive is created quickly and does notrequire any significant amount of disk storage space. You can browse and select therecovered data from this virtual drive as if you were viewing an actual recovery database,down to the folder level.

Only when you send the restore request are actual items copied out of the backup set tothe user’s mailbox. The items are placed in a folder in the user’s mailbox that is calledRestored Items, where the user can browse and select the items to keep - just like anyother folder in their mailbox. Using GLR saves you the time and resources that are neededto browse the actual database and retrieves only the items you selected.

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 select individualmailboxes 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 Stage operation.Closing the NMM GUI should remove the GLR RDB.

The NetWorker Module for Microsoft Administration Guide provides more information aboutGLR.

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

l NMM does not support GLR for Exchange Server 2016 backups.l NetWorker Server 9.0 must be installed on the NetWorker server.l You must have backed up the writer set or the database or storage group save set

with a GLR-compatible version of NMM 9.0 or later:

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 writer:APPLICATIONS:\Microsoft Exchange 2013

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

l The backup must be a full backup. Incremental backups are incompatible withExchange GLR.



l Public folders or objects cannot be recovered using GLR. For this reason, they are notdisplayed in the list of folders available for GLR.The GLR can be performed on 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 a significantamount of time to display these items. In this case, do one of the following:

n Restore the entire folder using Exchange GLR without browsing into it.

n Restore the database to the RDB and then browse from there.

l In firewall-enabled environments, you must provide firewall exceptions for theWindows Remote Management services:

1. Click Start, point to Administrative Tools, click Windows Firewall with AdvancedSecurity, 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 Disable Rule.

Recovering individual mailbox items using GLRThe 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. To recover adifferent version of the selected database, repeat step 5 on page 75 through step 11on page 106 on page 76. Changing to a different version dismounts the currentlymounted virtual drive. NMM creates a virtual drive with data from the newly selecteddatabase.

Procedure


2. In the host menu, select the NetWorker client on which the NMM client software wasconfigured for backup.

3. If the NMM client is part of a DAG, select the virtual client name of the DAG to whichyou are recovering data. You can select the virtual client from the client list attribute inthe application toolbar.

4. From the left pane, select Recover, select Exchange Recover Session, and then selectGranular Recover.

5. Select the mailbox database to recover.

Figure 20 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 of thesave set that is GLR-compatible. To select a GLR-compatible save set:


Recovering individual mailbox items using GLR 75

a. Click Yes.

b. Select a backup from the list of backups.

c. Check the Use selected item backup time as new browse time checkbox andthen 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’s mailbox.Figure 21 Sample mailbox

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

Performing a GLR to an alternate mailboxYou can recover of individual mailbox items, including folders, from any number of activeusers to any other active user in the Exchange organization. Recovery is not supported fordeleted users.

Note

Folder names containing / and \ are not recovered.

When you recover to an alternate mailbox, NMM creates a Recovered Items folder underthe root of the alternate mailbox. Inside this Recovered Items folder, NMM creates subfolders 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-DDhh:mm:ss, where YYYY-MM-DDD hh:mm:ss indicate the date and time of the recovery.Inside that folder, NMM creates sub-folders for each user, for example UserYY andUserZZ, and re-creates each user’s respective folder structure and mail items.

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.

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 mailboxThe 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 archive mailboxusing 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 -RecoveryDatabaseRDB-arch -RecoveryMailbox 3daa752d-a77c-47b7-ad6e-5a2aa6ee2579 -TargetFolder arch-folder -Identity arch2

6. Confirm that you want to perform the recovery.


Performing a GLR on an archive user mailbox 77

Performing a GLR to a PSTYou can recover a user mailbox from any active user in the Exchange organization andplace the recovered mailbox items in a PST. Recovery is not supported for deleted users.

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 of thefollowing:

Option Description

RDB MailboxRecover (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 LevelRecover

Browse and recover items from databases without first having torestore the database to an RDB. Select this option if no RDBcurrently exists.

Note

Database Recover overwrites existing production mailboxes, which does not producethe correct results.


4. Select the database in the NMM user interface.

If the database is not listed, select a browse time that includes the wanted backup.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 PST filedoes not have to exist, but the NMM GUI must be able to write to the target location.

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 in theExchange Recover Options dialog box.

Due to a Microsoft restriction, NMM does not support PST recovery for a single mailitem.



If no PST file is specified, then the items that are selected for recovery are recovered tothe production server.

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


Performing a GLR to a PST 79

CHAPTER 6

Troubleshooting


l Troubleshooting general errors..............................................................................82l Troubleshooting backups......................................................................................82l Troubleshooting recovery...................................................................................... 84

Troubleshooting 81

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

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

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 must restorethe original (source) mailbox to an alternate (target) mailbox by running the New-MaiboxRestoreRequest or Restore-Mailbox PowerShell cmdlet. Microsoftprovides a full list of syntax and parameters for these cmdlets.

Solution

Table 17 PowerShell cmdlets 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

Troubleshooting





Table 17 PowerShell cmdlets for restored mailboxes (continued)

Exchange version PowerShell cmdlet Microsoft website

Exchange Server 2010 Restore-Mailbox https://technet.microsoft.com/en-us/library/bb125218.aspx

The following examples show the New-MaiboxRestoreRequest and Restore-Mailbox cmdlets with sample parameters:

l Exchange Server 2010 SP1 or later and Exchange Server 2013 CU1 or later andExchange Server 2016:New-MaiboxRestoreRequest -SourceDatabase <RDBNAME> -SourceStoreMailbox <GUID_OF_MAILBOX_YOU_WANT_TO_RESTORE> -TargetMailbox <ORIGINAL_USER_MAILBOX> -Targetrootfolder<Folder_to_restore_into> allowlegacydnmismatch $true

l Exchange Server 2010:Restore-Mailbox -Identity <ALTERNATE_USER_MAILBOX> -RecoveryDatabase GLR20120320131224 -RecoveryMailbox<ORIGINAL_USER_MAILBOX> -IncludeFolders \Inbox -TargetFolderRECOVERY

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 log thatthe Microsoft Exchange Replication service VSS Writer failed. However, this conditionmight be temporary. If this backup failure and error occur, there are two solutions.

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. EMCplans to fix this in a future release.

MAPI browsing fails in Client Access Server (CAS) array or Network Load Balancing (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 NMM userinterface. The failure might be due to the NLB configuration, NLB type, firewall setup, orother error.

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

Troubleshooting

Troubleshooting backups 83

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



Unhandled exception occurs during item-level recovery for Exchange Server 2010 GLRRDBWhen performing item-level recovery to an alternate user mailbox for Exchange Server2010 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 GLR failing due to error with registry keysIf you try to perform GLR after upgrading to a newer version of NMM, the operation mayfail. To resolve this issue, delete the following MAPI profile registry keys in the followingorder:

1. HKEY_LOCALMACHINE\Software\Legato\NetWorker\RecoverOptions\MapiProfile

2. HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\LegatoNetWorker

After deleting these registry keys, GLR operations should complete successfully.

Exchange Server 2010 RDB alternate mailbox item-level recovery is failing with errorAlternate mailbox item-level recovery for Exchange Server 2010 RDB is failing with error:

An unspecified error has occurred. 1 0 19 E_FAIL.SolutionThe target user must log in to the mailbox through the Outlook Web Application and senda few test mails, and then perform item-level recovery to target user mailbox.

Unhandled exception occurs during item-level recovery for Exchange Server 2010 GLRRDBWhen performing item-level recovery to an alternate user mailbox for Exchange Server2010 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 after failedrecoverySometimes, 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.

Troubleshooting


In Exchange Server 2010, RDB item level recovery fails with “insufficient permissions toaccess 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 error message:

Insufficient permissions to access mailbox

SolutionTo browse the contents in RBD, ensure that the mailbox database where the currentlylogged in user mailbox resides is mounted. MAPI communicates with the RDB mailboxthrough the currently logged in user mailbox.

For example, if the user is logged in as Administrator, the mailbox database that containsthe 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 with NMM.This mailbox is created by default. Sometimes, the Active Directory entry for this mailboxbecomes 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 a mailbox.


1. Manually remove all Exchange Active Directory entries for the administrator by usingADSI 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 recover thebackup.

Alternate storage group directed recovery with different Exchange versions displayserror message while mounting the databaseYou must use the same version of Exchange Server for both backup and recovery. If youback up an Exchange database from one version of Exchange Server (for example, adatabase from Exchange Server 2010), but perform recovery of the same database fromanother Exchange Server version (for example, using Exchange Server 2013), the recoveryis successful. However, while mounting the database, the following error message isdisplayed:

Database "<Storage Group\Database>" is too new to be upgraded.SolutionEnsure that the same version of Exchange database is used for both backup andrecovery.

Troubleshooting

Troubleshooting recovery 85

Troubleshooting


emc networker module for microsoft for exchange · pdf fileemc networker module for microsoft...

Documents