D-AV-DY-23 Dell Avamar Deploy 2023 Exam Questions and Answers

Explanation/Reference:

The location of the client logs will vary depending on the platform:

On Windows: C:\program files\avs\var\

On Linux: /usr/local/avamar/var

On other UNIX platforms: /opt/AVMRclnt/var

On NetWare: sys:\avamar\var

On MAC: /private/var/avamar

You can retrieve maintenance logs (checkpoint, hfscheck, gc) using the "dumpmaintlogs" command and the

GSAN itself logs errors in /data01/cur/err.log on each node but in general.

Explanation/Reference:

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

Explanation/Reference:

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

Explanation/Reference:

Review Avamar Fundamentals free course on Dell

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

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

https://learning.Dell.com/Saba/Web/Customer

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

Explanation/Reference:

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

Explanation/Reference:

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

Explanation/Reference:

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

Explanation/Reference:

Iperf

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

EBSS

While there are several products that can be used to size an Dell deduplication system for Avamar or Data Domain, only the Dell Backup System Sizer (EBSS) is an official Dell product. It runs on Adobe Air and there for runs on Windows or Mac, and Dell recommends you always download the latest version. It will come in a zip file which includes supplements and a client questionnaire.

Performance Assurance Tool

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

Explanation/Reference:

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

Explanation/Reference:

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

Explanation/Reference:

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

Explanation/Reference:

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

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

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

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

Explanation/Reference:

The most important thing to do on a client with so many files is to make sure that the file cache is sized appropriately. The file cache is responsible for the vast majority (>90%) of the performance of the Avamar client. If there's a file cache miss, the client has to go and thrash your disk for a while chunking up a file that may already be on the server.

So how to tune the file cache size?

The file cache starts at 22MB in size and doubles in size each time it grows. Each file on a client will use 44 bytes of space in the file cache (two SHA-1 hashes consuming 20 bytes each and 4 bytes of metadata). For 25 million files, the client will generate just over 1GB of cache data.

http://jslabonte.blogspot.com/2013/08/avamar-and-large-dataset-with-multiples.html

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

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

Explanation/Reference:

The OS View is the total file system in the Avamar, while the gsan View is the total allocated to stripes. Gsan view is 65% of the Avamar server and it is used mainly for user data - this is the licensed capacity. Above that, 20% of the system file space is used for checkpoint overhead and the remaining 15% is for the operating system.

http://gregandthenetwork.blogspot.com/2013/11/managing-avamar-server-capacity.html

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.

Please stop back by later, I plan to talk about the NDMP Accelerator and it’s role in the Avamar System.

Explanation/Reference:

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

Explanation/Reference:

vamar, has a rather nifty technology called Sticky Byte Factoring which allows it to identify the changed information inside a file by breaking the file into variable length objects, this leads to much greater efficiency than fixed size approaches as changes made early in a fixed length sequence affect all subsequent blocks/chunks/objects/whatever in that sequence. This in turn changes all the fingerprints taken following the changed data which means you end up with a lot of new blocks/chunks/objects/whatever even if the data really hasn't changed all that much. Sticky Byte Factoring on the other hand can tell what exactly has changed, not just that things have changed.

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

Explanation/Reference:

The most important thing to do on a client with so many files is to make sure that the file cache is sized appropriately. The file cache is responsible for the vast majority (>90%) of the performance of the vamar client. If there's a file cache miss, the client has to go and thrash your disk for a while chunking up a file that may already be on the server.

So how to tune the file cache size?

The file cache starts at 22MB in size and doubles in size each time it grows. Each file on a client will use 44 bytes of space in the file cache (two SHA-1 hashes consuming 20 bytes each and 4 bytes of metadata). For 25 million files, the client will generate just over 1GB of cache data.

http://jslabonte.blogspot.com/2013/08/avamar-and-large-dataset-with-multiples.html

Explanation/Reference:

Not sure about the original answer!!

Road Map for Avamar 6#

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

Road Map for Avamar 7#

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

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

Explanation/Reference:

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

Explanation/Reference:

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

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

Explanation/Reference:

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

Explanation/Reference:

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