Pular para o conteúdo
#0438
Containers

Move a customer across a border with a copy and a cutover

The customer's HQ moved from Austin to Dublin, and their legal team wants the data to follow by quarter end. On a shared database that's a migration project. Here it is three calls.

POST /api/v1/containers/{id}/copy with target_server_id set to the Dublin box. The copy carries the whole filesystem, the databases, the installed software, and the configuration, and starts on the new machine. Run it a week early, keep serving from Austin, then POST /sync the night before cutover to pull the incremental delta. Point the customer's domain at the Dublin alias. Delete the Austin container.

No export job, no schema drift between regions, no dual-write window. The customer's entire computer changed countries. Their domain didn't.

A jurisdiction move is a copy, a sync, and a DELETE.