E20-598 Practice Exam Questions with Answers Backup Recovery - Avamar Specialist Exam for Storage Administrators Certification

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Review Avamar Fundamentals free course on EMC

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

Explanation/Reference:

vamar, has a rather nifty technology called Sticky Byte Factoring which allows it to identify the changedinformation inside a file by breaking the file into variable length objects, this leads to much greater efficiencythan 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 changeddata which means you end up with a lot of new blocks/chunks/objects/whatever even if the data really hasn'tchanged all that much. Sticky Byte Factoring on the other hand can tell what exactly has changed, not just thatthings have changed.

Explanation/Reference:

The most important thing to do on a client with so many files is to make sure that the file cache is sizedappropriately. The file cache is responsible for the vast majority (>90%) of the performance of the Avamarclient. If there's a file cache miss, the client has to go and thrash your disk for a while chunking up a file thatmay 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 44bytes of space in the file cache (two SHA-1 hashes consuming 20 bytes each and 4 bytes of metadata). For 25million 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:

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 ofindependent disks). The type of RAID depends on the particular node type.

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 wherethe 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 thesystem and compares the hash of that chunk with the hash that is recorded in the index. This confirms thateach 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 paritysweepphase, 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 ofdata that is referenced by a backup can be found in the index.

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

Explanation/Reference:

Are next type of node is the Storage Node, which run a process called gsan. This service communicates withthe 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.

Avamar Node Types and Processes

There are several different types of Nodes within an Avamar Server. The Utility node is the identity of theAvamar 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 asmonitoring and configuration for Avamar Replication.

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

Are next type of node is the Storage Node, which run a process called gsan. This service communicates withthe avtar command on the individual backup clients. Avtar communicateswith 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 placethat needs to be followed when a failed Storage Node occurs. In fact, the Avamar Server doesn’t even care ifthe Spare Node is powered on, so if you are a “Green” conscience company, feel free to leave the Spare Nodepowered down. EMC 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 Avagentprocess listens for backup/restore work orders from the MCS service on the Utility Node using port 28002 andexecutes the avtar command that handles the backup/restore processes and communicates with the gsanservice 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 arecomprised in each Storage Nodes type. These are depicted in the picture above as well as a breakdown ofhow the disks are structured.

http://whughgriffin.wordpress.com/2009/06/03/avamar-system-overview/

Explanation/Reference:

https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000TkN

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Thisquestionwas for Avamar 6so removing queue from A will make it the best ideal answer.

Situationin Avamar 7#

Explanation/Reference:

Explanation/Reference:

Not sure about the original answer!!

Road Map for Avamar 6#

Road Map for Avamar 7#

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Avamar Node Types and Processes

There are several different types of Nodes within an Avamar Server. The Utility node is the identity of theAvamar 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 asmonitoring and configuration for Avamar Replication.

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

Are next type of node is the Storage Node, which run a process called gsan. This service communicates withthe 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 placethat needs to be followed when a failed Storage Node occurs. In fact, the Avamar Server doesn’t even care ifthe Spare Node is powered on, so if you are a “Green” conscience company, feel free to leave the Spare Nodepowered down. EMC 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 Avagentprocess listens for backup/restore work orders from the MCS service on the Utility Node using port 28002 andexecutes the avtar command that handles the backup/restore processes and communicates with the gsanservice 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 arecomprised in each Storage Nodes type. These are depicted in the picture above as well as a breakdown ofhow the disks are structured.

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

Best Practices for Adding Large Filesystem Clients

-Ensure the file cache is sized properly

-Work with support / account teams to investigate using cache prefixing for clients with many millions of files

-For initial backups:

On low capacity grids, use overtime to allow the backup to complete

On higher capacity grids, allow the client to time out daily and rely on partial backups

For clients that will not complete within 7 days, start with a small dataset and gradually add more files anddirectories to avoid issues with parials backups expiring before the initial backup completes

-For incremental backups:

Typical backup performance is about 1 million files per hour

Generally the client disk performance is the bottleneck but be sure to confirm the bottleneck before makingany performance tweaks

Explanation/Reference:

Explanation/Reference:

Explanation/Reference:

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

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

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 andtotal licensed capacity is 31.2 TB

Explanation/Reference:

You must use the backup agents to backup Exchange and SQL. Databases on Image level backups will not beconsistent.

To backup the environments, you would need to do a guest level backup. i.e. Install the avamar agent, and theexchange VSS plugin on the Exchange server, and the SQL plugin on the sql server.

If you want to backup the OS, ensure you create windows datasets to skip the database files on the server,otherwise you'll be backing up database files that look totally different each time (consuming huge amounts ofspace on the grid), that will be no good to you (they'll be inconsistent)!

Besides the above points, the Exchange VSS plugin has some fairly useful functionality, like being able tobackup databases in parrallel, and being able to do granular level restores (i'm still trying to get this to work).

Well worth using.

https://community.emc.com/thread/126801

Explanation/Reference:

AVE 7

AVE 6