Verify an Existing Replica

Restore and check your own Litestream replica before signing up.

Run it locally

With the borela-agent binary installed, point verify at an existing file:// or s3:// Litestream replica. No Borela account, API key, or source database file is required. The command restores the latest available state into a private temporary directory, checks SQLite integrity, counts application tables and rows, prints the evidence, then removes the temporary file.

borela-agent verify -replica-url file:///srv/litestream/app.db

What the result means

A passing result proves this replica restored and passed PRAGMA integrity_check at the time shown. It does not measure when your app last committed a transaction or guarantee a recovery-point objective. Compare application data before relying on it for an incident.

Use --json for machine-readable output. If you already have a Borela recovery config, use -project NAME -config PATH instead of -replica-url.