Pass the EMC Data Protection D-AV-DY-23 Questions and answers with CertsForce

Explanation/Reference:

D:\Documents and Settings\useralbo\Desktop\1.jpg

Explanation/Reference:

D:\Documents and Settings\useralbo\Desktop\1.jpg

Avamar Node Types and Processes

There are several different types of Nodes within an Avamar Server. The Utility node is the identity of the Avamar Server and provides the bulk of the internal Avamar server processes such as: Avamar Administrator (used to manage the Avamar Server from a gui), cron jobs, DNS, NTP, external authentication, web access, MCS and EMS.

MCS (Management Console Server) provides centralized management including scheduling of backups, restore of backups, monitoring and reporting.

EMS (Enterprise Manager Server) provides web based management for multiple Avamar Servers as well as monitoring and configuration for Avamar Replication.

Web Access provides access to documentation, backup plug-ins as well as remote File System restore access to end users.

Are next type of node is the Storage Node, which run a process called gsan. This service communicates with the avtar command on the individual backup clients. Avtar communicates with a storage nodes gsan process, then that storage node spreads the data across the available data nodes.

A Spare Node is an active node that is present in a multi-node RAIN (Redundant Array of Independent Nodes) grid. The interesting thing about the Spare Node is that it is NOT a hot spare. There is a procedure in place that needs to be followed when a failed Storage Node occurs. In fact, the Avamar Server doesn’t even care if the Spare Node is powered on, so if you are a “Green” conscience company, feel free to leave the Spare Node powered down. Dell Best Practice is to leave the Spare Node up and active though. Avamar Backups clients can be installed with 2 different types of client plug-ins: File System and Databases. The Avamar client uses 2 processes in the backup and restore process: Avtar and Avagent. The Avagent process listens for backup/restore work orders from the MCS service on the Utility Node using port 28002 and executes the avtar command that handles the backup/restore processes and communicates with the gsan service on the storage nodes. This process is depicted in the included picture above.

Lastly, in a previous blog, I discussed the 2 different licensable options for Avamar and how the disks are comprised in each Storage Nodes type. These are depicted in the picture above as well as a breakdown of how the disks are structured.

Explanation/Reference:

D:\Documents and Settings\useralbo\Desktop\1.jpg

Explanation/Reference:

D:\Documents and Settings\useralbo\Desktop\1.jpg

Explanation/Reference:

For Gen4 3.9TB node:

Raw capacity is 6 TB and licensed capacity is 3.9 TB

For Gen4 7.8 TB node:

Raw capacity is 12 TB and licensed capacity is 7.8 TB

So, In a RAIN config with 1 utility node and 4 storage nodes (7.8 TB), the total capacity should be 48 TB and total licensed capacity is 31.2 TB

Explanation/Reference:

Capacity Threshold Warnings:

80% of user capacity = warning, start planning for expansion or cleanup

95% user capacity is the health check warning, new backups are suspended

100% user capacity makes the Avamar read-only, can still restore from server

85% of OS capacity = Garbage collection stops running, utilization increases rapidly

90% OS capacity = HFS checks stop running

96% OS capacity = no more checkpoints