Free EMC E20-598 Practice Exam with Questions & Answers

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:

During the backup window, an Avamar server has 18 backup "slots" per node, minus one slot that is globallyreserved for restore.

Explanation/Reference:

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

Situationin Avamar 7#

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:

Explanation/Reference:

Assume the file HAS been changed, and therefore the hash of the file no longer matches the hash in the filecache. From here, the data will be broken into variable segment lengths through Avamar’s patented sticky bytefactoring process. These segments are then compressed andhashed, and the resulting hash is written to aHASH CACHE file locally on the client. This file is also loaded into RAM when a backup is initiated.

http://www.egroup-us.com/2011/09/emc-avamar-how-source-global-dedupe-magic-happens/

Avamar, 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.

http://storagezilla.typepad.com/storagezilla/2007/09/the-future-is-v.html

Explanation/Reference:

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