Which snapshot belongs to the Friday edition if several servers use one repository?
restic/restic
restic creates encrypted, deduplicated file snapshots. A web operations team can rehearse recovering a particular edition of a site in a clean directory before agreeing to a cutover.
Public GitHub facts reviewed Nov 22, 2026. Independent editorial profile; not a sponsored entry.
How is the score calculated?
Calculated on 22.11.2026. Missing public information receives no points. The index does not establish code quality, security, fitness, or future visibility.
What can restic help with?
Rehearse a newsroom rollback
Put a sample headline and a harmless image in a test site directory. Back it up to a disposable repository, change the headline, and back it up again. Record the first snapshot ID with the edition you intended to retain.
Time a recovery check
Restore that ID into an empty staging directory using restic -r REPO restore ID --target TARGET. Record elapsed time and inspect the headline and image. Repeat from the credentials and machine available to the on-call editor.
Questions people ask before using restic
Which snapshot belongs to the Friday edition if several servers use one repository?
In the snapshots listing, narrow the candidates by host, source paths and timestamp. Match an edition marker inside the selected snapshot to the release log. Save the resulting ID so a later backup cannot change the choice.
How can I preview what a restore will put in my staging folder?
Pick an empty target and run restore with the selected ID, --dry-run and --verbose=2. Check the displayed directory structure and the paths being included. Remove the dry-run option only after confirming the destination.
Why can the uploads folder come back intact while an article points to a missing image?
The database and filesystem may represent different moments. Restore the matching database export into an isolated instance, open the test article, then compare its media reference with the recovered path. Plan a consistent capture step if they disagree.
How do I recover one image without replacing the live copy?
List the snapshot with restic ls to identify the recorded pathname, then select that path with --include during restore. Use a separate target directory. Open the recovered image and compare its digest with your fixture before copying anything elsewhere.
What proves our on-call editor can actually recover a file?
Have the designated operator access a test repository using the documented recovery credentials. Record which snapshot they used, when the file became available, and whether it matched the expected contents. An automated backup-success email covers a different step.
How do transferred bytes differ from the size of the source folder?
restic can reuse data blobs already present in the repository. Changes, prior backups and compression affect the added data. Read the backup summary and measure stored size and transfer costs at the backend separately before sizing the next run.
Can a quick repository check establish that all stored bytes can be read?
The ordinary check focuses on repository structure. Add --read-data for a complete data read, or plan documented subsets. A small random sample can miss a damaged pack and says little about the time needed to restore the entire site.
What if one backup file was unreadable but a snapshot still appeared?
Inspect the command exit status and the names reported in its output. Look up the specific fixture in the snapshot. Resolve the file permissions through the responsible operator, then run a fresh capture and test the missing item.
Which capability do we lose if the only copy lives in our collaboration server?
A synced folder is useful for editors to exchange changes. If access to the entire server is lost, recovering that folder may depend on the same unavailable system. Rehearse retrieving a separate snapshot using a different machine.
Does the project license also cover the site's photographs?
BSD-2-Clause applies to the covered restic software. The repository's copyright and redistribution terms do not grant republication rights to backed-up media. Keep asset licenses and software notices with their respective records.
What to check before adoption
- Primary language
- Go
- GitHub license field
- BSD-2-Clause
- License according to repository file
- BSD-2-Clause · LICENSE ↗
- Stars / forks in this snapshot
- 37,359 / 1,991
- Last code push
- 21.11.2026
- Self-hostable
- Potentially, verify operating requirements
Reading one snapshot does not establish the recovery time for a whole site. Keep database exports, runtime configuration, DNS, and the ability to regain access to storage in the recovery plan.
Comparison and original sources
Compared with server Nextcloud supports a shared workspace. A restic drill tests retrieval of a specific captured version after losing access to the working copy.
Documentation and repository data
Compare related projects
A local runtime for running selected language models on your own hardware.
GitHub snapshot 11.11.2026 · Score method on profile
A collaborative workspace for notes, projects, wikis, and team knowledge.
GitHub snapshot 11.11.2026 · Score method on profile
A scanner for vulnerabilities, configuration issues, and exposed secrets in software artifacts.
GitHub snapshot 11.11.2026 · Score method on profile
Back to Open Source Radar
Explore more projects by job, technology, and license.