data protection advisor 6.2 installation and administration guide

8/15/2019 Data Protection Advisor 6.2 Installation and Administration Guide

1/182

EMC® Data Protection Advisor Version 6.2

Installation and Administration Guide302-000-706

REV 05


2/182

Copyright © 2005-2015 EMC Corporation. All rights reserved. Published in USA.

Published April , 2015

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

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware 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 CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC Data Protection Advisor 6.2 Installation and Administration Guide


3/182

7

9

11

Preparing to install DPA 15

Overview.......................................................................................................16System requirements.................................................................................... 16

Datastore storage.............................................................................17

Permissions..................................................................................... 17Installation considerations............................................................................17Configuring virtual infrastructure memory and CPU...........................17OS resource optimization.................................................................18

Port settings..................................................................................................18Installation and configuration overview.........................................................22

Installing DPA 29

DPA server installation.................................................................................. 30Installing the Datastore Service........................................................30Installing the Application Service..................................................... 32

DPA Agent installation...................................................................................34Installing the DPA agent...................................................................35

Installing by using command line installation................................................36Application clustering................................................................................... 40

Adding an Application server to a cluster during installation............ 40Restrictions and recommendations for clustering.............................40

Datastore Replication....................................................................................41Configuring Datastore Replication....................................................41Configuring Datastore Replication during installation.......................42Datastore Replication best practices................................................ 42

DPA postinstallation .....................................................................................42Encryption of the DPA Application server..........................................43

Upgrades...................................................................................................... 44

Upgrade prerequisites......................................................................44Upgrading DPA.................................................................................45Upgrading existing clusters..............................................................46Upgrading with Datastore Replication enabled................................. 47

Administering DPA 49

License management.................................................................................... 50Evaluation license bundled with DPA............................................... 50Licensing types in DPA..................................................................... 50CLP and WLS license coexistence in DPA..........................................50Expired licenses...............................................................................50

License removal ............................................................................... 51

Figures

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

CONTENTS

EMC Data Protection Advisor 6.2 Installation and Administration Guide 3


4/182

Adding new licenses........................................................................ 51Disabling automatic temporary licence expiration pop-up................ 51

Users and systems settings...........................................................................51User roles and privileges..................................................................51LDAP authentication.........................................................................53Digital certificate..............................................................................57

Time periods....................................................................................57Automatic report prioritization......................................................... 58Schedules........................................................................................58System settings............................................................................... 58Manage Data Collection Defaults......................................................64

Application service administration................................................................ 78Customization of service information............................................... 78Clustering administration.................................................................81

Datastore service administration...................................................................83Backup of the Datastore...................................................................84Datastore Replication administration............................................... 85

DPA command line operations...................................................................... 90

Sourcing the DPA config file for UNIX users.......................................90dpa CLI command............................................................................ 90dpa application commands..............................................................91dpa datastore commands................................................................ 97dpa service commands.................................................................. 102Loading historical backup job data................................................ 103

Environment discovery in DPA 107

Configuring the environment for discovery...................................................108Discovery overview.........................................................................108Defining objects to be monitored................................................... 108Before you run the Discovery Wizard.............................................. 109Configuring application hosts for monitoring..................................112Configuration of storage arrays for replication analysis.................. 112Monitoring of data protection servers.............................................115Monitoring of Databases................................................................127Gathering of data from operating systems......................................132Monitoring of switches and I/O devices..........................................135Monitoring of file servers................................................................136Monitoring of backup appliances...................................................137Monitoring of disk management servers.........................................144Monitoring of VMware environment................................................145

Monitored objects and groups.....................................................................146Objects overview............................................................................146

Groups...........................................................................................148Object attr ibutes............................................................................148Smart Groups.................................................................................148

Configuring policies, rules, and alerts......................................................... 151Policies and alerts overview...........................................................151Policies..........................................................................................151Policies and generating events.......................................................164Parameter s for generating alerts from scripts................................. 165Rule Template................................................................................166Policy application...........................................................................166

Uninstalling DPA 167

Chapter 4

Chapter 5

CONTENTS



5/182

Uninstalling the software............................................................................ 168Uninstalling by using silent command line..................................... 168Uninstalling through user interface on Windows.............................168

Agent-only uninstallation............................................................................ 168

Troubleshooting 169Installation troubleshooting........................................................................ 170

DPA Datastore on Linux failure to start after installation................. 170DPA web console launch failure on Windows Server 2012.............. 170Postinstallation memory tuning......................................................170Error messages during upgrades....................................................170

Log files...................................................................................................... 171Changing default log detail level.................................................... 171Viewing install log file....................................................................171Viewing server log files ...................................................................171Server log files............................................................................... 171Viewing agent log files................................................................... 172

Managing log files..........................................................................172Enabling alternative log rotation on VMs running Windows............ 172Erroneous memory data in installer log file.....................................172Running a DPA Agent request in debug mode using DPA web console...................................................................................................... 172Default modtest deletion schedule.................................................173Generate Support Bundle...............................................................173

Data collection troubleshooting.................................................................. 173Troubleshooting data collection: first actions.................................174Troubleshooting data collection: second actions............................174Preparing a log file for submission to EMC Support........................ 174

Client/Storage discovery for replication analysis troubleshooting................175Client/storage discovery using remote execution........................... 175Client/stor age discovery with agent............................................... 176General client/storage discovery....................................................177Incorrect Recovery Point times Synchronization..............................179

Troubleshooting report output failure..........................................................180Troubleshooting report generation or publishing problems......................... 180System clock synchronization..................................................................... 180

Chapter 6

CONTENTS



6/182

CONTENTS



7/182

DPA 6.2 ports and protocols.......................................................................................... 19DPA installation workflow..............................................................................................22Relationship between DPA Application nodes and DPA Agents monitoring applications....................................................................................................................................108DataProcessor Tool data flow .......................................................................................139Object library Multilevel Smart Group configuration example.......................................150

123

45

FIGURES



8/182

FIGURES



9/182

Revision history.............................................................................................................11Ports required for installing any DPA Application service on local host using bind address......................................................................................................................................19Ports required for installing any DPA Application service on local host using loopbackaddress......................................................................................................................... 20Additional ports for clustered DPA Application service on local host using bind address......................................................................................................................................20Ports required for installing the DPA Datastore services on local host using bind address......................................................................................................................................21Ports required for installing the DPA Agent service on local host using bind address......21Ports required for DPA 5.x Collectors..............................................................................22Installation and configuration overview .........................................................................22Installer command line options......................................................................................36

Datastore installer variables.......................................................................................... 37Datastore Advanced options Replication variables.........................................................37Datastore Agent variables..............................................................................................38Application installer variables....................................................................................... 38Application server Agent variables.................................................................................38Application server Cluster Advanced option variables....................................................39Standalone Agent Installer variables..............................................................................39Users and user roles...................................................................................................... 51Agent setting ................................................................................................................ 59Server settings...............................................................................................................59Default collected data retention periods........................................................................ 61Default system-generated data retention periods...........................................................62

Replication analysis settings......................................................................................... 63Agentless Discovery settings......................................................................................... 63Data collection request options by module ....................................................................64VTL templates................................................................................................................79Command and option abbreviations ............................................................................. 91Data monitoring setup summary ................................................................................. 108Connectivity details for configuring data collection through the Discovery Wizard ....... 110HP Data Protector 6.1 patch IDs...................................................................................119System monitoring modules........................................................................................ 132Multilevel Smart Group example..................................................................................149Capacity planning........................................................................................................153Change management...................................................................................................154Configuration...............................................................................................................155

Data protection............................................................................................................155Licensing.....................................................................................................................157Performance................................................................................................................ 157Provisioning................................................................................................................ 157Resource utilization.....................................................................................................158Service Level Agreement..............................................................................................159Status..........................................................................................................................159Troubleshooting.......................................................................................................... 161Recoverability checks ................................................................................................. 162Script field parameters................................................................................................ 165Script alert arguments................................................................................................. 165Client/storage discovery problems and solutions ........................................................175

Client/storage discovery with agent problems and solutions....................................... 177

12

3

4

5

6789

101112131415161718192021

22232425262728293031323334

353637383940414243444546

47

TABLES



10/182

General client/storage discovery problems and solutions ...........................................17748

TABLES



11/182

Preface

As part of an effort to improve its product lines, EMC periodically releases revisions of itssoftware and hardware. Therefore, some functions described in this document might notbe supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properlyor 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.

PurposeThis document provides information on how to install DPA and set up DPA to monitor adata protection environment. This document also describes administrative functionssuch as creating users and roles, updating system settings, creating policies, andtroubleshooting data collection.

Audience

This document is intended for system administrators. Readers of this document must befamiliar with the following tasks:

l Identifying the different hardware and software components that make up the backupand 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 December 15, 2014 First release of this document for EMC Data Protection

Advisor 6.2

02 January 13. 2015 Updates to the following sections:

License management on page 50Preparing a log file for submission to EMC Support on

page 174

General client/storage discovery on page 177

Troubleshooting report generation or publishing

problems on page 180

03 February 5, 2015 Update to Monitoring of VMware environment on page

145

04 March 31, 2015 Addition of to Monitoring of VMware vSphere Data

Protection on page 146


https://support.emc.com/https://support.emc.com/


12/182

Table 1 Revision history (continued)

Revision Date Description

05 April 30, 2015 Updates to the following sections:

Data Collection Agents on page 59

Datastore service administration on page 83

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

l EMC Data Protection Advisor Release Notes

l EMC Data Protection Advisor Report Reference Guide

l EMC Engineer's 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



13/182

Typographical conventions

EMC uses the following type style conventions in this document:

Bold Use for names of interface elements, such as names of windows, dialog boxes, buttons, fields, tab names, key names, and menu paths (what

the user specifically selects or clicks)

Italic Use for full titles of publications referenced in text

Monospace Use 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 Use for variables

Monospace bold Use 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 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. You will see several options for contacting EMC Technical Support. Note that to open a service request, you must have avalid support agreement. Contact your EMC sales representative for details aboutobtaining a valid support agreement or with questions about your account.

Online communities

Visit EMC Community Network at https://community.emc.com for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith customers, partners, and certified professionals for all EMC products.

Your comments

Your suggestions will help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document [email protected]

Preface


mailto:[email protected]://community.emc.com/https://support.emc.com/


14/182

Preface



15/182

CHAPTER 1

Preparing to install DPA

This chapter includes the following sections:

l Overview...............................................................................................................16l System requirements............................................................................................ 16l Installation considerations....................................................................................17l Port settings..........................................................................................................18l Installation and configuration overview.................................................................22

Preparing to install DPA 15


16/182

OverviewAll 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 installing 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. Youcan connect multiple Application servers to the same Datastore server, where eachadditional Application server is on its own host and the Application servers are installedas a DPA cluster. You can install additional DPA Agents for system monitoring and remotedata collection. Clustering of the Application server is available to provide load balancing where a load balancing switch is implemented and quality of service separation. The Data Protection Advisor Architecture Guide provides more information.

System requirementsDPA has the following basic minimum system requirements. The EMC Data Protection Advisor Software Compatibility Guide provides a comprehensive list of systemrequirements.

l Split-server installation onlyCombined DPA Application and Datastore servers on one host is not supported

l 8GB RAM, 2 cores / CPUs per Application and Datastore server

l 18GB for the Application server

l 20GB for the Datastore Server 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 hostresources must be dedicated to DPA.

If running DPA in a virtualized environment the allocated CPU and memory must bereserved for the DPA servers

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

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, 2008 R2, 2012, 2012 R2

n Red Hat Linux ES/AS 5, 6.0, 6.2, 6.4 , 6.5Run the Update Agent (up2date) to ensure that the latest operating systempatches are installed

n SUSE Linux 11 x86Run the Update Agent (up2date) to ensure that the latest operating systempatches are installed




17/182

libaio is recommended to be installed on the system and available in the systemLD_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 systemsmight 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 optimizeperformance during installation under Advanced installation options

Permissions

Ensure that you have the following permissions before you install the software to avoidinstallation 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 thepermissions allow the creation of new users after you become root. This mustinclude the ability to create default home directories for the account to be created.

Installation considerationsThe DPA installation wizard presents advanced options for configuring DatastoreReplication with Master and Slave Datastores, and for configuring clustered Applicationobjects. 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 Representativefor 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 resourceallocation shares are set to High. Alternatively, select High Share Allocation for eachindividual VM.

l Select Thick Provision Eager Zeroed for Datastore disks. Thick Provision Eager Zeroeddisk allocation causes all space to be allocated upfront, and the full disk file is zeroedbefore the system is made available for usage.


Datastore storage 17


18/182

OS resource optimization

General tuning

During installation, the installer tunes the DPA Datastore Service for the host environmenton which it is being deployed. This tuning assumes that the host is dedicated to DPA andtakes into account resources such as Disk Space, Total Memory, and CPU cores. If other applications are installed on this host and also using these resources DPA performancewill be degraded. If during the lifetime of the DPA Datastore Service any of these physicalresources are increased or decreased, execute the dpa datastore tune command on theDatastore host. dpa datastore tune on page 101 provides more information.

Hardware issues with tuning

For deployments where optimal performance is a concern, the type and quality of thehardware 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 extraspindles help spread the reads and writes over multiple disks to increase throughput andto reduce drive head congestion.

For production purposes the DPA Application Service and the DPA Datastore Serviceshould be placed onto different hardware. Not only does this provide more hardwarededicated to the Datastore Service, but the operating system's disk cache will containmore 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.

Port settingsTo ensure communication between the DPA Server and DPA Agents, configure thefirewalls 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 onwhat you plan to monitor. For example, if you monitor Avamar, open port 5555 betweenthe Avamar server and the DPA Agent. Environment discovery in DPA on page 107provides more information.




19/182

Figure 1 DPA 6.2 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 initiatesconnection to DPA Application Server on 9002. For firewalls, it is based upon whoinitiates the connection and on what port, and who is listening on the other side. DPAAgent to DPA Application Server communication is on 9002 and 3741 TCP. The

communications are secure, encrypted, and compressed between the Agent and DPAserver.

The tables below detail the additional ports required on deployment hosts to allow DPAto function correctly. The ports listed must be able to accept connections and allowresponses back on any established connection. Some network vendors describe suchhandshaking communication as Bi-Directional; and such network security devices shouldreflect this accordingly.

The following table below details the ports that must be available and free to use on thelocal host. These ports are user for intra-application communication and are used for communication external to the host. These ports are referenced by DPA using a standardIP address, called the bind address.


Port settings 19


20/182

Table 2 Ports required for installing any DPA Application service on local host using bind address

Service Port Port Type Description

HTTP 9004 TCP inbound Used for UI, CLI, and

REST API

communications

HTTPS 9002 TCP inbound Used for UI, CLI and

REST API

communications over

SSL

DPA Agent 3741 TCP inbound Protocol port used by

DPA to send control

data and manage the

DPA Agent

REMOTING 4447 TCP inbound Used for intra-service

communicationTXN_RECOVERY 4712 TCP inbound Used for intra-service

communication

TXN_STATUS 4713 TCP inbound Used for intra-service

communication

MESSAGING 5445 TCP inbound Used for intra-service

communication

MESSAGING_THROUG

HPUT

5455 TCP inbound Used for intra-service

communication

The table below details the ports that must be available and free to use on the local host.These ports are user for intra-application communication and are not used for communication external to the host. These ports are referenced by DPA using thestandard loopback address: 127.0.0.1

Table 3 Ports required for installing any DPA Application service on local host using loopback

address


MANAGEMENT_NATIVE 9999 TCP inbound Used for intra-service

communication

MANAGEMENT_HTTP 9005 TCP inbound Used for intra-servicecommunication

OSGI 8090 TCP inbound Used for Service start-

up control

The table below details the ports that must be available and free to use on the local host.These ports are used for inter-application node communication and are used for communication external to the host. These ports are referenced by DPA using a standardIP address, called the bind address. Note that UDP Multicast ports are associated with aUDP Multicast Address that is specified during installation or via the DPA CLI.




21/182

Table 4 Additional ports for clustered DPA Application service on local host using bind address


JGROUPS-UDP 55200 UDP Multicast Used for

communication

between cluster nodes

JGROUPS-UDP-LOCK 5 5201 UDP Multicast Used for

synchronization

events between cluster

nodes

JGROUPS-UDP-FD 54200 UDP Multicast Used for resource

handling between

cluster nodes

JGROUPS-UDP-FD-

LOCK 5

4201 UDP Multicast Used for resource

synchronization

between cluster nodes

The table below details the ports that must be available and free to use on the local host.These ports are user for inter-application communication and are used for communication external to the host, specifically to the application nodes. These ports arereferenced by DPA using a standard IP address, called the bind address.

Table 5

Ports required for installing the DPA Datastore services on local host using bind address


PQSQL 9003 TCP inbound Used for listening to

connections to DPA

Agents


DPA to send control

data and manage the

DPA Agent

The table below details the ports that must be available and free to use on the local hostwhere a DPA Agent is to be installed. These ports are user for inter-applicationcommunication. These ports are referenced by DPA using a standard IP address, calledthe bind address.

Table 6 Ports required for installing the DPA Agent service on local host using bind address



DPA to send control

data and manage the

DPA Agent


Port settings 21


22/182

Table 7 Ports required for DPA 5.x Collectors


AGENT - HTTP 3741/9002 TCP

AGENT-CONFIGURATION

3916 TCP

AGENT - SEND DATA 4001 TCP

Installation and configuration overviewThe DPA installation workflow provides a high-level workflow of tasks for installing DPAwith 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 8 Installation and configuration overview

Action Comments

Set up host computer

Provide at least two hosts for DPA

server installation:

DPA must not be installed on servers already running other

applications. For installation in a production environment,




23/182

Table 8 Installation and configuration overview (continued)

Action Comments

One for the initial DPA Application

server, and one for the Datastore.

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

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.

you need one host for the Application Service and a

separate host for the Datastore Service. EMC recommends

that you use a dedicated server with at least 2GB of

temporary space. The EMC Data Protection Advisor Software

Compatibility Guide provides more information.

Provide a host for DPA Agent

installation (optional).

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.

If the DPA server is running on Windows and the discovered

host is also Windows, you need not install an Agent on the

discovered host.

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

by using command line installation on page 36 provides

more information.

Ensure that DPA and all its

components are configured as

exceptions in any antivirus

software.

Occasionally DPA components are shut down or associated

files are quarantined by antivirus software if not defined as

exceptions.

Provision networking infrastructure

and a shared directory if installing

multiple Application servers (DPA

clustering).

l Allocate a dedicated VLAN for use by the DPA

Application servers. If a dedicated VLAN is not

available, ask your network administrator for a UDP

Multicast group address that can be used for the DPA

cluster.

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

requirements.

DPA has been certified to work on a Linux or Windows

virtual machine in a VMware or Hyper-V environment. The

EMC Data Protection Advisor Software Compatibility Guide

provides more information.


Installation and configuration overview 23


24/182


Action Comments

Configure virtual infrastructure

memory and CPU

Configuring virtual infrastructure memory and CPU on page

17 provides more information.

Open or disable firewalls for

communciation between the DPA

servers.

If you want to use secure communication for connecting to

the Application server on port 9002, ensure that TLS

(Transport Layer 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 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. Port settings on page 18

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 system onthe DPA Server(s) and Agent host

and install all required patches.

The EMC Data Protection Advisor Software Compatibility Guide

lists the required architectures and patches.

Install all required software on the

agent host after the DPA 6.2

Application Server is ready.

When monitoring applications or devices remotely, you may

need to install additional software on the Agent host. For

example, the EMC NetWorker client must be installed on the

Agent host if the Agent will be used to monitor EMC

NetWorker remotely. For more information see Environment

discovery in DPA on page 107

If DNS is not enabled in the

environment, add the IP address

and FQDN of the SharePoint server on the DPA Application server’s

hosts file.

DPA and SharePoint integration requires the IP address and

FQDN to enable you to publish reports to SharePoint and to

configure the SharePoint port. The SharePoint port isconfigurable. The default port, if no port is specified, is 80.

You can set the port by using a standard URL in the existing

URL field in the SharePoint settings dialog. Table 19 on

page 59 provides information.

If you are going to use LDAP User

Authentication on your DPA server,

gather the information needed for

configuration

You need the following information for LDAP User

Authentication configuration:

l LDAP Server Name/IP

l Use SSL?

l LDAP Server Port




25/182


Action Comments

l LDAP Version

l Distinguished Name of Base Directory

l Identification Attribute

Download and save the DPA

binaries

To download the DPA Server, Agent, and Data Domain

DataProcessor tool binaries, go to the DPA downloads

section of http://support.emc.com.

Save the DPA Server and Agent binaries locally.

Save the Data Domain DataProcessor binaries accor ding to

the specifications provided in Running Data Domain

DataProcessor on page 139

Obtain and save DPA Licenses

Save the required license files on

your local machine for easy access

during installation. The DPA

installation wizard prompts you to

browse for the license file at license

installation.

You must know the IP address of the primary Datastore

server.

For more information on obtaining DPA licenses or types of

DPA licenses available and required, contact your EMC

Account Representative.

l For new non-migrated

installations - Obtain DPA

licenses for all components

that will be monitored.

l

For upgraded 6.0 SP1 andmigrated 5.x installations -

Existing licenses will be

migrated.

l The CLP license is required for

new 6.2 functionality and

increased capacity on a DPA

instance. If you are not adding

capacity or changing to new

6.2 functionality, import of CLP

licenses is not required. If you

are migrating from DPA version

5.x to version 6.2, 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 license types if they are

imported before CLP licenses.

CLP and WLS license

coexistence in DPA on page

50provides more

information .

A DPA license is required to administer DPA after

installation.

DPA is bundled with a 60-day evaluation license. The

evaluation license is created from the time of DPA

installation, is valid for up to 60 days, and allows access to

all features. If you import a license during 60-day

evaluation license period, the evaluation license is

removed and you have access to DPA features according to

license you imported.

For information on required DPA licenses or on purchasing

licenses for your DPA installation, contact your EMC sales

representative.



http://support.emc.com./


26/182


Action Comments

Provide the Solutions Enabler (SE)

licenses.l A minimum of one gatekeeper per HBA per Symmetrix

is 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 30 , Installing the Application Service on page 32,

and Installing the DPA agent on page 35provide more

information.

Configure EMC host array discovery and Solutions Enabler hosts

Configure Symmetrix and VNX/

CLARiiON array for discovery

Configuration of storage arrays for replication analysis on

page 112 provides more information. The steps in this

section apply only if you are monitoring a storage array,

database, or Microsoft Exchange Server for replication

analysis.

Provide the Solutions Enabler host

used to discover Symmetrix or VNX/CLARiiON storage arrays.

The EMC Data Protection Advisor Software Compatibility Guide

describes the versions of Solutions Enabler required for storage array discovery, and the software that must be

installed on the Solutions Enabler host. The host must be

able to connect to the Symmetrix 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 ports

between the DPA Agent host and

the monitored server or devices are

open and communication is

possible over the protocol.

Port settings on page 18 lists the protocols and default DPA

ports required for communication between the agent and

the monitored device or server.

Ensure that the DPA credential used

to connect to the monitored device

or server is sufficient, or have the

new credential details ready.

Permissions on page 17lists the default settings for the DPA

credentials that are installed with DPA.

Set up monitoring of RecoverPoint

(if applicable).

EMC RecoverPoint agent host and application host

requirements are listed in Monitoring of EMC

RecoverPoint on page 132

Discover and configure Application

Host import (if monitoring Microsoft

Exchange or a database).

l If a remote agent is being used to import hosts, the

DPA server must be able to resolve the agent host.




27/182


Action Comments

l If application discovery is being performed without an

agent, Configuring application hosts for monitoring on

page 112 provides more information.

Define the data protection policies

Prepare the details of the policies

that DPA will monitor for

compliance.

Policies on page 151 provides more information.

For replication analysis, the Data protection policy details

consist of:

l The type or replication, (SRDF/S, SRDF/A, MirrorView,

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.




28/182




29/182

CHAPTER 2

Installing DPA

This chapter includes the following sections:

l DPA server installation.......................................................................................... 30l DPA Agent installation...........................................................................................34l Installing by using command line installation........................................................36l Application clustering ........................................................................................... 40l Datastore Replication............................................................................................41l DPA postinstallation .............................................................................................42

l Upgrades.............................................................................................................. 44

Installing DPA 29


30/182

DPA server installationThe DPA server installation involves two stages:

1. Installing the Datastore Service on page 30

2. Installing the Application Service on page 32

Installation of the Application service before the Datastore service results in failure of Application service installation. If you encounter issues during the installation,Troubleshooting on page 169 provides information.

The procedures in this section are applicable to new installations. For upgrades fromsupported DPA versions to DPA 6.2, and to install version 6.2 patches, see Upgrades onpage 44. The DPA 6.2 Release Notes provides information on supported upgrades.

The DPA installer runs on Windows and Linux, provided that your Linux installationsupports running a UI. The following procedures explain a split- server installation in aWindows 64-bit environment.

Installing the Datastore Service

Before you begin

l Ensure that you log in as a local administrator or a Domain administrator with fulllocal 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 couldexperience problems with the Datastore server if you install after becoming rootthrough certain SU-type security software; for example, using the sesu command.

l Ensure that ports are opened or disabled for communication between the DPAservers. Installation and configuration overview on page 22 provides information.

l Ensure that you have the IP Address of the Application server for the Agent tocommunicate with. If installing on Linux IPv6, ensure that you also have the IPv6Interface ID of the Datastore server. You are prompted for this in the Configure Agentwindow 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 thisexample, fe80::9c9b:36f:2ab:d7a2 ) and those after refer to the interface Id (in

this example, 2 ).

l If installing Datastore Replication:

n Plan the final deployment topology before beginning installation. Additionalresources are available on the EMC Community Network (ECN) that provideguidance and best practice for planning your deployment.

n Have all hosts and IP addresses predetermined and available.

n Ensure that all Datastore server or Application server, including clustered nodes,are using the same IP type of IP addressing, either IPv4 addresses or IPv6addresses.

Installing DPA



31/182

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

To perform an advanced installation, select the Show Advanced Installation Optionscheckbox in the Advanced Installation screen, click Next, and follow the installationwizard.

The Advanced Options are:

l Do not register DPA services: Prevent the registration of the Datastore service withthe operating system manager. This will prevent the Datastore service from being

started after host reboot. You must use of the DPA Command Line Interface toinstall 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 theservice.

l Install with advanced datastore layout: Configure the datastore service with therequired filesystems distributed across different disks to optimize performance.

Selecting Advanced Installation Options also enables you to configure DatastoreReplication and select a replication role for this server later on in the installer.

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 onwhich 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(es) of the DPA Application Server(s) that will usethe Datastore from step 6 and then click Add and Next.

If you are installing a single DPA Application Server provide just the one address for that server.

If you are installing multiple DPA Application Servers in a clustered configuration,enter IP addresses for each DPA Application Server.

10.If you are configuring Datastore Replication, select Enable datastore replication > andselect the replication role for this server > SLAVE. Click Next.

a. Provide the IP address or FQDN of the Master Datastore server.

b. When prompted in the Configure Agent window, enter the FQDN or IP address of the DPA Application service that the installed DPA Agent needs to communicate

with.

Installing DPA

Installing the Datastore Service 31


32/182

By default, the Agent communicates with the Application server specified earlier inthe wizard.

If you are using clustered DPA Application servers, provide the load balancer'sFQDN/IP address. Provide the Application server/Load Balancer's IPV6 Address inthe following format: IPV6Address%Interface_Id

The FQDN/IPAddress default value is left blank in case of a cluster and in case youare using clustered DPA Application servers Linux IPv6 application server becauseyou must manually enter the IPV6%Interface_Id. In all other cases, the FQDN/IPAddress is automatically populated with the default value of the Applicationserver's IP Address.

Click Next.

11.When the DPA Datastore Server installation is complete, click Done.

Installing the Application Service

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

l If installing with Advanced Options on Linux IPv6, and the Agent wants to talk to adifferent 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 tocommunicate with. You are prompted for this in the Configure Agent window of theApplication 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 loadbalancer 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 installing Application server clustering:

n Plan the final deployment topology before beginning installation. Additional

resources are available on the EMC Community Network (ECN) that provideguidance and best practice for planning your deployment.

n Have all hosts and IP addresses predetermined and available, including the IPaddress configured for the load-balancing switch that will be placed in front of theApplication servers.

n Ensure that all cluster nodes are using the same IP type of IP addressing, either IPv4 addresses or IPv6 addresses.

n Specify a common directory that is shared across all nodes. This is the location of the folder where the reports generated by the DPA Application node are stored.

l If installing Application server clustering on UNIX, ensure that you specify thecommon shared directory to a local directory mapped to a UNIX NFS or CIFS network

share.

Installing DPA



33/182


34/182

7. Review the Pre-Installation Summary, the disk space information in particular, clickInstall.

The installation proceeds.

If there is not enough disk space, cancel the installation or choose a different drive onwhich to install DPA.

Note

A Datastore connection failure error might occur if the relevant firewalls required to

communicate between Application Server and the Datastore are not open. Port

settings on page 18 provides information.

8. In the Connect to Remote DPA Datastore step, enter the IP address for the DPADatastore server previously installed.

The installation resumes.

9. When prompted in the Configure Agent window, enter the FQDN or IP address of theDPA Application service that the installed DPA Agent needs to communicate with.

By default, the Agent communicates with the local Application server on which theinstallation is being carried out.

If you are using clustered DPA Application servers, provide the load balancer'sFQDN/IP address.

If on Linux IPV6, provide the Load Balancer's IPV6 Address in the following format:

IPV6Address%Interface_Id

Click Next

The DPA Application service installation is now complete.

10.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 DPAAdministrator's password and enable the DPA Administrator account when theDPA Datastore service is up and running. dpa application adminpassword on page92 provides more information.

11.Click Done.

After the installation is complete, start the DPA Server if required and license theServer. DPA postinstallation on page 42 provides more information.

DPA Agent installationThis section describes how to install the DPA Agent using the agent-only installationpackage. 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. For upgrades from DPA 6.1 and

Installing DPA



35/182

related service packs to DPA 6.2 and to install version 6.2 patches, see Upgrades on page44.

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 DPAdocumentation 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 tocommunicate with. If installing on Linux IPv6, ensure that you also have the IPv6Interface 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 thisexample,fe80::9c9b:36f:2ab:d7a2 ) and those after refer to the interface ID of

the Agent (in this example, 2 ).

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 Agentservice after installation.

If you select this option, you must manually start the DPA Agent from the commandline.

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 thatcommunicates with the DPA Agent.

l Agent will be used to monitor Oracle Database: Select this option to monitor anOracle database with the DPA Agent.

If you select this option, browse to the directory where the the DPA Agent can findthe Oracle Database device driver files.

7. Click Next.

8. In the Configure Agent window, enter the fully qualified domain name or the IPaddress 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 IPv6Interface ID of the Linux Agent.

Installing DPA

Installing the DPA agent 35


36/182

Click Next.

9. Click Done to complete the installation.

Installing by using command line installationUse the appropriate command line.

l UNIX/Linux

DPA--Linux--6.2.0.xxx.install.bin [option]

where option is one of the options listed for a silent or an interactive installation inTable 7.

For example:

DPA-Agent-Linux-x86_64-6.1.1.xxx.bin -i silent -DUSER_INSTALL_DIR="/opt/custom/emc/dpa"

l

WindowsDPA--Windows--6.2.0.xxx.install.exe[option]

where option is one of the options listed for a silent or an interactive installation inTable 7.

For example:

DPA-Agent-Windows-x86_64-6.1.1.xxx.exe -i silent -DUSER_INSTALL_DIR="C:\custom\emc\dpa"

Ensure that you carry out the steps provided in DPA postinstallation on page 42.

Table 9 Installer command line options

Option Description

-? Displays help text

-i [swing | console |

silent]

Specify the user interface mode for the installer:

swing - Graphical interface

console - console only

silent - no user interaction

-D ="" Shows the installer name-value pairs that might be set on the command line (using the -D option) to

override default installer values, or placed in a response file and used with the-f option.

Quotes must be used around the value.

Example:

-D=""

Where:

For example:

DPA-Agent-Linux-x86_64-6.2.0.xxx.bin -i silent -DPort="3740"

and descriptions are included in the following tables.

Installing DPA



37/182

Table 1 Datastore installer variables

Variable Name Description Possible Values Default Values

USER_INSTALL_DIR Installation location Valid Path Windows: C:\Program Files

\EMC\DPA

Linux: /opt/emc/dpa

CHOSEN_INSTALL_SET Installation set DS

VAR_INSTALL_SERVICE Advanced option to install the

Datastore Service

TRUE/FALSE TRUE

VAR_START_SERVICE Advanced option to start/stop

the Datastore service

TRUE/FALSE TRUE

VAR_DATASTORE_DATA_LOCAT

ION

Advanced Datastore layout

option to specify Datastore

server data directory for

optimizing performance

Valid Path $USER_INSTALL_DIR$\services

\datastore\

VAR_DATASTORE_XLOG_LOCAT

ION

Advanced Datastore layout

option to specify Datastore

server Xlog directory for

optimizing performance

Valid Path $USER_INSTALL_DIR$\services

\datastore\data\

VAR_USERNAME (LINUX only) Advanced option to specify an

existing UNIX user account to

install the Datastore service

Existing username

VAR_DATASTORE_BIND_ADDRE

SSES

IPAddress for Postgres to listen

on

Valid IP Address

VAR_DATASTORE_CLIENTS_ADDRESSES IPAddress of IP Address of Applicationserver(s) which will connect to

the Datastore service

Valid IP Addresses separatedby ", "

Table 11

Datastore Advanced options Replication variables


VAR_DATASTORE_REPLICATION Role for Datastore replication MASTER/SLAVE

VAR_DATASTORE_REPLICATION

_

The IP Address of Master or

Slave. If


_ROLE is set as "MASTER",

then the Slave's IPAddress

needs to be entered and vice

versa when


_ROLE is set as "SLAVE "

Valid IP Address of Master or

Slave

Installing DPA

Installing by using command line installation 37


38/182

Table 12 Datastore Agent variables


VAR_AGENT_APPLICATION_AD

DRESS DPA Server FQDN or IP

Address to manage the

Datastore Agent

DPA Server FQDN or IP Address

to manage the Datastore Agent

In case of linux IPv6,

%

Valid IP Address or hostname For multiple application

servers and for cases where

the datastore service is

communicatong with linux IPv6

application server(s), this

value will be empty. Otherwise

the default value is the same

as

VAR_DATASTORE_CLIENTS_AD

DRESSES

VAR_AGENT_START_SERVICE Advanced option to start/stop

Datastore Agent after install

TRUE/FALSE TRUE

VAR_AGENT_ORACLE_DIRECTO

RY

Advanced option used for

monitoring Oracle by theDatastore Agent. Path where

the Oracle Database device

driver files can be found

Valid Path

Table 13

Application installer variables



\EMC\DPA

Linux: /opt/emc/dpa

CHOSEN_INSTALL_SET Installation set APP

VAR_INSTALL_SERVICE Advanced option to Install the

Application Service

TRUE/FALSE TRUE

VAR_START_SERVICE Advanced option to start/stop

the Application service after

installation

TRUE/FALSE TRUE

VAR_APPLICATION_DATASTORE

_ADDRESS

IPAddress of the Datastore

server

Valid IP Address where

Datastore service is installed

and running

VAR_ADMIN_PASSWORD DPA application'sadministrator password

[Set at installation or resetusing DPA CLI.]

Table 14

Application server Agent variables



DRESS


to manage the Application

server's Agent

Valid IP Address or hostname 127.0.0.1

Installing DPA



39/182

Table 14 Application server Agent variables (continued)


VAR_AGENT_START_SERVICE Advanced option to start/stop

the Application server's Agent

after install

TRUE/FALSE TRUE

AVAR_AGENT_ORACLE_DIRECT

ORY


monitoring Oracle by the

Application server's Agent.

Path where the Oracle

Database device driver files

can be found

Valid Path

Table 15 Application server Cluster Advanced option variables


VAR_APPLICATION_ADDRESS The IP Address used by the

Application server to announce

itself to other DPA application

nodes.

Valid IPAddress

VAR_APPLICATION_CLUSTER_R

OLE

Role of the application node in

a cluster

MASTER/SLAVE

VAR_APPLICATION_MASTER_A

DDRESS

If

VAR_APPLICATION_CLUSTER_R

OLE="SLAVE", this value needs

to be entered.

Valid IP Address

VAR_APPLICATION_REPORT_DI

RECTORY

Path to the network shared

report folder

Valid path

VAR_APPLICATION_REPORT_US

ERNAME The

The user who will be owning

the Application service and

has permissions to the shared

report folder

Existing DOMAIN\\Username

for windows

existing username for UNIX

VAR_APPLICATION_REPORT_PA

SSWORD (Windows only)

The password of the above

user

Table 16

Standalone Agent Installer variables



\EMC\DPA

Linux: /opt/emc/dpa


DRESS


to manage this Agent Valid IP

Address or hostname.

In case of linux IPv6,

%

VAR_AGENT_START_SERVICE Advanced Option to start/stop

the Agent after install

TRUE/FALSE TRUE

Installing DPA

Installing by using command line installation 39


40/182

Table 16 Standalone Agent Installer variables (continued)


VAR_AGENT_ORACLE_DIRECTO

RY


monitoring Oracle. Path where

the Oracle Database device

driver files can be found

Valid Path

Application clustering DPA can be set up in a clustered configuration, with multiple DPA Application Serversworking with a single DPA Datastore Server. Clustering allows the ability for Applicationservers to dynamically start, share workload with other Application servers, and bestopped as demand decreases.

Clustered Application servers provide many benefits:

l Increased resiliency

l Load balancing of workload when placed behind a load-balancing switch that youprovide

l Ability to scale the DPA deployment rapidly

l Flexible, green resource management

l Reduction of single points of failure

Once multiple Application Servers have been configured as a cluster you can start andstop individual application servers based on load, such as powering-on additionalservers for end-of-month reporting or other high-usage periods. You can add new servers

to running clusters to improve performance due to load.Ensure that all cluster nodes are using the same IP type of IP addressing, either IPv4addresses or IPv6 addresses.

Adding an Application server to a cluster during installation

You can configure an extra node to a new or existing cluster in an Application server as acluster as part of installation using the Advanced Options.

The Advanced Options are:

l Do not register DPA services: suppresses the registration of the service with the OSthus preventing them from starting after a host reboot

l Do not start DPA services: suppresses the automatic start of the services after installation

l Install the DPA services as clusterable: Allows you to configure the DPA service todiscover and join any DPA cluster in your environment

Select Install the DPA services as clusterable: and follow the steps in the wizard.

Restrictions and recommendations for clustering

Observe the following restrictions and recommendations when configuring Clusters:

l DPA supports a maximum of four nodes in a cluster:

n

One Master

Installing DPA



41/182

n Three Slaves

l Each cluster of Application servers must be on its own LAN/VLAN.

n Spanning LANs is not possible.

n Clustering is UDP-broadcast based.

l

Clusters can communicate cross-LAN to Datastore.l A physical load-balancing switch should be placed in front of the Application server

cluster to manage the load between DPA Application server objects. The use of software load-balancing switches is not recommended.

l Any configuration accessible via the DPA web console is stored in the Datastore andis accessible cluster-wide. Any configuration operation that requires the use of thedpa executive utility, such as "dpa application promote, is local to the object onwhich it was executed. Adding an Application server to a cluster after DPAdeployment on page 81 and dpa application commands on page 91 provideinformation on the dpa application promote command.

l If you are implementing Application server clustering, ensure that you complete all

cluster configuration before enabling encryption on Application servers.

Datastore ReplicationDPA Datastore Replication enables continuous, safe, and reliable replication so that DPAcan maintain a replica copy, or Slave, of the primary Datastore, or Master , for resilienceagainst a single point of failure. You can add additional slaves in a cascading fashion tothe standard Master Slave configuration if required.

In the event of failure of the Master Datastore, the Slave can be updated to the Master role using the manual failover command, and the Application servers are then configuredto use this new Master. Reconfiguration should normally take the same amount of time to

take effect as the DPA Application and Datastore services startup take. Carrying outDatastore server failover on page 87 provides more information.

There can be only one Master Datastore per deployment. All Datastores are Masters oninstallation. Replication is enabled once a Slave Datastore can communicate with theMaster Datastore. Data starts being replicated when an Application server is started.

You can configure Datastore Replication during the Datastore installation or after installation.

Ensure that all Datastore nodes are using the same IP type of IP addressing, either IPv4addresses or IPv6 addresses.

Configuring Datastore Replication

Procedure

1. Configure the Slave Datastore, either during or after installation.

2. Configure the Master Datastore, either during or after installation.

3. Install or, if already installed, start the Application server.

Installing DPA

Datastore Replication 41


42/182

Configuring Datastore Replication during installation

The option to configure replication is provided at the end of the Datastore installationprocess if you choose to install with Advanced Options. You can choose any of theadvanced options.

When installing the Slave Datastore the Application server chosen should be the sameone that the Master Datastore is using.

Select Do install with advanced installation options and follow the steps in the wizard.Installing the Datastore Service on page 30 provides information. Install the SlaveDatastore first, then the Master Datastore, then the Application server.

Datastore Replication best practices

Observe the following best practices for Datastore Replication:

l You must restart the Datastore service any time the role between Master Datastoreand Slave Datastore is changed.

l Use the replication configuration command dpa ds rep to check the status of replication. Running the dpa ds rep command on the Master Datastore displays if replication is streaming and what the Slave Datastore is. Running on the SlaveDatastore tells you what the Master Datastore is.

l Before exporting a Datastore, ensure that you create an empty directory on theDatastore to which to export the Datastore file set. For example, /tmp/export.

l Master and Slave Datastores should have the same performance specifications andbe installed on the same version of DPA.

DPA postinstallationThe first time you access the DPA web console, you might see a message indicating thatthe DPA Server is starting. This message indicates initialization is in progress, which cantake approximately 10 minutes to complete.

During the initialization time, DPA is creating the database schemas, tables, views, andthe DPA Datastore. It also creates the various system reports and dashboards templates,the default system users, Analysis Engine Rulesets, and various other default and initialobjects. Your network connection time affects the speed at which all these actionscomplete. Ensure that you perform the following steps after installing DPA.

Procedure

1. If you have upgraded or migrated to 6.2, delete the browsing history/cache in your

browser before using 6.2.

2. (Optional) Carry out the following steps to verify whether initialization is still inprogress or completed:

a. Run dpa app status from a command prompt window.

Alternatively: On the DPA Application server, go to \services

\applications.

b. Check the *.rar ; *.ear, and *.war files for *.deployed, *.isdeploying, or .failedextensions.

l If files have an extension of *.isdeploying, then server initialization is still in

progress.

Installing DPA


8/15/2019 Data Protection Advisor 6.2 Installation and Administration Gu

data protection advisor 6.2 installation and administration guide

Documents