EMC NetWorker Module for Microsoft for Exchange Server VSS

Transcription

1 EMC NetWorker Module for Microsoft for Exchange Server VSS Version 9.0 User Guide REV 02

2 Copyright EMC Corporation. All rights reserved. Published in USA. 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 ( EMC Corporation Hopkinton, Massachusetts In North America EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

3 CONTENTS Figures 5 Tables 7 Preface 9 Chapter 1 Introduction 13 Overview Stand-alone and single Exchange Servers Exchange Server DAGs High availability in Exchange Server Active and passive nodes and databases...16 Using NMM in an Exchange Server environment Exchange Server 2010 VSS Writers...17 Exchange Server 2013 and 2016 VSS Writer...18 Compatibility with previous Exchange backups Backup initiated transaction log file truncation Backup types and levels...19 Federated backups...19 Recovery types Exchange Server Block Based Backup Chapter 2 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 Delivery status notifications (DSNs) for Exchange server DAG environments...23 Exchange backup prerequisites...23 Exchange administrator configuration tool Required permissions MAPI client and Collaboration Data Objects...26 Exchange Consistency Check Consistency check parameters for threading and throttling Chapter 3 Backup 29 Planning backups...30 Backup considerations...30 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...32 Shadow copy and log truncation Preferred Server Order List...32 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide 3

4 CONTENTS Configuring Exchange client resources Creating a client resource using the Client Backup Configuration wizard...34 Creating a client resource for Exchange backups by using the NetWorker Management Console Configuring Exchange backups...40 Backup configuration options Configuring NetWorker administrator privileges...41 Configuring a federated DAG backup...42 Complete list of Exchange Server Application Information attributes Viewing a valid application data save set Circumstances that promote incremental backup to full backup...46 Example of a federated backup Verifying a backup...47 Chapter 4 Mail Item Recovery 49 Overview Recovery types Restoring Exchange data Recovering individual mailboxes, mailbox folders, and messages...52 Exchange recovery prerequisites Additional requirements for browsing mailboxes...56 Additional requirements for recovering databases in a DAG Configuring Exchange Server recovery Specifying Exchange recovery options...57 Configuring roll-forward recovery of an Exchange server in a DAG environment Recovery procedures Recovering NetWorker Module for Microsoft Exchange backups Mounting the database after recovery Performing Exchange Server recovery Recovering deleted Exchange Server mailboxes, public folder databases, or public folder mailboxes...66 Performing a quick recovery of a deleted mailbox...67 Recovering Exchange Server mailbox, public folder database, or public folder mailbox files Best practices and recommendations...69 Exchange recovery limitations Chapter 5 Granular Level Recovery 71 Recovering Mailbox items with GLR GLR considerations Recovering individual mailbox items using GLR Performing a GLR to an alternate mailbox Performing a GLR on an archive user mailbox Performing a GLR to a PST...76 Chapter 6 Troubleshooting 79 Troubleshooting general errors...80 Troubleshooting backups...80 Troubleshooting recovery EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

5 FIGURES NetWorker and NMM installation in a stand-alone or single Exchange Server environment...14 NetWorker and NMM installation with a DAG in an Exchange Server environment Exchange Server DAG environment Exchange administrator configuration tool...24 Initial screen of Client Backup Configuration wizard...35 Example of an Exchange Server federated backup Recovery in a stand-alone Exchange Server environment Recovery to an alternate location in a stand-alone Exchange Server environment Recover using NMM granular level recovery Recover to an RDB, and then recover data from the RDB to a user mailbox Advanced Recovery dialog Exchange Recovery Summary dialog Manage RDB dialog Create RDB dialog...64 Delete confirmation dialog box Select Database dialog box Select Server dialog...66 Individual mailbox databases...73 Sample mailbox...74 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide 5

6 FIGURES 6 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

7 TABLES Revision history Style conventions Writers used by NMM for Exchange Server backup and recovery NMM support for highly available Exchange server Permissions configured by the Exchange administrator configuration tool Permissions configured by the Exchange administrator configuration tool Exchange application information variables for threading and throttling Exchange Server name attributes...33 Exchange Server 2010 save set names Exchange Server 2013 save set names Exchange Server 2016 save set names Exchange Server backup options Exchange Application Information attribute settings Commands for displaying valid application data save sets Special characters and their URL-encoded values PowerShell cmdlets for restored mailboxes...80 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide 7

8 TABLES 8 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

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 ( 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 ( 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: EMC NetWorker software EMC NetWorker data protection policy management Microsoft Volume Shadow Copy Service (VSS) technology EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide 9

10 Preface 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. Related documentation The NMM documentation set includes the following publications: EMC NetWorker Module for Microsoft Release Notes EMC NetWorker Module for Microsoft Administration Guide EMC NetWorker Module for Microsoft Installation Guide EMC NetWorker Module for Microsoft for SQL and SharePoint VSS User Guide EMC NetWorker Module for Microsoft for SQL VDI User Guide EMC NetWorker Module for Microsoft for Exchange VSS User Guide EMC EMC NetWorker Module for Microsoft for Hyper-V VSS User Guide EMC NetWorker Module for Microsoft for Windows Bare Metal Recovery Solution User Guide EMC NetWorker Performing Backup and Recovery of SharePoint Server by using NetWorker Module for Microsoft SQL VDI solution Technical Notes EMC NetWorker Performing Exchange Server Granular Recovery by using NetWorker Module for Microsoft with Ontrack PowerControls Technical Notes EMC NetWorker SharePoint BLOB Backup and Recovery by using NetWorker Module for Microsoft and Metalogix StoragePoint Technical Notes NetWorker documentation set Special notice conventions that are used in this document EMC 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 conventions EMC uses the following type style conventions in this document: 10 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

11 Preface Table 2 Style conventions Bold Italic Monospace Used for names of interface elements, such as names of buttons, fields, tab names, and menu paths (what the user specifically selects or clicks) Used for full titles of publications that are referenced in text Used for: System code System output, such as an error message or script Pathnames, file names, prompts, and syntax Commands and options Monospace italic Monospace bold Used for variables 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 the example Where to get help EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at Technical support Go to EMC Online Support and click Service Center. Several options for contacting EMC Technical Support appear on the site. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Online communities Go to EMC Community Network at for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professionals for all EMC products. Your comments Your suggestions help to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to DPAD.Doc.Feedback@emc.com. EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide 11

12 Preface 12 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

13 CHAPTER 1 Introduction This chapter includes the following sections: Overview Using NMM in an Exchange Server environment Introduction 13

14 Introduction 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 ( 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: Install the NetWorker and NMM clients on each Exchange server that has the mailbox role installed. You can replicate each Exchange database to multiple Exchange servers, with a maximum of 16 copies. 14 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

15 Introduction 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. When there are multiple copies of a database, only one copy of the database is active at a time. The remaining copies are passive. You can back up active copy mailbox databases, passive copy mailbox databases, and standalone databases. Standalone applies to an Exchange Server mailbox database that is not replicated across multiple servers, including and public folder mailboxes and public folder databases. 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: technet.microsoft.com/en-us/library/dd aspx. The Exchange Server 2010 equivalent for this limitation is available on the Microsoft TechNet website. Exchange Server DAGs 15

16 Introduction Figure 2 NetWorker and NMM installation with a DAG in an Exchange Server environment High availability in Exchange Server Active and passive nodes and databases 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. 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. The following topic describes NMM installations with Exchange server clustered environments. In a clustered environment, there are active and passive copies of the databases. This allows the server to constantly update a copy, or replica, as the passive copy, and minimize the impact on performance of the active copy. For backups, the passive copy allows you to back up the databases without affecting the performance or data of the 16 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

17 Introduction 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 Exchange Server 2010 VSS Writers 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. 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 Information Store Writer Replication Service Writer Description 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. 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 Using NMM in an Exchange Server environment 17

18 Introduction 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 Upgrade to Exchange Server Perform a full backup on Exchange Server 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 successfully, which allows the Exchange writer to proceed with log truncation. 18 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

19 Introduction Backup types and levels The time that the Exchange writer starts backup-initiated log file truncation differs for each backup type. In stand-alone configurations, the Exchange Writer truncates the transaction log files at the completion of successful full or incremental backups. 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. 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 Recovery types 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. This topic describes the types of Exchange recoveries supported by NMM. NMM supports the following types of recovery: Roll-forward recovery Point-in-time recovery Database recovery to Exchange RDB Remote database recovery for Exchange Server DAG Mailbox item level recovery from Exchange RDB databases Exchange RDB mailbox browsing, mailbox, folder, and message recovery Recovery to alternate mailbox database Recovery to alternate Mailbox Granular Level Recovery (GLR) to/from RDB or DAG Granular Level Recovery (GLR) to alternate mailbox Granular Lever Recovery (GLR) to PST files Backup types and levels 19

20 Introduction 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 NetWorker Module for Microsoft Administration Guide. 20 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

21 CHAPTER 2 Configuration This chapter includes the following sections: Supported Exchange server deployment scenarios and limitations...22 Exchange backup prerequisites...23 Exchange administrator configuration tool Required permissions MAPI client and Collaboration Data Objects...26 Exchange Consistency Check...26 Configuration 21

22 Configuration Supported Exchange server deployment scenarios and limitations Supported Exchange Server versions 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 provides the most up-to-date and accurate listing of hardware, operating system, service pack, and application versions that the NMM client supports. 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 for stand-alone deployments Supported operating system for DAG and highly available deployments 2016 Windows Server 2012 R2 Windows Server 2012 R SP3 Windows Server 2008 x64 R2 SP1 Windows Server CU2 Windows Server 2008 x64 R2 SP1 Windows Server SP1 Windows Server 2008 R2 SP1 Windows Server 2012 Windows Server 2008 x64 R2 SP1 Windows Server 2012 Windows Server 2012 R2 Windows Server 2012 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 NMM does not support Microsoft Exchange Server and Microsoft SharePoint Server installed on the same computer. Microsoft does not support this configuration. Instead, Microsoft best practices recommend that you install these server products on separate computers. 22 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

23 Configuration Delivery status notifications (DSNs) for Exchange server DAG environments Exchange backup prerequisites 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. This topic describes the required prerequisites for backup of Exchange server using NMM. Ensure that the following prerequisites are met before performing backup procedures: Install the.net Framework. Install the hotfixes and cumulative updates that are listed in the EMC NetWorker Module for Microsoft Installation Guide. Verify that all servers use the same Exchange Server and Windows Server version and the same service pack or cumulative update. Install the NetWorker client and NMM software on all Exchange servers that are a part of a backup. 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. For stand-alone environments, configure a dedicated storage node (DSN). For DAG environments: Create a client resource for all Exchange clients that are members of the DAG. Create a NetWorker client resource for the DAG name using the FQDN. For federated backups, add the NSR_FEDERATED_BACKUP application information attribute and specify yes as the value. 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. 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: 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. Delivery status notifications (DSNs) for Exchange server DAG environments 23

24 Configuration Update Admin Password - Modify the NMM Exchange administrator account password and update the registry credentials. 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: Creates an Active Directory user account. Creates a custom Exchange security group called EMC NMM Exchange Admin Roles. Adds the user account to the groups listed in the following table: Table 5 Permissions configured by the Exchange administrator configuration tool User group Security group memberships on NMM Client computer Security group memberships on Domain Controller Exchange Security Group memberships Exchange Server role Local Administrator Backup Operators Remote Desktop Users Exchange Servers EMC NMM Exchange Admin Roles, which includes: Exchange Roles: Database Copies Databases Disaster Recovery Mailbox Import Export Mail Recipient Creation Mail Recipients 24 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

25 Configuration Table 5 Permissions configured by the Exchange administrator configuration tool (continued) User group Exchange Server role View-Only Configuration View-Only Recipients Required permissions Assigns the "Mailbox Import Export" management role to the user. Creates an Exchange mailbox. Assigns Send-As and Receive-As rights. Registers the user account for backup and recovery on Exchange servers where NMM is installed. 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 Security group memberships on NMM client computer Security group memberships on Domain Controller An Exchange Server that is also a Domain Controller Exchange Security Group memberships Exchange Server role Local Administrator Backup Operators Remote Desktop Users Add the administrative account to the Organization Management group. Exchange Servers EMC NMM Exchange Admin Roles, which includes: Exchange Roles: Database Copies Databases Disaster Recovery Mailbox Import Export Mail Recipient Creation Mail Recipients View-Only Configuration View-Only Recipients Required permissions 25

26 Configuration 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 Kit. For RDB and GLR support, Exchange Server requires the MAPI/CDO kit. Exchange Server 2010 requires build Exchange Server 2013 requires build 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. The table below lists the Application Information attributes that you can specify in the client resource to set threading and throttling. 26 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

27 Configuration Table 7 Exchange application information variables for threading and throttling Attribute name NSR_ESE_UTIL_SEQUENTIAL Value Set to either of the following: True To run eseutil sequentially (single threaded). 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: True To allow eseutil throttling. False To prevent eseutil throttling. The default value is False. NSR_ESE_THROTTLE_IOS NSR_ESE_THROTTLE_DURATION NSR_ESE_CC_METHOD Specify the number of I/Os between pauses when throttling, in the value range of The default value is 100. For example: NSR_ESE_THROTTLE_IOS=500 Specify the duration of pause in milliseconds when throttling, in the value range of The default value is 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: DB_AND_LOGS DB_ONLY LOGS_ONLY The default value is DB_AND_LOGS. Consistency check parameters for threading and throttling 27

28 Configuration 28 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

29 CHAPTER 3 Backup This chapter includes the following sections: Planning backups...30 Preferred Server Order List...32 Configuring Exchange client resources Configuring Exchange backups...40 Example of a federated backup Verifying a backup...47 Backup 29

30 Backup Planning backups Backup considerations Backups in DAG environments This section contains information to help you plan an Exchange backup. When performing Exchange server backups, keep the following in mind: In a highly available DAG environment, schedule federated backups using the DAG client and using the DAG node client. 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. 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. 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. 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: Allows backups of passive database copies to continue even when the passive database copies move among Exchange servers. 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: Before you perform a DAG backup, you must configure the client resource. 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: Select the client resource for the DAG name and not individual servers in the DAG. Specify the parameters for the client resource. Configuring Exchange backups on page 40 provides more information. When you configure the backup, you can specify a preferred server order list (PSOL), which tells NMM the order to poll each server in the DAG to back up. Preferred Server Order List on page 32 provides more information. 30 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

31 Backup 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 Exchange Information Store backup 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. The Exchange data is stored in the Information Store. The Information Store contains the following data: The Exchange database (.edb) files include mailbox databases, public folder mailboxes (Exchange Server 2013 and 2016), and public folder databases (Exchange Server 2010). 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. Configuring backups to use a remote storage node in a DAG environment 31

32 Backup 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: Stand-alone databases 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 Shadow copy and log truncation Preferred Server Order List In a highly available DAG environment, you can schedule federated backups using the DAG client and using the DAG node client. 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. 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: Creating a client resource using the Client Backup Configuration wizard on page 34 Creating a client resource for Exchange backups by using the NetWorker Management Console on page EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

33 Backup 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 Stand-alone (including public folder databases and mailboxes) Requirement Type one of the following: The FQDN of the NetWorker client computer. The hostname of the NetWorker client computer. DAG Type the DAG name. 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\ <Database name> The table below provides the list of Exchange Server 2013 save sets for application data. Table 10 Exchange Server 2013 save set names Type of backup data Save set syntax Writer level APPLICATIONS:\Microsoft Exchange 2013 Database name level APPLICATIONS:\Microsoft Exchange 2013\ <Database name> The table below provides the list of Exchange Server 2016 save sets for application data. Table 11 Exchange Server 2016 save set names Type of backup data Save set syntax Writer level APPLICATIONS:\Microsoft Exchange 2016 Database name level APPLICATIONS:\Microsoft Exchange 2016\ <Database name> 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. Configuring Exchange client resources 33

34 Backup 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: 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. All: Similar to Preferred, to back up the passive copy or replica of each database if it is available. Passive: To back up only passive databases in the DAG. 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: 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. All: Similar to Preferred, to back up the passive copy or replica of each database if it is available. Passive: To back up only passive databases in the DAG. 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 1. In the Administration view of the NetWorker Management Console, select the Protection tab, and then from the menu bar, right-click Clients and select New Client wizard. 34 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

35 Backup 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. For stand-alone configurations, type the name of the client where NMM is installed. 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: None if you have not configured data deduplication. 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. Creating a client resource using the Client Backup Configuration wizard 35

36 Backup 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: 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. Passive Only Backup to back up only passive copies or replicas of databases. 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. You can configure the number of consistency check I/O operations to perform before pausing and the length of time to pause between I/O operation cycles. 36 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

37 Backup 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: 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. 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 dropdown 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: Automatically select the storage node and devices for the client to automatically select client storage nodes and devices. Backup to the NetWorker server only when the setup does not include a NetWorker storage node. 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: Click Back to revisit the previous pages. 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: Creating a client resource using the Client Backup Configuration wizard 37

38 Backup Click Back to modify the configuration data and rerun the Client Backup Configuration wizard. 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. e. Select the appropriate option in the Protection group list field. 38 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

39 Backup 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: 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. Do not select the name of a replication node here. This step links this client with its own deduplication node. 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: All remaining Exchange clients that are members of the DAG. 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. Creating a client resource for Exchange backups by using the NetWorker Management Console 39

40 Backup 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 Backup configuration options 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. Table 12 Exchange Server backup options Backup configuration Only active databases backup on the server Only passive databases backup on the server Details 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). You can back up all the passive database copies residing on an Exchange Server mailbox server in a DAG environment. You can perform full and incremental backups, including incremental backups of public folders. Passive node backups do not include public folder mailboxes or public folder databases. 40 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

41 Backup Table 12 Exchange Server backup options (continued) Backup configuration Both active and passive databases backup on the server Backup to a local storage node in a stand-alone environment Backup to a remote storage node in a DAG or non-dag environment Details 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. 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. 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. Configuring NetWorker administrator privileges 41

42 Backup 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: 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 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: Cluster node (both active and passive nodes) 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 1. Create a NetWorker client resource for each physical DAG node and the virtual DAG name. 42 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

43 Backup 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 NSR_EXCH_DAG= <DAG name> Specifies if consistency check should be run or not for databases. Optional, to specify the DAG name for a backup in a DAG environment. yes or no If you do not specify a value, NMM applies the following default values: Exchange Server DAG backup: no 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). 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. active - back up only active database copies. passive - back up only passive database copies. 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. 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: NSR_ESE_UTIL_SEQUENTIAL=<True/False> NSR_EXCH_CHECK=<yes/no> NSR_ESE_UTIL_THROTTLE=<True/False> The following application variables are examples for Exchange Server DAG backups: Complete list of Exchange Server Application Information attributes 43

44 Backup NSR_FEDERATED_BACKUP=yes NSR_FEDERATED_PSOL=<DAG Node1>,<DAG node2>,,<dag NodeN> NSR_EXCH_INCL_SA=<TRUE/FALSE> NSR_EXCH_DAG=<DAG FQDN> NSR_EXCH_CHECK=<yes/no> NSR_ESE_UTIL_SEQUENTIAL=<True/False> NSR_ESE_UTIL_THROTTLE=<True/False> Viewing a valid application data save set NSR_ESE_CC_METHOD=<db_and_logs/db_only/logs_only> 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 Exchange Server stand-alone node Exchange Server DAG Command 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 :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 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 Example output: 44 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

45 Backup 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. URL encoding for Exchange save sets 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. 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. Viewing a valid application data save set 45

46 Backup Viewing volumes to back up for recovery To view the volumes that you must back up in order to perform an Exchange Server recovery, perform either of the following steps using the NMM GUI: Right-click on the Exchange Writer level save set for which you want to view the required volumes, and select Required volumes. The Required NetWorker Volumes dialog with details about the volume appears. Select any of the backed up databases and select Required volumes. The Required NetWorker Volumes dialog with details about the volume appears. Circumstances that promote incremental backup to full backup The following rules apply for incremental backups: Example of a federated backup When NMM cannot find a full backup for the database within the specified save set, NMM promotes an incremental backup to a full backup. If you add a new Mailbox database to an existing save set, then NMM promotes the next backup to a full backup. If NMM detects log gaps between the last backup and the current set of logs, NMM promotes an incremental backup to a full backup. For example, there are gaps between highest log number retrieved from index and the lowest log number retrieved from the disk. If you change the database or the logs path after the last full backup, then NMM promotes the next incremental backup to a full backup. The following figure illustrates an example of a federated backup of a DAG cluster with three Exchange servers: MBX1, MBX2, and MBX3. The cluster contains four Exchange databases: DB1, DB2, DB3, and DB4. Each database can only have one active copy, but can have multiple passive or replica copies. In this example, there are two passive copies of DB1: one copy on two different Exchange servers (MBX2 and MBX3). The other databases (DB2, DB3, and DB4) only have one passive copy each in the cluster. Only one copy of each database needs to be backed up. The preferred server order list specifies to back up databases from the DAG in this order: MBX2, MBX3, and MBX1. The figure below illustrates an example Exchange Server federated backup. 46 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

47 Backup Figure 6 Example of an Exchange Server federated backup Verifying a backup To verify if a backup is successful, use the following command on the NetWorker client: mminfo -Sot -s <NW server> -c <NMM client> where the <Client Name> is the DAG name or Exchange Server mailbox server name. Verifying a backup 47

48 Backup 48 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

49 CHAPTER 4 Mail Item Recovery This chapter includes the following sections: Overview Exchange recovery prerequisites Configuring Exchange Server recovery Recovery procedures Best practices and recommendations...69 Mail Item Recovery 49

50 Mail Item Recovery Overview An Exchange recovery can serve many different purposes. The smallest unit of granularity of a backup is an Exchange database, log files, and checkpoint files. Those backups can be used to recover entire servers, individual databases, or mailbox items. When you perform backups of a Microsoft Exchange environment with NMM, the following recovery options are available for stand-alone and high-availability environments: Recover to the original location on the original Exchange server Recover to the Exchange Server RDB on the original Exchange server Recover to an Exchange Server RDB on a different Exchange server Message-level recovery using the Exchange GLR option Note To recover backups that were created using an NMM release earlier than 9.0, click Start > EMC NetWorker > NetWorker Tools > Recover previous release NMM backups to start the NetWorker Module for Microsoft GUI. Browse the backups and perform the recovery from the GUI that appears. Recovery types NMM provides many levels of recovery, such as recovering databases or recovering individual messages in a user mailbox. Database level recovery Message level and granular level recovery DAG recovery Public mailbox folder and database recovery When you recover a database, you generally overwrite the current database unless you recover to an RDB. See Recovering Exchange Server mailbox, public folder database, or public folder mailbox files on page 68. When you need to retrieve individual user mailboxes, user mail folders, or messages, you can do so without overwriting entire mail databases. You can recover a database to an Exchange RDB, and then use Exchange server management tools or NMM Granular Level Recovery (GLR) to select and recover individual mailboxes, folders, or messages. Those recovery procedures are provided in the Message and Granular Level Recovery on page 50 section. A DAG backup provides access to backups of all Exchange databases through one NMM client, even though they came from multiple Exchange servers in the DAG. You perform the recovery to the Exchange server that is hosting the active database copy. The recovery process to recover from a DAG backup is the same as a normal DAG recovery. You can recover public folder mailboxes (Exchange Server 2013 and 2016) and public folder databases (Exchange Server 2010) just as you would any other mailbox database. 50 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

51 Mail Item Recovery Restoring Exchange data This topic provides an overview of an Exchange database recovery. In a conventional Exchange recovery, entire databases are replaced or recovered. When you recover entire databases, it overwrites the current content at that location with the recovered data. If you do not want to overwrite the current content, you can recover the databases to an alternate location or server, or to a recovery database (RDB). This allows you to use Exchange server administration tools to browse mail folders and locate individual messages. The figure below illustrates a simple recovery of the Exchange databases in a stand-alone Exchange Server environment. Figure 7 Recovery in a stand-alone Exchange Server environment In a stand-alone environment, you can also recover data to an alternate location, such as a different directory on the same server, or to a different server, such as a backup (nonclustered) Exchange server, as shown in the following figure. This enables you to use NMM to recover content without directly overwriting existing content on the production Exchange server databases. This can be useful for migrating an Exchange server to a different computer, as shown in the following figure. Restoring Exchange data 51

52 Mail Item Recovery Figure 8 Recovery to an alternate location in a stand-alone Exchange Server environment Recovering individual mailboxes, mailbox folders, and messages Retrieving and restoring large backups can use a lot of network, memory, processor, and storage resources. Depending on the topology and architecture a site or organization uses, the recovery operations might also affect production server performance, which can impact mail users. NMM provides several methods for recovering individual items from within an Exchange database, such as individual user mailboxes, mailbox folders, and messages. These methods offer several advantages over full server or database recovery: You can recover backup data to an alternate location without overwriting the existing databases or servers. You can browse and select individual items from the recovered data, and then recover the items to the individual s mailbox. With NMM, you can recover individual items by using one the following methods: Granular level recovery: NMM mounts the backup set to a virtual drive, where you can 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 disk storage space. You can browse and select the data from this virtual drive, as if you were looking at the actual database, down to the message level. Only when you send the recovery request to the NMM server are actual items copied out of the backup set to the user s mailbox. The recovered items are placed in a new Recovered items folder in the user s mailbox. The user can browse and select the items to keep, just like any other folder in their mailbox. Using GLR saves you the time and space needed to browse the actual database, and saves you time and resources by only retrieving the items that you select, not entire databases. 52 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

53 Mail Item Recovery Recover to RDB: You can also recover databases to an RDB, and then browse those databases to select mailboxes, user folders, or messages for recovery. When you restore to an RDB, you can browse the database offline, on a separate server, or from in a folder location that is separate from your online production Exchange server. While this method allows you to browse and retrieve items without overwriting your live Exchange databases or user mailbox, recovery to a RDB does require disk space, network resources, and processor resources to stage the databases in the RDB. When you recover to an RDB, it takes time to copy gigabytes or terabytes of data from one location to another. NMM recovers the backup to the RDB, and then you can browse and retrieve individual items. Compare the following figures, which illustrate: Recover using NMM Granular Level Recovery. Recover to an RDB, and recover data from the RDB to a user mailbox. Recovering individual mailboxes, mailbox folders, and messages 53

54 Mail Item Recovery Figure 9 Recover using NMM granular level recovery 54 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

55 Mail Item Recovery Figure 10 Recover to an RDB, and then recover data from the RDB to a user mailbox Recovering individual mailboxes, mailbox folders, and messages 55

56 Mail Item Recovery NOTICE An RDB can only be used for recovering mailbox database data. It cannot be used to recover public folders. Exchange recovery prerequisites This topic describes the required prerequisites for a recovery of Exchange data using NMM. The following requirements must be met before you can recover Exchange Server data: Verify that the correct version of the Messaging API (MAPI) and Collaboration Data Objects (CDO) kit is installed. MAPI client and Collaboration Data Objects on page 26 provides details. For each Exchange database to be recovered, you must select the Exchange check box titled This database can be overwritten by a restore in the Exchange Management Console. This is a Microsoft requirement. In PowerShell, the flag is called Get- MailboxDatabase -Identity <DATABASE NAME> select AllowFileRestore and must be set to true. The Microsoft Exchange documentation provides more information about this checkbox. When creating an RDB, do not use symbols in the folder name. RDB item level recovery fails with an error if the folder name contains a symbol. For example, the folder name used is Recovered Data - sec77-04/03/ :28:45. Exchange does not support restoring public folder mailboxes (Exchange Server 2013 and 2016), or public folder databases (Exchange Server 2010) to RDBs. During recovery, when recovering mailbox items to a production database, ensure that the user mailbox is not full. If the allowed mailbox space is exceeded, then the item level recovery fails. When you overwrite existing databases with the recovery, perform a full level backup after every recovery performed in Exchange Server. This does not apply to RDB or granular restores. Additional requirements for browsing mailboxes The following topic describes the requirements for browsing Exchange RDB mailboxes. Databases must be online. NMM does not display mailboxes in offline databases. For Exchange Server 2010 and 2013, the MAPI/CDO 1.21 kit must be installed. Exchange System Attendant and Information Store services must be running. 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 or received. You must have backed up the writer set, database or storage group save set: For Exchange Server 2010: Writer: APPLICATIONS:\Microsoft Exchange 2010 Database: APPLICATIONS:\Microsoft Exchange 2010\Database For Exchange Server 2013: Writer: APPLICATIONS:\Microsoft Exchange EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

57 Mail Item Recovery Database: APPLICATIONS:\Microsoft Exchange 2013\Database For Exchange Server 2016: Writer: APPLICATIONS:\Microsoft Exchange 2016 Database: APPLICATIONS:\Microsoft Exchange 2016\Database Additional requirements for recovering databases in a DAG The following topic provides requirement details for recovering an Exchange DAG database. For DAG recovery, ensure that the database recovery node and state are correct. You must perform the recovery to the DAG member server on an active node. The restored databases must be in active state. Passive copies of the databases must be in Exchange replication suspended state. If the copies are not in suspended state, then you must manually suspend passive copies before a recovery is performed. You can suspend replication in three ways: By using the Exchange Shell command and calling Suspend-MailboxDatabaseCopy cmdlet For Exchange Server 2010, through the Exchange Management Console using Suspend Database Copy For Exchange Server 2013 and 2016, through the Exchange Admin Center using Suspend Resume the passive database copies after the restore. The Microsoft documentation provides details. Configuring Exchange Server recovery Specifying Exchange recovery options This section provides the required procedures for configuring an Exchange Server recovery. Procedure 1. Open the NMM client user interface. 2. Select the NetWorker Server on which the NMM client software was configured for backup. 3. If the NMM client is part of a cluster, select the virtual client to which you are recovering data. You can select the virtual client from the client list attribute in the application toolbar. 4. From the left pane, select Exchange 2010 Recover Session, Exchange 2013 Recover Session, or Exchange 2016 Recover Session and then select one of the following: Database Recover to view Exchange database backups and recover to RDB and perform either in-place recovery or alternate recovery from database backups. This is the default option for Exchange Server 2010 and 2013 and the only available option for Exchange Server RDB Mailbox Recover to browse and recover mailbox items from existing RDB databases. Granular Level Recover to browse and recover items from databases without first having to restore the database to an RDB. Additional requirements for recovering databases in a DAG 57

58 Mail Item Recovery 5. In the Exchange Server Session toolbar, click Recover Options. 6. Select the type of recovery to perform: To recover data for Exchange Server and retain all existing Exchange transactions that occurred after the time of backup, select Include existing logs (Roll forward recovery). To recover data for Exchange Server up to the time of backup only and to not include subsequent transactions, select Include logs only from this restore (Pointin-time recovery). After performing a point-in-time recovery, roll-forward recovery cannot be performed because the point-in-time recovery replaces the logs that were generated after the backup. To mount the database after the restore, select Put database online after restore. To recover the database and transaction logs from the backup without attempting to replay the transaction logs, select Do not replay the transaction logs. The database also cannot be mounted after the restore. If you select this option, you must manually replay the transaction logs by running the Exchange utility eseutil.exe. To specify the number of retries when attempting to mount the database, select a number from the Number of attempts to try before failing on mount dropdown list. 7. Click OK to close the Exchange Recover Options dialog box. 8. From the navigation tree, expand the folder Microsoft Exchange 2010, Microsoft Exchange 2013, or Microsoft Exchange Select the Exchange databases that are to be recovered. 10.From the Exchange 2010 Recover Session, Exchange 2013 Recover Session, or Exchange 2016 Recover Session toolbar, click Recover. Configuring roll-forward recovery of an Exchange server in a DAG environment NOTICE Perform the recovery from the node where the recovered database is currently active. Procedure 1. To identify the Exchange database that must be recovered: Use the Exchange Management Console (EMC), the Exchange Administrative Console (EAC), or a shell script 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 57 provides additional details. 2. In the Exchange Management Console or Exchange Administrative Console application, select the This database can be overwritten by a restore checkbox. 3. In the Exchange Management shell, stop replication of any passive copies of the database with the suspend-mailboxdatabasecopy command. The topic Additional requirements for recovering databases in a DAG provides additional details. For example: Suspend-MailboxDatabaseCopy -Identity "bv-e15svr1\first Database" 58 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

59 Mail Item Recovery 4. Open the NMM client. 5. Select the NetWorker Server on which the NMM client software was configured for backup. 6. On the main toolbar, select the Client drop-down menu, and then select the client that is the Exchange DAG. 7. From the left pane, select Exchange Recover, and then select Database Recover (default) To view Exchange database backups. 8. Click View and then click Refresh. 9. From the navigation tree, expand themicrosoft Exchange 2010 or the Microsoft Exchange 2013 folder. 10.Select the Exchange Server items that you want to restore. You can select more than one database for recovery. You can select backups of active or 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: If you need to change the options, click Recover Options. This opens the Exchange Recover Options dialog box, where you can change settings on the General, NetWorker, Security, and Exchange tabs. If the summary does not show that it is a Roll-forward recovery, then click Recover Options, go to the Exchange tab, and in the Transaction Log File Replay dialog, verify that Include existing logs (Roll-forward recovery) is selected. This is the default setting, but it might have been changed if the previous recovery was a point-in-time recovery. If the options are okay, click the Start Recover button. This closes the Exchange Recover Options dialog box and starts the recovery. 13.Click Restore. 14.After the restore operation completes, restore replication between the nodes with the resum boxdatabasecopy command. For example: resum boxdatabasecopy -Identity "bv-hood-e15svr1\first Database" NOTICE Perform a full backup after performing a roll-forward recovery. Recovery procedures The following topics describe the procedures on methods to perform a recovery using NMM. Recovering NetWorker Module for Microsoft Exchange backups NetWorker Module for Microsoft Exchange (NME) and NMM can not be installed on the same client. NME and NMM use some of the same binaries for item level browsing and Recovery procedures 59

60 Mail Item Recovery recovery, so running both NME and NMM on the same client causes versioning conflicts for the common binaries. To recover NME data after migrating from NME to NMM, perform the following steps: Procedure 1. Uninstall NMM, leaving the NetWorker client software running. 2. Install NME. 3. Recover the NME data. 4. Uninstall NME. 5. Re-install NMM. Mounting the database after recovery Performing Exchange Server recovery Performing a full recovery Certain Exchange pre- and post-restore operations enable quick access to after recovery. Until you remount Exchange databases, is not available for users to browse and verify. NMM provides options to automatically mount Exchange databases after restore. The Exchange administrator can decide if a restore of a particular Exchange database is required and if an automatic mounting of the database must be done after the restore is complete: If this option is specified, then the database is mounted after the successful restore of the Exchange Server. If this option is disabled, then the administrator must manually mount the database. By default, this option is enabled in NMM. The NetWorker Module for Microsoft Administration Guide describes how to select or disable the automatic mounting option. This section provides information on performing an Exchange Server recovery. You can recover the contents of a backed up database to the original database by performing full recovery. Procedure 1. From the left pane, select Exchange Recover Session, and then select one of the following: Database Recover (default) to view Exchange database backups. RDB Mailbox Recover to browse and recover Exchange Server items from existing RDB databases. Granular Level Recover to browse and recover items from databases without first having to restore the database to an RDB. 2. If no databases appear, click View > Refresh. 3. Select the database in the NMM user interface. 4. If the database is not listed, select a browse time that includes the desired backup. The NetWorker Administration Guide provides details. 60 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

61 Mail Item Recovery 5. Select Recover in the taskbar. NOTICE Always perform a full backup after performing a point-in-time or roll-forward recovery. Performing an advanced recovery In NMM, you can click Recover Session > Advanced Recover to recover a database to one of the following: A selected Recovery Database (RDB) Exchange Server 2010 Service Pack 1, Rollup 6 or later, Exchange Server 2013, and Exchange Server 2016 support the ability to restore data directly to a RDB. Mounting the recovered data as a RDB allows you to restore individual mailboxes or individual items in a mailbox. Public folders cannot be recovered to an RDB. An alternate database mounted on the mailbox server. A remote database In remote database recovery, a selected mailbox database is restored to a remote mailbox server, in the Exchange DAG where the active database resides. The remote database recovery option is only available for Exchange Server DAGs and not for Exchange Server stand-alone. Alternate and remote recovery are supported only in the same domain. Cross-domain Exchange 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 Administrative Console (EAC), or a shell script to determine the DAG member where the active copy of the database resides. b. Log on to the Exchange member that is running the active copy of the database that is to be recovered. c. From the EMC, open the database properties and select the This database can be overwritten by a restore checkbox. 2. Suspend all passive copies of the database that are to be recovered. The topic Additional requirements for recovering databases in a DAG on page 57 provides details. 3. From the left pane, select Exchange Recover Session, and then select Database Recover (default). 4. Select the DAG name for the client on which the NMM client software was configured for backup. 5. If no databases appear, click View > Refresh. 6. Select the DAG database to be recovered. You can browse and recover individual mailboxes and mailbox items from the list on the right pane. 7. In the Exchange Recover Session toolbar, click the Advanced Recover option. Performing Exchange Server recovery 61

62 Mail Item Recovery The Advanced Recovery dialog box appears. The Steps group lists the three steps for recovery: Select Recovery Select DB & Server Summary Figure 11 Advanced Recovery dialog Select Recover Options to skip the steps for Advanced Recovery and perform full recovery of the database listed in Database (Source). 8. In the Select Recovery Type group, under Recovery Type, select one of the following choices and click Next: Recovery Database (RDB) Recovery Recovering to a recovery database (RDB) on page 63 provides the remaining steps of the procedure. Alternate Database Recovery Recovering to an alternate database on page 65 provides the remaining steps of the procedure. Remote Database Recovery Recovering to a remote database on page 65 provides the remaining steps of the procedure. 9. The Exchange Recovery Summary dialog box appears. This dialog lists the Exchange Server Recovery options, the NetWorker Recovery Options and allows you to review the details before proceeding. Figure 12 Exchange Recovery Summary dialog To proceed with recovery, click Start Recovery. 62 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

63 Mail Item Recovery Recovering to a Recovery Database (RDB) RDB recovery is possible only when Exchange 2010 Service Pack 1, Rollup 6 or later, Exchange Server 2013, or Exchange Server 2013 is installed. The following recovery configurations are possible: An RDB can be created and recovered on a DAG member server that has a passive copy of the database. An RDB recovery can be done from any DAG node for any DAG Mailbox databases. An RDB recovery can be performed from other mailbox server which is not part of the DAG but part of the same Exchange organization. To browse the Exchange Server Recovery Database (RDB) for mailbox, folder, and message recovery, it is no longer necessary to install both the CAS and mailbox roles on the same server. In a multi-tenant environment, an administrator is created for each tenant. But when the user logs in as a domain administrator and performs RDB browsing, there is a conflict in names due to existence of more than one administrator. To work around this issue, create a new user (for example, NMMBackupUser) and add this user as member of the Organization Management group to each of the tenants. RDB browsing fails if the user credentials used for the operation have an Alias in Active Directory. In this situation, you must create a user (without an Alias) and install NMM with the credentials of the new user. Provide the necessary permissions and use the user account for RDB browsing operations. Performing an RDB recovery Procedure 1. In the Exchange Recover Session toolbar, click the Advanced Recover option. 2. In the Advanced Recovery dialog, select Recovery Database (RDB) Recovery and click Next. The Manage RDB dialog appears, as shown in the figure below. Figure 13 Manage RDB dialog 3. To create an RDB, click Create. The Create RDB dialog box appears. Performing Exchange Server recovery 63

64 Mail Item Recovery Figure 14 Create RDB dialog 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 logs path and Mailbox databases that reside on the same volume could not be stored in the same file path location. This restriction has been lifted. 7. Click Create. The new RDB is created and appears in the Recovery Database (RDB) List. 8. From the Manage RDB dialog, you can also: Delete a RDB Select the RDB from the Recovery Database (RDB) List and click Delete. Figure 15 Delete confirmation dialog box Unmount a RDB If a 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 for recovery. To unmount a RDB, select the RDB from the Recovery Database (RDB) List and click Unmount. Mount a RDB Select an RDB from the Recovery Database (RDB) List and click Mount. Note Only one RDB can be mounted at a time. Ensure that the RDB is mounted on the current node of the NMM client for successful recovery. If the recovered database is not mounted on the current node or if replication is on, then the recovery fails. Overwrite a RDB Select an RDB from the Recovery Database (RDB) List and click RDB Overwrite. 64 EMC NetWorker Module for Microsoft for Exchange Server VSS 9.0 User Guide

65 Mail Item Recovery The RDB is overwritten by the recovery operation. Ensure that the RDB is mounted before proceeding to the next step. 9. Select the created RDB and click Next. Recovering to an alternate database Alternate database recovery is supported on any Mailbox server. In this type of recovery, the backed up Mailbox database is recovered to a new database other than the original Mailbox database. Alternate database recovery is supported in both Exchange Server stand-alone and DAG environments. Procedure 1. In the Advanced Recovery dialog, select Alternate Database Recovery for recovery to an alternate database and click Next. The Select Database dialog with a list of alternate databases appears, as shown below. Figure 16 Select Database dialog box 2. Select the database which you want to recover to and click Next. The Exchange Recovery Summary dialog appears. This dialog lists the Exchange Server recovery options, the NetWorker recovery options and allows you to review the details before proceeding with recovery. 3. To proceed with recovery, click Start Recovery. Recovering to a remote database By performing remote recovery, you can start roll-forward or PIT recovery from a mailbox server that is not actually mounted. After remote recovery is started from DAG member server where the Mailbox database is not mounted (the Mailbox database with the passive copy) the recovery service nsrsnap_vss_recover.exe is automatically started 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 a remote recovery to a host that is not a part of DAG. 1. In the Advanced Recovery dialog, select Remote Database Recovery for recovery to an remote database in an Exchange DAG member and click Next. The Select Server dialog appears with a list of remote databases. Performing Exchange Server recovery 65