Repositories

Managing backup repositories

A repository is a restic backup destination. Valvet manages repository configuration and provides tools for maintenance.

Supported Backends

Valvet supports all restic repository backends:

BackendPath FormatExample
Local/path/to/repo/backups/restic
SFTPsftp:user@host:/pathsftp:backup@nas:/repos/server1
S3s3:endpoint/buckets3:s3.amazonaws.com/my-backups
Rest Serverrest:http://host:port/rest:http://restic-server:8000/
B2b2:bucket:pathb2:my-backups:/server1

Creating a Repository

Navigate to Repositories → Add Repository:

  1. Name — Friendly identifier
  2. Type — Backend type (local, sftp, s3, etc.)
  3. Path — Backend-specific path
  4. Password — Encryption password for the restic repository
  5. Environment Variables — Additional env vars needed by the backend (e.g., AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY for S3)

The repository is initialized automatically when the first backup runs against it.

Repository Stats

The hub collects real storage statistics from repositories using restic stats --mode raw-data. Stats include:

  • Total Size — Actual storage consumed (after deduplication and compression)
  • File Count — Total number of unique files across all snapshots
  • Snapshot Count — Number of snapshots in the repository

Stats are collected automatically after each successful backup and can be refreshed manually from the repositories page.

Maintenance

Prune

Removes unreferenced data from the repository, reclaiming storage space. Run from the repository detail page or via the API.

Check

Verifies the integrity of the repository data. Detects corruption or missing data packs.

Both operations are dispatched to the node via WebSocket and run restic’s built-in maintenance commands.