In Dell RecoverPoint, a Consistency Group is built from one or more replication sets. Each replication set consists of a production volume plus any local or remote copy volumes to which it is replicating1. Since the mission-critical application is stored on three volumes, and each volume will be part of a replication set, the Consistency Group for the application will contain three replication sets. This ensures that all three volumes are protected and replicated as part of the RecoverPoint protection strategy1.

It's important to note that the number of replication sets in a Consistency Group is equal to the number of production volumes being replicated. Therefore, if an application spans multiple volumes, each volume will be part of its own replication set within the Consistency Group1.

When using the MetroPoint feature of RecoverPoint to protect distributed VPLEX volumes, it is essential that both VPLEX clusters have a connected RecoverPoint cluster. This is necessary to create a MetroPoint Consistency Group, which is a configuration that allows for continuous data protection and availability across multiple sites1.

The MetroPoint solution provides a three-site configuration that combines VPLEX Metro (which operates within distances of 5-10ms round-trip time, application dependent) with a third site provided by a RecoverPoint appliance. This setup ensures that data is continuously available and protected, and it allows for failover between two Metro sites without impacting protection1.

It's important to note that while MetroPoint enables protection for VPLEX devices at both sites, the requirement for both VPLEX clusters to be connected to a RecoverPoint cluster is crucial for the creation and proper functioning of a MetroPoint Consistency Group1.

For the most accurate and up-to-date information, it is always best to consult the latest official Dell RecoverPoint documentation or contact Dell EMC support directly2.

When setting up replication for a Consistency Group between clusters using XtremIO storage arrays at each site connected through Fibre Channel, the maximum throughput that can be expected per RecoverPoint Appliance (RPA) is 300 MB/s. This throughput is a measure of how much data can be transferred from one site to another per second by each RPA involved in the replication process.

The throughput capacity is important for planning and ensuring that the RecoverPoint system can handle the expected data load during replication activities. It affects the Recovery Point Objective (RPO) and the overall efficiency of the disaster recovery setup. The 300 MB/s figure provides a benchmark for administrators to gauge the performance capabilities of their RecoverPoint system when used in conjunction with XtremIO storage arrays1.

It's important to note that actual throughput can vary based on several factors, including network conditions, the amount of data being replicated, and the specific configuration of the RecoverPoint and XtremIO systems1.

Calculate Daily Changes: With 100 GB of cumulative changes per day, the total amount of changes over two days would be 200 GB.

Determine Journal Size: The Journal size must be large enough to store all the changes for the required rollback periD. Therefore, a Journal size of 200 GB is necessary.

Set Protection Window: The ''Required Protection Window'' should be set for 2 days to match the rollback requirement.

Configure Copy Policy: The copy policy should be configured to ensure that the Journal maintains the point-in-time images for at least 48 hours.

By following these steps, the company can ensure maximum protection with the least amount of storage used, while also meeting their rollback requirements1234.

When creating a Consistency Group using Unisphere on RecoverPoint/EX, the wizard displays volumes for selection as copy volumes based on specific criteria. The volumes displayed must be masked to the selected cluster and must be the same size or larger than the production volume. This ensures that the copy volume has sufficient capacity to hold all the data from the production volume and any additional data that may be replicated in the future.

The process for selecting the copy volume involves:

Identifying all volumes visible to the selected cluster.

Filtering out volumes that are smaller than the production volume to prevent potential space issues.

Presenting the remaining volumes as options for the administrator to choose as the copy volume.

This approach prevents the accidental selection of a volume that is too small to serve as a copy volume, which could lead to replication issues or data loss. It also allows for flexibility in choosing a larger volume if desired, which can be beneficial in scenarios where future growth is anticipated1.