Tink vs PhotoRec
PhotoRec carves deleted files from a disk image. That is not a mechanic. Tink installs in one command, watches the Linux host, explains what is wrong, and helps you fix it.
PhotoRec recovers the files. Tink answers “why is this VPS sick?”
Accidental sysadmins land on PhotoRec because a free file carver looks like insurance. Then the host volume fills, nginx dies, and the last photorec.log still looks complete — no Search match for host fill. A filling /var is a Tink warning; it is not a PhotoRec job unless you scraped recovery 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 PhotoRec if you already run file carving. Use Tink if you run Linux servers and want a mechanic.
| Feature | Tink | PhotoRec |
|---|---|---|
| Setup time | 30 seconds (one curl | sh command) | Hours — boot a live ISO, run photorec on /dev/sdX, pick a file family, wait for recup_dir, then a host that still has no mechanic after the last carve finished |
| What you get | Working monitoring, diagnosis, and approved fixes | A file-carving ncurses tool. Disk fill, nginx, Postgres, and certs stay your problem until you SSH past the last photorec.log |
| Pricing | Free (Scout) / $9 / $29 per machine per month | GPL and free. You still pay the person who owns the VPS after the last PhotoRec Search looks finished |
| Hidden costs | None — fully managed | A quiet photorec.log that is not host fill, downtime to boot USB, recup_dir homework, and a second tool to tell you the box is sick while the last carve still showed complete |
| Monitoring approach | Agent on the server — CPU, disk, services, logs, certs, ports | PhotoRec Search, file-family filters, QPhotoRec, recup_dir. PhotoRec does not watch a quiet cert or host auth.log after the last recovery session ended |
| Configuration | None after install — heuristics and AI | Which /dev/sdX to Search, whole disk vs partition, JPEG vs everything, and which failed PhotoRec session actually pages you |
| Plain-English diagnosis | Yes — AI explains root cause, impact, and fix | You read photorec.log and recup_dir, then SSH into the host to change the Linux box PhotoRec already carved files off |
| Fix execution | Proposes and executes approved commands with an audit trail | Carve signatures into recup_dir — PhotoRec cannot free host disk, rotate a cert, or stop SSH brute-force unless you run photorec again |
| Alerting | Built-in across 8 channels | Not a PhotoRec job — cron mail from a failed image plus a separate monitoring tool have to fire |
| Predictive alerts | Yes — disk fills in ~6 days, memory and CPU trends | Not a PhotoRec job — a photorec.log date does not forecast a quiet host filling up |
| SSH brute-force detection | Built-in — parses auth.log every scan | Never — PhotoRec does not read host auth.log, journald, or firewall state after the last recovery session ended |
| Machine offline detection | Agent presence monitoring with multi-channel alerts | Silence if the host dies after the last PhotoRec Search — unless you built a separate uptime check |
| Public status page | Shareable URL with 90-day history | None — PhotoRec has no customer-facing status page for the Linux host |
| Weekly fleet digest | Automated Monday digest + daily brief when issues are open | None — a photorec.log recap is not a plain-English fleet narrative |
| On-call tracking | Built-in /oncall command + incident acknowledgment | Not included — wire failed PhotoRec Searches into PagerDuty or another incident tool |
| Conversation interface | Telegram, WhatsApp, web dashboard, CLI | The PhotoRec ncurses UI, QPhotoRec, and SSH. No mechanic you text when /var filled and the last Search still showed complete |
| Learning curve | None — works after install | Steep — photorec, QPhotoRec, file families, whole-disk vs partition, recup_dir names, and which failure is the carve vs the running host |
| Best for | Freelancers, small teams, accidental sysadmins (1-50 Linux servers) | Teams that already run PhotoRec for file carving, not a sick-VPS mechanic |
When PhotoRec is the right choice
Keep using PhotoRec when you already want that exact job:
- File carving — you need photorec Search, file-family filters, or QPhotoRec, not a mechanic.
- An existing recovery stack — live ISO boots, disk images, and a lab LAN matter more than guest nginx, certs, and SSH on a quiet VPS.
- An existing lab or nested setup — PhotoRec already runs, photorec.log already exists, and someone owns the USB stick.
- Hosts that only page on image or restore death — you already run failed-backup mail, not a sick-box SSH loop.
The real cost of “just run photorec”
PhotoRec carves files. A working ops loop for five Linux boxes is not:
- A healthy Search pass 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 — PhotoRec will stay quiet until the next recovery session
- A single VPS with a dead agent still needs a mechanic, not another photorec Search
For a 5-server team, Tink Mechanic at $45/month is cheaper than the engineer who keeps failed-backup notifications alive after a green PhotoRec session, and every scan includes a diagnosis a quiet photorec.log will not type.
No photorec.log or recup_dir homework. No silent host. One command install.
Start MechanicAlso compare: Tink vs SystemRescue · Tink vs Partclone · Tink vs FSArchiver