Moving a large site. What are the ways?

Question

big data

Prehistory
In general, it has already grown to sites of 25 thousand uniques per day.
For me, this is the first such step in my experience (8 years). Before that, there were up to 1 thousand uniques per day. There were more sites when I worked in Beeline (e1.ru, local.beeline.ru, beeline.ru), but system administrators did this. Now the question is for me. We don't have a sysadmin. I am confident in my abilities. I'm interested in the question in advance. Task start date is more than 1 month later.
Task.
The task was to support a large site on Bitrix. 25 thousand uniques per day.
The first task is to transfer to another hosting. Base 700 mb. Files over 40 GB.
Please share your stories of studying this issue. Please share links to articles on this issue.
And I went to flip through Google on this issue.
At the moment I see the following. Files, the whole list, I upload to git. along with the base. After uploading to a new hosting, I deploy the database.
Not entirely sure about the correctness of this solution.

Answer 1

To choose the right strategy for migrating a site to another server, first of all, you need to decide whether it is allowed to disable write / update operations in the database during the transfer of the resource, i.e. actual simple? Let's assume that we have started the transfer of a loaded online store, where every three minutes there is an order. If you stupidly take a database dump, make a file archive, overtake it to another server, deploy the whole thing, then the time lag will be at least 30 minutes, even if the new piece of iron is in the same rack. While the transfer is taking place, new orders will already be recorded in the old database. As an option, it is possible to prohibit the creation of orders and users during the migration, but business does not like a simple 30 minutes (and actually 2 hours), therefore, seamless relocation is practiced on large projects - first, a balancer is installed,cloud . As a result, we get the classic master-slave model. In the end, we change the roles in the database, make the new one the master, and the old one the slave. Shutting down the old server.

Answer 2

The base and most of the folders - with regular Bitrix backup tools, except for the upload folder and other heavy folders with static - they can be done using rsync.

Answer 3

> Files, the entire list, uploading to git. along with the base.
Your confidence is failing you. A real pro is never confident in his abilities.
In this case, the idea is very harmful and unnecessary. Use RSYNC.

Answer 4

The easiest way is a regular backup tool. Your 40Gb is most likely /upload - it's easy to skip it when backing up. And then rsincom, well, or through git it.

Answer 5

I don’t know what others in the answers mean by standard means, but since the version of Bitrix and its environment is not indicated in the task, we go from the most unpleasant and you need to use this script or any other analogue: dev.1c-bitrix.ru/ community/blogs/howto/945.php It
is undesirable to use the regular tool from the admin panel, it is more reliable to make backups using the server tools.

Answer 6

The transfer was performed by the following steps:
1. made a copy from a live site via rsync to a new one.
2. made a database dump from a live one to a new one.
3. deployed on a new one. configured.
4. sent the new.site.ru subdomain to the new server
5. tested the operation of the new server
6. put a stub on the old server (by renaming the document root folders)
7. extinguished the database. made a dump.
8. rsync updated the new server
9. updated dns.
it was updated overnight and in the morning users logged into the new server
Are there any wrong steps in my list? 1.2 point was filmed live without stopping.

Answer 7

"I put a stub on the old server (by renaming the document root folders)" - good afternoon - please comment on the procedure - in the process of performing a similar task.