Networker integrates with VMWare much like Avamar. It will do guest-based backup with agents installed in the guest VMs for which the VM needs to be powered on. It will also do image-level backup using VADP using a proxy client that takes a snapshot, mounts the snap and backs up the snapshot. This reduces overhead on the ESXi host. Also, like with Avamar, CBT can be used to backup only changed blocks of data in the VMDK files. Individual file restore from VMDK can take place only on NTFS volumes.
Networker integrates with cloud services, both private and public. It will compress and encrypt the data in transit, as well as throttle bandwidth to ensure service level to applications and customers. It will handle backup, recovery, staging and cloning. Clones are infinitely appendable when storing in the cloud.
Networker integrates with DPA, providing expanded monitoring and predictive analysis.
Networker integrates with Avamar, making Avamar to be seen as a storage device. It will then use Avamar's source-based deduplication and the Avamar is referred to as the dedupe node. One advantage over Avamar is that Networker will allow multiple simultaneous backup of the smae client, for instance you can run a file level and database backup at the same time reducing time. All jobs are managed and configured through Networker, and all Networker Modules can be used. One caveat is that Networker will not manage Avamar Replication. That still needs to be configured and managed through the Avamare interface.
When a backup request is sent from Networker to Avamar, the save command spawns the avasm, which in turn spawns the nsravtar. The process then follows the normal Avamar backup routine where it checks the hash file on the storage node, creates a hash cache and compares to new data, etc.
Data Domain can act as an AFTD or FTD, it can be utilized as VTL over Fibre Channel, and it can be used wiht DD Boost. With DD Boost, you oobtain the benefit of central config and management of backup. Replication is also controlled in Networker when integrated with Data Domain. You can install DD Boost on a storage noe, or install it on the client and do client direct backup.
Working my way toward being a Full Stack Engineer. I work for a state University leading the Systems Team, looking to chart a future of the data center and how it looks to build into the cloud in a responsible and innovative manner. This blog is largely a place to stash things I pick up in daily work life and pursuit of knowledge.
Showing posts with label DPA. Show all posts
Showing posts with label DPA. Show all posts
Thursday, November 7, 2013
Networker Integration
Labels:
Avamar,
Backup,
Data Domain,
Data Protection Advisor,
DPA,
EMC,
EMCTA,
NetWorker
Wednesday, November 6, 2013
Data Protection Advisor Reporting
A few notes on the reporting capability of DPA. DPA offers real-time visibility into the entire backup environment. Alerts can be sent via SMTP or SNMP, and DPA will flagged missed SLAs, backup jobs that run longer than average and on data loss exposure.
The Capacity report trends and forecasts system utilization, such as tape or disk capacity.
The Change Management tracks changes made throughout the entire system and correlates them across the environment.
The Backup Report Card is an at-a-glance report showing backup of every system over a period of time in blocks. Green = good, red = bad. Allows drilling into backup job for details and statistics as well.
The DPA system assists in troubleshooting by correlating data from one end of the backup system to the end of it. It will bring together data from each system in the backup job's life, giving visibility to problem areas for rapid resolution.
The Capacity report trends and forecasts system utilization, such as tape or disk capacity.
The Change Management tracks changes made throughout the entire system and correlates them across the environment.
The Backup Report Card is an at-a-glance report showing backup of every system over a period of time in blocks. Green = good, red = bad. Allows drilling into backup job for details and statistics as well.
The DPA system assists in troubleshooting by correlating data from one end of the backup system to the end of it. It will bring together data from each system in the backup job's life, giving visibility to problem areas for rapid resolution.
Data Protection Advisor Architecture
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.
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.
Data Protection Advisor Overview
Data Protection Advisor, or DPA, is a monitoring and reporting tool for backup environments. It is a single tool to manage, report provide trending and analysis of the backup environment end-to-end, from storage to servers to network to applications. It is installable by the customer, and can be done in a couple hours.
Wednesday, October 30, 2013
DPA - Data Protection Advisor - Overview
EMC's Data Protection Advisor is one of the few customer-installable software packages from EMC. It is a monitoring tool only, and will keep metrics on all aspects of the backup system. It will touch storage, network, applications, and provide analysis and reporting, alerting, troublehshooting assistance and capacity planning. It provides no ability to modify configurations, however.
The main component of the DPA is its Proactive Analysis Engine. This software runs continually against the data being collected and stored in DPA's database to provide comprehensive visibility in to the backup environment. It gives a higher rate of compliance satisfaction because of the ability to see quickly what jobs are running/ran/failed and which component most likely caused any failure. It allows reduction in resources by measuring capacity of disk and tapes in a backup system.
It is targeted at very large, very complex data centers with multiple backup technologies with heterogeneous environments. The use case discussed includes some 87,000 backup jobs over better than 4000 clients.
The main component of the DPA is its Proactive Analysis Engine. This software runs continually against the data being collected and stored in DPA's database to provide comprehensive visibility in to the backup environment. It gives a higher rate of compliance satisfaction because of the ability to see quickly what jobs are running/ran/failed and which component most likely caused any failure. It allows reduction in resources by measuring capacity of disk and tapes in a backup system.
It is targeted at very large, very complex data centers with multiple backup technologies with heterogeneous environments. The use case discussed includes some 87,000 backup jobs over better than 4000 clients.
Subscribe to:
Posts (Atom)