1

Recover Point Connectivity Diagram Overview :

Work flow of Data Replication from Production site to Remote site

• Host writes to the LUN would be protected by RP for replication

• The array splitter driver intercepts the writes and sends a copy to the local RP and another

copy to the production lun

• The original write is committed to the production LUN in the normal way

• Writes received by local RP are acknowledged immediately

• The splitter on receiving both ACK from local RP and production lun sends the ACK back to

the production host confirming the write

• Local RP sends the compressed, sequenced and bookmarked writes to the remote RP at DR

site over IP links

• Remote RP receives the write and commits the same into the remote Journal post

uncompressed

Data written to the journal volume is then distributed to the remote volumes on the DR array,

ensuring that write-order sequence is preserved for data consistency.

2

Creating Consistency Group:

1) Right Click on “Consistency Groups”

2) Click on “Add Group”

3

3) Enter the name for Consistency Group; Select the RPA on which you want this Consistency

Group to be created. Select the Compression level and Enable Deduplication.

4) Name the Production Copy and Select the Production Host OS.

4

5) Select the check box “Create Remote Copy at DR_VNX5500”. Name the Replica copy and

select the Remote Host OS.

6) Consistency Group creation in process.

5

7) Creating the Replication set. Select all the LUNs in the production site for a particular host

that you want to replicate to Remote site.

8) Select the LUN from Remote site that corresponds to the Production host LUNs.

6

9) Similarly select LUNs One by One. Each pair will form a Replication Set.

10) All the Replication Sets are displayed once all the LUN pairs are selected.

7

11) Select the Journal Volume for Production Site and Remote site. Click on Manually Select

Journal Volumes.

12) Select the Journal Volume for Production Site.

8

13) Select the Journal volume for the Remote site.

14) Verify the Replication sets and the Journal Volumes at Production and Remote site.

9

15) Replication Set configuration in Process.

16) Right Click on the consistency group that you have created and Click on “Start Transfer” to

initiate the replication.

10

17) Initialization in Process.

11

DR DRILL PROCEDURE:

1) Initial Verification, before application shut down: Ensure that Replication in Active state (

This means all the data is in synch with DR volumes), Proceed further only if this is in Active

State OR wait till that comes to active state

2) Stop application associated with the specific consistency group, Flush application data as necessary and unmount the consistency group volume(s) on all attached hosts.

12

3) Creating Bookmark: Click on “Bookmark” icon on Right hand side-Top of the window.

4) Type the Bookmark name in the Pop-up window

13

5) Run the verify_group command, to verify that the bookmarked image has arrived in the target-side journal. Or can also check in GUI. Make sure all the data is transferred to DR side. No Lag showing in GUI.

6) Run the pause_transfer command OR pause the transfer in GUI. Run the verify_group command Or check in GUI

7) Enable Image Access: Click on “Enable Image Access”

14

8) To access the latest image select “Select the latest image”. To access the image that you

have bookmarked, select “Select an image from the list”

9) Select “logged Access”.

15

10) Click on finish to enable the Image Access.

11) Enabling Image access in progress.

16

12) Check the Storage Status at the Right hand side bottom of the screen. Status should be

“Storage: Logged access(0% full)”

13) Import vg and mount volumes on target host. Start DB and Application. Confirm the Data

consistency.

14) Check that you are able to bring up the host application with the replicated image at the target side, and that the image meets your requirements for fail over (e.g., with regard to the level of consistency). DBA and Application personal should confirm consistency of the data.

15) If you are not satisfied with this image, shut down the application, unmount the volume(s), and repeat this process for another image. In the Recover Point Management Console, use the Change button (General tab, Group Properties box) to access a different image.

17

Failover to Remote Site:

16) Ensure that you select the correct active storage pool or replication direction. A mistake in setting this parameter can result in the accidental loss of data at the source side.

17) Ensure that the preferred production side policy parameter is set correctly. Use "Failover to Remote Copy" parameters. This will switch to remote replica. Transfer from Production will stop. The original journal is erased, and the host application now has direct access to the desired image on the storage at what is now the source side. This will start replication back from current source / production to remote site ( Reverse Replication) On the Right hand side- Top, Click on “Failover” Icon. Uncheck the “Start Transfer” Check

Box and Click on “Yes”.

18) Click on Yes. This will erase the Journal in the Remote Site.

18

19) Failover in Process.

20) Replication direction changes after Faliover.

19

21) Status after Failover:

22) Right Click on Consistency Group and Click on Start Transfer.

20

23) Initialization in Process

24) Release systems to Users. This means DR systems are in production and released to business

and reverse replication also been executed.

25) After Initialization (Active State): Wait over here till it completes Initialization and changes

the status to Active. Follow below failback steps when production requires to go back to

original site

21

Failback Steps: -

26) Ensure that Replication in Active state ( This means all the data is in synch with DR ( Original Production volumes), Proceed further only if this is in Active State OR wait till that comes to active state

27) Stop application associated with the specific consistency group, Flush application data as necessary and unmount the consistency group volume(s) on all attached hosts.

28) Take Bookmark:

22

29) Verify the Bookmark.

30) Verify that the bookmarked image has arrived in the target-side journal. Checked in GUI. Make sure all the data is transferred to DR side. No Lag showing in GUI.

31) Pause the transfer in GUI.

23

32) Enable Image access at current DR site(i.e Actual Production): To access the latest image

select “Select the latest image”. To access the image that you have bookmarked, select “Select an

image from the list”

33) Select Logged Access mode.

24

34) Finish.

35) Check Logged access is 0% full:

36) Import vg and mount volumes on target host. Start DB and Application. Confirm the Data

consistency.

37) Check that you are able to bring up the host application with the replicated image at the target side, and that the image meets your requirements for fail over (e.g., with regard to the level of consistency). DBA and Application personal should confirm consistency of the data.

38) If you are not satisfied with this image, shut down the application, unmount the volume(s), and repeat this process for another image. In the Recover Point Management Console, use the Change button (General tab, Group Properties box) to access a different image.

25

39) Ensure that you select the correct active storage pool or replication direction. A mistake in setting this parameter can result in the accidental loss of data at the source side.

40) Ensure that the preferred production side policy parameter is set correctly. Use "Failover to Remote Copy" parameters. This will switch to remote replica. Transfer from Production will stop. The original journal is erased, and the host application now has direct access to the desired image on the storage at what is now the source side. This will start replication back from current source / production to remote site Click on “Failover” Icon. Uncheck the “Start Transfer” Check Box and Click on “Yes”.

41) Click on “yes”. Journal volume at Remote Site will be erased.

42) Status after Failover

26

43) Start Transfer from Production site to Remote Site:

44) Initialization in process:

27

45) Release systems to Business.

46) After Initialization (Active State): Wait over here till it completes Initialization and changes

the status to Active.