Backup and recovery

Back up the whole state

Use PostgreSQL-consistent backups that include registry entries, immutable history/audit/event records, session/challenge state, transfer offers, and anchor outbox. Preserve protected configuration and signing material through the operator's secret-management process; never bundle secrets into documentation artifacts.

Verify ledgers

The real mars-ledger binary requires the postgres feature. With DATABASE_URL supplied securely:

mars-ledger verify

It verifies complete private-audit and public-event hash chains and returns JSON containing status, record counts, and head hashes. A connection or chain verification failure is an error, not an empty healthy chain. --max-connections defaults to 4.

Restore procedure

Restore into an isolated environment, verify the chains, inspect migration compatibility and outbox state, and validate readiness before accepting traffic. Reconcile uncertain external anchor intents with their recorded receipts before retrying. Operator retry/abandon endpoints require explicit admin authority and idempotency.

This page documents the recovery interface; no database restore or backend certification was performed by building this website.

Source authority

This page describes the checked-in implementation, not the availability of a public registry.

• mars-server/src/bin/mars-ledger.rs
• mars-server/src/store/postgres.rs
• mars-server/src/main.rs