ექსპლუატაცია6 წუთის საკითხავი
Moving a server without losing your players
Migrating between hosts or plans is mostly logistics. The order that keeps the world intact, the DNS timing nobody plans for, and how to make it uneventful.
ეს სტატია ჯერ ინგლისურადაა. ვთარგმნით.
A migration is not technically difficult. It goes wrong through timing: the world copied while it was still being written, or an address changed before anybody was told. Both are avoidable by doing the steps in a specific order.
The order
- Lower the DNS TTL a day in advance, so the change can propagate in minutes rather than hours.
- Set up the new server completely and start it once, with nobody connecting.
- Stop the old server. Copy the world only after it has fully stopped.
- Start the new one, verify with your own client, then change DNS.
- Leave the old server stopped but present for a few days rather than deleting it.
Copying a live world is the mistake
A world copied while the server is running is a copy of a file mid-write. It usually loads and it occasionally does not, and the failure appears days later as a specific area that crashes clients. Stop first; the five minutes of downtime is the cheapest part of the whole move.