Skip to main content
Application backup creates a PostgreSQL dump, artifact copy, schema/deployment metadata, and checksum sidecar. Restore verification uses a throwaway pgvector container and never changes live state. Phase 6 recovery checked an active record and a document original checksum; Phase 4 recovery checked active and superseded learning lineage. Backup and recovery topology showing an isolated application archive, off-host copy, throwaway restore target, and separate Basic Memory store. Basic Memory is backed up and restored independently. Application backups exclude its development store, and D10/D11 demonstrated that application lifecycle operations did not silently modify it. A same-host copy does not protect against host loss. The initial off-host destination is identified and used for recovery evidence, but its BitLocker at-rest-encryption state is not verified. See backup/restore operations.