restic
Fast, secure, efficient backup program
Runssource: GitHubhomepageGoBSD-2-Clausecommit 6adedec6b48a
Go, BSD-2-Clause licensed. The project labels itself: backup, dedupe, deduplication, go, restic and secure by default.
restic runs. An Argusic agent installed it in 8.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
restic 0.19.1-dev builds cleanly, the binary compiles and runs, backup/restore works on the local backend with end-to-end verification, all 52 test suites pass, except 2 mount-integration tests that require /dev/fuse which is unavailable in this unprivileged container
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Go compiler not found in container0.5 minutes
- fusermount binary missing; mount tests cannot run0.3 minutes
- python (not python3) required by TestStdinFromCommand tests0.2 minutes
- Install time
- 9 minutes
- Cold machine to finish
- 9 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- go test -count=1 -run 'Test[^M]|TestM[^o]' ./cmd/restic exited 0 (6.8s). End-to-end: restic init --repo /tmp/repo -> created repository, restic backup /tmp/src -> snapshot saved, restic restore latest -> restored file contents matched original. Binary: /tmp/restic version printed 'restic 0.19.1-dev (compiled manually) compiled with go1.27.1 on linux/amd64'
- Model tokens used
- 238,979
- Exact commit tested
- 6adedec6b48a
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
/bin/sh -lc 'echo "elapsed_seconds=$(( $(date +%s) - 1790342100 ))" && echo "minutes=$(echo '"\\\"s… succeeded in 0ms: elapsed_seconds=512 /bin/sh: 1: bc: not found /bin/sh: 1: 512: not found minutes="scale=1 exec /bin/sh -lc 'export PATH="/home/runner/bin:$PATH" && export PATH="/tmp/go-install/go/bin:$PATH" && … succeeded in 8912ms: ok github.com/restic/restic/cmd/restic 6.794s tokens used 238,979
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 8.5 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-2-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8.5 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/restic)Questions
- Does restic run?
- Yes. restic runs. Argusic installed and launched it on a clean machine in 9 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test restic?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6adedec6b48a. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test restic?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does restic take to install?
- 8.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does restic need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing restic?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for restic?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.