Your backups are green.
Are they good?

Lastcopy is not a backup tool. It watches the backup jobs you already run, whatever tool runs them, and catches the ones silently failing. The empty dump. The job that "succeeds" in 4 seconds. The retention that quietly broke. Exit code 0 doesn't mean your backup works.

Your job sends its numbers, size, file count and duration, in one line added at the end. Lastcopy learns what normal looks like and alerts when a run goes missing, fails outright, or succeeds looking wrong. It never sees the backup itself, only the numbers. No agent, and your backup logic stays exactly as it is.

Watch 6 backups free See a sample evidence report

For the person who runs the backups, and for the audit that eventually asks about them.

The whole integration, with any backup tool

your_backup_command \
  && curl -fsS -m 10 --retry 3 PING_URL -d "bytes=$SIZE&files=$COUNT" \
  || curl -fsS -m 10 PING_URL/fail

restic backup /srv --json | tail -n1 > /tmp/summary.json
curl -fsS -m 10 --retry 3 PING_URL -d "$(jq -r \
  '"bytes=\(.data_added)&files=\(.files_new + .files_changed)&duration=\(.total_duration|floor)&snapshot=\(.snapshot_id[0:8])"' \
  /tmp/summary.json)"

# /etc/borgmatic/config.yaml
commands:
  - after: action
    when: [create]
    run:
      - curl -fsS -m 10 --retry 3 PING_URL -d "status=ok"
  - after: error
    run:
      - curl -fsS -m 10 PING_URL/fail

pg_dump mydb > /backup/mydb.sql && gzip -f /backup/mydb.sql \
  && curl -fsS -m 10 --retry 3 PING_URL -d "bytes=$(stat -c%s /backup/mydb.sql.gz)&files=1" \
  || curl -fsS -m 10 PING_URL/fail
# on macOS use  stat -f%z  instead of  stat -c%s

mysqldump --all-databases > /backup/all.sql && gzip -f /backup/all.sql \
  && curl -fsS -m 10 --retry 3 PING_URL -d "bytes=$(stat -c%s /backup/all.sql.gz)&files=1" \
  || curl -fsS -m 10 PING_URL/fail

$s = Get-VBRBackupSession | Sort-Object CreationTime | Select-Object -Last 1
Invoke-RestMethod -Uri "PING_URL" -Method Post -Body @{
  status   = $s.Result
  bytes    = $s.Info.BackedUpSize
  duration = [int]($s.EndTime - $s.CreationTime).TotalSeconds
}

OUT=$(rsync -a --stats /srv/ backup:/srv/) \
  && curl -fsS -m 10 --retry 3 PING_URL -d "bytes=$(echo "$OUT" | awk '/Total transferred file size/ {gsub(/,/,""); print $5}')" \
  || curl -fsS -m 10 PING_URL/fail

Pick your tool above, or start from Any command and drop in whatever you run. If your backup can run one command when it finishes, it can report in, and that includes every tool above plus any script you wrote yourself. A check-in on success, /fail on error. There are more recipes in the docs, a longer guide to monitoring restic backups with systemd and cron, and a write-up of the silence tier as a dead man's switch for backups.

The whole install. A backup runs, the check-in arrives.

Three tiers of assurance

Each tier proves more than the one before. There are no thresholds to configure. After 7 runs Lastcopy knows this job's normal size, file count and duration, and every alert states its evidence.

ran

Checked in on schedule, numbers within learned norms. Catches the empty dump and the 4-second "backup", the failures that ping green.

verified

Your tool's own cryptographic integrity check (restic check --read-data, borg check --verify-data) ran and passed. Corruption detection, reported in one line.

drilled

You restored it and the contents validated. Lastcopy schedules the drill, nags weekly when it's overdue, and keeps the register, which is the evidence ISO 27001 and SOC 2 auditors ask for.

Use as many as the job needs. Every check-in gives you the first tier, and most jobs stay there. Add verification and drills on the ones where the evidence has to hold up. Every tier is on every plan.

Audit on the calendar?

The auditor will ask when you last restored, what you restored, whether it met your RTO, and who signed off. Most auditors work from one simple principle. If you don't have evidence, it didn't happen. And the most common finding isn't missing backups. The jobs run, but the evidence does not.

Lastcopy keeps that register for you. Every entry is timestamped on arrival, held outside your systems, with no edit function. It is not a spreadsheet someone fills in the week before the audit. ISO 27001 A.8.13 says backups shall be "regularly tested", and a backup that has never been restored is an assumption, not a control.

See the exact report your auditor gets How the register maps to ISO 27001 and SOC 2

99.5%coverage

4restore drills

52verifications

When	Result	By	RTO
14 Jun 2026	pass	adam	met 30m 42s
9 Dec 2025	fail	jamie	missed 1h 13m

From the sample evidence report. The failed drill stays on the record with its remediation, which is stronger evidence than a perfect page.

What Lastcopy never does

It does not run backups, store backups, or replace your backup tool. No agent, ever. Your backup logic stays the same. No marketing email. Every message is an alert or a summary you can turn off. And no alert noise. One alert per state change, one email per incident, a recovery notice when it's fixed. Every alert says exactly why it fired.

Point a backup at it

Sign up. Your first backup is created for you, ping URL ready.
Add one curl line to the job. The first check-in turns it green.
Let it learn. After 7 runs the baselines are live, and drills get scheduled, nagged and recorded.

Watch 6 backups free See the sample report

Your backups are green.Are they good?