CloudEndure continuous data replication not working

[Rob Dejournett]

Hi, so I migrated a Windows Server 2008 to GCE using CloudEndure.  This is to be a backup server of prod.  The hope is that it is continuously syncing with our prod server (which is a physical box hosted by rackspace).  

But I notice that the database transactions are 3 days old, and nothing from today.

ie this SQL:

select * from elg_data where created_on > '4/10/2017' order by created_on desc

Gives 1000 records in the backup server on GCE, but 30,000 records in real prod.

I'm at the "testing" step in GCE - in CloudEndure it says under status "Machine can be cutover / tested".  I select the machine and click the "test" button, then the VM is displayed in GCE. 

I guess I'm confused about Test vs Cutover.  Is the sync only working when "cutover"?  Or how does it work?  Where can I look to see why the sync stopped? 

[Brian Stark]

Hi Rob!

Thanks for reaching out.  The machine should not be 3 days out of sync .  Testing and Cutover should be independent of the syncing.  Did you change any network configuration on your side after the initial sync.

Adding Leonid from CloudEndure to comment as well.

Best,

Brian

Brian Stark |

Product, Google Cloud Platform |

bhs...@google.com |

+1 (415) 298-7808

 

--
© 2017 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussion+unsubscribe@googlegroups.com.
To post to this group, send email to gce-discussion@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gce-discussion/cc387758-1169-40ad-89bc-a3ff0d79883e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Leonid Feinberg]

Hi Rob,

Glad to help!

Two questions:

1. When did you issue the Test? Once a VM on GCP is launches, it starts its own life and is no longer in sync with the source machine. Replication is still taking place, but into a separate set of disks which will be used next time you click on Test or Cutover.

2. What does it say in the Lag column of this server in the migration console?

On 13 Apr 2017 4:50 p.m., "Brian Stark" <bhs...@google.com> wrote:

Hi Rob!

Thanks for reaching out.  The machine should not be 3 days out of sync .  Testing and Cutover should be independent of the syncing.  Did you change any network configuration on your side after the initial sync.

Adding Leonid from CloudEndure to comment as well.

Best,

Brian

Brian Stark |

Product, Google Cloud Platform |

bhs...@google.com |

+1 (415) 298-7808

 

On Thu, Apr 13, 2017 at 8:47 AM, Rob Dejournett <rdejo...@gmail.com> wrote:

Hi, so I migrated a Windows Server 2008 to GCE using CloudEndure.  This is to be a backup server of prod.  The hope is that it is continuously syncing with our prod server (which is a physical box hosted by rackspace).  

But I notice that the database transactions are 3 days old, and nothing from today.

ie this SQL:

select * from elg_data where created_on > '4/10/2017' order by created_on desc

Gives 1000 records in the backup server on GCE, but 30,000 records in real prod.

I'm at the "testing" step in GCE - in CloudEndure it says under status "Machine can be cutover / tested".  I select the machine and click the "test" button, then the VM is displayed in GCE. 

I guess I'm confused about Test vs Cutover.  Is the sync only working when "cutover"?  Or how does it work?  Where can I look to see why the sync stopped? 

--
© 2017 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043
 
Email preferences: You received this email because you signed up for the Google Compute Engine Discussion Google Group (gce-discussion@googlegroups.com) to participate in discussions with other members of the Google Compute Engine community and the Google Compute Engine Team.
---
You received this message because you are subscribed to the Google Groups "gce-discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gce-discussion+unsubscribe@googlegroups.com.

To post to this group, send email to gce-dis...@googlegroups.com.

[Rob Dejournett]

Okay so that's the question, I launched the target machine and expected it to be constantly in sync (I didn't understand how it works).  I tested it 3 days ago.

It does say Lag - 0.

Thanks!

--

Robert Dejournett, PhD
PhD Computer Consulting
Cell: 919-599-9369

[Leonid Feinberg]

Thanks for the clarification.

To have all the transactions from the last 3 days present in the target machine, you'll need to launch another Test. This will delete the previous target machine and will create a new one that will include all those transactions.

Also, please note that each machine can only be replicated for 3 months. After that period, no Test or Cutover jobs on the machine will work.

--

Leonid Feinberg  | VP Products | CloudEndure™ - All Systems Go.™
Israel: +972 (3) 5277367 x010 | US: (650) 360-0717 | www.CloudEndure.com

[Rob Dejournett]

Okay thanks.  I'm looking to see if there is any technology that will allow continuous data replication.  Any ideas?  It seems like I will have to do SQL database mirroring.

[Brian Stark]

are you looking for an active-active DB technology or DR.

CloudEndure is a nice DR solution; you'll need something else for active-active.

The DR portion of their product is not included in the migration service

Brian Stark |

Product, Google Cloud Platform |

bhs...@google.com |

+1 (415) 298-7808