VMware Cloud Community
ChrisAllwein
Contributor
Contributor

Recover Grayed out

Hi,

I've just been setting up servers to replicate on 5.5.  I'm getting green checks on the status, and i'd like to test.  When I go to the recovery site, the option to recover is grayed out.  Even after powering down the primary VM. I'm trying to recover it by right-clicking the replication under the monitor tab, vshpere replication. Any ideas why I cant select recover?

Tags (1)
Reply
0 Kudos
5 Replies
Biliana
VMware Employee
VMware Employee

Hi,

1) If you are using VR with SRM , replication can be managed by SRM. You can check that when navigating to Incoming Replications and see what is in  "Managed by" column. To be able to recover with VR the "Managed by" value should be "VR". If it is "SRM" that means that it is added in SRM protection group.

2) Has your replication passed the initial full sync?

Reply
0 Kudos
ChrisAllwein
Contributor
Contributor

Hi,

1) I have gotten that solution. I didn’t realize that I could not perform a recovery in the WebClient if it was managed by SRM. That is working now that I understand it.

2) The other issue I’m having is still ongoing. I believe that the server is too large for the circuit. With the drives involved, it is over 2Tb, and is our production SQL database server, so it will change frequently, and I believe that the replication cannot keep up.

Chris

Reply
0 Kudos
Biliana
VMware Employee
VMware Employee

So, if you would like to recover using the Web Client, you should remove the VM from SRM protection group. Or you can recover it as part of SRM recovery plan. For the initial full sync still not complete, you could use initial seed file for the VM copied on the target site. That way VR will sync only the differences between source and target vmdk files and this will greatly speed up the initial full sync process.

ChrisAllwein
Contributor
Contributor

Thank you for the helpful advice.  I've been able to do successful test in the VSphere console, now that I know that if the SRM is managing the replication, then it has to do the recovery.  I had been just using the webclient to set up simple replication, and didn't know that I couldn't recover them if I had them set up in SRM as well.

It seems as though my problem server has completed the copy, it is just hung in sync status.  I dont' know that taking a copy to to the physical location will change anything.  If it wont' sync now, I'm thinking that it won't with a seed copy either.  Not sure if there is anything I can do about this.

Reply
0 Kudos
Biliana
VMware Employee
VMware Employee

You might also have a look at that thread: Re: SRM replication sync time

Reply
0 Kudos