Comprehensive data protection for all workloads
ferrus
Veeam ProPartner
Posts: 299
Liked: 43 times
Joined: Dec 03, 2015 3:41 pm
Location: UK
Contact:

Re: Using Veeam replication to Migrate Datacenter

Post by ferrus » 1 person likes this post

We're just about to complete a staged 350 VM migration between Datacentres (and ESX versions), using Veeam replication.
I can't say specifically if it's the best option for your environment, but for us it worked perfectly. Difficult to think how we would have managed it without.

We moved one of our EMC Data Domains to the new DC, and used the nightly Backup Copy Jobs from that, to seed the VMs.
Then ran replication updates overnight for each server.
That step isn't required, but cuts down significantly on the preparation stage.

On the day of each migration, we ran the Replications Jobs to run continuously, so the delta was as small as possible.
When each migration window arrived, we powered down the VM, did a final replication with the VMs powered off - while our Comms engineers migrated the VLAN/IP range.
The VMs could then be powered on at the new DC with the original IP config, and the VMware HW and tools versions updated.
There was very little downtime, but obviously this wouldn't be suitable where zero downtime is required.

Think the only real issue related to Veeam that we faced was a recurring invalid CBT data bug on one file server which caused a digest recalculation every night. Eventually we spun it off onto its own replication job, wiped the destination VM and restarted to fix.

Extending drives on the source VM, also causes a digest recalculation (a colleague has just done this, this morning - right before the final migration :x ).
So remember an embargo on that before migration dates.
TinchoB
Enthusiast
Posts: 29
Liked: 3 times
Joined: Nov 17, 2020 9:49 pm
Full Name: Martin B
Contact:

Re: Using Veeam replication to Migrate Datacenter

Post by TinchoB »

Hello,
at this moment we are implementing VEEAM as the backup solution for a VMWARE environment of 35 Windows VM.

In some months we would have to move to a new site. The business do not tolerate to get off-line so we have to find a way to migrate (virtual and physical) without down time.
Both site are quite close (2kms away) and will plan to have a temporary LAN to LAN 10G fiber link with VLAN trunking. We are planning to put in advance two VMWARE hosts with a SAN Storage in the remote location, in order to have a "container" to migrate first batch of production VMs to the new site. All hosts (local and remote) managed by one vCenter instance. As the VMs of each VMWARE hosts in the old location are migrated, those "empty" servers will be one by one moved physically to the new site to get more remote resources. The LAN to LAN link will be used for the migration of the VMs but also for production traffic vlans (al least until we can move our users and the main internet access to the new site).

Do you think we could just use vMotion to safely achieve our goal or should we use VEEAM Replication or Quick Migration ?

Regards,

Tincho
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Using Veeam replication to Migrate Datacenter

Post by foggy »

Hi Martin, for a minimum and more controlled downtime, you need to use replication with the planned failover.
TinchoB
Enthusiast
Posts: 29
Liked: 3 times
Joined: Nov 17, 2020 9:49 pm
Full Name: Martin B
Contact:

Re: Using Veeam replication to Migrate Datacenter

Post by TinchoB »

Hi Foggy,
just to better understand your recommendation, don´t you think vmotion could handle it without service interruption over LAN to LAN ?

If using "planned failover":
The replicated VMs in the new site will have new VMWARE names and id ? (think we are using same vCenter instance).
What will happen with the Backups chains ? VEEAM will see these replicated VMs as new ones with no connection to backups it has of the source VMs in the old site ? Will it be a new instance ?
How much time will it take between the shutdown of the old VM and the power on of the remote one ?

Thanks !
Mildur
Product Manager
Posts: 8549
Liked: 2223 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Using Veeam replication to Migrate Datacenter

Post by Mildur »

Replicated VMs have always new ids. Name can be configured, id will be new.
Veeam will see the vm as new ones and a new chain has to be generated by the backup job.

Old vm will be automatically excluded from backup job if you are doing a permanent failover after your planned failover.

Time: It depends on your infrastructure and last changes, which has to be replicated. I have seen in my Environments failover times between 5-30 Minutes.
Product Management Analyst @ Veeam Software
foggy
Veeam Software
Posts: 21069
Liked: 2115 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Using Veeam replication to Migrate Datacenter

Post by foggy »

Unlike vMotion, replication with a failover allows you to fail back in case something goes wrong. Downtime will minimal due to the final sync that copies only the changes since the last replication run.
Post Reply

Who is online

Users browsing this forum: ThomasIkoula and 163 guests