EMC NetWorker Module for Microsoft for Exchange Server VSS

(1)

EMC

®

NetWorker

®

Module for

Microsoft for Exchange Server

VSS

Version 9.0

User Guide

302-001-753

(2)

Published October, 2015

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

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

EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC Corporation

Hopkinton, Massachusetts 01748-9103

(3)

5 7 9

Introduction 13

Overview... 14

Stand-alone and single Exchange Servers... 14

Exchange Server DAGs... 14

High availability in Exchange Server... 16

Active and passive nodes and databases...16

Using NMM in an Exchange Server environment... 17

Exchange Server 2010 VSS Writers...17

Exchange Server 2013 and 2016 VSS Writer...18

Compatibility with previous Exchange backups... 18

Backup initiated transaction log file truncation... 18

Backup types and levels...19

Federated backups...19

Recovery types... 19

Exchange Server Block Based Backup... 20

Configuration 21 Supported Exchange server deployment scenarios and limitations...22

Supported Exchange Server versions...22

Single server Microsoft Exchange Server and Microsoft SharePoint Server installations... 22

Delivery status notifications (DSNs) for Exchange server DAG environments...23

Exchange backup prerequisites...23

Exchange administrator configuration tool... 23

Required permissions... 25

MAPI client and Collaboration Data Objects...26

Exchange Consistency Check... 26

Consistency check parameters for threading and throttling... 26

Backup 29 Planning backups...30

Backup considerations...30

Backups in DAG environments... 30

Configuring backups to use a remote storage node in a DAG environment... 31

Exchange Information Store backup... 31

Backing up highly available Exchange server...32

Shadow copy and log truncation... 32

Preferred Server Order List...32

Figures Tables Preface Chapter 1 Chapter 2 Chapter 3

FIGURES

(6)

(7)

Revision history... 10

Style conventions... 11

Writers used by NMM for Exchange Server backup and recovery... 17

NMM support for highly available Exchange server... 22

Permissions configured by the Exchange administrator configuration tool ... 24

Permissions configured by the Exchange administrator configuration tool ... 25

Exchange application information variables for threading and throttling ... 27

Exchange Server name attributes ...33

Exchange Server 2010 save set names... 33

Exchange Server backup options... 40

Exchange Application Information attribute settings... 43

Commands for displaying valid application data save sets... 44

Special characters and their URL-encoded values... 45

PowerShell cmdlets for restored mailboxes...80 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

TABLES

(8)

(9)

Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions that are described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC technical support professional if a product does not function correctly or does not function as described in this document.

Note

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

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

Note

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

Audience

This guide is part of the NMM documentation set, and is intended for use by system administrators during the setup and maintenance of the product. Readers should be familiar with the following technologies used in backup and recovery:

l EMC NetWorker software

l EMC NetWorker data protection policy management l Microsoft Volume Shadow Copy Service (VSS) technology

(10)

Revision history

The following table presents the revision history of this document.

Table 1 Revision history

Revision Date Description

02 October, 2015 Updated the following sections:

Section "Compatibility with previous Exchange backups" in the Introduction chapter.

Section "Creating a client resource using the Client Backup Configuration wizard" in the Backup chapter. 01 September, 2015 First release of this document for EMC NetWorker Module

for Microsoft release 9.0.

CHAPTER 1 Introduction

This chapter includes the following sections:

l Overview... 14 l Using NMM in an Exchange Server environment... 17

(14)

Overview

The EMC® NetWorker® Module for Microsoft (NMM) release 9.0 software supports backup and recovery for Exchange Server 2010, 2013, and 2016 recovery databases (RDBs) in stand-alone and DAG configurations.

Note

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

Stand-alone and single Exchange Servers

This topic describes the relationship between stand-alone and single Exchange Servers to NMM.

In a stand-alone or single Exchange Server environment, all mailbox databases, log files, and checkpoint files reside on one server.

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

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

Exchange Server DAGs

This topic describes the relationship between Exchange server database availability groups (DAGs) and NMM.

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

l Install the NetWorker and NMM clients on each Exchange server that has the mailbox

role installed.

l You can replicate each Exchange database to multiple Exchange servers, with a

(15)

l For Client Direct file access (DFA) backups, each client resource that you create on the

NetWorker server for the Exchange client can contain a maximum of ten mailbox databases. For example, an Exchange server that contains 20 databases requires two client resources that contain ten databases each.

The NetWorker Module for Microsoft Administration Guide provides additional information about DFA.

l When there are multiple copies of a database, only one copy of the database is active

at a time. The remaining copies are passive.

l You can back up active copy mailbox databases, passive copy mailbox databases,

and standalone databases.

l “Standalone” applies to an Exchange Server mailbox database that is not replicated

across multiple servers, including and public folder mailboxes and public folder databases.

l You can only restore backups of databases in a DAG environment to active database

copies.

Information about Exchange DAG architecture is available on the Microsoft TechNet website.

Due to a Microsoft limitation, NMM does not support backups of Exchange Server 2013 and 2016 DAGs with cross-domain servers. The following Microsoft technical note provides more information about this limitation: http://

technet.microsoft.com/en-us/library/dd979802.aspx.

The Exchange Server 2010 equivalent for this limitation is available on the Microsoft TechNet website.

Introduction

(16)

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

Configuring Exchange backups on page 40, provides information on configuring a DAG backup after you install the NetWorker and NMM clients on each Exchange server in the cluster.

High availability in Exchange Server

Most larger enterprises typically deploy Exchange Server in some form of high-availability configuration. Exchange Server 2010, 2013, and 2016 typically includes the use of DAGs and mailbox database copies. You do not need to install and configure any Windows clustering before you install Exchange Server. You can add high availability to the Exchange Server environment after you deploy Exchange Server without having to uninstall Exchange Server and then reinstall in a high-availability configuration. These improvements in high availability and site resilience functionality also simplify

installation and configuration of the NetWorker and NMM clients for backup and recovery.

Active and passive nodes and databases

The following topic describes NMM installations with Exchange server clustered environments.

(17)

active copy. You designate individual databases, not nodes, as active or passive. This allows you to have a mix of active and passive databases on each node.

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

Figure 3 Exchange Server DAG environment

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

Using NMM in an Exchange Server environment

This section provides information for using NMM in an Exchange Server environment, for example supported backup and recovery types, VSS writers, and compatibility with previous Exchange backups.

Exchange Server 2010 VSS Writers

This 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 these writers during backup and recovery. The following table provides details.

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

Application writers Description

Information Store Writer

This writer is built into the Exchange Information Store, is available on any mailbox server, and is responsible for backup and recovery of active databases.

Replication Service Writer

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

The Replication Service Writer supports backup functionality for a selected database where the shadow copy is taken against the

Introduction

(18)

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

Application writers Description

replicated instance of the database and transaction log files. You can use the Information Store Writer to restore Replication Writer backups to the active database location.

Exchange Server 2013 and 2016 VSS Writer

This topic describes the Exchange Server 2013 and 2016 writer used for active and passive 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 during backup and recovery. This writer is used by Exchange Server-aware VSS-based

applications to backup active and passive database copies, and to restore backed up database copies. Although this new writer runs in the Microsoft Exchange Replication service, it requires the Microsoft Exchange Information Store service to be running in order for the writer to be advertised. As a result, both services are required in order to backup or restore Exchange Server databases.

Compatibility with previous Exchange backups

You can use NMM 9.0 to recover VSS backups created by using NMM 8.2.x and earlier release for Exchange Server.

The NetWorker Module for Microsoft Install Guide provides information about the "Restore of NMM 8.2.x and Earlier Backups (VSS workflows)" option in the installer. The NetWorker Module for Microsoft Administration Guide provides the information on editing client resources that were created using NMM 8.2.x and earlier release, and information about the NetWorker Management Console bulk edit feature.

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

If you want to upgrade the Exchange server version you are currently using, including Exchange Service Pack upgrades, perform a full backup before the upgrade. You must also do a full backup after upgrading.

You cannot recover data from a previous Exchange service pack to an Exchange server that runs a later service pack version. For example, if you have Exchange Server 2010 installed on a Windows Server environment and you want to upgrade to Exchange Server 2013:

1. Perform a full backup on Exchange Server 2010. 2. Upgrade to Exchange Server 2013.

3. Perform a full backup on Exchange Server 2013.

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

Backup initiated transaction log file truncation

This 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 truncate transaction logs. NMM notifies the Exchange writer that a backup has completed

(19)

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

l In stand-alone configurations, the Exchange Writer truncates the transaction log files

at the completion of successful full or incremental backups.

l In DAG configurations, the Replication service delays the log truncation until all

necessary log files are replayed into all other copies. The Replication service deletes the backed up log files both from the active and the passive copy log file paths after the Replication service verifies that the to-be-deleted log files have successfully been applied to the copy database and both active database and the database copies checkpoint has passed the log files to be deleted.

Backup types and levels

NMM 9.0 and later supports BBB full and incremental backups of stand-alone and DAG Exchange Server setups. A BBB full backup is a complete backup that archives every selected database and all necessary log files. After the backup completes, log files older than the checkpoint taken at backup start time are deleted. If you perform a full backup on a daily basis, you can prevent log files from consuming space on the hard disk. A BBB incremental backup backs up only the changed blocks of every selected database and all necessary logs. Like a BBB full backup, log files older than the checkpoint are deleted once the backup completes. The EMC NetWorker Module for Microsoft Administration Guide

provides details.

Federated backups

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

Recovery types

This 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

Introduction

(20)

Exchange Server Block Based Backup

Exchange Server Block Based Backup (BBB), the default backup method for NMM 9.0and later, enables faster backups and recoveries. For details on BBB, refer to the EMC

(21)

CHAPTER 2 Configuration

l Supported Exchange server deployment scenarios and limitations...22

l Exchange backup prerequisites...23

l Exchange administrator configuration tool... 23

l Required permissions... 25

l MAPI client and Collaboration Data Objects...26

l Exchange Consistency Check...26

(22)

Supported Exchange server deployment scenarios and

limitations

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

The NetWorker Online Software Compatibility Guide, available on the EMC online support website at http://compatibilityguide.emc.com:8080/CompGuideApp, provides the most up-to-date and accurate listing of hardware, operating system, service pack, and

application versions that the NMM client supports.

Supported Exchange Server versions

This topic describes the versions of Exchange Server and Windows Server that NMM supports for stand-alone, DAG, and passive/active highly available deployments.

Table 4 NMM support for highly available Exchange server

Exchange

Server version Supported operating system forstand-alone deployments Supported operating system forDAG and highly available deployments

2016 Windows Server 2012 R2 Windows Server 2012 R2 2010 SP3 l Windows Server 2008 x64 R2

SP1

l _{Windows Server 2012}

l Windows Server 2012

2013 CU2 l Windows Server 2008 x64 R2

SP1 l _{Windows Server 2012} l Windows Server 2008 x64 R2 SP1 l _{Windows Server 2012} 2013 SP1 l Windows Server 2008 R2 SP1 l _{Windows Server 2012} l Windows Server 2012 R2 l Windows Server 2012 R2

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 network is a supported configuration, it is not recommended. Using only one network connection can lead to unstable operations, such as databases that fail over to other systems when they experience network connection time outs.

Single server Microsoft Exchange Server and Microsoft SharePoint Server

installations

(23)

Delivery status notifications (DSNs) for Exchange server DAG environments

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

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

Exchange backup prerequisites

This 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 NetWorker

Module for Microsoft Installation Guide.

l Verify that all servers use the same Exchange Server and Windows Server version and

the same service pack or cumulative update.

l Install the NetWorker client and NMM software on all Exchange servers that are a part

of a backup.

l Transaction logs cannot be stored at the root level of a mount point. This results in

transactions logs that are not backed up at all.

l For stand-alone environments, configure a dedicated storage node (DSN). l For DAG environments:

n Create a client resource for all Exchange clients that are members of the DAG. n Create a NetWorker client resource for the DAG name using the FQDN.

n For federated backups, add the NSR_FEDERATED_BACKUP application information

attribute and specify “yes” as the value.

n NMM does not support DAGs configured without a cluster Administrative Access

Point.

Note

It is a best practice to perform these steps by using the client configuration wizard.

l Run the System Configuration Checker.

Exchange administrator configuration tool

The Exchange administrator configuration tool can create or reset the permissions of an account with the necessary privileges to perform backup and recovery operation on an Exchange Server. You should run the tool during NMM installation and to modify administrator account settings.

You can use the Exchange administrator configuration tool to perform the following tasks:

l Configure Admin User - Create an NMM Exchange administrator account and

configure the permissions and memberships to perform an Exchange database restore and granular level recovery.

Configuration

(24)

l Update Admin Password - Modify the NMM Exchange administrator account

password and update the registry credentials.

l Validate an existing user - Verify that an existing NMM Exchange administrator

account is correctly configured.

Note

To use the tool, you must be logged in with Domain Administrator permissions.

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

Figure 4 Exchange administrator configuration tool

To create an NMM Exchange administrator account, the tool performs the following steps:

l Creates an Active Directory user account.

l Creates a custom Exchange security group called EMC NMM Exchange Admin Roles. l Adds the user account to the groups listed in the following table:

Table 5 Permissions configured by the Exchange administrator configuration tool

User group Exchange Server role

Security group memberships on NMM Client computer

Local Administrator Security group memberships on Domain

Controller

Backup Operators Remote Desktop Users Exchange Security Group memberships Exchange Servers

EMC NMM Exchange Admin Roles, which includes:

(25)

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

User group Exchange Server role

n _{View-Only Configuration} n _{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 NMM

is installed.

Required permissions

This topic describes the minimum user account permissions required to perform backup and recovery with NMM.

Use the Exchange administrator configuration tool to create or reset the permissions of an account with the necessary privileges to perform backup and recovery operation on an Exchange Server.

Table 6 Permissions configured by the Exchange administrator configuration tool

For Exchange Server role

Security group memberships on NMM client computer

Local Administrator Security group memberships on

Domain Controller

Backup Operators Remote Desktop Users An Exchange Server that is also a

Domain Controller

Add the administrative account to the Organization Management group.

Exchange Security Group memberships

Exchange Servers

EMC NMM Exchange Admin Roles, which includes:

l _{Exchange Roles:} l Database Copies l _Databases l Disaster Recovery l _{Mailbox Import Export} l Mail Recipient Creation l _{Mail Recipients} l View-Only Configuration l _{View-Only Recipients}

Configuration

(26)

MAPI client and Collaboration Data Objects

This topic describes the Exchange Server 2010 and 2013 requirements for the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1 Kit.

For RDB and GLR support, Exchange Server requires the MAPI/CDO 1.2.1 kit. Exchange Server 2010 requires build 6.5.8244.0. Exchange Server 2013 requires build 6.5.8353.0. Exchange Server 2016 does not support MAPI.

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

Note

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

Exchange Consistency Check

The following topic describes how the Exchange consistency check improves the quality of a backup.

The Exchange consistency check verifies that the database and its corresponding set of transaction logs do not contain errors, and validates Exchange before performing a restore. 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 does not ensure complete consistency of the backup, it does offer the advantage of a shorter time to perform a consistency check. Exchange automatically runs a consistency check against stand-alone databases and public folders before NMM restores the data.

Consistency check parameters for threading and throttling

This topic describes the effects of the Exchange consistency check on NetWorker performance. Included is information about the Application Information attributes. The consistency check impacts Exchange backup performance. The larger the databases and associated transaction logs, the longer it takes to run a consistency check. NMM provides the option to run the consistency check on multiple databases in parallel. If you run multiple consistency checks in parallel without setting the proper throttle limits, performance problems might appear on the Exchange server. In extreme cases, this can cause I/O bottlenecks so severe that consistency checks fail and other system operations are adversely affected.

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

(27)

Table 7 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 (single}

threaded).

l _{False — To run eseutil in parallel against}

multiple storage groups (multi-threaded). The default value is False with a value of 4 maximum parallel threads. For example: NSR_ESE_UTIL_SEQUENTIAL=False

You can also specify the number of threads to use 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 pauses when 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 milliseconds when throttling, in the value range of 1000– 60000.

The default value is 1000.

NSR_ESE_CC_METHOD Specify whether to only perform the consistency check on the database and log files, database file only, or log files only.

Set to one of the following:

l _{DB_AND_LOGS} l _{DB_ONLY} l _{LOGS_ONLY}

The default value is DB_AND_LOGS.

Configuration

(28)

(29)

CHAPTER 3 Backup

l Planning backups...30 l Preferred Server Order List...32 l Configuring Exchange client resources... 32 l Configuring Exchange backups...40 l Example of a federated backup... 46 l Verifying a backup...47

(30)

Planning backups

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

Backup considerations

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

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

client and using the DAG node client.

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 then reopen it.

l After a backup of a data protection policy starts, you cannot interrupt or halt the

backup process.

For example, in Exchange backup, the nsrnmmsv.exe process on the production server and the eseutil process on the proxy resource might continue to run after you halt the backup. Any attempt to stop a backup in NMC takes a long time to complete.

l NMM only backs up mounted databases. If any databases are unmounted, NMM

does not display notifications during the backup operation. The NMM log files provide details about unmounted databases.

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

Backups in DAG environments

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

l Allows backups of passive database copies to continue even when the passive

database copies move among Exchange servers.

l Enables you to back up all DAG members with a single save set without running a

separate backup of each node. Each Exchange server for which a backup job is sent performs their backups in parallel with the other Exchange servers, resulting in faster backups.

Performing a DAG backup is similar to a standard backup, except for a few key differences:

l Before you perform a DAG backup, you must configure the client resource. l When you select which client to back up, you select the DAG client resource, not

individual servers in the DAG, for backup.

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

l Select the client resource for the DAG name and not individual servers in the DAG. l Specify the parameters for the client resource. Configuring Exchange backups on

page 40 provides more information.

l When you configure the backup, you can specify a preferred server order list (PSOL),

(31)

Note

It is a best practice to perform these steps by using the client configuration wizard.

Configuring backups to use a remote storage node in a DAG environment

This topic describes the steps for configuring remote storage in an Exchange DAG environment. This procedure allows you to specify a storage node for the physical clients in the DAG, which can differ from the storage node defined in the Policy for the federated backup.

To configure remote storage for an Exchange DAG environment: Procedure

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

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

a. On the Devices tab, right-click Storage Nodes and select New. b. Type the name of the client. For example, node1.domain.com.

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

3. To configure the client to use the storage node: a. Right-click Client and select Modify client.

b. On the Globals (2 of 2) tab, enter 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, add

NSR_USE_CLIENT_SN_LIST=yes.

b. Add each physical client to the same group as the DAG client, and mark each as disabled from the backup (deselect 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, make sure the selected pool contains the storage node that will be used for backup.

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

Exchange Information Store backup

The Exchange data is stored in the Information Store. The Information Store contains the following data:

l The Exchange database (.edb) files include mailbox databases, public folder

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

l The Transaction log (.log) files store database operations such as creating or

modifying a message. When the operations are committed, they are written to the .edb file.

Backup

(32)

l The Checkpoint (.chk) files store information about successful operations when they

are saved to the database on the hard disk.

When you select a database for backup, NMM backs up the database file and accompanying .log and .chk files. As part of your backup strategy for a Microsoft Exchange environment, make sure to back up the following components with NMM:

l Stand-alone databases

l Active or passive databases in a DAG environment

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

Backing up highly available Exchange server

In a highly available DAG environment, you can schedule federated backups using the DAG client and using the DAG node client.

Shadow copy and log truncation

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

Preferred Server Order List

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

Configuration wizard, and the PSOL is associated with a single DAG client resource. If you choose to include stand-alone databases (including public folder databases or public folder mailboxes), the coordinating node determines whether they exist on that server and, if so, adds them to the save set list as well. The coordinating node then goes to another server in the list and repeats the check for passive and stand-alone

databases; the node skips databases that are already listed.

Once the coordinating node has gone through the list of servers, then it validates that there 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.

Configuring Exchange client resources

A client resource specifies what to include in a snapshot of an NMM client. To create a client resource, you can use either of the following methods from the NetWorker Management Console:

l Creating a client resource using the Client Backup Configuration wizard on page 34 l Creating a client resource for Exchange backups by using the NetWorker Management

(33)

The table below describes how to determine the name to specify for the client resource for DAG and stand-alone setups.

Table 8 Exchange Server name attributes

Type of backup Requirement

Stand-alone (including public folder databases and mailboxes)

Type one of the following:

l _{The FQDN of the NetWorker client computer.} l _{The hostname of the NetWorker client computer.}

DAG l _{Type the DAG name.}

l For each physical computer of the DAG environment, type

the physical computer host name.

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

Table 9 Exchange Server 2010 save set names

Type of backup data Save set syntax

Writer level APPLICATIONS:\Microsoft Exchange 2010 Database name level APPLICATIONS:\Microsoft Exchange 2010\

For an Exchange Server federated DAG backup, type the following Application Information attributes and values:

NSR_EXCH_DAG=<dagname>

NSR_FEDERATED_BACKUP=yes

NSR_FEDERATED_PSOL: Type a comma-separated list of the order in which to back up the databases on each server in the DAG. If you do not specify a list, the coordinating node distributes the backups based on an unordered list of Exchange servers in the DAG.

Backup

(34)

NSR_EXCH_INCL_SA: Type False to exclude stand-alone databases and public folder mailboxes (Exchange Server 2013 and 2016), or public folder databases (Exchange Server 2010). The default setting is True.

NSR_EXCH _BACKUP or NSR_EXCH2010_BACKUP: Type one of the following:

l Preferred: To back up the passive copy or replica of each database if one is available.

The Exchange server on which each passive database is backed up is determined by the preferred server order list. If no passive database exists, then the active database is backed up.

l All: Similar to Preferred, to back up the passive copy or replica of each database if it

is available.

l Passive: To back up only passive databases in the DAG. l Active: To back up only active databases in the DAG.

NSR_EXCLUDE_COMPONENTS= Type the database name to exclude it from the backup. For an Exchange Server stand-alone backup, you can type any of the following optional Application Information attributes and values:

NSR_EXCH_INCL_SA: Type False to exclude stand-alone databases and public folder mailboxes (Exchange Server 2013 and 2016), or public folder databases (Exchange Server 2010). The default setting is True.

NSR_EXCH _BACKUP or NSR_EXCH2010_BACKUP: Type one of the following:

l Preferred: To back up the passive copy or replica of each database if one exists. The

Exchange server on which each passive database is backed up is determined by the preferred server order list. If no passive database exists, then the active database is backed up.

l All: Similar to Preferred, to back up the passive copy or replica of each database if it

is available.

l Passive: To back up only passive databases in the DAG. l Active: To back up only active databases in the DAG.

NSR_EXCLUDE_COMPONENTS= Type the database name to exclude it from the backup.

Complete list of Exchange Server Application Information attributes on page 43

provides additional details.

Creating a client resource using the Client Backup Configuration wizard

This section describes how to create a client resource using the Client Backup Configuration wizard.

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

Procedure

(35)

Figure 5 Initial screen of Client Backup Configuration wizard

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

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

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

installed.

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

NMM does not support DAGs configured without a cluster Administrative Access Point.

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

For Exchange Server 2013 SP1 configurations on Windows Server 2012 R2, type the static IP address of the DAG instance.

Do not use the IP address for the client name because it can cause errors. b. Select the Traditional type.

c. Click Next.

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

4. On the Specify the Client Backup Options screen:

a. To use the Client Direct feature, then select the Client Direct checkbox. The default setting is checked.

b. If you use parallel save streams per save set, then select Parallel save streams. c. Leave the Target Pool field blank.

d. Select one of the following deduplication options:

l None if you have not configured data deduplication.

l Data Domain backup if you are using a Data Domain device for data

deduplication. After selecting this option, enter the IP address of the Data Domain device.

e. Click Next.

Backup

(36)

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

By default, all of the databases are selected for the entire server backup. Clear the checkbox for any items that need to be excluded from the backup.

6. On the Exchange Backup Options screen:

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

l Preferred Passive Backup to back up passive or replica copies of the

databases.

If no replica copy is available or healthy for the database, the active copy is backed 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 selected type of database does not exist.

Note

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

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

a. Select Use Preferred Server Order List to specify the order in which to back up servers.

By default, the Use Preferred Server Order List is selected.

b. Select a server from the Available Servers list and then click the right arrow to move it to the Preferred Server List.

To adjust the order of servers:

a. Select a server in the Preferred Server List. b. Click the up and down arrows to change the order.

c. Select Include Standalone and Public Folder databases to back up stand-alone databases and public folder mailboxes (Exchange Server 2013 and 2016), or public 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 selecting

the Perform a consistency check during backup option and configure the following settings:

a. Select the Perform database consistency check during backup option to validate Exchange databases and logs, databases only, or logs only.

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

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

(37)

d. Click Next.

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

8. On the Specify the NetWorker Backup Group screen: a. Do one of the following:

l Select the Add to an existing group option to select an existing save group and

choose a save group from the provided list.

Only save groups with valid snapshot policies are available for selection.

l Select the Create a new group option to create a new save group and configure

the new group as follows:

a. In the Group Name field, type the name of the new save group. b. On the Client Retries menu, select 0.

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

d. Select the Automatically start the backup at the scheduled time option to automatically 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 new group, the Specify the NetWorker Snapshot Policy screen appears in the wizard.

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

Note

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

b. Click Next.

9. On the Specify the Storage Node Options screen:

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

l Automatically select the storage node and devices for the client to

automatically select client storage nodes and devices.

l Backup to the NetWorker server only when the setup does not include a

NetWorker storage node.

l Backup to the following storage nodes to select a specific NetWorker storage

node. Select one of the storage nodes listed. b. Click Next.

10.On the Backup Configuration Summary screen, review the details and do one of the following:

l Click Back to revisit the previous pages. l Click Create to configure the client resources.

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

Backup

(38)

l Click Back to modify the configuration data and rerun the Client Backup

Configuration wizard.

l Click Finish.

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

Perform these steps to edit the existing client resources for NMM backups. Make these changes for all existing client resources.

To be able to recover backups that were created by using a NMM 8.2.x or earlier, you must make changes to the existing client resource.

Procedure

1. In the Administration window, click Protection.

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

3. Select Modify Client Properties.

4. In the Backup Command field, delete the nsrsnap_vss_save command and type the

nsrnmmsv.exe command. This change must be performed for all the existing client

resources.

5. Make other changes, if required. 6. Click OK.

Creating a client resource for Exchange backups by using the NetWorker

Management Console

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

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

Procedure

1. In the Administration view of the NetWorker Management Console, select the Protection 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. Leave the Block based backup option clear.

d. In the Save Set attribute, specify the components to be backed up. Place multiple entries on separate lines.

(39)

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

Provide the appropriate application variables and values for your Exchange Server environment.

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

l If the pool configured for the NMM Exchange backups uses Data Domain Boost

devices, select the Data Domain backups option to enable client-side Data Domain Boost deduplication backups.

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

its own deduplication node.

l If the deduplication node for this client’s backup data changes, the next backup

done must be a level 0 (full) backup. If the deduplication node for this client’s backup data changes, the next backup performed must be a level 0 (full) backup. 7. Click the Globals (1 of 2) tab and complete verify that the Aliases attribute displays

the NETBIOS name for the client. This name is filled in automatically.

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

8. If using a NetWorker storage node, when configuring a client resource for the Mailbox server and a DAG resource, click the Globals (2 of 2) tab and type the storage node name 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 using the FQDN.

NMM does not support DAGs configured without a cluster Administrative Access Point.

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

For Exchange Server 2013 SP1 configurations on Windows Server 2012 R2, type the static IP address of the DAG instance.

Do not use the IP address for the client name because it can cause errors. a. In the expanded left pane, select Clients.

b. From the File menu, select New.

Backup

(40)

c. In the Name attribute, type the Exchange Server name or FQDN. d. In the Comment attribute, type a description.

Use this attribute to differentiate the purpose of each resource. e. For the Browse Policy attribute, select a browse policy from the list. f. For the Retention Policy attribute, select a retention policy from the list. g. Confirm that the Scheduled Backups attribute is selected.

h. In the Save Set attribute, specify the components to be backed up. i. Deselect the default group.

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

Configuring Exchange backups

To 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 Client Backup Configuration Wizard or the Client Properties dialog box. Configuring Exchange client resources on page 32 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 administrator privileges on page 41.

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

Backup configuration options

Table 12 Exchange Server backup options

Backup configuration Details

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

(41)

Table 12 Exchange Server backup options (continued)

Backup configuration Details

Both active and passive databases backup on the server

You can back up both active and passive databases on Exchange Server mailbox servers in the DAG environment. You can perform both full and incremental backups.

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

You can configure a virtual client to direct its backups to the storage node on the physical host on which it resides. To configure a virtual client, type curphyhost in the Storage Nodes attribute of the virtual client. This variable is not supported for DAG environments. The EMC NetWorker Administration Guide provides more information about curphyhost.

Backup to a remote storage node in a DAG or non-DAG environment

You can perform Exchange Server database backups by using a remote NetWorker storage node. The Exchange server and NetWorker storage node are on different computers in the non-DAG environment. You can perform both full and incremental backups.

NMM does not support server-based dedicated storage nodes in a DAG environment. Select No for the Dedicated storage node option in the Device properties dialog when configuring the storage node in a DAG environment. Refer to Configuring backups to use a remote storage node in a DAG environment to use a remote storage node in a DAG environment. A regular storage node license is required for DAG LAN-free backups. The EMC NetWorker Administration Guide provides details.

Configuring NetWorker administrator privileges

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

NOTICE

If you set up a proxy client for the NMM client, grant the proxy client NetWorker

administrator privileges. If you are setting up a NMM client in a cluster, grant NetWorker administrator 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.

Backup

(42)

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 value on a separate line:

user=administrator,host=NMM_client_host user=system,host=NMM_client_host

where NMM_client_host is the DNS hostname of the NMM client. Place each value on a separate line.

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

l Where a single user is granted administrator rights to perform all the NetWorker

functionality for a host, add the following values:

user=administrator,host=NMM_calientproxy_host user=system,host=NMM_clientproxy_host

l Where multiple users are configured and added to an administrator group and that

group is added on the NetWorker privilege list, all the users under this group have administrator rights.

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

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

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

l Cluster node (both active and passive nodes) l Virtual server

8. Click OK.

All NMM users must have administrator level privileges.

Configuring a federated DAG backup

You can configure a federated DAG environment by using the Client Configuration wizard or by manually configuring the NetWorker client resources. To manually configure the client resources, you must specify the Application Information attribute and provide a backup 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 any backup group.

The physical client resources of the DAG should be in the same protection Group as the DAG client resource. The physical client resources should have the Scheduled backup checkbox deselected.

Procedure

(43)

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

3. Assign DAG client resource to the policy.

Complete list of Exchange Server Application Information attributes

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

Table 13 Exchange Application Information attribute settings

Attribute name Description Values

NSR_EXCH_CHECK=value Specifies if consistency check should be run or not for databases. yes or no

If you do not specify a value, NMM applies the following default values:

l _{Exchange Server DAG backup: no}

l _{Exchange Server stand-alone backups: yes}

If the value is no, then NMM indicates the consistency check is skipped in the backup log file(s).

NSR_EXCH_DAG= <DAG name>

Optional, to specify the DAG name for a backup in a DAG environment. FQDN of the DAG. For example, NSR_EXCH_DAG=mydag.domainname.com NSR_EXCH_BACKUP= active/passive/preferred or all To back up only active database copies.

l _{active - back up only active database}

copies.

l passive - back up only passive database

copies.

l _{preferred - back up only passive copy or}

replica of each database if one is available. If no passive database exists, then the active database is backed up.

l all - back up both active and passive

databases. NSR_EXCLUDE_COMPONENTS =db1,db2… Excludes specified databases from backup name of database

The following application variables are examples for Exchange Server stand-alone backups:

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

l NSR_ESE_UTIL_THROTTLE=<True/False>

The following application variables are examples for Exchange Server DAG backups:

Backup

(44)

l NSR_FEDERATED_BACKUP=yes

l NSR_FEDERATED_PSOL=<DAG Node1>,<DAG node2>,…,<DAG NodeN> l NSR_EXCH_INCL_SA=<TRUE/FALSE> l NSR_EXCH_DAG=<DAG FQDN> l NSR_EXCH_CHECK=<yes/no> l NSR_ESE_UTIL_SEQUENTIAL=<True/False> l NSR_ESE_UTIL_THROTTLE=<True/False> l NSR_ESE_CC_METHOD=<db_and_logs/db_only/logs_only>

Viewing a valid application data save set

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

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

Table 14 Commands for displaying valid application data save sets

Application server Command

Exchange Server stand-alone node At the command prompt, type: nsrnmmsv -P Example output: “APPLICATIONS:\Microsoft Exchange 2010” “APPLICATIONS:\Microsoft Exchange 2010\Database 1” “APPLICATIONS:\Microsoft Exchange 2010\Database 2” “APPLICATIONS:\Microsoft Exchange 2010\ Database 3” “APPLICATIONS:\Microsoft Exchange 2010\ Database 4” 68150:nsrnmmsv:nsrnmmsv: Exiting with success.

This command only provides a list of databases on the Exchange server from which you run the command.

To include the state of the database (verbose output), type:

nsrnmmsv -P

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

nsrnmmsv -A NSR_FEDERATED_BACKUP=yes -A NSR_EXCH_DAG=<DAG client> -P

(45)

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

Application server Command

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

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

Remove the quotation marks when copying the save set name from the output. Each line of output corresponds to a save set entry that you can add to the save set attribute 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 must specify some special characters, such as the backward slash (\), by their URL-encoded values.

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

Table 15 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 < %3C ‘ %60 > %3E | %7C

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

Backup

EMC NetWorker Module for Microsoft for Exchange Server VSS

EMC

®

NetWorker

®

Module for

Microsoft for Exchange Server

VSS

User Guide

CONTENTS

FIGURES

TABLES

Preface

CHAPTER 1

Introduction

Overview

Stand-alone and single Exchange Servers

Exchange Server DAGs

High availability in Exchange Server

Active and passive nodes and databases

Using NMM in an Exchange Server environment

Exchange Server 2010 VSS Writers

Exchange Server 2013 and 2016 VSS Writer

Compatibility with previous Exchange backups

Backup initiated transaction log file truncation

Backup types and levels

Federated backups

Recovery types

Exchange Server Block Based Backup

CHAPTER 2

Configuration

Supported Exchange server deployment scenarios and

limitations

Supported Exchange Server versions

Single server Microsoft Exchange Server and Microsoft SharePoint Server

installations

Delivery status notifications (DSNs) for Exchange server DAG environments

Exchange backup prerequisites

Exchange administrator configuration tool

Required permissions

MAPI client and Collaboration Data Objects

Exchange Consistency Check

Consistency check parameters for threading and throttling

CHAPTER 3

Backup

Planning backups

Backup considerations

Backups in DAG environments

Configuring backups to use a remote storage node in a DAG environment

Exchange Information Store backup

Backing up highly available Exchange server

Shadow copy and log truncation

Preferred Server Order List

Configuring Exchange client resources

Creating a client resource using the Client Backup Configuration wizard

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

Creating a client resource for Exchange backups by using the NetWorker

Management Console

Configuring Exchange backups

Backup configuration options

Configuring NetWorker administrator privileges

Configuring a federated DAG backup

Manually configuring NetWorker client resources for a federated Exchange Server backup

Complete list of Exchange Server Application Information attributes

Viewing a valid application data save set

URL encoding for Exchange save sets