Pass the EMC Data Protection D-AV-DY-23 Questions and answers with CertsForce

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:

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:

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:

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.

Explanation/Reference:

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

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