dpa60-planningdesign_srg.pdf

Welcome to Data Protection Advisor (DPA) 6.0 Planning and Design. Click on the Supporting Materials tab to access the Student Resource Guide and course navigation information. Copyright 2013 EMC Corporation. All rights reserved. These materials may not be copied without EMC's written consent. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS IS. EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. EMC , EMC, EMC ControlCenter, AdvantEdge, AlphaStor, ApplicationXtender, Avamar, Captiva, Catalog Solution, Celerra, Centera, CentraStar, ClaimPack, ClaimsEditor, ClaimsEditor, Professional, CLARalert, CLARiiON, ClientPak, CodeLink, Connectrix, Co-StandbyServer, Dantz, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, EmailXaminer, EmailXtender, EmailXtract, enVision, eRoom, Event Explorer, FLARE, FormWare, HighRoad, InputAccel,InputAccel Express, Invista, ISIS, Max Retriever, Navisphere, NetWorker, nLayers, OpenScale, PixTools, Powerlink, PowerPath, Rainfinity, RepliStor, ResourcePak, Retrospect, RSA, RSA Secured, RSA Security, SecurID, SecurWorld, Smarts, SnapShotServer, SnapView/IP, SRDF, Symmetrix, TimeFinder, VisualSAN, VSAM-Assist, WebXtender, where information lives, xPression, xPresso, Xtender, Xtender Solutions; and EMC OnCourse, EMC Proven, EMC Snap, EMC Storage Administrator, Acartus, Access Logix, ArchiveXtender, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, C-Clip, Celerra Replicator, CLARevent, Codebook Correlation Technology, Common Information Model, CopyCross, CopyPoint, DatabaseXtender, Digital Mailroom, Direct Matrix, EDM, E-Lab, eInput, Enginuity, FarPoint, FirstPass, Fortress, Global File Virtualization, Graphic Visualization, InfoMover, Infoscape, MediaStor, MirrorView, Mozy, MozyEnterprise, MozyHome, MozyPro, NetWin, OnAlert, PowerSnap, QuickScan, RepliCare, SafeLine, SAN Advisor, SAN Copy, SAN Manager, SDMS, SnapImage, SnapSure, SnapView, StorageScope, SupportMate, SymmAPI, SymmEnabler, Symmetrix DMX, UltraFlex, UltraPoint, UltraScale, Viewlets, VisualSRM are trademarks of EMC Corporation. All other trademarks used herein are the property of their respective owners.

1 Copyright 2013 EMC Corporation. Do not Copy - All Rights Reserved.

This eLearning course examines the multiple factors that must be considered when planning and designing a Data Protection Advisor 6.0 solution from end user to storage array. The class starts with networking considerations for accessing the Web GUI, and moves through topics such as minimum requirements per physical and virtualized DPA infrastructure and OS platform, and new port communication layout. Included also are the requirements for Data Collection Agent deployment with EMC and third-party products, integrated database configuration figures, and planning for the discovery of applications, switches and arrays. The class emphasizes the need to address business pain points with a solution that includes availability, scalability, reliability, manageability and inter-process communication. This course is designed for those who are responsible for planning and designing a DPA solution and for those responsible for implementing it.

Copyright 2013 EMC Corporation. Do not Copy - All Rights Reserved. 2

This module discusses a number of crucial criteria and guidelines for planning and designing an end-to-end DPA 6.0 solution. The technical requirements for implementing such a solution will be presented as well.


Planning and designing a DPA 6.0 solution presupposes that you have previously documented and analyzed the current state of the environment where you are introducing DPA. This groundwork should result in a better understanding of the requirements, constraints, and assumptions that underlie the scope of your solution.


The following guidelines will help you address business pain points.

Design for DPA 6.0s best RPO/RTO under the customers requirements and constraints. Identify single points of failure and address them, ensuring that your solution meets business availability expectations. Remember that security is a critical aspect of availability.

Design also with the correct scalability figures in mind. Your solution should meet immediate and longer term requirements. If your solution is part of an EMC strategic engagement, you should address growth expectations that scale over years. Regardless of the scope of the engagement, your DPA 6.0 solution should have inherent stability and flexibility.

Design for predictable performance. Your solution should emphasize the fact that DPA 6.0s performance depends upon the health of the other components of the solution. The failure or degradation of other components for instance service providers (WMI, SE, SNMP, etc.) and VMware resources will affect the overall functioning of the product. This needs to be called out, and your design should be built around this fact.

Design for manageability. Either the solution will need to meet the abilities of the staff, or the staff will have to enhance their skills to meet the solution.

Design for integration of DPA 6.0 with other processes. DPA 6.0s REST API offers the ability for other applications to tap into the wealth of configuration-item information collected and organized by the product.


The design of your DPA 6.0 solution must involve the infrastructure stack from the end user to the storage arrays. DPA 6.0 is a network application depending on Web availability not only for access to its console, but also for exposure of its data to external applications via REST technology. Because of this Web dependence, the collection of data for your DPA 6.0 solution design must stretch from the Web to the arrays.


This module discusses core components of a DPA 6.0 solution, such as the Server, the Datastore, and the Data Collection Agent. It includes licensing changes information, as well as data migration options.


In version 6.0, the architecture of DPA can be divided into three main components: the unified Application Server, the Datastore, and the REST API.

Built upon standard JBoss Application Server, the unified Application Server replaces separate services found in previous versions of DPA, namely Controller, Reporter, Listener, Publisher and Analysis Engine. These are now functions performed by the unified Application Server.

The embedded DPA Datastore consolidates the three previous databases, namely Config, Datamine, and Illuminator. This allows not only for tighter integration between backup and replication, but also for better performance and supportability. The new DPA 6.0 datastore uses PostgreSQL technology.

The industry-standard REST API is used to access DPA data through standard HTTP(S)/XML protocols. This interface allows for DPA integration with other EMC management products via mashup technology.


The DPA 6.0 Server is 64-bit software that runs on either Windows, Linux, and Solaris (including Solaris 10 local zones). Replication Analysis (RA) is now supported on the three OS platforms, which represents a significant departure from the past, when RA was supported on Windows and Solaris only.


In all DPA 6.0 production environments, the DPA Server must be installed separate from its Datastore; that is to say, each on its own system. This is known as a Split Server/Datastore deployment, and it requires that the Datastore be installed prior to the Server. The single Application Server and single Datastore architecture is recommended for most small to mid-size production environments; the multiple Application servers and single Datastore design, to be discussed in the next slide, is for large environments. In virtualized datacenters, the virtual machines used for the Split configuration can be on the same virtualization server or on different ones.

Also supported is a Complete Server installation, when the DPA Server and its Datastore are installed on the same system. However, this configuration is recommended only for proof of concept (POC), testing, or Lab purposes, never for production environments.

Two Data Collection agents are installed during the Split Server/Datastore deployment: one for the Server system and one for the Datastore system. During the Complete Server installation, only one Agent is deployed.

DPA 6.0 demands more RAM and CPU power than previous versions. In the Split configuration, each system must have at least two processing cores or CPUs and eight GB RAM. The system used for a Complete configuration must have at least four processing cores or CPUs and eight GB RAM.

Remember to use EMC Data Protection Advisor Server Sizing Calculator to determine the size the DPA Server required for the specific customer environment.


As has been said, the multiple Application servers and single Datastore architecture is recommended for large datacenters, including cloud environments. With this deployment, a customer supplied load balancing switch may be placed in front of the DPA Application servers to distribute the user load, which can also be balanced manually by assigning groups of users across different Application servers. In virtual environments, Application servers can be brought online or offline as the user load demands; for instance, additional servers can be brought online to handle the increased load during peak monthly reporting periods.

One of the key design considerations for this new architecture was the ability to offer increased flexibility and scale-out options for large customers and multi-tenant service provider environments. Accordingly, Application servers can now be grouped into clusters that will handle the load placed on DPA by one group of users, without affecting the work of separate clusters managing other sets of users. This new functionality also enables the separation of DPA Application servers used for processing Collection agents data from DPA Application servers dedicated to run reports.


To align with the configuration options previously described, the DPA Server installer provides three deployment options:

Application Service, which installs the Application Server features only

Datastore Service, for the installation of the datastore only

Application and Datastore Service, to perform a complete system installation

Notice that a DPA Collection Agent is included with each option. There is a separate agent-only install package as well.


The type and quality of the hardware used for the Datastore system drastically impacts the overall performance of your DPA 6.0 solution. Here are some guidelines for selecting hardware for your Datastore system.

Disk types: Fast Ultra-320 SCSI disks are your best option. However, high-end SATA drives are also very good. SATA is substantially less expensive, which will let you get more spindles with your money.

RAID Controller: Ensure that the RAID controller can keep up with 8 fast hard drives.

RAID configuration: The optimum configuration is RAID 1+0, with as many disks as possible. Consider also deploying your transaction log on a separate disk (or stripe) all by itself. RAID 5 is not a very good option for databases unless you have more than 6 disks in your volume.

RAM: The more RAM you have the more disk cache you will have. This greatly impacts performance, considering that memory I/O is thousands of times faster than disk I/O. In general the more RAM and disk spindles you have in your system, the better it will perform. More RAM involves less disk access, and extra spindles will help spread the reads and writes over multiple disks, thereby increasing throughput and reducing drive head congestion.


A typical DPA 6.0s high performance Datastore configuration would include:

2 disks in mirror for the OS and DPA Datastore binaries.

2 disks in mirror for the Datastore transaction log.

4 disks in RAID 1+0 for the Datastore data files.


Will the DPA infrastructure be deployed on a virtualized server? What virtualization solution will be used, VMware or Hyper-V?

In a virtualized environment, it is recommended that:

Server CPU specifications be at least 20% higher than the recommended value for a non-virtual environment.

CPU cycles be reserved on the physical machine hosting the VMware or Hyper-V machine running the DPA server.

The memory of the VMware guest running DPA 6.0 be completely retained inside the memory of the VMware host, instead of being swapped out.

Remember that, in addition to interacting with the network and security personnel, DPA 6.0 administrators will now need to coordinate their work with the virtualized infrastructure administrators.


Listed here are the license changes in DPA 6.0.

In previous releases, DPA license for Avamar was based on Avamar grid hardware capacity, primary and replicated. In 6.0, DPA license for Avamar is based on the software capacity (size of grid plus size of data stored on data domain). Regardless of this change, there will be only one Avamar license for both DPA 5.x and 6.0. In previous versions, Avamar replicated capacity needed to be licensed; in 6.0, this is not required.

NetApp support has been discontinued and does not have a license in DPA 6.0.

Also, DPA licenses for Symmetrix and RecoverPoint have been merged into one that is capacity based.

DPA licenses for VNX File, Celerra and CLARiiON, not enforced in previous versions of DPA, are not used with 6.0, since they have been discontinued. There is no change in licensing for VNX block in DPA 6.0.


The process for obtaining and activating DPA 6.0 licenses is shown here. Most recent license changes will always appear in the latest EMC Data Protection Advisor Release Notes .

1. Customer sends EMC a purchase order through a regular Sales channel.

2. Sales channel submits the order to Powerlink Licensing.

3. Customer receives a License Authorization Confirmation (LAC) email letter for the purchased licenses.

4. To activate the software license certificate, customer goes to Powerlink Licensing (Powerlink.emc.com > Support > Software Downloads and Licensing > DPA) and enters the LAC and the DPA Servers host ID.

5. Powerlink Licensing sends the customer a product license activation email containing the license software keys (one *.wls file or more).

6. If the new license is a replacement for an existing license, customer deletes the old license using DPA License Manager.

7. Customer adds new license.


The DPA Collection Agent runs on Solaris, Windows, HP-UX, AIX, and Linux. You need to know the minimum requirements for this component.

The Agent can run on Solaris 9, 10, or 11 SPARC with an UltraSPARC III CPU minimum. The Solaris patch cluster must be in place, and Solaris 9 requires patches 111711-11 and 111712-11 as well. The Agent also runs on Solaris 10 or 11 on the x86 64 bit platform. If deploying the Agent on Solaris zones, it must be installed on a local zone. Keep in mind that disk Status requests are only supported on Solaris hosts running kernel 2.6 or later on SCSI disks. Tape Drive Performance system data applies only to Solaris hosts .

On Windows, ensure that the latest Service Pack is installed and that WMI has been enabled, since performance data collection depends upon it.

Similarly, ensure that the latest Linux patches are installed. On both Red Hat and SUSE, the X Font Server (xfs) must be running. If DPA is monitoring an Oracle database or Oracle RMAN on Red Hat, both libaio 0.3.105 and libaio-devel 0.3.105 must be in place; if monitoring those objects on SUSE, libaio 0.3.104 and libaio-devel 0.3.104 are required.

To collect performance statistics from AIX, make sure that the bos.perf.libperfstat file set is installed on the host.


Shown is an overview of the activities to perform in preparation for DPA 6.0 deployment. To scale requirements to your site, consult the EMC Data Protection Advisor Server Sizing Calculator.


Previous versions of DPA cannot be automatically upgraded to 6.0; instead, they must be migrated over to the new DPA 6.0 Server using the Migration Tool. Only DPA systems at level 5.5.1 or higher can be migrated; users of earlier versions must upgrade to 5.5.1 or a later version.

For DPA 5.5.x systems that use iAnywhere databases, the Migration Tool must be installed on the DPA 5.5.x Server. This is a requirement. For DPA 5.5.x systems that use other types of database management technologies, EMC recommends that the Tool be installed on the 5.5.x system, although the Tool could also be installed on any system that has connectivity to both the DPA 5.5.x and DPA 6.0 servers.

The DPA 6.0 Server must be deployed on separate hardware, which need not use the same OS platform, since the Migration Tool allows for the transfer of data between different types of DPA 6.0 Server. Thus, plan accordingly.

The migration process should not place a noticeable load on your DPA 5.5.x system, which will remain fully operational during the migration process. The DPA Migration Tool will estimate the duration of the migration. EMC recommends to schedule for a time when the DPA 5.5.x system is not being heavily used. Depending on the size of the Datamine database, the migration process could take from several hours to several days. To reduce migration time, EMC recommends limiting the amount of historical data to be moved.

In order to keep DPA 6.0 in sync with the system being migrated, the Migration Tool can be run more than once, as it keeps track of where it last left off. When the decision to cut over is made, one last migration pull must be done.

The migration process involves the following steps:

1.Install the DPA 6.0 Server on separate hardware.

2.Install the DPA Migration Tool.

3.Execute the Migration Tool to analyze and move the DPA 5.5.x data.

4.Install DPA 6.0 Data Collection agents, or redirect pre-existing collectors to the new DPA 6.0 Server.

5.Decommission the DPA 5.5.x Server.


Some traditional DPA features are not present in 6.0:

DPA 6.0 does not include support for NetApp appliances.

Theres no upgrade but a migration path for existing customers.

The DPA database schema is not open for direct SQL manipulation, since the DPA 6.0 datastore is accessible only by the DPA Server.

Custom analysis rulesets cannot be automatically migrated and must be manually recreated as analysis policies in DPA 6.0, since the new Analysis Engines architecture is different from that of previous versions.

Backup Auto-reconciliation Policies are considered deprecated and are not available.

The DPA 5.x API, which is not based on REST principles, is no longer available and has been replaced by the DPA 6.0 REST API.

Some types of report charts such as candle, bubble, 3D, and surface are not available in DPA 6.0.

HomeBase went End-of-Life on August 2012; DPA support for the product has been discontinued in 6.0.

Finally, DPA 6.0 does not support the import of hosts from EMC Ionix ControlCenter.


This module presents requirements concerning the DPA infrastructure and the multiple types of objects that can be discovered in a DPA 6.0 environment.


Here are some preliminary network considerations that should guide the design of your DPA 6.0 solution. The tables right column lists questions that you might ask:

What is the network topology?

Will there be firewalls between the end user and the DPA Server? DPA 6.0 uses standard ports for communication with service providers such as WMI, SSH, SNMP, etc; these ports must be available to the product. Do specific security regulations apply to your customers datacenter, and does network security comply therewith?

If DPA 6.0 will be deployed on virtualized hosts, what group manages the IP virtual network and switches?

Does your customers datacenter have directory services in place (Active Directory/LDAP)? Will there be DNS resolution between the end user desktops and the DPA Server?


The DPA 6.0 GUI must be launched from a JavaScript enabled browser that connects to the Web server running on the DPA Server. The minimum requirements for launching the GUI are described in this table. The browser requires a minimum of 512 MB of memory and 50 MB of disk space.

Flash 10.1 or later is also required. Some customers will not be able to download the Flash Player to their desktops due perhaps to company security policy, so make provisions to install the Flash Player in some other way, such as pre-installing it on customer desktops.


BY default, DPA 6.0 uses TCP port 9002 for HTTPS access to the Web console and the REST API. Note that the DPA GUI may remain inaccessible even after users authenticate with firewalls, due to IP address to hostname resolution issues. That is why your design should indicate that client-computer DNS settings may require reconfiguration: those settings should contain the DNS domain name hierarchy necessary to translate between the DPA Server computers FQDN and its IP address.

Still, after DNS reconfiguration the DPA GUI may remain unreachable; thus, indicate in your design that the client computers hosts file may help locate the DPA Server computer: the latters network information can be added to the hosts file.


Shown are considerations concerning storage arrays when Replication Analysis is part of the DPA package:

Does DPA 6.0 support the array models in the customers datacenter or datacenters? For Replication Analysis, the product supports VMAX, CLARiiON CX, AX4-5, CX3 and CX4 running Flare 02.19 or higher, as well as VNX, which requires Flare 05.31 or 05.32.

Current storage configuration is relevant, at the very least, as a baseline.

Does the customer have a business continuity setup in place (snaps, mirrors, BCVs, etc.)?

Does the customer suspect storage performance issues? This question is pertinent even if the cause of the performance problem cannot be determined at the moment, which will also give you a chance to stress the need for Replication Analysis.

What personnel will be handling DPA 6.0 storage? What skills do they have? Will they need DPA training?


This slide lists requirements for configuring data collection through DPA 6.0s Discovery Wizard. Here we name the pieces of information needed for discovery of virtual disks and discovery of servers and arrays.


The information necessary for monitoring Oracle and SQL databases is shown here. For PostgreSQL monitoring, the user account must have super user privileges.


For discovery of backup servers, tape libraries, and I/O devices, the information necessary is listed in the picture. If a DPA Agent is installed on the backup server, no user credentials will be needed.


The picture shows the ports required for both local and remote discovery.

When a DPA Agent is installed on an application host (for example, a host with Solutions Enabler, Oracle, or SQL Server), or when the Agent is running by itself , port 3741 must be open in such a host.

If the application host does not contain an Agent , RPC (UDP port 135), FTP (TCP port 21), SSH (TCP port 22), and Telnet (TCP port 23) should be enabled and accessible to the DPA Server.

When the DPA Agent is installed on a Windows host acting as proxy for the remote discovery of other Windows hosts from a Solaris DPA Server, TCP port 3741 must be open on the proxy host, and RPC services along with WMI must be accessible (UDP port 135). On the DPA Server, TCP ports 25011 and 8090 must be open. The latter port is used for communication between DPA and the Windows proxy Agent.

DPA discovers application hosts running in a VMware environment using VI-SDK (TCP port 443).


In version 6.0, Replication Analysis supports VPLEX appliances that are deployed in conjunction with RecoverPoint. DPA will calculate the recoverability status for the application or file system on the host that is connected to VPLEX and replicated by RecoverPoint.

DPA will not support applications or file systems that use VPLEX and are replicated by back-end storage technologies.


DPA 6.0 also adds support for Oracle Automatic Storage Management (ASM). ASM simplifies administration of Oracle related files by allowing the administrator to reference disk groups rather than individual disks and files. The ASM functionality is an extension of Oracle Managed Files (OMF), which also includes striping and mirroring to provide balanced and secure storage. ASM can be used in combination with existing raw and cooked file systems, along with OMF and manually managed files.

DPA can discover and monitor ASM disk group databases, when the following requirements are met:

Linux OS only

ASM instances using ASMLib

ASM based on disks and partitions; LV, LOFS and NFS devices are not supported.

Oracle 10.2 or later


When working as a proxy host for remote data monitoring, the DPA 6.0 Data Collection Agent must meet some requirements to communicate with applications hosts. Those requirements are shown in this slide and similar ones to be presented.

Here prerequisites for communication between the Data Collection Agent and EMC products are shown. Concerning Avamar, the Agent must be installed on a host that is in the same time zone as the Avamar server. Remember that the Agent should never be deployed on the Avamar Storage Node. DPA connects to Avamars mcdb database through default port 5555, using the viewuser account or one with equivalent privilege.

If monitoring NetWorker remotely, the NetWorker client package must be installed on the Agent host. For remote monitoring of NetWorker 7.5 or later, the DPA Agent service user and the proxy host must be added to the Users list of the NetWorker Administrators User Group. The NetWorker Servers hostname must be resolvable.

RecoverPoint is always monitored from a remote Agent that accesses the RecoverPoint Command Line Interface (CLI) through SSH port 22, using an account with sufficient privileges to run a CLI commands, such as the monitor (default password monitor).


We continue with the prerequisites for communication between the Data Collection Agent and EMC products.

Before starting gathering data from EMC Data Domain, SNMP must be enabled on the backup appliance, and a read-only community string must be set. If the community string is other than public, the value of the community string used as DPA Credential must be changed accordingly. SSH must also be enabled, since the DPA Agent uses it to issue CLI commands to the appliance.

In order for Data Protection Advisor 6.0 to monitor the EMC Disk Library Series, the hostname of the disk library must be resolvable from the Agent host. Since DPA gathers data via SNMP (default UDP 161 port), the DPA credential for the appliance must have the correct SNMP community string, which is public by default, but must be changed to match the value of the community string on the EDL.


CA BrightStor ARCserve hosts are monitored from a Data Collection Agent running locally on the ARCserve computer or remotely from a Windows computer in the environment. The ARCserve Manager must be present on the Agent host, and the Agent must be able to resolve the hostname of the ARCserve machine. The DPA credential must match an existing ARCserve account.

DPA monitors CommVault Simpana from an Agent running on the Simpana database, or from any remote Agent. The Agent has to run as an account that has permission to access and execute read-only statements in the CommVault database. If this is remote to the CommVault host, the hostname and instance name of the CommVault database must be part of the DPA credential. The CommVault server hostname must be resolvable from the remote Agent host.

HP Data Protector servers are monitored by a DPA Agent running locally on the HP Data Protector Cell Manager, or remotely on another computer. However, the DPA request for status information can only be set up locally. Data Protector environments with Manager of Managers capabilities can be monitored remotely only, and require that Data Protector client software be installed where the Agent runs. This, the Agent, must be configured to use a Data Protector account with permissions to run reporting and notifications and see private objects.

DPA collects data from an HP EVA Disk Array being monitored by HP Command View via an Agent running locally on the Command View host, or remotely on any other computer. The DPA credential must match a valid username and password defined in the Command View CIM server. The Agent gathers data via SMI-S, using the secure port 5989.


DPA 6.0 can 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). When monitoring a TSM instance remotely, the TSM client software must be installed on the DPA Agent host. The DPA credential for TSM only requires Analyst or Operator privileges. If using Gresham Clareti EDT (6.3.0 to 8.0), the TSM Server host needs a DPA Agent in it. If the TSM Server instance is a shared Library Client, the Agent must monitor the TSM Library Manager server to gather additional data. Remember that on UNIX platforms the dsm.opt SERVERNAME setting must contain a TSM instance name that corresponds to a dsm.sys stanza with identical SERVERNAME. In that stanza, the TCPServeraddress and TCPPort settings of the TSM instance must be specified.

DPA 6.0 gathers Oracle backup information remotely, via RMAN, the Oracle Recovery Manager utility. To collect such data (control file and/or recovery catalog), the Agent can be on the DPA Server, on an separate host, on the Oracle server, or on the RMAN server. The Oracle client binaries are needed where the Agent is running. To connect to RMAN, DPA needs 'SELECT' only privileges on the RMAN catalog.

Symantec NetBackup can be monitored by a DPA Agent running locally on the NetBackup Master Server, or remotely on any other host such as the DPA Server. To successfully gather data remotely, the NetBackup Server binaries must be installed on the Agent host, and the DPA credential must match an existing NetBackup account. If the NetBackup Master Server runs on UNIX, the name of the DPA Agent host must be in the bp.conf file. Make sure that the setting SERVER = is part of /usr/openv/netbackup/bp.conf. If the NetBackup Master Server runs on Windows, be sure that the name of the DPA Agent host has been added to the list of servers allowed to access the Master Server; this is typically done via the NetBackup Administration Console. The name of the DPA Agent host must be resolvable by the Master Server.

DPA can monitor a Symantec PureDisk server from an Agent running locally on the PureDisk Server, or remotely on a different host. PureDisk can only be monitored on SUSE 10. PureDisk servers implement a firewall that may prevent DPA from gathering data or from communicating with a DPA Agent installed on the PureDisk server. The DPA credential cannot be the root account.


For the products listed on this slide, set the SNMP Request setting to Enabled. Set the SNMP community string used as DPA credential to public or as defined on the tape library. Default SNMP port is 161. For IBM TS 3584, enable the SNMP Trap setting.


For HP StorageWorks, enter the IP address of the DPA Server in the Trap Address field. Set the SNMP community string used as DPA credential to public or as defined on the tape library.

For Fujitsu libraries, enable SNMP requests. Here also, set the SNMP community string used as DPA credential to public or as defined on the tape library.

ACSLS cannot be monitored remotely. A DPA Agent must be installed on the ACSLS host machine.


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. Fibre Channel Alliance MIB must be loaded and enabled on the switch.


If the DPA 6.0 environment is licensed for Replication Analysis, provide the Solutions Enabler (SE) host to discover Symmetrix or VNX/CLARiiON arrays. 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 Symmetrix arrays by a SAN connection. The host must have the TCP port 443 or 2163 enabled for the VNX/CLARiiON connection.

If the SE host is 64-bit, the 64-bit Solutions Enabler version must be used. One SE host can discover all VNX/CLARiiON arrays via IP address. For VNX/CLARiiON discovery, EMC recommends installing Solutions Enabler on the DPA server.

Symmetrix monitoring requires the Base and Dev Masking licenses. VNX/CLARiiON monitoring requires the Base license only if the symcfg command will be issued. A minimum of one gatekeeper per HBA per Symmetrix is required.

If RecoverPoint will be monitored, remember that the monitoring must be done from an Agent installed remotely (the DPA Server, for instance).

If monitoring Microsoft Exchange or a database remotely, the DPA Server must be able to resolve the application host.

Ensure that the required ports between the DPA Agent and the monitored objects are open, and that the DPA credentials used for discovery have correct privileges.


DPA 6.0 can remotely discover and monitor hosts on the IP network only if they have been correctly configured.

DPA discovers remote Windows hosts (Server 2003 and Server 2008) using their Windows Management Instrumentation (WMI) settings. Local operating system or domain credentials can be used to access hardware and software information from each Windows host. RPC communication is a prerequisite. if your DPA 6.0 Server runs on Solaris or Linux, Windows host discovery requires a proxy DPA Agent running on Windows.

UNIX and Linux hosts are discovered remotely via SSH, a network protocol that allows data to be exchanged using a secure channel between two networked devices. The SSH daemon must be running on the host for DPA to perform a discovery. Much like WMI, SSH uses operating system credentials for access; however, the SCSI commands that DPA needs to execute to successfully discover storage related information requires root privileges not normally allowed through SSH. To work around this common policy, the substitute user do (sudo) can be used. This utility temporarily grants a users credential the privileges needed to execute root-level commands associated with DPA discovery.

DPA 6.0 discovers virtualized VMware environments via VI-SDK, by accessing the vSphere server, not individual ESX/ESXi hosts. You will need to supply correct credentials for the virtual machines you choose to discover, in order to complete their identification as DPA host objects.

Remember that, in environments licensed for Replication Analysis, DPA has the ability to identify hosts via the Symmetrix and VNX/CLARiiON configuration. This type of discovery is useful when security concerns dictate against the installation of a local Data Collection Agent, or the deployment of a remote onewhich requires the disclosure of domain or local credentials.


Your design must include provisions for Fibre Channel switch discovery. Before a switch can become part of DPA 6.0, ensure that its hardware and software are listed in the EMC Data Protection Advisor Software Compatibility Guide. All switches must have TCP/IP connectivity.

DPA uses SNMP to discover all supported switches, using the default UDP port 161. It can discover any IP switch that supports SNMP MIB-2, using the community string value (public by default).

DPA can also discover any Fibre Channel switch that supports Fibre Alliance MIB v2.2, v3.0, and v4.0. To ensure that Brocade FC switches return all data, the Fibre Channel Alliance MIB must be loaded and enabled on the switch. Note that this MIB might not be installed on the switch by default.

To discover and monitor Xsigo I/O directors, DPAs SNMP credentials must contain the Director SNMP community string in the Password field of DPAs Credential Properties dialog box. Unless the community string was modified on the Director, the community string must be set to public.


EMC-array discovery with DPA 6.0 uses Solutions Enabler (SE).

For Symmetrix discovery, SE supported versions are 7.2, 7.3.0.1, 7.3.1, 7.3.2, and 7.4. The SE host must be capable of communicating with the Symmetrix array by a SAN connection, and must have a minimum of one gatekeeper per HBA per Symmetrix. Symmetrix array monitoring requires the Base and Dev masking licenses.

VNX/CLARiiON discovery also requires Solutions Enabler. If the customer only has this type of array, Solutions Enabler can be installed on the DPA 6.0 Server. SE 7.4.0.6 is the minimum version required and IP connectivity must exist between the SE host and the array Service Processors, via either TCP port 443 or port 2163. Once connectivity is established, Solutions Enabler commands must be used to authorize and discover the arrays.

In order to gather data from HP EVA Disk Array, DPA uses secure SMI-S running on the HP Command View server.


Additional details may be found at the resources listed here.


These are the key points covered in this course. This concludes the instruction; please proceed to the course assessment.


dpa60-planningdesign_srg.pdf

Documents

Transcript of dpa60-planningdesign_srg.pdf