D-AV-DY-23 Exam Dumps - EMC Data Protection Questions and Answers

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

Explanation/Reference:

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

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

Explanation/Reference:

For initial backup of Avamar clients, it's best to start with a small number of clients to produce a dataset from which commonality will be generated. This will increase the backup speed of following clients. On a new Avamar system, consider enabling overtime because all the data is new and there won't be much maintenance to take place. Never enable overtime on an existing Avamar, rather configure the use of partial backups to be saved. Partial backups are saved for 7 days and are not deleted by the garbage collection process. When an unfinished job ends before completing and partial backups are enabled, the backup job will continue from the last known state and will complete faster.

http://gregandthenetwork.blogspot.com/2013/12/avamar-configuration-design-best.html

https://communities.vmware.com/message/2166196

Explanation/Reference:

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

Explanation/Reference:

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

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