Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

2002

March 29th, 2015 22:00

what can I do when we decide to keep writes to a test copy

User do a test copy(not test copy and failover or test copy and recover production) , and some real application data was written to the image when copy is testing, User want to keep the data and want this snapshot with writen data be failback to production copy.

What can I do in this situation? I think the first step is to direct access, then what is the next? is to delete the CG and recreate a new CG and swap the production and replication, and then failover the CG? or there are some other easier steps to fulfill the task.

2 Intern

 • 

1.1K Posts

March 31st, 2015 01:00

Use Test a Copy in Logged Image Access mode, let it reach Logged mode, then choose Direct Access, then from the Activities pane choose Further Actions and then select Failover.

2 Intern

 • 

1.1K Posts

March 30th, 2015 02:00

Hi there,

After moving to direct image access mode you can simply invoke failover.

Regards,

Rich

1 Rookie

 • 

33 Posts

March 30th, 2015 16:00

Thanks Forshr, do you mean just need to click "Test  copy and failover" , then the wizard will skip the step of test copy and go to failover directly with current data in replication volume?

1 Rookie

 • 

33 Posts

March 31st, 2015 03:00

It's clear , Thanks very much

September 29th, 2016 07:00

I have been into similar situation where the customer wants to simulate actual DR situation.Once the operations are up at the copy site, the customer wants to resync all the changes made at the copy site to the production site. Do you think your idea of Logged Image Access --> Direct Access --> Failover would apply here as well?

I also have some follow-up questions:

1) Once you are in Direct Access mode, do you go to Manage Recovery and select Failover from the Select Next Action dropdown?

2) Once we issue Failover, what would be the state of replication, production site, and the copy site?

3) Once the changes from copy site are synced with the production site, what are the next steps to resume replication from production site to copy site (assuming production is up by now)?

Thank You,

Harsh

2 Intern

 • 

1.1K Posts

September 29th, 2016 12:00

Yes, apply exactly the same process.

1) Yes.

2) Replication is reversed and the two copies switch roles (assuming that there are just two copies), i.e. the remote/DR copy assumes to role of Production.

3)  Initiate Test a Copy and Failover without the need to move from Logged Image access to Direct Image access.

Regards,

Rich

No Events found!

Top