Repository Volume: This is a special volume used by RecoverPoint for storing metadata about the system's configuration and the data it protects. It is essential for the operation of RecoverPoint and must be present on any array that is part of a RecoverPoint/EX cluster1.

Journal Volume: The journal volume is used to store changes to protected data. It allows RecoverPoint to recover data to any point in time within the journal window. Like the repository volume, it is a required component of a RecoverPoint/EX cluster1.

When adding volumes from an unlicensed array to a RecoverPoint/EX cluster, both repository and journal volumes are supported and required for the cluster's operation. The administrator must ensure that these volumes are properly configured to meet the system's requirements1.

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.

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.

MetroPoint Consistency Group is designed to contain both active and standby production copies.

It integrates VPLEX Metro with RecoverPoint, providing a 3-site solution that allows for continuous availability and operational recovery1.

A single Consistency Group is configured which contains the two Production copies (active and standby) and a Replica Copy1.

This setup ensures that both VPLEX clusters' data are protected and continuously available, with the ability to failover between two Metro sites without impacting protection1.

For more detailed information, you can refer to Dell's official documentation on MetroPoint, which explains the functionalities and configurations of MetroPoint Consistency Groups12.

Proper communication between Deployment Manager and the RecoverPoint Appliances requires the following ports: TCP 21, 22, 25, 80, and 7225. These ports facilitate the necessary management and data transfer operations essential for the deployment and configuration of RecoverPoint systems.

Dell RecoverPoint for Virtual Machines 6.0.1 vSphere HTML5 Plugin Administrator's Guide, section on network requirements and port configurations.