Picking the right backup tool for your VPS can feel overwhelming. You have options. Three names keep coming up: Rsync, Restic, and Borg. Each one solves a different problem. Each one has trade-offs.
This guide breaks down every detail. We compare speed, cost, encryption, and real-world performance. By the end, you will know exactly which tool fits your small website VPS.
Whether you run a single WordPress site or manage multiple projects on a budget, this comparison covers it all. Let us get started.
Quick Answer: Which Backup Tool Is Right for Your VPS?
Not everyone has time to read a full comparison. Here is the short version. Pick the tool that matches your top priority.
Best for Cloud & Object Storage: Restic
Restic works natively with S3, Backblaze B2, Azure, and Google Cloud Storage. You do not need a special server. Just point Restic at your bucket and go. It encrypts everything before upload. This makes it ideal if you want cheap cloud storage for your VPS backup.
Best for Deduplication & Compression: Borg
Borg leads in deduplication efficiency. It achieves 70–85% data reduction on typical website backups. It also uses less RAM than Restic. If you back up daily and want to keep many versions, Borg saves serious disk space. Pair it with BorgBase for managed hosting.
Best for Mirroring & Migration: Rsync
Rsync is not a true backup tool. It copies files from A to B. That is it. No versioning. No deduplication. No built-in encryption. But for one-time migrations or simple file mirrors, Rsync backup remains fast and reliable. Every Linux VPS already has it installed.
Feature Comparison: Rsync Backup vs Restic vs Borg for VPS
Let us look at the numbers. The tables below show exactly how these three tools compare in 2026.
Deduplication, Compression & Encryption at a Glance
| Feature | Rsync | Restic | Borg |
|---|---|---|---|
| Deduplication | No | Yes (60–80%) | Yes (70–85%) |
| Compression | Optional (gzip via SSH) | Yes (zstd, since v0.14) | Yes (lz4, zstd, lzma) |
| Encryption | SSH transport only | AES-256-CTR + Poly1305-AES | AES-256-CTR + HMAC-SHA256 |
| Incremental Backup | Delta transfer only | Full snapshot with dedup | Full snapshot with dedup |
| Versioning / Retention | No | Yes (policies) | Yes (policies) |
| Resume Interrupted Backup | Yes | Yes | Yes |
The key takeaway: Rsync backup copies files. Restic and Borg create encrypted, deduplicated snapshots. For a real VPS backup strategy, you need versioning. Rsync alone cannot provide that.
Supported Storage Backends (S3, B2, SSH, SFTP)
| Backend | Rsync | Restic | Borg |
|---|---|---|---|
| Local disk | Yes | Yes | Yes |
| SSH / SFTP | Yes | Yes (via SFTP) | Yes (native) |
| Amazon S3 | No | Yes (native) | No (needs rclone) |
| Backblaze B2 | No | Yes (native) | No (needs rclone) |
| Azure Blob | No | Yes (native) | No (needs rclone) |
| Google Cloud Storage | No | Yes (native) | No (needs rclone) |
| REST server | No | Yes | No |
| Managed hosting | rsync.net | Various | BorgBase, rsync.net |
Restic wins on backend flexibility. If you want to use cheap object storage like Backblaze B2, Restic is your best option. Borg requires SSH access to a remote server. You can use BorgBase or rsync.net’s Borg service to handle that.
Performance Benchmarks & Memory Usage (2026 Data)
These benchmarks come from 2-vCPU / 2–4 GB KVM VPS tests with mixed file workloads.
| Metric | Rsync | Restic | Borg |
|---|---|---|---|
| Local backup speed | ~80–120 MB/s | 120–160 MB/s | 180–220 MB/s |
| RAM usage (typical) | ~20–50 MB | 100–200 MB | 50–150 MB |
| CPU overhead | Low | Medium | Low–Medium |
| Network efficiency (repeat backup) | Delta transfer | Dedup chunks only | Dedup chunks only |
Borg is the fastest. It also uses less memory than Restic. For a small VPS with only 2 GB of RAM, every megabyte matters. Borg leaves more room for your web server and database.
Rsync uses the least resources. But it sends more data over the network on repeat backups. Without deduplication, each Rsync backup transfer equals the full size of changed files.
Rsync Backup for VPS: Pros, Cons & Best Use Cases
Rsync has been around since 1996. It is installed on nearly every Linux system. It is simple. It is fast. But it was never designed as a backup tool.
Why Rsync Falls Short as a True Backup Solution
Rsync mirrors files. When you run rsync -a /source /destination, the destination becomes an exact copy of the source. If you delete a file on your VPS, it disappears from the backup too. If ransomware encrypts your site, your Rsync mirror gets encrypted too.
Here is what Rsync lacks:
- No versioning. You only see the latest state. No way to restore yesterday’s files.
- No deduplication. Every backup transfers all changed data. Storage costs grow fast.
- No native encryption. Data is only protected by SSH during transfer. At rest on the destination, files are plain text.
- No integrity checks. Silent data corruption can go unnoticed.
For a real VPS backup, you need point-in-time recovery. Rsync cannot give you that.
When Rsync Still Makes Sense for Small Websites
Rsync is not useless. It has valid use cases:
- Server migration. Moving a site from one VPS to another? Rsync is the fastest way to copy everything.
- Staging sync. Push updated files from local to a staging server.
- Pre-backup staging. Use Rsync to gather files locally, then let Borg or Restic handle the actual backup.
- Simple file mirrors. If you just need a hot spare and do not care about history.
Think of Rsync as a transport tool, not a backup tool. Use it to move data. Use Borg or Restic to protect it.
Rsync Bandwidth Usage & Transfer Speed
Rsync uses delta transfer. It only sends the parts of files that changed. This saves bandwidth compared to a full copy. But it still sends more data than deduplicating tools.
Example: A 5 GB WordPress site with 200 MB of daily changes.
- Rsync: Transfers ~200 MB per backup. Over 30 days, that is 6 GB total transfer.
- Borg: After dedup, might transfer only 50–80 MB per backup. Over 30 days, ~2 GB total.
- Restic: Similar to Borg, maybe slightly more due to chunking overhead.
On a VPS with limited bandwidth, this matters. Rsync backup works fine for small sites. But as your site grows, deduplicating tools save real money on transfer costs.
Restic for VPS Backup: Pros, Cons & Best Use Cases
Restic is a modern backup program written in Go. It runs on Linux, macOS, Windows, and FreeBSD. Its biggest strength is backend support. Restic speaks the language of every major cloud provider.
Restic’s Cloud Storage & Object Backend Advantages
Restic supports these backends out of the box:
- Amazon S3
- Backblaze B2
- Microsoft Azure Blob Storage
- Google Cloud Storage
- OpenStack Swift
- SFTP
- Local filesystem
- REST server
This means you can back up your VPS directly to Backblaze B2 at $0.006/GB/month. No extra server needed. No SSH setup. Just set environment variables and run.
For small website owners, this is huge. You get enterprise-grade backup storage at a fraction of AWS S3 pricing. Get started with Backblaze B2 →
Restic AES-256 Encryption & Security Features
Restic encrypts all data before it leaves your VPS. The encryption uses:
- AES-256 in CTR mode for confidentiality
- Poly1305-AES for message authentication
Your backup provider never sees your unencrypted data. Even if someone breaks into Backblaze B2, your files remain safe. You hold the only key.
Restic also uses content-defined chunking. This means it splits files into variable-length segments. Only changed chunks get uploaded. This is how Restic achieves 60–80% deduplication on typical server workloads.
Restic Performance on Low-RAM VPS (2–4 GB)
Restic uses more memory than Borg. On a 2 GB VPS, Restic typically consumes 100–200 MB during backup. This leaves less room for your web applications.
Practical tips for low-RAM VPS:
- Run Restic backups during off-peak hours (e.g., 3 AM cron job)
- Limit the number of files scanned per run
- Use
--read-concurrency 1to reduce parallel memory usage - Exclude cache and log directories from backups
If your VPS has 4 GB or more RAM, Restic’s memory usage is not a concern. For 2 GB VPS instances, consider Borg instead.
Borg Backup for VPS: Pros, Cons & Best Use Cases
Borg (short for BorgBackup) is a deduplicating backup program written in Python. It is fast, efficient, and designed specifically for Linux servers. If you run a VPS, Borg is often the best choice.
Borg’s Deduplication & Compression Efficiency
Borg leads the pack in deduplication. Benchmarks show 70–85% data reduction on typical website backups. Here is what that means in practice:
- Day 1: Full 5 GB backup → repository uses 5 GB
- Day 2: 200 MB changed → repository adds ~30 MB (after dedup)
- Day 30: You have 30 snapshots, but the repository might only use 6–8 GB
Borg also compresses data. You can choose from multiple algorithms:
- lz4: Fast, low CPU, moderate compression
- zstd: Best balance of speed and compression
- lzma: Maximum compression, slower
For a small website VPS, zstd gives you the best results. You get strong compression without slowing down your backup window.
Borg SSH-Based Backup Workflow for Linux Servers
Borg uses SSH for remote backups. You need a server that runs the Borg daemon. Two popular options:
- BorgBase — Managed Borg hosting. Free 10 GB tier. Paid plans from $24/year for 250 GB. Sign up for BorgBase →
- rsync.net Borg service — 100 GB for $18/year. No egress fees. Unlimited repositories.
The workflow is simple:
- Install Borg on your VPS:
apt install borgbackup - Generate an SSH key:
ssh-keygen - Add the public key to your BorgBase or rsync.net account
- Initialize a repository:
borg init --encryption=repokey-blake2 ssh://user@borgbase.com/./repo - Create your first backup:
borg create ssh://user@borgbase.com/./repo::backup-1 /var/www /etc /home
That is it. Your VPS backup is now encrypted, deduplicated, and stored offsite.
Borg Restore Speed & Archive Mounting
Borg restores are fast. On a local repository, you can expect speeds close to your disk’s read speed. Over SSH, network bandwidth is the bottleneck.
One standout feature: archive mounting. You can mount a Borg backup as a filesystem:
borg mount ssh://user@borgbase.com/./repo /mnt/backup
Now you can browse your backup like a normal folder. Copy individual files with cp. No need to restore the entire archive. This is incredibly useful when you just need one deleted config file or a single database dump.
Rsync vs Restic vs Borg: Real-World VPS Scenarios
Theory is useful. But what about your specific situation? Let us look at three common scenarios.
WordPress Site Backup Strategy
A typical WordPress site includes:
- PHP files (~200 MB)
- Media uploads (grows over time)
- MySQL database (50–500 MB)
- Configuration files
Recommended approach:
- Use
mysqldumpto export the database to a SQL file - Run Borg or Restic to back up
/var/www,/etc, and the SQL dump - Keep 7 daily + 4 weekly snapshots
Why not Rsync? WordPress changes daily. New posts, plugin updates, media uploads. Without versioning, a Rsync backup cannot protect you from a bad plugin update that breaks your site yesterday. You need snapshots.
Best tool: Borg with BorgBase. The deduplication handles daily database changes efficiently. The free 10 GB tier covers most small WordPress sites.
Static Website & Database-Heavy VPS
Static websites (Hugo, Jekyll, plain HTML) rarely change. A database-heavy VPS (multiple MySQL/PostgreSQL instances) generates lots of daily changes.
For static sites: Rsync backup actually works here. The files rarely change. A daily Rsync mirror to another server is cheap and simple. Add a weekly Borg snapshot for versioning.
For database-heavy VPS: Borg or Restic. The deduplication handles repeated database dumps well. Restic is better if you want to store backups in S3 or B2. Borg is better if you have SSH access to a backup server.
Multi-Site VPS with a Limited Budget
You run 5–10 small websites on one VPS. Budget is tight. You need reliable backups without spending much.
Best strategy:
- Use Borg for all sites. One repository, multiple paths.
- Host on BorgBase free tier (10 GB) or the Small plan ($24/year for 250 GB).
- If 250 GB is not enough, rsync.net’s Borg service offers 100 GB for $18/year.
- Set retention to 7 daily + 4 weekly + 6 monthly.
Total cost: $24–$42 per year for full VPS backup coverage. That is less than $4/month.
Rsync alone would cost more in storage because there is no deduplication. Restic would work too, but Borg’s lower memory usage is better for a multi-site VPS that already runs tight on resources.
Cost Comparison: Rsync Backup vs Restic vs Borg for Small Website VPS
Let us talk money. How much does it actually cost to back up a small VPS with each tool?
Storage Provider Pricing (Backblaze B2, BorgBase, rsync-net)
| Provider | Compatible Tool | Free Tier | Paid Plan | Cost per GB/Month |
|---|---|---|---|---|
| Backblaze B2 | Restic | 10 GB free | Pay-as-you-go | $0.006/GB |
| BorgBase | Borg | 10 GB free | Small: $24/year (250 GB) | ~$0.008/GB |
| BorgBase | Borg | — | Medium: $90/year (1 TB) | ~$0.0075/GB |
| BorgBase | Borg | — | Large: $165/year (2 TB) | ~$0.0069/GB |
| rsync.net (Borg) | Borg | — | 100 GB: $18/year | $0.015/GB |
| rsync.net (general) | Rsync, Borg | — | 800 GB minimum | $0.012/GB |
| Self-hosted VPS | Rsync, Borg, Restic | — | $5/month VPS | Varies |
Get BorgBase → | Get Backblaze B2 → | Get rsync.net →
Bandwidth & Resource Consumption Analysis
Let us compare total cost of ownership for a 50 GB VPS with 200 MB daily changes, backed up daily for 30 days.
| Factor | Rsync | Restic | Borg |
|---|---|---|---|
| Storage needed (after 30 days) | ~56 GB (no dedup) | ~8–12 GB (with dedup) | ~6–10 GB (with dedup) |
| Monthly storage cost (BorgBase) | N/A (needs SSH server) | N/A (use B2 instead) | ~$2/month (within free tier) |
| Monthly storage cost (B2 via Restic) | N/A | $0.05–$0.07 | N/A |
| Monthly transfer | ~6 GB | ~1.5–2.5 GB | ~1–2 GB |
| RAM usage during backup | 20–50 MB | 100–200 MB | 50–150 MB |
| CPU impact | Low | Medium | Low–Medium |
The numbers are clear. Deduplication saves money. Borg and Restic use 5–10x less storage than Rsync over time. For a small website VPS, this means your backup stays within free tiers or cheap plans.
Hybrid Backup Strategy: Combining Rsync, Restic & Borg
You do not have to pick just one. The best VPS backup strategy often combines tools. Each tool does what it does best.
Local Snapshot + Offsite Encrypted Backup Workflow
Here is a proven workflow for small website VPS:
- Step 1: Database dump. Run
mysqldumpto save SQL files to/backup/db/. - Step 2: Local Borg snapshot. Create a Borg repository on a local disk or separate partition. This gives you fast local recovery.
- Step 3: Offsite Restic or Borg backup. Push the same data to Backblaze B2 (via Restic) or BorgBase (via Borg). This protects against total VPS loss.
- Step 4 (optional): Rsync for migration. Keep Rsync available for quick file transfers or server migrations.
This gives you three layers of protection:
- Local Borg repo → restore in minutes
- Offsite encrypted backup → survive data center failure
- Rsync on standby → fast migration when needed
Automation & Monitoring Setup for Small Website VPS
Backups only work if they run automatically. Here is a simple cron-based setup:
- Database dump: Cron job at 2:00 AM daily
- Borg local backup: Cron job at 2:15 AM daily
- Restic offsite push: Cron job at 3:00 AM daily
- Retention cleanup:
borg pruneandrestic forgetweekly - Monitoring: Use Healthchecks.io (free tier) to alert you if a backup fails
Sample cron entries:
0 2 * * * /usr/bin/mysqldump --all-databases > /backup/db/all.sql15 2 * * * /usr/bin/borg create /backup/repo::daily-{now} /var/www /etc /backup/db0 3 * * * /usr/local/bin/restic -r b2:mybucket backup /var/www /etc /backup/db0 4 * * 0 /usr/bin/borg prune --keep-daily 7 --keep-weekly 4 /backup/repo
This setup costs almost nothing. It runs while you sleep. And Healthchecks.io sends you a ping if anything goes wrong.
FAQ: Common Questions About Rsync Backup vs Restic vs Borg for VPS
Is Rsync a good backup solution for VPS?
Rsync is a file synchronization tool, not a backup solution. It lacks versioning, deduplication, and encryption at rest. Use Rsync for file transfers and migrations. Use Borg or Restic for actual VPS backups.
Can I use Rsync and Borg together?
Yes. Many administrators use Rsync to gather files into a staging directory, then run Borg on that directory. This separates the collection step from the backup step. It works well for complex setups.
Which is better for a 2 GB RAM VPS: Restic or Borg?
Borg uses less memory (50–150 MB vs 100–200 MB for Restic). On a 2 GB VPS, Borg leaves more room for your web applications. Choose Borg for low-RAM environments.
Do I need encryption for my VPS backup?
Yes. Your backup contains database passwords, configuration files, and user data. Both Borg and Restic encrypt data by default. Always enable encryption. There is no reason to store unencrypted backups on a remote server.
How much does VPS backup cost per month?
For a small website (under 50 GB after deduplication), you can stay within free tiers. BorgBase offers 10 GB free. Backblaze B2 offers 10 GB free. For larger sites, expect to pay $2–$5 per month. That is less than most VPS plans cost.
Can Restic back up to Backblaze B2 directly?
Yes. Restic has native Backblaze B2 support. Set your B2 account ID and application key as environment variables, then run restic -r b2:bucketname backup /path. No extra tools needed.
Can Borg back up to S3 or Backblaze B2?
Not directly. Borg needs SSH access to a remote server. To use S3 or B2 with Borg, you need a bridge tool like rclone. Alternatively, use managed Borg hosting like BorgBase.
How often should I back up my VPS?
Daily backups are the minimum for any production website. Keep at least 7 daily snapshots and 4 weekly snapshots. For database-heavy sites, consider twice-daily backups.
Which tool is easiest to set up?
Rsync is the simplest. One command and you are done. But it is not a real backup. Between Borg and Restic, Restic is slightly easier for cloud backends (just set env variables). Borg requires SSH key setup but offers better performance.
Final Verdict: Choosing the Right VPS Backup Tool in 2026
Here is the bottom line. Each tool has a clear purpose.
| If You Need… | Choose | Why |
|---|---|---|
| Cloud storage backup (S3, B2) | Restic | Native support for all major object storage providers |
| Maximum deduplication & compression | Borg | 70–85% data reduction, fastest speed, lowest RAM usage |
| Simple file mirroring or migration | Rsync | Pre-installed, fast, zero configuration |
| Low-RAM VPS (2 GB) | Borg | Uses 50–150 MB vs 100–200 MB for Restic |
| Budget backup (under $25/year) | Borg + BorgBase | Free 10 GB tier or $24/year for 250 GB |
| Hybrid local + offsite strategy | Borg + Restic | Borg for local snapshots, Restic for cloud push |
For most small website VPS owners, we recommend Borg with BorgBase. It gives you the best deduplication, lowest resource usage, and affordable managed hosting. The free 10 GB tier is enough for many small sites.
If you prefer cloud object storage, choose Restic with Backblaze B2. The native S3-compatible backend support makes it effortless.
Keep Rsync in your toolkit for migrations and file transfers. But do not rely on it as your only backup.
→ Start with BorgBase (Free 10 GB)
→ Try Backblaze B2 for Restic (Free 10 GB)
→ Check rsync.net Borg Hosting ($18/year)
Your VPS data is valuable. A proper backup costs less than a cup of coffee per month. Set it up today. Your future self will thank you.