Operators

Backup and recovery

Create manual backups, verify regional availability and PITR, and run recovery drills without using client credentials.

Create a manual backup

shell
PROJECT_ID="<gcp-project>" deploy/gcp/backup.sh

With the Cloud SQL backend, this creates a managed on-demand backup. The script detects the deployed backend before choosing its backup path.

Verify protection

Confirm all of the following before a production release:

  • Cloud SQL state is runnable.
  • Availability type is regional and a secondary zone is present.
  • Automated backups are enabled.
  • Point-in-time recovery is enabled.
  • The broker readiness endpoint returns HTTP 200.

Run a recovery drill

shell
PROJECT_ID="<gcp-project>" deploy/gcp/recovery-drill.sh

Recovery drills may take several minutes while Cloud SQL creates and verifies temporary resources. Keep the command attached until it reports success or failure, and verify temporary resources are cleaned up.

Local fallback

LIVEPROBE_STATE_FILE remains a local and development fallback when DATABASE_URL is unset. The resource catalog, self-service service credentials, and durable audit store require PostgreSQL and return an unavailable error on JSON fallback.