Comprehensive data protection for all workloads
Post Reply
bproteau
Influencer
Posts: 23
Liked: never
Joined: Aug 11, 2011 6:57 pm
Full Name: Brian Proteau
Contact:

Replication for migration methodology

Post by bproteau » Aug 16, 2011 3:01 pm

I'm trying to deterine a methodology for cutovers from one datacenter to another. We are using the same IP for source and destination so we can't have them powered on at the same time. My thought was to:

(a) Decrease the replication job interval as I get closer to the cutover (down to say 5 minutes a few hours before the cutover)
(b) Power down the source VM and run the job one last time.
(c) Power on the source

I've been testing with a transactional DB and although each pass seems to be quicker and shorter, it's still taking about 30 minutes. I'm considering a continuous replication when applicable but, I'm trying to work out what my cutover process would look like. If I power off the source while the continuous replication job is running, what will be the indication that I'm completely synchronized? Would I stop the job and run it normally one last time?

I'm trying to get a sense for downtime requirements to set expectations.

Vitaliy S.
Product Manager
Posts: 22445
Liked: 1443 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Replication for migration methodology

Post by Vitaliy S. » Aug 16, 2011 4:42 pm

If you want to be completely synchronized between two datacenters, you need to run replication job while source VMs are powered off. This process relates to both cases: jobs with continuous replication and not, so your initial plan looks good to me.

bproteau
Influencer
Posts: 23
Liked: never
Joined: Aug 11, 2011 6:57 pm
Full Name: Brian Proteau
Contact:

Re: Replication for migration methodology

Post by bproteau » Aug 16, 2011 8:49 pm

That's what I figured but, I wondered if (after powering off the source), I could tell if the server was synchronized with a "continuous" job (i.e. would there be an indication that the final deltas had been committed or will I be staring at this job that would run indefinately no longer sending changes. That was my question about whether I ned to stop the continuous job and run a standard job.

Only reason I would consider a "continuous" type job is if it somehow made that last pre-cutover replication faster. I plan to test the theory but wondered if anyone had some insight. Below is a test job I scheduled to run over and over again.

This particular VM has a pretty active transactional DB on it which I assume explains the relatively long replication times. I seem to be leveling out to 20-25 minutes. Is this way off or does it sound right? Environments are ESXi to ESXi which I've heard doesn't perform as well as ESX. (NOTE: Initial replication job obviously took much longer and is not refelcted here).

Start Time End Time Job Session Performance Rate Transferred Data Status
8/16/2011 14:37 8/16/2011 15:05 Replication Job 1 123 MB/s 200.00 GB Success
8/16/2011 14:12 8/16/2011 14:36 Replication Job 1 140 MB/s 200.00 GB Success
8/16/2011 13:49 8/16/2011 14:11 Replication Job 1 151 MB/s 200.00 GB Success
8/16/2011 13:26 8/16/2011 13:48 Replication Job 1 154 MB/s 200.00 GB Success
8/16/2011 13:04 8/16/2011 13:25 Replication Job 1 163 MB/s 200.00 GB Success
8/16/2011 12:35 8/16/2011 13:03 Replication Job 1 121 MB/s 200.00 GB Success
8/16/2011 11:55 8/16/2011 12:23 Replication Job 1 123 MB/s 200.00 GB Success
8/16/2011 10:55 8/16/2011 11:28 Replication Job 1 106 MB/s 200.00 GB Success
8/16/2011 10:02 8/16/2011 10:28 Replication Job 1 133 MB/s 200.00 GB Success
8/16/2011 9:03 8/16/2011 9:36 Replication Job 1 105 MB/s 200.00 GB Success
8/16/2011 7:51 8/16/2011 8:43 Replication Job 1 66 MB/s 200.00 GB Success
8/15/2011 13:31 8/15/2011 15:27 Replication Job 1 29 MB/s 200.00 GB Success
8/15/2011 10:16 8/15/2011 12:23 Replication Job 1 27 MB/s 200.00 GB Success

Gostev
SVP, Product Management
Posts: 24092
Liked: 3280 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Replication for migration methodology

Post by Gostev » Aug 16, 2011 9:07 pm

Yes, looks normal for ESXi target and v5.

Post Reply

Who is online

Users browsing this forum: No registered users and 19 guests