Data loss on a VPS is not a question of if<\/em> but when<\/em>. Hardware failures, accidental deletions, ransomware attacks, and software bugs all threaten server data. A 2024 survey found that 40% of small-to-medium businesses that suffer major data loss never fully recover. Automated, tested backups are the only reliable defense.<\/p>\n\n\n\n This article compares three leading open-source backup tools \u2014 rsync, BorgBackup, and Restic \u2014 for VPS data protection. Each offers different trade-offs in speed, storage efficiency, encryption, and restoration simplicity. We evaluate each tool against real-world VPS scenarios including databases, application files, and configuration directories.<\/p>\n\n\n\n rsync has been the backbone of Unix file transfers for decades. It uses the rsync algorithm to transfer only the differences between source and destination files, making incremental backups fast and bandwidth-efficient.<\/p>\n\n\n\n Strengths:<\/strong> Universally available on every Linux distribution. Extremely fast for initial backups and filesystem-level restores. Supports SSH encryption natively. Simple to script with cron.<\/p>\n\n\n\n Weaknesses:<\/strong> No built-in deduplication across snapshots. No compression. No native encryption (relies on SSH tunnel). Not atomic \u2014 a backup taken during a write can be inconsistent. Manual scripting required for rotation and retention policies.<\/p>\n\n\n\n Best for:<\/strong> Simple file-level backups where you need full files restored without any tool-specific format. Excellent for off-site replication to a second VPS.<\/p>\n\n\n\n BorgBackup (Borg) is a deduplicating backup tool that splits files into chunks and stores each chunk only once, even across multiple backups. Combined with LZ4 or ZSTD compression, Borg can reduce storage requirements by 80\u201395% compared to uncompressed rsync copies.<\/p>\n\n\n\n Strengths:<\/strong> Content-defined chunking for cross-file deduplication. Built-in compression (zstd recommended). Authenticated encryption with AEAD. Append-only mode for ransomware protection. Mountable backup archives via FUSE for easy restoration. Prune and compact commands for automatic retention management.<\/p>\n\n\n\n Weaknesses:<\/strong> Repository format is Borg-specific \u2014 requires Borg to restore. Initial backup is CPU-intensive due to chunking. Slightly more complex setup than rsync. Not suitable for real-time sync (designed for periodic snapshots).<\/p>\n\n\n\n Best for:<\/strong> Long-term retention on limited storage. Servers where backup storage costs matter (small VPS plans, cheap object storage). Environments requiring encrypted off-site backups.<\/p>\n\n\n\n Restic is a modern backup tool designed from the ground up for cloud storage backends \u2014 S3, Backblaze B2, Google Cloud Storage, Azure Blob, and SFTP. Like Borg, it uses content-defined chunking and deduplication, but Restic emphasizes simplicity and broad backend support.<\/p>\n\n\n\n Strengths:<\/strong> Supports 10+ storage backends with a unified interface. Built-in AES-256-GCM encryption with key-based or password-based access. Automatic deduplication across all snapshots. Very fast restore \u2014 can restore individual files or entire snapshots. Immutable snapshots with append-only repositories. Self-healing via check command and data integrity verification.<\/p>\n\n\n\n Weaknesses:<\/strong> Slightly less compression efficient than Borg on highly redundant data. No built-in prune scheduling (must script it). Restic format is not mountable natively on all platforms.<\/p>\n\n\n\n Best for:<\/strong> Off-site backups to cloud object storage. Multi-server environments with a centralized backup repository. Compliance scenarios requiring encryption at rest and in transit.<\/p>\n\n\n\n The most resilient VPS backup architecture uses multiple tools together:<\/p>\n\n\n\nrsync: The Veteran File Synchronizer<\/h2>\n\n\n\n
Basic rsync Backup Script<\/h3>\n\n\n\n
#!\/bin\/bash\n# \/usr\/local\/bin\/rsync-backup.sh\nBACKUP_DIR=\"\/backup\/$(date +%Y-%m-%d)\"\nmkdir -p \"$BACKUP_DIR\"\n\n# Backup critical directories\nrsync -avz --delete --link-dest=\/backup\/latest \/etc\/ \"$BACKUP_DIR\/etc\/\"\n\nrsync -avz --delete --link-dest=\/backup\/latest \/var\/www\/ \"$BACKUP_DIR\/www\/\"\n\n# Database dump before backup\nmysqldump --all-databases > \/tmp\/alldb.sql\nrsync -avz \/tmp\/alldb.sql \"$BACKUP_DIR\/database\/\"\n\n# Update latest symlink\nrm -f \/backup\/latest\nln -s \"$BACKUP_DIR\" \/backup\/latest<\/code><\/pre>\n\n\n\nBorgBackup: Deduplication and Compression Powerhouse<\/h2>\n\n\n\n
Borg Backup Configuration<\/h3>\n\n\n\n
#!\/bin\/bash\n# \/usr\/local\/bin\/borg-backup.sh\nexport BORG_REPO=\"\/backup\/borg-repo\"\nexport BORG_PASSPHRASE=\"your-strong-encryption-key\"\n\n# Create backup\nborg create --verbose --filter AME --list --stats --show-rc --compression zstd,8 --exclude-caches --exclude '\/var\/cache\/*' --exclude '\/var\/tmp\/*' ::'{hostname}-{now:%Y-%m-%d_%H:%M}' \/etc \/var\/www \/var\/lib\/mysql\n\n# Prune old backups (keep 7 daily, 4 weekly, 6 monthly)\nborg prune --list --show-rc --keep-daily 7 --keep-weekly 4 --keep-monthly 6\n\n# Compact freed space\nborg compact<\/code><\/pre>\n\n\n\nRestic: Cloud-Native Encrypted Backups<\/h2>\n\n\n\n
Restic to Backblaze B2 Example<\/h3>\n\n\n\n
#!\/bin\/bash\n# \/usr\/local\/bin\/restic-backup.sh\nexport RESTIC_REPOSITORY=\"b2:mybucket-vps-backups\"\nexport RESTIC_PASSWORD=\"your-backup-encryption-key\"\nexport B2_ACCOUNT_ID=\"your-b2-key-id\"\nexport B2_ACCOUNT_KEY=\"your-b2-application-key\"\n\n# Create snapshot\nrestic backup --verbose --exclude '\/var\/cache\/*' --exclude '\/tmp\/*' --exclude '*.log' \/etc \/var\/www \/var\/lib\/mysql\n\n# Forget old snapshots (keep 7 daily, 4 weekly, 12 monthly)\nrestic forget --keep-daily 7 --keep-weekly 4 --keep-monthly 12 --prune\n\n# Verify repository integrity weekly\nif [ \"$(date +%u)\" = \"7\" ]; then\n restic check --read-data\nfi<\/code><\/pre>\n\n\n\nHead-to-Head Comparison<\/h2>\n\n\n\n
Feature<\/th> rsync<\/th> BorgBackup<\/th> Restic<\/th><\/tr><\/thead> Deduplication<\/td> No (per-file hardlink)<\/td> Yes (content-defined chunks)<\/td> Yes (content-defined chunks)<\/td><\/tr> Compression<\/td> No (uses SSH)<\/td> zstd, LZ4, LZMA<\/td> None built-in (repo-level)<\/td><\/tr> Encryption<\/td> SSH tunnel only<\/td> AEAD (keyfile\/password)<\/td> AES-256-GCM<\/td><\/tr> Cloud backends<\/td> SSH\/rsync daemon only<\/td> Local, SSH, FUSE<\/td> S3, B2, GCS, Azure, SFTP, local<\/td><\/tr> Restore speed<\/td> Fastest (file-level)<\/td> Fast (FUSE mount)<\/td> Fast (mount or restore)<\/td><\/tr> Incremental speed<\/td> Very fast (delta sync)<\/td> Fast (chunk-level)<\/td> Fast (chunk-level)<\/td><\/tr> Storage efficiency<\/td> Low (full copies)<\/td> Very high (dedup+compression)<\/td> High (dedup)<\/td><\/tr> Learning curve<\/td> Low<\/td> Medium<\/td> Low-Medium<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n Recommended Strategy: Layered Backups<\/h2>\n\n\n\n