D-AV-DY-23 Exam Questions and Answers

QUESTION: 25

What is the maximum number of nodes that can be configured for an Dell Avamar multi-node grid?

15 storage, 1 utility, 1 NDMP, and 1 spare
16 storage, 1 utility, and 1 spare
17 storage and 1 utility
17 storage, 1 utility, and 1 spare

Answer(s): B

Explanation:

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

QUESTION: 26

A company is using an Dell Avamar multi-node server with 2 TB storage nodes. The company wants to add 3 TB of Avamar storage to the multi-node server.

How can this be achieved?

Add one 3.3 TB storage node
Add two 2 TB AVEs
Add two 2 TB storage nodes
Add three 1 TB storage nodes

Answer(s): C

Explanation:

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

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

Reveal Solution Next Question

QUESTION: 27

Which client process listens for a work order from the Dell Avamar server?

avagent
avtar
avscc
mcs

Answer(s): A

Explanation:

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.

Reveal Solution Next Question

QUESTION: 28

In Dell Avamar, what is a variable-size unit of deduplicated data?

Chunk
Stripe
Hash
Block

Answer(s): A

Explanation:

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

Reveal Solution Next Question

QUESTION: 29

An Dell Avamar customer, without premium support, has a requirement to be able to recover from a failed storage node.
What is the minimum amount of nodes, of all types, that is required to support this functionality?

1
2
3
5

Answer(s): D

Explanation:

Single Node.

Also known as the Non-RAIN (Redundant Array of Independent Nodes) configuration. This is the entry level configuration in which the single node acts as the utility node and the data storage node.
When using this configuration 2 single nodes are needed. 1 is the main backup node, and the 2nd is used for replication purposes for fault tolerance. Used in small to medium sized environments.

Muti-Node Non RAIN.

This is basically is a 3 node setup consisting of 1 Utility Node and 2 Data Storage Nodes. It allows for double the storage capacity of a Single Node device.

This configuration also needs a duplicate setup for replication, so a total of 6 Nodes would be needed for fault tolerance. Used in medium sized environments.

Multi-Node RAIN.

The Standard RAIN configuration has 1 Utility Node, 4 Data Storage Nodes and 1 Spare Node. This configuration can be expanded for a total of 16 Data Storage Nodes max. All of the nodes work together to balance the storage equally across all of the other Data Storage Nodes. This architecture is easily scaled by adding as many Storage nodes as necessary. Typically used in large environments, this configuration can be initially setup with 3 Storage nodes instead of the standard 4 Storage nodes. It is recommended to setup a duplicate Multi-Node RAIN for replication, typically at a DR site. Although it is recommended, it is not a necessity like the Non-RAIN configurations, because there is a spare node that can be configured at any point for fault tolerance.

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