Start a Conversation

Unsolved

This post is more than 5 years old

3356

February 23rd, 2017 18:00

recoverpoint failover steps

Hello all,

I am very new to Recoverpoint and need some help here .

Customer has plans to  run a DR test and would like to write to their secondary site and discard the changes done .

And after a month or so failover again , but this time they want to run on the DR for a week and then failback .So all the production activity will be running from DR site for a week .

What should be a proper DR plan  for both the activities .

Here is the set up -

FC connected VNX1 at both the sites (remote replication) replicating via RP (v4.4).Only two node oracle hosts are attached to the VNX .

There are 4 CG. Also, no SRM .

Please let me know what are the initial information that I need to collect and what be the strategy  to do a failover .

If possible please share some documents ot links pertaining to RP DR without using SRM .

Thanks in advance .

2 Intern

 • 

1.1K Posts

February 24th, 2017 01:00

Hi Armin,

Firstly, I would recommend that you take a look at the RP Admin Guide as it contains a useful recovery operations section.

In respect of considerations relating to the failover activity itself, you may want to consider single CG failover versus using a Group Set that contains all of the CGs and failing over at the Group Set level.

In relation to this, any recovery activity has the pre-requisite step requirement of testing an image which requires the selection of a PiT image from the replica copy journal.

This aspect of the failover relates to the use of a crash-consistent versus application-consistent image and whether a parallel application-consistent image (parallel bookmarking) should be used as part of the test failover. Parallel bookmarks can be generated with or without the use of a Group Set and can be crash-consistent or application-consistent, although the generation of an application-consistent bookmark would require quiescing the database(s).

Regards,

Rich

No Events found!

Top