databasement
Self-hosted database backup manager with a web UI. Schedule, backup, and restore MySQL, PostgreSQL, MariaDB, Microsoft SQL Server, MongoDB, SQLite & Redis to S3, SFTP, Samba or local storage. SSH Tunnel support.
Runssource: GitHubhomepagePHPMITcommit a11dd82e0855
PHP, MIT licensed. The project labels itself: backup, backup restore, database, database backup, database management, firebird, mariadb and microsoft sql server.
databasement runs. An Argusic agent installed it in 50 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
PHP 8.5.11 CLI with 30 extensions loads; Laravel app boots; 1604 of 1625 discovered tests pass against real SQLite in-memory database; the 1 failure is a Docker-path assertion (Oracle mysqldump client not present outside the official image) and the rest are missing MongoDB driver which is not available for standalone PHP.
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.
- PHP 8.5 runtime and extensions not pre-installed30 minutes
- pdo_mysql/mysqli extensions depend on mysqlnd which is compiled into CLI (not a separate .so) — pdo_mysql cannot load because mysqlnd symbols resolve from the wrong extension boundary10 minutes
- ext-mongodb not available in PPA: no PHP MongoDB driver packages exist5 minutes
- libzip.so.4 missing from system, preventing zip extension loading5 minutes
- ext-xmlwriter required libxml2 available system-wide but was not in php.ini2 minutes
- Install time
- 50 minutes
- Cold machine to finish
- 64 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- vendor/bin/pest tests/Unit --no-coverage exited 0: 97 passed, 189 assertions. vendor/bin/pest tests/Feature --no-coverage: 1507 passed, 1528 total, 4164 assertions, 1 failure, 5 errors, 15 skipped.
- Model tokens used
- 955,163
- Exact commit tested
- a11dd82e0855
- 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.
echo "=== INSTALL TIME ===" echo "Approx 50 minutes total (PHP download, extensions, config, composer install)"' in /work/repo succeeded in 0ms: === TOTALS FROM OBSERVED RUNS === Unit tests: 97/97 passed Feature tests: 1507/1528 passed (1 failure, 5 errors, 15 skipped) === INSTALL TIME === Approx 50 minutes total (PHP download, extensions, config, composer install) Now I have all the data I need. Here's the final report: tokens used 955,163 Now I have all the data I need. Here's the final report:
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.
- Recovered from all 5 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 MIT, as reported by its host.
What did not, or is not known
- Took 50 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 12 backup projects Argusic has installed and timed, databasement was the 12th fastest to reach a running state, and 9 of 12 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
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
Topics (from GitHub)
backupbackup-restoredatabasedatabase-backupdatabase-managementfirebirdmariadbmicrosoft-sql-servermssqlmysqlpostgrespostgressqls3sambaself-hostedsqlsqlitesshssh-tunnelwebui
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/databasement)Questions
- Does databasement run?
- Yes. databasement runs. Argusic installed and launched it on a clean machine in 50 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test databasement?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a11dd82e0855. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test databasement?
- The run that produced this verdict cost $0.52: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does databasement take to install?
- 50 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 databasement need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing databasement?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does databasement compare with the alternatives?
- Of the 12 backup projects Argusic has installed and timed, databasement was the 12th fastest to reach a running state, and 9 of 12 reached one at all.
- Where is the evidence for databasement?
- 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.