Move a verified database copy to another region ​

Coordinator DB does not provide automatic multi-region replication. To move a dataset, create an independent database copy or export a defined set of rows, transfer it with your infrastructure tools, and validate the destination before directing clients to it.

Choose a transfer method ​

A local database copy uses the documented VACUUM INTO procedure and its restrictions. A logical transfer exports tables with explicit schemas and a supported interchange format. Record the moment or key boundary represented by the copy so users know which writes it includes.

Do not open the same database file from separate processes. Start the destination with its own file and listener addresses. Moving a file between hosts does not turn the two copies into synchronized replicas.

Plan the cutover ​

Decide how writes are paused or routed while the final copy is taken. Compare table definitions, row counts and representative values, then test the destination with the application's actual queries. Maintain a clear rollback decision before accepting new writes at the destination; later writes will not automatically return to the source.

Credentials, DNS and external transport protection need their own destination configuration. A successful file transfer alone does not prove SQL access or data completeness.

See database copies, local copy procedure and Parquet exchange.