Recovery point ( I would like to change the configuration of the present Consistency group making the secondary as Primary (Production) and Primary as secondary. )

If I am reading this correctly, this sounds like you want to do a failover or test a copy and failover in RP. This will allow you to enable image access, mount the LUNs on the target ESX hosts, validate the data (aka import the VM's), and then proceed to failover in the RP GUI - at that point when you failover, you will wipe the journal history and by default it will immediately start to replication backwards in the reverse direction. So the planning here would be to ensure you have shutdown, removed from inventory, etc on the source side prior to executing the failover.

Something like SRM will automate this for you in a better fashion as the manual process could be long and tedious on the VMware side given that is where all the work will be to cleanup and unmount, etc.

However the failover process in RP does what you want - presents and image on the target side and then reverses the roles and replication direction upon execution. What is left to the user is all of the host teardown, etc.

HTH

Hi , Thank you for the help,

So You are saying, Step 1: Shutdown the VM's and Remove it from Inventory from the Source side(Production).

Step 2: Test a Copy and Failover option on Recovery point and mount the Data store2 at Non production site and add the VM to the Inventory and Finish the failover to reverse replicate.

During these steps when do we unmount the production datastore1? If we are doing reverse replication the present Non production copy (Datastore1) , we need to unmount it right. If so When we need to unmount it.

correct - that is the general process to failover manually. In that process above, you would want to make sure you have unmounted the production (original primary site) prior to executing the failover in RP because that is when RP will attempt to reverse synchronize the data given the WAN links are all online.

If the intention is to simply cutover to another site you should initiate Logged Image Access mode on the CG in order to test the integrity of the data by mounting the VMs and then if all is good move to Direct Image Access mode to provide full R&W access. After doing this you can simply disable the CG.

There is no need to failover.

Regards,

Rich Forshaw

RecoverPoint Corporate Systems Engineering

Hi,

After cutting over want to use the same consistency group for reverse

replication.

Then you use the Test a Copy and Failover option and be mindful of the shutdown requirements at Prod. Note that appropriate messaging is provided in the UI warning you of the host shutdown requirements prior to the failover action.

Regards,

Rich

Hi Guys, Thank you for your help, still need to figure out some steps.

I Know the Process of Failover, i was asking the prerequisites to do the failover.

First we need to shutdown the Application VM and remove it from Inventory and then Unmount the production Datastore.

Second, Mount the Secondaty Datastore at Different site and add vmx to inventory, power on the Machine.

Follow the Failover procedure in Recovery Point. 

Is this Correct? i was wondering the process before failover (from source side and target side) .

OR

First we need to shutdown the Application VM and remove it from Inventory and then Unmount the production Datastore.

Remove the CONSISTENCY GROUP from the recovery point

Second, Mount the Secondaty Datastore at Different site and add vmx to inventory, power on the Machine, Assign the IP , DNS, NIC ADAPTER, check the Application is running at secondary.

Create a new CONSISTENCY GROUP WITH Secondary site as Production.

OR

Shutdown the Application server, Do the Test a copy in Recovery Point, Mount the Secondary datastore add the vmx to the Inventory Assign the IP, DNS, NIC VLAN.

Move it to the different Datastore which has a new consistency group assigned for reverse replication and start the replication reverse permanently.

Finish the Testing and remove the luns, old consistency group , on both the sites.

Which one is better and send me the prerequisites???

Shutting down the VMs prior to the activity will provide application consistency. You can issue a bookmark after doing this and then initiate the Test a Copy and Failover activity. Use the bookmarked snapshot as part of the Test a Copy part of the activity and then after testing issue the Failover option.

Dude,

I was asking much of vmware activity (mounting n unmounting , removing from

inventory), any how you guys helped me a lot, finished the activity

yestarday successfully. Its doing the full sweep because i have recreated

the group.