How do I migrate to another data center with no down time?
Linode
Linode Staff
I'd like to migrate my 4 Linodes from London to the Frankfurt Data Center.
I understand that my server will be powered down. But I want to know if
after the migration, the old server will be booted up, or if this is
possible at all.
I understand that the machine will be powered down during the time of
data-transfer. But I want to know if the 10-15 min per GB is for the
disk-images (25GB taking up to 6.2 hours) or for actual data on that
disk.
I understand that the IP will change. But I'd like to know if the old
machine, using the old IP will become available after migration, so that
I can change my DNS and complete the migration with no more downtime;
or
If I need to sync my DNS changes very closely to the migration; with
change of clients ending on the old, down, machine, whereas others may
end up on the new, not yet booted machine.
When I manage the migration myself can I keep old machines up while syncing the data/images? Then boot new machines while traffic is still directed at old machines.
1 Reply
asilverman
Linode Staff
Thanks for reaching out to us. From my understanding of what you are trying to do. You are worried about down time. Since you have Backups enabled there is a way to migrate the Linodes with almost no down time.
These Steps are Detailed Below
- You can take a manual snapshot of each Linode.
- Use that Backups image to create a new Linode.
- Request we can migrate those new Linodes to Frankfurt leaving the original in London by opening a Support Ticket in your Linode Manager.
- After the migration you can update your DNS settings with the new IPs.
- When the DNS records propagate you can delete the old Linodes.
Since we use hourly billing keeping both Linodes active for a few days will cost a couple dollars.
To answer your questions directly:
But I want to know if after the migration, the old server will be booted up, or if this is possible at all.
The old server is moved to the new data center and will not be available in London after the migration.
But I want to know if the 10-15 min per GB is for the disk-images (25GB taking up to 6.2 hours) or for actual data on that disk.
The copying of the disk is file based, so only the actual data on the disk.
I understand that the IP will change. But I'd like to know if the old machine, using the old IP will become available after migration, so that I can change my DNS and complete the migration with no more downtime; or if I need to sync my DNS changes very closely to the migration; with change of clients ending on the old, down, machine, whereas others may end up on the new, not yet booted machine.
The old machine will not be available. Because you will need to update your DNS settings to the new IPs. We can give you them when we schedule the migrations. But, DNS propagation sometimes can take up to 48 hours. I'm sure you want the sites up as soon as possible and there's no way to speed this up.
When I manage the migration myself can I keep old machines up while syncing the data/images? Then boot new machines while traffic is still directed at old machines.
We cannot keep the traffic pointed at the old machines once the migration starts. Since the Linodes will be powered down. Creating a Linode from the Backups image in the steps I stated above is best way to accomplish this. Since you will have redundant Linodes active.