Your backups are green. Are they good?
Backup monitoring that catches silent failures
Add one curl line to the end of a backup job. It sends the size, file count and run time. Lastcopy learns what a normal run looks like and emails you when a run is missing, fails, or comes in wrong.
| fileserver-nightly, 02:00 | took | size | files | exit | lastcopy |
|---|---|---|---|---|---|
| 09 Oct | 4m 12s | 2.5 GB | 48,102 | 0 | normal |
| 10 Oct | 4m 08s | 2.5 GB | 48,117 | 0 | normal |
| 11 Oct | 4m 15s | 2.5 GB | 48,140 | 0 | normal |
| 12 Oct | 4m 10s | 2.5 GB | 48,151 | 0 | normal |
| 13 Oct | 4s | 0 B | 0 | 0 | anomaly |
13 Oct 2026, 02:00 UTC
The failures that hurt report success
tar finds an empty mount and archives nothing. A dump runs against the wrong database. Pruning stops and the repository fills the disk. Each job exits 0, the dashboard stays green, and nobody looks until the day they need a restore.
A cron monitor tells you the job ran. Lastcopy also checks whether the numbers it sent look like the last thirty runs.
The whole integration
your_backup_command \ && curl -fsS -m 10 --retry 3 PING_URL -d "bytes=$SIZE&files=$COUNT" \ || curl -fsS -m 10 PING_URL/fail
That goes at the end of the job you already have. There is no agent to install, and Lastcopy never sees your data, only the numbers you send. The docs have recipes for restic, borgmatic, pg_dump, mysqldump, Veeam and rsync. There is also a longer guide to monitoring restic backups and a page on using Lastcopy as a dead man's switch for backups.
Three levels of proof
- ran
- The job checked in on time and its numbers sit inside what Lastcopy has learned is normal for it. Learning takes 7 runs. You set no thresholds.
- verified
- Your tool's own integrity check passed, such as
restic check --read-dataorborg check --verify-data, reported with the same curl line. - drilled
- Someone restored from it and checked the contents. Lastcopy schedules drills, reminds you weekly when one is overdue, and records the result.
Every check-in gets the first level. Add the other two on the jobs an auditor will ask about. All three are on every plan.
When the auditor asks
ISO 27001 A.8.13 says backups shall be "regularly tested". SOC 2 auditors ask the same thing in other words. The questions are always when you last restored, what you restored, how long it took and who signed it off.
Lastcopy keeps that record outside your systems. Entries are timestamped when they arrive and there is no edit button. A failed drill stays on the record next to the fix, which tells an auditor more than a page of passes.
| drill | result | by | RTO | took |
|---|---|---|---|---|
| 14 Jun 2026 | pass | adam | met | 30m 42s |
| 09 Dec 2025 | fail | jamie | missed | 1h 13m |
Open the sample evidence report. Or read how the register maps to ISO 27001 and SOC 2.
What it won't do
It doesn't run backups or store them. No agent, ever. No marketing email, ever. You get one email when something breaks and one when it recovers, and each one says why it fired.
Price
Free for up to 6 backups, with every feature. Bigger plans are on the pricing page. Everything is free while Lastcopy is in beta, and nothing gets charged without notice.
Who runs this
I'm Adam, an engineer in the UK. I built an early version of this for my own company, where it helped us get through compliance. Lastcopy is that idea done properly, run by one person.
The hosting is paid a year ahead. If I ever shut it down you get months of notice and your records stay exportable as CSV until the last day. Questions and complaints go to adam@getlastcopy.com and I read all of it.