percona-backup-mongodb

Percona Backup for MongoDB

Runs with mockssource: GitHubhomepageGoApache-2.0commit f007d41c0714

Go, Apache-2.0 licensed. The project labels itself: backup, mongodb, mongodb backup, pbm and percona backup.

percona-backup-mongodb runs, with stand-ins for the services it depends on. An Argusic agent installed it in 2 minutes and hit 3 errors on a clean machine with no GPU, and the whole session was recorded.

Percona Backup for MongoDB builds from source: all 4 production binaries compile and run (pbm version 2.16.0, pbm-agent version 2.16.0), 12 of 22 unit test packages pass, and the remaining 10 fail only because Docker is not available to run test containers (MongoDB, etcd, MinIO, GCS emulator).

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 85.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
85.3 / 100
cost of the verifying run
$0.06 (measured)
recorded runs
1
last tested
stars
338
forks
122
open issues
15
watchers
47
size
66 MB
created
last push

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.

Time lost to each failure while testing percona-backup-mongodb, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • go binary not on PATH1 minute
  • Makefile hardcodes -tags gssapi but krb5-dev headers not installable without root1 minute
  • Docker not installed; 10 pbm test packages and 3 x/ test packages require docker containers (mongodb, etcd, minio, gcs)
Install time
2 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
3 hit, 2 fixed with no human help
How the result was proved
make build exited 0 producing bin/{pbm,pbm-agent,pbm-speed-test} (76M/80M/75M). ./bin/pbm version returned 'Version: 2.16.0' and --help displayed all commands. ./bin/pbm-agent version returned same. 12 go test packages passed. All failing tests exclusively report 'rootless Docker not found' (Docker absent from container).
Model tokens used
479,288
Exact commit tested
f007d41c0714
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
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

**12 of 22 test packages pass** — the 10 failures are all Docker-dependent (need containers for Mon…
tokens used
479,288
All binaries built and verified. 12 test packages passed, 10 failed due solely to Docker being abse…
## Summary
**Makefile patched** to remove the hardcoded `-tags gssapi` from `BUILD_FLAGS` — the krb5-dev heade…
**Build succeeds** for all 4 binaries:
- `./bin/pbm` (76M)
- `./bin/pbm-agent` (80M)
- `./bin/pbm-speed-test` (75M)
- `./bin/pbm-agent-entrypoint` (2.7M)
**12 of 22 test packages pass** — the 10 failures are all Docker-dependent (need containers for Mon…

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

  • Installed in 2 minutes, faster than the median of the 47 comparable projects Argusic has measured.
  • Licensed Apache-2.0, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Hit 3 errors during setup, 1 of which were not solved.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 48 backup projects Argusic has installed and timed, percona-backup-mongodb was the 11th fastest to reach a running state, and 32 of 48 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks85.330.06

Topics (from GitHub)

backupmongodbmongodb-backuppbmpercona-backup

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/percona-backup-mongodb.svg)](https://argusic.com/subject/percona-backup-mongodb)

Questions

Does percona-backup-mongodb run?
percona-backup-mongodb runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test percona-backup-mongodb?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit f007d41c0714. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test percona-backup-mongodb?
The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does percona-backup-mongodb take to install?
2 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 percona-backup-mongodb need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing percona-backup-mongodb?
3 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does percona-backup-mongodb compare with the alternatives?
Of the 48 backup projects Argusic has installed and timed, percona-backup-mongodb was the 11th fastest to reach a running state, and 32 of 48 reached one at all.
Where is the evidence for percona-backup-mongodb?
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.

Discussion