D-RP-DY-A-24 Practice Questions

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})Journal​size=1.05×(write​traffic)×(rollback​time​in​seconds)/(1−image​access​log​percent

age)

We plug in the values:

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

0.2)Journal​size=1.05×(5​Mb/s)×(86,400​seconds)/(1−0.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.8Journal​size=1.05×(5/8,000​GB/s)×86,400/0.8

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

0.8Journal​size=1.05×0.000625​GB/s×86,400/0.8

\text{Journal size} = 1.05 \times 54 \text{ GB} / 0.8Journal​size=1.05×54​GB/0.8

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

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.

The System Modification wizard is part of the RecoverPoint Deployment Manager, which is used for

various important RecoverPoint operations1.

The wizard allows you to modify several environment settings of a RecoverPoint Appliance (RPA)

cluster2.

Among the settings that can be changed are:

Cluster name: This is the name assigned to the RecoverPoint cluster.

Time Zone: The local time zone for the RPA.

DNS server: The Domain Name System servers that the RPA will use for resolving hostnames.

These settings are essential for the proper functioning and integration of the RPA within the network

and with other systems like VNX, VMAX, or VPLEX2.

For the most accurate and detailed instructions, always refer to the latest official documentation or

contact Dell EMC support directly. The information provided here is based on general knowledge of

RecoverPoint systems and may not reflect the most recent updates or specific configurations.

Configure the zone including Unity ports and RP ports.

Perform the Unity cluster conversion (SE to EX).

Update the licenses to EX.

Confirm whether the RP cluster is added to Unity1.

The Conversion wizard will convert both clusters on the RP system. Note that the conversion will

convert the RP/SE system with the VNX arrays to a full RP system. RP/EX applies to licensing only.

There are no additional configurations changes required on the VNX arrays1.

For more detailed steps and scenarios, you may refer to the “Using RP for Mid-Range Array Refresh”

document available on Dell EMC Online Support, which is laid out in several scenarios1.

The correct sequence of steps for Snap-based replication on XtremIO is:

Create the snapshot

Get the DIFF between the snapshot and the root volume

Create a second snap, and then retrieve the DIFF between the first and second snapshot

Transfer the DIFF

Create and promote the snapshot

Snap-based replication on XtremIO involves the following steps:

Create the snapshot: This step involves taking a snapshot of the source volume that will be used as

the baseline for replication.

Get the DIFF between the snapshot and the root volume: Here, the differences between the

snapshot and the root volume are calculated. This is necessary to understand what changes have

been made since the last snapshot.

Create a second snap, and then retrieve the DIFF between the first and second snapshot: A second

snapshot is created to capture the latest state of the volume. The differences (DIFF) between the first

snapshot and the second snapshot are then calculated.

Transfer the DIFF: The differences identified between the snapshots are transferred to the target

volume. This ensures that only the changes are replicated, optimizing the replication process.

Create and promote the snapshot: Finally, the snapshot is created and promoted to ensure the target

volume is updated with the latest changes.

This sequence ensures efficient and accurate replication by focusing on the changes between

snapshots, rather than replicating the entire volume each time.

Reference:

Dell RecoverPoint for Virtual Machines 6.0.1 vSphere HTML5 Plugin Administrator's Guide, Chapter

on Snap-based replication steps

Install the new RecoverPoint/EX cluster: Begin by deploying the new RecoverPoint/EX cluster at the

new data center. This involves setting up the physical or virtual appliances that will form the new

cluster.

Add the license to the new cluster: Once the new cluster is installed, the next step is to add the

appropriate licenses. This is crucial as it enables the new cluster’s functionality within the

RecoverPoint environment.

Connect the new cluster to the existing system: After the licensing is in place, the new cluster needs

to be connected to the existing RecoverPoint system. This includes configuring the communication

between the new and existing clusters to ensure proper replication and synchronization.

For detailed guidance on these steps, the RecoverPoint Deployment Manager can be used. It

provides a suite of wizards that assist with various operations, including modifying cluster settings

and adding new clusters to an existing system1. Always ensure to use the latest version of the

Deployment Manager and follow the instructions provided within the tool for a non-disruptive

setup1.

It is also recommended to consult the Dell RecoverPoint for Virtual Machines Installation and

Deployment Guide for comprehensive instructions and best practices2. Additionally, for automation

and scripting of deployment tasks, including adding new clusters, refer to the documentation on

RecoverPoint for VMs Deployment Automation3.

=========================

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.

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.

Reference:

Dell RecoverPoint for Virtual Machines 6.0.1 vSphere HTML5 Plugin Administrator's Guide, Chapter

on implementing RecoverPoint/EX clusters using VNX splitters.

In the write phase of RecoverPoint replication, the write splitter intercepts write data from the

production host and sends it to the RecoverPoint Appliance (RPA).

The RPA then immediately acknowledges receipt of the write data to the write splitter1.

This acknowledgement occurs as soon as the RPA receives the write, which is before the distribution

phase or any acknowledgements from other copies involved in the replication process1.

The prompt acknowledgement allows the write splitter to continue processing other writes, ensuring

efficient replication and system performance1.

For detailed information on the write phase and the role of the RPA and write splitter in

RecoverPoint replication, it is advisable to consult the official Dell RecoverPoint documentation or

contact Dell EMC support.

Failover Execution: When a Consistency Group failover is performed to a remote copy, the remote

copy becomes the new production copy.

Journal Content Handling: The point-in-time images that were stored in the copy Journal, which was

associated with the remote copy, are deleted as part of the failover process1.

Post-Failover State: After the failover, the system will start fresh journaling for the new production

copy, and the previous point-in-time images are no longer required1.

This process ensures that the Journal is used efficiently and only contains relevant point-in-time

images for the current production copy1.

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.

Reference: This process is verified based on the official Dell RecoverPoint documentation, which

outlines the steps for accessing and retrieving WWNs / PWWNs from the RPAs12.