emc data protection advisor -...

EMC® Data Protection AdvisorVersion 6.0

Installation and Administration GuideP/N 300-013-677REV 02

FOR ADMINISTRATORS INSTALLING AND CONFIGURING DPA

DPA 6.0 Installation and Administration Guide2

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

Published April 2013

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.

EMC2, 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).

http://support.emc.com

CONTENTS

Chapter 1 Migrating from DPA 5.x to DPA 6.0

Overview....................................................................................................... 8Migrating using the DPA Migration Tool ................................................... 8Unsupported migration ........................................................................... 9

DPA 5.x customizations................................................................................. 9Migrating report menus from DPA 5.8.................................................... 10

Installing DPA 6.0........................................................................................ 12 Installing the DPA Migration Tool ................................................................. 12

Windows............................................................................................... 12Unix/Linux ............................................................................................ 12

Launching the DPA Migration Tool ............................................................... 12 Using the DPA Migration Tool ...................................................................... 13

Migrate connection settings .................................................................. 13Migrate configuration data .................................................................... 13Migrate the datamine data .................................................................... 14Migrate Replication Analysis data ......................................................... 15Check for new data................................................................................ 15

Redirecting existing 5.x collectors to the new server .................................... 15 Decommissioning the DPA 5.x system ......................................................... 15 Troubleshooting.......................................................................................... 15

Chapter 2 Installation and Uninstallation

Overview..................................................................................................... 18 System requirements .................................................................................. 18

Permissions .......................................................................................... 18Port settings.......................................................................................... 18

Pre-installation Checklist............................................................................. 20 Verifying connectivity .................................................................................. 22

RPC Communication.............................................................................. 22WMI Communication ............................................................................. 23Sudo ..................................................................................................... 23

Pre-installation worksheet........................................................................... 24 Installing DPA Server ................................................................................... 26 Split or Enterprise installation ..................................................................... 26 Complete or single-server installation ......................................................... 28 Installing the DPA Agent .............................................................................. 29 Command line installation .......................................................................... 30 Silent installation........................................................................................ 33

Setting the location of the agent persistent store (pfile) ........................ 35Setting the location of the agent initial log file....................................... 35

Installing a patch ........................................................................................ 35 After DPA installation .................................................................................. 36 Clustering ................................................................................................... 36

Adding an Application Node to a cluster................................................ 36Remove an Application Node from a cluster .......................................... 37Restrictions and recommendations ....................................................... 37

Starting and stopping DPA services ............................................................. 38 Uninstalling the software ............................................................................ 38

Uninstalling through userinterface on Windows .................................... 38

DPA 6.0 Installation and Administration Guide 3

Contents

Uninstalling a patch .................................................................................... 39

Chapter 3 Getting started

Logging into DPA......................................................................................... 42Changing the default password ............................................................. 42

Licensing the DPA Server............................................................................. 42Expired licenses.................................................................................... 42Removing a license ............................................................................... 43

Chapter 4 Discovering the environment

Monitoring setup summary ......................................................................... 46 Checking which licenses have been installed .............................................. 47 Monitoring hosts......................................................................................... 47

Performing Discovery on HP-UX and Linux ............................................. 47Importing hosts from a CSV file ............................................................. 47

Monitoring storage arrays ........................................................................... 48Discovering VNX/CLARiiON arrays ......................................................... 48Discovering EMC Symmetrix arrays........................................................ 50Discovering EMC VPLEX arrays............................................................... 50Performing hostless discovery on Symmetrix and VNX/CLARiiON........... 50Monitoring storage arrays that use EMC RecoverPoint ........................... 50

Monitoring data protection servers.............................................................. 51Monitoring CA BrightStor ARCserve........................................................ 51Monitoring CommVault Simpana........................................................... 51Monitoring EMC Avamar ........................................................................ 52Monitoring EMC NetWorker ................................................................... 52Monitoring HP Data Protector ................................................................ 53Monitoring IBM Tivoli Storage Manager (TSM) ....................................... 54Monitoring Oracle RMAN ....................................................................... 55Manually configuring DPA Agent to monitor Oracle database and (or) Oracle RMAN ......................................................................................... 56Before starting the Discovery Wizard ..................................................... 56Monitoring Symantec Backup Exec........................................................ 56Monitoring Symantec NetBackup .......................................................... 57Monitoring Symantec PureDisk.............................................................. 58Monitoring Microsoft Exchange Server................................................... 59

Monitoring Databases................................................................................. 60Monitoring Oracle ................................................................................. 60Monitoring SQL Server........................................................................... 61Monitoring PostgreSQL.......................................................................... 63

Monitoring EMC RecoverPoint ..................................................................... 63 Gathering data from operating systems....................................................... 64

Monitoring a Windows host remotely .................................................... 65Monitoring a host for system data ......................................................... 66

Monitoring tape libraries............................................................................. 66 Switches and I/O Devices............................................................................ 67

Monitoring Fibre Channel switches........................................................ 67Monitoring IP switches .......................................................................... 68Monitoring Xsigo I/O Director ................................................................ 68

File Servers ................................................................................................. 68Monitoring EMC File Storage.................................................................. 69

Backup appliances...................................................................................... 69Monitoring EMC Data Domain................................................................ 69

4 DPA 6.0 Installation and Administration Guide

Contents

Monitoring Oracle ACSLS............................................................................. 70 Disk management servers ........................................................................... 70

Monitoring HP Command View .............................................................. 70Monitoring VMware environment........................................................... 70Monitoring backup servers in a Veritas Cluster Server and Microsoft Cluster Server environment ............................................................................... 71

Chapter 5 Monitored objects and groups

Objects ....................................................................................................... 74 Groups........................................................................................................ 74

Child groups ......................................................................................... 74Configuration group .............................................................................. 74

Object attributes ......................................................................................... 75 Smart groups .............................................................................................. 75

Report output creates objects ............................................................... 75Report output creates a hierarchy.......................................................... 76

Chapter 6 User and system settings

User roles and privileges ............................................................................. 78 LDAP authentication ................................................................................... 78 Digital certificate......................................................................................... 80 Time periods............................................................................................... 80 Schedules................................................................................................... 80 System settings .......................................................................................... 81

Data Collection Agents .......................................................................... 81Server ................................................................................................... 81Replication Analysis.............................................................................. 82Agentless Discovery .............................................................................. 82

Chapter 7 Policies and Rules

Overview..................................................................................................... 84 Policies....................................................................................................... 84

Analysis policies ................................................................................... 84Protection policies ................................................................................ 85Chargeback policies ............................................................................. 86Data Collection policies......................................................................... 87Policy inheritance rules ......................................................................... 88

Generating events from policies .................................................................. 88 Rule Template ............................................................................................. 88 Applying a policy......................................................................................... 89

Chapter 8 Datastore maintenance

Backing up the datastore ............................................................................ 92Exporting the DPA datastore to a file ..................................................... 92Exporting the DPA datastore to Pipe ...................................................... 92Importing the DPA datastore ................................................................. 92

DPA Datastore performance optimization .................................................... 93General tuning ...................................................................................... 93

Chapter 9 Troubleshooting

Troubleshooting installation........................................................................ 96


Contents

DPA installationfailure on Solaris .......................................................... 96Application service installation failure................................................... 96

Viewing log files.......................................................................................... 96Install log file ........................................................................................ 97Server log files ...................................................................................... 97Agent log files ....................................................................................... 97Managing log files................................................................................. 97Erroneous memory data in installer log file............................................ 97

Troubleshooting data collection .................................................................. 97Data collection troubleshooting first actions ......................................... 98Data collection troubleshooting second actions .................................... 98Preparing a log file for submission to EMC Support................................ 98

Troubleshooting client discovery for replication analysis ............................. 99Client discovery using remote execution................................................ 99Client discovery with agent.................................................................. 100General client discovery ...................................................................... 101Synchronizing Incorrect Recovery Point times...................................... 102

Synchronizing the system clock................................................................. 103

Appendix A Analysis policy rule categories

Capacity planning ..................................................................................... 106Assigning alerts for pools and storage array analysis policies.............. 107

Change management ................................................................................ 107 Configuration ............................................................................................ 108 Data protection ......................................................................................... 109 Licensing .................................................................................................. 110 Performance ............................................................................................. 111 Provisioning.............................................................................................. 111 Resource utilization .................................................................................. 112 Service Level Agreements ......................................................................... 113 Status ....................................................................................................... 114 Troubleshooting........................................................................................ 116

Appendix B Available command line operations

dpa CLI command ..................................................................................... 120Command and option abbreviations ................................................... 120dpa application commands................................................................. 121dpa datastore commands ................................................................... 125dpa service commands ....................................................................... 129

Unix users................................................................................................. 131 Running reports from the command line.................................................... 131

Creating the script or batch file............................................................ 131 Loading historical backup job data ........................................................... 132

Job summary reports ........................................................................... 133

Index


CHAPTER 1Migrating from DPA 5.x to DPA 6.0

This chapter describes the process of migrating DPA 5.x installations to DPA 6.0. It contains the following sections:

◆ Overview................................................................................................................... 8◆ DPA 5.x customizations............................................................................................. 9◆ Installing DPA 6.0.................................................................................................... 12◆ Installing the DPA Migration Tool ............................................................................. 12◆ Launching the DPA Migration Tool ........................................................................... 12◆ Using the DPA Migration Tool .................................................................................. 13◆ Redirecting existing 5.x collectors to the new server ................................................ 15◆ Decommissioning the DPA 5.x system ..................................................................... 15◆ Troubleshooting...................................................................................................... 15

Migrating from DPA 5.x to DPA 6.0 7

Migrating from DPA 5.x to DPA 6.0

OverviewDPA versions earlier than version 5.5.1 cannot be upgraded to 6.0. Instead, upgrade earlier versions to DPA 5.5.1 or later and, thereafter migrate your recently updated DPA 5.x data to a new DPA 6.0 server using the DPA Migration Tool.

During the migration process, your DPA 5.x system remains fully operational.

Do not install DPA 6.0 on an existing DPA 5.x server. They cannot co-exist because of port conflicts.

The DPA Migration Tool is a standalone application that analyzes all of your existing DPA 5.x data, alerts you to any potential migration issues, and provides an estimate as to how long the migration will take. The DPA Migration Tool enables you to select the DPA 5.x data that you want to migrate (you can choose not to migrate old data that is no longer of value). In addition, the DPA Migration Tool can be used to change the platform of your DPA system. For example, you can use the DPA Migration Tool to migrate the data from a Windows DPA 5.x system to a Linux DPA 6.0 system.

DPA 6.0 no longer supports 32 bit operating systems for the DPA Server platform, Therefore the target DPA 6.0 Server or Datastore must be a 64 bit operating system.

Note that the DPA 6.0 target system can also be a virtual machine.

Migrating using the DPA Migration Tool

Using the DPA Migration Tool, you can migrate the following:

◆ Nodes

◆ Credentials and licenses

◆ Views and Groups

◆ Users and Roles

◆ Custom Reports, Custom Control Panels, and Custom Report Menus

◆ Scheduled Reports

◆ Chargeback, Protection, and Data Collection Policies

◆ Configuration, status, performance, and backup datamine data

◆ Replication Analysis host and storage data

If you are currently running DPA version earlier than DPA 5.5.1, upgrade your installation to DPA 5.5.1 or later before using the DPA Migration Tool.

To move from DPA 5.x to DPA 6.0 system:

1. Install DPA 6.0 server on new hardware.

2. Install the DPA Migration Tool on DPA 5.x.



3. Run the DPA Migration Tool to analyze the DPA 5.x data, select what data to migrate, and then to copy and merge the DPA 5.x data to the new DPA 6.0 system.

4. Redirect all 5.x collectors to the new DPA 6.0 server. You can either install new 6.0 DPA agents or redirect the existing 5.x collectors.

5. Migrate configuration, datamine, and replication analysis to ensure the latest and newer data has been captured prior to decommissioning the old DPA 5.x server.

6. Decomission the DPA 5.x server.

The migration process should not place a noticeable load on your DPA 5.x system.

Depending on the size of the datamine, the migration process could take from several hours to several days. To reduce the amount of time to move data into your DPA 6.0 system, EMC recommends limiting the amount of historical data that is migrated.

Unsupported migration

There are some aspects of the DPA 5.x system that cannot be migrated to DPA 6.0. These have to be manually migrated.

These include:

◆ Custom report data sources and operators - The Custom report data sources and operators cannot be automatically migrated. If your DPA 5.x system contains custom data sources or operators (provided by engineering or Professional Services), the DPA Migration Tool identifies them.

◆ Analysis rules and assigned analysis - The DPA 6.0 Analysis Engine is based on a different architecture than the DPA 5.x Analysis Engine. Therefore, existing analysis rules cannot be automatically migrated to DPA 6.0. Existing analysis rules will have to be manually recreated as analysis policies in DPA 6.0.

◆ Backup auto-reconciliation policies - Auto-reconciliation policies are not implemented in DPA 6.0 and are considered deprecated.

◆ Datamine maintenance plans - DPA 6.0 does not have a database maintenance plan. In DPA 6.0, data that is collected has a retention period that is set as part of the data gathering configuration. The retention period is fully configurable.

◆ Custom scripts accessing the DPA database schema and scripts using the DPA 5.x API

◆ Direct SQL access to DPA database schema

◆ Menu items of Command and Action type cannot be migrated.

DPA 5.x customizationsSome DPA 5.x customizations will not work with DPA 6.0 and need to be recreated using the functionality provided in DPA 6.0. These customizations include:

◆ Custom scripts accessing the DPA 5.x APIs - DPA 6.0 has a new REST API that is not backward compatible with the DPA 5.x APIs. The new REST API provides all of the functionality of the earlier API. However, any custom scripts that were created to access the DPA 5.x APIs have to be modified to take advantage of the new REST API. Also, DPA 6.0 does not provide the dpa_apitool, as the new REST API can be used with any standard REST client.

DPA 5.x customizations 9


◆ Custom scripts accessing the dpabkupjob tool - The dpabkupjob tool continues to be provided with DPA 6.0. However, there are some CLI parameter changes that might affect custom scripts that use the tool.

◆ Direct access to the DPA 5.x datamine - DPA 6.0 does not provide any direct access to the DPA datastore. Any custom report that uses the Database Query data source to run SQL queries against the DPA datamine will no longer work in DPA 6.0.

Migrating report menus from DPA 5.8

If you migrate report menus from DPA 5.8 to 6.0, you need to add the new 6.0 reports to your report menu because report names as known in 5.8 may have changed or reports may have been deleted.

Table 1 on page 10 lists the 5.8 navigator menus renamed in 6.0.

Table 2 on page 10 lists the changed and reports removed in 6.0 that existed in 5.8.

Table 1 Navigator Menus renamed in DPA 6.0:

Navigator menu name in 5.8 Navigator menu name in 6.0

Collector Errors Agent Errors

TSM Media Reclamation Distribution Media Reclamation Distribution

Table 2 List of changed and removed reports (page 1 of 2)

Changed and removed reports

Audit Log Access Log

Analysis Event reports

Analysis Event Details Analysis Event Details for Capacity Planning

Analysis Event Details for Configuration Analysis Event Details for Data Protection

Analysis Event Details for Media Management Analysis Event Details for Performance

Analysis Event Details for Service Level Management

Analysis Event Details for Status

Analysis Event Details for Utilization

Reports deleted from the Navigator Menu and DPA

DPA Status DPA License Details

Removed NetApp reports

NetApp Configuration NetApp Volume Number of Disk Sizes

NetApp Configuration Comparison NetApp Disk Overview

Volume Priority Configuration vFiler Configuration

NetApp Filer Utilization NetApp Cluster Pair Joint CPU Utilization

NetApp Top 5 Busiest Volumes NetApp Top 5 Fastest Growing Volumes

NetApp Volume Statistics NetApp Future Provisioning



Installing DPA 6.0EMC recommends that you install DPA 6.0 as a new installation on a new host according to the procedures described in Chapter 2, "Installation and Uninstallation."

NetApp Aggregate Utilization by Aggregate NetApp Aggregate Status

NetApp QTree Status Cluster Status

NetApp Raw Capacity NetApp Top 5 Fastest Growing Volumes

NetApp /etc/exports System File Configuration Changes

NetApp /etc/hosts System File Configuration Changes

NetApp /etc/hosts.equiv System File Configuration Changes

NetApp /etc/nsswitch.conf System File Configuration Changes

NetApp /etc/quotas System File Configuration Changes

NetApp /etc/rc System File Configuration Changes

NetApp /etc/resolv.conf System File Configuration Changes

NetApp /etc/snapmirror.conf System File Configuration Changes

NetApp /etc/usermap.cfg System File Configuration Changes

NetApp Configuration Changes

NetApp /etc/exports System File Configuration

NetApp /etc/exports System File Configuration Comparison

NetApp /etc/hosts System File Configuration NetApp /etc/hosts System File Configuration Comparison

NetApp /etc/hosts.equiv System File Configuration

NetApp /etc/hosts.equiv System File Configuration Comparison

NetApp /etc/nsswitch.conf System File Configuration

NetApp /etc/nsswitch.conf System File Configuration Comparison

NetApp /etc/quotas System File Configuration

NetApp /etc/quotas System File Configuration Comparison

NetApp /etc/rc System File Configuration NetApp /etc/rc System File Configuration Comparison

NetApp /etc/resolv.conf System File Configuration

NetApp /etc/resolv.conf System File Configuration Comparison

NetApp /etc/snapmirror.conf System File Configuration

NetApp /etc/snapmirror.conf System File Configuration Comparison

NetApp /etc/usermap.cfg System File Configuration

NetApp /etc/usermap.cfg System File Configuration Comparison

NetApp Aggregate Configuration Fileserver Engineering Overview control panel

Menu items removed from DPA 6 as there were no corresponding reports

• Compliance and Mitigation > SEC > Recovery Times

• Recoverability > Recoverability Workspace

• Recoverability > Replication Configuration

Table 2 List of changed and removed reports (page 2 of 2)

Installing DPA 6.0 11


Installing the DPA Migration Tool◆ If you use iAnywhere, the DPA Migration Tool must be installed on the 5.x server.

Do not close the Command Prompt window that is running in the background when installing the DPA Migration Tool. Closing this closes the DPA Migration Tool.

The DPA Migration Tool package name for each operating system is shown Table 3 on page 12

Windows

1. Double-click DPA-Migrator-<Windows>-<platform>-<build number>.exe, for example DPA-Migrator-Windows-x86_64-6.0.0.243.exe

2. Follow the installation wizard.

Unix/Linux

Note: When installing and running the DPA Migration Tool, you must have a running X server setup. If X server is not running, the user interface fails to launch and the DPA Migration Tool is installed with only the default values.

1. Run chmod +x DPA-Migrator-<platform>-<version>.bin,for example DPA-Migrator-Linux-x86_64-6.0.0.243.bin.

2. Run DPA-Migrator-<platform>-<version>.bin.

Launching the DPA Migration Tool1. To launch the DPA Migration Tool.

• On Windows, double-click dpa-migration.bat, which by default is in: C:\Program Files\emc\dpam\bin.

• On Unix/Linux, run dpa-migration.sh, which by default is in: /opt/emc/dpam/bin.

Table 3 DPA Migration Tool installation packages

Environment Installation package name

Linux 32 bit DPA-Migrator-Linux-x86-6.0.0.bin

Linux 64 bit DPA-Migrator-Linux-x86_64-6.0.0.bin

Solaris 64 bit (SPARC) DPA-Migrator-Solaris-SPARC64-6.0.0.bin

Windows 32 bit DPA-Migrator-Windows-x86-6.0.0.exe

Windows 64 bit DPA-Migrator-Windows-x86_64-6.0.0.exe



Using the DPA Migration ToolThe migration process can be stopped and restarted at any time. This enables you to control when migration occurs, for example overnight or over a weekend. It also enables you to safely stop the migration process if the DPA Migration Tool encounters an error and you want to investigate before continuing the process. This is possible only if the Tool is not installed in breaks or pauses while installing the Tool.

Migrate to DPA 6.0 server in the same order as explained in the following sections:

1. "Migrate connection settings"

2. "Migrate configuration data"

3. "Migrate the datamine data"

4. "Migrate Replication Analysis data"

5. "Check for new data"

Migrate connection settings

1. Launch the DPA Migration Tool.

2. Select Connection Settings.

The Connection Settings must be specified so that the DPA Migration Tool can connect to the DPA 5.x and DPA 6.0 servers.

3. Type the connection details for the DPA 5.x server.

4. Type the connection details for the DPA 6.0 server.

5. Click Next.

6. Click Start.

7. Specify the resolvable hostname of the DPA server and login credentials.

You can leave DPA Controller Port field with the default value unless you have configured a custom port in the version 5.x environment.

Migrate configuration data

Before you start migrating the configuration data, backup current DPA v5.x configuration to a file. To do this:

1. On your DPA 5.x Server, go to File > Export.

2. Select All.

3. Save the exported .wds file on a different server as a long-term file copy of your current configuration.

To migrate configuration data:

1. Select Migrate Configuration Data.

2. Select the configuration objects to migrate.

Using the DPA Migration Tool 13


By default, all configuration information is migrated. There are some interdependencies between the objects so selecting one object might automatically select another.

3. Click Start to check for possible migration issues.

4. The DPA Migration Tool analyzes the data in the configuration database and displays any items that cannot be automatically migrated. These items will have to be manually migrated. The output of this analysis is saved to the dpa6migration.log file, which is in the same directory as the DPA Migration Tool.

5. Click Next.

6. Click Start to migrate the configuration data.

The configuration data can take a few minutes to migrate. If you need to stop the migration, click Stop. The migration process can be restarted at anytime.

7. Click Finish.

Migrate the datamine data

Note that if Windows Authentication is configured in the existing DPA 5.x environment, an SQL authorized user must initiate the Migrator.

1. Select Migrate Datamine Data.

2. Select the datamine data to migrate. By default, all data is selected.

3. Click Next.

4. Select the data to be omitted during the datamine migration, that is the data that you do not want to migrate to the DPA 6.0 system.

5. By default, all historical data is migrated. You can elect to limit the amount of historical data to migrate. However, if you do not have a database maintenance plan or if you have very old data in your DPA 5.x system that is no longer of any value then, select the Skip data field field to determine the dates from which you wish to migrate the available data. Click Next.

6. Click Start to begin the migration.

The DPA Migration Tool analyzes the data in the datamine and displays the results.

This analysis, which could take up to an hour, examines the datamine data and generates the migration jobs that the DPA Migration Tool will use internally to migrate the datamine data. At the end of the analysis, an estimate of how long the migration will take is provided.

7. The datamine data migration process is started.

Migrating the datamine data takes time. Very large DPA 5.x datamines could take days to migrate. You can stop (and restart) the migration process at any time.

8. Click Finish.

Migrate Replication Analysis data

1. Select Migrate Replication Analysis Data.



2. Select the Replication Analysis data to migrate.

3. Click Next.

4. Click Start.

5. Click Finish.

Check for new data

After the initial migration is completed, run the DPA Migration Tool again to check for new data gathered by the DPA 5.x system while the initial migration was taking place. If new data is detected, run the DPA Migration Tool again to update the DPA 6.0 system with the new data.

Redirecting existing 5.x collectors to the new serverAfter all of the DPA 5.x data has been migrated to the new DPA 6.0 installation, the final step of the migration process is to redirect the existing 5.x collectors to the new DPA 6.0 server. Ideally, this can be accomplished through DNS or server name change. Otherwise, each 5.x collector will have to be manually redirected to the new server.

DPA 6.0 is compatible with DPA 5.5.1 and later collectors. Alternatively, you can install a new 6.0 agent. “Installing the DPA Agent” on page 29 provides more information. To redirect Unix/Linux agents, modify the DPA server name in the dpa.config file (typically located in /opt/dpa/etc directory):

# Collector configuration

COLLECTOR_CONTROLLERHOST=<DPA Servername>

To redirect Windows agent, go to the HKEY_LOCAL_MACHINE\SOFTWARE\EMC\DPA\Collector registry setting and modify the CONTROLLERHOST variable and set the value data as brsuk-dpa.

Note: After changing configuration, restart the agent service.

Decommissioning the DPA 5.x systemAfter you complete migrating, login to the DPA web console and inspect the migrated data. After you have verified that the DPA 6.0 system is up-and-running and fully tested, start decommissioning the existing DPA 5.x system.

TroubleshootingIf the DPA Migration Tool encounters a problem, information about the problem is displayed in the DPA Migration Tool console. In addition to the console output, the DPA Migration Tool has extensive logging capabilities. The dpa6migration.log file contains a record of the DPA 5.x data that was read and lists the DPA Migration Tool’s transactions with the DPA 6.0 server. This log file contains the information you need to troubleshoot the problem.

Redirecting existing 5.x collectors to the new server 15


While contacting EMC Support for troubleshooting migration issues, send the dpa6migration.log file and the DPA Migrator database file, dpa6migration.h2.db. If there is a problem migrating the configuration data, then export the DPA 5.x configuration to a WDS file using the DPA 5.x GUI and send that to EMC Support as well.


CHAPTER 2Installation and Uninstallation

This chapter describes how to install the DPA server and agent. It includes the following sections:

◆ Overview................................................................................................................. 18◆ System requirements .............................................................................................. 18◆ Pre-installation Checklist......................................................................................... 20◆ Verifying connectivity .............................................................................................. 22◆ Pre-installation worksheet....................................................................................... 24◆ Installing DPA Server ............................................................................................... 26◆ Split or Enterprise installation ................................................................................. 26◆ Complete or single-server installation ..................................................................... 28◆ Installing the DPA Agent .......................................................................................... 29◆ Command line installation ...................................................................................... 30◆ Silent installation.................................................................................................... 33◆ Clustering ............................................................................................................... 36◆ Starting and stopping DPA services ......................................................................... 38◆ Uninstalling the software ........................................................................................ 38

Installation and Uninstallation 17

Installation and Uninstallation

OverviewDPA supports two system configurations:

◆ Complete server - The server and datastore are installed on the same system. An agent is also installed to manage the system. This option is recommended only for proof of concepts, testing DPA or running in a laboratory scenario.

All production installs should be split application server / datastore server.

◆ Split server/datastore - The split server and datastore servers are installed on two different systems. Two agents are installed: one on the server system and one on the datastore system. When deploying this configuration, install the datastore first and then the server. EMC does not recommend installation of the DPA datastore on NAS storage (CIFS or NFS shares) because NAS and CIFS shares may not have the capacity to manage the I/O. The datastore can be stored on direct attached or SAN storage devices.

DPA provides the following deployment options:

◆ Multiple DPA Applications communicate with one DPA Datastore in cluster.

◆ One DPA Application communicates with one DPA Datastore. System requirements

The DPA Server and Replication Analysis can be installed on 64-bit Linux, Solaris, and Windows. The DPA Agent can be installed on 32-bit and 64-bit AIX, HP-UX, Linux, Solaris, and Windows. The DPA web console runs from any browser with the Flash plugin installed.

The EMC Data Protection Advisor Software Compatibility Guide provides a comprehensive listing of system requirements.

Permissions

Observe the following to avoid installation failure:

◆ You must have Administrator privileges (local or domain with full access) to install DPA.

◆ If User Account Control is enabled on the host, the installer must be launched by Run As Administrator.

Port settings

DPA uses TCP ports 3741, 9002, and 9003 by default for communication (other port numbers can be specified during installation). To ensure communication between the server and agents, the firewalls in the network must be configured to allow communication on these ports. During installation, these ports are checked to see if they are in use. If they are, the Installer prompts you to enter alternate port numbers.

In addition, while installing the DPA Application services, Datastore service, and Agent service ensure that the following ports are free. Installation halts if these ports are not free.

Ports required for installing the DPA Application servicesTable 4 on page 19 lists the ports required to install Application services.



Free ports required for installing the DPA Datastore serviceTable 5 on page 19 lists the free port required to install the Datastore service.

Free ports required for installing DPA Agent serviceTable 6 on page 19 lists the free port required to install the Datastore service.

Table 4 Ports required for installing the DPA Application services

Service Port Port Type

HTTP 9004 TCP

HTTPS 9002 TCP

MANAGEMENT_NATIVE 9999 TCP

MANAGEMENT_HTTP 9005 TCP

MESSAGING 5445 TCP

MESSAGING_THROUGHPUT 5455 TCP

OSGI 8090 TCP

REMOTING 4447 TCP

TXN_RECOVERY 4712 TCP

TXN_STATUS 4713 TCP

Table 5 Free ports required for installing the DPA Datastore services


POSTGRES - PQSQL 9003 TCP

Table 6 Free ports required for installing the DPA Agent service


AGENT - HTTP 3741 TCP

Overview 19


Pre-installation ChecklistThis section contains a checklist of the activities you need to perform in preparation for DPA installation and data monitoring. It also includes a summary of the installation and data monitoring activities.

Table 7 on page 20 provides a worksheet that can be used to capture the networking details for convenience of installation.

Table 7 Pre-installation worksheet (page 1 of 3)

Complete Action Comments

Install DPA

Install the DPA software. Install the DPA server and agent as per the installation instructions.

Set up host computer

Provide two hosts for DPA server installation. One each for the DPA Application Server and Datastore.

To scale the requirements to your site, consult the EMC Data Protection Advisor Server Sizing Calculator available from your EMC Sales representative.EMC recommends that you use a dedicated server. DPA should not be installed on servers already running some other application. For installation in a production environment, you need one host for the Application Service and a separate host for the Datastore Service.

Provide a host for DPA agent installation (optional).

If the DPA server resides on a Oracle Solaris host and you are performing client discovery of Windows hosts, at least one DPA agent must be installed on a Windows proxy host.

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 requirements for the machine might be higher than the minimum specification.

Install the operating system on the DPA Server and agent host and install all required patches.

The operating system must be 64 bit on the DPA server.The operating system on the agent host can be 32 or 64 bit.The EMC Data Protection Advisor Software Compatibility Guide lists the required patches.

Install all required software on the agent host after the until the DPA 6.0 Application Server is ready.

If the agent is installed on a separate computer to the application host being monitored, the agent host might require additional configuration (even if that host is the same host as the DPA Server). For more information about the configuration that must be performed, see Chapter 4, "Discovering the environment."

Set up data protection monitoring

Ensure that the ports between the DPA agent host and the monitored server or devices are open and communication is possible over the protocol.

Chapter 4, "Discovering the environment," 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.

Chapter 4, "Discovering the environment," lists the default settings for the DPA credentials that are installed with DPA.



Prepare the details of the policies that DPA will monitor for compliance.

For data protection reporting, the policies are:• Chargeback Policies - For financial cost analysis of data protection

operations. • Protection Policies - To analyze compliance with RTO and RPO data

protection targets.

Obtain DPA Licenses

• For new non-migrated installations - Obtain DPA licenses for all components that will be monitored.

• For migrated installations - If migrating from 5.x, then existing licenses will be migrated.

A DPA enterprise license is required to log in to DPA after installation. Additional licenses are required for the following:• DPA licenses for the number of clients backed up by supported backup

applications. The exception is Avamar, which is a capacity-based license only.

• DPA license for NetWorker capacity if NetWorker is not licensed through DPA Backup Client licenses. DPA NetWorker capacity license must match the total protected capacity in NetWorker.

• DPA license for Avamar, which must match the total primary capacity and capacity written to Data Domain through Avamar.

• DPA license for VMware, which depends on the number of ESX servers.• DPA license for Symmetrix, which depends on the total local and

replicated capacity.• DPA license for RecoverPoint, which depends on the total capacity that

is replicated for any Symmetrix or VNX arrays. • DPA license for VNX Block arrays, which depends on the number and

model of VNX block arrays. • Starting with DPA 6.0, licenses are not required for VNX File, Celerra,

and CLARiiON.

Set up Symmetrix and VNX/CLARiiON array discovery

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 (SE) host used to discover Symmetrix or VNX/CLARiiON storage arrays.

The EMC Data Protection Advisor Software Compatibility Guide describes the versions of SE required for storage array discovery, and the software that must be installed on the SE 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.

Refer the EMC Solutions Enabler Hosting Guide for Data Protection Advisor Tech Note for performance and sizing the SE host on EMC Online Support.

Provide the SE licenses. The following also apply:• Symmetrix array monitoring requires the base and dev masking

licenses. VNX/CLARiiON array monitoring requires the base license only if the symcfg command is issued.

• A minimum of one gatekeeper per HBA per Symmetrix is required.• 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.

• For Symmetrix discovery, follows the guidelines in the EMC Solutions Enabler Hosting Guide for Data Protection Advisor Tech Note available on EMC Online Support.

• If the Solutions Enabler host is 64-bit, the 64-bit Solutions Enabler version must be used.

Set up monitoring of RecoverPoint (if applicable).

EMC RecoverPoint agent host and application host requirements are listed in Chapter 4, "Discovering the environment."



Pre-installation Checklist 21

http://support.emc.com/





Verifying connectivityThis section describes how to check whether connectivity is established for RPC and WMI, and provides an example sudoers file for sites requiring the use of sudo over root user.

RPC Communication

To check the RPC connection:

1. Open the Run dialog box from the Windows Start menu.

2. Type:

net use \\<servername>\admin$ /user:<username>

3. Click Enter. Type the password.

4. A successful connection should return the following message: "The command completed successfully."

5. Delete the network map. Type:

net use \\servername\admin$ /delete

WMI Communication

To check the WMI connection:

1. Open the Run dialog box from the Windows Start menu.

2. Type WBEMtest and click Connect in the Windows Management Instrumentation Tester dialog box.

3. In the Connect field, type \\<servername>\root\cimv2.

4. In the Credentials fields, type the username and password used to connect to the application host you are monitoring.

Set up Application Host import (if monitoring Microsoft Exchange or a database).

• If a remote agent is being used to import hosts, the DPA server must be able to resolve the agent host.

• If application discovery is being performed without an agent, Windows host discovery uses Remote Procedure Calls (RPC) for Replication Analysis and WMI for System Information. Unix hosts are discovered using SSH or telnet/ftp (root or sudo).

Application hosts in a VMware environment are discovered using VI-SDK by individual ESX credentials or vCenter credentials."Verifying connectivity" on page 22 describes how to check connectivity for RPC and WMI, and provides an example sudoers file.

Define the data protection policies

Prepare the details of the policies that DPA will monitor for compliance.

For replication analysis, the Data protection policy details consist of:• The type or replication, (SRDF/S, SRDF/A, MirrorView, RecoverPoint,

etc.). • Whether the replication is PIT or continuous.• The replication target destination.





5. Click Connect to return to the Windows Management Instrumentation Tester dialog box. Click Query.

6. In the Enter Query field, type:

select * from win32_processor

7. Click Apply. If WMI can connect, data from the application host is displayed.

Sudo

If security requirements do not allow for root credentials to be supplied to DPA, sudo is a workaround tool that can temporarily elevate a user's credentials to root for specific commands configured in the sudoers file. A user can log in to a Unix host as a non-root user, and use sudo to run SCSI commands successfully to discover storage related information for the host. The following is an example of what needs to be added to the sudoers file

# sudoers file.## This file MUST be edited with the 'visudo' command as root.## See the sudoers man page for the details on how to write a sudoers

file.## Host alias specification# User alias specificationUser_Alias CMGU=cmguser# Cmnd alias specificationCmnd_Alias CMGEMC=/<homedir>/IllumAgent/l4magent# Defaults specification# User privilege specificationroot ALL=(ALL) ALLCMGU ALL=NOPASSWD:CMGEMC# Uncomment to allow people in group wheel to run all commands# %wheel ALL=(ALL) ALL# Same thing without a password# %wheel ALL=(ALL) NOPASSWD: ALL# Samples# %users ALL=/sbin/mount /cdrom,/sbin/umount /cdrom# %users localhost=/sbin/shutdown -h now#cmguser ALL=(ALL) NOPASSWD: ALL

Pre-installation worksheetThe following worksheet can be used to capture the connectivity details required when configuring data collection through the Discovery Wizard in DPA.

Table 8 Connectivity details worksheet (page 1 of 3)

Item Value

Network Configuration Information for DPA Server or agent (if agent is remote to DPA server)

Hostname

IP Address

Network mask

Primary DNS server address

Pre-installation worksheet 23


Secondary DNS server address

Gateway

Time zone

Credential Information Needed for Discovery of Virtual Disks through SSH

IP Address of ESX Server

ESX Server Root Credential

Information Needed for LDAP User Authentication (optional)

LDAP Server Name/IP

Use SSL?

LDAP Server Port

LDAP Version

Distinguished Name of Base Directory

Identification Attribute

Credential Information Needed for Discovery of Servers and Arrays

Server Name/IP

SSH Credentials

RPC Credentials

WMI Credentials

Solutions Enabler Host Credentials

RPA Credentials

Credential Information Needed for Monitoring of Oracle Databases

Oracle username and password required

Oracle Service Name and Port, specifically the Oracle SID and TNS port

Oracle Monitor RMANAn oracle user with catalog access to the RMAN schema and the username and password is required

Oracle Oracle Host Name

Oracle Monitor Schema(s)If multiple RMAN schemas are present on one Oracle SID, then each RMAN schema owner and username and password are required.

Credential information needed for SQL Server databases

SQL Database User Account

Table 8 Connectivity details worksheet (continued) (page 2 of 3)

Item Value



Installing DPA ServerThe DPA Server can be installed in two ways:

◆ "Split or Enterprise installation" - This is recommended for large-scale enterprise implementations and all production environment installations.

◆ "Complete or single-server installation" - This is recommended for any proof of concepts, test setup, or in lab environment. It is not recommended for any production installation.

SQL Server Instance

SQL Database Name

PostgreSQL Credentials

PostgreSQL User Account (must be a super user)

Credential information for Servers, Tape Libraries, I/O Devices

CommVault User Account

EMC Avamar User Account

Note: This is not required unless you have changed the username and password defined with Avamar for DPA's use.

HP Data Protector User Account

IBM TSM host, TSM Instance Name, TSM port and TSM username and password for each TSM instance is required

Symantec Backup Exec User Account

Symantec PureDisk User Account

SNMP community string for EMC Data DomainSSH username and password for Data Domain, preferably a separate username and password than the Data Domain’s system administrator default credentials.Both are required because data is collected using both the mechanism

SNMP Community String for EMC Disk Library

SNMP String for Fibre Channel Switch

SNMP Community String for Tape Libraries

SNMP Community String for IP Switch

Table 8 Connectivity details worksheet (continued) (page 3 of 3)

Item Value

Installing DPA Server 25


The server package name for each operating system is shown in Table 9 on page 26.

If you encounter issues during the installation, "Troubleshooting installation" on page 96 provides information.

Split or Enterprise installationA Split server or Enterprise installation involves two stages: "Installing the Datastore Service" and "Installing the Application Service"

Install the Datastore Service first and then, install the Application Service. Installation of the Application service before the Datastore Service results in failure of Application service installation.

The following procedure explains performing a split installation in a Windows 64-bit environment.

Task 1: Installing the Datastore Service

Note: Before you begin the installation, log in as a local administrator or a Domain administrator with full local access. If UAC is enabled on a Windows host, launch the installer by Run as Administrator.

1. Launch the installation.

2. Click Next.

3. Read and accept End User License Agreement. Click Next.

4. In the Installation Options screen, select to install Datastore Service, click Next.

5. If you do not to perform an advanced installation, click Next and follow the installation wizard.

If you want 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 Installation Options screen is displayed. The Advanced Options are:

• Do not register DPA services: Suppresses the registration of the service with the operating system thereby preventing them from starting after a host reboot.

Table 9 Installation packages


Solaris 64 bit (SPARC) DPA-Server-Solaris-SPARC64-6.0.0.bin

Windows 64 bit DPA-Server-Windows-x86_64-6.0.0.exe

Linux 64 bit DPA-Server-Linux-x86_64-6.0.0.bin



• Do not start DPA services: Suppresses the automatic start of the services after installation. You can restart the services through the command line.

• Install with advanced datastore layout: allows you to configure the DPA Service with the required filesystems distributed across different disks to optimize performance.

6. When the DPA Advisor installation is complete, click Done.

Task 2: Installing the Application Service

The Application Service installation process is similar to installing the Datastore Service.

1. Start the installation. Click Next.

2. Accept the End User License Agreement and click Next.

3. In the Choose Install Set screen, choose Application Service. Click Next.

4. As with the Datastore service installation, the Advanced Installation options are available here too.

The Advanced Options are:

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

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

• Install the DPA services as clusterable: Allows you to configure the DPA service to discover and join any DPA cluster in your environment.

If you would like to add an Application Node to a cluster, select Install the DPA services as clusterable and follow the steps in the wizard. "Clustering" on page 72 provides more information.

The rest of the installation is similar to the datastore installation

5. If you have chosen not to do the Advanced Options, you are prompted to select the install folder. Click Next.

6. Review the Pre-Installation Summary, the disk space information in particular, click Install. The installation proceeds.

Note: A datastore connection failure error might occur if the relevant firewalls required to communicate between Application Server and the Datastore are not open.

7. In the Configure Datastore Access step, type the IP addresses for the DPA application nodes that will be using this datastore. Click Add. Click Next.

The installation recommences.

8. Specify the IP address of the DPA server host with which the DPA agent will communicate. Click Next.

9. The DPA Application Service installation is now complete. Click Done.

Split or Enterprise installation 27


Complete or single-server installation

This installation type is not recommended for production environments.

This installs both the DPA application service and datastore service features on the same server.

Note: Before you begin the installation, log in as a local administrator or a Domain administrator with full local access. If UAC is enabled on a Windows host, launch the installer by Run as Administrator.

The following procedure explains installing the DPA Server in a Windows 64-bit environment.

1. Navigate to the location where the package was downloaded.

2. Select the install package, double-click the installer, and click Run. The install commences.

3. Read and accept the license agreement.

In order to accept the agreement, you have to scroll through the agreement and accept the license terms. If not, the option to accept the terms of the License Agreement is not active.

4. Click Next.

5. Select the install set.

Note: The option that you choose here indicates whether you are performing a Complete or a Split installation.

Choose Application and Datastore Service. This installs both the DPA application service and datastore service features. This installs the application and the database on the same server, in single instance and is not recommended for production environments.

6. Click Next.

7. Choose an installation folder. You can retain the default installation folder or choose an alternate location.

8. Further checks are made at this stage and if the prerequisites are met, the pre-installation summary page is displayed. Verify the Pre-Installation Summary.

If required, click Previous to modify the install settings. Else, click Install. The installation begins.

This will start various DPA services.

9. After the installation is complete, click Done.

After the installation is complete, launch the DPA Server and license the Server.



The first time you access the DPA web console, you might see a message indicating that the DPA Server is starting. This is due to some initialization after the initial install. You might experience a delay of approximately 10 minutes before you receive a message indicating that the DPA Server is up.

Installing the DPA AgentThis section describes how to install the DPA Agent using the agent-only installation package.

The agent package name for each operating system is shown in Table 10 on page 29.

The following procedure explains installing the DPA Agent a Windows environment.

1. Launch the installation.

2. Click Next.

3. Read and accept End User License Agreement. Click Next.

4. Choose an installation folder.

5. Verify the Pre-Installation Summary and click Install.

6. Choose the Agent installation options:

• 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 have selected Do not start DPA Agent service, click Next.

Type the fully qualified domain name or the IP address of the DPA Server with which the DPA Agent will communicate.

• 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, specify the directory where the Oracle Database device driver files can be found by the DPA Agent.

Table 10 Installation packages


AIX DPA-Agent-AIX-PPC64-6.0.0.bin

HP-UX IA64 DPA-Agent-HP-UX-IA64-6.0.0.bin

HP-UX PA64 DPA-Agent-HP-UX-PA64-6.0.0.bin

Linux 32 bit DPA-Agent-Linux-x86-6.0.0.bin

Linux 64 bit DPA-Agent-Linux-x86_64-6.0.0.bin

Solaris 64 bit (SPARC) DPA-Agent-Solaris-SPARC64-6.0.0.bin

Solaris 64 bit (x64) DPA-Agent-Solaris-x86_64-6.0.0.bin

Windows 32 bit DPA-Agent-Windows-x86-6.0.0.exe

Windows 64 bit DPA-Agent-Windows-x86_64-6.0.0.exe

Installing the DPA Agent 29


7. Click Next.

8. Type the fully qualified domain name or the IP address of the DPA Server with which the DPA Agent will communicate. Click Next.

9. Click Done to complete the installation.

Command line installationTo install using the command line options:

◆ Unix/Linux

./install.bin [option]◆ Windows

install.exe [option]Where option is one of the options listed in Table 11 on page 30.

Table 11 Installer command line options (page 1 of 4)

Option Description

-? Displays help text

-i [swing | console | silent]

Specify the user interface mode for the installer:swing - Graphical interfaceconsole - console onlysilent - no user interaction



-D <name>="<value>"

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 <variable name>="<value>"

Where:<variable name> and <value> descriptions are as follows:

Variable Name Description Possible values

DebugInfo Enables debug information in installer logs.

Yes and No

installDir Installation location Valid path

installSet Installation set to install Complete | Server | Datastore | Agent

AgentName Host name of agent Valid host name

AgentPort Port number to be used by agent Integer

AgentConcurrency Concurrency value for agent Integer

AgentLoglevel Log level for agent Fatal | Error | Warn | Info | Debug

AgentStatusperiod Status period for agent Integer

AgentAuthdifftime Authdifftime value for agent Integer

AgentMaxlistenerqueuelength Max Listener Queue Length for agent Integer

AgentServertimeout Server timeout for agent Integer

AgentInitFileName Specified the initialization file name to be used

Valid file name


Option Description

Command line installation 31


Variable name Description Possible values

AgentLogFileDir Specified the log file directory to be used

Valid path

AgentLogFileName Specified the agent log file name to be used

Valid file path

AgentPFileDir Specified the pfile directory to be used (Unix only)

Valid path

AgentUseLocalSystem Use local system for agent service con-text

Yes | No

AgentUserDomain Domain name for user in agent service context

Existing domain name

AgentInitFileDir Specified the initialization file directory to be used

Valid path

AgentUserName User name for user in agent service con-text

Existing user name

AgentUserPassword Password for user in agent service con-text

Existing password

AgentServerName DPA Server name to manage this agent Valid DPA server host name

AgentStart Start agent after install Yes | No

AgentNetWorkerInstalled Install NetWorker support Yes | No

AgentNetWorkerRoot Location of base directory for NetWorker Valid path

AgentNetWorkerDir Location of bin subdirectory directory for NetWorker binaries (relative to Agent-NetWorkerRoot)

Valid directory

AgentNetWorkerCanNondefault Can NetWorker be installed in a non-default directory location

Yes | No

AgentSupportOracle Install Oracle support for agent Yes | No

AgentSupportNetWorker Install NetWorker support for agent Yes | No

AgentMaxLogFiles Maximum number of log files to keep Integer

AgentMaxLogFileSize Maximum log file size Integer

AgentRemoteExecDir Location for remote exec agent files to be copied to during remote operations

Valid directory

ServerStart Start server on installation completion Yes | No


Option Description



Silent installationA silent installation is an installation that can be performed without having to manually type values to prompts. To perform a silent installation, a response file is created that contains the values that are to be entered during the installation. The installation software uses the values contained in this response file to perform the installation.

Task 1: Creating a response file

Response files are created using a text editor to enter the installer variable names. The response file format is the following:

installDir=<install_path>

Variable name Description Possible values

ServerUserDomain Domain name for user in server service context

Existing domain name

ServerUserName User name for user in server service con-text

Existing user name

ServerUserPassword Password for user in server service con-text

Existing password

ServerUseLocalSystem Use local system for server service con-text

Yes | No

ServerName Name of server Valid host name

ServerPort Port number used by server Integer

ServerWebPort Port number for server UI Integer

DatastoreStart Start datastore on completion of instal-lation

Yes | No

DatastoreListenAddress Which IP addresses for postgres to listen on

Valid IP address or '*'; IP address is local to system (i.e., localhost, 127.0.0.1, other IP address)

DatastorePort Port number for datastore Integer

DatastoreHostName Host Name for datastore Valid host name

DatastoreDataDir Datastore data directory Valid path

DatastoreTxLogDir Datastore transaction log directory Valid path

DatastoreSupportIPv4 Support TCP/IPv4 for datastore access Yes | No

DatastoreSupportIPv6 Support TCP/Ipv6 for datastore access Yes | No

-uninstall Uninstalls DPA

-f <response filename> Uses filename as a response file to provide default installation values


Option Description

Silent installation 33


serverName=<DPA_servername><variable name>=<value>...

where

◆ <install_path> is the installation path. The <install_path> on Windows must use an escaped backslash ( \\) when specifying a path to install the product.

For example:

C:\\emc\\dpa

◆ <DPA_servername> is the resolvable hostname of the computer on which the controlling DPA server is installed.

◆ <variable name>=<value> are a list of system settings and instructions that can be set during installation. Table 11 on page 30 describes the available installer variable names.

Task 2: Using the response file to perform a silent installation

To use the response file to perform silent installations:

1. Copy the installation package and response file to the host.

2. Type the following command:

Unix systems

install.bin -i silent -f <response filename>

Windows systems

install.exe -i silent -f <response filename>

where

<response filename> is the name of the response file that you created. If the default response file name was used, installer.properties, you do not need to specify -f command line switch or the file name.

The following behavior applies to using the response file with the installer command line options:

◆ The path to the response file might be either absolute or relative to the directory in which the installer resides.

◆ If a response file is specified and exists, all other command line options are ignored.

◆ If a properties file named either installer.properties or <NameOfInstaller>.properties resides in the same directory as the installer, it will automatically be used, overriding all other command line options, unless the -f option is used to point to another valid properties file.

◆ If an installer properties file is specified but does not exist, the default properties file, if present, will be used. Otherwise, any supplied command line options will be used. If no additional options were specified, the installer runs using the default settings.



Setting the location of the agent persistent store (pfile)

Agents store information locally on the file system as part of the data gathering process. This information is stored in a persistent store known as the pfile.

The AgentPFileDir variable allows you to set the directory in which the pfile is located during installation.

To set the pfile location, start the integrated installer with the following argument:

install.[bin or exe] -D options.AgentPFileDir=”<path>”

where

<path> is the location in which you want to install the pfiles.

For example, the following command sets the pfile_location on Solaris to /var/tmp:

./install.bin –console –D options.AgentPFileDir=”/var/tmp”

Setting the location of the agent initial log file

Agents write log files to a location stored in the DPA server. The location can be controlled through the web console. However, when the agent is initializing, it might write some initial debug information to a log file in a different location.

The AgentLogFileDir variable in the options file allows you to set the location of the log files that are created by DPA when the application is initializing.

To set the log file location, start the integrated installer with the following argument:

install.[bin or exe] -D options.AgentLogFileDir=”<path>”

where

<path> is the location in which you want to create the log files.

The following example sets the logfile location to /var/log/EMC/DPA:

./install.bin –console –D options.AgentLogFileDir=”/var/log/EMC/DPA”

"Viewing log files" on page 96 provides more information on log file locations.

After DPA installationAfter completing DPA installation, the datastore initialization must complete before you can launch the DPA web console. There are various ways to verify datastore initialization:

On Windows:

1. Go to <install-dir>\Program Files\EMC\DPA\services\applications

2. Check the \RAR, \EAR, and \WAR application folders for .deploying, .deployed, or .failed file extensions.

Alternatively, open the Task Manager to view status.

On Windows or UNIX:

◆ If both services are installed, in the command prompt, run the dpa svc status command

After DPA installation 35


◆ If just the Datastore or the Agent is installed, in the command prompt,run the individual app and ds commands.

ClusteringClustering is the ability for Application nodes to dynamically start, share workload with other Application nodes, and be stopped as demand decreases. Clustered Application nodes provide many benefits:

◆ Fault tolerance to hardware failure

◆ Load balancing of workload

◆ Workload partitioning

◆ Flexible, green resource management

◆ Reduction of single points of failure

You can add new nodes to running clusters to improve performance due to load. If you install a DPA Application Note, which detects and joins other Application Nodes to join a cluster, you’ll enjoy zero downtime and power-on-demand. You can also monitor clustered servers using DPA.

Adding an Application Node to a cluster

Add an Application Node to a cluster during installationYou can add an application node to a cluster at the time of DPA installation using the UI installer advanced option.

The Advanced Options are:

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

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

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

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

Add an Application Node to a cluster after DPA installation You can add an application node to a cluster after installation of DPA using the dpa CLI.

1. Type dpa application stop to stop the application service. The application service must be stopped before adding to a cluster.

2. Type dpa application promote to promote the application to a running cluster.

3. Type dpa datastore stop to stop the datastore service. The datastore service must be stopped before adding an application node to the datastore.

4. Type dpa datastore configure -add <ip_address> to add the application node to the datastore.



5. Type dpa application configure to verify that you are clustered.

If you have already installed DPA and want to use the UI installer to add an Application Cluster:

◆ uninstall DPA; "Uninstalling the software" on page 38 provides more information.

◆ and re-install DPA choosing the Install the DPA services as clusterable.

Remove an Application Node from a cluster

You remove an Application Node from a cluster using the dpa CLI. This makes the Application Node a standalone Node.

1. Type dpa application stop to stop the application service. The application service must be stopped before removing from a cluster.

2. Type dpa application demote to demote the application from a running cluster.

3. Type dpa application configure to verify that the application is removed from the cluster.

"dpa CLI command" on page 120 provides more information on dpa Clustering CLI commands.

Restrictions and recommendations

Observe the following restrictions and recommendations when configuring Clusters:

◆ Each Cluster must be on its own LAN/VLAN

• Spanning LANs is not possible.

• Clustering is UDP-broadcast based.

◆ Clusters can communicate cross-LAN to Datastore.

◆ EMC does not recommend using load-balancing software in production

Starting and stopping DPA servicesYou might experience delays in launching the web console when starting the DPA services. If the DPA services have just been installed, there is a delay of up to 10 minutes in launching the web console. Similarly, if the DPA services are restarted, there might be a delay of about 3 minutes in launching the web console. The delay is observed for the first time after installing DPA. This is not observed for subsequent launches or restarts.

Note: The DPA services must be running if you want to launch the DPA web console.

EMC recommends that you use the DPA commands to control the DPA services. "dpa CLI command" on page 120 provides more information.

Starting and stopping DPA services 37


Uninstalling the softwareThis section describes how to uninstall the DPA in both Unix/Linux and Windows environments.Change to the installation directory (_uninst) by running the following command:

cd $INSTALLDIR/_uninst

1. Initiate the uninstall process by running the one of following commands:

<install-dir>/emc/dpa/_uninstall/./Uninstall_Data_Protection_Advisor

When uninstalling, a warning indicating that the uninstaller will remove the features that were installed during product installation appears indicating the the database will be removed.

Silent uninstallations

◆ On Unix/Linux machines, start a command shell, navigate to the _uninst directory and type the following command:

./_uninst/<uninstall command> -i silent

◆ On Windows machines, type the following command through the commandline:

install.bin|exe -i silent

Uninstalling through user interface on Windows

1. Select Start > Control Panel > Programs and Features.

2. Uninstall EMC Data Protection Advisor from the list of installed applications.


CHAPTER 3Getting started

This chapter describes how to log in to the DPA web console, change the initial password, and load the license required to enable the software. It contains the following sections:

◆ Logging into DPA..................................................................................................... 42◆ Licensing the DPA Server......................................................................................... 42

Getting started 41

Getting started

Logging into DPAAfter you have successfully installed the DPA Server, launch a browser and connect to DPA Server over http on port 9004 or over https on port 9002.

For example: http://<server_name>:9004

or

https://<server_name>:9002

where <server_name> is the name or IP address of the server or localhost. If you chose a different port number during the installation of the DPA server, change 9002 to that port number.

Use administrator for both the user and password.

If this is the first time you are running DPA, you are prompted to add a license. Navigate to and select the license file or files that have been sent by EMC. For specific information on purchasing licenses for your DPA installation, contact your EMC sales representative.

Changing the default password

After installing the DPA Server and successfully logging into the web console, you are prompted to provide the license keys.

After you have successfully licensed the DPA server, you are prompted to change the default password for users, administrators, and engineers. This is an optional step and is not mandatory.

Licensing the DPA ServerAfter a license has been supplied, DPA licenses are managed through the web console. Select Admin > System > Manage Licenses to add, view, and delete licenses. DPA 6.0 introduces changes to the licensing model to simplify DPA licensing. With this, you no longer require separate licenses for replication and backup. The replication feature is now exposed through the DPA backup licenses and you get visibility into the replication information with a single unified license.

On initial login, you are prompted to provide the license key. Contact EMC Licensing to obtain the DPA licenses and provide this.

If you are migrating from DPA version 5.x to version 6.0, the existing licenses are migrated with your configuration and data.

The Setup Guide launched at initial login to the web console guides you through providing the license keys,

Expired licenses

If a license expires, a license violation warning appears in the report title for reports run from all objects enabled by the expired license. In addition, new objects cannot be added in the web console for module components enabled by an expired license.


Getting started

Removing a license

Removing a license will cause a license violation warning to appear when running reports against objects for that license. New objects of that type cannot be added in the web console until a replacement license is supplied.

Licensing the DPA Server 43

Getting started


CHAPTER 4Discovering the environment

This chapter describes the steps you must take before running the Discovery Wizard to discover the applications and devices in your environment. It contains the following sections:

◆ Monitoring setup summary ..................................................................................... 46◆ Checking which licenses have been installed .......................................................... 47◆ Monitoring hosts..................................................................................................... 47◆ Monitoring storage arrays........................................................................................ 48◆ Monitoring data protection servers.......................................................................... 51◆ Monitoring Databases............................................................................................. 60◆ Monitoring EMC RecoverPoint ................................................................................. 63◆ Gathering data from operating systems................................................................... 64◆ Monitoring tape libraries......................................................................................... 66◆ Switches and I/O Devices........................................................................................ 67◆ File Servers ............................................................................................................. 68◆ Backup appliances.................................................................................................. 69◆ Monitoring Oracle ACSLS......................................................................................... 70◆ Disk management servers ....................................................................................... 70◆ Monitoring VMware environment............................................................................. 70◆ Monitoring backup servers in a Veritas Cluster Server and Microsoft Cluster Server

environment ........................................................................................................... 71

Discovering the environment 45

Discovering the environment

Monitoring setup summaryTo set up an object in DPA to be monitored, follow the steps in Table 12 on page 46.

Table 12 Data monitoring setup summary

Step Description

Install licenses Check that the licenses to monitor your device, host, or environment have been purchased and installed. See "Checking which licenses have been installed"on page 47.

Install the agent If you are monitoring the object from a host other than the DPA server host, you need to install the remote agent. See "Installing the DPA Agent"on page 29.

Install third-party binaries or configure the object for monitoring

This is required for remote or agentless (proxy) data collection.You might need to install binaries on the DPA host or the remote agent host to connect to the monitored object. You also might need to configure an account or connection on the monitored object. The following sections describes the prerequisite configuration for all objects:• "Monitoring hosts"on page 47• "Monitoring storage arrays"on page 48• "Monitoring data protection servers"on page 51• "Monitoring Databases"on page 60• "Monitoring EMC RecoverPoint"on page 63• "Gathering data from operating systems"on page 64• "Monitoring tape libraries"on page 66• "Switches and I/O Devices"on page 67• "File Servers"on page 68• "Backup appliances"on page 69• "Monitoring Oracle ACSLS"on page 70• "Disk management servers"on page 70• "Monitoring VMware environment"on page 70

Create or modify the DPA credential

A credential stores the information used to connect to the monitored object. You might need to modify the default credential or create a new one with the account details from the previous step.

Run the Discovery Wizard

Select Inventory > Object Library > Run Discovery Wizard.

Modify the default Request settings

Because database maintenance plans are not migrated, these must be reviewed to set the retention times of the data per request. This is new in DPA 6.0.Data collection requests are assigned to the object created by the Discovery Wizard. If you want to modify the default data collection, select Policies > Data Collection Policies > Data Collection Policy Library.

Test data collection After at least ten minutes of letting the request run, run a report from the object that should include data (for example, Backup Job Summary or a configuration report).



Checking which licenses have been installedThe options that are available for configuration in the Discovery Wizard depend on the types of licenses that you have installed with DPA. If you do not have the correct license installed, the option to create that device or host is disabled in the wizard.

To see the installed licenses, select Admin > System > Manage Licenses.

Monitoring hostsDPA can monitor database hosts and Microsoft Exchange Server for replication analysis. Use the Discovery Wizard to configure application hosts for monitoring in DPA.

Performing Discovery on HP-UX and Linux

HP-UX

If you are performing discovery for a host on HP-UX 11v1, the following patches must be installed on the HP-UX host prior to the discovery:

◆ PHCO_24504

◆ PHSS_36004

◆ PHCO_31923

◆ PHCO_35743

◆ PHKL_34805

Linux

Retrieving VDISK information on Red Hat and SUSE Linux requires the following library to be installed on the host: libstdc++.so.6.

Importing hosts from a CSV file

You can provide the Discovery Wizard with a comma-separated list of hostname values that you want imported into the DPA Configuration view.

Before you start the Discovery WizardTo perform an import from a CSV file, you must select a text file from the local file system that is in a comma-separated value format. The format of the file must be:

Object_Type, Object_Name, IP_Address, Time_Zone, Platform, Credential_Name

◆ Object_Type - Identifies the type of object (case sensitive). Host, DataDomain, EDL, NearStore, TapeLibrary, EMC File Storage, RecoverPoint, HPEVA, FibreChannelSwitch, XSIGOSwitch.

◆ Object_Name - Identifies the name of the object.

◆ IP_Address - (optional). Identifies the object if it cannot be resolved from its name.

◆ Time_Zone - (optional) The object's time zone as a UTC offset, for example -05:00. If a time zone is not specified, the hosts will be imported without a time zone setting.

Checking which licenses have been installed 47


◆ Platform - Identifies the operating system of the object (case sensitive): LINUX, HP, SOLARIS, WINDOWS, AIX, or UNKNOWN

◆ Credential_Name - (optional) Identifies the credential of the object.

The credentials used to connect to the storage array host must include the following:

• Windows - A user with local or domain administrator rights.

• Unix and Linux - A user with root level rights, or a user with the following SUDO rights:

<user> <computer alias> = NOPASSWD: /<dir>/IllumAgent/l4magent

Where <dir> is the home directory for the user specified in the credential (usually/var/tmp). The SUDO program should support the -p parameter and the -s parameter when the interactive mode is used.

The following must be enabled to ensure communication between the monitored host and the recoverability process:

◆ RPC services should be enabled and accessible to the recoverability agent.

◆ SSHD should be enabled and accessible to the recoverability agent.

◆ FTP/Telnet services should be enabled and accessible to the recoverability agent.

Monitoring storage arrays DPA monitors EMC VNX/CLARiiON, Symmetrix, and EMC VPLEX storage arrays. If these storage arrays are replicated with EMC RecoverPoint, additional configuration is required to enable complete replication analysis.

Discovering VNX/CLARiiON arrays

PortDPA connects to the VNX/CLARiiON on TCP port 443. However, if the VNX/CLARiiON is configured to use port 2163, use port 2163.

DiscoveringEMC VNX/CLARiiON storage arrays must be monitored remotely from an agent running on a different host (such as the DPA server).

DPA discovers all of the storage arrays that are being managed and creates objects in the object library inventory.

You will need to supply the name of the host on which EMC Solutions Enabler is installed.

Setting up EMC Solutions Enabler

Discovering VNX/CLARiiON hosts from DPA requires version 7.4.0.6 of Solutions Enabler to be installed. The following are the steps required.

1. Download EMC Solutions Enabler version 7.4.0.6 from EMC Online Support at http://support.emc.com.


http://support.emc.com


2. Install Solutions Enabler on the DPA server or any supported host able to connect to the VNX/CLARiiON array through HTTPS.

Note: A Solutions Enabler license is not required to discover VNX/CLARiiON.

3. Create a text file with the following CLARiiON information, one line per VNX/CLARiiON:

<SPA IP> <SPB IP> <Username> <Password>

where

• <SPA IP> is the IP address of the first controller (SP-A).

• <SPB IP> is the IP address of the second controller (SP-B)

• <username> and <password> are the account name and password of a VNX/CLARiiON user with view permissions.

The first field must be the first VNX/CLARiiON controller, followed by the second controller.

4. If the Base license of Solutions Enabler exists, run the following command on the Solutions Enabler host to register the VNX/CLARiiON:

symcfg disco -clar -file <filename>

5. If the Base license of Solutions Enabler does not exist, copy the ClarApiDiscovery executable file from the following directory:

Windows

C:\Program Files\EMC\DPA\services\agent\win-x86\policyimport-clar\

Linux/Unix

/opt/emc/dpa/services/agent/<OS - e.g. win-x86_64>/policyimport-clar/

to the Solutions Enabler host.

Run the following command:

Windows

ClarApiDiscovery.exe REGISTER -file=<filename>

Unix

./ClarApiDiscovery REGISTER -file=<filename>

The available platforms are:

• AIX

• HP

• Linux

• Solaris

• Win32

6. Run the following command to confirm that the VNX/CLARiiON has been registered:

Monitoring storage arrays 49


symcfg list -clar

7. If the VNX/CLARiiON is listed, you are ready to run the Discovery Wizard in DPA and configure the VNX/CLARiiON.

Discovering EMC Symmetrix arrays

DiscoveringEMC Symmetrix storage arrays must be monitored remotely from an agent running on a different host (such as the DPA server).

To configure multiple hosts and multiple storage arrays, use the Discovery Wizard. DPA discovers all of the storage arrays that are being managed and creates objects in the object library inventory.

You need to supply the name of the host on which EMC Solutions Enabler is installed.

Discovering EMC VPLEX arrays

PortDPA connects to the VPLEX on TCP port 443.

DiscoveringEMC VPLEX storage arrays can be monitored from the DPA Server or remotely from any host that has DPA agent installed.

DPA discovers all of the storage arrays that are being managed and creates objects in the object library inventory.

Performing hostless discovery on Symmetrix and VNX/CLARiiON

Host discovery as described in"Discovering VNX/CLARiiON arrays"on page 48 requires either the installation of a local agent on the host or the deployment of a remote agent with credentials for host access. Either method might be prevented by customer security policies.

DPA can perform application discovery on storage arrays without needing to connect to the hosts on which applications are hosted. This changes the object hierarchy that appears and the reports that are available in the Replication Analysis area. The EMC Data Protection Advisor Product Guide provides more information.

The prerequisites for hostless discovery are the same as those described in "Discovering EMC Symmetrix arrays"on page 50.

Monitoring storage arrays that use EMC RecoverPoint

If your VNX/CLARiiON or Symmetrix storage arrays are replicated with EMC RecoverPoint, DPA provides replication analysis for RecoverPoint replication operations.

To perform replication analysis for RecoverPoint, you have to configure the VNX/CLARiiON or Symmetrix storage arrays and the RecoverPoint host in DPA in the correct order.

To gather RecoverPoint replication data:



1. Use the Discovery Wizard to create the host object for the Solutions Enabler host that is connected to the storage array replicated with RecoverPoint.

2. Discover the arrays attached to the host.

3. Configure the Symmetrix or VNX/CLARiiON arrays using the Discovery Wizard.

4. Import replication policy data from the storage arrays.

5. Configure the EMC RecoverPoint appliances’ data monitoring, as described in "Monitoring EMC RecoverPoint"on page 63.

6. Ensure that the RecoverPoint Configuration request has been assigned to the RecoverPoint appliance object that handles replication for the storage array. Run this request.

7. After the RecoverPoint Configuration request is run and sufficient time has passed, DPA should have begun gathering replication analysis data for RecoverPoint. Reports can be run from the storage array objects and the Replication Analysis area will show the mapping of storage and recovery points.

Monitoring data protection serversThis section describes how to monitor various data protection servers.

Monitoring CA BrightStor ARCserve

CA BrightStor ARCserve servers are monitored from an agent running on the CA BrightStor ARCserve server or from an agent running on any other Windows computer in the environment.

Before starting the Discovery WizardInstall the ARCserve Manager on the computer on which the agent is running. The agent credentials must match the existing ARCserve account.

You will need to know the resolvable hostname or IP address of the ARCserve server. When running ARCserve 11.x, the hostname must be the host short name (aliases cannot be used).

Monitoring CommVault Simpana

Monitor CommVault Simpana servers from an agent running on the CommVault Simpana database or from an agent running on any other computer in the environment.

Before starting the Discovery WizardThe agent has to run as an account that has permission to access and execute read-only statements in the CommVault database.

You will need to know:

◆ The resolvable hostname or IP address of the CommVault server.

◆ The database hostname and instance name if the CommVault database is remote to the server.

Monitoring data protection servers 51


Monitoring EMC Avamar

Monitor EMC Avamar® servers using an agent installed on any remote computer in the environment, including the DPA Server. Do not install an agent on the EMC Avamar server or storage node.

Before starting the Discovery WizardNo additional software is required to monitor an EMC Avamar server remotely.

To gather data from EMC Avamar, DPA connects directly to the EMC Avamar database. It connects to the mcdb database on the default port for EMC Avamar, which is 5555. If these parameters were modified, change the Avamar Config and Avamar Job Monitor requests to override these parameters with options on the request.

When DPA connects to the database, it uses the viewuser account to log in to the database. If the EMC Avamar installation was modified so that this user does not have permission to log in to the database, or the password for this user has been modified, change the user and password in the Default Avamar Credentials field to reflect the username and password that should be used to connect to the database.

Note: The agent must be installed on a host that is in the same time zone as the Avamar server.

Before you start the Discovery Wizard, you will need to know the resolvable hostname or IP address of the Avamar server.

Monitoring EMC NetWorker

Monitor NetWorker either from an agent running on the backup server or remotely using an agent running on the DPA Server.

Before starting the Discovery WizardIf monitoring NetWorker remotely, the NetWorker client package must be installed on the agent’s host. The NetWorker module uses commands such as mminfo and nsradmin to communicate with the NetWorker server and requires access to the binaries within the NetWorker client package.

If monitoring NetWorker 7.3 or later remotely, the DPA user and the proxy host must be added to the Users list of the NetWorker Administrators User Group. For example, if you are monitoring NetWorker remotely from the host DPAAgentHost and the agent is running as the Windows user DPAAgent, the following line must be added to the Users list of the properties for Administrators:

user=DPAAgent,host=DPAAgentHost

Before you start the Discovery Wizard, you will need to know the resolvable hostname or IP address of the NetWorker server.

Monitoring HP Data Protector

An agent can monitor HP Data Protector servers running on the HP Data Protector Cell Manager or remotely from another computer.



Before starting the Discovery WizardIf monitoring a Cell Manager remotely, follow the same instructions as documented in "Monitoring IBM Tivoli Storage Manager (TSM)"on page 54.

Note: The status request cannot be assigned when monitoring the HP Data Protector server remotely, as it relies on a command (omnisv) that is only available on the Data Protector server.

If you are monitoring a Data Protector environment that uses the Manager of Managers option, you must configure DPA as if monitoring a remote Data Protector server.

To monitor HP Data Protector remotely, the HP Data Protector client software must be installed on the agent’s host and the client must be configured on the Data Protector Cell Manager so that it has permission to run reports.

To test connectivity from the agent host, type:

omnirpt -tab -report list_sessions -timeframe 06/01/01 12:00 06/01/30 12:00

Gathering occupancy data

Gathering occupancy data is not enabled by default for HP Data Protector. To enable occupancy data gathering, the occupancy option for the DataProtector Jobmonitor request must be enabled and the DataProtector Client Occupancy request must be assigned to the Data Protector client in the Edit Request dialog.

Note: Gathering occupancy information for HP DataProtector can have a significant performance impact on the Data Protector server.

omnirpt patch

HP has released a patch for Data Protector 6.1 that must be installed on a Data Protector 6.1 installation before it can be supported by DPA.

Table 13 on page 53 lists the required patch ID by platform.

The patch is available for General Release from HP from www.hp.com. Type the patch ID into the Search field of the HP home page. You are directed to the patch download page.

Table 13 HP Data Protector 6.1 patch IDs

Platform Patch ID

Windows DPWIN_00417

HPUX PA-Risc PHSS_39512

HPUX IA64 PHSS_39513

Linux DPLNX_00077

Solaris DPSOL_00371



Monitoring IBM Tivoli Storage Manager (TSM)

Monitor a TSM server from an agent running on the TSM Server or remotely from an agent running on a different host (such as the DPA server). If you are monitoring TSM remotely, follow the instructions in "Monitoring TSM remotely"on page 55 before configuring the server in DPA.

Before starting the Discovery WizardThe TSM Credential must use the name and password of a TSM Administrator. The Administrative user does not need full system privileges: Analyst or Operator privileges are sufficient.

Select Admin > System > Manage Credentials to modify the TSM Credentials that are created after you have used the Discovery Wizard to create a TSM object.

If the Server being monitored is a shared Library Client, the agent also must query the Server’s Library Manager to gather certain data. By default, the agent uses the same credentials used to query the Library Client to query the Library Manager.

If different credentials are required to access the Library Manager, they can be set using the following DPA environment variables (Unix) or registry settings (Windows):

◆ AGENT_TSM_LIBMGRUSERNAME

◆ AGENT_TSM_LIBMGRPASSWORD

Gresham Clareti EDT

In Tivoli Storage Manager environments that use Gresham Clareti EDT for device control, DPA communicates with EDT to gather device configuration information by reading information from two files:

◆ elm.conf

◆ rc.edt

DPA reads from elm.conf at the following location:

◆ On Windows, an environment variable called EDT_DIR is set by EDT. DPA looks up the location specified in EDT_DIR.

◆ On Unix, DPA looks first in /opt/GESedt-acsls/bin for elm.conf. If not found, on AIX DPA looks in /usr/lpp/dtelm/bin. On other flavours of Unix/Linux, DPA looks in /opt/OMIdtelm/bin.

If the elm.conf file is not present in these directories, the registry variable (Windows) or environment variable (Unix) AGENT_TSM_ELMCONF_FILENAME can be set to the location of elm.conf if required.

DPA reads from the rc.edt file at the following location:

◆ On Windows, DPA looks up the location specified in the environment variable EDT_DIR.

◆ On Unix, DPA looks first in /opt/GESedt-acsls/SSI for rc.edt. If not found, on AIX DPA looks in /usr/lpp/dtelm/bin. On other flavours of Unix/Linux, DPA looks in /opt/OMIdtelm/bin.



If the rc.edt file is not present in these directories, the registry variable (Windows) or environment variable (Unix) AGENT_TSM_RCEDT_FILENAME can be set to the location of rc.edt if required.

Note: Because a TSM environment using EDT requires the agent to read from these files to collect configuration data, the agent must be on the same server as the TSM server.

Monitoring TSM remotelyWhen monitoring a TSM instance remotely, the TSM client software must be installed on the host that will monitor the TSM instance. The TSM module uses the dsmadmc command included with the TSM client software to connect to the TSM instance and gather data.

In a default TSM Client installation on a Windows computer, the administrative components required by DPA are not installed. To install the administrative components:

1. Click Custom when prompted during the TSM client installation.

2. Select Administrative Client Command Line Files and click Next. The TSM client installation continues.

3. After the TSM client installation is complete, initialize the client for the first time by starting the TSM Backup-Archive GUI from the Start menu. Use the wizard to configure the client.

4. To configure the client, accept the default Help me configure the TSM Backup Archive Client value and click Next. Either import an existing options file or create a new one when prompted.

5. Accept the default value Create a new options file. A blank options file (dsm.opt) will have to be created in the baclient directory under the install directory for TSM (default C:\Program Files\Tivoli\TSM).

6. Continue to progress through the wizard. Complete all of the windows in the wizard until a new options file is created.

Monitoring Oracle RMAN

DPA 6.0 no longer ships Oracle client (OCI) libraries with the DPA Agent. Therefore, in order for the DPA Agent to collect data from an Oracle database (or Oracle RMAN), you must provide these libraries and configure the DPA Agent to use them.

You can install either the full Oracle Client (if the DPA agent is deployed on the same host as the Oracle database itself) or the Oracle Database Instant Client, which is a light-weight version suitable for remote data collection. In either case, the DPA Agent must be aware of the directory containing the OCI library.

On Windows this is OCI.DLL and on Unix, it is libclntsh.so.

Note: The library must be for the same platform as the DPA Agent. Example, if a 64- bit Windows DPA agent is installed, then you must use the 64-bit Windows Oracle library.

You can download the Oracle Database Instant for free at http://www.oracle.com/technetwork/database/features/instant-client/index.html


http://www.oracle.com/technetwork/database/features/instant-client/index.html


While installing the DPA Agent, you are prompted to specify if you want to utilize the Agent to monitor Oracle and if so, provide the location of the Oracle client libraries. This action sets a registry setting (on Windows) or modifies an environment variable in the dpa.config file (on Unix). If you change the location of the libraries after the install process is completed, then you need to perform these steps manually.

Manually configuring DPA Agent to monitor Oracle database and (or) Oracle RMAN

◆ To manually configure the DPA Agent to monitor Oracle RMAN:

On Windows, set the HKLM/Software/EMC/DPA/Agent registry of value type REG_SZ as follows:

Value name: ORACLE_CLIENT_PATH

Value data: <directory containing the Oracle client libraries - oci.dll>

Note: The registry key is created if you have selected Oracle database to be monitored option selected while installing the DPA Agent. If the registry key is not created, you must create it manually.

◆ On Unix, modify the dpa.config file

The dpa.config file is available in <installdir>/agent/etc/dpa.config. Search for line, AGENT_ORACLE_CLIENT_PATH=

and set the variable to the directory containing the Oracle client libraries - libclntsh.so.

Restart the Agent service if you have changed the dpa.config file to include the Oracle client path.

Before starting the Discovery Wizard

To monitor Oracle RMAN remotely, the Oracle client must be installed on the agent's host so that the agent process can communicate with the database.

The version of the client installed on the computer must be compatible with the target database to which the agent connects.

Monitoring Symantec Backup Exec

Monitor Symantec Backup Exec servers from an agent running on the Backup Exec server or from an agent running on any other Windows computer in the environment. Also, the DPA Agent service needs to run with a named account that can authenticate with the BackupExec server.

Use Symantec PureDisk server to monitor an agent running on a Unix-based host.

Before starting the Discovery WizardTo monitor a Symantec Backup Exec backup server remotely, the agent must run as a named user account rather than the Local System account. When installing the agent, you are prompted to specify whether the agent runs using the Local System account or as a named user.



The Backup Exec Credentials must use the username and password of a Windows administrator account on the Backup Exec server.

Select Admin > System > Manage Credentials to modify the Backup Exec Credentials that are created after you have used the Discovery Wizard to create a Backup Exec object.

Monitoring Backup Exec RemotelyTo verify that the agent is running, launch the Windows Service Control Manager (Start > Settings > Control Panel > Administrative Tools > Services). Right-click on the DPA agent service and select Properties:

1. Select the Log On tab of the Service Properties panel.

2. Select This Account.

3. Type the username and password of the local administrator account to run the service.

4. Modify the service account details and click OK.

5. Restart the service to activate the changes.

Monitoring Symantec NetBackup

Configure a Symantec NetBackup server to be monitored from an agent running on the NetBackup Master Server or from an agent running on a different host such as the DPA server.

Before starting the Discovery WizardMedia Server Status data can only be collected if an agent is installed on the Media Server itself. It cannot be collected through proxy.

Configuring NetBackup authentication for remote data collectionTo gather data remotely, the following must be configured:

◆ The NetBackup Remote Administration Console, a component of the NetBackup Server software, must be installed and licensed on the agent's host.

◆ The agent’s host must be able to successfully resolve the NetBackup Media Servers.

◆ The NetBackup Master Server must be able to successfully resolve the agent’s host.

To resolve the agent host from the NetBackup Master Server:

Unix

If the NetBackup Master Server is running on a Unix computer, the name of the host on which the agent is running must be added to the bp.conf file on the NetBackup Master Server. To add the host:

1. Open /usr/openv/netbackup/bp.conf for editing and add the following line:

SERVER = Agenthost

where Agenthost is the agent’s hostname. The agent’s hostname must be resolvable by the Master Server.

2. Restart NetBackup on the Master Server for the changes take effect.



Windows

If the NetBackup Master Server is running on a Windows computer, add the name of the agent host through the NetBackup Administration Console:

1. Launch the NetBackup Administration Console and open the Master Server Properties dialog box.

2. Click Servers and add the name of the agent’s host to the list of additional servers that are allowed to access the Master Server.

3. Click OK.

4. Restart the NetBackup services to activate the changes.

Monitoring Symantec PureDisk

Configure a Symantec PureDisk server to be monitored from an agent running on the PureDisk Server or from an agent running on a different host, such as the DPA server. Symantec PureDisk can only be monitored on SUSE Linux 10. The root user cannot be used to gather data from PureDisk.

Before starting the Discovery WizardPureDisk servers implement a firewall that might prevent DPA from gathering data from PureDisk or from communicating with an agent installed on the PureDisk server. To ensure successful data gathering and communications, the following sections describe how to configure the PureDisk server before configuring the server in DPA.

The configuration process depends on the version of PureDisk being monitored.

Manually configuring the firewall (versions of PureDisk earlier than 6.5)

To manually configure the firewall for data collection:

1. Log on to the PureDisk server as the root user.

2. Stop the PureDisk firewall by running the following command:

/etc/init.d/pdiptables stop

3. Edit the file /etc/puredisk/iptables-rules by inserting one of the following lines directly after this line in the file:

-A INPUT –p icmp –j ACCEPT

Note: It is important that the line is inserted at the correct location in the file, otherwise it might not take effect.

• If you are monitoring PureDisk with an agent installed on the PureDisk server, add the following line:

-A INPUT –p tcp –m tcp –-dport 3741 –j ACCEPT

• If you are monitoring PureDisk from an agent running on a different host, add the following line:

-A INPUT –p tcp –m tcp –-dport 10085 –j ACCEPT



4. Restart the PureDisk firewall by running the following command:

/etc/init.d/pdiptables start

Updating the IP tables rules (PureDisk version 6.5)

Manually configuring the firewall will not work for PureDisk version 6.5. To update the PureDisk IP table:

1. Open the following file in a text editor:

/etc/puredisk/custom_iptables_rules

2. If the DPA agent is installed on the PureDisk server, add the following line to the rules file (three columns separated by a tab):

tcp {controller_host_ip} 3741

This allows connections from the controller host to the DPA agent on port 3741 on the PureDisk server.

3. If the DPA agent is installed on a remote host, add the following line to the rules file (three columns separated by a tab):

tcp {agent_host_ip} 10085

This allows connections from the agent host to the postgres database on port 10085 on the PureDisk server.

You can specify a single host or an entire subnet (by including a /mask), as in the following example:

tcp10.64.205.0/24 10085

The /etc/puredisk/custom_iptables_rules file provides additional information on configuring this file.

Monitoring Microsoft Exchange Server

An Exchange Server can be monitored for recoverability from an agent installed on the same host as the Exchange Server or an agent installed remotely.

Note: Microsoft Exchange can only be monitored for replication analysis, and for system information from the Exchange server host.

Before starting the Discovery WizardThe account used to connect DPA to the Exchange server must be a domain user with Exchange read-only administrator rights and local administrator rights. DPA does not support replication analysis for two Exchange information stores on a cluster.

Monitoring DatabasesThis section describes how to monitor Oracle, SQL Server, and PostgreSQL databases.

Monitoring Databases 59


Monitoring Oracle

An Oracle database can be monitored from an agent running on the same host as the Oracle server, or from an agent running on a different host, such as the DPA server.

Before starting the Discovery WizardTo monitor an Oracle database for data protection data, the agent must connect to the database as an Oracle user. To gather data successfully, this user must be able to perform selects on the following tables and views:

◆ V_$INSTANCE

◆ V_$PROCESS

◆ V_$DATABASE

◆ V_$PARAMETER

◆ DBA_DATA_FILES

◆ V_$SYSTEM_PARAMETER

◆ V_$DATAFILE

◆ V_$SESS_IO

◆ V_$SESSION

◆ DBA_FREE_SPACE

◆ V_$SESSMETRIC (Oracle 10 only)

Any user with the SYSDBA role will have these privileges by default, so it is recommended that you specify a user that has the SYSDBA role when configuring the database for monitoring.

If you do not want to use a user with the SYSDBA role to connect, then a separate user can be created and explicitly granted permissions on those tables, as the following example shows:

CREATE USER limited_user IDENTIFIED BY password;GRANT CREATE SESSION TO limited_user;GRANT SELECT ON V_$INSTANCE TO limited_user;GRANT SELECT ON V_$PROCESS TO limited_user;GRANT SELECT ON V_$DATABASE TO limited_user;GRANT SELECT ON V_$PARAMETER TO limited_user;GRANT SELECT ON DBA_DATA_FILES TO limited_user;GRANT SELECT ON V_$SYSTEM_PARAMETER TO limited_user;GRANT SELECT ON V_$DATAFILE TO limited_user;GRANT SELECT ON V_$SESS_IO TO limited_user;GRANT SELECT ON V_$SESSION TO limited_user;GRANT SELECT ON DBA_FREE_SPACE TO limited_user;GRANT SELECT ON DBA_TABLESPACES TO limited_user; GRANT SELECT ON DBA_EXTENTS TO limited_user;

On version 10 of Oracle, add the following line:

GRANT SELECT ON V_$SESSMETRIC TO limited_user;

Replication analysis

To monitor an Oracle database for replication analysis, the agent must connect to the database as an Oracle user able to perform selects on the following tables and views:



◆ Dba_data_files

◆ Dba_temp_files

◆ Dba_tablespaces

◆ V_$datafile

◆ V_$logfile

◆ V_$controlfile

◆ V_$log_history

◆ V_$archived_log

◆ V_$instance

◆ V_$database

◆ V_$parameter

◆ Dict

◆ dba_tab_columns

When monitoring Oracle on a Windows platform, the operating system user specified in the Credential must belong to the group ORA_DBA. On Unix, if Unix authentication is used, no further definition is required in the database.

Updating Oracle statistics

To gather accurate figures on the number of rows and size of tables and indexes, it is important that Oracle statistics are updated on a regular basis. The Oracle documentation contains more details on how to set up a job to update Oracle statistics.

One method to update Oracle statistics on a Schema is to run the following command:

exec dbms_stats.gather_schema_stats(ownname => '***SCHEMANAME***', estimate_percent => 5, cascade => true, options => 'GATHER');

Monitoring SQL Server

An SQL Server database can be monitored from an agent running on the same host as the SQL Server database, or from an agent running on a different host, such as the DPA server.

Before starting the Discovery WizardTo connect to SQL Server using Windows Authentication, the DPA agent must run as a named user and not as the Local System Account. Verify that the service is running as the correct user before proceeding with the configuration of the database.

Agent requirements

The agent needs to be able to connect to the SQL Server master database in order to gather the data required. The agent can either:

◆ Use SQL Server Authentication using the credentials of the request (if set).

◆ Use SQL Server Authentication using the credentials against an explicit master database in the list of databases to be monitored (if set)

Monitoring Databases 61


◆ If these are not set, the agent uses Windows Authentication using the logon ID of the agent process.

If none of these are sufficient to connect to the master database, the request will not gather data.

User account requirements

To gather data successfully, the user account used to connect to the SQL Server database must be granted specific privileges. Any SQL Server user with dbo access will have the correct privileges by default.

If you do not want to connect with a user with dbo access, configure a user with the following:

◆ The user must be mapped to the database with the public role.

◆ The user must be explicitly granted the VIEW SERVER STATE and VIEW DEFINITION privileges (SQL Server 2005 only).

The VIEW SERVER STATE privilege is granted at the server level. The VIEW DEFINITION privilege might be granted at the server level (under the name VIEW ANY DEFINITION) or at the database, schema, or individual object level.

SQL Server 2005 and 2008

To grant server-wide privileges to the SQL Server login used by the agent, including VIEW DEFINITION privileges for all database tables, connect to the SQL Server as an administrator and run:

GRANT VIEW SERVER STATE TO <login\domain>GRANT VIEW ANY DEFINITION TO <login\domain>

However, to grant VIEW DEFINITION privileges for only the specific databases that you want to monitor, connect to the SQL Server as an administrator and run:

GRANT VIEW SERVER STATE TO [login\domain]GRANT VIEW DEFINITION ON DATABASE :: <dbname> TO <username>

Replication analysis

The DPA server must connect as a database user with connect privileges for all of the databases and write privilege for the TEMPDB database. For Windows authentication, the user must be able to connect to all SQL Server databases and should have write privilege for the TEMPDB database.

Monitoring PostgreSQL

A PostgreSQL database can be monitored from an agent running on the same host as the PostgreSQL database or from an agent running on a different host, such as the DPA server.

Before starting the Discovery WizardTo monitor a PostgreSQL database, the agent must connect to the database as a PostgreSQL super user. A super user will have the correct privileges by default. EMC recommends that you specify a super user when configuring the database for monitoring.

To create a super user, the PostgreSQL administrator must be a super user, and create the account as in the following example:



CREATE ROLE xxxxx WITH login superuser password yyyyyy ;

where xxxxx is the new username and yyyyyy the new user's password.

The following parameters will not be populated in the database server parameters table unless you are connecting to the database as a super user:

◆ config_file

◆ data_directory

◆ dynamic_library_path

◆ external_pid_file

◆ hba_file

◆ ident_file

◆ krb_server_keyfile

◆ log_directory

◆ log_filename

◆ preload_libraries

◆ unix_socket_directory

The following items are also unavailable unless you are connecting as a super user:

◆ In the datafile configuration table, the full path to the datafiles cannot be shown, as the path of the file is found in the data_directory parameter. The string (postgres data directory) is shown instead.

◆ In the connection status table, the f_command and f_status fields will not be populated with the right information. These fields will be set to <insufficient privileges>.

Connecting to the database as a super user will populate all fields.

Monitoring EMC RecoverPointEMC RecoverPoint must be monitored from an agent installed remotely (the DPA server, for example).

Before starting the Discovery WizardDPA needs to be able to connect to the RecoverPoint environment Command Line Interface (CLI) through a secure SSH connection on port 22. DPA connects to the RecoverPoint appliance using the default CLI user admin, but any defined user with sufficient privileges to run a CLI command (remotely using SSH) is possible (the monitor account is sufficient).

However, DPA must not connect with the RecoverPoint user boxmgmt (this user is reserved for starting the RecoverPoint installation manager automatically).

Monitoring EMC RecoverPoint 63


Gathering data from operating systemsDPA can gather data from operating systems that enable users to report on operating system configuration, status, and performance. There are several DPA modules that gather different types of information, as described in Table 14 on page 64.

Unix

To perform system monitoring on Unix computers, install an agent on the host that is to be monitored. It is not possible to gather system information remotely from Unix computers.

Windows

To gather performance data from a Windows host, Windows Management Infrastructure (WMI) must be installed on the Windows host you are monitoring.

It is possible to gather all system monitoring information remotely from Windows computers, with the exception of Fibre Channel HBA information. To gather Fibre Channel HBA information, the agent must be installed on the computer. "Monitoring a Windows host remotely"on page 65 provides more details on the steps required to monitor a Windows host remotely.

To set up system monitoring for a system on which an agent is installed, assign the system monitoring requests to the host or group to monitor.

Monitoring a Windows host remotely

All system information can be gathered remotely from a Windows computer with the exception of Fibre Channel HBA information. To monitor a Windows computer remotely, an agent must be installed on another Windows computer. It is not possible to remotely monitor a Windows computer from an agent running on a Unix computer.

Table 14 System monitoring modules

Module Description

Host Gathers basic information about the operating system type.

Disk Gathers configuration, status, and performance information on the disks attached to the host.

Fibre Channel HBA

Gathers configuration, status, and performance information on Fibre Channel HBAs configured on the computer.

File system Gathers configuration, status, and performance information on the file systems mounted to the host.

Memory Gathers configuration, status, and performance information on memory in the host.

NetInt Gathers configuration, status, and performance information on network interface cards in the host.

Process Gathers information on any processes running on the host.

Processor Gathers configuration, status, and performance information on all CPUs on the host.



To monitor a Windows host from another Windows computer, the DPA agent service must run as administrator on the computer performing the monitoring. During the agent installation, type the name and password of an Administrator account on the local computer and the agent service is automatically configured for that user. If this was entered incorrectly during installation, modify the agent service login parameters so that the agent service runs as an Administrative account rather than the Local System account.

Modifying the login parameters of the agent serviceTo modify the login parameters of the agent service:

1. Launch the Windows Services control manager (Start > Settings > Control Panel > Administrative Tools > Services).

2. Select the data collection agent service.

3. Right-click and select Properties from the menu.

4. Select the Log On tab in the Properties dialog box.

5. Select This Account.

6. Type the username and password of the administrator that the service to run as.

7. Click OK and restart the service.

Monitoring activity on a remote computerTo monitor activity on a remote computer:

1. Create a host object for the computer to monitor in the web console. The name of the object is the hostname of the remote host. The hostname must be resolvable from the computer on which the agent that will be monitoring the object is running.

2. Assign requests to that object to specify the data to gather.

3. Mark each request as a proxy request and complete the details.

4. To complete the proxy details, type the name of the host for the agent in the Proxy Host field.

5. Create a Windows credential for the Administrator account on the computer being monitored. This account can be the name of a Local Administrator or that of a Domain Administrator.

6. Notify the agent that will monitor the server of the changes by reloading the agent.

Monitoring a host for system data

Monitor an application host for system data from an agent running on the host or another host in the environment.

Before starting the Discovery WizardSystem data can only be gathered from Unix systems by an agent local to the Unix host.

Gathering data from operating systems 65


Monitoring tape librariesDPA can gather information about tape libraries and the drives within those tape libraries. When specifying a hostname, it is important that the name of the tape library is resolvable from the host that is monitoring the tape library.

Before starting the Discovery WizardThe tape library credentials must contain the read-only community string for the tape library in the Password field of the Credential Properties dialog box. Unless the community string was modified on the tape library, set the community string to Public.

Select Admin > System > Manage Credentials to modify the tape library credentials that are created after using the Discovery Wizard to create a tape library object.

Monitoring the IBM System Storage TS 3500 tape library

Use the Tape Library Specialist web interface to enable Simple Network Management Protocol (SNMP) requests for the IBM System Storage TS 3500 Tape Library. To enable SNMP requests:

1. Type the Ethernet IP address on the URL line of the browser.

2. Select Manage Access > SNMP Settings. In the SNMP Trap Setting field, view the current setting then click to enable SNMP requests.

3. Ensure that the SNMP Requests Setting field is set to Enabled.

Monitoring the IBM TotalStorage 3583 tape library

Configure the Remote Management Unit (RMU) to enable SNMP for the IBM TotalStorage 3583 Tape Library. To enable SNMP:

1. In the RMU, click Configuration.

2. In the SNMP Configuration region, perform the following:

• To enable the feature, select ON in the SNMP Enabled field.

• To enable or disable SNMP alerts, select ON or OFF in the Alerts Enabled field.

• In the Manager field, type the SNMP server address.

• In the Public Name field, type the name of the read-only SNMP community.

• In the Private Name field, type the name of the read/write SNMP community.

3. Click Submit and review the changes.

4. Type the password and click Confirm. Redirect the browser if required.

5. Click Done to reboot.

Monitoring the IBM TotalStorage 3584 tape library

To enable SNMP from the web interface of the IBM TotalStorage 3584 tape library:

1. From the Welcome screen of the Tape Library Specialist Web Interface, select Manage Access > SMNP Settings.

2. In the SNMP Trap Setting field, view the current setting, and select the button to enable or disable SNMP requests.



Alternately, to enable SNMP requests from the operator panel:

1. From the Activity screen of the tape library operator panel, select MENU > Settings > Network > SNMP > Enable/Disable SNMP Requests > ENTER. The screen displays the current status of SNMP requests.

2. Press UP or DOWN to specify ENABLED or DISABLED for SNMP messaging, and click ENTER. The Enable/Disable SNMP Requests screen redisplays the new setting. To accept the new setting and return to the previous screen, click BACK.

Monitoring the Oracle SL24 Tape Autoloader and SL48 tape library

Configure the Remote Management Interface (RMI) to enable SNMP for the Oracle StorageTek SL24 Tape Autoloader or SL48 Tape Library. To enable SNMP:

1. In the RMI, navigate to Configuration > Network.

2. Ensure the SNMP Enabled checkbox is enabled.

3. The Community Name string must be contained in the credentials used to connect to this Tape Library in DPA.

4. Click Submit and review the changes.

Monitoring the HP StorageWorks tape library

Configure the NeoCenter utility to enable SNMP for the tape library. To enable SNMP:

1. Launch the NeoCenter utility from the host.

2. Select Configure from the Main screen menu. The Configure dialog box appears.

3. Select the SNMP Traps tab.

4. In one of the available Trap Address fields, type the IP address of the DPA server.

Switches and I/O DevicesDPA monitors Fibre Channel switches, IP switches, and Xsigo I/O Director devices.

Monitoring Fibre Channel switches

DPa gathers information about ports on Fibre Channel switches, including configuration, connectivity status, and throughput.

When specifying a hostname, it is important that the name of the switch is resolvable on the agent’s host.

Before starting the Discovery WizardTo ensure that Brocade switches return all data, verify that the Fibre Channel Alliance MIB is loaded and enabled on the switch. This MIB might not be installed on the switch by default. To enable FA-MIB support on Brocade switches, log in as an administrator and run the snmpmibcapset command. Change the FA-MIB parameter to Yes. Click Enter to accept the default for the other settings.

For example:

telnet <switch>

Switches and I/O Devices 67


> snmpmibcapsetThe SNMP Mib/Trap Capability has been set to support FE-MIB SW-MIB FA-MIB SW-TRAP FA-TRAP FA-MIB (yes, y, no, n): [yes] SW-TRAP (yes, y, no, n): [enter] FA-TRAP (yes, y, no, n): [enter] SW-EXTTRAP (yes, y, no, n): [enter]>

Monitoring IP switches

When you are specifying a hostname, ensure the name of the switch is resolvable on the agent’s host.

Before starting the Discovery WizardThe IP Switch Credentials must contain the SNMP community string for the IP switch in the Password field of the Credential Properties dialog box. Unless the community string was modified on the IP switch, set the community string to public.

Select Admin > System > Manage Credentials to modify the IP Switch Credentials that are created after you have used the Discovery wizard to create an IP switch object.

Monitoring Xsigo I/O Director

When you are specifying a hostname for the Xsigo I/O Director, ensure the hostname or IP address of the Director is resolvable on the agent’s host.

Before starting the Discovery WizardThe Xsigo Director SNMP credentials must contain the SNMP community string for the Director in the Password field of the Credential. Unless the community string was modified on the Director, set the community string to public.

Select Admin > System > Manage Credentials to modify the default Xsigo Director SNMP Credentials if required, or to create a new credential.

File ServersDPA monitors the EMC File Storage.

Note: EMC File Storage is interchangeably referred to as Celerra File Storage.

Monitoring EMC File Storage

EMC File Storage must be monitored from an agent running on a remote computer, for example, the DPA server.

Before starting the Discovery WizardThe EMC File Storage module gathers information from EMC File Storage through an XML API and directly from the EMC File Storage Control Station. An administrator with specific privileges must be created on the EMC File Storage:



1. Log in to the EMC File Storage Manager web browser interface as an administrator. (You can also use the command line interface to create a DPA administrator.)

2. Navigate to Security > Administrators.

3. Create a new administrator, with a username of DPA, for example.

4. Select Local Only Account and type and confirm a password for the administrator.

5. Select a Primary Group of at least opadmin level of privilege. DPA does not need greater privileges than those assigned by opadmin.

6. Enable the following client access options:

• XML API v2 allowed

• Control Station shell allowed

7. Click OK.

The DPA Credential used to connect to the EMC File Storage must contain the username and password of the EMC File Storage administrator you created.

Backup appliancesDPA monitors and EMC Data Domain.

Monitoring EMC Data Domain

DPA monitors EMC Data Domain backup appliances. For EMC Data Domain 4.8, only Tape Drive and Tape Library Status and Configuration information is returned.

Before starting the Discovery WizardSNMP on port 161 and SSH on port 22 must be enabled on the EMC Data Domain backup appliance. You also need to set the community string. This can be done from the command line.

To enable SNMP on the EMC Data Domain appliance:

1. Log on to the EMC Data Domain appliance console using the sysadmin account.

2. Type the following commands:

snmp add ro-community <string>yessnmp enable

where <string> is the selected community string (for example, public). If SNMP is already enabled, you will have to disable and re-enable SNMP for the new string to take effect.

If you are not using a community string of public, you must change the community string used in the EMC Data Domain Credential.

SNMP settings can also be set through the System Settings tab of the EMC Data Domain Enterprise Manager interface.

Backup appliances 69


Monitoring Oracle ACSLSACSLS cannot be monitored remotely. A DPA agent must be installed on the ACSLS Solaris and AIX host.

Before starting the Discovery WizardThe agent must be installed and running on the ACSLS server that you want to monitor.

After installing the agent, verify that the ACS_HOME value in the DPA.config file matches the location in which ACSLS is installed. Verify that the ACSDBDIR value in the DPA.config file matches the path to the ACSLS DB folder (the default is export/home/ACSDB 1.0).

Disk management serversDPA monitors HP Command View.

Monitoring HP Command View

Monitor a HP EVA Disk Array through HP Command View from an agent running on the Command View host, or remotely from an agent running on a different host (such as the DPA server).

The username and password used to gather data must match a valid username and password defined in the CommandView CIM server (configurable from the CommandView management interface).

DPA gathers data from HP Command View using SMI-Son the default secure port of 5989.

Monitoring VMware environment

Monitor your VMware environment from an agent running on the VirtualCenter Server or remotely from an agent running on a different host (such as the DPA server).

DPA provides a plug-in for VMware that allows VMware administrators to view DPA data protection reports in a tab in the infrastructure client GUI.

Monitoring backup servers in a Veritas Cluster Server and Microsoft Cluster Server environment

To monitor backup servers in Veritas Cluster Server (VCS) and Microsoft Cluster Server (MSCS) environments, an Agent must be installed within the clustered environment so that at only one version of the Agent is running on a physical host. This Agent should be configured within the DPA Server as the name of the Cluster Alias itself rather than that of the physical host that it is running on.

Supported platforms

◆ VCS is supported on Linux and Solaris

◆ MSCS is supported on Windows



The EMC Data Protection Advisor Software Compatibility Guide provides more information on supported platform versions.The following Knowledge Base article, available to all customers with an account, provides information on configuring DPA to monitor clustered servers:

http://solutions.emc.com/emcsolutionview.asp?id=esg117911

If the Knowledge Base article is insufficient to configure DPA to monitor your clustered environment, please contact your EMC Professional Services representative. EMC Support is unable to assist with configuring clustered environments.

Disk management servers 71

http://solutions.emc.com/emcsolutionview.asp?id=esg117911

CHAPTER 5Monitored objects and groups

This chapter describes objects, groups, and smart groups. It contains the following sections:

◆ Objects ................................................................................................................... 74◆ Groups.................................................................................................................... 74◆ Object attributes ..................................................................................................... 75◆ Smart groups .......................................................................................................... 75

Monitored objects and groups 73

Monitored objects and groups

ObjectsDPA discovers the applications and devices in your data protection environment and stores these logical and physical entities as objects in the object library. Discovered objects are grouped into the following categories in the object library:

◆ Applications

◆ Hosts

◆ Storage

◆ Switches

The following rules apply to objects:

◆ No two objects can share the same name

◆ No object can share its name with an alias of another object

The object library enables you to view objects and their attributes. To view the object library, select Inventory > Object Library.

GroupsA group is a collection of objects. For example, you can create a group of objects that are used by an application. This way, when you apply a policy to the group, the policy is applied to all of the objects within the group.

Note: An object can however exist in more than one group.

Child groups

A child group is a group that contains components of a system, such as a file system. Child objects are most often created and assigned automatically during the discovery process. Child objects created automatically by DPA cannot be unassigned. You can create and assign specific types of child objects (for example, file systems or backup clients) to groups.

Configuration group

The Configuration group is created by default. The Configuration group is created with an initial structure that groups the data protection environment into Servers, Switches, and Storage. All data protection hosts, devices, and applications discovered by the Discovery Wizard are first added to the Configuration group. Objects that are unassigned from the Configuration group are not deleted. No data gathering is performed on objects that have been unassigned from the Configuration group, even if the object is assigned to another group.



Object attributesObject attributes extend the information that DPA holds about an object. After an object attribute is created, the attribute can be enabled and assigned a value from any valid object.

When creating or editing an object, attributes are filtered to be associated with one or more specific types of objects, and only to objects with an existing attribute that matches a given value.

For example, an Asset Tag attribute might be created to represent an asset identifier for the physical components of an operating environment (such as hosts, storage arrays, and switches). The Asset Tag attribute need not be assignable to logical components like database instances or processes.

In the attribute definition, the Asset Tag is configured to be associated with a subset of physical object types. You can further configure this attribute to only be associated with physical object types that have an attribute of Business Unit, for example.

Smart groupsSmart groups allow users with administrative privileges to create groups that are populated dynamically with information from the results of DPA reports. A smart group runs a custom report and then creates objects based on the results of the report.

The main benefit of smart groups is that they provide high levels of flexibility. Administrators can set up smart groups to dynamically create lists of objects that match specific business and technical criteria.

To create a smart group, select Inventory > Group Management. Click Create Group and then Create Smart Group.

Report output creates objects

Report output creates objects that return a single set of objects from a report, contained in one or two levels of hierarchy, depending on the Report and objects selected.

You can assign the same items that you can assign to regular objects, including analysis and scheduled reports. DPA can then generate alerts and reports for a smart group outputting objects.

For example, a financial firm might have a convention where the first two characters of each backup client indicate the business unit to which the client is assigned. If the first two characters are a and m, then the backup client belongs to the asset management group. Due to the nature of the business, a large number of clients are created, renamed, or removed daily. Rather than spend a lot of time updating the group configuration each day, the DPA administrator can create a smart group that uses the existing Backup Client Configuration report to list each backup client. In the smart group, the administrator can filter the results to only contain clients that start with a and m.

As DPA automatically updates the client configuration list every time it obtains data from the backup server, this list is kept up-to-date with whatever changes are made within the backup environment.

Other examples include:

Object attributes 75


◆ All backup clients containing exch.

◆ All hosts with an E: drive.

◆ All objects with severity 1 alerts in the last day.

Report output creates a hierarchy

Report output creates a hierarchy that produces a more complex dynamic structure, in which a set of parent objects can be created, and one or more sets of child objects are created for each parent object. One report is used to produce the set of parent objects and another report is run against each created parent object to produce the child objects.

Hierarchical smart groups are usually integrated with external data sources and are used to provide a complete multi-level view of data.

Objects that are returned as results of hierarchical smart groups cannot be associated with scheduled reports.


CHAPTER 6User and system settings

This chapter describes how to change user and system configuration parameters. It contains the following sections:

◆ User roles and privileges ......................................................................................... 78◆ LDAP authentication ............................................................................................... 78◆ Digital certificate..................................................................................................... 80◆ Time periods........................................................................................................... 80◆ Schedules............................................................................................................... 80◆ System settings ...................................................................................................... 81

User and system settings 77

User and system settings

User roles and privilegesA user role is a way to limit the functionality and web console options granted to groups of DPA users, by assigning only specific privileges. User role privileges, such as Create User and Delete User, limit user roles. A user can edit his or her own profile to customize preferences and web console appearance.

Table 15 on page 78 explains the users and user roles created by default.

LDAP authenticationDPA allows the integration of a Lightweight Directory Access Protocol (LDAP) server in the environment so that user passwords do not need to be stored in the DPA database. When a user logs in, DPA communicates with the LDAP server, verifies that the user exists, and authenticates the password against that user stored in LDAP.

DPA supports Microsoft Active Directory and OpenLDAP as LDAP servers. If you have installed DPA on a Unix environment and are authenticating to a Microsoft Active Directory LDAP server, you cannot connect to the Windows host using SSL.

To enable LDAP authentication, select Admin > Users & Security > Manage External Authentication.

Anonymous bindWhen binding anonymously to the LDAP server, DPA connects to the LDAP server without having to connect as a specific named user. This allows basic user authentication.

When authenticating a user using an anonymous bind, DPA must pass the Distinguished Name (DN) of the user to the LDAP server to authenticate it. DPA must determine the full DN of the user when the user logs in.

An example of a DN for a user is:

CN=Mark,CN=Users,DC=eng,DC=company,DC=com

The DN must be specified in the Base Name field when defining a user. When the user logs in to the application, their username is authenticated against the LDAP server.

Table 15 Users and user roles

Users and user roles Default password Privileges

Administrator administrator Can perform all configuration and reporting functions.

Application owner application owner Can perform all reporting functions and modify credential settings.

Engineer engineer Can perform all reporting functions and most configuration functions. Engineers cannot create or modify users or user roles, or modify system settings.

User user Can perform reporting functions only.



The disadvantage of using the anonymous bind method of authentication is that every user you want to log in must be predefined in the application along with the DN of each user. It is sometimes difficult to determine the DN of each user and it is possible to make typing mistakes that might cause authentication to fail. The alternative is to use a non-anonymous bind.

Non-anonymous bindIf a non-anonymous bind is used, DPA connects to the LDAP server as a named user before attempting to authenticate users who log in to the application. By logging in as a named user, DPA has access to search the directory for users. This means that you do not need to specify the DN of each user who you want to have access to the application when creating user definitions.

This means that you do not need to know the full path to each user inside the directory. For example, you could type a value like: John Citizen.

During authentication, DPA searches the repository for users named John Citizen, and regardless of which Organization Unit (OU), they are in, it should find them.

When logging in to the application, DPA attempts to connect to the LDAP server with the username and password specified in the LDAP settings, and searches the directory for that user. Upon finding the user, it attempts to authenticate with the password typed at login.

Auto-LoginAnother advantage of using a non-anonymous bind to connect to an LDAP server is the ability to use the Auto-Login feature. With Auto-Login, there is no need to define user entries in DPA for each user requiring access to the application. Access is granted based on the existence and group membership of a user in the LDAP directory.

Note: Note: h-????The Auto-Login feature is supported when connecting to a Microsoft Active Directory server only. Do not attempt to use this feature with an LDAP server other than Microsoft Active Directory.

If there are members of multiple groups in LDAP, and multiple groups have been defined in the Group Mapping table, they are granted the role that is mapped to the first group in the list of which they are a member. The groups that map to a role with greater permissions should be highest in the list.

If using the Auto-Login feature, do not create a user definition in the application before attempting to log in. The first time the user logs in, DPA authenticates the username and password, and then attempts to determine the role that should be granted based on the values specified in the Default User Role and Group Mapping fields. If a role cannot be determined, the user is not granted access to the application. If the role can be determined, DPA automatically creates a user definition and the user is permitted to log in.

Users who are removed from LDAP are no longer granted access. If a user’s group membership is changed in LDAP, the role is re-evaluated at next login and is updated.

LDAP authentication 79


Connecting to an LDAP server using SSLDPA supports the ability to authenticate to an LDAP server using SSL in environments in which the LDAP implementation uses Microsoft Active Directory. In this configuration, Active Directory must be configured to accept connections using SSL and the DPA server must be installed on a host that is a member of a domain configured on the Active Directory server. The DPA server must be installed on a Windows host.

Connecting to an LDAP Server using SSL is not supported on Unix DPA servers. It is also not supported if the LDAP implementation is something other than Microsoft Active Directory.

Digital certificateDPA uses a self-signed digital certificate for identification and encryption. This certificate expires in five years. To use a certificate that is signed by your own Certificate Authority, you must:

1. Export a certificate request (CRT) file.

2. Ask your Certificate Authority administrator to create a signed certificate in Base-64 Encoded X.509 (CER) format.

3. Import the signed certificate into DPA.

The Online Help provides more information on adding digital certificate.

Time periodsWhen you run a report or create a scheduled report, you must decide the period of time over which the report is run, for example right now or last week. Several predefined time periods are provided by default and you can create custom time periods.

To create a custom time period, select Admin > System > Manage Time Periods.

SchedulesSchedules are used to define when to run a scheduled report or generate a dashboard view block, or to define the backup window specified in the Protection Policy. Several predefined schedules are provided by default and you can also create custom schedules.

A schedule is made up of components that define when each schedule produces certain results or runs certain reports. The Schedule Editor provides two ways to create schedules:

◆ Basic editor - allows you to create and edit schedules using a graphical editor that last up to a week. These schedules repeat every week.

◆ Advanced editor - allows you to create more complex schedules by manually editing the schedule parameters.

Schedules created in the basic editor can be edited using the advanced editor. However, schedules created and saved in the advanced editor cannot be edited in the basic editor.

To create a schedule, select Admin > System > Manage Schedules.



System settingsThis section describes how to modify the default system settings for DPA agents, the server, and the datastore. To view or edit system settings, select Admin > System > Configure System Settings.

Data Collection Agents

Agent settings control the behavior of the agent processes. Table 16 on page 81 describes each agent setting.

Server

The server settings configure global agent and email settings. The server settings are described in Table 17 on page 81.

Table 16 Agent setting

Setting Description

Data Collection Agent Port Port on which the data collection agent listens for requests

Concurrency Maximum number of threads the data collection agent uses to gather data. The default is five

Log Level Verbosity level when the data collection agent writes to the log file. For example, selecting Fatal writes only critical errors to the log file

Max Log File Size (MB) Maximum size to which a log file can grow before the creation of a new log file (in MB). To set no limit for the size of the log file, set this value to 0

Max Number of Log Files Maximum number of log files maintained on the system. If a new file is created because the maximum file size of the current log file is exceeded, the oldest log file is removed.

Max Forward Queue Length Maximum number of reports stored by the agent locally if the Server is offline.

Max Forward Queue Size (MB) Maximum total size of all reports stored by the DPA data collection agent locally if the Server is offline (in MB).

Table 17 Server settings

Setting Description

Binary Multiplier Switching this global setting on, defaults all Agents to use the binary multiplier. It applies to NetWorker agents only and is ignored when monitoring other applications.

Timeout(s) Time out setting that the server uses when talking to the agent. The default is 120 seconds.

Mail Server Host Name Mail server to which email messages are forwarded when sent from DPA.

Mail From Address E-mail address assigned to email messages sent from DPA.

Mail Server Port Mail server port number.

System settings 81


Replication Analysis

The Replication Analysis settings configure client-server time difference. The settings are described in Table 18 on page 82.

Agentless Discovery

The Agentless Discovery settings are described in Table 19 on page 82.

Table 18 Replication Analysis settings

Setting Description

Client-server Time Difference Select the time offset you calculated Client-server Time Difference (in seconds or minutes).

Display dirty recovery points in Replication Status Diagram and Topology Reports

Dirty recovery points are the recovery points that the user does not want DPA to use for RPO calculations like replicas that are used for reporting or test systems. The user can define the dirty recovery points in the data protection policy.

Table 19 Agentless Discovery settings

Setting Description

Agent Response Timeout The time that DPA waits for response from the agent before timeout.

Telnet/SSH Login Prompt Timeout

The time that DPA waits for Telnet/SSH session to be created before timeout.

Telnet/SSH Handshake Timeout

The time that DPA waits for Telnet/SSH handshake before timeout.

Delete files created on the client during agentless discovery

Defines if temporary files will be deleted from the analyzed node at the end of the discovery. The default is that the files will be deleted.


CHAPTER 7Policies and Rules

This chapter introduces the different DPA policies and how DPA policies enhance reporting capabilities. It includes the following sections:

◆ Overview................................................................................................................. 84◆ Policies................................................................................................................... 84◆ Generating events from policies .............................................................................. 88◆ Rule Template ......................................................................................................... 88◆ Applying a policy..................................................................................................... 89

Policies and Rules 83

Policies and Rules

OverviewDPA compares collected data in the datamine to a set of conditions to predict and monitor alert situations that may happen. The set of conditions is defined by a rules and policies.

PoliciesData Protection Advisor policies are a collection of user data about how backup and replication should operate in the environment (recoverability and data protection policies) or about the cost of storage and data protection operations (chargeback policies).

Recoverability, backup, and service level management reports then show how the operations in the environment compare to the policy settings, for example, gaps in the recoverability chain for a storage array, or if a backup server is not meeting a Recovery Point Objective.

DPA provides the following policy types:

◆ Analysis policies - are a collection of one or more rules that are used primarily for generating alerts.

◆ Protection policies - are a collection of user data about how backup and replication should operate in the environment. These policies consist of recoverability and protection rules.

◆ Chargeback policies - are used to determine the cost of storage and data protection operations.

◆ Data Collection policies - are used to determine what data to collect and how often data should be collected. Each policy contains agent requests that collect data.

By default, protection and chargeback policies are off for all objects and groups.

Analysis policies

An analysis policy is a collection of one or more rules that is assigned to an object or group. Rules contain the logic for when to issue an alert. DPA compares collected data in the datastore to the conditions in the rule to trigger alerts. Event-based rules trigger an alert in response to data that is streaming into the DPA server. Schedule base rules periodically check whether to issue an alert. Alerts can contain dynamic textual information and might include populated links to reports. Only analysis policies can generate alerts.

Analysis rule templateAn analysis rule template is a set of instructions that defines the rules logic. When a rule template is added to an analysis policy, the Analysis Engine carries out certain operations and then displays the resulting events in the Advisor section of the web console.

A rule template consists of the name of the rule along with details that specify how that rule is run. It includes the following:

◆ Schedule - determines the hours for which the rule is run.

◆ Period - determines how often it should run within the selected schedule.

◆ Values - are passed to the rule as parameters.


Policies and Rules

For example, a rule template can be created specifying the file system filling up rule and should monitor for partitions whose utilization exceeds 90% in the next hour, every 30 minutes between 9 a.m. and 5 p.m.

A rule template contains multiple rules that apply to different object types. The Analysis Engine only runs the rules that are applicable to a given object. For example, if the object is a switch, then the Analysis Engine will only run the rules in the policy that apply to switches.

Creating an analysis ruleUse the DPA rule editor to create an analysis rule template. The following is a high-level overview of the process. The online help available in the DPA web console provides detailed instructions.

1. In the DPA web console, navigate to Policies > Analysis Policies > Rules Templates.

2. Click Create Rule Template. This open the rules editor.

3. Provide a name and description for the alert that is triggered by this rule.

4. Select a category associated with the rule.

The DPA online help provides information on rule categories and descriptions.

5. Specify whether the rule is event based or a scheduled rule.

An event-based rule triggers an alert in response to data that is streaming into the DPA server. A Schedule base rule runs periodically to check whether to issue an alert.

6. Select the appropriate object types - by hierarchy or by function.

7. Define when and how the alert must be triggered.

Adding an Analysis Rule to an Analysis PolicyAfter a rule template is added to an Analysis Policy, the Analysis Engine carries out certain operations and then displays the resulting events in the Advisor section of the user interface.

The Analysis Policies contain multiple Analysis Rules that apply to different types of objects. DPA automatically applies the appropriate rules from the applied Analysis Policy to an object. For example, DPA applies rules for switches to switches only, not to backup servers.

Protection policies

Protection policies are used to define service level agreements and exposure reporting to calculate whether a backup ran in its backup window and to calculate whether an application or host is meeting its recovery time and recovery point objectives (RTO, RPO). Protection policies also determine how an application, host, or device should be replicated or backed up. Policies are assigned to objects and consist of a set of rules that dictate:

◆ For replication: the type of copy, the replication level, and the schedule.

◆ For backups: the level of backup and the schedule.

Policies 85

Policies and Rules

DPA reports then compare the protection policy for an object to the actual replication or backup taking place to display the level of compliance with policy.

Recoverability checksRecoverability checks are additional consistency checks that are performed by DPA on an environment, if recoverability analysis is configured. A recoverability check verifies that the storage and recoverability environment is configured to a user’s particular requirement (for example, disaster recovery).

If enabled and an inconsistency is detected, a recoverability check generates an exposure just like an exposure generated by a Protection Policy breach or a Recoverability request. Recoverability check exposures are displayed in the Replication Analysis area and the Exposure reports.

There are three system recoverability checks that identify gaps, as described in Table 20 on page 86.

Chargeback policies

Chargeback reports provide the ability to perform a financial cost analysis for backups, restores, and data protection replication operations in a customer’s environment. A cost is calculated for each backup client and can be charged back to the business unit that is responsible for that client or set of clients.

DPA calculates chargeback using two models: one for data backup and restore, and one for the protection and replication of storage data by EMC RecoverPoint. Chargeback is calculated for clients based on the inputs for each type.

Chargeback for backup applications uses the following inputs:

◆ Number of Backups - the number of backups that have been performed by that client during the reporting period.

◆ Backup Size - the amount of data backed up on that client during the reporting period.

◆ Number of Restores - the number of restores that have occurred on that client during the reporting period.

◆ Restore Size - the total amount of data restored by that client during the reporting period.

Table 20 Recoverability checks

Recoverability check Description

Consistency Group Check Checks whether the devices of the recovery point are configured in the same consistency group and the consistency group is enabled. If no consistency group exists, a consistency violation gap is generated for the recovery point.

Consistent Device Replication Check

Checks whether the consistency option was used when the images were created, when applicable. This is a best practice check. If the consistency option was not used, then a Consistency Violation gap is generated for the recovery point.

DR Host Visibility Check Checks whether the devices of a recovery point are mapped, masked, and visible to the Disaster Recovery host. Otherwise, a Consistency Violation gap is generated.


Policies and Rules

◆ Number of Tapes - the number of tapes used by that client during the backup process.

◆ Data Retained - the total amount of data stored for that client on the backup server.

Chargeback for storage uses the following inputs:

◆ Size of data protected - the amount of data protected by RecoverPoint.

◆ Size of data transferred - the amount of data replicated from primary storage by RecoverPoint Appliances.

A Chargeback Policy allows you to specify a value for each of these parameters. The total cost for a client is calculated by adding each of the different cost elements. For example, if you want to implement a chargeback model where you charge $5 for each backup that took place and $0.20 for each GB that was backed up, then you can specify values for these fields in the chargeback policy but not specify values for the other parameters.

Backup client objects are assigned a cost center, which allows Chargeback costs to be calculated by cost center. A default cost center exists for objects that have not been assigned a cost center.

Multiple chargeback policies can be created and different clients or groups of clients can have different policies assigned to them. For example, if you wanted to calculate the chargeback cost for one group of backup clients based on the number of backups performed and another group based on the number of tapes used during the backup process, two chargeback policies can be created and associated with each group of clients.

Data Collection policies

A DPA request contains data on how and when to gather data from an object. You can change the default data collection settings by adding, deleting, and changing request details.

All requests have a default data gathering frequency and a set of options associated with them. When a request is assigned to an object, the request inherits the default settings unless they are overridden in the Edit Request dialog box.

In larger environments, you can assign the same request to multiple objects. If you want all of the requests for these objects to have the same frequency and option settings, you can modify the default settings for the request.

All objects to which the requests are assigned are updated with the changes.

You can gather certain types of data with DPA without deploying an agent on the monitored device. To do this, an agent on another computer (such as the DPA Server) gathers the data remotely. When gathering data remotely, the agent’s host is referred to as a proxy server. The agent uses a protocol to gather data from the remote computer and forwards it back to the DPA server. The protocol used depends on the type of data being collected.

For certain devices types, such as IP and Fibre Channel switches, data must always be gathered remotely as it is impossible to install an agent directly on a switch.

Policies 87

Policies and Rules

To configure remote data collection within DPA, configure the details when assigning requests. If the Discovery Wizard created the objects, this configuration is already created. However, if proxy or credential details have changed, modify the details as required. Retention Periods on Requests are set on individual request using the Edit Request dialog box. By default, the retention period is set to 365 days.

Policy inheritance rules

Each policy type is applied separately to either an object or to a group (child groups without their own policies inherit the parent’s policies). It is best if policies are applied to the highest level group. Policies applied directly to an object will take precedence over the policy applied at the group level. If a policy at the group level is turned off, the policy is also turned off for all of the child objects that inherit the policy. Since objects can be part of multiple groups, the object will inherit the policy of the group which has been most recently applied.

Generating events from policiesWhen a policy finds a matching condition, DPA generates an event. All events are automatically logged in to the DPA datastore and can be viewed in the Advisor section of the web console. Policies can generate an email or send an SNMP trap,.

To monitor an object or group, you must assign an policy to an object in the inventory.

Policies that are assigned to groups are automatically inherited by the objects that are children of that group.

Rule TemplateA rule is the set of instructions used by the DPA Analysis Engine to determine whether a condition has been met and if an alert is generated. For example, the file system filling up rule contains the set of rules to determine if any file systems will exceed the threshold at a certain point in the future.

A rule is used by an Analysis job to perform analysis and alerting based on information within the DPA database. When DPA is installed, a number of pre-defined rules are installed that can monitor for common problems that may occur in the environment. You can use these rules as the basis for creating analysis. DPA provides a rules editor that you can use to create entirely new rules.

The term rule template is used to differentiate the rule definition from the rule instance. The rule template defines the rule's logic. When a rule template is added to an analysis policy, it becomes a rule instance (or a rule) that the Analysis Engine will run. Also, when rule templates are added to a policy, users can specify the values for any parameters. This allows rules to be reused by different policies.

For example A Tier 1 policy might generate an alert when disk space is 80% utilized, while a Tier 2 policy can generate an alert when disk space is 90% utilized. This can be handled with the same rule template that uses a parameter for utilization.


Policies and Rules

Applying a policyPolicies can be applied directly to a group or an object. Policies applied directly to an object always take precedence. When a policy is set at the group level, objects in the group that do not have their own policies inherit the group's policy. The best practice is to apply the policy at the highest group level.

If an object is moved from one group to another group, the most recently applied policy is implemented. For example, if an object is moved from Group A to Group B, the object inherits the policy of Group B.

An administrator or any user with the Edit Node privileges can apply a policy to a group or object.

Applying a policy 89

Policies and Rules


CHAPTER 8Datastore maintenance

This chapter includes the following sections:

◆ Backing up the datastore ........................................................................................ 92◆ DPA Datastore performance optimization ................................................................ 93

Datastore maintenance 91

Datastore maintenance

Backing up the datastoreEMC recommends that the DPA datastore be regularly backed up.

Exporting the DPA datastore to a file

With this export format, 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-<date-and-time>.part.<x> ; where x denotes the part number of the export. A new part number is created if the export file is greater than the maximum export file size. This maximum can be adjusted using the --maxsize option.

Type the following command from a command line prompt.

dpa datastore export [options]

The following options are available:

◆ -u - exports the datastore to an uncompressed data file.

◆ -m - sets the maximum export file size, where the file size is specified as <number>M|G . If this option is not specified, the default export file size is 10 GB.

• M - exports file size in megabytes

• G - exports file size in gigabytes.

The exported datastore file is saved to the same directory where the export command was run. If the maximum export file size is specified, then one or more export files are created (they are identified as .part.1, .part.2, .part.3, and so on).

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

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.

Before you start:

1. Stop the DPA Application.

2. Import the datastore.

3. Start the DPA Application.

From a command line prompt, type the following:



dpa app stopdpa datastore import [options] <filename>dpa app start

Where <filename> is the previously exported datastore file.Use the -u option to import an uncompressed datastore file.

The import command will replace the existing datastore contents with the contents contained in the datastore export file.

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

DPA Datastore performance optimizationThe DPA Datastore ships with a default configuration aimed the best engineering estimate as to how an average database on an average hardware should be set up.

General tuning

During installation, the installer tunes the DPA Datastore Service for the host environment on which it is being deployed. This tuning 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 following command on the Datastore host:

dpa datastore configure --tune

Note: Restart the datastore for the new parameters to be applied. Subsequently, restart the connecting application service(s).

Hardware issuesFor 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. Following are some guidelines to consider when commissioning hardware for your Datastore host:

◆ Disk types - Fast Ultra-320 SCSI disks are the best option. You can also use the high-end Serial ATA (SATA) drives. With SATA, each disk is substantially cheaper and with that you can afford more spindles than with SCSI on the same budget.

◆ RAM - RAM is directly proportionate to the disk cache. This greatly impacts performance considering the fact that memory I/O is very fast than the disk I/O.

◆ RAID Controller - Ensure that the RAID controller can keep up with eight fast HDDs.

◆ Disk configuration - The optimum configuration is RAID 1+0 with as many disks as possible and with your transaction log on a separate disk or stripe. RAID 5 is not a very good option for databases unless you have more than 6 disks in your volume.

A typical high performance configuration contains:

◆ Two disks in mirror for the OS and DPA Datastore binaries

◆ Two disks in mirror for the Datastore transaction log

◆ Four disks in RAID 10 for the Datastore data files

DPA Datastore performance optimization 93


Note: Make sure that operating system partitions and RAID stripe boundaries are aligned and undertaken when the partitions are created.

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.


CHAPTER 9Troubleshooting

This chapter provides assistance on troubleshooting configuration and data gathering problems that might be encountered in DPA. It also describes how to tune the server to scale to your environment. It includes the following sections:

◆ Troubleshooting installation.................................................................................... 96◆ Viewing log files...................................................................................................... 96◆ Troubleshooting data collection .............................................................................. 97◆ Troubleshooting client discovery for replication analysis ......................................... 99◆ Synchronizing the system clock............................................................................. 103

Troubleshooting 95

Troubleshooting

Troubleshooting installation

DPA installation failure on Solaris

DPA fails to install on Solaris SPARC 64-bit with the following error message:

The included VM could not be unarchived (TAR). Please try to download the installer again and make sure that you download using ’binary' modecopy. Please do not attempt to install this currently downloaded copy.

Ensure that gnu tar is installed and available in the PATH ahead of the native Solaris version before running the installer.

For example, through the command line,

1. cd /usr/sfw/bin/

2. ln -s gtar tar

If you are using Bourne shell, type,

export PATH=/usr/sfw/bin:${PATH}

IMPORTANT

The gtar version must be available on the Solaris host before executing the DPA 6.0 installer. Else, it will result in errors in the DPA 6.0 installation binaries.

This pertains to issue number DPA-21289.

Application service installation failure

If the Application service installation fails or cannot complete, ensure that you have installed the Datastore service first. The required installation order is:

1. Datastore service

2. Application service

Viewing log filesLog files provide important information when troubleshooting problems.

Note: The following section describes the log file locations for a standard DPA installation. If the default installation directory was changed during installation, the location of the log directory will be different.

By default, logs only contain warnings and error messages. These may not provide enough information when troubleshooting complex problems. To change the log detail level, select Admin > System > Configure System Settings.


Troubleshooting

Install log file

The Data_Protection_Advisor_Install_[two-digit date]_[two-digit month]__[year]_[two-digit hour]_[two-digit minute]_[two-digit seconds].log file is generated during installation and contains all log messages. For successful installations, this file can be found in the install directory (for example, /opt/emc/dpa). For unsuccessful installations on Unix platforms, the file can be found in the root of the system drive. On Windows platforms, the file can be found on the desktop.

Server log files

The server log files are generated in the following locations:

◆ Unix: /opt/emc/dpa/services/logs

◆ Windows: C:\Program Files\EMC\Data Protection Advisor\services\logs

Agent log files

The agent log files are generated in the following locations:

◆ Unix: <installdir>/agent/logs

◆ Windows: C:\Program Files\EMC\Data Protection Advisor\agent\log\agent.log

Managing log files

When a log file reaches its maximum size, and the maximum number of log files exist in the log file directory, the oldest log file for that process is deleted and a new log file created. You can modify the maximum log file size and maximum number of log files. You can also change the location of log files, if required.

Erroneous memory data in installer log file

The Free Memory and Total Memory data indicated at the top of the installation log files is erroneous. The correct Free Memory and Total Memory data is located further down in the log file, under STDERR ENTRIES.

The Corrected Total Memory data indicated under Executing IAUpdatePostgesconfFile: [INFO] refers to data being used for the DPA datastore service.

Troubleshooting data collectionThis section describes the steps that can be taken to diagnose problems when trying to gather data. The following scenario is assumed:

◆ DPA was successfully installed.

◆ The Discovery Wizard was successfully run to create the object to monitor.

◆ Requests have been assigned to the object and the agent has been reloaded.

◆ Sufficient time (fifteen minutes) has passed to allow the agent to gather data.

◆ An appropriate report has been run that returns no data when data should exist for the object.

Troubleshooting data collection 97

Troubleshooting

Data collection troubleshooting first actions

1. Verify that the time period selected for the report is correct.

2. Check that the correct requests have been assigned to the object.

Select Policies > Data Collection Policies > Data Collection Policy Library. Select the policy that contains the object > Edit to ensure that the request is enabled.

3. Rerun the report.

Review any errors returned by the Agent Errors report and take corrective action if possible (for example, an authentication problem that needs to be resolved).

Data collection troubleshooting second actions

If the first round of steps do not resolve the problem, perform the following:

1. If no resolvable agent errors are reported, select Admin > System, click Configure System Settings, and verify the data collection agent settings.

2. If the status shows that the agent is active, verify that the process is active on the operating system on which the agent is installed.

3. Run the Agent log reports in the web console followed by the Agent Status, and then the Data Collection History report.

4. Rerun the report. If the report continues to show no data, open the agent log and look for any problems. For example, was an incorrect value entered during agent installation. "Viewing log files" on page 96 describes how to view the log files.

Preparing a log file for submission to EMC Support

When submitting a log file to EMC Support, steps can be taken to ensure that the log file contains the relevant information and unnecessary log entries are minimized.

To prepare a clean log file:

1. Set the Log Level of the process to Debug in System Settings, as described in "Viewing log files" on page 96.

2. Stop the agent process.

3. Navigate to the directory in which the log file is stored. Rename or remove all existing log files for the process.

4. Restart the process.

Restarting an agent reloads all the requests assigned to that agent and starts the data gathering routine. This ensures that all requests have been attempted. Starting a new log file removes the need to search through unnecessarily long log files for a problem.

5. Select the related Data Collection Policy and select the History button. Or run a Agent History report.

6. Rerun the report to confirm data is not being gathered.

7. Set the Log Level of the process back to Info in System Settings.

8. Make a copy of the log for submission to EMC Support.


Troubleshooting

Troubleshooting client discovery for replication analysisThis section describes the steps that can be taken to diagnose problems when trying to configure VNX/CLARiiON or Symmetrix storage arrays for replication analysis. The following scenario is assumed:

◆ DPA was successfully installed.

◆ The DPA server and the storage array host meet the requirements as specified in the EMC Data Protection Advisor Software Compatibility Guide.

◆ EMC Solutions Enabler has been successfully installed.

Client discovery using remote execution

Table 1 on page 99 describes possible problems and solutions encountered when attempting to discover clients remotely (without a DPA agent).

Table 1 Client discovery problems and solutions (page 1 of 2)

Problem Solutions

Client discovery fails: No authentication defined, or unable to log in.

• Create a credential in DPA (Admin > System > Manage Credentials) and assign it to the client.

• Check that the username and password supplied with the credential is able to connect the client.

• Ensure su or sudo are not needed to connect, and if so that the correct parameters are supplied in the credential.

Client Discovery fails: Failed to connect to client using RPC, or a specified logon session does not exist.

• Check that the username and password supplied with the credential is able to connect the client.

• Ensure you supplied the username along with the domain name: <domain>\<username > for remote computers, <computer name>\<username> for local computers. In most cases localhost\<username> can be used.

• Check if the host is accessible from the DPA server using the admin share: \\hostname\Admin$

• If the error exists after you tried all the preceding actions, change the Log on as value for the DPA server service from local system to any other user with administrator privileges. A local administrator also can be set.

Client Discovery failed: Failed to connect to client using RPC. The network path was not found.

• Check if the client's Name, IP, or Alias is defined correctly and reachable from the DPA server.

• Check if the host is accessible from the DPA server using the admin share: \\hostname\Admin$

If the share is not accessible, check that it is not blocked by a firewall.

Client Discovery failed: User does not have enough privileges to get the device mapping information.

• Follow the system requirements for remote execution permissions.

• Assign a user with administrator capabilities to the credential.• Check that the user that connects to the client has write and

execute privileges to the path /var/tmp. (Unix)

Troubleshooting client discovery for replication analysis 99

Troubleshooting

Client discovery with agent

Table 2 on page 100 describes possible problems and solutions encountered when attempting to discover clients using the DPA agent.

Client Discovery failed: Failed to send file for discovery to client using SCP orFailed to send file for discovery to client using FTP.

Check for free disk space in /var/tmp.

If the DPA Server is installed on Solaris host and you would like to run a request on a Windows host without installing a local agent, you must run the request trough a proxy (a Windows host that has an agent installed on it).If the proxy host does not resolve the DPA server name correctly (DNS issues), the following error will appear in the request history log:"Error Running Request: No Data"(The following error will also appear in the Agent Log:Detail: get host by name failed in tcp_connect() )

Ensure the DPA server is resolvable from the Windows Proxy host. The DPA server name might need to be added to the hosts file.

Client Discovery fails: Error (977). Overlapped IO operation in progress.

Verify that there is no antivirus software installed on the host; antivirus software might be blocking the irxsvs.exe operation. Disable antivirus blocking by authorizing the irxsvs.exe file in the anti-virus software.

Client discovery fails with the following error:<client_name> irx errMsg: Unable to connect host:<client_name> with user:<domain>\<username> using RPC irx output: Error (1203): No network provider accepted the given network path.

Ensure that the following services are running: Server, Computer Browser, and Workstation.

When using sudo, the Host Config request might fail to return volume group information on AIX hosts with the following message:SymMapVgShow exited with code 161 (SYMAPI_C_VG_NOT_AVAILABLE) SessionId: 0 - for VG:<vg_name> with type: 2(AIX LVM) VolumeGroup information will not be parsed.

This occurs only when the credentials are configured to use sudo. Add the following line to the sudoers file: Defaults env_keep += "ODMDIR"

Table 1 Client discovery problems and solutions (page 2 of 2)

Problem Solutions

Table 2 Client discovery with agent problems and solutions

Problem Solution

Client Discovery request is using remote execution instead of using the installed agent.

1. Ensure that the agent is installed on the host.

2. Ensure that the DPA server is defined as the controller for the agent.

3. Restart the agent service.


Troubleshooting

General client discovery

Table 3 on page 101 describes general possible problems and solutions encountered when attempting to discover clients from DPA.

Table 3 General client discovery problems and solutions (page 1 of 2)

Problem Solution

Client discovery finished with warnings:Failed to discover application storage objects for application <application_name> on client <client_name>.

• Check if the application is running and available for connection.

• Check if the user configured in the DPA credential has enough privileges to query the application's system data.

Client discovery failed: can’t connect to any IP. • Check that port 25011 from the host to the DPA server is not blocked by a firewall.

Client discovery finished with warnings:Home directory was not found for application.

1. Select Admin > System > Manage Credentials.

2. Click Edit to edit the Credential.

Unsupported File System Type encountered: <filesystem_name>.

This file system type is not supported by DPA.To avoid this warning in the next client discovery, you can ignore discovery for this file system.

Note: DPA will not display recovery data for this file system.

Client discovery failed with the error:Please verify that you have enough disk space and write permission.orFailed to unpack file on client <client_name>.

Ensure that there is enough disk space in the host's root file system according to the system requirements.

Client discovery finished with warnings:Can't find or no permission to execute file <home_dir>.

• Check if <home_dir> that was discovered exists on the client.• Check if the file sqlplus in the home directory that was

discovered has enough permissions for being executed by DPA.

Client discovery finished with error:Timeout waiting for agent response on client <client_name>.

1. In DPA, select Admin > System > Configure System Settings.

2. Select Server.

3. Change the parameter Timeou(s) from the default 120 to a larger value.

orCheck if the DPA server has two network cards enabled and the client is able to reach both of them. If the client is not able to reach one of the cards, disable this network card.

When connecting to ECC 6.1, client discovery finished with error:Error Import Clients for w2k3-96-52.dm1nprlab.com finished with errors.Check previous error messages for further information.Unable to logon (Connection refused).

1. Run a batch file containing the following command:

%ECC_INSTALL_ROOT%\tools\JRE\Nt\latest\bin\java -cp %ECC_INSTALL_ROOT%\ECCAPIServer\class;%ECC_INSTALL_ROOT%\ECCAPIServer\ecc_inf\exec\eccapiclient.jar; com.emc.ecc.eccapi.client.util.EccApiPopulateRandomPassword ApiClient

The additional classpath parameter is only required if the command is not used from within the ECC classes directory.

Troubleshooting client discovery for replication analysis 101

Troubleshooting

Synchronizing Incorrect Recovery Point times

If there is a time difference between the DPA server and the storage array being monitored, recovery points might be displayed with times that do not match the expected times. For example, a system administrator initiates a recovery point at 0200H but the recovery point is displayed at 0400H in DPA.

The discovery requests have a Time Offset option that accounts for time differences and allows recovery points to be displayed with consistent times. You must calculate the exact offset between the DPA server and the storage array host.

In the following instructions, connector refers to the DPA host which has the SYMAPI/CLARAPI Engine Discovery request assigned.

The time offset is calculated in seconds.

VNX/CLARiiONTo calculate the time offset between the VNX/CLARiiON and the DPA server:

1. Query the VNX/CLARiiON's time using the navicli command getsptime.

2. At the same time, query the connector's time.

3. If the connector time and the DPA server time are equal (no Time Zone difference):

TimeOffset = Connector time - VNX/CLARiiON time.

4. Otherwise, if there is a time difference also between the connector time and the DPA server time:

TimeOffset = (DPA server time - Connector time) - VNX/Clariion's time.

5. Set the time offset for the request. "Configuring the time offset" on page 103 provides information on this.

SYMAPI and CLARAPI discovery requests fail when run together for the first time on a Solaris DPA Server.

1. Run the discovery requests separately; make sure that one CLARAPI or SYMAPI discovery is successful before running the other.

2. After successful requests have been run sequentially first, they can be run together.

Client discovery is not correctly resolving LUNs on VFMS on ESX 4.1.When trying to correlate the virtual devices to the remote storage they reside on, and the hosting ESX of the virtual machine cannot resolve the name of the VM (DNS configuration), the correlation fails and the virtual devices are displayed as local devices.

Configure the DNS on the ESX properly or add the VM name and IP to the ESX hosts file.

Importing CLARiiON information request fails with the following error message: "An error occurred while data was being loaded from a Clariion ClarEventGet exited with code 3593 (SYMAPI_C_CLARIION_LOAD_ERROR) "

Run the SYMCLI command on the SE host for this CLARiiON:symcfg sync -clar

Table 3 General client discovery problems and solutions (page 2 of 2)

Problem Solution


Troubleshooting

SymmetrixTo calculate the time offset between the Symmetrix and the DPA server:

1. Query the DPA server time.

2. At the same time, query the connector's time.

3. If the Connector time and DPA server time are not equal:

TimeOffset = DPA server time - Connector Time.

4. Otherwise, no time offset for Symmetrix needs to be set.

5. Set the time offset for the request."Configuring the time offset" on page 103 provides information on this.

Configuring the time offsetAfter you have calculated the time offset, set the value for the request. To set the time offset value:

1. Select Policies > Data Collection Policies > Data Collection Policy Library.

2. Select the policy containing the request and click Edit.

3. Select the time offset you calculated Client-server Time Difference (in seconds or minutes).

4. Click Apply.

Synchronizing the system clockAs part of the User Authentication process, DPA relies on the system clock times on the client machine and the server differing by less than one minute. In the event that clock times are unsynchronized, the following error message is displayed:

User Authentication failed due to the times on the client and server not matching. Please ensure that the times are synchronized.

To resolve this issue, ensure that the system clock times on the client and server are synchronized.

It is also advised that NTP be used to synchronize the DPA Server and all the DPA Agent hosts as well. This is imperative for accurate data collection.

Synchronizing the system clock 103

Troubleshooting


APPENDIX AAnalysis policy rule categories

This appendix contains information regarding all the analysis policy categories included in DPA and contains the following sections:

◆ Capacity planning ................................................................................................. 106◆ Change management ............................................................................................ 107◆ Configuration ........................................................................................................ 108◆ Data protection ..................................................................................................... 109◆ Licensing .............................................................................................................. 110◆ Performance ......................................................................................................... 111◆ Provisioning.......................................................................................................... 111◆ Resource utilization .............................................................................................. 112◆ Service Level Agreements ..................................................................................... 113◆ Status ................................................................................................................... 114◆ Troubleshooting.................................................................................................... 116

Analysis policy rule categories 105

Analysis policy rule categories

Capacity planningCapacity planning analysis policies create alerts about events that indicate that resources might soon run out. Table 4 on page 106 describes these jobs.

Table 4 Capacity planning

Name Description Rule Parameters

File system May Be Full In 2 Weeks

Generates alerts if a file system utilization will exceed 90% in the next 2 weeks.

File system filling up

Max Predicted Utilization - 100%Number of hours to forecast 336

Less Than 25 Available Backup Client Licenses

Generates alerts if the license only permits you to monitor less than an additional 25 computers.

Running out of backup client licenses

Maximum client licenses - 25

Pool is Filling Up Alerts when according to the growing trend there will not be space left on the pool for the selected time period.

Pool is Filling Up

Minimum Free Space Allowed - 0Days to Forecast - 90

Pool is Filled Up Alerts when there is no space on the pool to physically allocate a new LUN.

Pool is Filled Up

Initial Consumed Capacity - 3

Storage Array is Filling Up

Alerts when there is no space left to allocate a new LUN on the pool and there are no free disks available on the storage array.

Storage Array is Filling Up

Initial Consumed Capacity - 2

Tape Pool May Be Out of Empty Tapes within 6 weeks

Generates alerts if there will be no empty tapes available in a tape pool within 6 weeks.

Running out of empty tapes

Maximum Predicted Count - 0Number of hours to forecast - 1008

TSM Database May be Full in Two Weeks

Generates an alert if the TSM Database is predicted to reach 100% usage within 2 weeks.

TSM Database Filling Up

Number of Hours to Forecast - 336Maximum Predicted Utilization - 100

TSM Recovery Log May be Full in Two Weeks

Generates an alert if the TSM Recovery log is predicted to reach 100% usage within 2 weeks.

TSM Recovery Log Filling Up

Number of Hours to Forecast - 336Maximum Predicted Utilization - 100



Assigning alerts for pools and storage array analysis policies

When assigning the following analysis policies to objects, the recommended severity levels are:

◆ Pool is Filling Up - Severity 3

◆ Pool is Filled Up - Severity 2

◆ Storage Array is Filling Up - Severity 1

Change managementChange management analysis policies alert about changes in the environment. Table 5 on page 107 describes these jobs.

Table 5 Change management


Backup Client Configuration Changed

Generates alerts if the configuration of a backup client has been modified.

Backup client configuration changed

N/A

Backup Device Configuration Changed

Generates alerts if the configuration of a backup device has been modified.

Backup device configuration changed

N/A

Backup Group Configuration Changed

Generates alerts if the configuration of a backup group has been modified.

Backup group configuration changed

N/A

Disk Firmware Level Changed

Generates alerts if the firmware level of a disk has changed.

Disk firmware level changed

N/A

Disk Serial Number Changed

Generates alerts if a disk serial number has changed.

Disk serial number changed

N/A

Object Operating System Changed

Generates alerts if the operating system of a object has changed.

Object operating system changed

N/A

RecoverPoint Active RPA Changed

Generates an alert if the active RPA has changed since the last analysis run.

RecoverPoint Active RPA changed

N/a

RecoverPoint RPA Link Status Changed

Generates an alert if the status of the RPA link has changed since the last analysis run.

RecoverPoint RPA Link Status Changed

N/a

Tape Drive Firmware Level Changed

Generates alerts if the firmware level on a tape drive has changed.

Tape drive firmware level changed

N/A

Tape Drive Serial Number Changed

Generates alerts if the serial number of a tape drive has changed.

Tape drive serial number changed

N/A

Change management 107


ConfigurationThe configuration analysis policies monitor the environment for device or application configuration issues. Table 6 on page 108 describes these jobs.

Table 6 Configuration


Backup Client Inactive

Generates alerts if a backup client is not scheduled to run.

Backup client inactive N/A

Fileserver export and LUN on same volume

Generates alerts if a fileserver export is on the same volume as a LUN.

Fileserver export and LUN on same volume

N/A

LUN on vol0 Generates alerts if a LUN has been configured on vol0.

LUN on given volume Volume - vol0

Network Autonegotiation Mismatch

Generates alerts if there is an autonegotiation mismatch between a host and its switch port.

IP autonegotiation mismatch

N/A

Network Duplex Mismatch

Generates alerts if there is a duplex mismatch between object and switch.

IP duplex mismatch N/A

Virtual Memory Less Than 1.5x Physical Memory

Generates alerts if the amount of virtual memory on a computer is less than 1.5 times the amount of physical memory.

Not enough virtual memory

N/A

Volume Priority Not Normal

Generates alerts when volume priority is set to something other than normal.

Volume priority not normal

N/A



Data protectionThe data protection analysis policies monitor the environment for exceptions related to backup and recovery issues. Table 7 on page 109 describes the monitored jobs.

Table 7 Data protection (page 1 of 2)


Application Restore Time Estimate More Than 12 Hours

Generates alerts if it is estimated that it will take more than 12 hours to restore an application.

Application restore time estimate too high

Recovery time objective - 12 hours

Application Unprotected For 72 Hours

Alert if an application has not had a successful backup in more than 72 hours.

Application recovery point objective missed

Recovery point objective - 72 hours

Backup Failed Alert generated if a backup fails.

Backup failed N/A

Backup Failed More than Twice In A Row

Alert generated if a backup fails two consecutive times.

Backup failed many times

Maximum failures - 2

Backup More Than 200% of Average Size

Generates an Alert if a backup Job is double its size of its average size over the last 14 days.

Backup larger than average

Days of history - 14 daysDeviation - 100%

Backup Not Succeeded For At Least 3 Days

Alert is generated if a host has not had a backup in the last 3 days.

Backup not occurred for many days

Maximum days not backed up - 3

Backup Running at Same Time as TSM Server Operation

Generates an alert if there were any backups completed over a period that overlapped with any of the following operations on the backup server:• Delete volumes• Expirations• Storage pool copies• Moves• Database backup• Migrations• Reclamations

Backup Running at Same Time as Server Operation

None.

Backup Spans More Than 3 Tapes

Alert is generated if a backup spans more than 3 tapes.

Backup spans multiple tapes

Maximum number of tapes - 3

Full Backup Less Than 50% of Average Size

Generates alerts if a Full backup is less than 50% of its usual size.

Full backup smaller than average

Days of History - 14 daysDeviation - 50%

Full Backup Not Succeeded for At Least 14 days

Generates alerts if a host has not had a successful full backup in the last 14 days.

Full backup not occurred for many days

Maximum Days Not Backed Up - 14

Data protection 109


LicensingThe licensing analysis policies monitor the environment and generate alerts about licensing issues. Table 8 on page 110 describes these policies in more detail.

Mirror Not Updated For At Least 2 Days

Generates alerts if a Remote Disk Mirror has not been updated in at least 2 days.

Mirror not updated for a number of hours

Maximum Exposure - 48 hours

More than 7 Backups Without A Full

Generates alerts if there have been more than seven runs of a backup Job since the last Full backup.

Too many backups without a full

Maximum Non Fulls - 7

No NetWorker Bootstrap Generated in Last 48 Hours

Generates an alert if there has not been a NetWorker bootstrap ran in the last 48 hours.

No NetWorker bootstrap generated

Maximum hours without bootstrap - defaults to 48 hours

TSM Database Backup Running at Same Time as TSM Server Operation

Generates an alert if a database backup process completed while there was other activity on the backup server, including other backups

TSM Database Backup Running at Same Time as Server Operation

None.

TSM Database Backup Occurred in Last 24 Hours

Alerts if there was a TSM database backup in the last 24 hours, or returns the last TSM backup time if there was no backup.

TSM Database Backup Occurred

Time - 24 Hours

Table 7 Data protection (page 2 of 2)


Table 8 Licensing


License Expired Generates an alert if a license in DPA has expired.

License expired N/A

License Will Expire in the Next Week

Generates an alert if a license will expire in the next week.

License nearing expiration

Minimum days before expiry - defaults to 7 days



PerformanceThe performance analysis policies monitor the environment and generate performance problem alerts. Table 9 on page 111 describes these jobs in detail.

ProvisioningThe provisioning analysis policies generate alerts about events that might require provisioning operations. Table 10 on page 111 describes the jobs.

Table 9 Performance


Backup Less Than 50% of Average Speed

Generates an alert if the performance of a backup job is 50% less than its average over the last 2 weeks.

Backup slower than average

Days of history - 14Deviation - 50%

Backup Running For More Than 18 Hours

Generates an alert if a backup has been running for more than 18 hours.

Backup overrunning

Max Runtime - 18 hours

Fileserver Cache Hit Rate Below 80%

Generates alerts if the cache hit rate of a fileserver drops below 80%.

Fileserver cache hit rate low

Minimum cache hit rate - 80%

Full Backup Ran At Less Than 300 KB/sec

Generates an alert if a full backup ran at less than 300 KB/sec.

Full backup succeeded but slow

Minimum expected speed - 300 KB/sec

Table 10 Provisioning


File system Peak Snapshot Usage Below 80%

Generates alerts if the peak snapshot usage over the last 14 days is less than 80%.

File system snapshot space under utilized

Days to examine usage - 14Minimum peak snapshot usage - 80%

Performance 111


Resource utilizationResource utilization analysis policies generate alerts about events that have occurred because of resource utilization problems within the environment. Table 11 on page 112 describes these jobs in detail.

Table 11 Resource utilization (page 1 of 2)


Aggregate Snapshot Utilization Above 90%

Generates an alert if an aggregate snapshot utilization is higher than a specified threshold.

Aggregate snapshot utilization high

Maximum aggregate snapshot utilization - default is 90%

CPU Utilization At Least 90% For Last 30 Minutes

Generates an alert if the CPU Utilization on a host is greater than 90% for last 30 minutes.

CPU pegged Maximum CPU utilization - defaults to 90%Number of minutes - 30 minutes

Disk Activity At Least 90% For Last 30 Minutes

Generates an alert if a disk on a host is greater than 90% busy for over 30 minutes.

Disk pegged Maximum Disk Busy Percentage - 90%Number of minutes - defaults to 30 minutes

Fibre Channel Port Above 70% of Rated Throughput

Generates an alert if a Fibre Channel port exceeds 70% of its max throughput.

Fibre Channel port utilization high

Maximum utilization - 70%

Fibre Channel Port Out of BB Credits

Generates an alert if a Fibre Channel port has ran out of buffer to buffer credits.

Fibre Channel port no BB credits

N/A

File system File Utilization High

Generates an alert if the number of files on a file system is greater than 90% of the max number allowed.

File system file utilization high

Maximum file system file utilization - 90%

File system Snapshot Utilization Above 90%

Generates an alert if a file systems snapshot utilization is above 90%.

File system snapshot utilization high

Maximum file system snapshot utilization - defaults to 90%

File system Utilization Above 90% and Increasing

Generates alerts if a file system utilization is above 90% and is increasing.

File system utilization high and increasing

Maximum file system utilization - defaults to 90%

Memory Utilization Above 90%

Generates an alert if memory utilization on a host is greater than 90%.

Memory utilization high

Maximum memory utilization - defaults to 90%

Network Interface Above 70% of Rated Throughput

Generates an alert if a network interface exceeds 70% of its rated throughput.

Network utilization high

Maximum utilization - defaults to 70%



Service Level AgreementsService Level Agreement (SLA) analysis policies generate alerts about SLA violations. Table 12 on page 113 describes the SLA jobs.

RecoverPoint Journal Utilization High

Generates an alert if the journal utilization for an RPA is above a specified warning or critical threshold.


Warning threshold Critical Threshold

RecoverPoint RPA SAN Usage High

Generates an alert if the SAN utilization for an RPA is above a specified warning or critical threshold.



RecoverPoint RPA WAN Usage High

Generates an alert if the WAN utilization for an RPA is above a specified warning or critical threshold.

RecoverPoint RPA WAN Usage High


RecoverPoint Replication Lag High

Generates an alert if the replication time or data lag is above a specified warning or critical level.

RecoverPoint Replication Lag High

Time Lag Warning threshold Time Lag Critical Threshold Data Lag Warning threshold Data Lag Critical Threshold

TSM Database Utilization Higher than 90%

Generates an alert if the TSM Database utilization exceeds 90%.

TSM Database Utilization High

Maximum Database Utilization - 90%

TSM Expiration Process Duration Exceeds Expectation

Generates an alert if the TSM Expiration process take longer than an hour to run, or more than 25% longer that the average expiration process time over the last seven days.

Expiration Process Duration Exceeds Expectation

% Increase - 25%Period - 7Max Duration - 1

TSM Recovery Log Utilization Higher than 90%

Generates an alert if the TSM Database utilization exceeds 90%

TSM Recovery Log Utilization High

Maximum Recovery Log Utilization - 90%

Table 11 Resource utilization (page 2 of 2)


Table 12 Service Level Agreement


Backup Succeeded But Did Not Meet SLA Requirements

Generates an alert if a backup was successful but outside of its backup window.

Backup succeed but failed SLA requirements

N/A

Service Level Agreements 113


StatusStatus category analysis policies generate alerts when there is concern of the current status of a monitored device or application match. Table 13 on page 114 describes status jobs.

Table 13 Status (page 1 of 2)


Backup Server Errors

Generates an alert if a backup server error is logged (TSM only).

Backup server errors N/A

CPU Offline Generates an alert if a CPU is offline.

CPU offline N/A

Agent Heartbeat Failed

Generates an alert if an agent fails to send in its heartbeat.

Agent heartbeat failed

N/A

Agent Log File Message

Alerts on any message that appears in the agent log files.

Agent Log Messages N/A

Disk Failed Generates an alert if a disk has failed.

Disk failed N/A

EDL Failover occurred

Generates an alert if one EDL appliance fails over to another.

EDL Failover Occurred

N/A

Fan Inactive Generates an alert if a fan on a device is inactive.

Fan inactive N/A

Fibre Channel Port Changed State

Generates an alert if a Fibre Channel port has changed state.

Fibre Channel port changed state

N/A

Less than 75% of Backup Devices Available

Generates an alert if less than 75% of the backup devices on a backup server are Up.

Less than x% of backup devices available

Lowest backup device availability - defaults to 75%

More Than 3 Backup Devices Unavailable

Generates an alert if there are more than 3 backup devices on a backup server Down.

Many backup devices unavailable

Maximum number of downed devices - 3

Network Interface Changed State

Generates an alert if network interface gets a link up or link down event.

Network interface changed state

N/A

Object Restarted Generates an alert if a host has been rebooted.

Object restarted N/A

Object Status not Up

Generates an alert if a object’s status changes to anything except active.

Object Status not Up N/A

PSU Inactive Generate an alert if a Power Supply Unit is not active.

PSU inactive N/A



Publisher Hung Generates an alert if the Publisher queue hasn’t changed since the last poll.

Publisher Queue Hung

N/A

Server Log File Message

Alerts on any messages appearing in server log files.

Server Log Messages

N/A

Tape Drive Needs Cleaning

Generates an alert if a tape drive needs cleaning.

Tape drive needs cleaning

N/A

Tape Drive Not Okay

Generates an alert if a tape drive is reporting a status other than OK.

Tape drive not okay N/A

Tape Library Not Okay

Generates an alert if a tape library is reporting a status other than OK.

Tape library not okay N/A

Thermometer Inactive

Generates an alert if a thermometer becomes inactive.

Thermometer Inactive

N/A

Thermometer Overheating

Generates an alert if a thermometer on a device indicates that it is overheating.

Thermometer overheating

N/A

Waiting For Writable Tapes For More Than 30 Minutes

Generates an alert if a backup server has been waiting more than 30 minutes for a writable tape.

Waiting for writable devices

Maximum outstanding devices - defaults to 0Minutes before alerting - defaults to 30 minutes

Xsigo Fan Less Than 90% of Normal Speed

Generates an alert if the speed of a fan on a Xsigo Director falls below 90% of the normal speed.

Xsigo Fan Speed Less than Expected

Percentage to Check - defaults to 90%.

Table 13 Status (page 2 of 2)


Status 115


TroubleshootingThe troubleshooting analysis policies provide help for troubleshooting problems with there environment. Table 14 on page 116 describes these jobs.

Table 14 Troubleshooting (page 1 of 2)


Backup Failed Due to Client Network Errors

Generate an alert if a backup failed on a client while it experienced an increase in network errors.

Backup failed due to client network errors

N/A

Backup Failed Due To High Client CPU Utilization

Generate an alert if a backup failed on a client, while the CPU utilization on the computer was greater than 90%.

Backup failed due to high client CPU utilization

Maximum processor utilization - defaults to 90%

Backup Failed Due To High Client Memory Utilization

Generates an alert if a backup failed on a client whilst the memory utilization on that client was greater than 90%.

Backup failed due to high client memory utilization

Maximum memory utilization - defaults to 90

Backup Failed Due To High Server CPU Utilization

Generates an alert if a backup failed on a client whilst the CPU utilization on the backup server was greater than 90%.

Backup failed due to high server CPU utilization

Maximum processor utilization - defaults to 90%

Backup Failed Due to High Server Memory Utilization

Generates an alert if a backup fails whilst the memory utilization on the backup server is greater than 90%.

Backup failed due to high server memory utilization

Maximum memory utilization - defaults to 90%

Backup Failed Due to Server Network Errors

Generates an alert if a backup failed while there was an increase in the number of network errors on the backup server.

Backup failed due to server network errors

N/A

Disk Failed For More Than 48 Hours

Generates an alert if a disk is in a failed state for more than 48 hours.

Disk failed for a number of hours

Maximum failure time - defaults to 48 hours

Fibre Channel Port Reporting Errors

Generates an alert if a Fibre Channel port is reporting errors.

Fibre Channel port reporting errors

N/A

Fibre Channel Port Reporting Errors On More Than 1% Frames

Generates an alert if more than 1% of all frames going through a Fibre Channel port have errors.

Fibre Channel port reporting more than x% errors

Maximum percentage errors - defaults to 1%



Network Interface Reporting Errors

Generates an alert if errors are being seen on a network interface.

Network interface reporting errors

N/A

Network Interface Reporting Errors On More Than 1% Packets

Generates an alert if more than 1% of the packets travelling through a network interface have errors.

Network interface reporting more than x% errors

Maximum percentage errors - defaults to 1%

Tape Drive Reporting Errors

Generates an alert if there is an increase in the number of errors seen on a tape drive.

Tape drive reporting errors.

Include Recoverable Errors - defaults to False

Table 14 Troubleshooting (page 2 of 2)


Troubleshooting 117

APPENDIX CAvailable command line operations

This appendix describes administrator utilities that are available from the command line:

◆ dpa CLI command ................................................................................................. 120◆ Unix users............................................................................................................. 131◆ Running reports from the command line................................................................ 131◆ Loading historical backup job data........................................................................ 132

Available command line operations 119

Available command line operations

dpa CLI commandIn a default DPA installation, the dpa CLI command can be found in <install_dir>/services/bin on UNIX and Linux and in <install_dir>\services\bin on Windows. Use the following syntax:

dpa <service_part> <command> [options]

Where <service_part> is application, datastore, or service. The service component includes both the application and datastore services.

dpa application <command> [options]dpa datastore <command> [options]dpa service <command> [options]

If the application and datastore services are installed, use the dpa service command to start, stop, or restart the services rather than the separate dpa application and dpa datastore commands.

Command and option abbreviations

The dpa command supports the abbreviations shown in Table 15 on page 120. Refer to the specific dpa command for available options for that command.

Table 15 Command and option abbreviations

Command and option Abbreviation

--add -a

--bind -b

--cluster -c

--delete -d

--help -h

--master -m

--maxsize -m

--ping -p

--pipeline -p

--platform -p

--tune -t

--uncompressed -u

dpa application dpa app

dpa datastore dpa ds

dpa service dpa svc



dpa application commands

Use the dpa application commands to manage the DPA Application service.

dpa application configure [options]dpa application demote [options] [<Datastore_IP_Address> |

<Datastore_FQDN>]dpa application install [options]dpa application promote [options] [<Datastore_IP_Address> |

<Datastore_FQDN>]dpa application restart [options]dpa application start [options]dpa application status [options]dpa application stop [options]dpa application uninstall [options]dpa application version [options]

After you start, stop, or restart a service, it may take a number of minutes to complete and may not result in an immediate state change.

dpa application configure

Configures the application service, including specifying the datastore and cluster to communicate with.

dpa application configure [options]

Command options

--master <IP_address> — Identifies the datastore to communicate. The application service must be stopped for this command to operate.

--ping — Pings the datastore service that has been defined. The Operation Mode in the output identifies whether the application is within a cluster or standalone.

--tune <value> — Tune the application memory utilization. Where <value> is the total host memory in megabytes. The application service must be restarted for the new memory utilization to take effect. The service must be stopped for this command to operate.

--cluster <IP_address> — Identifies the cluster IP address to announce on

--help — Displays the help screen

--version — Displays the tool version information

--quiet — Suppresses all output except for warning and error messages

Examples

dpa application configure --cluster 192.168.1.2dpa app con --tune 8192

# dpa application configure --pingEMC Data Protection Advisor[INFO] Datastore Service : 127.0.0.1[INFO] Operation Mode : STANDALONE

dpa CLI command 121


dpa application demote

Demotes the application service from a cluster environment. The application service will operate as a standalone node instance. The application service must be installed and stopped for this command to operate.

dpa application demote [options] [<Datastore_IP_Address> | <Datastore_FQDN>]

Command options




<Datastore_IP_Address> — additional or override IP address for the datastore

<Datastore_FQDN> — additional or override FQDN for the datastore

Examples

dpa application demote

dpa app demote 192.168.1.10

dpa application install

Installs the application service. The application service will operate as a system managed service, manageable through normal operating system service commands. Management of the lifecycle of the service can also be managed through this command line tool. This command will install the service, but will not start it automatically. If the application service is already installed this command will fail.

dpa application install [options]

Command options




dpa application promote

Promotes the application service to a cluster environment. The application service will operate as a node within a cluster of nodes. Management of the lifecycle of the service can also be managed through this command line tool. The application service must be installed and stopped for this command to operate.

dpa application promote [options] [<Datastore_IP_Address> | <Datastore_FQDN>]

Command options

--cluster <cluster> — Set the cluster announce address for the application service






<Datastore_IP_Address> — additional or override IP address for the datastore

<Datastore_FQDN> — additional or override FQDN for the datastore

Examples

dpa application promote --cluster 192.168.1.1

dpa app promote 192.168.1.10

dpa application restart

Restarts the application service. This command first stops the application service and then starts the service. The application service must be running for this command to operate.

dpa application restart [options]

Command options




dpa application start

Starts the application service. The application service must be installed and stopped for this command to operate.

dpa application start [options]

Command options




dpa application status

Displays the status of application service. For example, RUNNING (STARTING...), RUNNING, STOPPED

dpa application status [options]

Command options




dpa CLI command 123


Examples

# dpa application statusEMC Data Protection AdvisorThe status of the Application Service is RUNNING

dpa application stop

Stops the application service. The application service must be installed and running for this command to operate.

dpa application stop [options]

Command options




dpa application uninstall

Uninstalls the application service.

dpa application uninstall [options]

Command options




dpa application version

Displays the version information for the various functional libraries that make up the application service. The functional libraries include Apollo, Controller, DPA, Remotex, and UI.

dpa application version [options]

Command options

--platform — Include platform version info




Examples

# dpa application version[INFO] Version for Apollo EAR is 1.0.0.3304[INFO] Version for Controller RAR is 6.0.0.69338[INFO] Version for DPA EAR is 6.0.0.69338[INFO] Version for Remotex EAR is 1.0.0.3304[INFO] Version for UI WAR is 6.0.0.local



dpa datastore commands

Use the dpa datastore commands to manage the DPA Datastore service.

dpa datastore configure [options]dpa datastore export [options]dpa datastore import [options] <import_filename>dpa datastore install [options]dpa datastore reindex [options]dpa datastore restart [options]dpa datastore start [options]dpa datastore status [options]dpa datastore stop [options]dpa datastore uninstall [options]

After you start, stop, or restart a service, it may take a number of minutes to complete and may not result in an immediate state change.

dpa datastore configure

Configures the datastore service, including adding or removing an application service to the list of allowed connections to the datastore service.

dpa datastore configure [options]

Command options

--bind <IP_address> — Set the bind address for the datastore service. The default is 127.0.0.1

--bind cannot be specified with --add or --delete.

--add <IP_address> — Add an application service node as a valid datastore client

--delete <IP_address> — Remove an application service node as a valid datastore client

--tune <tune> — Tune the datastore memory utilization. Where <tune> is the total host memory in MB (megabytes) or GB (gigabytes). The datastore service must be restarted for the new memory utilization to take effect.




Examples

dpa datastore configure --add 192.168.1.10dpa ds con --bind 192.168.1.1dpa datastore con --tune 8192MB

dpa datastore export

Exports the contents of the datastore to the filename or pipeline specified.

dpa CLI command 125


◆ When exporting to a file, a complete and consistent copy of the datastore will be exported to the local file system in a location that can be optionally specified. The default filename of the export is: datastore-<date_and_time>.part.<x>. Where <x> is the part number of the export. A new part number is created if the export file is greater than the maximum export file size. The default is 10 gigabytes. Use the --maxsize option to adjust the maximum size.

◆ When exporting to pipe, a complete and consistent copy of the datastore will be streamed to a named pipe from where a Backup Manager can read the contents.

The datastore service must be installed and running for this command to operate. Any existing filename present will be overwritten.

dpa datastore export [options]

Command options

--maxsize <number>M|G — Set the maximum size of each export file part. Where <number>M|G is in megabytes or gigabytes. For example, 15G is 15 gigabytes

--uncompressed — Export in uncompressed format

--pipeline — Export to pipe




Examples

# dpa datastore exportEMC Data Protection AdvisorDatatstore exported to file :

C:\Users\Administrator\datastore-2013-02-20-1205Exported from the datastore successfully

dpa datastore import

Imports the contents of the datastore export file to the datastore. The import files must be available on the local filesystem. The datastore service must be running for the import command to execute. Any existing filename present will be overwritten.

dpa datastore import [options] <import_filename>

Command options

--uncompressed — Import from uncompressed format




<import_filename> — Filename of the exported file to import

Examples

# dpa datastore import datastore-2013-02-20-1205.part.1



EMC Data Protection AdvisorDatatstore imported from file : datastore-2013-02-20-1205Imported to the datastore successfully

dpa datastore install

Installs the datastore service. The datastore service will operate as a system managed service, manageable through normal operating system service commands. Management of the lifecycle of the service can also be managed through this command line tool. This command will install the service, but will not start it automatically. If the datastore service is already installed this command will fail.

dpa datastore install [options]

Command options




dpa datastore reindex

Reindexes the datastore service to ensure optimal performance. By default, the datastore automatically undertakes activities to ensure optimal performance. Reindex is a manual option to begin these activities outside of the automatic cycle. For example, if a datastore suffers from many writes and many deletes in a short time span, then run dpa datastore reindex to ensure that you have optimal performance.

dpa datastore reindex [options]

Command options




dpa datastore restart

Restarts the datastore service. This command first stops the datastore service and then starts the service. The datastore service must be running for this command to operate.

dpa datastore restart [options]

Command options




dpa CLI command 127


dpa datastore start

Starts the datastore service. The datastore service must be installed and stopped for this command to operate.

dpa datastore start [options]

Command options




dpa datastore status

Displays the status of datastore service. For example, RUNNING (STARTING...), RUNNING, STOPPED

dpa datastore status [options]

Command options




Examples

# dpa datastore statusEMC Data Protection AdvisorThe status of the Datastore Service is RUNNING

dpa datastore stop

Stops the datastore service. The datastore service must be installed and running for this command to operate.

dpa datastore stop [options]

Command options




dpa datastore uninstall

Uninstalls the datastore service.

dpa datastore uninstall [options]

Command options






dpa service commands

Use the dpa service commands to manage the DPA Application and the DPA Datastore services.

dpa service install [options]dpa service restart [options]dpa service start [options]dpa service status [options]dpa service stop [options]dpa service uninstall [options]

dpa service install

Installs the datastore service and then the application service. The services will operate as a system managed services, manageable through normal operating system service commands. Management of the lifecycle of the services can also be managed through this command line tool. This command will install the services, but will not start them automatically. If the services are already installed this command will fail.

dpa service install [options]

Command options




dpa service restart

Restarts the application and datastore services. This command stops the application service, stops the datastore service, and then starts the datastore service and application service. The services must be running for this command to operate.

dpa service restart [options]

Command options




dpa service start

Starts the datastore service and then application service. The services must be installed and stopped for this command to operate.

dpa service start [options]

dpa CLI command 129


Command options




dpa service status

Displays the status of application and datastore services. For example, RUNNING (STARTING...), RUNNING, STOPPED

dpa service status [options]

Command options




Examples

# dpa service statusEMC Data Protection AdvisorThe status of the Datastore Service is RUNNINGThe status of the Application Service is RUNNING (STARTING ...)

dpa service stop

Stops the application service and then the datastore service. The services must be installed and running for this command to operate.

dpa service stop [options]

Command options




dpa service uninstall

Uninstalls the application service and then the datastore service.

dpa service uninstall [options]

Command options






Unix usersUnix users must source the DPA config file before running any of the command line operations.

To source the config file, navigate to the etc folder of the DPA installation directory and run the command as follows:

cd <DPA install dir>/agent/etc

. ./dpa.config

Running reports from the command lineReports can be run from the command line that are either saved to disk or sent as email. This allows on-demand reports to run from other scripts or applications without having to wait for a scheduled event to occur.

Creating the script or batch file

To run a report, create a shell script or batch file with the following settings:

java -Xmx512m -classpath <class path> com.sysdm.wysdm.publisher.Main -r reportname -v view -n object [ -c objecttype -P partOfObject ] -t timeperiod [ -F format ] [ -w -f filename ] [ -m mailaddress -s subject ] -u username -p password

Unix and Windows differences

On Windows, only double quotes should be used in the above command in the batch file. On Unix, only single quotes should be used.

<class path> should be the equivalent of CPATH on Windows and $CLASSPATH on Unix.

The following options must be set:

◆ -r — Name of report to be run. This is the name of the report, not the scheduled report.

◆ -n — Name of object to run the report against.

◆ -t — Time period to run the report against (for example, Last Day).

The following are optional:

◆ -c — Object type. Used to specify the type of object when reporting on more complex object types, such as file systems.

◆ -N — Path to a file containing a list of objects. Each line in the file represents an object. Each line should be in the format: object name, [type], [partOfObject].

Some file examples are:

auwysdmnivd1c

or

auwysdmnivd1c, Host

or

C:, Filesystem, auwysdmnivd1c

Unix users 131


or

C:, Filesystem, auwysdmnivd1cD:, Filesystem, auwysdmnivd1cE:, Filesystem, auwysdmnivd1c

◆ -P — Parent object of the object to object to report against.

◆ -F — Format in which you want the report to be displayed: csv, jpg, pdf, xml, html. The format defaults to HTML if not specified.

◆ -w — Specify if you want to save the report to disk.

◆ - f — Name of file for the report to be created, as specified by the –w option.

Note: This is stored relative to the Doc Root setting.

◆ -m — E-mail address of the user you want to receive a report using email.

◆ -s — Subject to be specified in email.

◆ -u — Username of a DPA administrator.

◆ -p — Password for the username.

The following is the list of valid object types than can be used with the -c flag:

◆ Root, Group, Query-Single, Query-Multi, Host, TapeLibrary, IPSwitch, FCSwitch, EDL, Data Domain, Celerra, RecoverPoint, NearStore, ArcServe, Avamar, DataProtector, NetWorker, TSM, NetBackup, PureDisk, BackupExec, CommVault, MSExchange, MSSQLServer, OracleDB, PostgreSQL, ACSLS, HPCommand View, vCenter, Other Application, Symmetrix, Clariion, HPEVA, VirtualHost, VirtualTapeDrive, VirtualTapeLibrary, NetworkShare, LUN, vFiler, qTree, Aggregate, VolumePriority, DataMover, FCPort, Filesystem, NetInt, Disk, iSCSI, Process, TapeDrive, BackupClient, BackupGroup, BackupPool, BackupLib, BackupDev, BackupJob, MSExchangeStorageGroup, MSSQLServerDB, RPConsistencyGroup, RPSite, RPSplitter, RPA, RPConsistencyGroupCopy, VirtualDataMover.

Loading historical backup job data After a backup application object is created and requests are assigned, the agent immediately begins gathering data on backup jobs to store in the datastore. However, the agent also can gather data on backup jobs that were run prior to object creation in DPA.

IMPORTANT

To commit the data to the DPA server, the installed agent must have previously been started and successfully registered with the DPA Server. However, it need not be currently running in order to load the historical data.

To load historical backup data, run the agent binary from the command line with the following parameters:

Each backup module has an equivalent executable in the installed Agent's bin directory. Valid modules are:

◆ NetWorker - dpaagent_modnetworker



◆ NetBackup - dpaagent_modnetbackup

◆ Tivoli Storage Manager - dpaagent_modtsm

◆ Avamar - dpaagent_modavamar

◆ Backup Exec - dpaagent_modbackupexec

Running the executable with the -? parameter shows the valid command line options. You should specifically use:

◆ -f <function name> — Name of data gathering function to execute. Always jobmonitor. Mandatory.

◆ -t <target host> — Host address of backup application server. The default is localhost.

◆ -B <start time> — Start time from which to gather backup jobs. The format is dd/mm/yyyy hh:mm:dd.

◆ -E <end time> — End time from which to gather backup jobs. The format is dd/mm/yyyy hh:mm:dd.

The start and end times can also be in Unix epoch time format.

If <start time> is specified and <end time> is not, <end time> is set to the current time. This includes all the backup jobs that ended after <start time>.

If <end time> is specified and <start time> is not, <start time> is set to 0. This includes all the backup jobs that end before <end time>.

◆ -i — TSM instance name (TSM only).

◆ -U — Username to connect to the backup application (TSM and Avamar only).

◆ -P — Password to connect to the backup application (TSM and Avamar only).

◆ -c- Commit — Instructs the module to send the data to the DPA Server. Mandatory.

The following example collects backup job data run between 20:15 to 23:15 on 10/09/2012 from a NetBackup server on NBUmaster:

Example: dpaagent.exe -f jobmonitor -t NBUmaster -B "10/09/2012 20:15:00" -E "10/09/2012 23:15:00" -c

Job summary reports

The job summary reports provide overviews of the totals of backup and maintenance jobs (such as all jobs, successful jobs, failed jobs) that have occurred on backup servers. The summary reports rely on the most up-to-date data in the datastore to produce accurate summary results.

While historical backup job data is loading using the agent command line options, summary reports might display inaccurate totals. It is best to wait until all historical job data is loaded before running summary reports for the loaded historical periods.

Loading historical backup job data 133

INDEX

Aagent 38Analysis policy 85, 88attributes 75

BBackup Applications 51Branch Elements 85

Cchargeback 86Complete or single-server installation 28Config file, sourcing 131consistency group check 86consistent device replication check 86

DDiscovering EMC VPLEX arrays 50DR host visibility check 86

EEMC ControlCenter

monitoring 48, 50Enterprise installation 26

FFibre Channel Switches 67

HHistorical backup data, loading 132HP Commandview

monitoring 70

IInstallation Package Names 12, 26, 29Installing the Application Service 27Installing the Datastore Service 27IP Switches 68

LLDAP

anonymous bind 78

NNetBackup

configuring authentication 57NetWorker 52

Ooptions files 33

Ppfile 35ports, replication analysis 48PureDisk 58

RRecoverability checks 86RecoverPoint, monitoring for Storage Arrays 50Remote Data Collection 87Remote Windows host monitoring 65reports, command-line 131requests, data gathering 87rules 85

Sschedules 80silent installation 33single-server installation 28SNMP community string 66Solutions Enabler 48Split or Enterprise installation 26Symantec NetBackup 57System Monitoring Modules 64

TTape Libraries 66Tivoli Storage Manager 54

UUNIX environments

uninstalling the agent software 38Using 13Using the DPA Migration Tool 13

VVMware, monitoring 70

XXsigo Director

configuring data monitoring 68


Index


emc data protection advisor -...

Documents