Docu33787 Data Protection Advisor 5.8 Administration Guide

8/10/2019 Docu33787 Data Protection Advisor 5.8 Administration Guide

1/150

EMC CorporationCorporate Headquarters:

Hopkinton, MA 01748-91031-508-435-1000www.EMC.com

EMCData Protection AdvisorVersion 5.8

Administration Guide

300-012-559

REV 11

FOR ADMINISTRATORS SETTING UP DATA MONITORING IN DPA


2/150

EMC Data Protection Advisor Version 5.8 Administration Guide2

Copyright

Copyright 2005-2014 EMC Corporation. All rights reserved.

Published July 2014

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 withrespect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for aparticular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and othercountries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date support, product, and licensing information to to EMC Online Support at http://support.EMC.com.

For technical support, go to EMC Online Support and select Support. There are several options, including one to create a servicerequest. To create a service request you must have a valid support agreement. Contact your EMC sales representative aboutobtaining a valid support agreement or with questions about your account.

Your suggestions will help us to improve the accuracy, organization, and overall quality of user publications. To provide

feedback, please email [email protected].


3/150

EMC Data Protection Advisor Version 5.8 Administration Guide 3

Revision history

The following table presents the revision history of this document:

Revision Date Description

10 April 4, 2014 Addition of Revision history.Addition of Collector time format limitationsafter Collector installation within first 13days of the month on page 83

11 July 31, 2014 Modifications to Monitoring HP DataProtector, Gathering Occupancy Data on p.31.


4/150



5/150


Revision history ........................................................................................................ 3

Chapter 1 Configuring Security andPort Settings

Setting the ports for the DPA processes ............. ............... ............... ............... 9Server port settings..................... ............... ................ .............. ............... .......... 10GUI Client port settings................................................................................... 10Illuminator port settings.................................................................................. 11Allowing Collector ports through a firewall ................................................ 11How the Collector starts up ............................................................................ 11

Enabling secure communications between processes ............... ............... ......... 13Enabling encryption between processes ............................................................. 14

What happens during an encrypted session ................................................ 14Using the key tool to set the encryption key type ....................................... 15Encrypting from a web browser interface .................................................... 16

Chapter 2 Setting up DataMonitoring

Monitoring setup summary ............................................................................ 17Checking which licenses have been installed..................... ............... ............... .. 18Monitoring databases and Microsoft Exchange Server................ ................ ..... 19

Performing Discovery on HP-UX and Linux ............................................... 19Importing hosts from a CSV file.............. ................ ............... ................ ........ 19Importing hosts from EMC Ionix ControlCenter.................... ................ ..... 20Monitoring a single host.................................................................................. 22

Monitoring storage arrays..................................................................................... 24Discovering VNX/CLARiiON arrays ........................................................... 24Discovering EMC Symmetrix arrays ............................................................. 26

Performing Hostless Discovery on Symmetrix and VNX/CLARiiON .... 27Monitoring storage arrays that use RecoverPoint .............. ............... .......... 28

Monitoring data protection servers........... ............... ................ ............... ............. 29Monitoring CA BrightStor ARCserve................... ............... ............... ........... 29Monitoring CommVault Simpana.............. ................ ............... ............... ...... 29Monitoring EMC Avamar................................................................................ 30Monitoring EMC NetWorker ............... ............... ................ .............. .............. 31Monitoring HP Data Protector ....................................................................... 31Monitoring IBM Tivoli Storage Manager ............... ............... .............. .......... 33Monitoring Oracle RMAN .............................................................................. 35

Contents


6/150


Contents

Monitoring Symantec Backup Exec................................................................ 35Monitoring Symantec NetBackup .............. ............... ................ ............... ...... 36Monitoring Symantec PureDisk...................................................................... 37Monitoring EMC HomeBase ............... .............. ............... ................ .............. . 38Monitoring Microsoft Exchange Server......................................................... 39

Databases.................................................................................................................. 40Monitoring Oracle............................................................................................. 40Monitoring SQL Server ............... .............. ............... ............... .............. ........... 41Monitoring PostgreSQL ............... .............. ................ .............. ............... ......... 43

RecoverPoint .............. ............... ............... ............... ............... .............. ................ .... 44 Host system monitoring......................................................................................... 45

Monitoring a Windows host remotely .......................................................... 45Monitoring a host for system data.................................................................. 46

Tape libraries............................................................................................................ 48Switches and I/O Devices...................................................................................... 50

Monitoring Fibre Channel switches ............... .............. ................ ............... ... 50Monitoring IP switches ............... ............... ............... .............. ................ ......... 50Monitoring Xsigo I/O Director....................................................................... 51

File Servers .............. ............... ............... ............... ............... .............. ................ ....... 52

Monitoring EMC File Storage ......................................................................... 52Monitoring Network Appliance Filers ............... ................ ................ ........... 52 Backup appliances................................................................................................... 54

Monitoring EMC Disk Libraries ............... ............... .............. ................ ......... 54Monitoring EMC Data Domain ...................................................................... 54Monitoring NetApp NearStore....................................................................... 55Monitoring Fujitsu ETERNUS CS................................................................... 55Moniitoring FalconStor Virtual Tape Library devices ............... ............... ... 56

ACSLS .............. ............... .............. .............. ................ .............. .............. ............... ... 57 Disk management servers...................................................................................... 58

Monitoring HP Command View..................................................................... 58VMware .............. .............. ............... ............... ............... .............. ............... .............. 59Monitoring a clustered server .............. .............. ................ .............. ............... ...... 60

Creating a credential............................................................................................... 61

Chapter 3 Troubleshooting andReporter Performance

Tuning the Reporter for performance .............. .............. ............... ................ ....... 64Setting the parameters for Reporter worker processes .............. ................ . 64How the Reporter handles report requests .............. ................ ............... ...... 65

Allocating more memory to a GUI client............................................................. 66Viewing the log files................................................................................................ 67

Finding the server process log files ............. ................ .............. ............... ...... 67Finding the client process log file ............. ................ ............... ................ ....... 67Changing the log level (server)....................................................................... 67

Managing the log files...................................................................................... 68Viewing log files from the GUI ............... ............... ............... ............... ........... 69Sending notifications on warnings and errors.............................................. 69

Managing the DPA processes................................................................................ 71Stopping and restarting a process .............. ............... ................ ............... ...... 71Viewing a process status from the GUI.......................................................... 71

Troubleshooting data collection ................ ............... ............... ............... ............... 72Data collection troubleshooting first actions .............. .............. ............... ..... 72Data collection troubleshooting second actions ............... .............. .............. 72Data collection troubleshooting third actions............................................... 73


7/150


Conten

Preparing a log file for submission to EMC Support .................................. 73Troubleshooting client discovery for recoverability analysis................ ........... 74

Client discovery using remote execution............. ................ ............... .......... 74Client discovery with Collector...................................................................... 75General client discovery .................................................................................. 76Synchronizing Incorrect Recovery Point times .............. ................ .............. 77

Viewing the report history......... ............... .............. ................ .............. ............... .. 79Synchronizing the system clock............ ............... .............. ................ ............... .... 80

Chapter 4 Changing the defaultdata collection settings

Assigning a request to a node............................................................................... 82Reloading the Collector .......... ................ ............... .............. ................ ........... 83Removing a request.......................................................................................... 83Collector time format limitations after Collector installationwithin first 13 days of the month ................................................................... 83

Assigning recoverability requests ........................................................................ 85Editing default request settings ......... ................ .............. ............... ............... ...... 86

Viewing the requests assigned to a node ............................................................ 88Viewing the request history ............................................................................ 88

Collecting data remotely................... ................ ............... ............... ............... ........ 89

Chapter 5 Configuring Control Panels

Creating a Control Panel ................................................................................. 91Running a Control Panel from the navigation tree ..................................... 94Setting a Control Panel to open when a user logs in............... ................ .... 94Editing a Control Panel ................ .............. ............... ............... ............... ........ 95Deleting a Control Panel............ ............... ............... ............... ............... .......... 96

Chapter 6 Monitoring an environmentfor alert conditions

What are rulesets and analyses?................ .............. ............... ................ ........ 97Generating events from analysis jobs ............. .............. ............... .............. .... 97

Assigning an analysis job to a node..................................................................... 99Creating an alert ............................................................................................... 99Passing arguments to an alert....................................................................... 102

Creating an analysis job ...................................................................................... 103Editing an analysis job ................................................................................... 104

Editing an existing ruleset ................................................................................... 105Creating a simple ruleset .................... ................ ............... ................ .............. ... 106Creating complex rulesets ................................................................................... 114Testing a ruleset.......... ............... .............. .............. ............... .............. .............. ..... 116

Appendix A Analysis Job Definitions

Capacity planning..................... .............. ................ .............. ............... ............... .. 118Assigning alerts for pools and storage array analysis jobs ...................... 118

Change management.......... ............... .............. ............... ............... .............. ......... 119Configuration ........................................................................................................ 120

Data protection...................................................................................................... 122Licensing ................................................................................................................ 124

Performance.................... ................ .............. ............... .............. ................ ............ 125Provisioning....................... .............. ................ .............. ............... ............... .......... 126


8/150


Contents

Resource utilization ................ .............. ............... ................ .............. ............... .... 127 Service Level Agreements.................................................................................... 129 Status....................................................................................................................... 130 Troubleshooting..................................................................................................... 132

Appendix B Exporting and importing

DPA configurationWorking with the WDS file.................................................................................. 136

Importing the WDS file ............. ............... .............. ................ .............. .......... 136Exporting the WDS file .................................................................................. 136

Appendix C Available CommandLine Operations

Exporting the WDS file from the command line .............. .............. ................ .. 138Running reports from the Publisher................................................................... 140

Creating the script or batch file..................................................................... 140Setting the classpath ............... .............. ............... .............. ............... .............. 141

Changing the terminology in the GUI ............................................................... 143Loading historical backup job data ............... ............... .............. .............. ......... 144

Job summary reports ............. ............... ............... .............. ................ ............. 145

Index 147


9/150

Configuring Security and Port Settings 9

1

Configuring Security andPort Settings

Setting the ports forthe DPA processes

Figure 1 on page 9displays a summary of the ports used by DPA processes forinterprocess communication.

Figure 1 DPA process communication

Although omitted in the above diagram for clarity, a remote proxy collector requires aconnection to the Controller (3741, 3916) and the Listener (4001).

The ports described in this section are the default values. If necessary, anadministrator can change the port on which a process listens from the File> SystemSettingsdialog box.

The administrator requires the "Edit System Settings - Processes" privilege.


10/150


Configuring Security and Port Settings

Server port settings The default ports for communications between the core Server processes aredescribed in Table 1 on page 10.

GUI Client portsettings

The default ports for communications between the GUI Client and Server processesare described in Table 2 on page 10.

For almost all functionality, the GUI Client only needs to connect to ports 3916(Controller) and port 4002 (Reporter). Connection to ports 9002, 4001, and 4007 areonly required if the features described in Table 2 on page 10are required.

Table 1 Server process communications

This process: Listens on port: Communicates with:

Collector 3741 Controller, Listener, Illuminator

Controller 3916 All other processes

Illuminator 8009, 8080, 8092, 8093

25011 - Always used

8090 - Opened from theproxy host. Use whenthe Discovery proxy hostis not the DPA Server

Collector

8587 (by RMI) Reporter

Listener 4001 Collector, Controller, GUI

Reporter 4002 Controller

8583 (by RMI) Illuminator

Publisher 4007 Controller, Reporter, GUI

Web Server 9002 GUI

Table 2 Client communications

Client listens on port: Communicates with:

3916 Controller

4002 Reporter

9002 Web Server

The user can launch the GUI from a web browser, or chose to install itlocally. If they choose to launch from a web browser, the client also needsto be able to connect to port 9002, which is the web server.

4001 Listener

In the backup module, the user has the ability to annotate failed backupswith the reason the job failed and other information. To use this feature,the GUI needs to connect to port 4001 (Listener) to store data in thedatabase.

4007 Publisher

If the user is using scheduled reports, and wishes to test the report fromthe GUI, the GUI neeeds to connect to port 4007 (Publisher).


11/150

11

Configuring Security and Port Settin

Illuminator portsettings

The default port settings for gathering date remotely from the Illuminator server aredescribed in Table 3 on page 11.

Local and remotediscovery

Figure 1 on page 9shows both the ports required for both the local and remotediscovery processes:

Collector only or application host with Collector

This scenario refers to a DPA Collector installed remotely on any platform, or aCollector installed on an application host (for exampole, an ECC host).

Windows proxy Collector

This scenario refers to a DPA Collector installed on a Windows platform toperform discovery on Windows hosts. This configuration is required to remotelydiscover Windows hosts when DPA server is running on Solaris.

Application host without Collector

This scenario refers to discovery performed on an application host without aCollector installed local to the host.

If the recoverability discovery process is performed remotely, DPA will attempt onSSH (default port 22). If that fails, DPA will attempt via ftp/telnet (ports 21/23). Ifthis fails, DPA will attempt an RPC connection (default port 135).

The following must be enabled to ensure communication between the monitored hostand the Illuminator process:

RPC services should be enabled and accessible to the DPA Server .

SSHD should be enabled and accessible to the DPA Server, orFTP/Telnet servicesshould be enabled and accessible to the DPA Server

Allowing Collectorports through afirewall

Ensure that the firewall between a Collector and the server that is running thecontroller allows traffic destined for ports 3916 and 4001 to flow from the Collector tothe controller and listener. The Controller must communicate with the Collector onport 3741 to allow the Collector to be informed of changes in the configuration.

How the Collectorstarts up

The following is the sequence of events during Collector startup:

1. The Collector is started by the system (/etc/init.d or Windows Services) ormanually.

Table 3 Remote communications

Operating system Direction: Using port:

Windows From DPA server RPC port range

(Default port 135).

To DPA server RPC port Range

(Default 1024-65535).

TCP port 25011.

UNIX From DPA server One of:

SSH (TCP 22)

FTP & Telnet (TCP 23,TCP 21)

To DPA server Port 25011


12/150



2. The Collector initiates a connection to the Controller as configured duringinstallation, and identifies the hostname and aliases.

3. The Controller obtains its configuration for the host from the configdatabase andforwards this information to the Collector. This information includes the items tomonitor along with any options (for example, username and passwords, specificports, time-out values, polling interval).

4. The Collector immediately starts monitoring the system upon receipt of theconfiguration.

5. Upon gathering data, the Collector formats the information into an XML packet,and sends the packet to the Listener.

6. The Collector returns to idle, and continues polling each request at the specifiedinterval for that request.

7. The Listener, upon receipt of a packet from the Collector, inserts the data into thedatabase, either as a new row or as an update to data that is already present.

In addition, specific Collectors may require other available ports. For example,collecting data through SNMP requires access from the Collector to port 161 on the

node being monitored by both TCP and UDP protocols. The full details of the portsrequired for each module depend on the application being monitored (for example,NetWorker or Symantec NetBackup).

Chapter 2, Setting up Data Monitoring,describes the configuration prerequisitesfor all of the data gathering modules of DPA.


13/150

Enabling secure communications between processes 13


Enabling secure communications between processes

Security for all server processes includes the Reporter, Listener, Analysis engine, andPublisher. If security is enabled, users are not able to connect to any of these processesusing the API without being authenticated first.

To enable security, modify the controller.xml file on the server. There is anAUTHREQUIRED setting in this file that can be set to one of three values:

none

Security is not enabled. Users can connect to Server-side processes using the APIwithout being authenticated.

compatauth

Security is enabled. Users must authenticate when connecting to the Server-sideprocesses. This method should be used with Collectors 2.1 or 2.1.2 in yourenvironment.

fullauth

Security is enabled. Users must authenticate when connecting to server processes.This method should be used if all Collectors in the environment are version 3.0 orlater.

If upgrading from a previous version that had security enabled, the security setting isautomatically changed to the new method of configuration, and the security level isset to compatauth.

If Collectors earlier than version 2.1 are in your environment, do not enable serversecurity. The Collectors will not be able to communicate with the Controller and willstop gathering data.


14/150



Enabling encryption between processes

If encryption is enabled, all communications between all processes in the product areencrypted.

To enable encryption, modify the controller.xml file on the server by changing the

CRYPTREQUIRED variable to one of the following values: none

No encryption occurs between any processes.

allow

Processes are capable of performing encryption, and communications areencrypted. Use this setting if components in the environment are an earlierversion of the product and are not capable of encryption.

enforce

All communications are encrypted. If a component is incapable of encryptingdata, it will not be able to communicate with other processes. Use this setting if all

components are version 3.1 and later.If upgrading from an old version of DPA, set the Collector to allowso that Collectorsin the environment that have not been upgraded can continue to communicate withthe server.

Restart the Controller to apply the changes and enable encryption .

What happens during an encrypted session

When encryption is enabled, data is encrypted using the Advanced EncryptionStandard (AES). A session key is used to encrypt all data sent across the network.This key is unique to each individual network connection and is used only for theduration of that connection.

When a client initiates a network connection, it must negotiate a session key with theserver. As part of the negotiation phase, the initiating process sends itspublic keyacross the network to the server. The server generates a unique symmetric session key(256 bit AES by default) and encrypts the session key using the provided public keyof the client. The encrypted session key is then returned to the client, which uses itsprivate key to obtain the decrypted session key. The session key is then used toencrypt all further data sent over the network.

The private key used by the client process during the negotiation of the session key iscreated by default when the process is installed. This key is unique to that host. Bydefault, the client process will generate a 2048 bit RSA key. The following algorithmsare supported:

RSA (1024 and 2048 bit keys)

AES (128 and 256 bit keys)

3DES (192 bit keys)

DES (56 bit key).

The encryption algorithm and key used during the session key negotiation can bemodified by a customer if necessary, using the key tool.


15/150

Enabling encryption between processes 15


Using the key tool to set the encryption key type

To change the encryption algorithm, a binary called dpa_keytool is distributed withthe Server and Collector packages. The key tool binary is used to generate a newencryption key. Its usage is:

dpa_keytool []

The list of possible values for type and key length are shown in Table 4 on page 15.

For example:

dpa_keytool RSA 1024 MyDPA.key

When run, the key tool produces a file containing the generated key. If the parameter is not specified, the file is created in the same directory in which thecommand was run, with a file extension that matches the specified algorithm and keylength.

On UNIX platforms, you must source the dpa.config file before running the key tool.For sh, ksk, bash, or equivalent shell, run:

. /etc/dpa.config

For csh, tcsh, or equivalent shell, run:

source /etc/dpa.config

For the new key file to take effect, it must be placed in the keys directory for thecomponent. The location of the keys directory depends on the operating system:

The Windows keys directory is $INSTALLDIR/keys.

The UNIX keys directory is $INSTALLDIR/etc/keys.

After creating a key, move the key file into the keys directory on that machine.Multiple keys can be placed in the keys directory. The encryption process uses the key

with the longest key length that exists in the keys directory. After putting the key filein the keys directory, all processes must be restarted for the change to take affect.

Table 4 Key type and key length

Algorithm Key Length

RSA 2048

RSA 1024

AES 256

AES 128

DES3 192DES 56


16/150



Encrypting from a web browser interface

To change the encryption method used by a GUI launched from a web browser, thegenerated keys must be placed inside a jar file.

To place the keys inside a jar file for the user interface:

1. Rename the resource.jar file in $INSTALLDIR/webapps/root/resource.jar toresource.zip.

2. Open the file using a zip compression tool.

3. Add the key file or files to the zip file.

4. Save the zip file back to the $INSTALLDIR/webapps/root directory and renameit with a .jar extension.


17/150

Setting up Data Monitoring 17

2

Setting up DataMonitoring

Monitoring setupsummary

To set up an object in DPA to be monitored, follow the steps in Table 5 on page 17.

Table 5 Data monitoring setup summary

Step Description

Install licenses Check that the licenses to monitor your device, host, or environment has beenpurchased and installed. See "Checking which licenses have been installed" onpage 18.

Install the Collector If you are monitoring the object from a host other than the DPA server host, you needto install the remote Collector. Install and run the installation package you used to

install the DPA server, and follow the instructions in the installation wizard.The DPA Installation Guidedescribes how to install a Collector.

Install third-partybinaries or configure theobject for monitoring

You may need to install binaries on the DPA host or the remote Collector host toconnect to the monitored object. You also may need to configure an account orconnection on the monitored object.

The following sections descibes the prerequisite configuration for all objects:

"Monitoring databases and Microsoft Exchange Server" on page 19

"Monitoring storage arrays" on page 24

"Monitoring data protection servers" on page 29

"Databases" on page 41

"RecoverPoint" on page 45

"Host system monitoring" on page 46

"Tape libraries" on page 49

"Switches and I/O Devices" on page 51

"File Servers" on page 53

"Backup appliances" on page 55

"ACSLS" on page 58

"Disk management servers" on page 59

"VMware" on page 60

Create or modify theDPA credential

A credential stores the information used to connect to the monitored object. You mayneed to modify the default credential or create a new one with the account details fromthe previous step. See "Creating a credential" on page 62.

Run the Discovery orData Collection Wizard

If you are configuring a Symmetrix or VNX environment, or Microoft Exchange Server,select Tools> Discovery Wizard. If you are monitoring anything else, select Tools>Data Collection Wizard. Click Helpin the wizard to open the online help, which will

step you through the wizard for setting up your monitored object.

Modify the defaultRequest settings.

Data Collection requests are assigned to the node created by the wizards. If you wantto modify the default data collection, right-click the node and select Administration>Node Properties(for example, not collecting performance data, or collectingconfiguration data every week instead of every day.

Chapter 4, "Changing the default data collection settings,"describes editing requests.

Test data collection After at least ten minutes of letting the request run, run a report from the node thatshould include data (for example, Backup Job Summary, or a configuration report). Ifno data is gathered, see Chapter 3, "Troubleshooting and Reporter Performance,"


18/150


Setting up Data Monitoring

Checking which licenses have been installed

The options that are available for configuration in the Data Collection and Discoverywizards depend on the types of licenses that you have installed with DPA. If you donot have the correct license installed, the option to create that device or host isdisabled in the wizard.

To see the installed licenses, go to Tools> License Manager.

The EMC Data Protection Advisor Installation Guide describes the license typesavailable for DPA. For more information on how to obtain licenses for reporting,please contact an EMC Account Manager or Customer Support Engineer.


19/150

Monitoring databases and Microsoft Exchange Server 19

Setting up Data Monitorin

Monitoring databases and Microsoft Exchange Server

DPA can monitor database hosts and Microsoft Exchange Server for recoverabilityanalysis. There are two methods to configure application hosts for monitoring inDPA:

To configure multiple hosts, use the Discovery Wizard. Hosts can be importedfrom a CSV file, or by connecting to an EMC Ionix ControlCenter host andimporting the defined clients.

To configure a single host, use the Data Collection Wizard.

The following sections describe how to create application host nodes for gatheringdata:

"Importing hosts from a CSV file" on page 19

"Importing hosts from EMC Ionix ControlCenter" on page 20

"Monitoring a single host" on page 22

PerformingDiscovery on HP-UXand Linux

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

PHCO_24504

PHSS_36004

PHCO_31923

PHCO_35743

PHKL_34805

LinuxRetrieving VDISK information on Red Hat and SUSE Linux requires the following

library to be installed on the host: libstdc++.so.6.

Importing hosts froma CSV file

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

Before you start the Discovery Wizard

To perform an import from a CSV file, the user must select a text file from the localfilesystem that is in a comma-separated value format. The format of the file must be:

Client,AlternativeName,Timezone,Platform

The values for the time zone field and Platform field are optional, but if specifiedmust conform to the following formats:

Timezone A valid Java time zone string, as defined athttp://java.sun.com/j2se/1.4.2/docs/api/java/util/TimeZone.html#NormalizedCustomID

Platform One of: Windows, Solaris, Linux, HP-UX, AIX, ESX.

If no time zone is specified, the default time zone is taken from the machine on whichthe DPA client is running.

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

Windows A user with local or domain administrator rights.


20/150



UNIX and Linux A user with root level rights , or a user with the followingSUDO rights:

= NOPASSWD: //IllumAgent/l4magent

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

To import hosts from a CSV file

1. Select Tools> Discovery Wizardfrom the toolbar. The Discovery Wizard appears.

2. Select Serversand click Nextto proceed to theImport Sourcepanel.

3. Select File, and enter the full path to the CSV file in the File namefield, or clickBrowseto search for the file.

4. Click Nextto proceed to the Select Clientspanel. All of the hosts defined in theCSV file are displayed.

5. Select the hosts from the file to be imported. Click Next. The Recoverability panelappears.

6. Select Monitor for Recoverabilityto enable recoverability analysis for theselected hosts.

7. Select a Credentialto use to connect to the hosts to gather recoverability data, orclick Editto modify or create a credential.

8. Select a Schedulefor the recoverability data gathering request, or click Editto

modify or create a schedule. Click Next. The Import Location panel appears.

9. Select Assign nodes in Tree to assign the imported host nodes to the selectedposition in the Configuration view.

By default, the created nodes are not added to the Configuration view, but addedto the configuration database, and can be edited and assigned from the Node Listdialog.

10. Click Next. The Importing panel appears. Click Nextto start importing theselected clients.

11. A message indicates if the import process was successful. Select Finishto closethe Discovery Wizard, or OKto return to the Wizard if the import failed.

12. If the import was successful, the host nodes are created and the client discoveryrequest is assigned to the nodes with the specified credential and schedule togather recoverability data.

Importing hosts fromEMC IonixControlCenter

You can discover application hosts from EMC Ionix ControlCenter by connecting tothe ControlCenter host.

Before you start the Discovery Wizard

The DPA Collector must be able to communicate with the ECC API.


21/150



The credentials used to connect to hosts for recoverability monitoring must includethe following:

Windows A user with local or domain administrator rights.

UNIX and Linux A user with root level rights , or a user with the followingSUDO rights:

= NOPASSWD: //IllumAgent/l4magent

The SUDO program should support the -p parameter and the -s parameter whenthe interactive mode is used.

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

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

SSH should be enabled and accessible to the recoverability agent .

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

To import hosts from EMC Ionix ControlCenter


2. Select Serversand click Nextto proceed to theImport Sourcepanel.

3. Select ECC connection.

4. If at least one ControlCenter host has already been defined using the DataCollection or Discovery Wizard, it will appear in the Existinglist. ControlCenternodes created using the Node Editor will not appear in this list. Select an existingControlCenter host from the list to reimport the EMC Ionix ControlCenterconfiguration.

5. Otherwise, select Customto import from a known ControlCenter host. Completethe fields:

Hostname The name of the host on which ECC API is running.

Port The port on which the ECC API listens.

Credential The credential used to connect to the ControlCenter host.

ECC Credential The credential used to connect to ECC API.

Connect Remotely Select if DPA should connect directly to ECC API.Otherwise, DPA will connect to the ECC host (using host credentials) andconnect from there to ECC API.

6. Click Nextto proceed to the Select Clientspanel.

7. Select the hosts that you want to import and click Next.

8. If the import is successful, the Wizard displays a list of all of the hosts that wereimported from this ControlCenter server. Click Next. The Recoverability panel

appears.

9. Select Monitor for Recoverabilityto enable recoverability analysis for theselected clients.

10. Select a Credentialto use to connect to the clients to gather recoverability data, orclick Editto modify or create a credential.

11. Select a Schedulefor the recoverability data gathering request, or click Edittomodify or create a schedule. Click Next. The Import Location panel appears.


22/150



12. Select Assign nodes in Tree to assign the imported hosts to the selected positionin the Configuration view. By default, the created nodes are not added to theConfiguration view, but added to the configuration database, and can be editedand assigned from the Node List dialog.

13. Click Next. The Importing panel appears. Click Nextto start importing theselected hosts.


15. If the import was successful, the host nodes are created and the client discoveryrequest is assigned to the nodes with the specified credential and schedule togather recoverability data.

Monitoring a singlehost

Monitor an application host from a Collector running on the host machine or anothermachine in the environment. System data can only be gathered from UNIX systemsby a Collector local to the UNIX machine.

"Before you start the Discovery Wizard" on page 19provides the prerequisites formonitoring application hosts.

To monitor a host

1. Launch the Data Collection wizard by selecting Tools > Data Collection wizardfrom the menu.

2. Click Hostin the Data Collection Wizard and click Next. The Host Details panelappears.

3. In the Enter the name of the Hostfield, type the name or IP address of the host.

Note: The unique node name must be the name of a valid host. This name is restricted to255 characters.

4. In the Enter a description of the Hostfield, type a short description that will helpto identify the host.

5. In the Select the operating system running on the Hostfield, select an operatingsystem from the list of values.

6. In the Enter any aliases of the Hostfield, type any aliases that are associated withthe host.

Note: Aliases can be entered on separate lines or separated by commas (for example,Alias1, Alias2, Alias3).

7. Click Next. The Collector Location panel appears. This panel does not appear foroperating systems of type Other.

8. In the Is there or will there be a Collector installed on the Host?field, selecteither Yesor No. Click Nextand the Data Gathering panel appears.

9. Select Yesto gather system information from the applications host in the Do youwant to gather system information?field, or Noto not gather systeminformation.

10. Click Nextand the Remote System Information Permissions panel appears.

The Remote System Information Permissions panel only appears if the followingconditions are met:


23/150



The operating system is Windows.

A Collector is not installed on the computer.

System information is to be monitored.

11. In the User Namefield, type the user name for an account that exists on the host.In the Passwordfield, type the password for the user name. In the ConfirmPasswordfield, type the password again.

12. Click Next. The Recoverability Analysis Permissions panel appears.

13. Select Yesin the Do you want to perform Recoverability Analysis on this hostfield. Select a Credentialused to connect, or click Editto create or edit an existingcredential.

14. Click Next. The Item Location panel appears. Click to select the folder in theNavigation tree under which you want the node to appear.

15. Click Next. The Summary panel appears.

Click Finishto create the node. All applicable requests, proxy information, andcredentials are assigned to the host node and the Collectors are reloaded.


24/150



Monitoring storage arrays

Data Protection Advisor monitors EMC CLARiiON and Symmetrix storage arrays.EMC CLARiiON and Symmetrix storage arrays replicated with EMC RecoverPointrequire additional configuration to enable complete recoverability analysis. Thefollowing sections describe setting up storage array nodes for monitoring:

"Discovering VNX/CLARiiON arrays" on page 24

"Discovering EMC Symmetrix arrays" on page 26

"Performing Hostless Discovery on Symmetrix and VNX/CLARiiON" on page 27

"Monitoring storage arrays that use RecoverPoint" on page 28

DiscoveringVNX/CLARiiONarrays

EMC VNX/CLARiiON storage arrays must be monitored remotely from a Collectorrunning on a different host (such as the DPA server).

To configure hosts and storage arrays, use the Discovery Wizard, as described in"Using the Discovery Wizard to discover CLARiiON arrays" on page 25. DPAdiscovers all of the storage arrays that are being managed and creates nodes in theNavigation tree.

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

Before starting the Discovery Wizard

Monitoring VNX/CLARiiON requires additional licensing. Without the correctlicense, the option to configure VNX/CLARiiON for monitoring does not appear inthe Data Collection Wizard.

The recoverability server connects to the VNX/CLARiiON on TCP port 443. If theVNX/CLARiiON is configured to use port 2163, use port 2163.

Setting up EMC Solutions EnablerDiscovering VNX/CLARiiON hosts from DPA requires Solutions Enabler to beinstalled. The following are the steps required.

1. Download EMC Solutions Enabler version 7.2.1 or later from support.emc.com.

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

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

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

where is the IP address of the first controller (SP-A).

is the IP address of the second controller (SP-B).

and are the account name and password of aVNX/CLARiiON user with view permissions.

The first field mustbe the first VNX/CLARiiON controller, followed by thesecond controller.

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


25/150

Monitoring storage arrays 25


symcfg disco -clar -file

5. If the Base license of Solutions Enabler does notexist, copy the ClarApiDiscoveryexecutable file from the following directory:

\Illuminator_Agent\bin\ClarAPI\

to the Solutions Enabler host, and run the following command:

WindowsClarApiDiscovery.exe REGISTER -file=

UNIX./ClarApiDiscovery REGISTER -file=

The available platforms are:

AIX

Hp

Linux

Solaris

Win326. Run the following command to confirm that the VNX/CLARiiON has been

registered:

symcfg list -clar

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

Using the DiscoveryWizard to discover

CLARiiON arrays

To perform a discovery of CLARiiON storage arrays, select either a host previouslyconfigured in DPA, or connect to a host with Solutions Enabler installed.

To discover storage arrays:

1. Select Tools> Discovery Wizardfrom the toolbar. The Discovery Wizard appears.2. Select Storage Arraysand click Nextto proceed to the Import Sourcepanel.

3. If at least one host has already been defined using the Data Collection orDiscovery Wizards, it will appear in the Existinglist. Storage array hosts createdusing the Node Editor will not appear in this list. Select an existing host from thelist to re-import changes in the storage array configuration.

4. Otherwise, select Newto import from a known host. Complete the fields:

Hostname The name of the host running Solutions Enabler.

Credential The credential used to connect to the host.

Method Select EMC CLARiiON (CLARAPI).

Time Offset Specifies the time difference between the Symmetrix host andthe recoverability analysis agent (SYMAPI only).

5. Click Next.

6. If the import is successful, the Wizard displays a list of all of the storage arraysthat were discovered from this host in the Select Storage Arrays panel.

The Remotecolumn indicates if the Storage Array API is remote to the SE host.The Connectorcolumn indicates the current node used to store the SE host forthis storage array. Click on the Connectorcolumn to change the connector nodeused to discover this storage array.


26/150



7. Select the storage arrays that you want to import and click Next.


9. Select Assign nodes in Tree to assign the imported client nodes to the selectedposition in the Configuration view. By default, the created nodes are not added tothe Configuration view, but added to the configuration database, and can beedited and assigned from the Node List dialog.



12. If the import was successful, the storage array nodes are created. If the userselected recoverability monitoring, the client discovery request is assigned to thenodes with the specified credential and schedule to gather recoverability data.

Discovering EMC

Symmetrix arrays

EMC Symmetrix storage arrays (Symmetrix) must be monitored remotely from a

Collector running on a different host (such as the DPA server).To configure multiple hosts and multiple storage arrays, use the Discovery Wizard, asdescribed in "Using the Discovery Wizard to discover Symmetrix arrays" on page 27.DPA discovers all of the storage arrays that are being managed and creates nodes inthe Navigation tree.

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

Before starting the Discovery Wizard

Monitoring EMC Symmetrix requires additional licensing. Without the correctlicense, the option to configure EMC Symmetrix for monitoring does not appear inthe Data Collection or Discovery Wizard.

Setting up EMC Solutions EnablerDiscovering Symmetrix hosts from DPA requires an existing EMC Solutions Enablerhost, or Solutions Enabler to be installed. The following are the steps required.

1. If you are using an existing Solutions Enabler host, it must satisfy the followingrequirements:

The host operating system and Solutions Enabler version are supported byDPA as described in the EMC Data Protection Advisor Compatibility Matrix.

The host must be connected to the Symmetrix array by a SAN connection.

The DPA server must be able to connect to the Solutions Enabler host.

Otherwise, download a supported version of EMC Solutions Enabler from

support.emc.comand install on a host that satisfies the above.

2. Obtain the "Base" and "DevMasking" licenses for Solutions Enabler.

3. Run the following command on the Solutions Enabler host to register theSymmetrix:

symcfg discover

4. Run the following command to confirm that the Symmetrix has been registered:

symcfg list


27/150

Monitoring storage arrays 27


5. If the Symmetrix is listed, you are ready to run the Discovery Wizard in DPA andconfigure the Symmetrix.

Using the DiscoveryWizard to discoverSymmetrix arrays

To perform a discovery of Symmetrix storage arrays, select either a host previouslyconfigured in DPA, or connect to a host with Solutions Enabler installed.

To import a storage array:


2. Select Storage Arraysand click Nextto proceed to the Import Sourcepanel.

3. If at least one host has already been defined using the Data Collection orDiscovery Wizards, it will appear in the Existinglist. Storage array hosts createdusing the Node Editor will not appear in this list. Select an existing host from thelist to reimport changes in the storage array configuration.

4. Otherwise, select Customto import from a known host. Complete the fields:

Hostname The name of the host running Solutions Enabler.

Credential The credential used to connect to the host.

Method Select EMC Symmetrix (SYMAPI).

Time Offset Specifies the time difference between the Symmetrix host andthe recoverability analysis agent (SYMAPI only).

5. Click Next.

6. If the import is successful, the Wizard displays a list of all of the storage arraysthat were discovered from this host in the Select Storage Arrays panel.

The Remotecolumn indicates if the Storage Array API is remote to the SE host.The Connectorcolumn indicates the current node used to store the SE host forthis storage array. Click on the Connectorcolumn to change the connector nodeused to discover this storage array.

7. Select the storage arrays that you want to import and click Next.


9. Select Assign nodes in Tree to assign the imported client nodes to the selectedposition in the Configuration view. By default, the created nodes are not added tothe Configuration view, but added to the configuration database, and can beedited and assigned from the Node List dialog.



12. If the import was successful, the storage array nodes are created. If the userselected recoverability monitoring, the client discovery request is assigned to thenodes with the specified credential and schedule to gather recoverability data.

Performing HostlessDiscovery onSymmetrix andVNX/CLARiiON

Host discovery as described above requires either the installation of a local Collectoron the host, or the deployment of a remote Collector with credentials for host access.Either method may be prevented by customer security policies.

DPA can perform application discovery on storage arrays without needing to connectto the hosts on which applications are hosted. This changes the node heirarchy that


28/150



appears, and the reports that are available, in the SLM Workspace. The EMC DataProtection Advisor Report User Guideprovides more information.

The prerequisites for hostless discovery are the same as those described in "Using theDiscovery Wizard to discover CLARiiON arrays" on page 25and "Using theDiscovery Wizard to discover Symmetrix arrays" on page 27.

Using the DiscoveryWizard for hostlessdiscovery

1. Create a storage array node using the procedure described in "Using theDiscovery Wizard to discover CLARiiON arrays" on page 25and "Using theDiscovery Wizard to discover Symmetrix arrays" on page 27.

Remember that the credential you select in the Storage Array Permissions panel isthe credential to access the Solutions Enabler host.

2. Your storage array node wil be created in the node tree in the location youselected (default Storage> Disk Storage> VNX/CLARiiONor EMCSymmetrix).

3. Right-click on the new node and select Administration> Properties. Click theAssignations tab.

4. In the Requests list, select either Import CLARiiON Informationor Import

Symmetrix Informationand click Run.

5. DPA will perform discovery on the selected storage array. Once the request hasrun successfully, you can view the storage topology for the array in the SLMWorkspace and run Replication Analysis reports.

Monitoring storagearrays that useRecoverPoint

If your VNX/CLARiiON or Symmetrix storage arrays are replicated with EMCRecoverPoint, DPA provides recoverability analysis for RecoverPoint replicationoperations.

To perform recoverability analysis for RecoverPoint, you have to configure theVNX/CLARiiON or Symmetrix storage arrays and the RecoverPoint host in DPA incorrect order.

To gather RecoverPoint recoverability data:

1. Use the Data Collection Wizard to create the host node for the Solutions Enablerhost that is connected to the storage array replicated with RecoverPoint.

2. Run the Illuminator Client Discovery request from the host connector node youcreated, to discover the arrays attached to the host.

3. Configure the Symmetrix or VNX/CLARiiON arrays using the DiscoveryWizard, as described in "Monitoring storage arrays" on page 24.

4. Run the Illuminator Policy Import request on the storage array nodes you createdto import recoverability policy data.

5. Using the Data Collection Wizard, configure the EMC RecoverPoint appliances

data monitoring, as described in "RecoverPoint" on page 45.

6. Ensure that the RecoverPoint Configuration request has been assigned to theRecoverPoint appliance node that handles replication for the storage array. Runthis request. Chapter 4, "Changing the default data collection settings,"describeshow to assign requests to nodes and run requests.

7. After the RecoverPoint Configuration request is run and sufficient time haspassed, DPA should have begun gathering recoverability analysis data forRecoverPoint. Reports can be run from the storage array nodes and the SLMworkspace will show the mapping of storage and recovery points.


29/150

Monitoring data protection servers 29


Monitoring data protection servers

This section describes how to monitor the following data protection servers:

"Monitoring CA BrightStor ARCserve" on page 29

"Monitoring CommVault Simpana" on page 29

"Monitoring EMC Avamar" on page 30

"Monitoring EMC NetWorker" on page 31

"Monitoring HP Data Protector" on page 31

"Monitoring IBM Tivoli Storage Manager" on page 34

"Monitoring Oracle RMAN" on page 35

"Monitoring Symantec Backup Exec" on page 36

"Monitoring Symantec NetBackup" on page 37

"Monitoring Symantec PureDisk" on page 38

"Monitoring EMC HomeBase" on page 39

"Monitoring Microsoft Exchange Server" on page 39

Monitoring CABrightStor ARCserve

CA BrightStor ARCserve servers are monitored from a Collector running on the CABrightStor ARCserve server or from a Collector running on any other Windowscomputer in the environment.

Before starting the Data Collection Wizard

Install the ARCserve Manager on the computer in which the Collector is running.

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 (aliasescannot be used either).

Setting up ARCserve server



3. Step through the Wizard, using the instructions as a guide. Click Helpto bring upthe online help.

MonitoringCommVault

Simpana

Monitor CommVault Simpana servers from a Collector running on the CommVaultSimpana database or from a Collector running on any other computer in the

environment.


The Collector has to run as an account that has permission to access and executeread-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 remoteto the server.


30/150



Setting up CommVault Simpana

1. Launch the Data Collectionwizard by selecting Tools > Data Collection wizardfrom the menu.

2. Click Hostin the Data Collectionwizard. Click Nextand the Host Details panelappears.


Monitoring EMCAvamar

Monitor EMC Avamarservers using a Collector installed on any remote computerin the environment, including the DPA Server. Do not install a Collector on an EMCAvamar server or storage node.


To monitor an EMC Avamar server remotely, no additional software is required.

Monitoring EMC Avamar requires additional licensing. Without the correct license,the option to configure EMC Avamar for monitoring does not appear in the DataCollection Wizard.

The steps in "Setting up an Avamar server" on page 30assume that the EMC Avamarserver being monitored is a standard EMC Avamar installation. It is possible for theEMC Avamar database to have been modified with different connection parameters.If this is the case, modify the DPA configuration to reflect the changes.

To gather data from EMC Avamar, DPA connects directly to the EMC Avamardatabase. It connects to the mcdbdatabase on the default port for EMC Avamar,which is 5555. If these parameters were modified, change the Avamar ConfigandAvamar Job Monitor requests to override these parameters with options on therequest.

Chapter 4, "Changing the default data collection settings,"describes how to modifyexisting requests.

When DPA connects to the database, it uses the viewuseraccount to log in to thedatabase. If the EMC Avamar installation was modified so that this user does nothave permission to log in to the database, or the password for this user has beenmodified, change the user and password in the Default Avamar Credentialsto reflectthe username and password that should be used to connect to the database.

The Collector must be installed on a host that is in the same time zone as the Avamarserver.

Before you start the Data Collection Wizard, you will need to know the resolvablehostname or IP address of the Avamar server.

Setting up an Avamar server





31/150



Monitoring EMCNetWorker

Monitor NetWorker either from a Collector running on the backup server or remotelyusing a Collector running on the DPA Server.


If monitoring NetWorker remotely, the NetWorker client package must be installedon the Collectors host. The NetWorker module uses commands such as mminfo andnsradmin to communicate with the NetWorker server and requires access to thebinaries within the NetWorker client package.

If monitoring NetWorker 7.3 or later remotely, the DPA Collector service user and theproxy host must be added to the Users list of the NetWorker AdministratorsUserGroup. For example, if you are monitoring NetWorker remotely from the hostDPACollectorHost, and the Collector is running as the Windows userDPACollector, the following line must be added to the Users list of the propertiesfor Administrators:

user=DPACollector,host=DPACollectorHost

Before you start the Data Collection Wizard, you will need to know the resolvablehostname or IP address of the NetWorker server.

Setting up a NetWorker server




Monitoring HP DataProtector

A Collector can monitor HP Data Protector servers running on the HP Data ProtectorCell Manager or remotely from another computer.


If monitoring a Cell Manager remotely, follow the instructions in "Monitoring HPData Protector remotely" on page 33.

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

If monitoring a Cell Manager from a Collector installed on the Cell Manager, skip tothe section entitled "Setting up a HP Data Protector Server" on page 34.

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

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

Gathering Occupancy dataGathering occupancy data is not enabled by default for HP Data Protector. To enableoccupancy data gathering, the occupancy option for the DataProtector Jobmonitorrequest must be enabled, and the DataProtector Client Occupancy request must beassigned to the Data Protector client in the Node Properties dialog.


32/150



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

You can use the DP_OCCUPANCY_DB_PATH environment variable for the DPA

Agent to control where the occupancy data is stored when you run the jobmonitorrequest. If you do not use the DP_OCCUPANCY_DB_PATH environment variable,then the system stores the occupancy data in the temporary directory.

Changing the location of Occupancy database on Linux1. Stop the DPA Agent.

2. Use the cd command to access the /opt/emc/dpa/agent/etc directory.

3. Edit the dpa.custom file. Add the following to the end of the file:

COLLECTOR_DP_OCCUPANCY_DB_PATH=/your/absolute/path/

export COLLECTOR_DP_OCCUPANCY_DB_PATH

Ensure that you include the trailing backward slash (/) character in the above

path.

4. Restart the DPA Agent.

Changing the location of Occupancy database on Windows1. Stop the DPA Agent.

2. Run the regedit.exe as the administrator user.

3. Expand the HKEY_LOCAL_MACHINE registry key.

4. Expand the SOFTWARE registry key.

5. Create an EMC registry key if one does not already exist.

6. Create a DPA registry key if one does not already exist.

7. Ceate an Collector registry key if one does not already exist.

8. Create a new String registry value with name DP_OCCUPANCY_DB_PATH and

set the value to the desired directory path. For example:

C:\DPA\OccupancyData\

Ensure that you include the trailing backward slash (/) character in the above

path.

9. Restart the DPA Agent.

omnirpt patchHP has released a patch for Data Protector 6.1 that mustbe installed onto a DataProtector 6.1 installation before it can be supported by DPA.


33/150



Table 6 on page 33lists the required patch ID by platform.

The patch is available for General Release from HP from www.hp.com. Enter thepatch ID into the Searchfield of the HP home page to be directed to the patchdownload page.

Refer to Chapter 4, "Changing the default data collection settings,"for moreinformation on configuring and assigning requests.

Monitoring HP DataProtector remotely

To install the client software on the computer that monitors the Cell Manager:

1. Launch the Data Protector Manager administration GUI to add a client.

2. When selecting the software components to install on the client, ensure that theUser Interfaceoption is selected.

The DPA Data Protector module requires access to commands such as omnirptand omnicellinfoto gather data from the Cell Manager. These components areonly installed when the user interface component is installed, so it is essential toselect this option.

3. Configure the client to have permissions to run reports on the Cell Manager. Firstdetermine the user for which the Collector process will be running:

On UNIX systems, the Collector always runs as the rootuser.

On Windows systems, the Collector runs as the DPACollector service user. Toverify the user for the service on a Windows system, launch the Windowsservice control manager and view the details of the DPACollectorservice.

4. Create a user on the Cell Manager that matches the Collectors username. Typethe name of the host in the user definitionfield.

5. Add the user to a Data Protector User Group that has Reporting andNotificationsand See Private Objectspermissions.

Typically, this means adding the user to the admingroup. However, to restrict auser from inheriting other administrator privileges, create a new group withReportingandNotificationand See Private Objectspermissions and add theuser to that group.

6. Verify that remote authentication privileges are set up correctly by running thefollowing command from the Collectors host:

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

06/01/30 12:00

If successful, this command returns a list of all the sessions that have run on the DataProtector server during the time period specified. If an error indicating insufficientpermission to run reports appears, review the configuration settings on the DataProtector server.

Table 6 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


34/150


35/150



If the rc.edt file is not present in these directories, the registry variable (Windows) orenvironment variable (UNIX) COLLECTOR_TSM_RCEDT_FILENAME can be set tothe location of rc.edt if required.

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

Monitoring TSM remotely

When monitoring a TSM instance remotely, the TSM client software must be installedon the host that will monitor the TSM instance. The TSM module uses the dsmadmccommand included with the TSM client software to connect to the TSM instance andgather data.

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

1. Click Customwhen prompted during the TSM client installation.

2. The installation components are displayed. Select Administrative Client

Command Line Filesand click Next. The TSM client installation continues.

3. After the TSM client installation is complete, initialize the client for the first timeby starting the TSM Backup-Archive GUI from the Startmenu. Use the wizard toconfigure the client.

4. To configure the client, accept the default Help me configure the TSM BackupArchive Clientvalue and click Next. Either import an existing options file orcreate 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 forTSM (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.

Setting up a TSM server

1. Launch the Data Collectionwizard by selecting Tools > Data Collection wizardfrom the menu.

2. Select Hostin the Data Collection Wizard panel. Click Next. The Host Detailspanel appears.


Monitoring Oracle

RMAN

DPA gathers detailed information about Oracle backup Jobs with the Oracle

(Recovery Manager) RMAN utility. When RMAN backups run, they write detailedinformation about the backups to either the database that was backed up or to adesignated recovery catalog within the environment. Depending on the configurationof the DPA Oracle RMAN module, the module gathers information directly from thedatabase that was backed up or from a centralized recovery catalog.

Backup applications such as NetWorker and Symantec NetBackup interface directlywith RMAN to perform hot backups of Oracle databases. If you are monitoring thebackup applications with DPA, you receive information about the RMAN backupsthat occurred on the backup application. However, the level of detail that is available


36/150


37/150



2. Ensure This Accountis selected.

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

4. Modify the service account details and click OK.

5. Restart the service to activate the changes.

Setting up a Backup Exec server


2. Click Hostin the Data Collection wizard and click Next. The Host Details panelappears.


MonitoringSymantec

NetBackup

Configure a Symantec NetBackup server to be monitored from a Collector running onthe NetBackup Master Server, or from a Collector running on a different host such as

the DPA server.


If gathering data from NetBackup remotely, follow the instructions described in"Configuring NetBackup authentication for remote data collection" on page 37.

Note: Media Server Status data can only be collected if a Collector is stored on the MediaServer itself. It can not be collected via proxy.

ConfiguringNetBackup

authentication for

remote datacollection

To successfully gather data remotely, the following must be configured:

The NetBackup Server binaries must be installed on the Collectors host.

The Collectors host must be able to successfully resolve the NetBackup MediaServers.

The NetBackup Master Server must be able to successfully resolve the Collectorshost. The instructions for this are provided.

To resolve the Collector host from the NetBackup Master Server:

UNIXIf the NetBackup Master Server is running on a UNIX computer, the name of the hoston which the Collector is running must be added to the bp.conf file on the NetBackupMaster Server. To add the host:

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

SERVER = Collectorhost

where Collectorhostis the Collectors hostname. The Collectors hostname must beresolvable by the Master Server.

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

WindowsIf the NetBackup Master Server is running on a Windows computer, add the name ofthe Collector host through the NetBackup Administration Console:

1. Launch the NetBackup Administration Consoleand open the Master ServerProperties dialog box.


38/150



2. Click Serversand add the name of the Collectors host to the list of additionalservers that are allowed to access the Master Server. Click OK.

3. Restart the NetBackup services to activate the changes.

Setting up a NetBackup server

1. Launch the Data Collectionwizard by selecting Tools > Data Collection wizard

from the menu.

2. Select Hostin the Data Collectionwizard and click Next. The Host Details panelappears.


MonitoringSymantec PureDisk

Configure a Symantec PureDisk server to be monitored from a Collector running onthe PureDisk Server, or from a Collector running on a different host, such as the DPAserver.


PureDisk servers implement a firewall that may prevent Data Protection Advisorfrom gathering data from PureDisk, or from communicating with a collector installedon the PureDisk server. In order to ensure successful data gathering andcommunications, the following sections describe how to configure the PureDiskserver beforeconfiguring the server in the Data Protection Advisor GUI.

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-rulesby inserting one of the following linesdirectly after this line in the file:

-A INPUT p icmp j ACCEPT

If you are monitoring PureDisk with a collector installed on the PureDiskserver, add the following line:

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

If you are monitoring PureDisk from a collector running on a differentmachine, add the following line:

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

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

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 updatethe PureDisk IP table:


39/150



1. Open the following file in a text editor:

/etc/puredisk/custom_iptables_rules

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

tcp {controller_host_ip} 3741

This allows connections from the controller host to the DPA collector on port 3741on the Puredisk server.

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

tcp {collector_host_ip} 10085

This allows connections from the collector host to the postgres database on port10085 on the Puredisk server.

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

tcp10.64.205.0/24 10085

Refer to the /etc/puredisk/custom_iptables_rules file itself for additionalinformation on configuring this file.

Setting up a PureDiskserver

1. Launch the Data Collection Wizard by selecting Tools > Data Collection Wizardfrom the menu bar.

2. Select Hostin the Data Collection Wizardpanel. Click Next. The Host Detailspanel appears.


Monitoring EMCHomeBase

EMC HomeBase is capable of forwarding data about Data Protection events intoDPA. Unlike other backup applications, the DPA Collector does not actively connectto Homebase and gather data. Instead, the HomeBase server forwards information onevents when they occur. To enable monitoring of a Homebase server, the user mustenable DPA Alerting in HomeBase, and must configure the Homebase server in DPA(as described in "Setting up a HomeBase server" on page 39), so that reports can berun from it.

For more details on how to enable DPA Alerting in HomeBase, please consult theHomeBase product documentation.

Setting up aHomeBase server

1. Launch the Data Collection Wizard by selecting Tools > Data Collection Wizardfrom the menu bar.

2. Select Hostin the Data Collection Wizardpanel. Click Next. The Host Detailspanel appears.


Monitoring MicrosoftExchange Server

An Exchange Server can be monitored for recoverability from a Collector installed onthe same machine as the Exchange Server or a Collector installed remotely.


40/150



Note: Microsoft Exchange can only be monitored for recoverability analysis, and for systeminformation from the Exchange server host.


The 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 doesnot support recoverability analysis for two Exchange Information Stores on a cluster.

Setting up an Exchange server

1. Select Tools > Data Collection Wizardfrom the menu to launch the DataCollection wizard.

2. Click Hosts in the Data Collection Wizardpanel and click Next. The Host Detailspanel appears.



41/150

Databases 41


Databases

This section describes:

"Monitoring Oracle" on page 41

"Monitoring SQL Server" on page 42

"Monitoring PostgreSQL" on page 44

M

Date post:	02-Jun-2018
Category:	Documents
Upload:	echoicmp
View:	242 times
Download:	0 times

Docu33787 Data Protection Advisor 5.8 Administration Guide

Documents