Child pages
  • How to Migrate to another Server
Skip to end of metadata
Go to start of metadata

Introduction

In case you have grown out of your current dedicated server, needing a more powerful server to accommodate your new hosting needs. You will possibly want to migrate your existing data and configuration to your new server.

To summarize the process you will need to install an operating system and configure your new server. Then transfer your data between the two servers. And last either swap the IP addresses or change your DNS records.

Downtime associated with a migration, depends on your services and how they are set up. To avoid unnecessary downtime of your services, this page provides you with some guidelines and helpful tips to make the transition process as smooth as possible.

Plan the migration process

Migration process can differ depending on services and how they are used, we recommend that you make a plan of your migration process before you begin. This will help you to avoid unnecessary downtime of your services.

Prepare your new server, before migration

If you are going to transfer IP addresses between the two servers, make sure both servers belong to the same EasySpeedy Control Center dashboard. You can use the Move Server feature in your current Control Center to move servers between Control Centers.

Install your preferred operating system on your new server, and configure it with the primary IP address assigned to the new server (even if you are later going to swap the IP addresses).

Install your required services and firewall configuration.

Depending on what services you are using and how they are configured, it might be a good idea to copy the service configuration files from your old server and apply them on your new server. This could be an Apache virtual host configuration, SSL certificates, or other service configuration files.

Transferring your Data

If your are migrating a service where the data is ever changing, you can use a tool like rsync to copy and synchronize your data before you change to the new platform. Depending on your database platform there may also be some synchronization utilities available for your platform.

You can copy data directly over the Internet between the two servers. However if your servers are connected with Private LAN we strongly recommend using this instead, due to the higher bandwidth and security.

We encourage our customers to use encryption where available. For file transfers we recommend using SSH/SCP for encrypted file transfers between servers.

IP addresses and DNS records

Hosted services are typically tied to a domain name or record. Depending on how many services you are hosting on your server, and how often the server data is changed (e.g. databases) you may want to simply move the IP address from one server to another.

You are allowed to use IP addresses assigned to one server, on the other, when both servers belong to the same EasySpeedy Control Center. This way you don't have to change any DNS records, and have to deal with old cached records in DNS servers hours after you made the change.

Changing DNS records to another IP address may however prove useful in some scenarios, e.g. where only a few services are migrated to the new server. Or if you are not migrating all the services at once.

Swapping IP addresses

When both servers belong to the same Control Center you can freely re-assign IP addresses between them, by changing your network configuration on the server.

We recommend that you use KVMoIP while changing your servers network or firewall configuration, in the event that you lock yourself out of the server due to misconfiguration or otherwise unforeseen consequences. This will allow you to quickly either reverse the change or correct the problem.

E.g. when configuring the new server with the IP address of the old server. If you do this make sure that you either disconnect the old server, by closing the switch port in the Control Center, or configure the old server, with one of your other IP addresses.

If the new IP address assignment hasn't taken effect immediately, it could be due to ARP cache on the gateway router. To refresh the gateway ARP cache, you can use arping to send an unsolicited ARP reply to the gateway router to update its cache.

Example:

arping -A -s <SERVER-IP> -I eth0 <GATEWAY-IP>

Other versions of Arping may require you to swap the -s option with -S

 

 

When your IP addresses are replaced, please submit a Support ticket requesting us to re-assign the IP addresses inside your Control Center. That way you will make sure that if you cancel the subscription of the old server, the IP address is not removed from your account.

  • No labels