BackupPC
Let’s say you’re managing a bunch of machines — Linux here, some Windows there, maybe a few Macs in the mix. You don’t want agents on every box. You don’t want to deal with yet another cloud panel or be tied to a proprietary system. You just want backups that work, stay out of the way, and don’t eat up all your storage. That’s where BackupPC fits.
It’s open source, has been around for years, and does one thing well: backs up multiple systems to a central server — efficiently, quietly, and without drama.
Why It’s Still in Use (And Why People Stick With It)
– No agents needed. BackupPC talks over rsync, SMB, or SSH — nothing to install on the client side.
– It’s smart with space. Identical files? Stored once, even across machines. That alone saves a ton.
– Everything stays on disk. No weird archive formats — just files, deduplicated, compressed, and easy to browse or restore.
– Control freaks welcome. You get per-host configs, scheduling, exclusions, retention settings — the works.
– No vendor lock-in. No subscriptions. No hidden sync tools phoning home.
Feature Rundown
| Feature | Why It Matters |
| No Agent Needed | Uses rsync, SMB, or tar over SSH — nothing to install on clients |
| Deduplication at File Level | Saves space by storing duplicate files only once |
| Compression | Reduces disk usage without slowing down restores |
| Web Interface | Central place to check status, configure hosts, and restore data |
| Incremental Backups | Unchanged files are hardlinked — fast and efficient |
| Restore Flexibility | Restore to client or download via web — up to you |
| Granular Scheduling | Per-host timing, includes/excludes, retention policies |
| Works Across OSes | Handles Linux, macOS, and Windows without issue |
| Scriptable | Cron-friendly, CLI tools included |
| Notification System | Email reports keep you posted without needing to log in |
Installation Basics
On Ubuntu/Debian:
sudo apt update
sudo apt install backuppc
Access UI at http://<server-ip>/cgi-bin/BackupPC_Admin
On CentOS/RHEL:
sudo dnf install epel-release
sudo dnf install backuppc
Don’t forget to enable Apache and tweak /etc/httpd/conf.d/backuppc.conf if needed.
Quick Setup Guide
- List your clients. Add them to /etc/backuppc/hosts
- Pick your method. Linux/macOS: rsync or tar + SSH, Windows: SMB or rsyncd
- Per-host tweaks. Configs live at /etc/backuppc/pc/<hostname>/config.pl
- Start a manual run (optional):
sudo -u backuppc /usr/share/backuppc/bin/BackupPC_dump <hostname> - Check your schedule. Backups are scheduled with cron by default — tune it if needed.
- Restore when needed. Through the web or CLI, download individual files or push them back.
When BackupPC Makes Sense
- You’ve got more than a few machines to back up.
- You don’t want cloud anything in your backup pipeline.
- You care about deduplication, retention, and policy control.
- You want something that’s been tested, stable, and doesn’t break when unattended.
- You prefer to spend time setting it up once — and then forget it’s there.
Bottom Line
BackupPC isn’t flashy. It doesn’t come with a glossy dashboard or a sales team. What it does have is a reputation for being reliable and efficient — and that’s often exactly what you need. It’s been running quietly behind the scenes in real-world networks for years, and it continues to earn its place.
If you like knowing how your backups work, and you don’t mind configuring a few things up front, it’s a solid, no-nonsense solution that’ll stick with you.
