How to do a Server Migration

There are very different reasons for trans­fer­ring data to a new server. In most cases, mi­gra­tions take place because more capacity is needed. If the hardware can no longer meet the re­quire­ments and an upgrade is not possible, there is no al­tern­at­ive but to relocate to a new server. Vice versa, it makes sense to migrate your data to a smaller server if the available computing power exceeds the amount you require. This is mainly due to the cost factor, which is often why people change their supplier.

If you rent your server resources, you might not look ex­clus­ively at the costs for the re­spect­ive hosting service. The contract con­di­tions can also be a reason for migrating servers. The various packages from providers differ in what they offer i.e. avail­ab­il­ity, data security, and support. Therefore, it makes sense to compare the different packages before making your selection. Another reason for migrating data could be that you want to take some pressure off your IT de­part­ment. In this case, a managed server solution would be a good choice. It isn’t only hosted, but also main­tained and updated by the provider.

To make the con­fig­ur­a­tion and in­tro­duc­tion of the new server as simple as possible, it makes sense to tidy up the server you’re currently using. Therefore, data migration is the optimal time to delete any redundant or outdated pages, back-ups, e-mail accounts, and user accounts. This means you reduce the amount of data you’re trans­fer­ring to a minimum and, on the other hand, you obtain greater value out of the required resources on the target system.

In addition, you should develop an accurate schedule for shutting down the active server processes so that no com­plic­a­tions occur later with the result of data being lost. Specify a time at which any changes to files, scripts, and con­fig­ur­a­tions should be stopped, and tem­por­ar­ily block access to your databases, if possible. It’s also possible to update your database later. In most cases, the data transfer takes place by means of a complete server backup (which you should also carry out if you are aiming for a different migration strategy).

The easiest way to migrate your data is to use a one-to-one copy of the actual state. You transfer this to the new server hardware before you make necessary con­fig­ur­a­tions and ad­just­ments and then you can test if it works. Finally, you can adjust the DNS or IP settings, which will allow you to start your web project live on the new system. Although this approach usually requires the support of system ad­min­is­trat­ors, it is easy to plan and execute. However, it means the current server will be com­pletely suspended and you won’t be able to access or use your website for the duration of the data migration. If you offer a service that requires constant database access, you need a hybrid migration solution that keeps the current server active. In this case, you should declare the current database on the server as 'master', which then sub­or­din­ates the new database to 'slave' once the con­fig­ur­a­tion is complete. This enables the two ap­plic­a­tions to syn­chron­ise in real time. If both databases are in the same state, reverse the roles so that the new database becomes master. This means that your project can continue being available during data migration. In addition, this strategy offers the pos­sib­il­ity of you always being able to access the old database (which still has the current data), if the new server is ex­per­i­en­cing com­plic­a­tions. In order to test the func­tion­al­ity of a web or ap­plic­a­tion server without having to switch off the old version, you can use a load balancer: by first re­dir­ect­ing the traffic of your web project to the new server, you will see if it is properly con­figured and works as desired. Once again, you benefit from no downtime and can therefore rest assured.

There are several tools and services available that simplify server migration. For example, if you want to simply move your data without having to adjust the operating system or other software, you shouldn’t forgo a control panel. Server man­age­ment pro­grammes like these help you create backups of your data and then migrate them to the new server. The required con­fig­ur­a­tion effort is minimal. Content man­age­ment systems such as WordPress can also be trans­ferred using simple FTP and backup ap­plic­a­tions, and often offer their own plugins for migrating the linked database. These automate the process for the most part.

For more complex projects, root per­mis­sions always pay dividends: via SSH, you can transfer complete databases, including all per­mis­sions and user data, to a new server via the re­spect­ive command line. For example, you can use MySQLdump to send MySQL databases to the target system as a copy. As a Microsoft SQL server user, you can even use the built-in functions for this purpose.

However, you can also outsource the migration of your server data: many hosting providers offer their customers not only specific software for manually per­form­ing a server data transfer, but also offer to actively support the data migration. Fur­ther­more, there are also services that spe­cial­ise in the migration of web projects and provide a round-the-clock service – whether it’s a simple switch from one shared server to another, you’re changing your provider, or you plan to switch to a server cluster.

Importing images

After you have created an image of the output server, you can use it to create a new server with the same database. To import your server image in the Cloud panel, go to 'In­fra­struc­ture' à 'Images' section of the Cloud panel.

1. To migrate data to the new server using an image, first click the 'Create' button and give an ap­pro­pri­ate name to the copy that’s in the panel.
2. Select the 'Import image' option and specify the operating system of the server image in the 'Operating system' field.
3. In the 'URL' field, copy the address of the location where the image file is stored.
4. In the advanced settings, you can finally enter the data centre of your choice in the 'Display' section.
5. Click on 'Create' to start the import process.

3. The next field is where you specify the URL under which the ISO image is to be down­loaded.
   
   
4. Under 'Ad­di­tion­al Settings', you can now select the required data centre by clicking on 'Display' before you start importing the ISO file after clicking on 'Create'.