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

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

Explanation/Reference:

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

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

Explanation/Reference:

While performing the backup of system state using Windows VSS plugin choose the option "Create Disaster Recovery Backup", this option will allow you to perform restore of the system using "Avamar disaster Recovery Wizard"

https://community.Dell.com/thread/114519

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

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

Explanation/Reference:

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

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:

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

The total number of client connections which can be made to the Avamar server will vary according to which operations are currently running, how the connection is made and the number of data nodes which are online.

Various parameters in the /usr/local/avamar/var/mc/server_data/prefs/mcserver.xml file govern this behavior.

The number of concurrent jobs for the whole grid will not exceed max_current_jobs.

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

AVE 7 is#

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

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

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

Assisted Ref# https://Dell--c.na5.visual.force.com/apex/KB_HowTo?id=kA0700000004Nlp

Explanation/Reference:

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

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

Explanation/Reference:

http://gregandthenetwork.blogspot.com/2013/12/design-imapact-of-avamar-system.html

Garbage Collection is the single most important process to ensure a consistent state of the Avamar. If garbage collection is running, the system is in a read-only state and no other maintenance or backup can run.

Coincidentally, if backup is still running, garbage collection will not begin. Garbage collection can free up about 10GB/node/hour once the Avamar is in a steady state, but this will take longer as utilization of the Avamar grows.

Explanation/Reference:

I am sure answer is NOT A

As assessment I was selecting A which is not valid in the results

Avamar ensures protection from disk and data corruption through the use of RAID (redundant array of independent disks). The type of RAID depends on the particular node type.

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

The phases of hfscheck mentioned above run in the following sequence:

1- indexsweep

2- datasweep

3- paritysweep

4- refcheck

During the indexsweep phase, the system confirms the integrity of the index (the index is the "table of contents" for all the data on the system) and also caches the index entries for each data chunk onto the same disk where the chunk itself is stored. This is done to improve the performance of later phases of the hfscheck. The datasweep phase is typically the longest phase of hfscheck. This phase reads each data chunk from the system and compares the hash of that chunk with the hash that is recorded in the index. This confirms that each data chunk is the same as it was when it was backed up.

As I'm sure you know, multi-node Avamar systems are protected by RAIN parity. During the paritysweep phase, the parity information is recalculated and checked against the parity information on disk.

The refcheck phase of hfscheck checks the referential integrity of the backups by verifying that every chunk of data that is referenced by a backup can be found in the index.

https://community.Dell.com/thread/180789

Explanation/Reference:

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

Explanation/Reference:

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

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:

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:

http://whughgriffin.wordpress.com/2011/07/05/avamar-ads-gen4-node-hardware/

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

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:

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:

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