vSphere Replication

 View Only

  • 1.  Replication for recovered virtual machine

    Posted Jun 14, 2013 04:30 PM

    Hi,

    I am new to Vmware Replication. We are using replication (not SRM) 5.1 between two sites (A & B). Email Server is running on Site A and replicating on Site B. Recently due to crash of the Email Server, we have recovered the VM in Site B using vSphere Replication. Now, in vSphere replication console , under Outgoing Replications we have found the status of the Mail Server replication as "Recovered" and none of the options was highlighted other than "Stop". I have the following queries

    1) If I click Stop, what will happen?

    2) What i have to do if i want to continue the replication?

    Please find the attachment also



  • 2.  RE: Replication for recovered virtual machine

    Posted Jun 14, 2013 06:55 PM

    Hi ,

    Check out the stop option in vSphere replication

    Stop vs Pause with vSphere Replication | VMware vSphere Blog - VMware Blogs

    Regards

    Mohammed



  • 3.  RE: Replication for recovered virtual machine

    Broadcom Employee
    Posted Jun 14, 2013 08:05 PM

    The Stop action will remove the replication entry from your list and nothing more in your case. At this point no deltas is transferred from site to site B. Since the mail server has run for some time there is difference between what you have on site B and on site A.

    What you can do is to configure a replication from Site B to site using the source VM on site A as a initial seeds (http://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.replication_admin.doc%2FGUID-C7CD1006-7E2F-42B3-A3EC-429F365140E1.html

    Once you do that you will sink sync data to site A and code do recovery on Site A and start using it from there.

    hope this helps



  • 4.  RE: Replication for recovered virtual machine

    Broadcom Employee
    Posted Jun 20, 2013 04:08 PM

    Once a VM is recovered the replication is no longer taking place as there is no primary any more.  Well, technically the secondary has become the primary.

    So the configured replication is no longer valid, meaning you need to "stop" the replication, and reconfigure it to get it started again.

    ExchangeA stopped, ExchangeB started, right?  So now ExchangeA is offline, so the replication is no longer valid.

    With ExchangeB running, "stop" the replication, then reconfigure it from scratch.  In essence you'll be configuring a 'new' replication from ExchangeB back to your primary site.  You can use the old ExchangeA as your replication seed if you like to reduce the amount of data to be transmitted.

    Basically, after recovery, there is nothing else you can do other than stopping the old replication and reconfiguring it from scratch.