Backup and Restore

Scope

Back up PostgreSQL, evidence storage, configuration required to rebuild the deployment, audit exports, license material required for recovery, and customer-controlled key references. Do not place private keys or plaintext secrets in an unencrypted backup.

Customer Recovery Objectives

The customer system owner approves RPO, RTO, retention, offsite-copy, legal-hold, and destruction requirements based on the business functions supported by the Workbench.

PostgreSQL

Use encrypted full backups plus WAL archiving or the customer database platform's point-in-time recovery.
Monitor backup completion and storage capacity.
Keep at least one logically or physically separate copy.
Restrict restore authority and record every restore.

pg_dump --format=custom --file=projectxit_workbench.dump "$DATABASE_URL"

createdb projectxit_workbench_restore
pg_restore --clean --if-exists --dbname=projectxit_workbench_restore projectxit_workbench.dump

Evidence and Configuration

Back up evidence storage with integrity metadata, deployment/.env through the approved secrets process, reverse-proxy configuration, certificate-chain material, license file, release manifest, SBOM, and customer operating records. Maintain the private keys separately under the customer key-management process.

Restore Test

Open a recovery ticket and record the approved restore point.
Restore into an isolated environment.
Validate database consistency, evidence hashes, application health, authentication, authorization, relationship maps, reports, audit history, and license validation.
Confirm no connector or notification can contact production unless explicitly approved.
Record elapsed time against RTO and recovered point against RPO.
Obtain customer owner approval and securely destroy the test environment.

Test restoration at least annually and after material architecture, database, storage, or backup-tool changes. Critical deployments should test more frequently.