Docu40285 RecoverPoint Deploying With VPLEX Technical Notes

7/18/2019 Docu40285 RecoverPoint Deploying With VPLEX Technical Notes

http://slidepdf.com/reader/full/docu40285-recoverpoint-deploying-with-vplex-technical-notes 1/23

1

These technical notes provide information, required procedures, and best practices that are specific to replicating VPLEX virtual volumeswith RecoverPoint. For information about VPLEX, refer to the VPLEX

documentation. For information about RecoverPoint refer to theRecoverPoint 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 ® RecoverPoint

Deploying with VPLEX™

Technical NotesP/N 300-013-380

Rev 02

September 10, 2012



2 RecoverPoint Deploying with VPLEX Technical Notes

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.

http://-/?-

http://-/?-



3

VPLEX and RecoverPoint

RecoverPoint Deploying with VPLEX Technical Notes


VPLEX conceptsand features

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

VPLEX is deployed as clusters of one or more engines. Each engine

comprises two I/O directors. Each cluster runs a storagevirtualization software environment called GeoSynchrony. Eachcluster has a service management station that provides storagemanagement.

The VPLEX front end appears to hosts like storage controllers (targetports). 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 hardwareor path failure, any remaining director can access data and serviceI/Os without any disruption of operations.

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

VPLEX Metro VPLEX Metro provides active-active access to data at two sites thatare within synchronous replication distance (less than 5 msround-trip time is recommended) of each other. The same set ofdevices is exposed at both sites. I/Os can be performed locally ateither site, and VPLEX storage management assures coherency andprotection 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 thatare asynchronous replication distance of each other.

VPLEX configurationssupported byRecoverPoint

RecoverPoint supports only VPLEX Local and VPLEX Metroconfigurations. RecoverPoint can replicate the virtual volumes inVPLEX Metro consistency groups if and only if they are local to thesite where RecoverPoint is attached; or distributed virtual volumeswith a local extent.

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





Data migration VPLEX can non-disruptively move data between heterogeneous

storage devices or extents (units of physical storage that constitute adevice).

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

VPLEX Metro provides distributed RAID 1 devices. VPLEX virtualvolumes 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 havefull read/write access to their virtual volumes, even if the otherVPLEX cluster is down.

VPLEX cluster witnessand winner-loser

arbitration

If the Metro link between VPLEX sites fails, VPLEX elects a single sitefor each consistency group to be the winner; this site will continue toreceive all host I/Os. VPLEX consistency groups must be attached tothe VPLEX splitter at the site specified as the winning site. For this

reason, RecoverPoint can only protect a distributed device at oneVPLEX Metro site. VPLEX does not allow a virtual volume to beprotected by RecoverPoint unless the virtual volume is in a VPLEXconsistency group that is RecoverPoint enabled and set to prefer thesite with RecoverPoint attached.

If the preferred site (site with the VPLEX splitter) fails, VPLEXWitness can override the site preference rule (override thepre-defined winner). At that point, host I/Os will continue at thelosing site, but new writes will not be protected by RecoverPoint untilthe failed site comes back online and is updated. RecoverPoint accessto the volumes will be disabled until the failed site is repaired andupdated. For more information, refer to “Disaster recovery” onpage 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



5

Solution design


Solution designThe following configurations are currently supported whendeploying VPLEX with RecoverPoint:

Supportedtopologies

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 beconnected to a single VPLEX cluster in the Metro system.

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

RecoverPoint can only protect distributed VPLEX devices from onesite 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 singlesite.

VPLEX Local

RecoverPoint CRR

RecoverPoint provides remote replication and point-in-timerecovery.

VPLEX LocalRecoverPoint CLR

RecoverPoint provides replication to one remote site andpoint-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-timerecovery.

VPLEX MetroRecoverPoint CLR

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




Solution design

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

There are several ways to implement VPLEX Metro withRecoverPoint:

◆ A standard VPLEX Metro implementation: production site onVPLEX A, mirror on VPLEX B, and RecoverPoint replica on adifferent 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 asproduction

The following VPLEX volumes may be replicated by RecoverPoint:

◆ local volumes.

◆ distributed volumes. Splitting and replicating is only allowed onone 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 VPLEXsite protected by RecoverPoint, and not distributed. If necessary, theRecoverPoint repository and journals may be on the physical array,without VPLEX virtualization, or on a different array. The bestpractice is to have the RecoverPoint repository, journals, andreplication volumes on the VPLEX.

Cabling ◆ As for any other array-based splitter, every RecoverPointappliance needs to be cabled to two fabrics. Single-fabricconfigurations are not supported.

◆ Each RecoverPoint appliance should have at least two physicalconnections 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 scaledenvironments, zoning must adhere to the guidelines in thisdocument.

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



7

Solution design


pane, click RPAs. In the Component pane, double-click on the RPAname.

You can also use the RecoverPoint Installation Manager (log in to theRecoverPoint appliance as boxmgmt) and select Diagnostics > FibreChannel diagnostics > View Fibre Channel details to list thepWWNs 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 istherefore not necessary to separate RPA Fibre Channel ports intoinitiator and target zones.

The best practice is to use the RPA Fibre Channel ports as bothinitiators and targets. In this configuration, maximum performanceand redundancy, and optimal use of resources are achieved. If, because of Initiator-Target LUN (ITL) limitations or othernon-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 andavailability. However, initiator-target separation is not supported atall 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 notFibre-dead, but RecoverPoint cannot communicate with it),RecoverPoint replication is not available.

◆ VPLEX Metro remote exported volumes cannot be replicated byRecoverPoint.

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

◆ The RecoverPoint repository and journal volumes must be aVPLEX Local volume (not distributed). If necessary, therepository or journals may be presented directly to RecoverPoint

from the physical array, without VPLEX virtualization. If there is




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 therepository and journals.

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

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

• VPLEX virtual volume expansion

• RecoverPoint virtual image access (use logged access instead)

• Device migrations between two VPLEX clusters are notsupported if one leg of the device is replicated byRecoverPoint

◆ A VPLEX cluster supports up to 2048 splitter sessions. Onesplitter session is required for each LUN that is used either asproduction or as a replica. As a result, if production and a replicareside on the same VPLEX cluster (CDP), one session is requiredfor the production LUN and another for the local replica LUN. Ifthe VPLEX splitter is shared among multiple RecoverPointclusters, the sessions of each cluster is counted towards themaximum number of splitter sessions per VPLEX cluster.

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

◆ VPLEX supports a maximum of 8000 local devices with globalvisibility.

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


Prerequisites ◆ VPLEX 5.1.0 or later



9



◆ 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 arerequired:

• IP connectivity between the Metro sites

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

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

VPLEX installation 1. Use EZ Setup as for any other VPLEX installation. Forinstructions, refer to the EMC VPLEX Configuration Guide. VPLEX5.1 and later supports RecoverPoint and contains a built-in

RecoverPoint write splitter.

VPLEX-to-storagezoning

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 beconnected to the back-end fabric.

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

RPA-to-VPLEXfront-end zoning

• In each fabric, create one zone that includes all RecoverPointFibre Channel ports and all VPLEX front-end ports involved

in RecoverPoint replication. Both VPLEX and RecoverPointmust have at least one Fibre Channel port per fabric for eachVPLEX director.

RegisteringRecoverPoint

Register RecoverPoint Fibre Channel initiator ports with VPLEX:

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

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





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

Creating

RecoverPointrepository

6. Create a VPLEX local (not distributed) virtual volume for the

RecoverPoint repository. Make sure the RecoverPoint repositoryis at least 3 GB.

CreatingRecoverPointstorage view

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

a. From the drop-down menu in the VPLEX GUI, select

Provision Storage > <cluster name> > Storage Views > CreateStorage View.

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

c. Add to the RecoverPoint System storage view:

– All RecoverPoint initiators

– All VPLEX front-end ports used by the RecoverPointcluster

– VPLEX Virtual Volumes to be used for the RecoverPointrepository, 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 RecoverPointstorage view:

– Remote volumes

– Volumes that are already in a different RecoverPointstorage view

– Volumes in VPLEX consistency groups whose members arein a different RecoverPoint storage view



11



A RecoverPoint cluster may take up to 2 minutes to registerchanges to VPLEX consistency groups. Wait 2 minutes aftermaking the following changes before creating or changing aRecoverPoint consistency group:

• Adding virtual volumes to or removing them from a VPLEXconsistency group

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

• Changing the detach rule of a VPLEX consistency group

InstallingRecoverPoint

8. Use RecoverPoint Installer wizard to install RecoverPoint.Continue up to and including zoning (Wizard step 7.1.1). Fordetailed 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 differentnames 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 twoclusters must refer to the Beijing site by different names, such asBeijing1 and Beijing2. In addition, the same LUN cannot bereplicated both to Bangalore and to Frankfurt.

ActivatingRecoverPointlicense

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

ImportingRecoverPointcertificate in VPLEX

The best practice is to use certificates to avoid user configurationerrors. To do so, the RecoverPoint certificate is imported into VPLEXand the VPLEX certificate is imported in RecoverPoint. Without thecertificates, VPLEX and RecoverPoint cannot obtain managementinformation about volume types. With the certificates, VPLEX andRecoverPoint 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





Volume dialog box, because distributed volumes are not supportedfor journals.

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

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

b. Import the RecoverPoint certificate:

VPlexcli:/> rp import -certificate

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

c. Enter:

..> CONTINUE

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

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

..> y

The VPLEX Management Console closes.

AddingRecoverPoint clusterto VPLEX

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

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

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



13



When RPAs are zoned to VPLEX using single-channel mode (2

RPA ports zoned to VPLEX front-end ports, and 2 RPA portszoned to VPLEX back-end ports), this command issues awarning. The system checks that all 4 ports on the RPA arezoned to both VPLEX front-end and back-end ports(dual-channel mode).

Best practice is to zone every RPA port to both VPLEX frontend and back-end ports. Administrators who have purposely

configured single-channel mode can safely ignore thewarning.

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

Creating VPLEXconsistency 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 asfollows:

a. Consistency groups for replication volumes:

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

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

b. VPLEX consistency group for journals and repository:

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

– Add the repository to the consistency group for journals.





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

14. Add RecoverPoint replication volumes and journal volumes tothe RecoverPoint storage view.

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

RPA-to-VPLEXback-end zoning

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

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

Add the VPLEXsplitter

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

a. Click Add Splitter. Select the VPLEX splitter to Add. PressNext.

b. Fill out the Credentials.

Import the VPLEXcertificate

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

CreatingRecoverPointconsistency groups

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

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

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

volume, regardless to which splitter the production volume isattached.



15

Updating


The replication volumes will be attached to the VPLEX splitterautomatically.

Validating theRecoverPointalignment in VPLEX

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

20. Start replication.

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

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

Updating

This section contains instructions for updating various components

of the VPLEX and RecoverPoint solution.

Certificates Certificates expire from time to time. Use the following procedures toupdate 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, andclick 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 followingprocedure at both Metro clusters.

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

3. Import the RecoverPoint certificate:

VPlexcli:/> rp import -certificate




Disaster recovery

You will be prompted that modifying security settings will causethe VPLEX CLI to restart and will require a new login from allconnected GUI and CLI clients.

4. Enter:

..> CONTINUE

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

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

The VPLEX Management Console closes.

Disaster recovery

This section lists disaster scenarios, their consequences, and recoveryprocedures.

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

Table 3 Disaster scenarios and recovery procedures: VPLEX Local

Disaster scenario Consequences Recovery procedure Restore procedure

VPLEX-RecoverPoint linkfailure

Marking on splitter. Replicanot up to date.

Restore link, RecoverPointautomatically resynchronizes.

Production not affected. Norestore required.

VPLEX cluster failure Production loss. If CDP onsame cluster, loss of localreplica.

In RecoverPoint, fail over toRecoverPoint replica. |f theonly RecoverPoint copy is on

the same cluster, no recoveryoption.

In RecoverPoint, restoreproduction. Failback isautomatic.

RecoverPoint failure Replica loss. No replicationand no image access.

Restore RecoverPoint,RecoverPoint automaticallyresynchronizes.


Data corruption VPLEX volumes corrupted. Halt applications. InRecoverPoint, find lastuncorrupted image.

In RecoverPoint, restoreproduction from lastuncorrupted image. Restartproduction and applications.



17

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 orinter-cluster link. VPLEXautomatically resynchronizes.

Other cluster not affected. Norestore required.

VPLEX RecoverPoint linkfailure, Marking on splitter. Restore link. RecoverPoint willautomatically resynchronize. Production not affected. Norestore required.

RecoverPoint cluster failure. No replica. No replication andno image access.

Restore RecoverPoint cluster.RecoverPoint willautomatically resynchronize.


Data corruption VPLEX volumes corrupted. Halt applications. InRecoverPoint, find lastuncorrupted image.

In RecoverPoint, restoreproduction from lastuncorrupted image at replica.

Both legs of Metro clusterrestored simultaneously.RecoverPoint fails backautomatically.

VPLEX cluster (RecoverPointside) failure.

Loss of the VPLEX cluster.Applications continue to writeto the other VPLEX cluster(non-RecoverPoint side). AllRecoverPoint replicas invalid.RecoverPoint disables accessto volumes and stopsreplications

Restore the VPLEX cluster.VPLEX automaticallyresynchronizes from the activecluster (non-RecoverPointside).

Once the failed VPLEX clusteris functioning again, VPLEXautomatically updates the datafrom the other cluster. Afterrestore, RecoverPoint accessis enabled, which triggersresynchronization of allRecoverPoint replicas. Duringrebuild of the VPLEX clusterand while resynchronizingreplicas, RecoverPointconsistency groups havestatus = init . Image accessand snapshots are disabled

during this process.




Disaster recovery

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

Table 5 Disaster scenarios and recovery procedures: VPLEX Metro with ClusterWitness


Inter-cluster link failure,Cluster Witness able tocontact both clusters

The winning cluster detachesfrom the Metro system andresumes operations. All newI/Os are logged. The losing

cluster suspends I/Os,

Restore the inter-cluster link. RecoverPoint not affected, asit is attached to the winningcluster. After link is restored,VPLEX automatically

resynchronizes the losingcluster from logged I/Os.

Inter-cluster link failure,Cluster Witness unable tocontact winning cluster.

Winner suspends I/Os. Loserresumes operation.RecoverPoint cannot read orwrite to volumes andreplication stops. Metro DR1volumes may be inconsistent.

Restore the Cluster WitnessServer WAN link and theinter-cluster link.

VPLEX rebuilds andresynchronizes the suspendedcluster. When both VPLEXclusters are up-to-date,RecoverPoint will be notifiedthat it can continue operations.Volume sweeps of DR1

volumes will start.


Administrator detacheswinning cluster manually fromMetro system.

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

Restore the Cluster WitnessServer WAN link and theinter-cluster link. Administratormust declare winning c luster.Non-RecoverPoint attachedcluster cannot be declared thewinner. Manually resumelosing cluster.

VPLEX rebuilds andresynchronizes the suspendedcluster. When both VPLEXclusters are up-to-date,RecoverPoint will be notifiedthat it can continue operations.Volume sweeps of DR1volumes will start.



19

Disaster recovery





Splitter delays writes to thevolumes.

RecoverPoint cannot accessthe volumes, replica not up todate.

RecoverPoint consistencygroups have status = pausedby system in no access andactive in image access.

In image access state, if thelink failure continues for morethan 5 minutes, the replicastate will be changed to noaccess (applications can’t

access the volumes untilrestore).

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

VPLEX cluster failure Loss of the VPLEX cluster.Applications cannot accessthe volumes.

RecoverPoint cannot accessthe volumes, replica not up todate.


In image access state, if thelink failure continues for morethan 5 minutes, the replicastate will be changed to noaccess (applications can’taccess the volumes until

restore).

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

RecoverPoint failure Replication stops. Splitterdelays writes to volumes. If thelink failure continues for morethan 5 minutes, the replicastate will be changed to noaccess (applications can’taccess the volumes until

restore).


ResynchronizingRecoverPoint. Replicas mayrequire full sweep or volumesweep.




Disaster recovery

Data corruption During image access, VPLEXvolumes corrupted.

Halt applications. InRecoverPoint, find lastuncorrupted image.

In RecoverPoint, performfailover to the last uncorruptedimage in the replica, thenrestore production.






In winner cluster, splitterdelays writes to the volumes.In loser cluster, writes willarrive to the volumes.

RecoverPoint cannot access

the volumes, replica not up todate.


In image access state, if thelink failure continues for morethan 5 minutes, the replica

state will be changed to noaccess (applications can’taccess the volumes untilrestore).

Restore link. After restore, RecoverPointautomatically resynchronizes.If 5 minutes passed, there willbe volume sweeps on thevolumes that writes were sent

to.

VPLEX cluster (RecoverPoint

side) failure.

Loss of the VPLEX cluster.Applications cannot accessthe volumes on either cluster.

RecoverPoint cannot accessthe volumes, replica not up to

date.


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



21

Disaster recovery


RecoverPoint failure In winner cluster, splitterdelays writes to the volumes.In loser cluster, writes willarrive to the volumes.

RecoverPoint is down.

In image access state, if theRPAs are not back online for

more than 5 minutes, thereplica state will be changed tono access (applications can’taccess the volumes untilrestore).


After restore, RecoverPointautomatically resynchronizes.If 5 minutes passed, there willbe volumes sweep on thevolumes that writes were sentto.

Double disaster: VPLEX

cluster (RecoverPoint side)

failure, RecoverPoint failure.

Loss of the VPLEX cluster.Applications can’t access thevolumes in both clusters.

RecoverPoint is down.

Restore the VPLEX cluster.Restore RecoverPoint.

Once the VPLEX cluster andRecoverPoint are up again,RecoverPoint automaticallyresynchronizes.

Resynchronizing RecoverPointreplica may require full sweepor volume sweep.





Inter-cluster link failure,Cluster Witness able tocontact both clusters

The winning cluster detachesfrom the Metro system andresumes operations. All newI/Os are logged.

Restore the inter-cluster link. RecoverPoint not affected, asit is attached to the winningcluster. After link is restored,VPLEX automaticallyresynchronizes the losingcluster from logged I/Os.

Inter-cluster link failure,Cluster Witness unable tocontact winning cluster.Replica is in no access stateor in image access state.

Applications and RecoverPointcannot access the volumes.


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

RecoverPoint access to thevolumes is restored.RecoverPoint consistencygroups have status = active.




Disaster recovery

VPLEX inter-cluster linkfailure.

Administrator decides toresume loser cluster manually.

Replica is in no access stateor in image access state,

VPLEX inter-cluster linkfailure. Administrator decidesto resume loser clustermanually.

Replica is in no access stateor in image access state.

Restore the inter-cluster link. VPLEX rebuilds andresynchronizes the clusters.When both VPLEX clustersare up-to-date, RecoverPointwill be notified that it cancontinue operations. Fullsweep of the volumes willstart.

Notice: All the I/Os thatarrived during the disasterfrom VPLEX cluster(non-RecoverPoint side) willbe overridden. To avoid thisoutcome, user must performfailover to RecoverPointproduction copy BEFORE

starting the restore procedure.


Administrator detacheswinning cluster manually fromMetro system. Replica is in noaccess state or in image

access state

Specific case:

Administrator has decided toallow applications to continuewriting to non-RecoverPointattached cluster. The volumesare inconsistent.

In no access and in image

access states, applications onthe loser cluster continuesending I/Os.

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

VPLEX rebuilds andresynchronizes the clusters.When both VPLEX clustersare up-to-date, RecoverPointwill be notified that it cancontinue operations. Fullsweep of the volumes willstart.

Notice: All the I/Os thatarrived during the disasterfrom VPLEX cluster(non-RecoverPoint side) willbe overridden. To avoid thisoutcome, user must performfailover to RecoverPointproduction copy BEFOREstarting the restore procedure.





23

Troubleshooting


Troubleshooting

Regaining access toa volume that waspreviously attachedto the VPLEX splitter

If a RecoverPoint cluster is decommissioned or taken down withoutdisabling its consistency groups, it may leave production and replicadevices 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 issubject 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 INTHIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicablesoftware 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.

Date post:	02-Mar-2016
Category:	Documents
Upload:	arul-kurian-raj
View:	410 times
Download:	16 times

Docu40285 RecoverPoint Deploying With VPLEX Technical Notes

Documents