Know what the bundle can recover
A closed-Session guard is not a provider-wide orphan audit. Confirm the resources associated with the backed-up workload and retain unresolved records separately. Offline consistency also requires that no other process writes the selected database/settings while the backup is taken; stopping one launcher is not proof that every external writer is stopped.
Prepare an offline backup
Install pg_dump/pg_restore and select the correct DATABASE_URL/HEXAGON_DATA_DIR. Settle Runs, close every cloud Session with confirmed cleanup, and stop the local service. The implementation rejects running services, unclosed Sessions, and mismatched identity/decryption.Restore into a fresh target
Create an empty PostgreSQL database and an absent/empty data directory. Replace this illustrative connection with your dedicated target:Recover from an interrupted restore
The entire command is not one atomic transaction across PostgreSQL and the filesystem. A second attempt against a populated target is correctly refused. Do not delete that target as a generic retry step or start both old and restored deployments against the same remote resources.