DELL D-RP-DY-A-24 Practice Test - Questions Answers

When determining the Journal volume size, the factors that must be considered are:

B . Rate of change, application data type to be replicated, and the number of snapshots to retain

Explanation: To determine the appropriate size for the Journal volume in a RecoverPoint system, several key factors need to be taken into account. These include the rate of change of the data being replicated, the type of application data (as different data types can have different change rates), and the number of snapshots to retain for recovery purposes. These factors collectively help in estimating the amount of space required for efficient journaling and replication.

Reference: Dell RecoverPoint for Virtual Machines 6.0.1 vSphere HTML5 Plugin Administrator's Guide, Chapter on Journal Sizing and Management.

Select the Correct Installer: In the RecoverPoint Deployment Manager wizard, select the ''RecoverPoint with VNX Installer'' option. This installer is specifically designed for environments using VNX storage systems.

Cluster Configuration: Configure the clusters at both the production and disaster recovery sites to be managed as a single RecoverPoint system.

Complete the Installation: Follow the remaining steps in the Deployment Manager wizard to complete the installation and ensure that all four VNXs are integrated into the RecoverPoint system.

For detailed installation instructions and to ensure that the clusters are managed as one system, refer to the Dell RecoverPoint for Virtual Machines Installation and Deployment Guide1. This document provides comprehensive guidance on installing and configuring a Dell RecoverPoint system, including scenarios with multiple clusters and VNX arrays.

To calculate the minimum required size for the Journal volume, we can use the provided formula and input the given parameters:

Average Write Traffic: 5 Mb/s

Required Rollback Time: 24 hours (which is 24 * 60 * 60 = 86,400 seconds)

Default Parameters: Assuming the image access log percentage is 20% (which is a common default), and the reserved for marking is negligible.

Using the formula:

\text{Journal size} = 1.05 \times (\text{write traffic}) \times (\text{rollback time in seconds}) / (1 - \text{image access log percentage})Journalsize=1.05(writetraffic)(rollbacktimeinseconds)/(1imageaccesslogpercentage)

We plug in the values:

\text{Journal size} = 1.05 \times (5 \text{ Mb/s}) \times (86,400 \text{ seconds}) / (1 - 0.2)Journalsize=1.05(5Mb/s)(86,400seconds)/(10.2)

Converting Mb to GB (1 Mb = 1/8,000 GB):

\text{Journal size} = 1.05 \times (5/8,000 \text{ GB/s}) \times 86,400 / 0.8Journalsize=1.05(5/8,000GB/s)86,400/0.8

\text{Journal size} = 1.05 \times 0.000625 \text{ GB/s} \times 86,400 / 0.8Journalsize=1.050.000625GB/s86,400/0.8

\text{Journal size} = 1.05 \times 54 \text{ GB} / 0.8Journalsize=1.0554GB/0.8

\text{Journal size} = 70.875 \text{ GB}Journalsize=70.875GB

Since we need to round up to ensure we have enough space, the minimum required size for the Journal volume is approximately 72.4 GB.

This calculation ensures that the Journal volume is adequately sized to handle the write traffic and maintain the required rollback time, providing a buffer for the image access log1.

Physical Connection: The RPAs should be physically connected to each other using their iSCSI ports. This is because the host systems are configured with iSCSI HBAs, which indicates that the storage network is based on iSCSI protocol1.

Configuration in RecoverPoint: In the RecoverPoint Deployment Manager, ensure that the iSCSI ports of the RPAs are correctly configured to communicate with the VNX array.

Verification: After the physical connections and configurations are made, verify that the RPAs can communicate with the VNX array and that the iSCSI connections are stable and operational.

It is important to note that while the RPAs are connected through their iSCSI ports, they should not be connected to any MirrorView ports on the VNX array. Additionally, ensure that the RPAs are connected directly to the FC ports on the Storage Processors (SPs) and not to an expansion SFP on the file side1.

Access the CLI: Log into the RecoverPoint Command Line Interface (CLI) using appropriate credentials.

Run the Command: Execute the export_statistics command to gather performance data.

Save the Data: The command will output the performance data, which can then be saved to a spreadsheet.

Review and Graph: Use the spreadsheet to review the performance data and create graphs to visualize system performance over the specified time period.

The export_statistics command is used to export performance data from RecoverPoint, which can then be analyzed and graphed for a better understanding of system performance and to identify any potential issues1.

Deployment Manager Overview: The Deployment Manager is a tool used to install and configure RecoverPoint clusters. It guides users through various steps to ensure the proper setup and configuration of the system.

Prepare New Cluster for Connection: During this step, the Deployment Manager prepares the new cluster for connection to the existing infrastructure. This involves several sub-steps, including network configuration, validation of the environment, and ensuring that all necessary components are in place.

Adding Licenses: As part of the ''Prepare New Cluster for Connection'' step, new RecoverPoint licenses are added to the cluster. This is crucial because the licenses enable the functionality of the RecoverPoint system, allowing it to perform replication and recovery tasks.

Verification: After adding the licenses, the Deployment Manager verifies that the licenses are correctly applied and that the cluster is ready for the next steps in the deployment process.

Understanding Group Sets: Group Sets in Dell RecoverPoint allow administrators to create a consistent point-in-time image across multiple Consistency Groups. This is particularly useful in environments where data consistency across different applications or databases is critical.

Functionality: When using Group Sets, a single bookmark can be applied to multiple Consistency Groups simultaneously. This ensures that all the groups are synchronized to the same point in time, providing a consistent recovery point across different data sets.

Implementation:

Step 1: Access the RecoverPoint Management Application.

Step 2: Navigate to the Group Sets section.

Step 3: Create a new Group Set and select the Consistency Groups that need to be included.

Step 4: Apply a bookmark to the Group Set. This action will create a consistent point-in-time image across all selected Consistency Groups.

Verification: After setting up the Group Set and applying the bookmark, verify that the point-in-time image is consistent across all included Consistency Groups. This can be done by checking the bookmarks and ensuring they are synchronized.

Accessing the RPA: To retrieve the WWNs / PWWNs, you need to log into each RecoverPoint Appliance (RPA) individually.

Step 1: Use an SSH client to connect to the RPA.

Step 2: Log in with the boxmgmt user credentials.

Navigating to SAN Diagnostics: Once logged in, navigate to the SAN Diagnostics menu.

Step 3: From the main menu, select the option for SAN Diagnostics. This menu provides various diagnostic tools and information related to the SAN environment.

Retrieving WWNs / PWWNs: Within the SAN Diagnostics menu, you can retrieve the WWNs / PWWNs.

Step 4: Select the option to display the initiators. This will list the WWNs / PWWNs associated with the RPA.

Verification: Ensure that the retrieved WWNs / PWWNs are correct and correspond to the intended RPAs. This information is crucial for configuring zoning on the Brocade switch.

After completing the zoning between the RPAs and the VNX ports and ensuring the RPA ports are available in the connectivity status on the VNX, the next step is to create a storage group on the VNX for RecoverPoint. This step is crucial to logically group the LUNs that will be managed and replicated by the RecoverPoint system.

Dell RecoverPoint for Virtual Machines 6.0.1 vSphere HTML5 Plugin Administrator's Guide, Chapter on implementing RecoverPoint/EX clusters using VNX splitters.