verify

Verify integrity of blobs on the configured backend

Usage

aegis verify [OPTIONS]

Options

Option	Description
--repo	Specify a path to a repo to use instead of the current working directory
--backend	Use a specific backend instead of the one specified by default_backend in aegis.toml
--snapshot	A query specifying the snapshot to use. This can be "latest", a snapshot root checksum, or an index number. Use aegis list-snapshots --backend {backend name} to get checksums/indexes. (default: latest)
--num-verify-threads	How many threads to use for verification (default: 3)

Description

The verify command downloads and re-checksums every blob referenced by a snapshot. This can detect bit rot of your data on a given backend.

Examples

# Verify Latest Snapshot
aegis verify

# Verify a Specific Snapshot
aegis verify 3

# Verify on a Specific Backend
aegis verify --backend cloud

Output

Success:

All blobs validated successfully!

Failure:

Blob abc123...:
  Found at: /documents/report.pdf
  Invalid checksum!

1 blob(s) failed to validate!

Performance/cost considerations

Verification requires downloading all data, so it can be slow for large backups, and can be costly if verifying a backend that charges for download bandwidth.