RecoverPoint-Deploying-with-VPLEX-Technical-Notes

These technical notes provide information, required procedures, and best practices that are specific to replicating VPLEX virtual volumes with RecoverPoint. For information about VPLEX, refer to the VPLEX documentation. For information about RecoverPoint refer to the RecoverPoint documentation. Topics include:

◆ Revision History ................................................................................... 2◆ VPLEX and RecoverPoint.................................................................... 3◆ Solution design ..................................................................................... 5◆ VPLEX / RecoverPoint installation and integration....................... 8◆ Updating.............................................................................................. 15◆ Disaster recovery ................................................................................ 16◆ Troubleshooting .................................................................................. 23

EMC® RecoverPointDeploying with VPLEX™

Technical NotesP/N 300-013-380

Rev 02

September 10, 2012

1

2

Revision History

Revision HistoryTable 1 on page 2 shows the revision history for this document.

Table 1 Revision history

Revision Date Description

02 September 2012 • Added replica-site disaster scenarios• Added certificate updates in Updating section

A 01 May 2012 • First publication.

RecoverPoint Deploying with VPLEX Technical Notes

VPLEX and RecoverPoint


VPLEX concepts and features

VPLEX provides a single storage virtualization interface for multiple storage arrays, even if the physical storage is located on two different Storage Area Networks and at two different data centers at geographically separated sites.

VPLEX is deployed as clusters of one or more engines. Each engine comprises two I/O directors. Each cluster runs a storage virtualization software environment called GeoSynchrony. Each cluster has a service management station that provides storage management.

The VPLEX front end appears to hosts like storage controllers (target ports). The VPLEX back end appears to a storage controller like a host (initiator ports).

A VPLEX cluster can contain from 1 to 4 engines. In case of hardware or path failure, any remaining director can access data and service I/Os without any disruption of operations.

VPLEX Local VPLEX Local provides data mobility, availability, and simplified single site (data center) management of heterogeneous storage arrays from a single interface.

VPLEX Metro VPLEX Metro provides active-active access to data at two sites that are within synchronous replication distance (less than 5 ms round-trip time is recommended) of each other. The same set of devices is exposed at both sites. I/Os can be performed locally at either site, and VPLEX storage management assures coherency and protection from simultaneous access. Virtual servers and storage can be moved transparently between the sites.

VPLEX Geo VPLEX Geo provides data access and mobility between two sites that are asynchronous replication distance of each other.

VPLEX configurationssupported byRecoverPoint

RecoverPoint supports only VPLEX Local and VPLEX Metro configurations. RecoverPoint can replicate the virtual volumes in VPLEX Metro consistency groups if and only if they are local to the site where RecoverPoint is attached; or distributed virtual volumes with a local extent.

The current versions of VPLEX and RecoverPoint do not support RecoverPoint replication for VPLEX Geo clusters.

3RecoverPoint Deploying with VPLEX Technical Notes

4


Data migration VPLEX can non-disruptively move data between heterogeneous storage devices or extents (units of physical storage that constitute a device).

Data mirroring VPLEX supports volume mirroring, providing the ability to make two copies on two different storage arrays in two locations.

VPLEX Metro provides distributed RAID 1 devices. VPLEX virtual volumes protected by distributed devices comprise two mirror legs (two copies of data) built from physical storage elements residing at two distinct locations. Hosts at one VPLEX cluster are able to have full read/write access to their virtual volumes, even if the other VPLEX cluster is down.

VPLEX cluster witnessand winner-loser

arbitration

If the Metro link between VPLEX sites fails, VPLEX elects a single site for each consistency group to be the winner; this site will continue to receive all host I/Os. VPLEX consistency groups must be attached to the VPLEX splitter at the site specified as the winning site. For this reason, RecoverPoint can only protect a distributed device at one VPLEX Metro site. VPLEX does not allow a virtual volume to be protected by RecoverPoint unless the virtual volume is in a VPLEX consistency group that is RecoverPoint enabled and set to prefer the site with RecoverPoint attached.

If the preferred site (site with the VPLEX splitter) fails, VPLEX Witness can override the site preference rule (override the pre-defined winner). At that point, host I/Os will continue at the losing site, but new writes will not be protected by RecoverPoint until the failed site comes back online and is updated. RecoverPoint access to the volumes will be disabled until the failed site is repaired and updated. For more information, refer to “Disaster recovery” on page 16.

Related documents EMC VPLEX Product Guide

EMC VPLEX Configuration Guide

EMC VPLEX Administration Guide

EMC RecoverPoint Administrator's Guide

EMC RecoverPoint Glossary

EMC RecoverPoint Deployment Manager Product Guide


Solution design

Solution designThe following configurations are currently supported when deploying VPLEX with RecoverPoint:

Supported topologies

VPLEX Local VPLEX Local virtual volumes can be replicated locally (CDP), remotely (CRR), or both (CLR).

VPLEX Metro VPLEX Metro virtual volumes can be replicated locally (CDP), remotely (CRR), or both (CLR). All RPAs (in all RPA clusters) must be connected to a single VPLEX cluster in the Metro system.

In VPLEX Metro systems, RecoverPoint can replicate only one VPLEX cluster. Replication at both VPLEX clusters is not supported.

RecoverPoint can only protect distributed VPLEX devices from one site of a VPLEX Metro, the site where RecoverPoint is attached (via Fibre Channel). Each VPLEX consistency group that is protected by

Table 2 VPLEX/RecoverPoint solutions

Type Description

VPLEX LocalRecoverPoint CDP

RecoverPoint provides point-in-time protection at a single site.

VPLEX LocalRecoverPoint CRR

RecoverPoint provides remote replication and point-in-time recovery.

VPLEX LocalRecoverPoint CLR

RecoverPoint provides replication to one remote site and point-in-time recovery from the local site.

VPLEX MetroRecoverPoint CDP

Metro active-active copies provide disaster avoidance. RecoverPoint local copy provides point-in-time recovery.

VPLEX MetroRecoverPoint CRR

Metro active-active copies provide disaster avoidance. RecoverPoint provides remote copy and point-in-time recovery.

VPLEX MetroRecoverPoint CLR

Metro active-active copies provide disaster avoidance. RecoverPoint provides local copy, remote copy, and point-in-time recovery.


6

Solution design

RecoverPoint must have its site preference (winning site) set to the site where the write splitting is taking place.

There are several ways to implement VPLEX Metro with RecoverPoint:

◆ A standard VPLEX Metro implementation: production site on VPLEX A, mirror on VPLEX B, and RecoverPoint replica on a different VPLEX or on a non-VPLEX array

◆ Two RecoverPoint replica sites, one local and one remote

◆ RecoverPoint CDP (local) replica on the same VPLEX cluster as production

The following VPLEX volumes may be replicated by RecoverPoint:

◆ local volumes.

◆ distributed volumes. Splitting and replicating is only allowed on one site of the distributed volumes, the site with Fibre Channel connections to the RecoverPoint cluster.

The RecoverPoint repository and journals must be local to the VPLEX site protected by RecoverPoint, and not distributed. If necessary, the RecoverPoint repository and journals may be on the physical array, without VPLEX virtualization, or on a different array. The best practice is to have the RecoverPoint repository, journals, and replication volumes on the VPLEX.

Cabling ◆ As for any other array-based splitter, every RecoverPoint appliance needs to be cabled to two fabrics. Single-fabric configurations are not supported.

◆ Each RecoverPoint appliance should have at least two physical connections to the front-end fabric switch.

◆ The best practice is that each VPLEX director should have at least one front-end connection to each fabric.

◆ The best practice is that each VPLEX director have at least one physical connection to each of the back-end fabric switches.

Zoning For effective use of RecoverPoint, particularly in scaled environments, zoning must adhere to the guidelines in this document.

EMC supports port WWN zoning only. To display the port WWNs of RecoverPoint Fibre Channel ports, in the RecoverPoint Navigation


Solution design

pane, click RPAs. In the Component pane, double-click on the RPA name.

You can also use the RecoverPoint Installation Manager (log in to the RecoverPoint appliance as boxmgmt) and select Diagnostics > Fibre Channel diagnostics > View Fibre Channel details to list the pWWNs of each RecoverPoint appliance.

RecoverPoint WWNs can be recognized by their 5001248 prefix.

RPA Fibre Channelports as both initiators

and targets

VPLEX supports only RecoverPoint Gen4 and later RPAs. It is therefore not necessary to separate RPA Fibre Channel ports into initiator and target zones.

The best practice is to use the RPA Fibre Channel ports as both initiators and targets. In this configuration, maximum performance and redundancy, and optimal use of resources are achieved. If, because of Initiator-Target LUN (ITL) limitations or other non-RecoverPoint considerations, you need to zone RPA Fibre Channel ports in either the initiator zone or the target zone, but not both, there will be only minor differences in performance and availability. However, initiator-target separation is not supported at all in the following cases:

◆ when mixing different splitter types at the same site

◆ when using remote replication over Fibre Channel

◆ when using distributed consistency groups

Limitations ◆ When the VPLEX splitter is uncontrollable (that is, it is not Fibre-dead, but RecoverPoint cannot communicate with it), RecoverPoint replication is not available.

◆ VPLEX Metro remote exported volumes cannot be replicated by RecoverPoint.

◆ RecoverPoint cannot replicate writes if the Metro link is down and RecoverPoint is on the losing site. This should not occur, but if it does, replication is disabled until VPLEX splitter notifies that the protected volume has been fully recovered.

◆ The RecoverPoint repository and journal volumes must be a VPLEX Local volume (not distributed). If necessary, the repository or journals may be presented directly to RecoverPoint from the physical array, without VPLEX virtualization. If there is


8

VPLEX / RecoverPoint installation and integration

a compelling need, the repository may be on a different array. The best practice is to use virtualized VPLEX volumes for the repository and journals.

◆ RecoverPoint cannot enforce the selection of a supported repository volume type because the repository must be selected before RecoverPoint system is running and able to retrieve volume information from VPLEX. The user is therefore responsible to select a supported repository volume.

◆ The following features are not available for VPLEX volumes protected by RecoverPoint:

• VPLEX virtual volume expansion

• RecoverPoint virtual image access (use logged access instead)

• Device migrations between two VPLEX clusters are not supported if one leg of the device is replicated by RecoverPoint

◆ A VPLEX cluster supports up to 2048 splitter sessions. One splitter session is required for each LUN that is used either as production or as a replica. As a result, if production and a replica reside on the same VPLEX cluster (CDP), one session is required for the production LUN and another for the local replica LUN. If the VPLEX splitter is shared among multiple RecoverPoint clusters, the sessions of each cluster is counted towards the maximum number of splitter sessions per VPLEX cluster.

◆ VPLEX supports a maximum of 8000 distributed devices (total number of distributed virtual devices) plus top-level—not child of another device—local devices with global visibility.

◆ VPLEX supports a maximum of 8000 local devices with global visibility.

◆ When more than one VPLEX system are connected to the same RP installation (for instance production, CDP, and CRR), only one VPLEX system can be upgraded at a time. Upgrade to a second VPLEX system will fail until upgrade to the first VPLEX system has been completed.


Prerequisites ◆ VPLEX 5.1.0 or later



◆ RecoverPoint 3.5 or later

◆ All RecoverPoint appliances must be Gen4 or later.

◆ For RecoverPoint management information to be available at both sites of a VPLEX Metro installation, the following are required:

• IP connectivity between the Metro sites

• RecoverPoint site added to the VPLEX CLI at the non-RecoverPoint site of the VPLEX Metro.

In some situations, it may not be possible to add the RecoverPoint site to the VPLEX CLI at the non-RecoverPoint site due to limitations on network connections.

VPLEX installation 1. Use EZ Setup as for any other VPLEX installation. For instructions, refer to the EMC VPLEX Configuration Guide. VPLEX 5.1 and later supports RecoverPoint and contains a built-in RecoverPoint write splitter.

VPLEX-to-storage zoning

2. Zone physical arrays to the VPLEX back-end.

• Each director must have redundant I/O paths to every back-end storage array.

• Each storage array must have redundant controllers; the best practice is that at least two ports of each controller be connected to the back-end fabric.

• Each VPLEX director supports a maximum of 4 paths per storage volume.

RPA-to-VPLEX front-end zoning

• In each fabric, create one zone that includes all RecoverPoint Fibre Channel ports and all VPLEX front-end ports involved in RecoverPoint replication. Both VPLEX and RecoverPoint must have at least one Fibre Channel port per fabric for each VPLEX director.

Registering RecoverPoint

Register RecoverPoint Fibre Channel initiator ports with VPLEX:

3. Log in to the VPLEX GUI (https://<ManagementServerIP>).

4. Select Provision Storage > <cluster name> > Initiators. The Initiator Properties dialog box appears.


10


5. In the Initiator Name field, select an unregistered RecoverPoint initiator. The port WWN will be preceded by the prefix UNREGISTERED (Example: UNREGISTERED-0x5001248061931a3b). Click Register (at the bottom of the display). You may assign a significant name to the port. Set Host Type = recoverpoint. Repeat until all RecoverPoint unregistered ports are registered.

Creating RecoverPoint repository

6. Create a VPLEX local (not distributed) virtual volume for the RecoverPoint repository. Make sure the RecoverPoint repository is at least 3 GB.

Creating RecoverPoint storage view

7. In the VPLEX GUI, create a storage view for the RecoverPoint cluster:

a. From the drop-down menu in the VPLEX GUI, select Provision Storage > <cluster name> > Storage Views > Create Storage View.

b. Use the Create Storage View wizard to create the VPLEX Storage View that will be used for the RecoverPoint RPAs. Name it RecoverPoint System or other appropriate name to indicate that it contains RecoverPoint volumes.

c. Add to the RecoverPoint System storage view:

– All RecoverPoint initiators– All VPLEX front-end ports used by the RecoverPoint

cluster– VPLEX Virtual Volumes to be used for the RecoverPoint

repository, journal volumes, and replication volumes.– Make sure that repository is exposed only to RecoverPoint,

and not to any host server.d. The following volumes may not be added to the RecoverPoint

storage view:

– Remote volumes– Volumes that are already in a different RecoverPoint

storage view– Volumes in VPLEX consistency groups whose members are

in a different RecoverPoint storage view



A RecoverPoint cluster may take up to 2 minutes to register changes to VPLEX consistency groups. Wait 2 minutes after making the following changes before creating or changing a RecoverPoint consistency group:

• Adding virtual volumes to or removing them from a VPLEX consistency group

• Enabling or disabling the recoverpoint-enabled property of a VPLEX consistency group

• Changing the detach rule of a VPLEX consistency group

Installing RecoverPoint

8. Use RecoverPoint Installer wizard to install RecoverPoint. Continue up to and including zoning (Wizard step 7.1.1). For detailed instructions, refer to EMC RecoverPoint Deployment Manager Product Guide 1.1.

For the repository, use the VPLEX volume previously created.

Site names whenusing more than oneRecoverPoint cluster

RecoverPoint clusters sharing a VPLEX splitter must use different names for the site.

For example:

• Cluster #1 is replicating between Beijing and Bangalore.

• Cluster #2 is replicating between Beijing and Frankfurt.

Both clusters use the same VPLEX splitter in Beijing. The two clusters must refer to the Beijing site by different names, such as Beijing1 and Beijing2. In addition, the same LUN cannot be replicated both to Bangalore and to Frankfurt.

Activating RecoverPoint license

9. Install RecoverPoint license and activation code. Refer to the EMC RecoverPoint Administrator’s Guide.

Importing RecoverPoint certificate in VPLEX

The best practice is to use certificates to avoid user configuration errors. To do so, the RecoverPoint certificate is imported into VPLEX and the VPLEX certificate is imported in RecoverPoint. Without the certificates, VPLEX and RecoverPoint cannot obtain management information about volume types. With the certificates, VPLEX and RecoverPoint will not display unsupported options in their GUI, so that the user will not select them inadvertently. For instance, distributed volumes will not appear in the RecoverPoint Add Journal


12


Volume dialog box, because distributed volumes are not supported for journals.

10. Import the RecoverPoint certificate to VPLEX. Use the following procedure. If deploying with VPLEX Metro, perform the following procedure at both Metro clusters.

a. Log in to the VPLEX Management Server and open the VPLEX CLI.

b. Import the RecoverPoint certificate:

VPlexcli:/> rp import -certificate

You will be prompted that modifying security settings will cause the VPLEX CLI to restart and will require a new login from all connected GUI and CLI clients.

c. Enter:

..> CONTINUE

d. Enter the RecoverPoint Site Management IPv4 address for the cluster connected to the VPLEX.

e. When prompted if you trust this certificate, enter:

..> y

The VPLEX Management Console closes.

Adding RecoverPoint cluster to VPLEX

11. Add the RecoverPoint cluster to VPLEX. In a Metro configuration, perform this procedure in both clusters:

a. Log in to the VPLEX CLI. Add the RecoverPoint cluster or clusters:

VPlexcli:/> rp rpa-cluster add -o <RP Management Server> -u admin

b. When prompted, RPA cluster administrative password, enter:

..> <password>

c. Verify that the cluster was added and that no errors occurred:

..> ls/recoverpoint/rpa-clusters/<RP Management Server>

d. Validate the VPLEX RecoverPoint configuration:

..> rp validate-configuration



When RPAs are zoned to VPLEX using single-channel mode (2 RPA ports zoned to VPLEX front-end ports, and 2 RPA ports zoned to VPLEX back-end ports), this command issues a warning. The system checks that all 4 ports on the RPA are zoned to both VPLEX front-end and back-end ports (dual-channel mode).

Best practice is to zone every RPA port to both VPLEX front end and back-end ports. Administrators who have purposely configured single-channel mode can safely ignore the warning.

e. In the VPLEX GUI, check the RecoverPoint status:

Creating VPLEX consistency groups

12. Create VPLEX virtual volumes for RecoverPoint replication and journal volumes (journals must be local virtual volumes, minimum size 5 GB). Create VPLEX consistency groups as follows:

a. Consistency groups for replication volumes:

– Local virtual volumes and distributed virtual volumes should be in separate consistency groups.

– If CDP (local replica) volumes reside on the same cluster as production volumes, they must be in a separate VPLEX consistency group from the production volumes.

b. VPLEX consistency group for journals and repository:

– Production and local replica copy journals may be in the same VPLEX consistency group.

– Add the repository to the consistency group for journals.


14


13. For each consistency group created, click on the consistency group name. The Consistency Group Properties dialog appears. Check the recoverpoint-enabled checkbox.

14. Add RecoverPoint replication volumes and journal volumes to the RecoverPoint storage view.

15. To allow host access to RecoverPoint production or replica volumes, add replication volumes to the host’s storage view. Make sure that journal volumes are exposed only to RecoverPoint, and not to any host server.

RPA-to-VPLEX back-end zoning

16. Create a zone for each VPLEX back-end port. Add all RecoverPoint Fibre Channel ports to the zone of each VPLEX back-end port.

A VPLEX back-end port should never be in the same zone with VPLEX front-end ports.

Add the VPLEX splitter

17. At the RecoverPoint Management Application, add the VPLEX splitter using the New Splitter wizard:

a. Click Add Splitter. Select the VPLEX splitter to Add. Press Next.

b. Fill out the Credentials.

Import the VPLEXcertificate

c. Select the method of importing the VPLEX certificate and either click View and approve certificate or click Browse.

Creating RecoverPoint consistency groups

18. Create RecoverPoint consistency groups. The best practice is to have exactly the same replication volumes in the RecoverPoint consistency groups as in the corresponding VPLEX consistency groups. For example:

• VPLEX consistency group contains production volumes A, B, C, and D; when adding A to a RecoverPoint consistency group, the system will propose to add B, C, and D to the same consistency group. The best practice is to accept.

• The VPLEX splitter does not support fake size. In consequence, if a replica volume is attached to the VPLEX splitter, it must be the exact same size as the production volume, regardless to which splitter the production volume is attached.


Updating

The replication volumes will be attached to the VPLEX splitter automatically.

Validating the RecoverPoint alignment in VPLEX

19. In the VPLEX GUI, select Consistency Groups, and click Check RecoverPoint Alignment button near the bottom of the display.

20. Start replication.

For details about RecoverPoint replication, refer to the RecoverPoint Administrator’s Guide.

Virtual Access and Virtual Access with Roll are currently not supported for VPLEX virtual volumes.

UpdatingThis section contains instructions for updating various components of the VPLEX and RecoverPoint solution.

Certificates Certificates expire from time to time. Use the following procedures to update expired certificates.

VPLEX certificate inRecoverPoint

To update the VPLEX certificate in RecoverPoint:

1. In the RecoverPoint Navigation pane, select Splitters. Select the splitter of the VPLEX whose certificate you wish to update, and click the Splitter Properties icon.

The Splitter Properties dialog box opens.

2. Click Credentials

The Configure login credentials dialog box opens.

3. Click the Browse button and select a valid certificate.

RecoverPointcertificate in VPLEX

To update the RecoverPoint certificate in VPLEX:

1. If deploying with VPLEX Metro, perform the following procedure at both Metro clusters.

2. Log in to the VPLEX Management Server and open the VPLEX CLI.

3. Import the RecoverPoint certificate:

VPlexcli:/> rp import -certificate


16

Disaster recovery

You will be prompted that modifying security settings will cause the VPLEX CLI to restart and will require a new login from all connected GUI and CLI clients.

4. Enter:

..> CONTINUE

5. Enter the RecoverPoint Site Management IPv4 address for the cluster connected to the VPLEX.

6. When prompted if you trust this certificate, enter:

..> y

The VPLEX Management Console closes.

Disaster recoveryThis section lists disaster scenarios, their consequences, and recovery procedures.

Production disasters The tables in this section cover disaster scenarios of production on the VPLEX platform.

Table 3 Disaster scenarios and recovery procedures: VPLEX Local

Disaster scenario Consequences Recovery procedure Restore procedure

VPLEX-RecoverPoint link failure

Marking on splitter. Replica not up to date.

Restore link, RecoverPoint automatically resynchronizes.

Production not affected. No restore required.

VPLEX cluster failure Production loss. If CDP on same cluster, loss of local replica.

In RecoverPoint, fail over to RecoverPoint replica. |f the only RecoverPoint copy is on the same cluster, no recovery option.

In RecoverPoint, restore production. Failback is automatic.

RecoverPoint failure Replica loss. No replication and no image access.

Restore RecoverPoint, RecoverPoint automatically resynchronizes.


Data corruption VPLEX volumes corrupted. Halt applications. In RecoverPoint, find last uncorrupted image.

In RecoverPoint, restore production from last uncorrupted image. Restart production and applications.


Disaster recovery

Table 4 Disaster scenarios and recovery procedures: VPLEX Metro


VPLEX cluster (non-RecoverPoint side) failure; VPLEX inter-cluster link failure

Loss of VPLEX cluster (non-RecoverPoint side). RecoverPoint not affected.

Restore VPLEX cluster or inter-cluster link. VPLEX automatically resynchronizes.

Other cluster not affected. No restore required.

VPLEX RecoverPoint link failure,

Marking on splitter. Restore link. RecoverPoint will automatically resynchronize.


RecoverPoint cluster failure. No replica. No replication and no image access.

Restore RecoverPoint cluster. RecoverPoint will automatically resynchronize.


Data corruption VPLEX volumes corrupted. Halt applications. In RecoverPoint, find last uncorrupted image.

In RecoverPoint, restore production from last uncorrupted image at replica. Both legs of Metro cluster restored simultaneously. RecoverPoint fails back automatically.

VPLEX cluster (RecoverPoint side) failure.

Loss of the VPLEX cluster. Applications continue to write to the other VPLEX cluster (non-RecoverPoint side). All RecoverPoint replicas invalid. RecoverPoint disables access to volumes and stops replications

Restore the VPLEX cluster. VPLEX automatically resynchronizes from the active cluster (non-RecoverPoint side).

Once the failed VPLEX cluster is functioning again, VPLEX automatically updates the data from the other cluster. After restore, RecoverPoint access is enabled, which triggers resynchronization of all RecoverPoint replicas. During rebuild of the VPLEX cluster and while resynchronizing replicas, RecoverPoint consistency groups have status = init. Image access and snapshots are disabled during this process.


18

Disaster recovery

Replica disasters The tables in this section cover disaster scenarios of replicas on the VPLEX platform.

Table 5 Disaster scenarios and recovery procedures: VPLEX Metro with Cluster Witness


Inter-cluster link failure, Cluster Witness able to contact both clusters

The winning cluster detaches from the Metro system and resumes operations. All new I/Os are logged. The losing cluster suspends I/Os,

Restore the inter-cluster link. RecoverPoint not affected, as it is attached to the winning cluster. After link is restored, VPLEX automatically resynchronizes the losing cluster from logged I/Os.

Inter-cluster link failure, Cluster Witness unable to contact winning cluster.

Winner suspends I/Os. Loser resumes operation. RecoverPoint cannot read or write to volumes and replication stops. Metro DR1 volumes may be inconsistent.

Restore the Cluster Witness Server WAN link and the inter-cluster link.

VPLEX rebuilds and resynchronizes the suspended cluster. When both VPLEX clusters are up-to-date, RecoverPoint will be notified that it can continue operations. Volume sweeps of DR1 volumes will start.

Inter-cluster link failure, Cluster Witness unable to contact winning cluster.Administrator detaches winning cluster manually from Metro system.

Both clusters can receive I/Os, but will be unsynchronized. RecoverPoint will continue to protect the winning cluster.

Restore the Cluster Witness Server WAN link and the inter-cluster link. Administrator must declare winning cluster. Non-RecoverPoint attached cluster cannot be declared the winner. Manually resume losing cluster.

VPLEX rebuilds and resynchronizes the suspended cluster. When both VPLEX clusters are up-to-date, RecoverPoint will be notified that it can continue operations. Volume sweeps of DR1 volumes will start.


Disaster recovery




Splitter delays writes to the volumes.RecoverPoint cannot access the volumes, replica not up to date.RecoverPoint consistency groups have status = paused by system in no access and active in image access.In image access state, if the link failure continues for more than 5 minutes, the replica state will be changed to no access (applications can’t access the volumes until restore).

Restore link After restore, there will be a short init on the replica.

VPLEX cluster failure Loss of the VPLEX cluster. Applications cannot access the volumes.RecoverPoint cannot access the volumes, replica not up to date.RecoverPoint consistency groups have status = paused by system in no access and active in image access.In image access state, if the link failure continues for more than 5 minutes, the replica state will be changed to no access (applications can’t access the volumes until restore).

Restore VPLEX cluster. After restore, there will be a short init on the replica.

RecoverPoint failure Replication stops. Splitter delays writes to volumes. If the link failure continues for more than 5 minutes, the replica state will be changed to no access (applications can’t access the volumes until restore).


Resynchronizing RecoverPoint. Replicas may require full sweep or volume sweep.


20

Disaster recovery

Data corruption During image access, VPLEX volumes corrupted.

Halt applications. In RecoverPoint, find last uncorrupted image.

In RecoverPoint, perform failover to the last uncorrupted image in the replica, then restore production.






In winner cluster, splitter delays writes to the volumes. In loser cluster, writes will arrive to the volumes.RecoverPoint cannot access the volumes, replica not up to date.RecoverPoint consistency groups have status = paused by system in no access and active in image access.In image access state, if the link failure continues for more than 5 minutes, the replica state will be changed to no access (applications can’t access the volumes until restore).

Restore link. After restore, RecoverPoint automatically resynchronizes. If 5 minutes passed, there will be volume sweeps on the volumes that writes were sent to.

VPLEX cluster (RecoverPointside) failure.

Loss of the VPLEX cluster. Applications cannot access the volumes on either cluster.RecoverPoint cannot access the volumes, replica not up to date.RecoverPoint consistency groups have status = paused by system in no access and active in image access.

Restore the VPLEX cluster. After restore, there will be a short init of the replica.


Disaster recovery

RecoverPoint failure In winner cluster, splitter delays writes to the volumes. In loser cluster, writes will arrive to the volumes.RecoverPoint is down.In image access state, if the RPAs are not back online for more than 5 minutes, the replica state will be changed to no access (applications can’t access the volumes until restore).


After restore, RecoverPoint automatically resynchronizes. If 5 minutes passed, there will be volumes sweep on the volumes that writes were sent to.

Double disaster: VPLEXcluster (RecoverPoint side)failure, RecoverPoint failure.

Loss of the VPLEX cluster. Applications can’t access the volumes in both clusters.RecoverPoint is down.

Restore the VPLEX cluster. Restore RecoverPoint.

Once the VPLEX cluster and RecoverPoint are up again, RecoverPoint automatically resynchronizes. Resynchronizing RecoverPoint replica may require full sweep or volume sweep.





Inter-cluster link failure, Cluster Witness able to contact both clusters

The winning cluster detaches from the Metro system and resumes operations. All new I/Os are logged.

Restore the inter-cluster link. RecoverPoint not affected, as it is attached to the winning cluster. After link is restored, VPLEX automatically resynchronizes the losing cluster from logged I/Os.

Inter-cluster link failure, Cluster Witness unable to contact winning cluster. Replica is in no access state or in image access state.

Applications and RecoverPoint cannot access the volumes.RecoverPoint consistency groups have status = paused by system in no access and active in image access.

Restore the Cluster Witness, Server WAN link, and the inter-cluster link.

RecoverPoint access to the volumes is restored. RecoverPoint consistency groups have status = active.


22

Disaster recovery

VPLEX inter-cluster link failure.Administrator decides to resume loser cluster manually.Replica is in no access state or in image access state,

VPLEX inter-cluster link failure. Administrator decides to resume loser cluster manually.Replica is in no access state or in image access state.

Restore the inter-cluster link. VPLEX rebuilds and resynchronizes the clusters. When both VPLEX clusters are up-to-date, RecoverPoint will be notified that it can continue operations. Full sweep of the volumes will start.Notice: All the I/Os that arrived during the disaster from VPLEX cluster (non-RecoverPoint side) will be overridden. To avoid this outcome, user must perform failover to RecoverPoint production copy BEFORE starting the restore procedure.

Inter-cluster link failure, Cluster Witness unable to contact winning cluster.Administrator detaches winning cluster manually from Metro system. Replica is in no access state or in image access state

Specific case:Administrator has decided to allow applications to continue writing to non-RecoverPoint attached cluster. The volumes are inconsistent.In no access and in image access states, applications on the loser cluster continue sending I/Os.

Restore the Cluster Witness, Server WAN link, and the inter-cluster link.

VPLEX rebuilds and resynchronizes the clusters. When both VPLEX clusters are up-to-date, RecoverPoint will be notified that it can continue operations. Full sweep of the volumes will start.

Notice: All the I/Os that arrived during the disaster from VPLEX cluster (non-RecoverPoint side) will be overridden. To avoid this outcome, user must perform failover to RecoverPoint production copy BEFORE starting the restore procedure.




Troubleshooting

Troubleshooting

Regaining access to a volume that was previously attached to the VPLEX splitter

If a RecoverPoint cluster is decommissioned or taken down without disabling its consistency groups, it may leave production and replica devices with failed splitter sessions, held, and/or in a read-only state. Contact EMC Customer Service regain access to these volumes.

Copyright © 2012 EMC Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the EMC Online Support Site.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com.

All other trademarks used herein are the property of their respective owners.


Documents

RecoverPoint-Deploying-with-VPLEX-Technical-Notes