Froda wrote:
Thank you for your reply very helpful !
Additional question, once I run the command ("setrcopygroup override <Rcopygroup name>" from the supposed source side) will the replication automatically start once more or will I have to start it manually?
Also, how can I be sure that the replication will transfer from my secondary datacenter 3PAR back to my primary datacenter 3PAR system, because as I mentioned we are running off of our secondary datacenter 3PAR system and would hate to see the replication go the wrong way?
Thanks again for you help
Well, you don't provide a lot of information here, so this would be best effort.....
Once you do override the RC group should transition to "started" mode and start resyncing. If it stays in "stopped" for a minute, you could try starting it manually.
Depending on what type of replication and setup you're running, getting back to your original datacenter depends on what type of setup you're running.... Do you have peer persistence? I'm assuming this is sync replication.... Do you have a stretched fabric? Are you running CLX?
For PP it's just a matter of doing a switchover. For CLX you might need to do a reverse natural if you have a stretched fabric and now running on hosts in site A and storage in site B. For just simple replication you need to do a failover (which will be disruptive).