In Dell RecoverPoint, a Bookmark is a user-created point-in-time image that can be tied to specific application events. This feature allows users to mark a particular point in time within the continuous data protection timeline of RecoverPoint, which can be used for recovery purposes. Here’s how it works:

User Command : A user issues a command to create a Bookmark, typically through the RecoverPoint management interface or via scripting.

Tied to Application Events : The Bookmark can be associated with specific application events, such as before and after a significant update or batch process.

Point-in-Time Image : The Bookmark represents a point-in-time image of the data at the moment the Bookmark was created.

Recovery : In the event of data corruption or loss, the Bookmark can be used to recover data to the exact state it was in at the time of the Bookmark.

Bookmarks are an integral part of RecoverPoint’s data protection capabilities, providing flexibility and precision for data recovery operations 1 .

When a Consistency Group failover is performed to a remote copy in a Dell RecoverPoint system, the point-in-time images stored in the copy Journal are deleted after the copy becomes the new production. This is because the copy Journal’s role is to maintain a record of changes for recovery purposes, and once the copy is promoted to production, its Journal is reset to start recording new changes from that point forward 1 .

The process involves the following steps:

Failover Initiated : The administrator initiates a failover to the remote copy.

Copy Becomes Production : The remote copy is promoted to the production role.

Journal Reset : The point-in-time images in the copy Journal are deleted as part of the promotion process.

New Production Journal : A new production Journal is started to record changes from the new production copy moving forward.

This ensures that the RecoverPoint system can continue to protect the data with a fresh start for the new production environment 1 .

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 sites 1 .

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 protection 1 .

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 Group 1 .

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 directly 2 .

RecoverPoint and VMAX Connectivity :

A physical RecoverPoint cluster connected to a VMAX array uses Fibre Channel connections for communication. Each RPA typically has two Fibre Channel ports.

WWPN (World Wide Port Name) :

WWPNs are unique identifiers assigned to each port in a Fibre Channel network, including both RecoverPoint and VMAX ports.

Minimum Number of WWPNs :

For a single RecoverPoint appliance (RPA), the minimum number of ports includes:

2 RecoverPoint Ports (RP Ports) : Each RPA usually has at least two Fibre Channel ports for redundancy.

1 Front-End Adapter (FA) Port : The VMAX array has at least one FA port connected to the RecoverPoint system.

Diagnostic Tests :

When running SAN diagnostics from the boxmgmt menu, the test will show the WWPNs of all connected ports, including both the RPA ports and the VMAX FA ports.

The priority level of a Consistency Group in Dell RecoverPoint is used to manage bandwidth allocation among multiple CGs that share the same primary RecoverPoint Appliance (RPA). Here’s how it works:

Priority Level Setting : The priority level is set within the CG’s settings, indicating its importance relative to other CGs.

Bandwidth Allocation : The higher the priority level, the more bandwidth is allocated to that CG when bandwidth is limited.

Resource Management : This setting helps ensure that critical CGs receive the necessary resources for replication, especially during peak times or when system resources are constrained.

Replication Efficiency : By managing bandwidth allocation through priority levels, RecoverPoint can maintain efficient replication and meet Recovery Point Objectives (RPOs) for all CGs 1 .

This feature is particularly important in environments with multiple CGs and limited bandwidth, as it allows administrators to ensure that the most critical data is replicated first 1 .

The “Detect Bottlenecks” tool in Unisphere for RecoverPoint is designed to analyze the performance of Consistency Groups and identify any potential bottlenecks that may be affecting replication efficiency. If the tool detects issues that require user action, it will provide recommendations on how to address them. The steps involved in using this tool are:

Access Unisphere for RecoverPoint : Log into the Unisphere interface.

Navigate to System Analysis Tools : Locate the section for system analysis tools.

Select ‘Detect Bottlenecks’ : Choose this option to start the analysis.

Review Results : Examine the output for any identified bottlenecks and follow the recommendations provided to resolve any issues and optimize replication performance 1 .

This tool is an essential part of the RecoverPoint system analysis suite, helping administrators maintain efficient replication and ensure data protection 1 .

To identify whether physical or virtual RPAs are in use on a specific cluster using Unisphere for RecoverPoint, follow these steps:

Navigate to RPA Clusters : In Unisphere, locate and click on the ‘RPA clusters’ section.

Select Cluster Name : Find and select the specific cluster you want to investigate.

View RPA Details : Click on the ‘RPAs’ option to view detailed information about the RPAs associated with the selected cluster.

This process will provide you with the necessary information to determine the type of RPAs (physical or virtual) that are being used within the specified cluster 1 .