How to Self-Host Backrest
Backrest web interface and scheduler for Restic backups with snapshot browsing, restores, retention policies, health checks, hooks, and notifications. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Backrest is a good fit
Choose Backrest when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Install the standalone binary or official container, keep the web interface private, and connect only the source paths and Restic repositories it needs.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up the Backrest configuration separately from the Restic repository and schedule both repository checks and real restore drills.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
A green backup job is not proof of recovery; restore representative files on a schedule and protect repository passwords outside the UI.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
