Module backup 

Online backup manifest and verification.

The manifest audit fields (Stage 1G, spec section 10.7) are additive and every one of them defaults, so backups written before Stage 1G still deserialize and validate unchanged: database_id/encryption decode as None, and catalog_version, snapshot_unix_micros, and open_generation decode as 0 (“unknown”). Conversely, pre-1G binaries ignore the new keys because the manifest never denied unknown fields.

Structs

BackupEncryptionMetadata

Encryption metadata recorded in a backup manifest (Stage 1G). The KEK salt itself travels inside the backup as the _meta/keys file, so only the scheme identifiers live here.

BackupFile

BackupManifest

BackupReport

RestoreReport

Outcome of a post-restore validation pass (Stage 1G, spec 10.7), in the idiom of crate::gc::CheckReport/crate::gc::DoctorReport: soft findings collect in issues, hard corruption returns Err.

Constants

BACKUP_FORMAT_VERSION

BACKUP_MANIFEST_PATH

Functions

validate_restore

Post-restore validation pass over a backup or restored database tree: re-verifies the manifest, every listed file size/hash, and the manifest/ file-set equality, then loads the catalog. Row counts are intentionally out of scope: opening the tree as a database would take its lock and bump its open generation.

verify_backup

Verify a backup manifest, every listed file size/hash, and the catalog.