DPA is comprised of 3 components as of version 6.0. There is an application server, a data store and an agent. The Application Server and Datastore can be installed on the same box or separated for scalability.
The applications server is the main interface and replaces several services previously in use by DPA such as the controller, the Reporter, the Listener, the publisher and the analysis engine. The data store is a PostgreSQL database and is embedded in the project, replacing the Illuminator, Configuration and Datamine databases. This gives tighter integration and better performance.
The Data Collection Agent gathers data. It is automatically installed on the Datastore and Application Server, and can also collect data remotely using a proxy server for systems for which there is no installable agent, such as data switches and Fibre switches. Lilnux servers require an agent be installed and can not proxy data. The DPA version 6 supports the newer agents as well as DPA 5.5 and newer collectors, and sends the data via http and XML.
DPA uses REST (REpresentational State Transfer) to interface the components. The CLI, the GUI and the agents all communicate with the App server through the REST API. The REST API also communicates with the messaging service and the Datastore. DPA 6.0 uses a high-performance messaging bus, which utilizes an append-only journal that fits in a single disk cylander for performance. REST also launches responses to events in the UI.
DPA is built on JBoss, which is owned by RedHat, and uses PostgreSQL 9.1 as the database. No users are able to access the database without using the "apollosuperuser" account unless they acces sit through the REST API. The apollosuperuser account is a non-privileged account with full access to the database.
Files are kept in "/opt/emc/dpa/services/datastore/data and /engine. The transaction log is pg_xlog, and log rotation happense automatically at 250MB. The max connections to the datastore is 100.
DPA is event-driven, or uses the Event Driven Architecture. The analysis engine uses policies and compares data with those policy conditions to provide recommendations and events.
DPA will run on Solaris 10-11, Windows 2003-2008R2, and RedHat or SuSE linux on 64-bit platforms with 8 GB of memory. If DPA's components are all on one box, 4 CPUs is required, and if they are split out, 2 CPUs per server are required.
The main ports for DPA are 3741, 9002 and 9003. 9002 is the HTTPS connection from agents to server, 9003 is PostreSQL and 3741 is the agent HTTP connection.
DPA Agent will run on Windows, Solaris, Linux, HP-UX and AIX, both 32- and 64-bit architectures.
DPA can be licensed in a couple ways. The DPA for backup is the main application and provides the majority of function. It is licensed by the number of clients unless you are using Avamar, at which point it is licensed by capacity like Avamar to keep things consistent. There is a DPA for Replication Analysis, which is licensed by TB for Symmetrix and RecoverPoint, and per array for VNX systems.
DPA for VMWare is licensed by ESXi host and provides for unlimited VMWare VMs.
VNX File, Celerra and Clariion require no license for use with DPA.
Hi, thanks for sharing the information. Could you please let me know default credentials for database access. While connecting it's asking me for credentials.
ReplyDeleteThe default credentials are administrator/administrator. If you need more specifics, or if you lost the installed credentials you'll want to contact EMC Support for assistance.
Delete