Contents

Dell PowerProtect 19.6 Data Manager Exchange Server User Guide PDF

1 of 58
1 of 58

Summary of Content for Dell PowerProtect 19.6 Data Manager Exchange Server User Guide PDF

PowerProtect Data Manager for Microsoft Application Agent Exchange Server User Guide

Version 19.6

Dell Inc.

October 2020 Rev. 01

Notes, cautions, and warnings

NOTE: A NOTE indicates important information that helps you make better use of your product.

CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid

the problem.

WARNING: A WARNING indicates a potential for property damage, personal injury, or death.

2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners.

Preface.........................................................................................................................................................................................5

Chapter 1: PowerProtect Data Manager for Microsoft Application Agent Overview....................... 9 PowerProtect Data Manager overview..........................................................................................................................9 Introducing the Microsoft application agent for Exchange.......................................................................................9 Prerequisites....................................................................................................................................................................... 10 Firewall and port considerations.....................................................................................................................................10 PowerProtect Data Manager new deployment overview......................................................................................... 11 PowerProtect Data Manager existing deployment overview...................................................................................11

Chapter 2: Enabling the Microsoft Application Agent for Exchange..............................................13 Microsoft Exchange Server data protection and replication requirements......................................................... 13 Protecting a stand-alone Exchange Server.................................................................................................................13 Protecting Exchange DAG environments.....................................................................................................................14 Install and configure the application agent.................................................................................................................. 14

Prerequisites..................................................................................................................................................................14 Install the Microsoft application agent................................................................................................................... 15 Uninstall the Microsoft application agent with the setup file........................................................................... 15 Configure the Exchange Server operations...........................................................................................................16

Manage the Microsoft application agent for Exchange...........................................................................................23 Support for existing Microsoft application agent backups with PowerProtect Data Manager..................... 24

Supporting existing Microsoft application agent backups with PowerProtect Data Manager................ 24 Using the backup discovery tool for PowerProtect Data Manager management of existing

backups......................................................................................................................................................................25 Troubleshooting Microsoft application agent discoveries on Windows 2008 and Application Direct..........26

Chapter 3: Managing Storage, Assets, and Protection................................................................. 27 Add protection storage ................................................................................................................................................... 27

Troubleshooting protection policy for DD storage unit......................................................................................28 Viewing the DD Boost storage unit password......................................................................................................28

Enable an asset source.................................................................................................................................................... 29 Disable an asset source..............................................................................................................................................29

Discover an Exchange application host....................................................................................................................... 30 Add a protection policy for Exchange database protection................................................................................... 30 Edit the retention period for backup copies............................................................................................................... 33 Delete backup copies........................................................................................................................................................33

Retry a failed backup copy deletion........................................................................................................................34 Export data for deleted backup copies.................................................................................................................. 34 Remove backup copies from the PowerProtect Data Manager database.................................................... 35

Manage the PowerProtect agent service................................................................................................................... 35 About the PowerProtect agent service................................................................................................................. 36 Start, stop, or obtain the status of the PowerProtect agent service............................................................ 36 Troubleshoot the PowerProtect agent service installation...............................................................................37 Troubleshoot the PowerProtect agent service operations............................................................................... 37 Register the PowerProtect agent service to a different server address on Windows.............................. 37

Contents

Contents 3

Recovering the PowerProtect agent service from a disaster.......................................................................... 38 Manage the cloud tier operations with PowerProtect Data Manager................................................................. 39

Add a cloud tier schedule to a protection policy..................................................................................................39 Tier the PowerProtect Data Manager backups from Data Domain to the cloud.........................................40 Restore the cloud tier backups to Data Domain...................................................................................................41

Chapter 4: Performing Self-Service Backups and Restores of Microsoft Exchange Databases.....42 Performing self-service backups of Microsoft Exchange databases................................................................... 42

Back up Exchange Server with the Windows PowerShell backup cmdlet.................................................... 42 Listing backups and save files.................................................................................................................................. 46 Reading the backup object from Windows PowerShell cmdlet output..........................................................48 Formatting the list of backups..................................................................................................................................51

Restore an Exchange application host..........................................................................................................................51 Prerequisite for Exchange restore operations...................................................................................................... 51 Restoring Exchange Server databases.................................................................................................................. 52 Performing granular-level restores......................................................................................................................... 55

4 Contents

Preface As part of an effort to improve product lines, periodic revisions of software and hardware are released. Therefore, all versions of the software or hardware currently in use might not support some functions that are described in this document. The product release notes provide the most up-to-date information on product features.

If a product does not function correctly or does not function as described in this document, contact a technical support professional.

NOTE: This document was accurate at publication time. To ensure that you are using the latest version of this document,

go to the Support website https://www.dell.com/support.

Data Domain (DD) is now PowerProtect DD. References to Data Domain or Data Domain systems in this documentation, in

the user interface, and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many

cases the user interface has not yet been updated to reflect this change.

Purpose This document describes how to configure and use the PowerProtect Data Manager with the Microsoft application agent to back up and restore Microsoft Exchange Server. The PowerProtect Data Manager Administration and User Guide provides additional details about configuration and usage procedures.

Audience This document is intended for the host system administrator who configures and uses the PowerProtect Data Manager with the Microsoft application agent to back up and restore Microsoft Exchange Server.

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

Table 1. Revision history

Revision Date Description

01 October 27, 2020 Initial release of this document for PowerProtect Data Manager version 19.6.

Compatibility information Software compatibility information for the PowerProtect Data Manager software is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

Related documentation The following publications are available on Dell EMC Online Support and provide additional information:

PowerProtect Data Manager Administration and User GuideDescribes how to configure the software. PowerProtect Data Manager Deployment GuideDescribes how to deploy the software. PowerProtect Data Manager Release NotesContains information on new features, known limitations, environment, and

system requirements for the software. PowerProtect Data Manager Security Configuration GuideContains security information. PowerProtect Data Manager AWS Deployment GuideDescribes how to deploy the software to Amazon Web Services

(AWS).

Preface 5

PowerProtect Data Manager Azure Deployment GuideDescribes how to deploy the software to Microsoft Azure. PowerProtect Data Manager Cloud Disaster Recovery Administration and User GuideDescribes how to deploy Cloud DR,

protect VMs in the AWS or Azure cloud, and run recovery operations. PowerProtect Data Manager for Cyber Recovery User GuideDescribes how to install, upgrade, patch, and uninstall the

Dell EMC PowerProtect Cyber Recovery software. PowerProtect Data Manager for File System Agent User GuideDescribes how to configure and use the software with the

File System agent for file system data protection. PowerProtect Data Manager for Microsoft Application Agent Exchange Server User GuideDescribes how to configure

and use the software in a Microsoft Exchange Server environment. PowerProtect Data Manager for Microsoft Application Agent SQL Server User GuideDescribes how to configure and use

the software in a Microsoft SQL Server environment. PowerProtect Data Manager for Oracle RMAN Agent User GuideDescribes how to configure and use the software in an

Oracle Server environment. PowerProtect Data Manager for SAP HANA Agent User GuideDescribes how to configure and use the software in an SAP

HANA Server environment. PowerProtect Data Manager for Storage Direct Agent User GuideDescribes how to configure and use the software with

the Storage Direct agent to protect data on VMAX storage arrays through snapshot backup technology. PowerProtect Data Manager API documentation: https://developer.dellemc.comContains the PowerProtect Data

Manager APIs and includes tutorials to guide to you in their use.

Typographical conventions The following type style conventions are used in this document:

Table 2. Style conventions

Formatting Description

Bold Used for interface elements that a user specifically selects or clicks, for example, names of buttons, fields, tab names, and menu paths. Also used for the name of a dialog box, page, pane, screen area with title, table label, and window.

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

Monospace Used for:

System code System output, such as an error message or script Pathnames, file names, file name extensions, prompts, and syntax Commands and options

Monospace italic Used for variables.

Monospace bold Used for user input.

[ ] Square brackets enclose optional values.

| Vertical line indicates alternate selections. The vertical line means or for the alternate selections.

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

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

You can use the following resources to find more information about this product, obtain support, and provide feedback.

Where to find product documentation https://www.dell.com/support https://www.dell.com/community

6 Preface

Where to get support The Support website https://www.dell.com/support provides access to product licensing, documentation, advisories, downloads, and how-to and troubleshooting information. The information can enable you to resolve a product issue before you contact Support.

To access a product-specific page:

1. Go to https://www.dell.com/support. 2. In the search box, type a product name, and then from the list that appears, select the product.

Knowledgebase The Knowledgebase contains applicable solutions that you can search for either by solution number (for example, KB000xxxxxx) or by keyword.

To search the Knowledgebase:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Knowledge Base. 3. In the search box, type either the solution number or keywords. Optionally, you can limit the search to specific products by

typing a product name in the search box, and then selecting the product from the list that appears.

Live chat To participate in a live interactive chat with a support agent:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Contact Support. 3. On the Contact Information page, click the relevant support, and then proceed.

Service requests To obtain in-depth help from Licensing, submit a service request. To submit a service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests.

NOTE: To create a service request, you must have a valid support agreement. For details about either an account or

obtaining a valid support agreement, contact a sales representative. To find the details of a service request, in the

Service Request Number field, type the service request number, and then click the right arrow.

To review an open service request:

1. Go to https://www.dell.com/support. 2. On the Support tab, click Service Requests. 3. On the Service Requests page, under Manage Your Service Requests, click View All Dell Service Requests.

Online communities For peer contacts, conversations, and content on product support and solutions, go to the Community Network https:// www.dell.com/community. Interactively engage with customers, partners, and certified professionals online.

Preface 7

How to provide feedback Feedback helps to improve the accuracy, organization, and overall quality of publications. You can send feedback to DPAD.Doc.Feedback@emc.com.

8 Preface

PowerProtect Data Manager for Microsoft Application Agent Overview

Topics:

PowerProtect Data Manager overview Introducing the Microsoft application agent for Exchange Prerequisites Firewall and port considerations PowerProtect Data Manager new deployment overview PowerProtect Data Manager existing deployment overview

PowerProtect Data Manager overview Use PowerProtect Data Manager with the application agent to perform the following operations:

Automate the configuration of the application agent backup policy and protection storage settings. Create a catalog of backups that are produced by the application agent, and then monitor that catalog data to determine if

retention policies are being adhered to. Manage the life cycle of backups that are created by the application agentthat is, ensure that the backups are marked for

garbage collection based on the rules of the retention policy.

PowerProtect Data Manager does not change the way that the application agent works. DBAs or system/backup administrators create the backups and perform the restores.

Introducing the Microsoft application agent for Exchange The Microsoft application agent enables an application administrator to protect and recover the Exchange application data on the application host. PowerProtect Data Manager integrates with the Microsoft application agent to check and monitor backup compliance against protection policies. PowerProtect Data Manager also enables central scheduling for backups.

You can install the Microsoft application agent on a Windows Exchange Server host by using the install wizard. Install and configure the application agent on page 14 provides instructions.

NOTE:

PowerProtect Data Manager supports the coexistence of the Microsoft application agent and the File System agent on

Windows.

To enable the discovery and scheduling of backups with PowerProtect Data Manager, you must approve the client in the

PowerProtect Data Manager UI. Manage the Microsoft application agent for Exchange on page 23 provides more

information.

The Microsoft application agent does not support the MetaCacheDatabase (MCDB) feature in Exchange Server 2019.

Ensure that you do not enable MCDB in Exchange Server 2019.

Software compatibility information for the PowerProtect Data Manager software and application agents is provided in the eLab Navigator, available at https://elabnavigator.emc.com/eln/modernHomeDataProtection.

1

PowerProtect Data Manager for Microsoft Application Agent Overview 9

Prerequisites Ensure that your environment meets the requirements for a new deployment or upgrade of PowerProtect Data Manager.

Requirements:

A list of hosts that write backups to DD systems is available. DD OS version 6.1 or later and the DD Management Console (DDMC). All models of DD systems are supported.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use

a DD system directly without DDMC.

Application agent 19.6 or earlier. License: A trial license is provided with the PowerProtect Data Manager software. DPS Applications, Backup, and Enterprise

customers can contact Dell EMC Licensing Support for assistance with a permanent PowerProtect Data Manager license. Large environments require multiple PowerProtect Data Manager instances. Contact Champions.eCDM@emc.com for

assistance with sizing requests. The PowerProtect Data Manager 19.6 download file requires the following:

ESXi version 6.0, 6.5, 6.7, or 7.0. 8 vCPUs, 18 GB RAM, one 100 GB disk, and one 500 GB disk. The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI. TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.

Firewall and port considerations Table 3. PowerProtect Data Manager port requirements

Description Communication Port

SSH communications Bidirectional communication between the SSH client and the PowerProtect Data Manager appliance

22 TCP/UDP

RestServer Bidirectional communication between the HTTP client and the PowerProtect Data Manager appliance

8443 TCP

UI redirect Inbound only 80 TCP

443

LDAP Outbound only 389 TCP/UDP

636 TCP

Discovery (devices) Outbound between the PowerProtect Data Manager appliance and the device

3009 TCPStorage Direct and DD system

5989 TCPSMI-S

PowerProtect Data Manager agent

Bidirectional communication between the database hosts and the PowerProtect Data Manager appliance

7000 TCP

Embedded VM Direct service

Outbound 9090 TCP

10 PowerProtect Data Manager for Microsoft Application Agent Overview

PowerProtect Data Manager new deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the application agent.

Steps

1. Design how to group the backups based on the storage requirements and retention policies.

The account team can help with backup storage design.

2. Install DD Management Center (DDMC).

PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use

a DD system directly without DDMC.

3. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

4. Add external DD systems or DDMC to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

5. Install the application agent on the appropriate hosts and connect them to PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

This operation should be performed by DBAs.

6. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

7. After the approval of agent requests, PowerProtect Data Manager must run a discovery operation to discover the assets.

The PowerProtect Data Manager Administration and User Guide provides information.

8. Add a protection policy for groups of assets that you want to back up.

You must add credentials to the database so that PowerProtect Data Manager can access the database and create backups. The PowerProtect Data Manager Administration and User Guide provides instructions.

NOTE: After you create a centralized protection job, the first backup is a full backup.

9. Add Service Level Objectives to the protection policy to verify that the protected assets meet the Service Level Agreements (SLAs).

The PowerProtect Data Manager Administration and User Guide provides instructions.

Configuration is complete.

10. Monitor protection compliance in the PowerProtect Data Manager dashboard.

PowerProtect Data Manager existing deployment overview Familiarize yourself with the high-level steps required to install PowerProtect Data Manager with the application agent in an existing environment.

Steps

1. Install DD Management Center (DDMC).

PowerProtect Data Manager uses DDMC to connect to the DD systems. The DD Management Center Installation and Administration Guide provides instructions.

NOTE: DDMC is required with a DD OS version earlier than 6.1.2. With DD OS version 6.1.2 or later, you can add and use

a DD system directly without DDMC.

PowerProtect Data Manager for Microsoft Application Agent Overview 11

2. Install PowerProtect Data Manager from the download file.

The PowerProtect Data Manager Deployment Guide provides instructions.

3. Add external DD systems or DDMC to PowerProtect Data Manager.

The PowerProtect Data Manager Administration and User Guide provides instructions on how to add protection storage.

4. Upgrade the application agent or uninstall and then reinstall the application agent on the hosts and connect them to PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

This operation should be performed by DBAs.

5. Add new or approve pending agent requests in the PowerProtect Data Manager according to the instructions in the next "Enabling" chapter.

6. After the approval of agent requests, PowerProtect Data Manager must run a discovery operation to discover the assets.

The PowerProtect Data Manager Administration and User Guide provides information.

7. Add a protection policy for groups of assets that you want to back up.

You must add credentials to the database so that PowerProtect Data Manager can access the database and create backups. The PowerProtect Data Manager Administration and User Guide provides instructions.

NOTE: After you create a centralized protection job, the first backup is a full backup.

8. Add Service Level Objectives to the protection policy to verify that the protected assets meet the Service Level Agreements (SLAs).

The PowerProtect Data Manager Administration and User Guide provides instructions.

Configuration is complete.

9. Monitor protection compliance in the PowerProtect Data Manager dashboard.

12 PowerProtect Data Manager for Microsoft Application Agent Overview

Enabling the Microsoft Application Agent for Exchange

Topics:

Microsoft Exchange Server data protection and replication requirements Protecting a stand-alone Exchange Server Protecting Exchange DAG environments Install and configure the application agent Manage the Microsoft application agent for Exchange Support for existing Microsoft application agent backups with PowerProtect Data Manager Troubleshooting Microsoft application agent discoveries on Windows 2008 and Application Direct

Microsoft Exchange Server data protection and replication requirements PowerProtect Data Manager can manage and monitor data protection and replication for Microsoft Exchange Server assets through integration with the Microsoft application agent.

After installing the Microsoft application agent, review the following information for additional requirements before adding the Microsoft application agent as an asset source in PowerProtect Data Manager and discovering the Exchange Server assets.

Verify that the environment meets the following requirements:

Ensure that all clocks on the Exchange Server host, domain controller, and PowerProtect Data Manager are time-synced to the local NTP server to ensure discovery of the backups.

Ensure that the Exchange Server and the PowerProtect Data Manager system network can see and resolve each other. Ensure that port 7000 is open on the Exchange Server host. Ensure that DNS is configured correctly on the application agent host for Exchange Server. Ensure that DNS is configured correctly on the PowerProtect Data Manager host and the name resolution matches.

Protecting a stand-alone Exchange Server Learn how to configure protection of a stand-alone Exchange Server.

Steps

1. Add storage for Data Domain Management Console or the external Data Domain.

Add protection storage on page 27 provides information.

2. Install the Microsoft application agent on the Exchange Server host.

Install and configure the application agent on page 14 provides information.

3. Configure the required user privileges on the Exchange Server host.

Configure users with the App Agent Exchange Admin Configuration tool on page 16 provides information.

4. Add or approve the Microsoft application agent in PowerProtect Data Manager. Manage the Microsoft application agent for Exchange on page 23 provides information.

5. Discover the Exchange application host.

Discover an Exchange application host on page 30 provides information.

6. Create a protection policy to protect the Exchange host.

2

Enabling the Microsoft Application Agent for Exchange 13

Add a protection policy for Exchange database protection on page 30 provides information.

NOTE: You cannot perform a backup to a secondary Data Domain device. You can only restore from a secondary Data

Domain device

Protecting Exchange DAG environments Learn how to configure the protection of Exchange database availability group (DAG) environments.

About this task

On each node in the DAG, repeat the steps to install the Microsoft application agent, and then add and discover the application host in PowerProtect Data Manager.

CAUTION: Protection of the nodes in a DAG requires that all the nodes be registered to the PowerProtect Data

Manager server.

Steps

1. Add a storage system.

Add protection storage on page 27 provides information.

2. Install the Microsoft application agent on each node in the DAG.

Install and configure the application agent on page 14 provides information.

3. Configure the required user privileges on each node in the DAG.

Configure users with the App Agent Exchange Admin Configuration tool on page 16 provides information.

4. Add or approve the Microsoft application agent on each node in the DAG. Manage the Microsoft application agent for Exchange on page 23 provides information.

5. Discover each Exchange application host.

Discover an Exchange application host on page 30 provides information.

6. Create a protection policy to protect the assets of the Exchange hosts.

Add a protection policy for Exchange database protection on page 30 provides information.

NOTE: You cannot perform a backup to a secondary Data Domain device. You can only restore from a secondary Data

Domain device.

Install and configure the application agent

Prerequisites

Ensure that an Exchange Server environment meets the following prerequisites before you install the Microsoft application agent:

Install the following applications on the Windows host:

Microsoft Exchange Server .NET Framework 4.0 or later

If you are installing ItemPoint for granular-level recovery, install .NET Framework 4.5.

In the PowerProtect Data Manager UI, select Agent Downloads from the System Settings menu, select the Microsoft application agent download package, msappagent196_win_x64.zip, and then download the package to the Windows Exchange Server host.

Log in to the Exchange Server host as an Administrator to install the Microsoft application agent.

14 Enabling the Microsoft Application Agent for Exchange

Install the Microsoft application agent

Learn how to install the Microsoft application agent.

About this task

NOTE: In DAG environments, you must install the Microsoft application agent on each node in the DAG.

Steps

1. In the PowerProtect Data Manager UI:

a. Select Agent Downloads from the System Settings menu. b. Select the Microsoft application agent download package, msappagent196_win_x64.zip.

c. Download the package to the host where you want to install the Microsoft application agent.

2. Open msappagent196_win_x64.zip with WinZip.

3. Use WinZip to unzip the msappagent196_win_x64.zip file.

4. In the unzipped directory, launch emcmsappagent-19.6.0.0.exe. The installation wizard appears.

5. On the Welcome Wizard page, select I agree to the license term and agreements, and then click Next.

6. On the Change Install Location page, perform one of the following tasks:

To install the Microsoft application agent in the default directory, leave the installation location as is.

The default installation directory is C:\Program Files\DPSAPPS\MSAPPAGENT.

To specify a different installation location, perform the following steps:

a. Click Change. b. In the dialog box that appears, specify the installation location. c. Click OK.

NOTE: Even when you choose to install the Microsoft application agent in a non-default directory, the lockbox is

created in the default directory, C:\Program Files\DPSAPPS\common\lockbox. The PowerProtect Data

Manager integration requires that the lockbox is located in the default directory.

7. Click Next.

8. On the Configure Installation Options page, specify the following options as required to integrate the Microsoft application agent with PowerProtect for centralized or self-service protection of Exchange Server data:

To install the Microsoft application agent software, select Application Direct. To enable granular-level restores, select ItemPoint.

This option installs ItemPoint for Microsoft Exchange Server, which you can use to perform granular-level restores.

You must specify the PowerProtect appliance details by performing the following steps:

a. Select PowerProtect Data Manager Integration. b. In the Appliance Hostname or IP address field, type the hostname or IP address of the PowerProtect server.

NOTE: Installation of the Microsoft application agent requires port 7000 on the Exchange Server and port 8443 on

PowerProtect to be open bidirectionally. These ports enable communication between the Microsoft application agent

and PowerProtect.

9. Click Install >.

10. On the Complete the Setup page, click Finish.

Uninstall the Microsoft application agent with the setup file

About this task

To uninstall the Microsoft application agent for Exchange Server with the setup file, perform the following steps.

Enabling the Microsoft Application Agent for Exchange 15

NOTE: If a granular-level restore was performed since the last reboot of the host, Microsoft application agent requests a

reboot during an uninstall operation. The Microsoft application agent installs and uses the Eldos CBFS driver for granular-

level restores. The Eldos CBFS driver is loaded during the granular-level restore operation. Microsoft requires the driver to

be unloaded prior to an uninstall operation.

Steps

1. Launch emcmsappagent-19.6.0.0.exe.

2. On the Install Modification page, select Remove, and then click Next.

3. On the Configure Uninstallation Options page, click Remove.

4. On the Complete the Setup page, click Finish.

Configure the Exchange Server operations

You must complete the required configurations to enable the backup and restore operations in an Exchange Server environment. The following topics provide the product configuration details.

Configure users with the App Agent Exchange Admin Configuration tool

In order to protect a stand-alone Exchange Server or Exchange database availability group (DAG) with the Microsoft application agent you must configure an account with the required privileges.

The App Agent Exchange Admin Configuration tool simplifies configuring security group memberships by ensuring that users have all the required Active Directory security group memberships and PowerShell management roles.

The App Agent Exchange Admin Configuration tool enables you to create or reset account permissions with the necessary privileges to perform backup and recovery operations on an Exchange Server. After installing the Microsoft application agent, use the tool to create an account, or to modify, validate, and update existing account privileges.

To use the App Agent Exchange Admin Configuration tool, you must be logged in with domain administrator permissions. You can use an existing non-administrative user to run the App Agent Exchange Admin Configuration tool only if you select Skip Active Directory Authentication and configure the user on each Exchange Server node. This option skips the Active Directory authentication and authorization operations for the user, and only sets the user as the Microsoft application agent Exchange user account in the registry for backup and recovery operations.

The Microsoft application agent uses the user account that is set in the registry by the App Agent Exchange Admin Configuration tool to perform backups and database or granular-level recovery.

To create a Microsoft application agent Exchange administrator account, the App Agent Exchange Admin Configuration tool performs the following steps:

Creates an Active Directory user account. Creates a custom Exchange security group, which is EMC App Agent Exchange Admin Roles. Adds the user account to the groups that are listed in the following table.

Table 4. Permissions that the Exchange Admin Configuration tool configures

User group Exchange Server role

Security group memberships on the Microsoft application agent client host

Local Administrator

Security group memberships on Domain Controller Remote Desktop Users

Exchange Security Group memberships Exchange Servers EMC App Agent Exchange Admin Roles, which include: Exchange Roles Database Copies Databases Disaster Recovery Mailbox Import Export Mail Recipient Creation Mail Recipients

16 Enabling the Microsoft Application Agent for Exchange

Table 4. Permissions that the Exchange Admin Configuration tool configures (continued)

User group Exchange Server role

View-Only Configuration

Configuring an administrative user

You can perform the following actions after clicking Configure Admin User:

Create a Microsoft application agent Exchange Admin user, configure the permissions that are required for Exchange backup and recovery (both database and GLR), and set the user account in the registry.

Update an existing Exchange Admin user's permissions to those that are required for Exchange backup and recovery (both database and GLR), and set the App Agent Exchange administrator account in the registry.

Set an existing user as an App Agent Exchange Admin account in the registry.

Configure an administrative Exchange backup account

You can configure an administrator user with the App Agent Exchange Admin Configuration tool by creating an account, or by using an existing account.

Steps

1. In the App Agent Exchange Admin Configuration window, click Configure Admin User.

2. Under Action, select one of the following options:

Create new adminCreate an Exchange user account for Microsoft application agent backup and recovery operations. Configure existing userUse an existing Exchange user account for Microsoft application agent backup and recovery

operations.

3. Type the User Name and Password.

4. If you are creating an account:

a. In the Confirm Password field, retype the password. b. From the Database list, select the Exchange database for which the user will perform backups and recoveries.

5. (Optional) Select Assign Organization Management rights.

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

NOTE: If you select Assign Organization Management rights, the Microsoft application agent adds the user to the

Organization Management group. The tool does not create a EMC App Agent Exchange Admin Roles security group.

If you do not select this option and also do not select the Skip Active Directory Authentication option, the Microsoft

application agent will create an Active Directory security group called EMC App Agent Exchange Admin Roles and add

the user to that group.

6. (Optional) Select Create ContentSubmitters security group.

This option creates a ContentSubmitters Active Directory security group. This option is unavailable if a ContentSubmitters group is already created in the Active Directory. This option is available only on Exchange Server 2013 and later.

7. (Optional) If you are configuring an existing user, select Skip Active Directory Authentication.

This option skips the Active Directory authentication and authorization operations for the user, and only sets the user as the Microsoft application agent Exchange user account in the registry for backup and recovery operations.

NOTE: This option should be selected when you manually configure a user.

8. Click Configure. The output window shows the status of the configure operation, including any warning or error messages.

Results

The user receives the necessary permissions to backup and restore the Exchange database. View the configured user in the Properties window of the Exchange Servers security group, on the Members tab.

Enabling the Microsoft Application Agent for Exchange 17

Configuring an administrator in a parent and child domain environment

Consider the following when configuring a user in a parent and child domain environment.

In a parent child domain environment, when you create a user in a child domain, then the user is added to the Active Directory of the child mailbox server. However, the user inherits the security group membership from the parent domain.

The App Agent Exchange Admin Configuration Tool does not support user configurations for the following scenarios:

To create a user in the parent Active Directory from a child mailbox server. To create a user in the child Active Directory from a parent mailbox server. To create a user from a child or parent mailbox server in a different domain of the same forest.

Manually configure a user in these scenarios.

Examples of administrative user configurations

This section provides examples of configuring an administrator with the App Agent Exchange Admin Configuration tool.

Configuring or modifying an Admin user with Organization Management rights

The user will be a member of the Organization Management group, but will not be a member of the EMC App Agent Exchange Admin Roles group.

1. In the App Agent Exchange Admin Configuration window, click Configure Admin User. 2. Complete the Configure Admin User page, and then select Assign Organization Management rights. 3. Click Configure. 4. Verify that all the configurations are correctly set, System Configuration Checker.

Configuring or modifying an Admin user without Organization Management rights

The user will be a member of the EMC App Agent Exchange Admin Roles group, but will not be a member of the Organization Management group.

1. In the App Agent Exchange Admin Configuration window, click Configure Admin User. 2. Complete the Configure Admin User page. Ensure that Assign Organization Management rights is not selected. 3. Click Configure. 4. Verify that all the configurations are correctly set by running the System Configuration Checker.

Manually configuring an Exchange backup Admin user

1. Configure the user manually in Active Directory, and ensure that the user has the appropriate roles and rights, as described in Configure users with the App Agent Exchange Admin Configuration tool on page 16.

2. In the App Agent Exchange Admin Configuration window, click Configure Admin User. 3. On the Configure Admin User page, perform the following steps:

a. Select Configure Existing User. b. In the User Name and Password fields, type the required information. c. Select Skip Active Directory Authentication. d. Click Configure.

Configuring a non-administrative user

You can create an Exchange backup user with non-administrative privileges.

In order to configure a non-admin Windows user to perform Exchange protection operations, you must create a domain user and assign that user the required privileges with the App Agent Exchange Admin Configuration tool.

NOTE: You can use a non-administrative user to run the App Agent Exchange Admin Configuration tool only if you select

Skip Active Directory Authentication and configure the user with the tool on each Exchange Server node.

Creating a non-administrative domain account for creating Exchange backup users

You can create Exchange backup users with a non-administrative Windows account if it is configured with the required privileges.

Prerequisites

You must be logged in to a domain controller as an administrative domain user.

18 Enabling the Microsoft Application Agent for Exchange

Steps

1. Create a new domain user.

Once created, the user is listed in the Active Directory Users and Computers window.

2. Open the user Properties window, and in the Members Of tab, ensure that the user is added to the following user groups:

User right Description

Remote Desktop Users Allows the user to remotely connect to a domain controller.

Account Operators Allows the user to create domain user accounts.

The user is also a member of the Domain Users group by default.

3. Open the Group Policy Management Editor window, and under Windows Settings > Security Settings > Local Policies > User Rights Assignment, grant the user the following rights:

User right Description

Allow log on locally Allows the user to log on to all domain controllers in the domain.

Allow log on through Remote Desktop Services

Allows the user to log on to all domain controllers in the domain through Remote Desktop Services.

Account Operators Allows the user to create domain user accounts.

4. To apply the changes, log out of the domain controller.

Configure a non-administrative Exchange backup account

You can use the App Agent Exchange Admin Configuration tool to configure a non-administrative Windows account to perform Exchange backup and recovery.

Prerequisites

Log in to a domain controller with a user who can create domain accounts. Creating a non-administrative domain account for creating Exchange backup users on page 18 provides details on how to configure a non-administrative user with the required privileges.

Steps

1. Create a new domain user.

Once created, the user is listed in the Active Directory Users and Computers window.

2. Open the user Properties window, and in the Members Of tab, ensure that the user is added to the following user groups:

User right Description

Remote Desktop Users Allows the user to remotely connect to a domain controller.

Organization Management Allows the user administrative access to the Exchange organization.

The user is also a member of the Domain Users group by default.

3. Perform the following steps on each Exchange Server that you want to back up, including all servers that are part of a database availability group (DAG):

a. Log on to the Exchange Server as a local Administrator. b. In Computer Management > Local Users and Groups, add the new user to the Administrators group. c. To apply the changes, log out of the Exchange Server. d. Log on to the Exchange Server as the new user. e. Launch the App Agent Exchange Admin Configuration tool. f. In the App Agent Exchange Admin Configuration tool window, click Configure Admin User. g. On the Configure Admin User page, perform the following actions:

i. Select Configure existing user. ii. Enter the credentials for the user created in step 1. iii. Select Skip Active Directory Authentication.

Enabling the Microsoft Application Agent for Exchange 19

NOTE: Do not select Assign Organization Management rights, otherwise the configuration will fail.

iv. Click Configure.

Results

The user is set in the registry and assigned the non-administrative permissions that are required for Exchange backup and recovery.

Update Admin Password

Click Update Admin Password to modify the Microsoft application agent Exchange administrator account password and update the registry.

Validating an existing administrator

Use the App Agent Exchange Admin Configuration tool to verify whether a Microsoft application agent Exchange administrator account is correctly configured.

About this task

NOTE: Validating an existing administrator in a parent and child domain environment can fail because the tool might try to

contact Active Directory to validate credentials from the registry.

Steps

1. In the App Agent Exchange Admin Configuration window, click Validate an existing Admin.

2. In the User Name and Password fields, type the required information.

3. Click Validate. A window that lists the Exchange servers in your environment opens.

4. Select each server that the user must back up or recover, and then click OK. The window closes and the validate operation starts. The output window shows the status of the operation including any warning or error messages.

Results

The output window shows the results of the validate operation.

Import the configuration file

Use the Import-ExchangeBackupConfigFile cmdlet to import the configuration parameters needed to perform a specific operation to an object.

Import the configuration parameters to an object that you can use to perform operations such as backups, listing backups, mounting backups, and restores by using the corresponding cmdlets.

Use the following syntax to import the configuration file parameters with the Import-ExchangeBackupConfigFile cmdlet:

= Import-ExchangeBackupConfigFile [-Backup [ ]] [-Identity [ ]] [-Restore ] [ ]

where:

Specifies the object that contains the configuration parameters to use with other cmdlets.

-Backup

Specifies that the configuration parameters needed to perform the backup using the Backup-Exchange cmdlet will be imported. This parameter applies to the PowerProtect Data Manager integrated backup workflows for both self-service and centralized backups.

-Identity

20 Enabling the Microsoft Application Agent for Exchange

This optional parameter is only used with the -Backup parameter. This parameter specifies that the configuration parameters needed to perform the backup of the specified database using the Backup- Exchange cmdlet will be imported. Specify the database identity with this parameter.

-Restore

Specifies that the configuration parameters needed to list, mount, and restore the backups will be imported. This parameter applies to the PowerProtect Data Manager integrated backup workflows for both self-service and centralized backups.

Specifies any combination of the following common PowerShell parameters:

Verbose Debug ErrorAction ErrorVariable WarningAction WarningVariable OutBuffer PipelineVariable OutVariable The following Microsoft article provides information about the common PowerShell parameters:

https://go.microsoft.com/fwlink/?LinkID=113216

To obtain the full help information about the cmdlet, run the following command:

help Import-ExchangeBackupConfigFile -full

Set the lockbox for Exchange server

When you first use the PowerProtect Data Manager UI to add the Microsoft application agent and create the protection policy for Exchange data protection, the PowerProtect Data Manager automatically configures the lockbox for the Exchange server.

In the following cases, you can re-register the lockbox for the Exchange server by using the Set Lockbox button in the PowerProtect Data Manager UI:

The existing lockbox has become corrupted and you want to re-register the lockbox. A new storage unit has been configured and you want to register the lockbox for the storage unit settings.

To re-register the lockbox for the Exchange server in the PowerProtect Data Manager UI:

1. Go to Protection > Protection Policies. 2. Select the protection policy for the Exchange server, and click Set Lockbox.

A message appears, stating that the lockbox has been configured and the job will start in the specified policy window.

Import the EMCExchangeBackupRestore PowerShell modules to Exchange Server 2010

For the backup and restore cmdlets to function on Exchange Server 2010, you must manually import the EMCExchangeBackupRestore modules.

Run the following commands in the Exchange Management Shell on Exchange Server 2010:

Import-Module EMCExchangeBackupRestore.psm1

Import-Module EMCExchangeBackupRestore.dll

Update-FormatData -AppendPath "C:\Program Files\DPSAPPS\MSAPPAGENT\PowerShell\Modules \EMCExchangeBackupRestore\EMCExchangeBackupRestore.Format.ps1xml"

Enabling the Microsoft Application Agent for Exchange 21

NOTE: You are only required to import the EMCExchangeBackupRestore modules with Exchange Server version 2010.

Add settings for centralized backups of Exchange DAG

For centralized backups of databases in an Exchange DAG, you must add the required settings for the type of backup and the server order list.

About this task

You must specify one of three types of DAG backups:

Passive backup Active backup Preferred passive backup

You can also specify the server order list for the order in which the DAG servers are backed up.

Perform the following steps to specify the settings for centralized Exchange DAG backups.

Steps

1. Create a file named userlockbox.cfg in the required directory:

When the Microsoft application agent is installed in the default directory, create the userlockbox.cfg file in the C:\Program Files\DPSAPPS\common\lockbox directory.

When the Microsoft application agent is installed in a non-default directory, add the common\lockbox subdirectory in the installation directory and create the userlockbox.cfg file in the \common \lockbox directory.

2. In the userlockbox.cfg file, add the following parameter settings:

Specify the type of DAG backup in the backuptype parameter setting. The valid parameter setting is active, passive, or preferred. For example:

backuptype=passive Specify the DAG server order list in the serverorderlist parameter setting. The valid parameter setting is a comma-

separated list of node names. For example:

serverorderlist=node1,node2

Configure the parallelism for centralized Exchange backups

You can configure the parallelism setting for a centralized backup of Exchange databases by setting the clientParallelism parameter value in the userlockbox.cfg file on the Exchange server host.

About this task

The default parallelism setting for a centralized Exchange backup is 16. You can override this default setting with the clientParallelism parameter setting in the configuration file.

NOTE: For a self-service Exchange backup, you can specify the parallelism with the -Parallelism parameter setting in

the Backup-Exchange PowerShell cmdlet, described in Back up Exchange Server with the Windows PowerShell backup

cmdlet on page 42.

Based on the number of CPUs on the host and the parallelism setting, the application agent uses the following effective parallelism value for a centralized Exchange backup:

With 10 or more CPUs, the effective parallelism equals the minimum of the number of CPUs and the parallelism setting, minus 4. For example, with 12 CPUs and a parallelism of 16, the effective parallelism value is 8 (12 minus 4).

With 4 to 9 CPUs, the effective parallelism equals the minimum of the number of CPUs and the parallelism setting, minus 2. For example, with 8 CPUs and a parallelism of 10, the effective parallelism value is 6 (8 minus 2).

22 Enabling the Microsoft Application Agent for Exchange

With fewer than 4 CPUs, the effective parallelism equals the number of CPUs. For example, with 2 CPUs, the effective parallelism value is 2.

If the effective parallelism value is 8, then 8 threads are created for the Exchange backup, with each thread assigned to transfer either an EDB file or the related log files. An asset transfer is complete only when an EDB file and the related log files are both copied to the DD system. Using 8 threads, effectively 4 assets are backed up in parallel from the host.

You can set the clientParallelism parameter in the configuration file according to the following steps.

Steps

1. Ensure that the file named userlockbox.cfg is located in the required directory:

When the Microsoft application agent is installed in the default directory, the userlockbox.cfg file must be located in the C:\Program Files\DPSAPPS\common\lockbox directory.

When the Microsoft application agent is installed in a non-default directory, the userlockbox.cfg file must be located in the \common\lockbox directory.

2. In the userlockbox.cfg file, set the clientParallelism parameter to the required parallelism setting. For example:

clientParallelism=10

Manage the Microsoft application agent for Exchange You can use the PowerProtect Data Manager UI to add a Microsoft application agent for Exchange data protection, approve and reject pending agent requests, and edit and delete existing agents.

Steps

1. Select Infrastructure > Application Agents.

The Application Agents window appears.

NOTE: If the PowerProtect agent service was able to register during the installation, the Exchange host is already listed

and does not need to be added.

2. Click Add. The Add Application/FS Agent window appears.

3. Select one of the following options:

Add FQDN or CSV Filename.

This process is also called whitelisting.

If you select Add FQDN, perform the following steps:

a. Type the fully qualified domain name (FQDN) for the application agent. b. Specify the date until which the application agent is preapproved. c. Click Save.

If you select CSV Filename, perform the following steps:

a. Click the Choose File icon.

NOTE: The contents of the .csv file must be in the following format, for example:

"ppdm.dell.com" "ppdm2.emc.com" "ppdm.dellemc.com"

The Explorer window appears.

b. Select the .csv file, and then click Open.

The file appears in the Application/FS Agents window.

c. Select the date until which the application agent is preapproved.

Enabling the Microsoft Application Agent for Exchange 23

d. Click Save.

If you have disabled Auto whitelist, perform the following steps:

NOTE: The Auto whitelist option is disabled by default. When Auto whitelist is enabled, all preapproved

application agents are automatically approved.

a. Select the required application agent. b. Click one of the following options:

Approve Reject Edit, then make the required changes. Remove

c. Click Save.

Next steps

Discover an Exchange application host on page 30 describes how to set the host credentials before you schedule a backup.

Support for existing Microsoft application agent backups with PowerProtect Data Manager The Microsoft application agent provides the capability to onboard existing stand-alone deployments, including their existing backups, to PowerProtect Data Manager. Existing backups are Microsoft application agent backups that you performed before integrating the Microsoft application agent with the PowerProtect Data Manager software and before adding an asset to a PowerProtect Data Manager protection policy.

NOTE:

Onboarding of Exchange backup copies to PowerProtect Data Manager is supported only from backups performed with

Microsoft application agent 4.7 and later.

You can onboard up to three previous months of existing backups.

Retention lock is not supported for discovered existing backups in PowerProtect Data Manager.

Onboarding of DD Boost-over-FC backups is not supported.

With the onboarding capability, PowerProtect Data Manager provides the following centralized features:

Visibility of both existing backups and any new self-service or PowerProtect Data Manager policy-driven backups of onboarded assets.

Automatic configuration of target protection storage based on the PowerProtect Data Manager protection policies that are used for your database.

All the other functionality that is provided for PowerProtect Data Manager protection policies.

When you create a protection policy, the PowerProtect Data Manager software creates a storage unit on the specified DD system backup host that is managed by PowerProtect Data Manager. All subsequent backups of assets in that protection policy will go to this new storage unit. This implementation overrides the storage unit information that is provided in any running backup through scripts with the storage unit information that is provided by PowerProtect Data Manager.

Supporting existing Microsoft application agent backups with PowerProtect Data Manager

Learn how to support the existing Microsoft application agent backups.

Steps

1. Run the backup discovery tool, AgentBackupDiscovery.exe, to enable management of existing Microsoft application agent backups with PowerProtect Data Manager.

24 Enabling the Microsoft Application Agent for Exchange

Using the backup discovery tool for PowerProtect Data Manager management of existing backups on page 25 provides information.

NOTE: This step enables the discovery of old backup copies that the Microsoft application agent created during self-

service backups with stand-alone deployments.

2. Register and approve the Microsoft application agent in PowerProtect Data Manager.

Manage the Microsoft application agent for Exchange on page 23 provides information.

After a few minutes of approving the Exchange host, older backup copies are discovered. Depending on the number of backups, the discovery and subsequent visibility of the backups in PowerProtect Data Manager can take some time. The retention time for the discovered backup is the same as the expiration time when the backup was performed.

3. Discover the Exchange application host.

Discover an Exchange application host on page 30 provides information.

4. Create a protection policy to protect the Exchange host. For onboarding assets, only a subset of databases can be onboarded. It is not mandatory for all the databases on the host to be onboarded.

Add a protection policy for Exchange database protection on page 30 provides information.

The first backup after onboarding must be a full backup:

The first centralized backup is automatically promoted to a full backup. The first self-service backup is automatically performed as a full backup.

NOTE: You cannot perform a backup to a secondary DD system device. You can restore only from a secondary DD

system device.

5. Perform a self-service backup of the Microsoft Exchange databases. Onboarded assets can be part of either a centralized or self-service protection policy.

Performing self-service backups of Microsoft Exchange databases on page 42 provides information.

Using the backup discovery tool for PowerProtect Data Manager management of existing backups

To enable the PowerProtect Data Manager management of existing backups after you have upgraded from a previous version of Microsoft application agent or onboarded the current version, you must run the backup discovery tool, AgentBackupDiscovery.exe. Existing backups are Microsoft application agent backups that you performed before integrating the Microsoft application agent with the PowerProtect Data Manager software.

At the end of an upgrade of the Microsoft application agent with the installer, the wizard displays a message about running the AgentBackupDiscovery.exe tool to discover existing backups and manage them in PowerProtect Data Manager software.

CAUTION:

Onboarding of Exchange backup copies to PowerProtect Data Manager is supported only from backups

performed with Microsoft application agent 4.7 and later.

Retention lock is not supported for discovered existing backups in PowerProtect Data Manager.

You cannot use the backup discovery tool to discover existing DD Boost-over-FC backups.

If you delete an Exchange database before onboarding but the database backup copies exist on the Data Domain

system, then after onboarding, PowerProtect Data Manager will not manage those backup copies.

After you run the backup discovery tool, you can continue to use the existing backup scripts to perform the

Microsoft application agent backups. Ensure that all the databases backed up with a particular script are added

to a single protection policy.

To discover the existing backups by using the backup discovery tool, perform the following steps.

1. Ensure that you have added in PowerProtect Data Manager the Data Domain that was used for the existing backups prior to the PowerProtect Data Manager integration. Ensure that you have discovered the storage unit that was used for the backups.

Enabling the Microsoft Application Agent for Exchange 25

2. In the Microsoft application agent installation directory, C:\Program Files\DPSAPPS\MSAPPAGENT\bin, run AgentBackupDiscovery.exe as the administrator.

The Discovery of existing backups dialog box appears.

NOTE: If the program does not start but displays the following message, an ongoing backup discovery process is

running, as invoked by the PowerProtect Data Manager:

Backup discovery is in progress. Please wait for it to complete.

When the discovery process is complete, you can run the backup discovery tool.

3. In the Data Domain system list in the dialog box, select the appropriate Data Domain IP address or hostname, storage unit, and username for the existing backups that you want the PowerProtect Data Manager software to discover.

NOTE: Select only one storage unit at a time. After discovery is complete for the storage unit, you can run the backup

discovery tool again to discover the backups of another storage unit.

4. In the Client hostname field, you can change the client hostname from the default local hostname as needed.

To enable the backup discovery when the host is part of a DAG, specify the Windows cluster name.

5. In the Backup discovery time period field, select the number of months for the time period, as the time in the past when the backups were performed. You can select 1 month, 2 months, or 3 months for the time period.

6. In the Application field, select Exchange as the application. 7. After you have specified the required field values, click Generate.

When the PowerProtect Data Manager software completes the generation of the backup metadata or breadcrumbs, the following message appears in the dialog box. Depending on the number of old backups, the generation of breadcrumbs can take some time:

Breadcrumbs generated successfully.

The retention time for the discovered backup will be same as the expiration time set when the backup was taken.

Troubleshooting Microsoft application agent discoveries on Windows 2008 and Application Direct When you perform a Microsoft application agent discovery on Windows 2008 on PowerProtect Data Manager and Application Direct versions 4.5 and 4.6, the PowerProtect Data Manager agent uses the wmic.exe command to discover the installed programs. The default PowerProtect Data Manager agent installation on Windows 2008 R2 produces an error in the ecdmagent log, and discovery fails.

In Some Windows 2008 environments, the wmic.exe command does not work properly when you run it from the local user or local system account, and it causes the following error: Failed to run wmic: ERROR: error running command `wmic.exe product where name like 'DDBEA and ProtectPoint Microsoft app agent' or name like 'Microsoft Application agent' get Name, Version /format:csv`: exit status 44210 To avoid the error and ensure that Microsoft application agent discoveries on Windows 2008 and Application Direct succeed, run the wmic.exe command as domain administrator instead of local administrator.

26 Enabling the Microsoft Application Agent for Exchange

Managing Storage, Assets, and Protection

Topics:

Add protection storage Enable an asset source Discover an Exchange application host Add a protection policy for Exchange database protection Edit the retention period for backup copies Delete backup copies Manage the PowerProtect agent service Manage the cloud tier operations with PowerProtect Data Manager

Add protection storage

About this task

The PowerProtect Data Manager UI enables users with administrator credentials to add the following storage types:

DD Management Center (DDMC) External DD system

NOTE:

Adding the DDMC is not required for the Storage Direct agent.

The most up-to-date software compatibility information for PowerProtect Data Manager is provided in the eLab

Navigator.

PowerProtect Data Manager does not support DD systems with the High Availability (HA) feature enabled.

When a DD Management Center is added, PowerProtect Data Manager discovers all the supported DD systems that are managed by the DD Management Center. The PowerProtect Data Manager UI displays the discovered DD systems on the Protection Storage tab of the Infrastructure > Storage window. The DD systems that are managed by the DD Management Center are not displayed until discovery is complete. It might take a few minutes for the DD systems to appear in the Storage window.

For each DD system, the DD Management Center that manages the DD system is indicated in the Managed By column in the table.

If a DD system is added directly to PowerProtect Data Manager, the name that was provided for the DD system when it was added to the PowerProtect Data Manager system is displayed in the Managed By column.

NOTE: Data Domain is now PowerProtect DD. References to Data Domain or DD systems in this documentation, in the UI,

and elsewhere in the product include PowerProtect DD systems and older Data Domain systems. In many cases the UI has

not yet been updated to reflect this change.

Steps

1. Select Infrastructure > Storage.

The Storage window appears.

2. In the Protection Storage tab, click Add.

3. In the Add Storage dialog box, select a storage system (DD System, DD Management Center).

NOTE: If using the Storage Direct agent to move snapshot backups from a VMAX storage array to a DD system, you do

not need to add a DD Management Center.

4. Specify the storage system attributes:

3

Managing Storage, Assets, and Protection 27

a. In the Name field, specify a storage name. b. In the Address field, specify the hostname, fully qualified domain name (FQDN), or the IP address. c. In the Port field, specify the port for SSL communication. Default is 3009.

5. Under Host Credentials click Add, if you have already configured DD credentials that are common across DD systems, select an existing password. Alternatively, you can add new credentials, and then click Save .

6. If a trusted certificate does not exist on the storage system, a dialog box appears requesting certificate approval. Click Verify to review the certificate, and then click Accept.

7. Click Save to exit the Add Storage dialog and initiate the discovery of the storage system.

A dialog box appears to indicate that the request to add storage has been initiated.

8. In the Storage window, click Discover to refresh the window with any newly discovered storage systems. When a discovery completes successfully, the Status column updates to OK.

9. To modify a storage system location, complete the following steps:

A storage system location is a label that is applied to a storage system. If you want to store your copies in a specific location, the label helps you select the correct storage system during policy creation.

a. In the Storage window, select the storage system from the table. b. Click Set Location.

The Set Location window appears. c. Click Add in the Location list.

The Add Location window appears. d. In the Name field, type a location name for the asset, and click Save.

10. To manage MTrees in the Storage window, select the storage system from the table and click View storage units.

NOTE: For information about MTrees, see the DD Operating System Administration Guide.

Results

PowerProtect Data Manager displays External DD systems only in the Storage window Name column. PowerProtect Data Manager displays DD Management Center storage types in the Managed By column.

Troubleshooting protection policy for DD storage unit

When adding a protection policy in PowerProtect Data Manager, creation of a storage unit on the selected DD system fails if you reach the maximum MTree and Users count on the DD system. PowerProtect Data Manager enables you to finish adding the protection policy without the storage unit. However, if you subsequently run a backup of this protection policy, the backup process is suspended indefinitely with no error message.

To continue backup operations on this device, you must perform a cleanup on the DD system.

Viewing the DD Boost storage unit password

PowerProtect Data Manager provides a script to retrieve the password of a DD Boost unit that is configured as a backup target.

Prerequisites

This process requires the name of the DD MTree where the DD Boost storage unit resides.

Steps

1. SSH to the PowerProtect Data Manager appliance as the admin user.

2. Navigate to the /usr/local/brs/puppet/scripts directory.

3. Obtain the DD Boost storage unit password by typing the following command:

./get_dd_mtree_credential.py PLC-PROTECTION-1551667983302

28 Managing Storage, Assets, and Protection

Enable an asset source An asset source, such as a vCenter Server, must be enabled in PowerProtect Data Manager before you can add and register the asset source for the protection of assets.

About this task

There are some circumstances where enabling an asset source is not required, such as the following:

For application agents and other agents such as File System and Storage Direct, an asset source is enabled automatically when you register and approve the agent host. For example, if you have not enabled an Oracle asset source but have registered the application host though the API or the PowerProtect Data Manager UI, PowerProtect Data Manager automatically enables the Oracle asset source.

When you upgrade to PowerProtect Data Manager 19.6 from an earlier release, any asset sources that were previously enabled appear in the PowerProtect Data Manager UI. On a new installation, however, no asset sources are enabled by default.

Steps

1. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then click + to reveal the New Asset Source tab.

2. In the pane for the asset source that you want to add, click Enable Source. The Asset Sources window updates to display a tab for the new asset source.

Results

You can now add or approve the asset source for use in PowerProtect Data Manager. For a vCenter Server, Kubernetes cluster, or SMIS Server, select the appropriate tab in this window and click Add. For an application agent, go to Infrastructure > Application Agents and click Add or Approve as required.

Disable an asset source

If you enabled an asset source that you no longer require, and the host has not been registered in PowerProtect Data Manager, perform the following steps to disable the asset source.

About this task

NOTE: An asset source cannot be disabled when one or more sources are still registered or there are backup copies of the

source assets. For example, if you registered a vCenter Server and created policy backups for the vCenter virtual machines,

then you cannot disable the vCenter asset source. But if you register a vCenter Server and then delete the vCenter without

creating any backups, you can disable the asset source.

Steps

1. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources, and then select the tab of the asset source that you want to disable. If no host registration is detected, a red Disable button appears.

2. Click Disable.

Results

PowerProtect Data Manager removes the tab for this asset source.

Managing Storage, Assets, and Protection 29

Discover an Exchange application host After you register an application host with PowerProtect Data Manager, the host appears in the Asset Sources window. Then you can select the host and perform discovery. For application hosts, discovery is required if you want to schedule a backup. Assets must also be discovered for the centralized copy management of self-service backups.

About this task

Perform the following steps to discover an Exchange application host as an asset source in the PowerProtect Data Manager UI.

Steps

1. Select Infrastructure > Asset Sources.

The Asset Sources window appears.

2. Select the App/File System Host tab.

3. On the App/File System Host tab, select the application host and click Discover to perform discovery.

The Discover dialog appears with an option to set the discovery schedule.

4. From the Discovery Schedule list, select the time of day to initiate the discovery, or select Manual to disable scheduled discovery. You can also select the Discover Now check box to perform the discovery upon completion of this procedure.

NOTE: On the App/File System Host tab, you can click Discover at any time if any additions or other changes to your

Asset Sources have taken place outside of the PowerProtect Data Manager environment. Asset discovery is also

initiated by default after registration of the host to PowerProtect Data Manager and at hourly intervals. Discovery time

is based on networking bandwidth. Each time you initiate a discovery process, the resources that are discovered and

those that are handling the discovery impact the system performance.

5. Click Save.

Results

If the application host is properly configured and discovery is successful, the database assets can now be added to a PowerProtect Data Manager protection policy.

Add a protection policy for Exchange database protection Use the PowerProtect Data Manager UI to add a protection policy for Exchange database protection.

Prerequisites

If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The PowerProtect Data Manager Administration and User Guide provides more information.

Steps

1. Select Protection > Protection Policies.

The Protection Policies window appears.

2. Click Add.

The Add Policy wizard appears.

3. On the Type page, specify the new protection policies group fields. For example, if you are creating a protection policy for daily backups in the Exchange production environment:

a. In the Name field, specify the name of the protection policy. For example, specify Exchange Prod Databases.

NOTE: The name that you specify becomes part of the Data Domain MTree entry.

b. In the Description field, specify a short description of the protection policy. For example, specify Exchange Prod Daily Backups.

30 Managing Storage, Assets, and Protection

c. In theType field, select Microsoft Exchange Database. d. Click Next.

The Purpose page appears.

4. On the Purpose page, select one of the following options to indicate the purpose of the new protection policy group, and then click Next:

Centralized ProtectionThe backup is triggered according to the schedule. PowerProtect Data Manager manages the complete protection life cycle.

Self-ServiceThe backup is triggered manually from the Exchange Server. PowerProtect Data Manager manages the complete protection life cycle.

ExclusionAny assets that are added to this type of protection policies group are excluded from the data protection operation.

5. On the Assets page, select the unprotected assets that you want to add to the backup of this protection policy group. The window enables you to filter by asset name to locate the required assets.

NOTE: An Exchange database asset can be protected by only one protection policy at a time.

6. Click Next.

If you selected Exclusion on the Purpose page, the Summary page appears. Skip to the final two steps.

If you selected Centralized Protection or Self-Service Protection, the Schedule page appears.

7. Click + Backup. The Add Primary Backup dialog box appears.

8. Specify the backup schedule fields:

For centralized protection:

a. In the Recurrence field, select the interval at which the backup job runs within the window that you specify.

Recurrence relates to Start Time and End Time fields.

When you select Hourly, Daily, Weekly, and Monthly recurrence, you are selecting the interval at which the backup job runs within the window that you specify.

b. In the Create Copy field, specify how often to create a synthetic full backup. A synthetic full backs up only the data that has changed since the last backup, to create a new, full backup.

c. In the Create Full field, specify the interval in hours to create a full backup.

The interval should be between 1 and 12 hours.

d. In the Keep For field, specify the retention period for the backup.

You can extend the retention period for the latest primary backup copy by adding a promotion backup. For example, your regular schedule for daily backups can use a retention period of 30 days, but you can apply promotion backups to keep the full backups taken on Mondays for 10 weeks. Step 9 on page 32 provides instructions.

NOTE: For database backups, PowerProtect Data Manager chains the dependent backups together. For

example, the synthetic full or transaction log backups are chained to their base full backup. The backups do not

expire until the last backup in the chain expires. This ensures that all synthetic full and transaction log backups

are recoverable until they have all expired.

e. In the Start Time field, specify the time when new backups are initiated in this policy. f. In the End Time field, specify the time after which no new backups are initiated in this policy. It does not mean that

any policy that is running is stopped at this time. g. Click OK.

NOTE:

When a new asset is added to a protection policy during a scheduled backup window, the backup starts right

away. However, if an asset is added to a protection policy outside of the scheduled backup window, the backup

does not start until the next time that backups are configured to run.

If a new asset is added to a protection policy that has a weekly or monthly backup schedule and the current time

is within the scheduled Start Time and End Time, the backup runs right away, regardless of the date. If the

current time is not within the scheduled Start Time and End Time, the backup does not start until the next time

that backups are configured to run.

Managing Storage, Assets, and Protection 31

The Schedule page updates with the newly added backup schedule.

For self-service protection:

a. In the Keep For field, specify the retention period for the backup. b. Click OK.

After you complete a backup schedule, you can change any schedule details by selecting the check box next to the added schedule and clicking Edit.

9. To extend the retention period for the latest primary backup copy, add a promotion backup:

a. Select the checkbox next to the added schedule and click + Backup. b. In the Add Promotion Backup dialog box, specify a weekly or monthly recurrence for the promotion backup schedule, a

retention period for the backup, and then click OK.

10. To replicate these backups to a remote DD system:

a. Select the checkbox next to the primary backup schedule and click Replicate.

NOTE: You cannot replicate a promotion backup. When you select a promotion backup schedule, the Replicate

button is disabled.

b. Complete the schedule details in the Add Primary Replication dialog box, and then click OK.

NOTE: To enable replication, ensure that you add a remote DD system as the replication location.

11. Optionally, to add a cloud stage for the purpose of moving backups from DD storage to the cloud tier, select the check box next to the primary, replication, or promotion schedule, and then select Cloud Tier. Add a cloud tier schedule to a protection policy on page 39 provides more information.

NOTE: In order to move a backup or replica to the cloud tier, schedules must have a weekly or monthly recurrence and

a retention time of 14 days or more. Also, discovery of a DD system configured with a cloud unit is required.

12. Click Set Storage Quotas to set storage space restrictions for a Data Domain MTree or storage unit to prevent the consumption of excess space. There are two kinds of quota limits, hard limits and soft limits. You can set either a soft or hard limit or both a soft and hard limit. Both values must be integers, and the soft value must be less than the hard value.

NOTE: When you set a soft limit and the limit is reached, an alert is generated but data can still be written to the Data

Domain. When you set a hard limit and the limit is reached, data cannot be written to the MTree. Therefore, all data

protection operations fail until data is deleted from the MTree. The Data Domain Operating System Administration Guide

provides more information about MTree quota configuration.

a. Capacity QuotaSpecifies the total size of pre-compression data written to the Data Domain. b. Stream QuotaSpecifies the number of concurrent streams allowed on the system during data protection operations.

Setting a Stream Quota limit can help ensure that system performance is not impacted negatively if a data protection operation consumes too many system resources.

13. Select the Retention Lock check box to enable retention locking for these backups on the selected system.

14. Click Next. The Options page appears.

15. On the Options page, select the additional options that are required for the policy:

Data Consistency CheckSelect one of the following options to enable the consistency checking of the Exchange database and logs:

NoneNo consistency check is performed. AllBoth the database and logs are checked for consistency. DatabaseOnly the database is checked for consistency.

NOTE: A consistency check of only the database does not ensure the complete consistency of the backup, but

the check takes less time to perform.

LogsOnly the logs are checked for consistency.

The Exchange consistency check occurs at backup time and verifies that the database and its transaction logs do not contain errors, such as on-disk data corruption. The consistency check improves the Exchange backup quality and performance, validating that the backup is viable and will not cause issues when restored.

NOTE: Consistency checking can affect the backup performance and increase the backup window.

32 Managing Storage, Assets, and Protection

TroubleshootingSelect this option to enable the debug logs for troubleshooting purposes.

16. Click Next. The Summary page appears.

17. Review the protection policy group configuration details. You can click Edit next to any completed window's details to change any information. When completed, click Finish. An informational message appears to confirm that PowerProtect Data Manager has saved the protection policy. When a new protection policy is created, PowerProtect Data Manager performs the first full backup and subsequent backups according to the specified schedule.

18. Click OK to exit the window, or click Go to Jobs to open the Jobs window to monitor the backup of the new protection policy group.

Edit the retention period for backup copies You can edit the retention period of one or more backup copies to extend or shorten the amount of time that backups are retained.

About this task

You can edit the retention period for all asset types and backup types.

Steps

1. Select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to edit the retention period. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more backup copies from the table, and click Edit Retention.

6. Select one of the following options:

To select a calendar date as the expiration date for backups, select Retention Date. To define a fixed retention period in days, weeks, months, or years after the backup is performed, select Retention

Value. For example, you can specify that backups expire after 6 months.

NOTE: When you edit the retention period for copies that are retention locked, you can only extend the retention

period.

7. When satisfied with the changes, click Save. The asset is displayed in the list with the changes. The Retention column displays both the original and new retention periods, and indicates whether the retention period has been extended or shortened.

Delete backup copies In addition to deleting backups upon expiration of the retention period, PowerProtect Data Manager enables you to manually delete backup copies from the DD system.

About this task

If you no longer require a backup copy and the retention lock is not enabled, you can delete backup copies prior to their expiration date.

Steps

1. Select Infrastructure > Assets.

2. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

Managing Storage, Assets, and Protection 33

3. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

4. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

5. Select one or more copies from the table that you want to delete from the DD system, and then click Delete.

A preview window opens and displays the selected backup copies.

6. For all asset types, you can choose to keep the latest backup copies or delete them. By default, PowerProtect Data Manager keeps the latest backup copies. To delete the latest backup copies, clear the checkbox next to Include latest copies.

7. To delete the backup copies, in the preview window, click Delete.

NOTE: The delete operation may take a few minutes and cannot be undone.

An informational dialog box opens to confirm the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

When the job completes, the task summary provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC.

An audit log is also generated and provides details of each deleted backup copy, including the time that each copy was created, the backup level, and the retention time. The time of copy creation and the retention time is shown in UTC. Go to Alerts > Audit Logs to view the audit log.

8. Verify that the copies are deleted successfully from the DD system. If the deletion is successful, the deleted copies no longer appear in the table.

Retry a failed backup copy deletion

If a backup copy is not deleted successfully, you can manually retry the operation.

Steps

1. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

2. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

3. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

4. Select one or more backup copies with the Deletion Failed status from the table, and then click Delete.

You can also filter and sort the list of backup copies by status in the Copy Status column.

The system displays a warning to confirm you want to delete the selected backup copies.

5. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

6. Verify that the copies are successfully deleted from the DD system. If the deletion is successful, the deleted copies no longer appear in the table.

Export data for deleted backup copies

This option enables you to export results of deleted backup copies to a CSV file so that you can download an Excel file of the data.

Steps

1. From the Assets window, select the tab for the asset type for which you want to export results of deleted backup copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

2. Select one or more protected assets from the table and click Export Deleted Copies.

If you do not select an asset, PowerProtect Data Manager exports the data for deleted backup copies for all assets for the specific asset type.

3. Specify the following fields for the export:

34 Managing Storage, Assets, and Protection

a. Time Range

The default is Last 24 Hours.

b. Copy Status

In order to export data for deleted backup copies, the backup copies must be in one of the following states:

Deleted Deleting Deletion Failed Deletion Failed (Agent Catalog)

NOTE: You cannot export data for backup copies that are in an Available state.

4. Click Download. If applicable, the navigation window appears for you to select the location to save the CSV file.

5. Save the CSV file in the desired location and click Save.

Remove backup copies from the PowerProtect Data Manager database

This option enables you to delete the backup copy records from the PowerProtect Data Manager database, but keep the backup copies in the DD system.

About this task

For backup copies that could not be deleted from the DD system, you can remove the backup copies from the PowerProtect Data Manager database. Removing the backup copies from PowerProtect Data Manager does not delete the copies in the DD system.

Steps

1. From the Assets window, select the tab for the asset type for which you want to delete copies. If a policy has been assigned, the table lists the assets that have been discovered, along with the associated protection policy.

2. Select a protected asset from the table, and then click View Copies. The Copy Locations pane identifies where the backups are stored.

3. In the left pane, click the storage icon to the right of the icon for the asset, for example, DD. The table in the right pane lists the backup copies.

4. Select one or more backup copies with the Deletion Failed or Deletion Failed (Agent Catalog) status from the table, and then click Remove from PowerProtect.

For backup copies with the Deletion Failed (Agent Catalog) status, click Remove from PowerProtect to remove the information from PowerProtect Data Manager for any backup copies that were successfully deleted from the DD system but for which the agent catalog was not deleted from the agent host.

The system displays a warning to confirm you want to delete the selected backup copies.

5. Click OK. An informational dialog box opens to confirm that the copies are being deleted. To monitor the progress of the operation, click Go to Jobs. To view the list of backup copies and their status, click OK.

6. Verify that the copies are deleted from the PowerProtect Data Manager database. If the deletion is successful, the deleted copies no longer appear in the table. The backup copies remain in the DD system.

Manage the PowerProtect agent service The PowerProtect agent service provides important functionality for the application agent operations with the PowerProtect Data Manager.

Review the following topics to ensure that you enable and manage the PowerProtect agent service functionality as required for application agent operations.

Managing Storage, Assets, and Protection 35

About the PowerProtect agent service

The PowerProtect agent service is a REST API based service that is installed by the application agent on the application host. The agent service provides services and APIs for discovery, protection, restore, instant access, and other related operations. The PowerProtect Data Manager uses the agent service to provide integrated data protection for the application assets.

This section uses to represent the PowerProtect agent service installation directory. By default, the agent service installation location is C:\Program Files\DPSAPPS\AgentService on Windows and /opt/dpsapps/agentsvc on Linux. All files that are referenced in this section are the relative paths to the agent service installation location.

The PowerProtect agent service performs the following operations:

Addon detectionAn addon integrates the application agent into the agent service. The agent service automatically detects the addons on the system for each application asset type and notifies the PowerProtect Data Manager. While multiple addons can operate with different asset types, only one agent service runs on the application host. Specific asset types can coexist on the same application host.

DiscoveryThe agent service discovers both stand-alone and clustered database servers (application systems), databases and file systems (assets), and their backup copies on the application agent host. After the initial discovery, when the agent service discovers any new application systems, assets, or copies, the agent service notifies the PowerProtect Data Manager.

Self-service configurationThe agent service can configure the application agent for self-service operations by using information that is provided by the PowerProtect Data Manager. When you add an asset to a protection policy for self- service or centralized protection, or modify the protection policy, including changing the DD Boost credentials, the PowerProtect Data Manager automatically pushes the protection configuration to the agents.

Centralized backupsThe agent service performs the centralized backups as requested by the PowerProtect Data Manager.

Centralized restoresThe agent service performs the centralized restores as requested by the PowerProtect Data Manager.

NOTE: In the current release, the centralized restores are only available for the File System agent and Storage Direct

agent.

Backup deletion and catalog cleanupThe PowerProtect Data Manager deletes the backup files directly from the protection storage when a backup expires or an explicit delete request is received and no dependent (incremental or log) backups exist.

NOTE: Deletion of any backup copies manually or through the command line is not recommended. PowerProtect Data

Manager deletes all the expired copies as needed.

The agent service is started during the agent installation by the installer. The agent service runs in the background as a service and you do not interact with it directly.

The config.yml file contains the configuration information for the agent service, including several parameter settings that you can change within the file. The config.yml file is located in the directory.

The agent service periodically starts subprocesses to perform the discovery jobs. You can see the type and frequency of these jobs in the jobs: section of the config.yml file. The job interval unit is minutes.

The agent service maintains a datastore in the /dbs/v1 directory, which contains information about the application system, assets, and backups discovered on the system. The size of the datastore files depends on the number of applications and copies on the host. The agent service periodically creates a backup of its datastore in the /dbs/v1/backups directory, as used to recover the datastore if this datastore is lost.

NOTE: The size of each datastore backup is the same as the datastore itself. By default, a backup is created every hour. To

save space on the file system, you can reduce this datastore backup frequency for large datastores. By default, the

datastore backup is retained for one week. You can change the datastore backup frequency, retention period, and backup

location in the config.yml file.

Start, stop, or obtain the status of the PowerProtect agent service

The PowerProtect agent service is started during the agent installation by the installer. If needed, you can use the appropriate procedure to start, stop, or obtain the status of the agent service.

On Windows, you can start, stop, or obtain the status of the PowerProtect agent service from the Services Manager, similar to other Windows services. The name of the service in the Services Manager is PowerProtect Agent Service.

36 Managing Storage, Assets, and Protection

Troubleshoot the PowerProtect agent service installation

The PowerProtect agent service installation might fail with the following error message:

Service 'PowerProtect Agent Service' (AgentService) could not be installed. Verify that you have sufficient privileges to install system services.

Possible causes of the installation failure are as follows:

The installation was attempted on a passive node of a Failover Cluster Instance (FCI). The installation was canceled and a rollback left some stale entries of PowerProtect agent services.

As a workaround, clean up the PowerProtect agent service entries, and retry the installation.

Troubleshoot the PowerProtect agent service operations

To troubleshoot the agent service operations, you can check the agent service log file OpAgentSvc- .log, which is created in \logs on Windows and /logs on Linux. To modify the log level and retention of temporary files, you can modify specific parameter settings in the config.yml file.

About this task

To modify the log level and retention of temporary files, you can perform the following steps.

Steps

1. Stop the agent service by using the appropriate procedure from the preceding topic.

2. Open the config.yml file in an editor.

3. Modify the log-level settings in the following parameters, as required:

NOTE: These parameters are listed in order of decreasing number of messages in the debug information output. The

default log-level is INFO.

DEBUG INFO WARNING ERROR CRITICAL

4. To retain the temporary files, set the keepTempFiles parameter to True in the config.yml file.

NOTE: The agent service and application agent communicate through the temporary files, which are typically deleted

after use but can be useful for troubleshooting purposes. Do not leave the keepTempFiles parameter set to True

permanently, or the temporary files can use excessive space on the file system.

5. Start the agent service by using the appropriate procedure from the preceding topic.

Register the PowerProtect agent service to a different server address on Windows

The PowerProtect agent service is registered to a particular PowerProtect Data Manager server during the agent installation by the installer. If needed, you can register the agent service to a different PowerProtect Data Manager server address. If there are multiple agents installed on a host, all agents will be re-registered to the new PowerProtect server.

The agent service can only be registered to a single PowerProtect Data Manager server.

On Windows, perform the following steps to register the agent service to a different server address.

1. To unregister from the current PowerProtect Data Manager server, go to the C:\Program Files\DPSAPPS \AgentService directory and run unregister.bat.

2. In the dbs\v1 directory, rename the copies.db file to copies-backup.db.

Managing Storage, Assets, and Protection 37

3. To register the agent service to the different server address, run register.bat and provide the new PowerProtect Data Manager server IP address or hostname.

4. Verify the agent registration status:

a. In the PowerProtect Data Manager UI, select Infrastructure > Application Agents.

b. In the Application Agents window, select the entry that contains the agent hostname and ensure that the status is Registered.

5. To perform asset discovery for the agent:

a. In the PowerProtect Data Manager UI, select Infrastructure > Asset Sources.

The Asset Sources window appears.

b. Select the App/File System Host tab. c. Select the agent hostname and click Discover. At the confirmation prompt, click Yes.

When you select Infrastructure > Assets, the Assets window displays the discovered assets.

Recovering the PowerProtect agent service from a disaster

You can perform self-service restores of application assets by using a file system or application agent, regardless of the state of the agent service or PowerProtect Data Manager. The information in the this section describes how to bring the agent service to an operational state to continue if a disaster occurs and the agent service datastore is lost.

The agent service periodically creates a backup of its datastore in the /dbs/v1/backups repository. If all these backups are lost, the agent service can still start. The agent service discovers all the application systems, assets, and backup copies on the system again, and notifies PowerProtect Data Manager. Depending on when the failure occurred, the agent service might not be able to find older backup copies for some asset types. As a result, the centralized deletion operations might fail when cleaning up the database vendor catalog or removing older backups that are taken before the asset is added to PowerProtect Data Manager.

By default, the agent service backs up consistent copies of its datastore files to the local disk every hour and keeps the copies for 7 days. Each time the agent service backs up the contents of the datastore, it creates a subdirectory under the /dbs/v1/backups repository. The subdirectories are named after the time the operation occurred, in the format YYYY-MM-DD_HH-MM-SS_epochTime.

By default, the datastore repository is on the local disk. To ensure that the agent service datastore and its local backups are not lost, it is recommended that you back up the datastore through file system backups. You can also change the datastore backup location to a different location that is not local to the system. To change the datastore backup location, update the values in the config.yml file.

Restore the PowerProtect Data Manager agent service datastore

Prerequisites

NOTE: Ensure that the agent service is powered off. Do not start the agent service until disaster recovery is complete.

About this task

You can restore the datastore from the datastore backup repository. If the repository is no longer on the local disk, restore the datastore from file system backups first.

To restore the datastore from a backup in the datastore backup repository, complete the following steps:

Steps

1. Move the files in the /dbs/v1 directory to a location for safe keeping.

NOTE: Do not move or delete any /dbs/v1 subdirectories.

2. Select the most recent datastore backup.

The directories in the datastore backup repository are named after the time the backup was created.

38 Managing Storage, Assets, and Protection

3. Copy the contents of the datastore backup directory to the /dbs/v1 directory. After the copy operation is complete, the /dbs/v1 directory should contain the following files:

copies.db objects.db resources.db sessions.db

4. Start the agent service.

Manage the cloud tier operations with PowerProtect Data Manager The PowerProtect Data Manager cloud tier feature works in tandem with the Data Domain Cloud Tier feature to move PowerProtect Data Manager backups from Data Domain systems to the cloud. This provides long-term storage of PowerProtect Data Manager backups by seamlessly and securely tiering data to the cloud.

From the PowerProtect Data Manager UI, you configure cloud tier to move PowerProtect Data Manager backups from Data Domain to the cloud, and you can perform seamless recovery of these backups.

Data Domain cloud storage units must be pre-configured on the Data Domain system before they are configured for cloud tier in the PowerProtect Data Manager UI. The Data Domain Operating System Administration Guide provides more information.

Add a cloud tier schedule to a protection policy

You can add a cloud tier schedule to a protection policy for Exchange centralized and self-service backups to cloud tier.

Prerequisites

Ensure that a Data Domain system is set up for cloud tiering.

About this task

Both Exchange centralized and self-service protection policies support cloud tiering. You can create the cloud tier schedule from both primary and replication stages. Schedules must have a minimum weekly recurrence and a retention time of 14 days or greater.

Steps

1. Log in to PowerProtect Data Manager with administrator credentials.

2. Select Protection > Protection Policies > Add.

3. On the Type page, enter a name and description, select Exchange as the type of system to back up, and click Next.

4. On the Purpose page, select from the available options to indicate the purpose of the new protection policy, and then click Next.

5. On the Assets page, select the assets to be protected with this policy, and then click Next.

6. On the Schedule page, select + Backup.

7. On the Add Primary page, set the following parameters, and then click OK:

RecurrenceSelect Weekly or Monthly. Keep forCloud Tier backup requires a minimum of 2 weeks. Optionally, change the Start Time or End Time or both.

8. Select the Primary protection policy that you created, and then select Cloud Tier.

9. For Self -Service Protection Policy:

Select a primary backup to create a promotion backup. Keep forCloud Tier backup requires a minimum of 2 weeks.

10. In the Add Promotion Backup dialog box, set the following parameters, and then click OK:

Managing Storage, Assets, and Protection 39

RecurrenceSelect Weekly or Monthly. Create Full (Level 0)Add the option as per the recurrence. Keep forCloud Tier backup requires a minimum of 2 weeks.

11. Select the Promotion Backup policy, and then select Cloud Tier.

12. In the Add Cloud Tier dialog box, set the following parameters, and then click OK:

Select the appropriate unit from the Cloud Target list. For Tier After, set a time of at least 2 weeks.

The cloud tier protection policy is created.

13. Click Next, verify the information, and then click Finish. A new job is created, which you can view under the Jobs tab after the job completes.

Tier the PowerProtect Data Manager backups from Data Domain to the cloud

Once you add the Exchange database assets to a protection policy that contains a cloud tier stage, you can perform tiering of these assets by using the PowerProtect Data Manager UI.

Steps

1. Log in to PowerProtect Data Manager with administrator credentials.

2. Select Infrastructure > Assets > Exchange Databases.

3. On the Type Assets page, select the asset, and then click View Copies.

4. Select the Data Domain system where the PowerProtect Data Manager backups for Exchange reside, and then select Full protection copy which is older than 2 weeks.

5. Click Tier to tier the backups.

A new job is created, which you can view under the Jobs tab after the job completes. When you monitor the cloud tier progress of backup copies for the asset job, the status remains in the running state until the data movement occurs from the Data Domain system.

6. Log in to the Data Domain system, and obtain the storage unit details by running the command data-movement policy show. For example:

# data-movement policy show

Mtree Target(Tier/Unit Name) Policy Value ----------------------------------------- ---------------------- ----------- ------- /data/col1/rman137-blrv136g140-840dd Cloud/ecs-unit app-managed enabled /data/col1/rman134-copy-blrv136g138-61900 Cloud/ecs-unit app-managed enabled /data/col1/rman-11-blrv136h010-7014f Cloud/ecs-unit app-managed enabled

7. Run the data-movement start mtrees command for the particular MTree. For example:

# data-movement start mtrees /data/col1/rman137-blrv136g140-840dd

After the successful data movement to the cloud, the cloud tier monitoring job completes. After some time, on the Assets > View Copies page, the Location field of the protection backups changes to Cloud.

The Data Domain Operating System Administration Guide provides more details about cloud tier data movement.

40 Managing Storage, Assets, and Protection

Restore the cloud tier backups to Data Domain

The restore operations of backups that have been tiered to the cloud are identical to normal restore operations.

The PowerProtect Data Manager software recalls a copy of the backup from the cloud to the local (active) tier of the Data Domain system, and then performs a restore of the backup from the active tier to the client. The status appears as Cloud. After the restore, the backup copy is removed from the cloud tier, and is stored on the active tier of the Data Domain system for a minimum of 14 days, after which the backup may be returned to the cloud, depending on the protection policy.

Recall and re-tier the cloud tier backup

You can restore directly from a cloud tier backup. You can also manually recall the cloud tier backup and then restore from the local copy.

The direct restore from the cloud tier backup is identical to a normal restore operation. PowerProtect Data Manager software recalls the backup from the cloud tier to the local (active) tier and then restores the recalled backup.

NOTE:

When a backup is recalled from the cloud tier to the active tier, the copy is removed from the cloud tier.

You can restore from a cloud tier backup to either a backup stage or replication stage. For restore to a replication stage,

ensure that you select a cloud tier enabled Data Domain.

As an alternative, you can manually recall the backup from the cloud tier and restore the local copy:

1. In the PowerProtect Data Manager UI, go to Infrastructure > Assets and select the Exchange Databases tab. 2. Select the required asset, and then click View Copies. 3. Select the backup in the cloud, click Recall, and then specify how long to keep the copy on the active tier.

A job is created to recall the backup copy from the cloud tier for the selected asset. The copy moves from the cloud tier, and the status changes from Cloud to Local_Recalled.

4. Select the recalled asset, and then click Restore.

To re-tier the recalled copy, select the recalled copy and click Re-tier.

To change the retention period for the recalled copy, select the recalled copy and click Edit Recall Retention.

Managing Storage, Assets, and Protection 41

Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Topics:

Performing self-service backups of Microsoft Exchange databases Restore an Exchange application host

Performing self-service backups of Microsoft Exchange databases To enable self-service protection, when you create the Exchange protection policy, select Self-Service Protection.

When performing a self-service stand-alone backup of a DAG asset, the backups appear under the DAG asset.

Back up Exchange Server with the Windows PowerShell backup cmdlet

The Microsoft application agent supports full and incremental block-based backups. NOTE: For self-service backups, do not select assets from multiple protection policies in the same backup request. This is a

limitation of the Microsoft application agent.

Use the Backup-Exchange PowerShell cmdlet to back up Exchange Server to a Data Domain server.

To perform specific backup-related and restore-related operations, the Microsoft application agent also supports the ddbmadmin.exe command besides the msagentadmin.exe command. However, the ddbmadmin.exe command is deprecated.

All cmdlets support the standard common PowerShell parameters. https://technet.microsoft.com/en-us/library/ dd901844(v=vs.85).aspx provides the list of common parameters and their description.

NOTE: In the syntaxes, the parameters that are enclosed in square brackets, that is, [ and ] are optional.

Syntax to perform stand-alone server backups

Use the following syntax to back up a stand-alone Exchange Server:

[ ] | Backup-Exchange -BackupViaBlockBasedBackup -ClientName -DataDomainHost -DataDomainHostPath / -DataDomainUser [ ]

where:

(Optional) Specifies the configuration object that was imported using the Import- ExchangeBackupConfigFile cmdlet.

NOTE: For self-service backups with protection policies created through PowerProtect Data

Manager, run the Import-ExchangeBackupConfigFile cmdlet with the -Backup parameter

to import the backup parameters to the object.

-ClientName

4

42 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Specifies the FQDN of the Exchange Server to use for indexing the backup.

You can use the -C or -CN alias for the -ClientName parameter.

-BackupViaBlockBasedBackup

Specifies that the backup is a block-based backup.

You can use the -BBB alias for the -BackupViaBlockBasedBackup parameter.

-DataDomainHost

Specifies the Data Domain server hostname.

You can use the -S, -SH, -DDHost or -StorageHost alias for the -DataDomainHost parameter.

-DataDomainHostPath /

Specifies the full path to the Data Domain storage unit for the backup. The Data Domain user must have appropriate access rights to this path.

You can use the -Path, -DevicePath, -StoragePath, -StorageHostPath, or - DataDomainPath alias for the -DataDomainHostPath parameter.

-DataDomainUser

Specifies the Data Domain username.

Full credentials are retrieved from the lockbox to authenticate with the host. -DDUser, - StorageUser You can use the -DDUser or -StorageUser alias for the -DataDomainUser parameter.

Example stand-alone backup command to the Data Domain host ledmd035.lss.example.com

Backup-Exchange -ClientName ledmf175.msapp.com -BackupViaBlockBasedBackup - DataDomainHost ledmd035.lss.example.com -DataDomainPath /SU_DD163 -DataDomainUser DD163_user

Example stand-alone backup command with a configuration object

$serverinfo | Backup-Exchange

Syntax to perform federated backups

Use the following syntax to perform a federated backup of a database availability group:

[ ] | Backup-Exchange -BackupViaBlockBasedBackup -ClientName -DataDomainHost - DataDomainHostPath / -DataDomainUser {[- BackupActive] | [-BackupPassive] | [-BackupPreferred]} [-IncludeStandaloneDatabases] [- ServerOrderList ] [ ]

where:

(Optional) Specifies the configuration object that was imported using the Import- ExchangeBackupConfigFile cmdlet.

NOTE: For self-service backups with protection policies created through PowerProtect Data

Manager, run the Import-ExchangeBackupConfigFile cmdlet with the -Backup parameter

to import the backup parameters to the object.

-ClientName

Specifies the FQDN of the database availability group instance to use for indexing the backup.

You can use the -C or -CN alias for the -ClientName parameter.

-BackupViaBlockBasedBackup

Specifies that the backup is a block-based backup.

You can use the -BBB alias for the -BackupViaBlockBasedBackup parameter.

-DataDomainHost

Specifies the Data Domain server hostname.

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 43

You can use the -S, -SH, -DDHost or -StorageHost alias for the -DataDomainHost parameter.

-DataDomainHostPath /

Specifies the full path to the Data Domain storage unit for the backup. The Data Domain user must have appropriate access rights to this path.

You can use the -Path, -DevicePath, -StoragePath, -StorageHostPath, or - DataDomainPath alias for the -DataDomainHostPath parameter.

-DataDomainUser

Specifies the Data Domain username.

Full credentials are retrieved from the lockbox to authenticate with the host. -DDUser, - StorageUser You can use the -DDUser or -StorageUser alias for the -DataDomainUser parameter.

{-BackupActive | -BackupPassive | -BackupPreferred}

(Optional) Specifies that the database backup preference is either active (-BackupActive), passive (-BackupPassive), or preferred (-BackupPreferred).

-IncludeStandaloneDatabases

(Optional) Specifies to include stand-alone databases and public folder databases in back up.

-ServerOrderList

(Optional) Specifies the preferred Exchange Server order list if you have to select multiple copies.

Separate multiple servers with commas.

Example federated backup command

The following command backs up the database TestDB and the Mailbox Database 1250665181 in DAG1 to the Data Domain host ledmd035.lss.example.com:

Backup-Exchange -Identity TestDB,'Mailbox Database 1250665181' -ClientName DAG1.msapp.com -BackupViaBlockBasedBackup -DataDomainHost ledmd035.lss.example.com - DataDomainPath /SU_DD163 -DataDomainUser DD163_user -Preferred -ServerOrderList node1, node2 -IncludeStandaloneDatabases

Example federated backup command with a configuration object

The following command backs up the Exchange Server by using a configuration object:

$serverinfo | Backup-Exchange -Identity TestDB,'Mailbox Database 1250665181'

Optional parameters for the Backup-Exchange cmdlet

The following list describes the optional parameters for the Backup-Exchange cmdlet:

-Incremental

Specifies that the backup level is a block-based incremental backup.

If you don't specify this parameter, the backup is taken at level full.

-Retention + {d | m | w | y}

Specifies the period in which to retain a backup. After the period passes, the backup expires.

The default retention period is 30 days. The maximum retention date is 2/7/2106.

The -Retention parameter accepts a + followed by an integer followed by one of the following time indicators:

d specifies a retention period in days.

w specifies a retention period in weeks.

m specifies a retention period in months.

y specifies a retention period in years.

For example, -Retention +20d specifies to retain the backup for 20 days.

-Identity

44 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Specifies the identity of the database to back up. If you do not specify this parameter, the operation backs up all databases.

-LockBoxPath

Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use.

You can use the -LB or -LBPath alias for the -LockBoxPath parameter.

-DebugLevel <1_through_9>

Specifies the debug level for the backup. The default value is 0 (zero).

You can use the -DL or -D alias for the -DebugLevel parameter.

-DeleteDebugLogsInDays

Deletes debug log files that are older than the specified number of days. The valid range is between 1 and 32767

By default, debug logs are not deleted. Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

This parameter only deletes debug logs named in the default format and located in the logs folder at \MSAPPAGENT\logs.

-Verbose

Indicates the verbose output. In this context, the standard output stream of the Microsoft application agent appears.

You can use the -vb alias for the -Verbose parameter.

-VeryVerbose {True | False}

Increases the volume of the verbose output.

To use this parameter, you must also specify the -Verbose parameter.

The default value is False.

-ExeFileName

Specifies the full path to the application program executable msagentsv.exe.

Use this option only to diagnose. In normal operations, the cmdlet automatically locates the installed application.

-AsJob {$true | $false}

Runs the cmdlet as a background job.

The command returns an object that represents the job, and then displays the command prompt. You can continue to work in the session during the job.

You can use the -AJ or -Job alias for the -AsJob parameter.

-JobName

Specifies a friendly name for the job when you use this parameter with the -AsJob parameter. If you do not specify the -AsJob parameter, the -JobName parameter is ignored.

You can use the name to identify the job against other job cmdlets such as, Stop-Job.

-Parallelism

Specifies the parallelism setting for the backup.

Based on the number of CPUs on the host and the parallelism setting, the application agent uses the following effective parallelism value for the backup:

With 10 or more CPUs, the effective parallelism equals the minimum of the number of CPUs and the parallelism setting, minus 4. For example, with 12 CPUs and a parallelism of 16, the effective parallelism value is 8 (12 minus 4).

With 4 to 9 CPUs, the effective parallelism equals the minimum of the number of CPUs and the parallelism setting, minus 2. For example, with 8 CPUs and a parallelism of 10, the effective parallelism value is 6 (8 minus 2).

With fewer than 4 CPUs, the effective parallelism equals the number of CPUs. For example, with 2 CPUs, the effective parallelism value is 2.

If the effective parallelism value is 8, then 8 threads are created for the backup, with each thread assigned to transfer either an EDB file or the related log files. An asset transfer is complete only when an

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 45

EDB file and the related log files are both copied to the DD system. Using 8 threads, effectively 4 assets are backed up in parallel from the host.

Listing backups and save files

You can list backups and save files with the Windows PowerShell Get-ExchangeBackup cmdlet or with the msagentadmin administration list commands.

List backups with the Get-ExchangeBackup cmdlet

To list Exchange Server backups, use the Get-ExchangeBackup cmdlet.

Use the Get-ExchangeBackup PowerShell cmdlet with the following syntax to list Exchange Server backups on a Data Domain server:

[ ] | Get-ExchangeBackup -BackupViaBlockBasedBackup -DataDomainHost -DataDomainUser -DataDomainHostPath / -ClientName [ ]

where:

(Optional) Specifies the configuration object that was imported using the Import- ExchangeBackupConfigFile cmdlet.

NOTE: For PowerProtect Data Manager centralized and self-service workflows, run the Import- ExchangeBackupConfigFile cmdlet with the -Restore parameter to import the configuration

parameters to the object.

-BackupViaBlockBasedBackup

Specifies to list the block-based backups.

You can use the -BBB or -BlockBasedBackup alias for the -BackupViaBlockBasedBackup parameter.

-ClientName

Specifies the FQDN of the stand-alone Exchange Server or database availability group instance to use for listing the backup.

You can use the -C or -CN alias for the -ClientName parameter.

-DataDomainHost

Specifies the Data Domain server hostname.

You can use the -S, -SH, -DDHost or -StorageHost alias for the -DataDomainHost parameter.

-DataDomainHostPath /

Specifies the full path to the Data Domain storage unit to query for the backups. The Data Domain user must have appropriate access rights to this path.

You can use the -Path, -DevicePath, -StoragePath, -StorageHostPath, or - DataDomainPath alias for the -DataDomainHostPath parameter.

-DataDomainUser

Specifies the Data Domain username.

Full credentials are retrieved from the lockbox to authenticate with the host. -DDUser, - StorageUser You can use the -DDUser or -StorageUser alias for the -DataDomainUser parameter.

NOTE:

Depending on the number of backups and network performance, the Get-ExchangeBackup cmdlet may require

significant time to list the backups.

46 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

For the listing of backups, use the Import-ExchangeBackupConfigFile cmdlet only with the -Restore parameter.

Listing of backups with Import-ExchangeBackupConfigFIle -Backup produces invalid results.

Due to excessive property length, property values might not be completely visible and shown in the dots after a fixed

length. In this case, use the FormatEnumerationLimit and Format-List parameters to increase the property length

and to see the full property values.

Formatting the list of backups on page 51 describes multiple formatting options and filters.

The -ExcludeClientNameResolution parameter, as described in the next topic, is mandatory for IP-less DAG

restores with PowerProtect Data Manager integrated workflows (both self-service and centralized).

Optional parameters for the Get-ExchangeBackup cmdlet

The following list describes the additional parameters for the Get-ExchangeBackup cmdlet:

-ExcludeClientNameResolution

NOTE: The -ExcludeClientNameResolution parameter is mandatory for IP-less DAG

restores with PowerProtect Data Manager integrated workflows (both self-service and centralized).

Uses the client name that is provided as-is without converting it to the fully qualified domain name (FQDN).

Use this parameter to list backups taken with Microsoft application agent version 4.5 or earlier that use the short name as the client name.

You can use the -ExcludeCNResolution alias for the -ExcludeClientNameResolution parameter.

-Before

Lists only the backups that were taken on or before the given date or time.

If you do not specify a value, the value defaults to the current date and time.

-After

Lists only the backups that were taken on or after the given date or time.

-Limit

Limits the results to the specified number of backups.

-LockBoxPath

Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use.

If you do not specify this parameter, the default installation path is used, which is C:\Program Files \DPSAPPS\common\lockbox.

You can use the -LB or -LBPath alias for the -LockBoxPath parameter.

-Debug

Indicates the PowerShell debug, which enables the debug output. By default, the cmdlet pauses on every debug output.

You can use the -db alias for the -Debug parameter.

-DebugLevel <1_through_9>

Specifies the debug level. The default value is 0 (zero).

You can use the -DL or -D alias for the -DebugLevel parameter.

-Verbose

Indicates the verbose output. In this context, the standard output stream of the Microsoft application agent appears.

You can use the -vb alias for the -Verbose parameter.

-VeryVerbose {True | False}

Increases the volume of the verbose output.

To use this parameter, you must also specify the -Verbose parameter.

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 47

The default value is False.

-ExeFileName

Specifies the full path to the application program executable file, that is, msagentadmin.exe.

Use this option only to diagnose. In normal operations, the cmdlet automatically locates the installed application.

-AsJob {$true | $false}

Runs the cmdlet as a background job.

The command returns an object that represents the job, and then displays the command prompt. You can continue to work in the session during the job.

You can use the -AJ or -Job alias for the -AsJob parameter.

-JobName

Specifies a friendly name for the job when you use this parameter with the -AsJob parameter. If you do not specify the -AsJob parameter, the -JobName parameter is ignored.

You can use the name to identify the job against other job cmdlets such as, Stop-Job.

List backups and save files with the msagentadmin administration command

The Microsoft application agent supports list commands to view backups and save files.

List backups or save files using the msagentadmin administration command with the following syntax:

msagentadmin administration {--list | --listfiles} --ddhost " " --ddpath "<name_and_path_of_storage_unit>" --dduser "<DD_Boost_username>" --appID " msapp_bbb" [ ]

where:

{--list | --listfiles}

Specifies the type of list operation. You must only specify one of the following parameters:

--listfiles specifies to list save files on the storage unit.

--list specifies to list backups.

You can use the -s alias for the list parameter.

--ddhost " "

Specifies the name of the server that contains the storage unit, to which you backed up the databases.

--ddpath "/ "

Specifies the name and the path of the storage unit, to which you backed up the databases.

--dduser " "

Specifies the username of the DD Boost user.

--appID "msapp_bbb"

Specifies the application ID (namespace) to locate backups. Specify msapp_bbb for Exchange Server.

You can use the -n alias for the --appID parameter.

Reading the backup object from Windows PowerShell cmdlet output

Learn how to read the Windows PowerShell cmdlet output.

The output of the cmdlets to perform backups (Backup-Exchange), list backups (Get-ExchangeBackup), and remove backups (Remove-ExchangeBackup) is a backup object.

The Get-ExchangeBackup and Remove-ExchangeBackup cmdlets list arrays of backup objects.

48 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Output formats

Learn about the various output formats available for Windows PowerShell cmdlets for backup operations.

Table Format

The default format of the EMCExchangeBackupRestore.BackupData.ExchangeBackup object is a table, which contains the BackupDateTimeUTC, BackupID, ClientName, Successful, and BackupDatabases columns.

Consider the following example:

Table format output from the Get-ExchangeBackup cmdlet

$serverinfo | Get-ExchangeBackup -BackupViaBlockBasedBackup

BackupDate TimeUTC BackupID ClientName Successful BackupDatabases -------- -------- ---------- ---------- -------- -------- 3/14/2016 4:38:54 PM 1457973534 exchangehost.myorg.com True {TestDB, Mailbox Database 1250665181}

List format

The list format displays all attributes with the backup date and time according to the local time zone, except the static image information.

Use the Format-List parameter to enable the list format output.

Consider the following example:

Table format output from the Get-ExchangeBackup cmdlet

$serverinfo | Get-ExchangeBackup -BackupViaBlockBasedBackup | Format-List

ExchangeVersion : 2013 BackupDateTimeUTC : 10/20/2016 4:37:16 PM BackupDatabases : {183c4310-6910-4c0f-bf8c-d152560035d9, 82da2fb5-866e-4b26- a360-0f15ddfec475, 6efb90ca-279e-4e52-9784-e0861ec5c362} Level : full BackupID : msapp_bbb:1476981436 Successful : True ClientName : ledmf175.msapp.com DataDomainHost : ledmd035.lss.example.com DataDomainHostPath : /SU_DD163 RecoverPointHost : Bookmarks : {}

Wide format

The wide format displays only the BackupDateTimeUTC attribute.

Use the Format-Wide parameter to enable the wide format output.

Consider the following example:

Wide format output from the Get-ExchangeBackup cmdlet

$serverinfo | Get-ExchangeBackup -Before (Get-Date).AddDays(-5) -Limit 3 | Format-Wide

6/10/2016 12:45:18 PM 6/10/2016 12:43:36 PM 6/3/2016 3:39:53 PM

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 49

EMCExchangeBackupRestore.BackupData.ExchangeBackupDatabase object attributes

The EMCExchangeBackupRestore.BackupData.ExchangeBackupDatabase object lists information for a single database.

The following table lists the attributes that the EMCExchangeBackupRestore.BackupData.ExchangeBackupDatabase object contains:

Table 5. Attributes of the EMCExchangeBackupRestore.BackupData.ExchangeBackupDatabase object

Attribute Description

Identity The identity of the database.

Guid The GUID of the database.

BackupID The backup ID of the individual database.

Though you can use this attribute to restore an individual database, the Microsoft application agent recommends you to use the general or overall BackupID to perform restores.

DatabaseFileBackupID The backup ID of the EDB backup. In the case of a block based backup, this attribute is different from the BackupID attribute.

You cannot use this backup ID to perform restores.

LogFilesBackupID The backup ID of the log folder backup. In the case of a block based backup, this attribute is different from the BackupID attribute.

You cannot use this backup ID to perform restores.

EdbFilePath The original path of the backed up EDB file. This attribute corresponds to Get-Datatabase | Format-Table EdbFilePath during the backup.

LogFolderPath The original folder of the backed up log files. This attribute corresponds to Get-Database | Format-Table LogFolderPath during the backup.

EMCExchangeBackupRestore.BackupData.ExchangeBackup object attributes

The EMCExchangeBackupRestore.BackupData.ExchangeBackup object lists an array of database backup objects.

The following table lists the attributes that the EMCExchangeBackupRestore.BackupData.ExchangeBackup object contains:

Table 6. Attributes of the EMCExchangeBackupRestore.BackupData.ExchangeBackup object

Attribute Description

BackupDateTimeUTC The date and time of the backup in UTC.

BackupDatabases An array of EMCExchangeBackupRestore.BackupData.ExchangeBackupDatabase objects.

BackupID The ID of the backup. Each ID has the backup technology and a colon as the prefix.

In the case of block based backups, the prefix is msapp_bbb:.

If you do not specify a prefix for a backup ID in any of the Exchange Server backup operations, the default prefix is msapp_pp:.

BookmarkName Empty list.

ClientName The FQDN of the Exchange Server.

DataDomainHost The Data Domain server name.

50 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Table 6. Attributes of the EMCExchangeBackupRestore.BackupData.ExchangeBackup object (continued)

Attribute Description

DataDomainHostPath The full path to the Data Domain storage unit.

ExchangeVersion The version of the Exchange Server.

Level The backup level, which is always FULL even in the case of incremental block based backups.

StaticImages An array of EMCExchangeBackupRestore.BackupData.ExchangeBackupDDStaticImage objects.

Successful $true, if the backup is successful.

Formatting the list of backups

If the BackupDatabases column values are truncated and include dots at the end, you can increase the windows and buffer length in the Exchange management shell.

In addition to increasing the length, you can use the following commands to better format the output and filter the output:

To display the full output:

Get-ExchangeBackup | format-table -AutoSize To list only the backups that contain a specific database:

$list = Get-ExchangeBackup | format-table -AutoSize

$list = foreach($obj in $list) { foreach($bkup in $obj.BackupDatabases){ if($bkup.Identity -EQ "DatabaseName"){ Write-Output $obj } } }

To list the backups that occurred on a specific date:

$list | where BackupDateTimeUTC -CMatch "6/14/2020"

To perform various types of comparisons, you can use the following flags:

"CGE"Greater than or equal to a specific value. "CGT"Greater than a specific value. "CLE"Less than or equal to a specific value. "CLT"Less than a specific value.

Restore an Exchange application host You can perform database or granular-level restores directly to the Exchange application host using the Microsoft application agent.

Prerequisite for Exchange restore operations

You must run the set-mailboxdatabase cmdlet to allow an Exchange database to be restored from a backup.

Run the set-mailboxdatabase PowerShell cmdlet with the following syntax prior to any restore operation:

set-mailboxdatabase -AllowFileRestore $true

where:

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 51

Specifies the name of the database that is the target for the restore operation.

-AllowFileRestore $true

Specifies to allow restore operations for the database.

NOTE: Run this command for each target database for the restore operation.

The Microsoft documentation provides more information on the set-mailboxdatabase cmdlet.

Restoring Exchange Server databases

The Microsoft application agent supports the following types of database restores:

Normal restore: Restore of a database to the original source database. Alternate database restore: Restore of a database to another database that is different from the source database.

You can view the list of backups and then restore only the required backups by using the backup IDs. Listing backups and save files on page 46 provides information about how to list backups.

Restore a backup to the source database

Use the Restore-Exchange cmdlet with the following syntax to restore a database to the source location (normal restore):

[ ] | Restore-Exchange -NormalRestore {-BackupID [- Identity ] | -Backup } -ClientName - DataDomainHost -DataDomainHostPath / - DataDomainUser

where:

(Optional) Specifies the configuration object that was imported using the Import- ExchangeBackupConfigFile cmdlet.

NOTE: For PowerProtect Data Manager centralized and self-service workflows, run the Import- ExchangeBackupConfigFile cmdlet with the -Restore parameter to import the configuration

parameters to the object.

-NormalRestore

Specifies that the database is being restored to the original source location.

You can use the -Restore alias for the -NormalRestore parameter.

{-BackupID [-Identity ] | -Backup }

Specifies the backup to restore using either the backup identity or object. You must specify only one of the following options:

Specify -BackupID to use a backup ID. Optionally, specify -Identity with -BackupID to specify the identity of one or more databases to restore.

Specify -Backup to use a backup object.

You can retrieve the backup ID and object from the Backup-Exchange or Get-ExchangeBackup cmdlet output.

-ClientName

Specifies the client name that was used for the backup.

You can use the -C or -CN alias for the -ClientName parameter.

-DataDomainHost

Specifies the hostname of the Data Domain server that contains the backups.

You can use the -S, -SH, -DDHost or -StorageHost alias for the -DataDomainHost parameter.

-DataDomainHostPath

52 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Specifies the full path of the Data Domain storage unit that contains the backups.The Data Domain user must have appropriate access rights to this path.

You can use the -Path, -DevicePath, -StoragePath, -StorageHostPath, or - DataDomainPath alias for the -DataDomainHostPath parameter.

-DataDomainUser

Specifies the Data Domain username.

Full credentials are retrieved from the lockbox to authenticate with the host. -DDUser, - StorageUser You can use the -DDUser or -StorageUser alias for the -DataDomainUser parameter.

Restore a backup to an alternate database

NOTE: Before you perform a copy or alternate database restore, ensure that the target database exists.

Use the Restore-Exchange cmdlet with the following syntax to restore a database to an alternate location (copy restore):

[ ] | Restore-Exchange -CopyRestore -BackupID -Identity -RestoreDatabaseIdentity -ClientName -DataDomainHost -DataDomainHostPath / -DataDomainUser [ ]

where:

(Optional) Specifies the configuration object that was imported using the Import- ExchangeBackupConfigFile cmdlet.

NOTE: For PowerProtect Data Manager centralized and self-service workflows, run the Import- ExchangeBackupConfigFile cmdlet with the -Restore parameter to import the configuration

parameters to the object.

-CopyRestore

Specifies that the database is being restored to an alternate location.

You can use the -Alternate alias for the -CopyRestore parameter.

-BackupID

Specifies the backup ID to restore. You can retrieve the backup ID from the Backup-Exchange or Get-ExchangeBackup cmdlet output.

-Identity

Specifies the identity of one or more databases to restore.

-RestoreDatabaseIdentity

Specifies the target identity of the alternate database to restore to.

You can use the -RestoreDB, -Target, -RDB, or -RestoreDatabaseID alias for the - CopyRestore parameter.

-ClientName

Specifies the client name that was used for the backup.

You can use the -C or -CN alias for the -ClientName parameter.

-DataDomainHost

Specifies the hostname of the Data Domain server that contains the backups.

You can use the -S, -SH, -DDHost or -StorageHost alias for the -DataDomainHost parameter.

-DataDomainHostPath

Specifies the full path of the Data Domain storage unit that contains the backups.The Data Domain user must have appropriate access rights to this path.

You can use the -Path, -DevicePath, -StoragePath, -StorageHostPath, or - DataDomainPath alias for the -DataDomainHostPath parameter.

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 53

-DataDomainUser

Specifies the Data Domain username.

Full credentials are retrieved from the lockbox to authenticate with the host. -DDUser, - StorageUser You can use the -DDUser or -StorageUser alias for the -DataDomainUser parameter.

Optional parameters for the Restore-Exchange cmdlet

The following list details the optional parameters for the Restore-Exchange cmdlet:

-ExcludeClientNameResolution

Uses the client name that is provided as-is without converting it to the fully qualified domain name (FQDN).

Use this parameter to restore a backup taken with Microsoft application agent version 4.5 or earlier that uses the short name as the client name.

You can use the -ExcludeCNResolution alias for the -ExcludeClientNameResolution parameter.

-Confirm:{$true | $false}

Specifies whether to enable confirmation prompts for the operation. The default value is $true.

-PointInTime:{$true | $false}

Specifies whether to perform a point-in-time-restore operation. The default value is $true.

You can use the -PIT alias for the -PointInTime parameter.

-ExchangeServer

Specifies the short name of the Exchange Server, for example, ledmf999, if the name is different from the local hostname.

If you do not specify a value, the parameter takes the local hostname by default.

-DataDomainVDiskUser

Specifies the Data Domain vdisk user.

If you do not specify this parameter, the value defaults to the -DataDomainUser value.

Full credentials are retrieved from the lockbox to authenticate with the host.

You can use the -DDVDiskUser, -VDiskUser, or -VDU alias for the -DataDomainVDiskUser parameter.

-LockBoxPath

Specifies the folder that contains the lockbox file, which contains encrypted information about the registered hosts and the corresponding usernames in pairs. Each pair is associated with a password that backups use.

You can use the -LB or -LBPath alias for the -LockBoxPath parameter.

-Debug

Specifies to enable the PowerShell debug output. By default, the cmdlet pauses on every debug output.

-DebugLevel <1_through_9>

Specifies the debug level for the backup. The default value is 0 (zero).

You can use the -DL or -D alias for the -DebugLevel parameter.

-DeleteDebugLogsInDays

Deletes debug log files that are older than the specified number of days. The valid range is between 1 and 32767

By default, debug logs are not deleted. Regularly deleting debug logs prevents the log folder on the installation drive from becoming too large.

This parameter only deletes debug logs named in the default format and located in the logs folder at \MSAPPAGENT\logs.

-Verbose

54 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Indicates the verbose output. In this context, the standard output stream of the Microsoft application agent appears.

You can use the -vb alias for the -Verbose parameter.

-VeryVerbose {True | False}

Increases the volume of the verbose output.

To use this parameter, you must also specify the -Verbose parameter.

The default value is False.

-ExeFileName

Specifies the full path to the application program executable, that is, msagentrc.exe.

Use this option only to diagnose. In normal operations, the cmdlet automatically locates the installed application.

-AsJob {$true | $false}

Runs the cmdlet as a background job.

The command returns an object that represents the job, and then displays the command prompt. You can continue to work in the session during the job.

You can use the -AJ or -Job alias for the -AsJob parameter.

-JobName

Specifies a friendly name for the job when you use this parameter with the -AsJob parameter. If you do not specify the -AsJob parameter, the -JobName parameter is ignored.

You can use the name to identify the job against other job cmdlets such as, Stop-Job.

Performing granular-level restores

To recover granular-level Exchange Server data, you must first mount the backup using the Mount-ExchangeBackup PowerShell cmdlet. Once the backup is mounted, you can browse and recover granular items, such as mailboxes or folders, with ItemPoint for Microsoft Exchange Server.

Mount backups

To perform granular-level restores, you must first mount the backups.

Use the Mount-ExchangeBackup cmdlet with the following syntax to mount backups:

[ = ] Mount-ExchangeBackup {-BackupID [- Identity ] | -Backup } -ClientName - DataDomainHost -DataDomainHostPath / - DataDomainUser [ ]

where:

(Optional) Specifies the name of the mount object when using a configuration object.

(Optional) Specifies the configuration object that was imported using the Import- ExchangeBackupConfigFile cmdlet.

NOTE: For PowerProtect Data Manager centralized and self-service workflows, run the Import- ExchangeBackupConfigFile cmdlet with the -Restore parameter to import the configuration

parameters to the object.

{-BackupID [-Identity ] | -Backup }

Specifies the backup to restore using either the backup identity or object. You must specify only one of the following options:

Specify -BackupID to use a backup ID. Optionally, specify -Identity with -BackupID to specify the identity of one or more databases to restore.

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 55

Specify -Backup to use a backup object.

You can retrieve the backup ID and object from the Backup-Exchange or Get-ExchangeBackup cmdlet output.

-ClientName

Specifies the client name that was used for the backup.

You can use the -C or -CN alias for the -ClientName parameter.

-DataDomainHost

Specifies the hostname of the Data Domain server that contains the backups.

You can use the -S, -SH, -DDHost or -StorageHost alias for the -DataDomainHost parameter.

-DataDomainHostPath /

Specifies the full path of the Data Domain storage unit that contains the backups.The Data Domain user must have appropriate access rights to this path.

You can use the -Path, -DevicePath, -StoragePath, -StorageHostPath, or - DataDomainPath alias for the -DataDomainHostPath parameter.

-DataDomainUser

Specifies the Data Domain username.

Full credentials are retrieved from the lockbox to authenticate with the host. -DDUser, - StorageUser You can use the -DDUser or -StorageUser alias for the -DataDomainUser parameter.

Result

The backup is mounted in a path similar to the following:

C:\Program Files\DPSAPPS\MSAPPAGENT\tmp\BBBMountPoint \131248297060279537_{4A60AF18-86ED-4BBD-A1C9-2618F1AC1041}_5832\Program Files\Microsoft \Exchange Server\V15\Mailbox\DB2\ The mounted items are unmounted after you restart the host.

Browse and recover granular-level data with ItemPoint for Microsoft Exchange Server

Prerequisites

Before you use ItemPoint for granular-level recovery, ensure that the backup is mounted.

About this task

The ItemPoint for Exchange Server User Guide provides more information on performing granular-level recovery of Exchange data.

Steps

1. Launch ItemPoint.

2. In ItemPoint, launch the Restore wizard.

3. On the Source Selection page, select the source and specify the EDB and log file path from the mounted volume that contains the Exchange backup data as shown in the following figure, and then click Next.

56 Performing Self-Service Backups and Restores of Microsoft Exchange Databases

Figure 1. Selecting the source path in ItemPoint for Exchange Server

4. On the Target Selection page, click Skip.

Figure 2. Selecting target path in ItemPoint for Exchange Server

5. Follow the Data Wizard prompts to complete the granular-level recovery.

The ItemPoint for Exchange Server User Guide provides more information.

Next steps

Once the granular-level recovery is complete, dismount the backup.

Managing mounted backups with the Mount Service system tray icon

After a mount operation succeeds, the Mount Service system tray icon appears as shown in the following figure.

Performing Self-Service Backups and Restores of Microsoft Exchange Databases 57

Figure 3. Mount Service system tray icon

Right-click the Mount Service icon, and select any of the following options to perform corresponding tasks according to your requirement:

Dismount Backups: Dismounts the mounted backups. Mount Details: Lists the mounted backups with mount details. Extend Timeout: Extends the timeout of the mount. The default value is 8 hours.

List Exchange Server mounted backups using the Mount Service system tray icon

To list the mounted block-based backup

Manualsnet FAQs

If you want to find out how the 19.6 Dell works, you can view and download the Dell PowerProtect 19.6 Data Manager Exchange Server User Guide on the Manualsnet website.

Yes, we have the Exchange Server User Guide for Dell 19.6 as well as other Dell manuals. All you need to do is to use our search bar and find the user manual that you are looking for.

The Exchange Server User Guide should include all the details that are needed to use a Dell 19.6. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell PowerProtect 19.6 Data Manager Exchange Server User Guide is by checking the Table of Contents at the top of the page where available. This allows you to navigate a manual by jumping to the section you are looking for.

This Dell PowerProtect 19.6 Data Manager Exchange Server User Guide consists of sections like Table of Contents, to name a few. For easier navigation, use the Table of Contents in the upper left corner.

You can download Dell PowerProtect 19.6 Data Manager Exchange Server User Guide free of charge simply by clicking the “download” button in the upper right corner of any manuals page. This feature allows you to download any manual in a couple of seconds and is generally in PDF format. You can also save a manual for later by adding it to your saved documents in the user profile.

To be able to print Dell PowerProtect 19.6 Data Manager Exchange Server User Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell PowerProtect 19.6 Data Manager Exchange Server User Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.