Contents

Dell PowerProtect 19.5 Data Manager Installation Guide PDF

1 of 22
1 of 22

Summary of Content for Dell PowerProtect 19.5 Data Manager Installation Guide PDF

PowerProtect Microsoft Application Agent Installation Guide

Version 19.5

Dell Inc.

September 2020 Rev. 03

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.

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

Tables........................................................................................................................................... 4

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

Chapter 1: Product Overview.........................................................................................................8 Introduction to the Microsoft application agent..........................................................................................................8 Application Direct overview.............................................................................................................................................. 8 Storage Direct overview.................................................................................................................................................... 9

Chapter 2: Installing the Microsoft Application Agent..................................................................10 System requirements........................................................................................................................................................ 10 Prerequisites....................................................................................................................................................................... 10

SQL Server prerequisites........................................................................................................................................... 10 Exchange Server prerequisites.................................................................................................................................. 11

Installing the Microsoft application agent.................................................................................................................... 12 Installing the Microsoft application agent using the installation wizard......................................................... 12 Installing the Microsoft application agent with the command prompt (silent installation)........................13

Important steps to perform after installation..............................................................................................................15 Deploying the CLR assembly..................................................................................................................................... 15 (Optional) Creating and registering the T-SQL stored procedures in a user database..............................16

Changing the Microsoft application agent installation options............................................................................... 17

Chapter 3: Upgrading the Microsoft Application Agent................................................................ 18 Upgrading the Microsoft application agent by using the upgrade wizard........................................................... 18 Upgrading the Microsoft application agent by using the command line interface (silent upgrade)..............18 Using the backup discovery tool for PowerProtect Data Manager management of existing backups........ 19

Chapter 4: Uninstalling the Microsoft Application Agent..............................................................21 Uninstall the Microsoft application agent with the setup file................................................................................. 21 Uninstalling the Microsoft application agent by using the Windows uninstall program....................................21 Uninstalling the Microsoft application agent with the command prompt (silent uninstallation)................... 22

Contents

Contents 3

1 Revision history.......................................................................................................................................................... 5

2 Style conventions.......................................................................................................................................................6

3 Required silent install command variables.......................................................................................................... 14

4 Optional silent install command variables........................................................................................................... 14

5 Supported command options to run ddbmaSQLCLRDeployApp.exe........................................................... 16

Tables

4 Tables

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

Purpose This document describes how to install and upgrade the PowerProtect Microsoft application agent.

Audience This document is intended for the user who installs and upgrades the Microsoft application agent.

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

Table 1. Revision history

Revision Date Description

03 September 30, 2020 Updated the following topic:

SQL Server prerequisites (Chapter 2)Added the final bullets about SQL Server host system requirements.

02 August 18, 2020 Updated the following topics:

Installing the Microsoft application agent using the installation wizard (Chapter 2)In step 2, deleted the line about typing a password at the password prompt.

Upgrading the Microsoft application agent by using the upgrade wizard (Chapter 3)In step 2, deleted the line about typing a password at the password prompt.

01 June 30, 2020 Initial release of this document for the Microsoft application agent 19.5.

Related documentation The following publications provide additional information:

PowerProtect Microsoft Application Agent Exchange Server User Guide PowerProtect Microsoft Application Agent SQL Server User Guide PowerProtect Microsoft Application Agent Release Notes PowerProtect ItemPoint for Microsoft SQL Server User Guide PowerProtect ItemPoint for Microsoft Exchange Server User Guide

Preface 5

PowerProtect Database Application Agent Installation and Administration Guide PowerProtect Database Application Agent Release Notes DDBEA section of the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection Data Domain Operating System documentation PowerProtect Storage Direct Primary and Protection Storage Configuration Guide PowerProtect Storage Direct Solutions Guide RecoverPoint documentation XtremIO documentation VMAX documentation

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

Table 2. Style conventions

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

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.

6 Preface

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.

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.

Preface 7

Product Overview

Topics:

Introduction to the Microsoft application agent Application Direct overview Storage Direct overview

Introduction to the Microsoft application agent The Microsoft application agent leverages an enterprise application data protection framework to provide application-centric data protection.

The Microsoft application agent enables database and application administrators to efficiently back up and restore applications by using the applications native tools.

Microsoft application agent backups are application-consistent. The Microsoft application agent can completely restore the backups.

Application Direct overview Application Direct integrates with the following technologies:

Data Domain Boost Data Domain, a purpose-build backup appliance

The Microsoft application agent for Application Direct provides the following capabilities:

Supports Application Direct backups to a Data Domain system. Supports Application Direct backups and restores of SQL Server over either an Ethernet (IP) or a Fibre Channel (FC)

network connection to Data Domain. Backups and restores use a SQL Virtual Device Interface (VDI). Supports Application Direct backups and restores of Exchange Server over either IP or FC to Data Domain by using the

block-based backup technology. Supports in-flight encryption for Application Direct connections to a Data Domain 6.0 or later operating system over a WAN

connection.

To use this feature, you can configure the Data Domain system with either medium-strength or high-strength TLS encryption. The configuration is transparent to the Microsoft application agent. The latest Data Domain Boost Administration Guide provides information.

Supports Internet Protocol version 6 (IPv6) for Application Direct backups and restores. Supports Data Domain IPv4, IPv6, and mixed IPv4 and IPv6 networks, that is, multi-homed environments of dual NIC

environments. Supports federated Application Direct backups to protect SQL Server Always On availability group environments, which

honors the Always On availability groups Backup Preferences that were set on the SQL Server. You can set backup preferences to perform tasks, such as offloading backups to a specific secondary node.

Supports federated Application Direct backups of Exchange Server Database Availability Groups (DAGs). Supports backup and recovery operations for Data Domain Virtual Edition (DDVE) for SQL Server and Exchange Server in

the following cloud environments:

Amazon Web Services (AWS) cloud. Azure cloud.

NOTE: Cluster configurations and cloud-tier are not supported for AWS and Azure cloud environments.

1

8 Product Overview

Storage Direct overview The Storage Direct solution integrates primary storage with protection storage for backups to a Data Domain system.

Storage Direct provides block movement of the data on application source LUNs to Data Domain LUNs over a dedicated storage network.

The application host neither reads nor moves data. Only the changed blocks are moved from primary storage to protection storage over the dedicated network.

The Storage Direct workflow can provide data protection in situations, such as small or non-existent backup windows, demanding recovery time objective (RTO) or recovery point objective (RPO) requirements, or a combination of these situations, when more traditional approaches cannot successfully meet business demands.

The Microsoft application agent for Storage Direct provides the following capabilities:

Enables you to perform the following types of backups:

Storage Direct with RecoverPoint backups from XtremIO primary storage to a Data Domain system Storage Direct backups from Symmetrix VMAX primary storage to a Data Domain system

Supports SQL and Exchange server backup and restore operations on the following storage arrays:

XtremeIO with RecoverPoint VMAX

Supports Internet Protocol version 6 (IPv6) for Storage Direct backups and restores. In the case of federated Storage Direct backups, the Microsoft application agent backs up Always On availability group

databases as stand-alone databases. Offloading backups to another node for Storage Direct protection is not a concern because data moves from primary storage directly to a Data Domain system.

Product Overview 9

Installing the Microsoft Application Agent

Topics:

System requirements Prerequisites Installing the Microsoft application agent Important steps to perform after installation Changing the Microsoft application agent installation options

System requirements The DDBEA section of the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection provides information about the supported operating systems and applications for the Microsoft application agent for Application Direct and Storage Direct.

Prerequisites Ensure that the following prerequisites are met before you install the Microsoft application agent.

SQL Server prerequisites

Ensure that a SQL Server environment meets the following prerequisites before installing the Microsoft application agent:

Ensure that the volume on which you install the Microsoft application agent will not be part of backups. Install the following applications on the host as Administrator:

Microsoft SQL Server. Either the SQL Server Management Studio (SSMS) as part of the SQL Server installation or the Microsoft Visual Studio

2010 Shell (Isolated) Redistributable Package management tool. .NET Framework 4.0.

To install and use ItemPoint for SQL for Storage Direct backups, install .Net 4.5 framework.

The DDBEA section of the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection provides more information about the supported software and operating system versions.

If you are installing Microsoft application agent with Storage Direct for VMAX, install VMAX Solutions Enabler first before you install Microsoft application agent. Otherwise, when the Microsoft application agent is installed it overwrites the registry keys. Ensure that you perform a typical installation of the VMAX Solutions Enabler. The Solutions Enabler Installation and Configuration Guide provides installation instructions.

Obtain the required software licenses.

Contact your sales representative for more details about the required licenses for the environment.

Download the Microsoft application agent software package from Online Support (https://www.dell.com/support) to the Windows Microsoft application agent for SQL Server host.

To deploy Common Language Runtime (CLR) assembly and run CLR-integrated T-SQL functions in a SQL environment, you must be an administrator on:

The SQL host domain admin if the SQL host is part of domain and SQL server is running in the context of a domain admin.

The SQL Server and the master database. To register the CLR assembly that you require for T-SQL integration, you have made .NET Framework 4.0 available in the

MSSQL environment.

2

10 Installing the Microsoft Application Agent

For the Windows login account that the Microsoft application agent backup and restore processes use to connect to a SQL Server, grant the following roles:

SQL Server system administrator (sysadmin) role to provide the T-SQL backup query. SQL Server sysadmin role to open a shared memory handle when starting the VDI.

As a Microsoft application agent user, ensure that you are a member of the following groups:

Local backup operators group. Local administrators group.

For SQL Server Application Direct operations, the PowerProtect Microsoft Application Agent SQL Server User Guide provides the minimum user privileges that are required for the SQL Server and Windows account.

Log in with an administrative user to install and start the Microsoft application agent. If you are not a domain administrator user, run as a local administrator.

To perform the Microsoft application agent for SQL Server backups to a Data Domain server over FC, you have granted the SQL Server user (SERVICE) the administrator privileges.

To successfully create backup and restore logs, you have granted the SQL Server user (SERVICE) the write access to the Microsoft application agent installation folder and the log subfolder.

Log in with an administrative user to run ItemPoint. You must run ItemPoint in the administrative mode. Installation of the PowerProtect agent requires port 7000 to be open bidirectionally. This port is required to enable

communication between the Microsoft application agent and the PowerProtect appliance. Each SQL Server host meets the following minimum system requirements:

In a scaled environment:

8 CPU cores 16 GB of RAM

In a stand-alone environment:

4 CPU cores 4 GB of RAM

NOTE: It is recommended to use stripes only in the case of large databases.

Exchange Server prerequisites

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

Ensure that the volume on which you Install the Microsoft application agent will not be part of backups. Install the following applications on the host as Administrator:

Microsoft Exchange Server. .NET Framework 4.0.

To install and use ItemPoint for Exchange for Storage Direct backups, install .NET 4.0 SP1 framework.

Ensure that you are using Microsoft Office Outlook 2010 or later (32-bit versions only).

The DDBEA section of the eLab Navigator at https://elabnavigator.emc.com/eln/modernHomeDataProtection provides more information about the supported software and operating system versions.

If you are installing Microsoft application agent with Storage Direct for VMAX, install VMAX Solutions Enabler first before you install Microsoft application agent. Otherwise, when Microsoft application agent is installed it overwrites the registry keys. Ensure that you perform a typical installation of the VMAX Solutions Enabler in local mode. The Solutions Enabler Installation and Configuration Guide provides installation instructions.

Obtain one of the following software licenses:

Data Protection Suite for Enterprise Applications Capacity license. Data Protection Suite Capacity license.

To enable Storage Direct with RecoverPoint operations with an XtremIO system, obtain the appropriate XtremIO and RecoverPoint source capacity licenses.

Contact your sales representative for more details about the license for the environment.

Download the Microsoft application agent software package from Online Support (https://www.dell.com/support) to the Windows Microsoft application agent for Exchange Server host.

Ensure that the Microsoft application agent user is a member of the local administrators group.

Installing the Microsoft Application Agent 11

Log in with an administrative user to install and start the Microsoft application agent. If you are not a domain administrator user, run as a local administrator.

Log in with an administrative user to run ItemPoint. You must run ItemPoint in the administrative mode.

Installing the Microsoft application agent Your system must meet specific requirements and prerequisites before you install the Microsoft application agent.

NOTE:

The Microsoft application agent can coexist with the File System agent, but cannot coexist with the database application

agent.

If a table-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 table-level

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

unloaded prior to an uninstall operation.

Installing the Microsoft application agent using the installation wizard

To install the Microsoft application agent using the installation wizard, perform the following steps:

About this task

Steps

1. Download the msappagent195_win_x64.zip file to the host where you want to install the Microsoft application agent.

2. Open msappagent195_win_x64.zip with WinZip.

3. Use WinZip to extract the msappagent195_win_x64.zip file.

4. In the extracted folder, launch emcmsappagent-19.5.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 folder, leave the installation location as-is.

The default installation folder 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.

7. Click Next.

8. On the Configure Installation Options page, complete the following steps:

a. Select any of the following install options as required:

Select Application Direct to install the Data Domain Boost for Enterprise Applications (DDBEA) solution to protect data using Data Domain Boost technology.

Select Storage Direct to install the Storage Direct hardware provider to protect data using VMAX or RecoverPoint. Select VM Direct to restore a backup to a SQL Server virtual machine that is not protected in a PowerProtect

protection policy.

NOTE: By default, when a SQL Server virtual machine is added to a protection policy in PowerProtect, the

Microsoft application agent and ItemPoint silently install on the protected virtual machine. When you are restoring

a VM Direct backup to an alternate instance on a virtual machine that is not part of a protection policy, you must

install the Microsoft application agent on the target virtual machine.

12 Installing the Microsoft Application Agent

Select SSMS Plug-in to install the SQL Server Management Studio plug-in user interface, which you can use to perform SQL Server backup and restore operations.

Select ItemPoint to install the ItemPoint software, which you can use to perform granular-level and table-level restore operations.

NOTE: If a table-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 table-level restores. The Eldos CBFS driver is loaded during the table-level restore operation. Microsoft

requires the driver to be unloaded prior to an uninstall operation.

To connect the Microsoft application agent with a PowerProtect appliance, perform the following steps:

i. Select the PowerProtect Data Manager check box. ii. In the Appliance Hostname or IP address field, type the hostname or IP address of the PowerProtect server.

You can enable integration with a PowerProtect server at any time by re-running the installation wizard.

NOTE: Installation of the PowerProtect agent requires port 7000 to be open bidirectionally. This port is required to

enable communication between the Microsoft application agent and the PowerProtect appliance.

b. Click Install >.

NOTE: If you select Storage Direct and the Solutions Enabler is not detected on the host, a warning message appears.

Ensure that you install Solutions Enabler before you install the Microsoft application agent.

9. For SQL Server only, review the information in Deploying the CLR assembly on page 15 and (Optional) Creating and registering the T-SQL stored procedures in a user database on page 16.

10. For SQL Server only, on the CLR assembly deployment wizard page, perform the following steps:

NOTE: This step does not apply to installations on Exchange Server. If you are installing the software on an Exchange

Server, click Close.

a. Select or clear the SQL Server instances on which you want to deploy the CLR Assembly. By default, all the SQL Server instances are selected.

b. To deploy CLR Assembly, select one of the following authentication options:

Current Windows User Use Windows Authentication Use Database Authentication

c. Select Enable ProtectPoint Stored Procedures to use the Storage Direct stored procedures. d. In the User name and Password fields respectively, type the username and the password of the user who has the

privileges to deploy the CLR Assembly. e. Click Deploy.

If you have selected ItemPoint to install on a SQL Server host, the Windows Security dialog box appears to confirm the installation of the EldoS driver.

f. Click Install. g. After the deployment completes, click Next.

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

If you are installing the Microsoft application agent on an Exchange Server host, the App Agent Exchange Admin Configuration tool launches. The PowerProtect Microsoft Application Agent Exchange Server User Guide provides information about the tool.

Installing the Microsoft application agent with the command prompt (silent installation)

To silently install the Microsoft application agent, run the following command:

emcmsappagent-19.5.0.0.exe -silent -log " " [ProductInstallPath=" "] [EnableSSMS={0|1}] [EnableVMDirect={0|1}] [EnableProtectPoint={0|1}] [EnableSSMSProtectPoint={0|1}] [InstallPPDMAgentCheckBox={0|

Installing the Microsoft Application Agent 13

1}] [PPDMHostname=" "] [EnableCLR={0|1}]

NOTE: The ItemPoint software cannot be installed silently. To install ItemPoint for granular-level recovery, use the

Microsoft application agent installation wizard.

The following table describes the required silent install command variables.

Table 3. Required silent install command variables

Variable Description

-silent Indicates a silent installation.

-log " " Specifies the path where the log file must be created or saved.

The log file displays the status of the installation. In the case of silent installation, you must use the -log option.

The following table describes the optional silent install command variables.

Table 4. Optional silent install command variables

Variable Description

ProductInstallPath=" " Specifies a modified path where the product must be installed. If you don't specify this option, the product is installed to the default location.

EnableSSMS={0|1} Specifies whether to install the SSMS plug-in. The default value is 1, which installs the SSMS plug-in.

EnableVMDirect={0|1} Installs VM Direct when you specify 1. The default value is 0, which does not install VM Direct.

EnableProtectPoint={0|1} Installs the Storage Direct hardware provider when you specify 1. The default value is 0, which does not install Storage Direct.

EnableSSMSProtectPoint={0|1} Installs the Storage Direct hardware provider and the SSMS plug-in for Storage Direct when you specify 1. The default value is 0, which does not install these options.

InstallPPDMAgentCheckBox={0|1} Integrates the Microsoft application agent with a PowerProtect server during installation when you specify 1. The default value is 0.

NOTE: Installation of the PowerProtect agent requires port 7000 to be open bidirectionally. This port is required to enable communication between the Microsoft application agent and the PowerProtect appliance.

PPDMHostname=" " Specifies the hostname or IP address of the PowerProtect server where the backup information will be reported.

EnableCLR={0|1} Specifies whether to deploy CLR. By default, this option is enabled and has the value 1, which deploys CLR.

Example commands to silently install the Microsoft application agent

Consider the following example commands to silently install the Microsoft application agent:

The following command installs the Microsoft application agent with VM Direct:

emcmsappagent-19.5.0.0.exe -silent EnableVMDirect=1

14 Installing the Microsoft Application Agent

The following command installs the Microsoft application agent with the Application Direct SSMS plug-in:

emcmsappagent-19.5.0.0.exe -silent -log "C:\Users\Administrator\Desktop \installLog.txt" ProductInstallPath="C:\Users\Administrator\Desktop\EMC msappagent sappagent40"

The following command installs the Microsoft application agent without deploying CLR:

emcmsappagent-19.5.0.0.exe -silent -log "C:\Users\Administrator\Desktop \installLog.txt" ProductInstallPath="C:\Users\Administrator\Desktop\EMC msappagent sappagent40" EnableCLR=0

The following command installs the Microsoft application agent with Storage Direct only:

emcmsappagent-19.5.0.0.exe -silent -log "C:\Users\Administrator\Desktop \installLog.txt" ProductInstallPath="C:\Users\Administrator\Desktop\EMC msappagent sappagent40" EnableProtectPoint=1 EnableSSMS=0

The following command installs the Microsoft application agent with Storage Direct and the SSMS plug-in:

emcmsappagent-19.5.0.0.exe -silent -log "C:\Users\Administrator\Desktop \installLog.txt" ProductInstallPath="C:\Users\Administrator\Desktop\EMC msappagent sappagent40" EnableSSMSProtectPoint=1

The following command installs the Microsoft application agent with the PowerProtect integration:

emcmsappagent-19.5.0.0.exe -silent InstallPPDMAgentCheckBox=1 PPDMHostname=" "

Important steps to perform after installation Install the Microsoft application agent on all the nodes of a SQL Server cluster so the CLR Assembly is deployed for all the

SQL Server instances. To deploy the CLR Assembly on a new instance, or modify the CLR Assembly on an instance, run the CLR Assembly

deployment wizard by using ddbmaSQLCLRDeployApp.exe, which is typically present in the \DPSAPPS\MSAPPAGENT\bin folder.

The installer installs all the binaries as a single agent that supports Application Direct and Storage Direct. However, the installer registers the Storage Direct Hardware Provider as a COM service (automatic), which is inactive.

If you will perform backups through PowerProtect Data Manager, enable the discovery and scheduling of backups with PowerProtect Data Manager by approving the client in the PowerProtect Data Manager UI.

Deploying the CLR assembly

You must deploy the CLR Assembly to perform any of the following tasks in a SQL Server environment:

Create and use T-SQL backups Delete expired backups Restore T-SQL backups

To deploy the CLR Assembly on a SQL Server instance, you must enable or register the CLR assembly on the SQL Server. The Microsoft application agent for SQL Server installation process uses the registered CLR assembly to deploy the CLR-integrated T-SQL functions. http://msdn.microsoft.com/en-us/library/ms254498(v=vs.110).aspx provides information about SQL Server CLR.

The deployment creates a CLR assembly (Dynamic Link Library [DLL]) that contains the following stored procedures, which run the Microsoft application agent for SQL Server CLI commands:

emc_run_backup emc_run_restore emc_run_delete protectpoint_run_backup protectpoint_run_restore protectpoint_run_delete

Installing the Microsoft Application Agent 15

The Microsoft application agent for Application Direct with SQL Server chapter provides information about using the Microsoft application agent for SQL Server command prompt and GUI.

You must deploy the CLR Assembly on all the SQL Server instances, on which you want to run the Microsoft application agent for SQL Server T-SQL scripts.

To deploy the CLR Assembly on a new instance, or modify the CLR Assembly on an instance, run the CLR Assembly deployment wizard by using ddbmaSQLCLRDeployApp.exe, which is typically present in the \DPSAPPS\MSAPPAGENT\bin folder.

You can run the binary either in an interactive Windows mode, or with the command prompt by specifying the -q option.

The following table lists the supported command line options and their description.

Table 5. Supported command options to run ddbmaSQLCLRDeployApp.exe

Option Description

-h | -help Displays the usage of the command line and the description of the behavior.

-m: [install | uninstall] Runs the application in either the installation or the uninstallation mode. The default value is install.

-i : Specifies the name of the instance to register. If you do not specify the instance name, all the instances are connected.

-u: Specifies the name of the database user to use for SQL connection.

-q: Does not display the GUI to the user and displays all text to the console.

(Optional) Creating and registering the T-SQL stored procedures in a user database

By default, the installation wizard (CLR deployment wizard) creates the stored procedures in the master database. However, you can create and register the T-SQL stored procedures in a user database, which is not a master database.

About this task

NOTE: This procedure uses the default Microsoft application agent installation path. If the Microsoft application agent is

not installed in the default path, use the relevant path in the commands.

Steps

1. When you install the Microsoft application agent, do not deploy the CLR Assembly on the SQL Server instance, on which you want to register the Microsoft application agent stored procedures in a user database. If the assembly is already registered on the instance, unregister or remove the assembly by using the ddbmaSQLCLRDeployApp.exe file.

2. After the Microsoft application agent installation completes, run the following commands on the SQL Server:

sp_configure 'show advanced options', 1; GO RECONFIGURE; GO sp_configure 'clr enabled', 1; GO RECONFIGURE; GO

NOTE: If you have modified the CPU or IO affinity mask for the server, replace RECONFIGURE with RECONFIGURE WITH OVERRIDE in the above commands. This modification disables configuration parameter checking that would

otherwise prevent the changes from being made.

3. Create a login in the master table by running the following commands:

16 Installing the Microsoft Application Agent

create asymmetric key ddbmaCLRExtensionKey from executable file = 'C:\Program Files \DPSAPPS\MSAPPAGENT\bin\DDBMASQLCLRLib.dll' go create login ddbmaCLRExtLogin from asymmetric key ddbmaCLRExtensionKey; go grant unsafe assembly to ddbmaCLRExtLogin; go

4. Run the following commands on the user database, in which you want to register or save the stored procedures:

CREATE ASSEMBLY ddbmaSQLCLR from 'C:\Program Files\DPSAPPS\MSAPPAGENT\bin \DDBMASQLCLRLib.dll' WITH PERMISSION_SET = UNSAFE; go CREATE PROCEDURE emc_run_backup @cmdText nvarchar(MAX) AS EXTERNAL NAME ddbmaSQLCLR. [ddbmaSQLCLRLib.DDBMASQL].RunBackup; go CREATE PROCEDURE emc_run_restore @cmdText nvarchar(MAX) AS EXTERNAL NAME ddbmaSQLCLR. [ddbmaSQLCLRLib.DDBMASQL].RunRestore; go CREATE PROCEDURE emc_run_delete @cmdText nvarchar(MAX) AS EXTERNAL NAME ddbmaSQLCLR. [ddbmaSQLCLRLib.DDBMASQL].RunDelete; go After you register or save the stored procedures in a user database, you must use this user database to run T-SQL procedures to perform backups and restores.

Changing the Microsoft application agent installation options

About this task

After installing the Microsoft application agent, you can change installation options at any time by rerunning the install wizard.

Steps

1. Double-click emcmsappagent-19.5.0.0.exe.

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

3. On the Configure Installation Options page, select the optional features that you want to install.

If you do not select features that were previously installed, they are removed.

4. Click Change.

Installing the Microsoft Application Agent 17

Upgrading the Microsoft Application Agent To upgrade the Microsoft application agent, use either the upgrade wizard or the command line interface (silent upgrade).

NOTE: You must install the same version of the Microsoft application agent on each node in a high-availability environment,

including Microsoft SQL Failover Cluster, Microsoft SQL Always On Availability Group, and Microsoft Exchange Database

Availability Group. During an upgrade of the software, ensure that no backups or restores are running on either the client or

each node in the high-availability environment.

Topics:

Upgrading the Microsoft application agent by using the upgrade wizard Upgrading the Microsoft application agent by using the command line interface (silent upgrade) Using the backup discovery tool for PowerProtect Data Manager management of existing backups

Upgrading the Microsoft application agent by using the upgrade wizard

NOTE: If Microsoft application agent version 4.7 or earlier is integrated with eCDM software, then instead of upgrading to

the latest version of Microsoft application agent, you must uninstall the earlier version and then install the latest version of

the software.

1. Download the msappagent195_win_x64.zip file to the Microsoft application agent host.

2. Open and extract the msappagent195_win_x64.zip file with WinZip.

3. To start the installation wizard, double-click emcmsappagent-19.5.0.0.exe. 4. On the Welcome Wizard page, select I agree to the license term and agreements, and then click Next. 5. On the Change Install Location page, click Upgrade. 6. On the Configure Installation Options page, select the optional installation features that you require.

If you had previously enabled PowerProtect integration, you are not required to specify the hostname or IP address of the PowerProtect server.

7. Click Upgrade.

CAUTION: If the Microsoft application agent that you are upgrading is integrated with PowerProtect,

immediately after the Microsoft application agent version 19.5 is installed, the PowerProtect administrator must

run auto-configuration for the Microsoft application agent protection policies. From the Protection Policies

page, select the policy for the upgraded Microsoft application agent, and then click SET LOCKBOX.

Upgrading the Microsoft application agent by using the command line interface (silent upgrade)

NOTE: If Microsoft application agent version 4.7 or earlier is integrated with eCDM software, then instead of upgrading to

the latest version of Microsoft application agent, you must uninstall the earlier version and then install the latest version of

the software.

To upgrade the Microsoft application agent silently, run one of the following commands:

emcmsappagent-19.5.0.0.exe -s -log " The command to either install or upgrade is the same, where -s performs silent installation or upgrade.

-log specifies the path, where the log file must be created or saved.

3

18 Upgrading the Microsoft Application Agent

NOTE: The log file displays the status of the installation. In the case of silent installation, you must use the -log option.

emcmsappagent-19.5.0.0.exe -s -upgrade -log The -upgrade option in this command indicates that you are performing an upgrade. The result of running this command is the same as the result of running the emcmsappagent.exe -s command.

-log specifies the path, where the log file must be created or saved.

NOTE: The log file displays the status of the installation. In the case of silent installation, you must use the -log option.

emcmsappagent-19.5.0.0.exe -s -upgrade InstallPPDMAgentCheckBox=1 PPDMHostname=" " The -upgrade option in this command indicates that you are performing an upgrade. This command performs the silent upgrade with the PowerProtect integration.

CAUTION: If the Microsoft application agent that you are upgrading is integrated with PowerProtect,

immediately after the Microsoft application agent version 19.5 is installed, the PowerProtect Administrator

must run auto-configuration for the Microsoft application agent protection policies. From the Protection

Policies page, select the policy for the upgraded Microsoft application agent, and then click SET LOCKBOX.

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 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 SQL 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 or 32-bit FCI instance

backups.

If you delete a SQL 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. By default, the PowerProtect Data Manager overrides the Data Domain details by

using the storage unit from the protection policy. If you do not want the Data Domain details to be overridden,

use the -a "SKIP_DD_OVERRIDE=TRUE" option in the backup scripts.

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

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

Upgrading the Microsoft Application Agent 19

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

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

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

To enable the backup discovery for an AAG or FCI, you must specify the appropriate client hostname:

If the host is part of an AAG, specify the Windows cluster name. If the host is part of a SQL virtual server or FCI, specify the virtual server name.

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

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

20 Upgrading the Microsoft Application Agent

Uninstalling the Microsoft Application Agent You can use the setup file, the Windows uninstall program, or the command prompt (silent uninstallation) to uninstall the Microsoft application agent.

Topics:

Uninstall the Microsoft application agent with the setup file Uninstalling the Microsoft application agent by using the Windows uninstall program Uninstalling the Microsoft application agent with the command prompt (silent uninstallation)

Uninstall the Microsoft application agent with the setup file

About this task

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

NOTE: If a table-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 table-level

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

unloaded prior to an uninstall operation.

Steps

1. Launch emcmsappagent-19.5.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 Removing the CLR assembly page:

a. Select the required SQL Server instances to remove the CLR Assembly.

By default, all the SQL Server instances are selected.

b. Select one of the following options to remove the CLR assembly:

Use Windows Authentication Use Database Authentication

c. In the User name and Password fields, type the credentials for the user who has the privileges to remove CLR assembly.

d. Click Remove. e. After the removal completes, click Next.

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

Uninstalling the Microsoft application agent by using the Windows uninstall program

About this task

To uninstall the Microsoft application agent by using the Windows uninstall program, perform the following steps.

NOTE: If a table-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 table-level

4

Uninstalling the Microsoft Application Agent 21

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

unloaded prior to an uninstall operation.

Steps

1. On the Windows desktop, click Start > Control Panel > Programs > Uninstall a program.

2. In the Uninstall or change a program window, perform one of the following steps:

Select Microsoft app agent, and then click Uninstall.

Double-click Microsoft app agent.

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

4. On the Removing the CLR assembly page:

a. Either select or clear the required SQL Server instances to remove the CLR Assembly. By default, all the SQL Server instances are selected.

b. Select either Use Windows Authentication or Use Database Authentication to remove CLR assembly. c. In the User name and Password fields respectively, type the username and the password of the user, who has the

privileges to remove CLR assembly. d. Click Remove. e. After the removal completes, click Next.

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

Uninstalling the Microsoft application agent with the command prompt (silent uninstallation)

NOTE: If a table-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 table-level

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

unloaded prior to an uninstall operation.

To uninstall the Microsoft application agent without any intervention, run the following command:

emcmsappagent-19.5.0.0.exe -uninstall -q UninstallADMAgent=1 -log " " where:

-q indicates silent uninstallation.

UninstallADMAgent=1 is compulsory for silent uninstallation. If this option is not added in the uninstall command, then the ADM agent will still exist after the Microsoft application agent is uninstalled.

-log specifies the path, where the log file must be created or saved. NOTE: The log file displays the status of the installation. In the case of silen

Manualsnet FAQs

If you want to find out how the 19.5 Dell works, you can view and download the Dell PowerProtect 19.5 Data Manager Installation Guide on the Manualsnet website.

Yes, we have the Installation Guide for Dell 19.5 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 Installation Guide should include all the details that are needed to use a Dell 19.5. Full manuals and user guide PDFs can be downloaded from Manualsnet.com.

The best way to navigate the Dell PowerProtect 19.5 Data Manager Installation 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.5 Data Manager Installation 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.5 Data Manager Installation 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.5 Data Manager Installation Guide, simply download the document to your computer. Once downloaded, open the PDF file and print the Dell PowerProtect 19.5 Data Manager Installation Guide as you would any other document. This can usually be achieved by clicking on “File” and then “Print” from the menu bar.