DPA SolVe 62SP3 Implementing Plain

EMC® Data Protection Advisor
Version 6.2 SP3
DPA Plain Implementation (Installing the

software)
Copyright © 2005-2016 EMC Corporation. All rights reserved. Published in the USA.
Published April, 2016
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with
respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a
particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC², EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other
countries. All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).
EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com
2 EMC Data Protection Advisor 6.2 SP3 DPA Plain Implementation (Installing the software)
CONTENTS
Preface 5
Chapter 1 Preparing to install DPA 9

Overview....................................................................................................... 10
System requirements.................................................................................... 10
DPA Server platforms....................................................................... 10
Datastore storage.............................................................................11
Permissions..................................................................................... 11
NTP time synchronization.................................................................11
Installation considerations............................................................................12
Configuring virtual infrastructure memory and CPU...........................12
OS resource optimization................................................................. 12
Communications settings in DPA...................................................................13
DPA port settings ..........................................................................................15
Installation and configuration overview......................................................... 18
Chapter 2 Installing DPA 25

DPA server installation.................................................................................. 26
Installing the Datastore Service........................................................26
Installing the Application Service..................................................... 27
DPA Agent installation...................................................................................29
Installing the DPA agent................................................................... 29
DPA postinstallation steps............................................................................ 30
dpa application support...................................................................33
Encryption of the DPA Application server.......................................... 33
Configuring antivirus software with DPA........................................... 35
Chapter 3 Administering DPA 37

Backup of the Datastore................................................................................ 38
Exporting the DPA Datastore to a file................................................ 38
Exporting the DPA Datastore to Pipe................................................. 38
Importing the DPA Datastore............................................................ 38
dpa datastore export..................................................................................... 39
dpa datastore import.....................................................................................39
dpa application adminpassword................................................................... 40
Running Data Domain DataProcessor ........................................................... 40
CLP and WLS license coexistence in DPA....................................................... 43
Chapter 4 Uninstalling DPA 45

Uninstalling the software...............................................................................46
Uninstalling by using silent command line....................................... 46
Uninstalling through user interface on Windows...............................46
Agent-only uninstallation.............................................................................. 46
EMC Data Protection Advisor 6.2 SP3 DPA Plain Implementation (Installing the software) 3
CONTENTS
Preface
As part of an effort to improve its product lines, EMC periodically releases revisions of its
software and hardware. Therefore, some functions described in this document might not
be supported by all versions of the software or hardware currently in use. The product
release notes provide the most up-to-date information on product features.
Contact your EMC technical support professional if a product does not function properly
or does not function as described in this document.
Note
This document was accurate at publication time. Go to EMC Online Support (https://
support.emc.com) to ensure that you are using the latest version of this document.
Purpose
This document provides information on how to install DPA and set up DPA to monitor a
data protection environment. This document also describes administrative functions
such as creating users and roles, updating system settings, creating policies, and
troubleshooting data collection.
The management system governing the design and development of this product is ISO
9001:2008 certified.
Audience
This document is intended for system administrators. Readers of this document must be
familiar with the following tasks:
l Identifying the different hardware and software components that make up the backup
and replication environment.
l Following procedures to configure backup and replication operations.
l Following guidelines to locate problems and implement solutions.
Revision history
The following table presents the revision history of this document.
Table 1 Revision history
Revision Date Description

01 April 29, 2016 First release of this document for EMC Data Protection
Advisor 6.2 SP3
Related documentation
The DPA documentation set includes the following publications:
l EMC Data Protection Advisor Custom Reporting Guide
l EMC Data Protection Advisor Data Collection Reference Guide
l EMC Data Protection Advisor Installation and Administration Guide
l EMC Data Protection Advisor Migrator Technical Notes
l EMC Data Protection Advisor online help system
l EMC Data Protection Advisor Product Guide
Preface
l EMC Data Protection Advisor Release Notes

l EMC Data Protection Advisor Report Reference Guide
l EMC Programmers' Guide to Using DPA REST API
l EMC Data Protection Advisor Software Compatibility Guide
l Other Technical Notes/White Papers
Special notice conventions used in this document
EMC uses the following conventions for special notices:
NOTICE
Addresses practices not related to personal injury.
Note
Presents information that is important, but not hazard-related.
Preface
Table 2 Style conventions
Bold Used for names of interface elements, such as names of buttons, fields,
tab names, and menu paths (what the user specifically selects or
clicks)
Italic Used for full titles of publications that are referenced in text
Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, file names, prompts, and syntax
l Commands and options
Monospace italic Used for variables

Monospace bold Used for user input
[] Square brackets enclose optional values
| Vertical bar indicates alternate selections - the bar means “or”
{} Braces enclose content that the user must specify, such as x or y or z
... Ellipses indicate non-essential information that is omitted from the

example
Where to get help

EMC support, product, and licensing information can be obtained as follows:
Product information
For documentation, release notes, software updates, or information about EMC products,
go to EMC Online Support at https://support.emc.com.
Technical support
Go to EMC Online Support and click Service Center. Several options for contacting EMC
Technical Support appear on the site. Note that to open a service request, you must have
a valid support agreement. Contact your EMC sales representative for details about
obtaining a valid support agreement or with questions about your account.
Online communities
Go to EMC Community Network at https://community.emc.com for peer contacts,
conversations, and content on product support and solutions. Interactively engage online
with customers, partners, and certified professionals for all EMC products.
Your comments
Your suggestions help to improve the accuracy, organization, and overall quality of the
user publications. Send your opinions of this document to
DPAD.Doc.Feedback@emc.com.
Preface
CHAPTER 1
Preparing to install DPA
This chapter includes the following sections:
l Overview............................................................................................................... 10
l System requirements............................................................................................ 10
l Installation considerations....................................................................................12
l Communications settings in DPA........................................................................... 13
l DPA port settings ..................................................................................................15
l Installation and configuration overview................................................................. 18
Preparing to install DPA 9

Overview
All of EMC® Data Protection Advisor (DPA) deployments include the following
installations:
l DPA Datastore server and a DPA agent on one host
l DPA Application server and a DPA agent on another host
When you install DPA, the installation wizard takes you step by step through placement
of these components.
Installing the Application and Datastore servers on a single host is not supported. You
can connect multiple Application servers to the same Datastore server, where each
additional Application server is on its own host and the Application servers are installed
as a DPA cluster. You can install additional DPA Agents for system monitoring and remote
data collection. The Data Protection Advisor Architecture Guide provides more information.
DPA supports Datastore Replication to enable continuous, safe, and reliable replication
so that DPA can maintain a replica copy, or Slave, of the primary Datastore, or Master, for
resilience against a single point of failure.
System requirements
DPA has the following basic minimum system requirements. The EMC Data Protection
Advisor Software Compatibility Guide provides a comprehensive list of system
requirements.
DPA Server platforms

DPA servers support for 64-bit operating systems only. Work with your EMC Account
Representative to determine appropriate sizing for your environment.
Hard Disk Drive requirements:
l 8GB RAM/2 cores for the DPA Datastore server
l 8GB RAM/2 cores for the DPA Application Server
Note
Co-located Application and Datastore systems are not supported in production

systems. Although the installer provides a co-located system option, when it is
selected, a dialogue stating that it is not supported in a production systems displays.
l 18GB of locally attached disk storage for the Application server
l 20GB of locally attached disk storage for the Datastore Server
l The DPA Application server and DPA Datastore servers must not be used to run other
applications. The DPA Application server host and DPA Datastore server host
resources must be dedicated to DPA.
l If running DPA in a virtualized environment the allocated CPU and memory must be
reserved for the DPA servers
l The DPA installer has a soft threshold of 7892 MB and a hard threshold of 5844 MB.
The soft threshold allows the installation to continue, but the hard threshold does
not.
l Automatic sizing and tuning of internal DPA resource usage takes place during
installation. If resources (CPU, Memory) are taken away from the installation by other
applications performance of DPA could be adversely affected.
l Operating systems:
n Support for 64-bit operating systems only
n Microsoft Windows Server 2008 R2, 2012, 2012 R2 (x64 only)
n Red Hat Linux ES/AS 5.5, 6.0, 6.2, 6.4 (64 bit), 6.5, 7, 7.1
Run the Update Agent (up2date) to ensure that the latest operating system
patches are installed
n SUSE Linux 11 x86 (64 bit)
Run the Update Agent (up2date) to ensure that the latest operating system patches
are installed
libaio is recommended to be installed on the system and available in the system
LD_LIBRARY_PATH for performance gains
Datastore storage
For performance reasons, the installation of the DPA Datastore server on NAS-based file
systems, such as CIFS or NFS shares is not recommended because these file systems
might not have the bandwidth to manage the required I/O.
Although the standard datastore file system layout is adequate for most deployments,
you can distribute different file systems across different file systems to optimize
performance during installation under Advanced installation options.
Permissions
Ensure that you have the following permissions before you install the software to avoid
installation failure:
l Windows:
n Administrator privileges (domain or local with full access)
n If User Account Control (UAC) is enabled, use Run As Administrator
l UNIX / Linux:
n Root user
n If using security software to manage access to the root account, ensure the
permissions allow the creation of new users after you become root. This must
include the ability to create default home directories for the account to be created.
NTP time synchronization

It is a best practice to have Network Time Protocol (NTP) available to synchronize the DPA
Server and the DPA Agent hosts. This ensures accurate and consistent data collection.
The DPA User Authentication process requires that the times on the system clock on the
client machine and on the server be synchronized within one minute of one another.
Datastore storage 11
Installation considerations
The DPA installation wizard presents advanced options for configuring Datastore
Replication with Master and Slave Datastores, and for configuring clustered Application
objects. If using either or both of these options, ensure that you:
l Plan the final deployment topology before beginning installation.
l Have all hosts and IP addresses predetermined and available.
If you are planning an advanced installation, contact your EMC Account Representative
for help with advanced architecture solution design.
Configuring virtual infrastructure memory and CPU

If you plan to deploy DPA in a virtualized infrastructure, perform the following steps:
Procedure
l Ensure that the memory allocated is reserved exclusively for each VM.
l Place the DPA Application and Datastore VMs in a resource pool where the resource
allocation shares are set to High. Alternatively, select High Share Allocation for each
individual VM.
l Select Thick Provision Eager Zeroed for Datastore disks. Thick Provision Eager Zeroed
disk allocation causes all space to be allocated upfront, and the full disk file is zeroed
before the system is made available for usage.
OS resource optimization
General tuning
During installation, the installer tunes the DPA Datastore Service for the host environment
on which it is being deployed. This tuning assumes that the host is dedicated to DPA and
takes into account resources such as Disk Space, Total Memory, and CPU cores. If during
the lifetime of the DPA Datastore Service any of these physical resources are increased or
decreased, execute the dpa datastore tune command on the Datastore host. dpa
datastore tune on page 12 provides more information.
dpa datastore tune

Configures tunable parameters of the datastore service for the available host memory
resources and database connections.
dpa datastore tune <size>MB|GB [options]

dpa ds tune <size>MB|GB [options]
Command options
--connections (-c) <connections> — Maximum number of concurrent Datastore
connections allowed
--help — Displays the help screen
--quiet — Suppresses all output except for warning and error messages
Hardware issues with tuning

For deployments where optimal performance is a concern, the type and quality of the
hardware you use for your Datastore host server drastically impacts the performance of
the Datastore Service.
Usually, the performance is better when you have more RAM and disk spindles in your
system. This is because with the extra RAM you will access your disks less. And the extra
spindles help spread the reads and writes over multiple disks to increase throughput and
to reduce drive head congestion.
For production purposes the DPA Application Service and the DPA Datastore Service
should be placed onto different hardware. Not only does this provide more hardware
dedicated to the Datastore Service, but the operating system's disk cache will contain
more Datastore data and not any other application or system data. The DPA Deployment
Architecture Guide provides guidelines to consider when commissioning hardware for your
Datastore host.
Communications settings in DPA

To ensure communication between the DPA Server and DPA Agents, configure the
firewalls in the network to allow communication on these ports, as shown in the following
figure. Additional firewall configuration can be required for other ports depending on
what you plan to monitor. For example, if you monitor Avamar, open port 5555 between
the Avamar server and the DPA Agent. "Environment discovery in DPA" provides more
information.
Communications settings in DPA 13

Figure 1 DPA 6.2 and minor releases ports and protocols
Note
*Application servers and Collectors can be one or many.
In the graphic above, the arrows show the initiation direction. The DPA Agent initiates
connection to DPA Application Server on 9002. For firewalls, it is based upon who
initiates the connection and on what port, and who is listening on the other side. DPA
Agent to DPA Application Server communication is on 9002 and 3741 TCP. The
communications are secure, encrypted, and compressed between the Agent and DPA
server.
The following tables detail the additional ports required on deployment hosts to allow
DPA to function correctly. The ports listed must be able to accept connections and allow
responses back on any established connection. Some network vendors describe such
handshaking communication as Bi-Directional; and such network security devices should
reflect this accordingly.
DPA port settings

The following tables provide the ports needed by DPA to function correctly. Additional
ports can be required for the DPA Agents depending on the systems being monitored. The
EMC Data Protection Advisor Installation and Administration Guide provides information on
installation requirements.
Table 3 DPA Application ports settings
Port Description Traffic direction
25 TCP port used for the SMTP service Outbound connection to SMTP
server.
80 TCP port used for the SharePoint service Outbound connection to

SharePoint server.
161 UDP port used for SNMP service Outbound connection to

SNMP devices.
389/636 (over TCP port used for LDAP integration Outbound connection to LDAP
SSL) server.
3741 TCP port used for DPA Agents communications. Outbound connection to DPA
agents
4447 TCP port used for intra-service communication Inbound connection
4712 TCP port used for intra-service communication Localhost connection
9002 TCP port used for the HTTPS service. Inbound connection over SSL
from UI, CLI and REST API
clients.
9003 TCP port used for DPA Datastore Outbound connection to DPA
communications. Datastore.
9004 TCP port used for the HTTP service. Inbound connection from UI,
CLI and REST API clients.
9005 TCP port used for Jboss Management Localhost connection
Table 4 DPA Datastore port settings
3741 TCP port used for DPA Agents communications. Inbound connection from DPA
Application server.
DPA port settings 15

Table 4 DPA Datastore port settings (continued)
9002 TCP port used for the HTTPS service. Outbound connection over SSL to DPA
Application server.
9003 TCP port used for DPA Datastore Inbound connection from DPA
communications. Application server.
Table 5 DPA Agent port settings
3741 TCP port used for DPA Agents Inbound connection from DPA Application
communications. server.
9002 TCP port used for the HTTPS service. Outbound connection over SSL to DPA
Application server.
Table 6 DPA cluster port settings
25 TCP port used for the SMTP service Outbound connection to SMTP
server.
80 TCP port used for the SharePoint service Outbound connection to

SharePoint server.
161 UDP port used for SNMP service Outbound connection to SNMP
devices.
389/636 (over TCP port used for LDAP integration Outbound connection to LDAP
SSL) server.
3741 TCP port used for DPA Agents Outbound connection to DPA
communications. agents
4447 TCP port used for intra-service Inbound connection

communication
4712 TCP port used for intra-service Localhost connection

communication

communication
5445 TCP port used for intra-service Bidirectional connection for

communication Cluster
5455 TCP port used for intra-service Bidirectional connection for

communication Cluster
7500 Multicast over UDP Bidirectional connection for

Cluster
7600 Multicast over TCP Inbound connection for Cluster

communication
Table 6 DPA cluster port settings (continued)
9002 TCP port used for the HTTPS service. Inbound connection over SSL from
UI, CLI and REST API clients.
9003 TCP port used for DPA Datastore Outbound connection to DPA
communications. Datastore.
9004 TCP port used for the HTTP service. Inbound connection from UI, CLI
and REST API clients.
9876 Multicast over TCP Bidirectional connection for

Cluster

Cluster

Cluster

Cluster

Cluster

Cluster

Cluster

Cluster

Cluster

Cluster
DPA port settings 17

Installation and configuration overview

The DPA installation workflow provides a high-level workflow of tasks for installing DPA
with various configurations.
Figure 2 DPA installation workflow
The Installation and configuration overview lists the tasks you need to perform for
installing DPA and configuring data monitoring.
Table 7 Installation and configuration overview
Action Comments
Set up host computer
Provide at least two hosts DPA must not be installed on servers already running other
for DPA server installation: applications. For installation in a production environment, you need
One for the initial DPA one host for the Application Service and a separate host for the
Application server, and Datastore Service. EMC recommends that you use a dedicated server
one for the Datastore. with at least 2GB of temporary space. The EMC Data Protection Advisor
Software Compatibility Guide provides more information.
A separate host is
required for the Datastore
and Application server so
that the operating system
on each server can
successfully and properly
manage the IO
Table 7 Installation and configuration overview (continued)
Action Comments
performance needs of one
service and the RAM and
caching requirements of
the other service, without
the two services
competing with each other
for resources.
Provide a host for DPA Review the DPA Deployment Architecture Guide, available on EMC
Agent installation Online Support DPA documentation section, for guidelines on how to
(optional). determine number and location of Agents to be deployed.
If the DPA server is running on Windows and the discovered host(s)
are also Windows, you need not install an Agent on the discovered
host. However, we recommend that you use the Agent installed on
the DPA Server hosts for DPA Server monitoring only.
If the DPA server resides on a Linux host and you are performing
client discovery of Windows hosts, at least one DPA agent must be
installed on a Windows Agent.
Ensure that DPA and all its Occasionally DPA components are shut down or associated files are
components are quarantined by antivirus software if not defined as exceptions.
configured as exceptions
in any antivirus software.
Provision networking l Allocate a dedicated VLAN for use by the DPA Application
infrastructure and a servers. If a dedicated VLAN is not available, ask your network
shared directory if administrator for a UDP Multicast group address that can be
installing multiple used for the DPA cluster.
Application servers (DPA
clustering).
l To increase resiliency and quality of service, provision a
hardware load-balancing switch as a gateway to the DPA
Application servers.
l Configure a shared directory that will be accessible by all
Application Servers. DPA will use this shared directory for writing
scheduled reports and other temporary files that all Application
Servers need to access.
Check VMware or Hyper-V DPA has been certified to work on a Linux or Windows virtual
requirements. machine in a VMware or Hyper-V environment. The EMC Data
Protection Advisor Software Compatibility Guide provides more
information.
Configure virtual Configuring virtual infrastructure memory and CPU on page 12

infrastructure memory and provides more information.
CPU
Open or disable firewalls If you want to use secure communication for connecting to the
for communciation Application server on port 9002, ensure that TLS (Transport Layer
between the DPA servers. Security) settings are enabled for secure communication in your
browser settings.
When installing on DPA Servers, the operating system/software–
based firewalls can be disabled or have ports opened for
Installation and configuration overview 19

Action Comments
communication between the DPA Application server, the DPA
Datastore server, and the DPA Agents prior to installing the DPA
components.
Typically, the network in which the DPA servers and DPA Agents
reside are secure and behind a network firewall. This means that you
could choose to disable operating system/software based firewalls.
If you choose to leave the operating system/software based in effect,
you must open/unblock the required ports. Communications settings
in DPA on page 13 provides information.
If on Linux and you choose to disable the firewall, run the following
commands to disable and ensure that the firewall remains disabled
after startup or reboot:
l Run iptables stop.
l Set the chkconfig utility to iptables off.
Install the host operating The EMC Data Protection Advisor Software Compatibility Guide lists the
system on the DPA required architectures and patches.
Server(s) and Agent host
and install all required
patches.
Install all required When monitoring applications or devices remotely, you may need to
software on the agent host install additional software on the Agent host. For example, the EMC
after the DPA 6.2 and NetWorker client must be installed on the Agent host if the Agent will
minor releases be used to monitor EMC NetWorker remotely.
Application Server is
ready.
If DNS is not enabled in DPA and SharePoint integration requires the IP address and FQDN to
the environment, add the enable you to publish reports to SharePoint and to configure the
IP address and FQDN of SharePoint port. The SharePoint port is configurable. The default
the SharePoint server on port, if no port is specified, is 80. You can set the port by using a
the DPA Application standard URL in the existing URL field in the SharePoint settings
server’s hosts file. dialog.
If you are going to use You need the following information for LDAP User Authentication
LDAP User Authentication configuration:
on your DPA server, gather
l LDAP Server Name/IP
the information needed
for configuration l Use SSL?
l LDAP Server Port
l LDAP Version
l Distinguished Name of Base Directory
l Identification Attribute
Download and save the To download the DPA Server, Agent, and Data Domain DataProcessor
DPA binaries tool binaries, go to the DPA downloads section of http://
support.emc.com.
Action Comments
Save the DPA Server and Agent binaries locally.
Save the Data Domain DataProcessor binaries according to the
specifications provided in Running Data Domain DataProcessor on
page 40.
Obtain and save DPA Licenses
Save the required license You must know the IP address of the primary Datastore server.
files on your local
For more information on obtaining DPA licenses or types of DPA
machine for easy access
licenses available and required, contact your EMC Account
during installation. The
Representative.
DPA installation wizard
prompts you to browse for
the license file at license
installation.
l For new non-migrated A DPA license is required to administer DPA after installation.
installations - Obtain DPA is bundled with a 60-day evaluation license. The evaluation
DPA licenses for all license is created from the time of DPA installation, is valid for up to
components that will 60 days, and allows access to all features. If you import a license
be monitored. during 60-day evaluation license period, the evaluation license is
l For migrated 5.x removed and you have access to DPA features according to license
installations - Existing you imported.
licenses will be For information on required DPA licenses or on purchasing licenses
migrated. for your DPA installation, contact your EMC sales representative.
l The CLP license is
required for new 6.2
and minor releases
functionality and
increased capacity on
a DPA instance. If you
are not adding
capacity or changing
to new 6.2 and minor
releases functionality,
import of CLP licenses
is not required. If you
are migrating from
DPA version 5.x to
version 6.2 and minor
releases, the existing
licenses are migrated
with your
configuration and
data. When not
increasing capacity or
changing functionality
on existing WLS
licenses, WLS
licenses can only
coexist with CLP

Action Comments
license types if they

are imported before
CLP licenses. CLP and
WLS license
coexistence in DPA on
page 43 provides
more information.
Provide the Solutions l A minimum of one gatekeeper per HBA per Symmetrix is
Enabler (SE) licenses. required.
l One Solutions Enabler host can discover all VNX/CLARiiON
arrays through IP address. For VNX/CLARiiON discovery, EMC
recommends installing Solutions Enabler on the DPA server.
l The EMC Data Protection Advisor Software Compatibility Guide
describes the versions of Solutions Enabler required for storage
array discovery.
Install DPA
Install the DPA software. Install the DPA server and agent according to the installation
instructions. Installing the Datastore Service on page 26, Installing
the Application Service on page 27, and Installing the DPA
agent on page 29provide more information.
Configure EMC host array discovery and Solutions Enabler hosts
Configure Symmetrix and The steps in this section apply only if you are monitoring a storage
VNX/CLARiiON array for array, database, or Microsoft Exchange Server for replication analysis.
discovery
Provide the Solutions The EMC Data Protection Advisor Software Compatibility Guide
Enabler host used to describes the versions of Solutions Enabler required for storage array
discover Symmetrix or discovery, and the software that must be installed on the Solutions
VNX/CLARiiON storage Enabler host. The host must be able to connect to the Symmetrix
arrays. array by a SAN connection. The host must have the TCP port 443 or
2163 enabled for the VNX/CLARiiON connection.
Configure the environment for data protection monitoring
Ensure that the required Communications settings in DPA on page 13 lists the protocols and
ports between the DPA default DPA ports required for communication between the agent and
Agent host and the the monitored device or server.
monitored server or
devices are open and
communication is
possible over the
protocol.
Ensure that the DPA Permissions on page 11 lists the default settings for the DPA
credential used to connect credentials that are installed with DPA.
to the monitored device or
server is sufficient, or
Action Comments
have the new credential
details ready.
Set up monitoring of
RecoverPoint (if
applicable).
Discover and configure l If a remote agent is being used to import hosts, the DPA server
Application Host import (if must be able to resolve the agent host.
monitoring Microsoft
Exchange or a database).
Define the data protection policies
Prepare the details of the For replication analysis, the Data protection policy details consist of:
policies that DPA will
l The type or replication, (SRDF/S, SRDF/A, MirrorView,
monitor for compliance.
RecoverPoint, and so forth).
l Whether the replication is Point-in-Time or continuous.
l The replication target destination.
For data protection reporting, the policies are:
l Chargeback Policies - For financial cost analysis of data
protection operations.
l Protection Policies - To analyze compliance with recovery time
objective (RTO) and recovery point objective (RPO) data
protection targets.

CHAPTER 2
Installing DPA
l DPA server installation.......................................................................................... 26

l DPA Agent installation...........................................................................................29
l DPA postinstallation steps.................................................................................... 30
Installing DPA 25
Installing DPA
DPA server installation

The DPA server installation involves two stages:
1. Installing the Datastore service
2. Installing the Application service
Installation of the Application service before the Datastore service results in failure of
Application service installation.
The procedures in this section are applicable to new installations. The DPA Release
Notes provides information on supported upgrades.
The DPA installer runs on Windows and Linux, provided that your Linux installation
supports running a UI. The following procedures describe installation in a Windows 64-bit
environment.
Installing the Datastore Service

This procedure includes implementation for a normal Datastore installation without
clustering and Datastore Replication.
Before you begin
l Ensure that you log in as a local administrator or a Domain administrator with full
local access.
l If UAC is enabled on a Windows host, start the installer by Run as Administrator.
l Copy the installation binary to the server or to your local machine.
l If installing on UNIX/Linux, ensure that you are logged in as root. You could
experience problems with the Datastore server if you install after becoming root
through certain SU-type security software; for example, using the sesu command.
l Ensure that ports are opened or disabled for communication between the DPA
servers. Installation and configuration overview on page 18 provides information.
l Ensure that you have the IP Address of the Application server for the Agent to
communicate with. If installing on Linux IPv6, ensure that you also have the IPv6
Interface ID of the Datastore server. You are prompted for this in the Configure Agent
window of the Datastore installation. To get the IPv6 Interface ID, run the ip addr
show command on the Linux Agent machine and use the output to find the IPv6
Interface ID. For example:
fe80::9c9b:36f:2ab:d7a2%2
Where the values before the % refer to the IPv6 of the Application server (in this
example, fe80::9c9b:36f:2ab:d7a2) and those after refer to the interface Id (in
this example, 2).
Procedure
1. Double-click the DPA server binary to start the installation.
Installing DPA
2. Click Next.
3. Read and accept End User License Agreement. Scroll to the end of the agreement to
activate the option to accept the terms of the License Agreement. Click Next.
4. In the Installation Options screen, select to install Datastore service, click Next.
5. If you do not perform an advanced installation, click Next and follow the installation
wizard.
To perform an advanced installation, select the Show Advanced Installation Options
checkbox in the Advanced Installation screen, click Next, and follow the installation
wizard.
The Advanced Options are:
l Do not register DPA services: Prevent the registration of the Datastore service with
the operating system manager. This will prevent the Datastore service from being
started after host reboot. You must use the DPA Command Line Interface to install
the service with the operating system.
l Do not start DPA services: Prevent the starting of the Datastore services after
installation. Use of the DPA Command Line Interface will be required to start the
service.
l Install with advanced datastore layout: Configure the Datastore service with the
required filesystems distributed across different disks to optimize performance.
6. When prompted, choose the installation folder.
Choose the default location or browse to another folder location.
7. Review the Pre-Installation Summary, the disk space information in particular, click
Install.
The installation proceeds.
If there is not enough disk space, cancel the installation or choose a different drive on
which to install DPA.
8. When prompted, select the IP addresses that the Datastore should listen on for
connections from the DPA Application Server(s).
9. When prompted, enter the IP address of the DPA Application Server that will use the
Datastore from step 8 and then click Add and Next.
10. When the DPA Datastore Server installation is complete, click Done.
Installing the Application Service

This procedure includes implementation for a normal Application service installation
without clustering and Datastore Replication.
Before you begin
l Copy the installation binary to the server or to your local machine.

l Ensure that the Datastore service option is checked, and that the Datastore service is
running.
l If installing with Advanced Options on Linux IPv6, and the Agent wants to talk to a
different application server or a Load Balancer, for example, in case of a cluster,
ensure that you have the IP Address of the Application server for the Agent to
communicate with. You are prompted for this in the Configure Agent window of the
Installing the Application Service 27

Installing DPA
Application server installation. To get the IPv6 Interface ID, run the ip addr show
command on the Application server and use the output to find the IPv6 Interface ID.
For example:
fe80::9c9b:36f:2ab:d7a2%2
Where the values before the % refer to the IPv6 of the Application server or the load
balancer to which the Agent wants to connect (in this example, fe80::9c9b:36f:
2ab:d7a2) and those after refer to the interface ID of the current Application server
(in this example, 2).
l If you are planning on using ESRS-VE for remote troubleshooting (recommended),
ensure that you have the ESRS-VE environment installed and configured before DPA
installation. The EMC Secure Remote Services landing page at https://
support.emc.com/downloads/37716_EMC-Secure-Remote-Services-Virtual-Edition
on EMC Online Support provides more information on ESRS-VE installations.
The Application service installation process is similar to installing the Datastore service.
Procedure
1. Double-click the DPA server binary to start the installation.
2. Click Next.
3. Read and accept End User License Agreement. Scroll to the end of the agreement to
enable the option to accept the terms of the License Agreement. Click Next.
4. In the Installation Options screen, select to install Application service, click Next.
5. If you do not perform an advanced installation, click Next and follow the installation
wizard.
The Advanced Options are:
l Do not register DPA services: Prevents the registration of the service with the
operating system service manager. This option prevents the DPA services from
being started after a host reboot.
l Do not start DPA services: Prevents the DPA services from being started after
installation. Use of the DPA command line interface is required to start the service.
l Install the DPA services as clusterable: Configures the DPA service to discover and
join any present DPA cluster.
The rest of the installation is similar to the Datastore installation.
6. Review the Pre-Installation Summary, the disk space information in particular, click
Install. The installation proceeds.
If there is not enough disk space, cancel the installation or choose a different drive to
install DPA on.
Note
A datastore connection failure error might occur if the relevant firewalls required to
communicate between Application Server and the Datastore are not open.
Communications settings in DPA on page 13 provides information.
7. In the Connect to Remote DPA Datastore step, enter the IP address for the DPA
Datastore server previously installed.
The installation resumes.
Installing DPA
8. When prompted, specify the name or IP address of the DPA Application server host
with which the DPA Agent will communicate. By default the Agent communicates with
the local Application server with IP address 127.0.0.1. In a clustered configuration
provide the IP address of the load balancing switch placed in front of the Application
servers. Click Next.
The DPA Application service installation is now complete.
9. Set the Administrator password.

Note the following regarding Administrator password:
l Blank passwords are not supported.
l There is no character minimum; the character maximum is 255.
l The dpa app adminpassword command can be used to reset the DPA
Administrator's password and enable the DPA Administrator account when the
DPA Datastore service is up and running. dpa application adminpassword on page
40 provides more information.
10. Click Done.

After the installation is complete, start the DPA Server and license the Server. DPA
postinstallation steps on page 30 provides more information.
DPA Agent installation

This section describes how to install the DPA Agent using the agent-only installation
package. It is applicable to new installations.
An Agent is automatically installed on the DPA Application and Datastore servers.
Therefore do not run this procedure on the DPA servers.
Installing the DPA agent

The following procedure explains installing the DPA Agent in a Windows environment.
Before you begin
l Review the DPA Deployment Architecture Guide, available on EMC Online Support DPA
documentation section, for guidelines on how to determine number and location of
Agents to be deployed.
l Ensure that you have the IP Address of the DPA Application server for the Agent to
communicate with. If installing on Linux IPv6, ensure that you also have the IPv6
Interface ID of the Agent. You are prompted for this in the Configure Agent window of
the Agent installation. To get the IPv6 Interface ID, run the ip addr show command
on the Linux Agent machine and use the output to find the IPv6 Interface ID. For
example:
fe80::9c9b:36f:2ab:d7a2%2
Where the values before the % refer to the IPv6 of the DPA Application server (in this
example, fe80::9c9b:36f:2ab:d7a2) and those after refer to the interface ID of
the Agent (in this example, 2).
DPA Agent installation 29

Installing DPA
Procedure
1. Double-click the DPA Agent binary to start the installation.
2. Click Next.
3. Read and accept End User License Agreement. Click Next.
4. Choose an installation folder and click Next.
5. Verify the Pre-Installation Summary and click Install.
6. Choose the Agent installation options:
l Do not start DPA Agent service - this option prevents starting of the DPA Agent
service after installation.
If you select this option, you must manually start the DPA Agent from the command
line.
If you select Do not start DPA Agent service, click Next.
Type the fully qualified domain name or the IP address of the DPA Server that
communicates with the DPA Agent.
l Agent will be used to monitor Oracle Database: Select this option to monitor an
Oracle database with the DPA Agent.
If you select this option, browse to the directory where the the DPA Agent can find
the Oracle Database device driver files.
7. Click Next.
8. In the Configure Agent window, enter the fully qualified domain name or the IP
address of the DPA Application Server that communicates with the DPA Agent.
If you are installing on Linux IPv6 and are installing Linux Agents, enter the IPv6
Interface ID of the Linux Agent.
Click Next.
9. Click Done to complete the installation.
DPA postinstallation steps

After you install or upgrade DPA and access the DPA web console, a message is displayed
that indicates the DPA Server the status of the initialization process. The initialization
process can take approximately 10 minutes to complete.
During the initialization time, DPA is creating the database schemas, tables, views, and
the DPA Datastore. It also creates the various system reports and dashboards templates,
the default system users, Analysis Engine Rulesets, and various other default and initial
objects. Your network connection time affects the speed at which all these actions
complete. Ensure that you perform the following steps after installing DPA.
Procedure
1. If you have upgraded or migrated to 6.2 SP3, delete the browsing history/cache in
your browser before using 6.2 SP3.
2. (Optional) Carry out the following steps to verify whether initialization is still in
progress or completed:
a. If you installed on Linux and the install is done to a non-default location, log out
and back in to the session. Alternatively, run from a new login window.
A new shell is required for the executive command paths to be found before
running dpa.sh svc status.
Installing DPA
b. On the DPA Application server, go to <install_dir>\services\applications.

c. Check the *.rar ; *.ear, and *.war files for *.deployed, *.isdeploying, or .failed
extensions.
l If files have an extension of *.isdeploying, then server initialization is still in
progress.
l If files have an extension of *.deployed, then server initialization is complete
and you can login to the DPA web console.
l If files have an extension of *.failed, then server initialization failed; contact
EMC Technical Support.
3. Start the web console to verify successful DPA installation.

All DPA services must be running when you launch the web console. The Adobe Flash
plugin in your web browser is required to launch the web console.
a. Start a browser and connect to DPA Server over https on port 9002. Ensure that all
pop-up blockers are disabled. For example:
https://<server_name>:9002
where <server_name> is the name or IP address of the server or localhost.
b. Type the username and password. Username and password fields are case-
sensitive.
c. Click Login
4. Add licenses to the DPA server.
The DPA server is installed with a 60-day temporary license.
If you are upgrading and you are not adding capacity or changing to new 6.2 SP3
functionality, no licensing changes are needed.
The CLP license is required for new 6.2 SP3 functionality and increased capacity on a
DPA instance. If you are not adding capacity or changing to new 6.2 SP3 functionality,
import of CLP licenses is not required. If you are migrating from DPA version 5.x to
version 6.2 SP3, the existing licenses are migrated with your configuration and data.
CLP and WLS license coexistence in DPA on page 43 provides more information.
If you are adding CLP licenses, ensure that you select license files with the .lic file
extension.
If you are adding WLS licenses, select license files with the .wls file extension.
After you install the license file, the DPA web console prompts you to close so it can
register the license file.
5. Log back in to the DPA web console.
6. (Recommended) If you added CLP licenses in step 4, register the DPA Application
server with the ESRS-VE. This registration process enables EMC Customer Support to
service the DPA instance.
Observe the following:
l If you are upgrading a previously registered ESRS, it is possible that ESRS will
show that it is already registered with the following error:
[ERROR] This node is already registered with an EMC Secure
Remote Support Service.
DPA postinstallation steps 31

Installing DPA
Then, ESRS shows that host IP is not available anymore with the following errors:
[ERROR] This node failed to delete with EMC Secure Remote
Support Service.
Offline: Validation error
Search EMC Knowledgebase article xxxxxx, available on http://
www.support.emc.com, for more information. This is an environment issue not
related to DPA.
l Registering ESRS after a fresh installation requires that an ESRS-VE be already
installed and reachable from the DPA Application server. If you are planning on
using ESRS-VE for remote troubleshooting (recommended), ensure that you have
the ESRS-VE environment installed and configured before DPA installation. The
EMC Secure Remote Services landing page at https://support.emc.com/
downloads/37716_EMC-Secure-Remote-Services-Virtual-Edition on EMC Online
Support provides more information on ESRS-VE installations. The EMC Data
Protection Advisor Software Compatibility Guide provides supported ESRS-VE module
and version information.
l Register a single Application service. The registration includes both DPA Datastore
and Application servers.
l If you are working in a clustered environment, register the Master Application
server with ESRS. Use the dpa app con command to check if your Application
server is Master or Slave server. The CLI section provides more information.
l When prompted for EMC Secure Remote Support username and password, provide
EMC online support credentials for registration. For example:
dpa app support --register 10.11.110.111

EMC Data Protection Advisor
Enter DPA Administrator username :
Enter DPA Administrator password :
Enter EMC Secure Remote Support username :
Enter EMC Secure Remote Support password :
l Note the following: In a clustered environment, do not use the Application server
registered with ESRS for scheduled reports. Any problems with the scheduled
reports or data collection on the listener are propagated across the Application
servers in the cluster.
a. Log in to the Application server using Remote Desktop Connection for Windows or
PuTTY for Linux.
b. Type the dpa app support --register ESRS_IP command to register a
DPA server.
Where ESRS_IP is the IP address of the ESRS Gateway. For example:
C:\Program Files\EMC\DPA\services\bin>dpa app support --

register 10.11.110.111
c. When prompted, type the EMC Secure Remote Support username and password.
Output appears that indicates that the request to register the DPA server with IP
address that you typed is approved and the command is successful.
7. (Optional) If you want to configure alerting on Replication Monitoring, ensure that you
create Recoverabilty rules to the Analysis Policy and assign the rules to the desired
object. Go to Policies > Analysis Policies
8. (Optional) If you have upgraded from 6.2 SP1 or 6.2 SP2 and you would like to display
the Data Domain Overview dashboard and the Data Domain Details dashboard:
Installing DPA
a. Go to Dashboard > + icon > Open Existing Dashboard.

The Open Existing Dashboard window appears.
b. Select Data Domain and Click OK.
9. (Optional) If you are monitoring a Data Domain OS 5.7 and later and would like to
ensure configuration of Physical Capacity Reporting data collection:
a. Manually assign the request to any Data Domain OS 5.7 boxes.
b. Run the request so that the statistics are gathered on the Data Domain and the
schedule is created. Then, when you are ready to run the first report, data is
returned.
10. If you have upgraded to 6.2 SP3 and you are running the Data Domain DataProcessor,
go to dpa schema and delete all records in the ddup_status and dd_analysis tables
before you run the client aggregation and file age commands.
dpa application support

Configures the DPA Application server with EMC Secure Remote Support (ESRS) Gateway.
If you are planning on using ESRS-VE for remote troubleshooting (recommended), ensure
that you have the ESRS-VE environment installed and configured before DPA installation.
The EMC Secure Remote Services landing page at https://support.emc.com/downloads/
37716_EMC-Secure-Remote-Services-Virtual-Edition on EMC Online Support provides
more information on ESRS-VE installations. .
dpa application support [options]
dpa app support [options]
Command options
--register (-r) <ESRS_IP address> — Registers the DPA Application with ESRS gateway
--update (-u) <DPA_new_IP address> — Updates the ESRS gateway with a new DPA server
IP address
--deregister (-d) — Unregisters the DPA Application server from ESRS gateway
--ping (-p) <ESRS_IP address> — Pings to obtain the DPA Application server/node
information
--help (-h) — Displays the help screen
Example
C:\Program Files\EMC\DPA\services\bin>dpa app support --register
10.11.110.111
Encryption of the DPA Application server

To encrypt the information flowing between the Application server and the DPA web
console, you must install a certificate on the Application server.
Encrypting the DPA Datastore server

To encrypt the information that flows between the DPA Datastore and Application server,
you must install a certificate on the Datastore server. You can use DPA to generate and
install a self-signed certificate, or you can request a Trusted Certificate from Certificate
Authority (CA) and install the Trusted Certificate on the Datastore. Using the DPA self-
dpa application support 33

Installing DPA
signed certificate to encrypt Datastore server on page 34 and Using a Trusted Certificate
from a CA to encrypt the Datastore server on page 34 provide more information.
Using the DPA self-signed certificate to encrypt Datastore server

l (Prerequisites) Ensure that all Datastore and Application services are stopped.
l If you are implementing Application server clustering, ensure that you complete all
cluster configuration before enabling encryption on the Datastore and Applicaiton
servers.
Procedure
1. On the Datastore server, use the dpa ds inscert command to generate and
install a newly generated self-signed certificate. Output indicates that SSL is enabled.
The dpa ds inscert command generates two files and stores them in the
<services>/datastore/data directory:
l server.key
l server.crt
2. Save the self-signed certificate to the same location on the Application server that has
been saved on the Datastore server.
By default, the certificate is saved to the following location on the Datastore server:
l On UNIX: /opt/emc/dpa/services/datastore/data/
l On Windows: C:\Program Files\EMC\DPA\services\datastore\data

\server
3. Run the dpa app condscert command to install the self-signed certificate on the
Application server. Ensure that you specify the path where the certificate was saved in
step 2 of this procedure. For example:
dpa app condscert /opt/emc/dpa/services/datastore/data/
4. Start the Datastore and Application services.
Using a Trusted Certificate from a CA to encrypt the Datastore server

l (Prerequisites) Ensure that you have requested and obtained a Trusted Certificate for
the Datastore server from a CA. The DPA Software Compatibility Guide provides
information on supported CAs.
l Ensure that all Datastore and Application services are stopped.
Procedure
1. On the Datastore server, use the dpa ds inscert command with the certificate
name and location and keyfile parameters. For example:
dpa ds inscert C:\SSL\RSA-CombinedCertChainMachinename.cer C:\SSL
\apollossl.key
Ensure that you include the filename and path of your Trusted Certificate and key; in
the example, this is C:\SSL\apollossl.key.
2. Save the Trusted Certificate to the same location on the Application server that is has
been saved on the Datastore server.
Installing DPA
3. Run the dpa app condscert command to install the Trusted Certificate on the
the Application server. Ensure that you specify the path where to which the certificate
was saved in step 1 of this procedure. For example:
dpa app condscert C:\SSL\RSA-CombinedCertChainMachinename.cer. If no
certificate file and key file location are specified in the command line, DPA generates
its own certificates. It creates the certificate and key and puts them in the data folder.
4. Restart the DPA Datastore and Application services.
Encrypting the DPA Application server

Out of the box, the information that flows between the DPA Application server and the
DPA web console is encrypted using the self-signed certificate that is included with the
DPA Application server. You can also install your own certificates on the Application
server. This procedure uses a Trusted Certificate with a private key inside a keystore file.
Before you begin:
l Ensure that you have requested and obtained a Trusted Certificate and private key for
the Application server from a CA. The DPA Software Compatibility Guide provides
information on supported CAs.
l Ensure that you have merged the Trusted Certificate and the private key inside a
keystore file. Refer to CA vendor documentation for information.
l If you are implementing Application server clustering, ensure that you complete all
cluster configuration before enabling encryption on the Datastore and Application
servers.
Procedure
1. Use the dpa app impcert -kf command to import the self-signed certificate:
dpa app impcert -kf "C:\work\new.keystore" -al newkey -pw password
2. Restart the DPA Application service. The dpa app --help command provides
additional information.
3. (Optional) Install the certificate in those browsers that you use to access DPA. Follow
the instructions of your chosen browser.
It may take a few minutes on initial connection to open DPA when using a secure
connection.
Configuring antivirus software with DPA

Configure the following antivirus configuration. Refer to your particular antivirus software
documentation for information on how to configure the software so that there is no real-
time monitoring of these processes or monitoring of the files that they read.
It is not necessary to have all DPA file systems monitored by antivirus software, and
scanning certain file systems and processes can potentially degrade overall performance
due to the impact of increased disk IO activity.
Procedure
1. Exclude the following files and processes from antivirus monitoring.
If you are configuring antivirus software on Linux, the following file names will not
have a .exe extension.
l DPA Application Server:
Configuring antivirus software with DPA 35

Installing DPA
n <install_dir>services\executive\wrapper.exe
n <install_dir>\agent\bin\dpaagent.exe
n <install_dir>\services\_jre\bin\java.exe
l DPA Datastore Server:
n <install_dir>\services\datastore\engine\bin\postgres.exe
n <install_dir>\agent\bin\dpaagent.exe
2. Exclude the following specific directories form being monitored by your antivirus
software.
l DPA Application Server:
n <install_dir>\services\standalone\**
n <install_dir>\services\tmp\**
n <install_dir>\services\shared\**
l File space on the DPA Datastore Server:
Note
If you selected advanced file system layout during Datastore installation, then
alternative directories may be used instead of the following defaults.
n <install_dir>\services\datastore\data\**
n <install_dir>\services\datastore\data\pg_log\**
CHAPTER 3
Administering DPA
l Backup of the Datastore........................................................................................ 38

l dpa datastore export............................................................................................. 39
l dpa datastore import.............................................................................................39
l dpa application adminpassword........................................................................... 40
l Running Data Domain DataProcessor ....................................................................40
l CLP and WLS license coexistence in DPA............................................................... 43
Administering DPA 37
Administering DPA
Backup of the Datastore

It is a best practice to back up the DPA Datastore regularly and particularly prior to
making any major change to DPA such as upgrading to a newer version or migrating to
new hardware. An export of the Datastore contents is part of an overall backup of the DPA
instance.
Exporting and importing a DPA Datastore is supported only on the same version of the
DPA Datastore.
Exporting the DPA Datastore to a file

With this export command, a complete and consistent copy of the Datastore is exported
to the local file system, in a location that can optionally be specified.
The default filename of the export is: datastore-<version> <date and time>.
For example, datastore-6_2_0_90597-2014-10-01-1135.
Type the following command from a command line prompt. dpa datastore export
[options]
The exported Datastore file is saved to the same directory where the export command
was run.
To save the exported Datastore file to a specific directory, specify the location at the end
of the command line. For example, the following command line exports the file to C:\
because that is the location specified: C:\Program Files\EMC\DPA\services
\bin>dpa datastore export C:\
Exporting the DPA Datastore to Pipe

With this export format, a complete and consistent copy of the Datastore is streamed to a
named pipe from a location where a Backup Manager can read the contents.
Type the following command from a command line prompt. dpa datastore export --
pipeline
For example, dpa datastore export --pipeline /mydir/mypipe

DPA supports backup up to Avamar using the ds export command and piping it
directly to Avamar. For more information, see the Avamar documentation on how to pipe
a backup into Avamar using "named pipes."
Importing the DPA Datastore

The dpa datastore import command line option is used to import the contents of
a Datastore file to the DPA Datastore.
Procedure
1. Stop the DPA Application service.
2. Import the Datastore.
3. Start the DPA Application service.
4. From a command line prompt, type the following:
dpa app stop dpa datastore import [options] <filename> dpa app
startWhere <filename> is the previously exported Datastore file. The import
Administering DPA
command replaces the existing datastore contents with the contents contained in the
Datastore export file.
After you finish

For a complete list of DPA commands, type dpa --help from a command line prompt.
dpa datastore export

Exports the contents of the Datastore to the filename or pipeline specified. The Datastore
service must be installed and running for this command to operate. Any existing filename
present will be overwritten.
dpa datastore export [options]
dpa datastore export [options] <directory>
Command options
--pipeline — Export to pipe
Examples
C:\Program Files\EMC\DPA\services\bin>dpa datastore export C:\
The default filename of the export is: datastore-<version> <date and time>.
For example, datastore-6_2_0_90597-2014-10-01-1135.
dpa datastore import

Imports the contents of the Datastore export file to the Datastore. The import files must
be available on the local filesystem. You will be prompted to stop all Application servers
that communicate with this Datastore prior running the command. The datastore service
must be running for the import command to execute.
dpa datastore import [options] <filename>
Where <filename> is a previously exported datastore file. The import command replaces
the existing Datastore contents with the contents contained in the Datastore export file.
Command options
<import_filename> — Filename of the exported file to import
Examples
# dpa datastore import datastore-2013-02-20-1205

Datatstore imported from file : datastore-2013-02-20-1205
Imported to the datastore successfully
dpa datastore export 39

Administering DPA
dpa application adminpassword

Resets the DPA Administrator password. You must run the command when the Datastore
Service is running.
dpa application adminpassword [options]

dpa app pwd [options]
Command options
--help (-h) — Displays the help screen
--version — Displays the tool version information
Example
C:\Program Files\EMC\DPA\services\bin>dpa.bat app pwd
Enter new administrator password:
Retype new administrator password:
Command completed successfully.
Completed in : 17.3secs
C:\Program Files\EMC\DPA\services\bin>
Running Data Domain DataProcessor

Before you begin
Ensure the following before starting this procedure:
l You are familiar with Data Domain.
l You have Admin role rights:
n to the Data Domain system on which you are collecting the data which you want to
report through DPA.
n to run Data Domain DataProcessor Processor analysis requests. SSH requests on
the Data Domain system.
l You must have user role rights to run primary SSH requests on the Data Domain
system.
l Your DPA hosts meet the system requirements needed to run the commands below.
The EMC Data Protection Advisor Software Compatibility Guide provides information.
l The dedicated host where you are going to run the DataProcessor can connect to the
DPA Application and to the Data Domain.
l The host on which you plan to run the DataProcessor tool has minimum of 100GB of
extra disk space. This is required for the resulting input files that are created by
running the DataProcessor. Your actual disk space requirement may be greater than
100GB and depends on the number if entries in your Data Domain.
l You have a quiet time in which to run the DataProcessor as it will consume significant
resources on both the Data Domain and the DPA Application.
l If you have upgraded to 6.2 SP3, go to dpa schema and delete all records in the
ddup_status and dd_analysis tables before you run the client aggregation
Administering DPA
and file age commands. You run only the DataProcessor for client
aggregation or for file age commands depending on your needs. Only run
both commands if you need to do so.
l The example commands in the procedure below that end in .bat are shown for
Windows. For UNIX/Linux implementation, the commands should end in .sh. For
example:
n for Windows: dd_scanner.bat
n For Linux: dd_scanner.sh
Procedure
1. Download the Data Domain DataProcessor package.
On Windows, the package is DPA-Data-Processor-Windows-x86_64-
<version>.xxxxx.zip. On UNIX, the package is DPA-Data-Processor-Linux-x86_64-
<version>.xxxxx.tar.gz, where<version> is the DPA DataProcessor version number and
xxxxx is the build number. The EMC Data Protection Advisor Release Notes provides
package location, version, and build information.
2. Extract the zip or tar.gz file to a folder on the dedicated host where you want to run the
DataProcessor tool.
3. On the DataProcessor tool host box, to go the /bin folder within installation directory
where you extracted the zip or tar.gz file.
4. To connect to the Data Domain and generate an input file for later analysis, run
dd_scanner.bat <datadomain host> <username>
where username is the Data Domain user with Admin role rights and datadomain host
is the name of the Data Domain object as it appears in the Inventory > Object Library
Storage tab.
The information collected is stored in a gzip compressed text file in a data/

incoming folder under the DataProcessor tool installation directory.
5. Enter the Data Domain Admin user password when prompted.
6. To analyze the input file for client aggregation data to run the Data Domain System
Utilization and Data Domain Reduction Ratios reports, run:
client_aggregation.bat <input file> <dpa server> <dpa username>.
For example: \bin>client_aggregation.bat \data\incoming

\lxxxx111_lxx_emc_com_1401414141.txt 10.11.111.111 administrator
Where:
l the input file is the gzip compressed text file that is generated by the
dd_scanner.bat command
l the dpa server is the server where the DataProcessor sends the data
l the dpa username is the username to log in to the DPA instance
The client aggregation command scans the information that was collected by the
previous dd_scanner command and sends client aggregation data to the DPA
server. The process auto-generates a folder with a name and datestamp of when the
dd_scanner command was run and when the input file was generated.
The DPA Reports Reference Guide provides information on the reports.

7. Enter your DPA server password when prompted.
Running Data Domain DataProcessor 41

Administering DPA
Output such as the following appears:
*************************************************************
** Client Aggregation **
** Version: 6.2.0. (12345) **
*************************************************************
Please enter password for the user:
Running process 1 of 3: Parsing DataDomain scan file - Success

Running process 2 of 3: Aggregating backup client data - Success
Running process 3 of 3: Uploading results - Success
Clearing the temp folder... Complete.

Client Aggregation completed.
You must leave the window open while the processes are running. If the output
indicates a failed or skipped process, rerun the command starting with the failed or
skipped process number. For example: \bin>client_aggregation.bat \data
\incoming\lxxxx111_lxx_emc_com_1401414141.txt 10.11.111.111
administrator 3
8. To analyze the input file for file age data to run the Data Domain File Distribution By
Count and Data Domain File Distribution By Size reports, run: file_age.bat <input
file> <dpa server> <dpa username>.
For example: \bin>file_age.bat \data\incoming

\lxxxx111_lxx_emc_com_1401414141.txt 10.11.111.111 administrator
Where:
l the input file is the gzip compressed text file that is generated by the
dd_scanner.bat command
l the dpa server is the server where the DataProcessor sends the data
l the dpa username is the username to log in to the DPA instance
The DPA Reports Reference Guide provides information on the reports.

9. Enter your DPA server password when prompted.
Output such as the following appears:
Running process 1 of 3: Parsing DataDomain scan file - Success

Running process 2 of 3: File Age calculator - Success
Running process 3 of 3: Uploading results - Success
Clearing the temp folder... Complete.

File Age completed.
You must leave the window open while the processes are running. If the output
indicates failed or skipped process, rerun the command starting with the failed or
skipped process number.
Results
The client aggregation and file age data is available in the DPA server. DPA can report on
client aggregation and file age data for Avamar, NetWorker, NetBackup, and Oracle
RMAN.
Administering DPA
After you finish

Before you can run any reports, you must assign the Data Domain Analysis request to
each Data Domain node on which you want to run these reports. This makes the
appropriate reports become available in the report menus.
CLP and WLS license coexistence in DPA

The CLP license is required for 6.2 and later functionality and increased capacity on a DPA
instance as of DPA 6.2.
If you are not adding capacity or changing to 6.2 and later functionality, import of CLP
licenses is not required. However, if you are upgrading to DPA 6.2 and later we
recommend that you contact licensing@emc.com after upgrade or migration to assist you
with legacy license transition to CLP licenses of all your WLS licenses. If you are migrating
from DPA version 5.x to version 6.2 and later, the existing licenses are migrated with your
configuration and data. You need to add CLP licenses only for 6.2 and later functionality
or for increasing current license capacity.
CLP licenses work on a replacement model. When you import a CLP license, the CLP
license replaces all the existing licenses of the same type. Additionally, the base and
Enterprise license functionality is moved into each CLP license. You must be aware of the
existing license count when you order CLP licenses of the same type, then add on the new
capacity required and order for the total. For information on purchasing licenses for your
DPA installation, contact your EMC Account Representative.
A system that has been migrated or upgraded from a previous version of DPA will contain
WLS licenses. WLS and CLP can coexist only where they aren't for the same functionality.
CLP and WLS license coexistence in DPA 43

Administering DPA
CHAPTER 4
Uninstalling DPA
l Uninstalling the software.......................................................................................46

l Agent-only uninstallation...................................................................................... 46
Uninstalling DPA 45
Uninstalling DPA
Uninstalling the software

This section describes how to uninstall DPA in both UNIX/Linux and Windows
environments.
Procedure
1. Run the following command:
<DPA_install_directory>/_uninstall/
Uninstall_Data_Protection_Advisor
Add -i silent to the command if you want silent uninstallation. The uninstaller
will not ask you for input.
Results
When uninstalling the DPA Datastore, a warning indicating that the uninstaller will
remove the features that were installed during product installation appears indicating
that the database will be removed.
Uninstalling by using silent command line

l On UNIX/Linux machines, start a command shell, navigate to the _uninstall directory
and type the following command:
./Uninstall_Data_Protection_Advisor -i silent
l On Windows machines, type the following command through the command line:
Uninstall_Data_Protection_Advisor.exe -i silent
Uninstalling through user interface on Windows

Procedure
1. Select Start > Control Panel > Programs and Features.
2. Uninstall EMC Data Protection Advisor from the list of installed applications.
Agent-only uninstallation
You cannot uninstall only the Agent from the DPA Application server or Datastore server
installation.
If you would like to upgrade the DPA Agent, upgrade the Agent only on the existing DPA
Application server or Datastore server installation.

DPA SolVe 62SP3 Implementing Plain

Uploaded by

Copyright:

Available Formats

DPA SolVe 62SP3 Implementing Plain

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DPA SolVe 62SP3 Implementing Plain

Uploaded by

Copyright:

Available Formats

EMC® Data Protection Advisor

Version 6.2 SP3

DPA Plain Implementation (Installing the

Published April, 2016

Chapter 1 Preparing to install DPA 9

Chapter 2 Installing DPA 25

Chapter 3 Administering DPA 37

Chapter 4 Uninstalling DPA 45

Revision Date Description

l EMC Data Protection Advisor Release Notes

Addresses practices not related to personal injury.

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

Table 2 Style conventions

Monospace italic Used for variables

[] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

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

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

Where to get help

This chapter includes the following sections:

Preparing to install DPA 9

DPA Server platforms

Co-located Application and Datastore systems are not supported in production

NTP time synchronization

Configuring virtual infrastructure memory and CPU

dpa datastore tune

dpa datastore tune <size>MB|GB [options]

Hardware issues with tuning

Communications settings in DPA

Communications settings in DPA 13

Figure 1 DPA 6.2 and minor releases ports and protocols

*Application servers and Collectors can be one or many.

DPA port settings

Table 3 DPA Application ports settings

Port Description Traffic direction

80 TCP port used for the SharePoint service Outbound connection to

161 UDP port used for SNMP service Outbound connection to

4447 TCP port used for intra-service communication Inbound connection

4712 TCP port used for intra-service communication Localhost connection

4713 TCP port used for intra-service communication Localhost connection

5445 TCP port used for intra-service communication Localhost connection

5455 TCP port used for intra-service communication Localhost connection

8090 TCP port used for intra-service communication Localhost connection

9005 TCP port used for Jboss Management Localhost connection

9999 TCP port used for Jboss Management Localhost connection

Table 4 DPA Datastore port settings

Port Description Traffic direction

DPA port settings 15

Table 4 DPA Datastore port settings (continued)

Table 5 DPA Agent port settings

Port Description Traffic direction

Table 6 DPA cluster port settings

Port Description Traffic direction

80 TCP port used for the SharePoint service Outbound connection to

4447 TCP port used for intra-service Inbound connection

4712 TCP port used for intra-service Localhost connection

4713 TCP port used for intra-service Localhost connection

5445 TCP port used for intra-service Bidirectional connection for

5455 TCP port used for intra-service Bidirectional connection for

7500 Multicast over UDP Bidirectional connection for