Migrating a VPS Without Downtime — Replication, Cutover, Rollback

A cutover pattern that keeps the old server serving while the new one catches up: rsync replication, DNS/database switchover and a tested rollback path.

Le corps de l'article est en anglais. L'interface, le catalogue et la caisse sont traduits.

The pattern

Run old and new in parallel, replicate forward, switch reads and writes at the data layer, then retire the old box. Downtime lives only in the seconds between the final sync and the write switchover — not in a move-the-disk weekend.

Steps

1. Provision the target in the destination location; harden it with the same checklist.
2. Replicate data continuously (rsync over SSH, database replication, or application-level sync) until the delta is seconds.
3. Lower DNS TTLs to 60–300 seconds a day ahead.
4. Cutover: stop writes on old → final sync → point writes at new → smoke-test → let DNS converge.
5. Keep the old VPS alive for a rollback window; snapshot it before decommission.

Where NovaVPS fits

Snapshots on VPS/Storage plans make the sync-and-cutover pattern cheap: clone, verify, switch. Same no-KYC checkout on both sides of a migration — including moves from providers that want a passport scan for the destination.