How is the server moving from one data center to another?

Question

Data center

How is the move from one data center to another?

Let's say a server is rented in Germany, and you need to urgently transfer all the information to a more powerful rented server in a Russian data center.

Who knows, describe all the nuances of the move and who (what kind of person who can be hired) will be able to pull it all off?

Answer 1

It all depends on the amount of data, the server software, the type of your service..
1. First, transfer the data.
2.Set up the software on the new server in the same way as on the old one.
3. If stopping the service for some time is critical, you need to transfer databases with minimal downtime.
4. Depending on the time of the NS/ip update, you need to organize a remote connection to the database on the old service so that people can use your site during the ip update.

Answer 2

I can crank it))
My skype neo_new
Downtime will be equal to the speed of copying and deploying the database.
If desired, I can without downtime.

Answer 3

see what's going on there. if the site, then transfers the database to a new server, immediately build a remote connection to the database of the new server on the donor, transfers files to the new server, checks the correct operation on the new and old server. change A,MX to a new ip or dns (if the dns is someone else's) and wait 48 hours. after that, folding and renting the old server and enjoying the move. if anything else in each case you need to consider the logistics.

Answer 4

Everything is very individual.
1. Everything is copied.
2. The site address is corrected in the hosts of the admin's local computer. Checked.
3. The record is minimized (or the record in the database is completely disabled).
4. The database is copied again.
5. Changes IP in DNS.
But in this option, we don't know when users will migrate from the old site to the new one.
A more serious option - there are 2 versions of the site operating at the same time.
For example, http://new.mysite.ru and just http://mysite.ru.
From http://mysite.ru redirection to a new site is done.
Then DNS is applied.
In a few days, when the DNS bugs out, it is guaranteed for all users (you can see by attendance) it will be possible to kill the old site.
And you do a reverse redirect from http://new.moisite.ru to http://moisite.ru.
Third option:
The site is initially designed to work with server failures, CDN stuff, etc. Then turning off the server does not threaten anything at all.
I don't suggest database replication for the first and second options - it's too confused.