If I understand your question correctly you are asking whether you can perform a failback to the original production site. Yes, you can do that with ease. You perform a failover from Site1 (Prod) to Site2 (DR). Once you are up and running at DR you start replicating from Site2 to Site1, after you are satisfied with the data at Site2. RP will perform a sync between Site2 and Site1 - it will only copy the changes that were made at Site2 since the failover. After the sync is done you would perform another failover (aka failback) and at that point you are back in business at Site1.
Use failover to the DR site and if you don't want the writes at the DR site to replicate back to the original Prod site then simply pause CG replication to the original Prod site prior to allowing host access at the DR site. This will mark the write data at the DR site (now the new Prod site as the roles will have changed due to the failover) using the CG local copy journals and when you're ready to fail back to the original Prod site (now the DR site) simply resume the replication, wait until the CGs reach an Active state and then initiate a failover back to the original Prod site.
etaljic81
1K Posts
0
July 31st, 2015 05:00
If I understand your question correctly you are asking whether you can perform a failback to the original production site. Yes, you can do that with ease. You perform a failover from Site1 (Prod) to Site2 (DR). Once you are up and running at DR you start replicating from Site2 to Site1, after you are satisfied with the data at Site2. RP will perform a sync between Site2 and Site1 - it will only copy the changes that were made at Site2 since the failover. After the sync is done you would perform another failover (aka failback) and at that point you are back in business at Site1.
etaljic81
1K Posts
1
July 31st, 2015 05:00
By the way, no re-install of RP or re-licensing. That's how the product is designed.
forshr
2 Intern
•
1.1K Posts
1
July 31st, 2015 06:00
Hi Dave,
Use failover to the DR site and if you don't want the writes at the DR site to replicate back to the original Prod site then simply pause CG replication to the original Prod site prior to allowing host access at the DR site. This will mark the write data at the DR site (now the new Prod site as the roles will have changed due to the failover) using the CG local copy journals and when you're ready to fail back to the original Prod site (now the DR site) simply resume the replication, wait until the CGs reach an Active state and then initiate a failover back to the original Prod site.
Regards,
Rich Forshaw
RecoverPoint Corporate Systems Engineering
Dave_Hays
2 Posts
1
July 31st, 2015 10:00
Thank you these are very useful responses. I am really looking forward to conducting tests later this summer.
Thanks everyone for your responses!
-dave hays