Tink vs rsnapshot
rsnapshot copies rotating trees, retain intervals, and rsync hard links. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
rsnapshot rotates the tree. Tink answers “why is this VPS sick?”
Accidental sysadmins land on rsnapshot because a hard-link snapshot looks cheaper than an outage. Then the host volume fills, nginx dies, and rsnapshot hourly still looks Success — no retain match for host fill. A filling /var is a Tink warning; it is not an rsnapshot job unless you scraped cron mail and watched it.
Tink is the other job: detect the issue on the machine, say why it happened in plain English, propose the command, and run it only after you approve. Keep using rsnapshot if you already run rotating trees. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | rsnapshot |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — rsnapshot.conf, snapshot_root, retain hourly/daily/weekly, then a host that still has no mechanic after the last rsnapshot hourly exits 0 |
| What you get | Working monitoring, diagnosis, and approved fixes | Rotating snapshot trees, hard links, and rsync. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past hourly.0 |
| Pricing | Free (Scout) / $9 / $29 per machine per month | GPL and free. You still pay the person who owns the VPS after the last retain interval stays listed |
| Hidden costs | None — fully managed | A quiet cron at 2am, a full snapshot_root that is not host fill, and a second tool to tell you the box is sick while rsnapshot hourly still looks Success |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | Trees, retain counts, and rsync exit codes. rsnapshot does not watch a quiet cert or host auth.log after the last hourly.0 landed |
| Configuration | None after install — heuristics and AI | rsnapshot.conf, snapshot_root, backup points, cmd_rsync, exclude files, and which cron actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read rsnapshot -v, then SSH into the host to change the Linux box rsnapshot already sits on |
| Fix execution | Proposes and executes approved commands with an audit trail | Retry rsnapshot hourly — rsnapshot cannot free host disk, rotate a cert, or stop SSH brute-force unless you wrote that backup line |
| Alerting | Built-in across 8 channels | Not an rsnapshot job — cron mail plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not an rsnapshot job — a retain interval does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — rsnapshot does not read host auth.log, journald, or firewall state after the last hourly.0 landed |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the guest dies after the last Success cron — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — rsnapshot has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a retain recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed rsnapshot cron into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | snapshot_root and SSH. No mechanic you text when /var filled and the last hourly.0 still showed transferred |
| Learning curve | None — works after install | Steep — rsnapshot.conf, retain intervals, hard-link rotation, and which failure is rsync vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run rsnapshot for rotating trees, not a sick-VPS mechanic |
When rsnapshot is the right choice
Keep using rsnapshot when you already want that exact job:
- Rotating rsync hard-link trees — you need snapshot_root, retain hourly/daily/weekly, and rsnapshot.conf, not a mechanic.
- An existing backup cron — interval rotation, exclude files, and local snapshot_root matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — rsnapshot already runs, the tree already ships, and someone owns the snapshot disk.
- Hosts that only page on backup cron death — you already run rsnapshot mail, not a sick-box SSH loop.
The real cost of “just watch rsnapshot hourly”
rsnapshot rotates trees and retain intervals. A working ops loop for five Linux boxes is not:
- A healthy hourly.0 still means you SSH into the host and change the box by hand when it gets sick later
- Host fill, nginx, certs, and SSH brute-force never appear unless a separate tool scraped those signals and a rule fired
- A filling /var is a Tink disk warning on every scan — rsnapshot will stay quiet until the next cron fails
- A single VPS with a dead agent still needs a mechanic, not another retain interval
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-cron notifications alive after an rsnapshot install, and every scan includes a diagnosis a quiet rsnapshot hourly Success will not type.
No snapshot_root homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs rsync · Tink vs restic · Tink vs Borg