{"id":620,"date":"2026-07-18T04:41:00","date_gmt":"2026-07-18T04:41:00","guid":{"rendered":"https:\/\/virtualserversvps.com\/blog\/?p=620"},"modified":"2026-08-05T22:18:12","modified_gmt":"2026-08-05T22:18:12","slug":"vps-backup-automation-rsync-restic-rclone","status":"publish","type":"post","link":"https:\/\/virtualserversvps.com\/blog\/vps-backup-automation-rsync-restic-rclone\/","title":{"rendered":"VPS Backup Automation with rsync, restic, and rclone: Cron Jobs, Snapshots, and Offsite Copies"},"content":{"rendered":"\n

A misconfigured cron job or an accidental rm -rf<\/code> can erase months of work in seconds, and provider-level storage failures, while rare, do happen. The 3-2-1 rule \u2014 three copies of your data, on two different media types, with one copy offsite \u2014 exists for exactly this reason, and on a VPS it is fully automatable with three complementary tools: rsync<\/strong> for continuous file-level sync, restic<\/strong> for encrypted, deduplicated snapshots, and rclone<\/strong> for offsite copies to object storage.<\/p>\n\n\n\n

Storage sizing comes before the pipeline: a snapshot repository needs headroom above your live data, and offsite copies consume their own quota. If you are still choosing the server, see the full specs on our VPS comparison table<\/a> and pick a plan with at least double your dataset size in disk.<\/p>\n\n\n\n

The Tools and What Each One Does<\/h2>\n\n\n\n
Tool<\/th>Job<\/th>Key property<\/th><\/tr><\/thead>
rsync<\/td>File-level sync over SSH<\/td>Incremental delta transfers<\/td><\/tr>
restic<\/td>Point-in-time snapshots<\/td>Encrypted, deduplicated, append-only<\/td><\/tr>
rclone<\/td>Offsite cloud copies<\/td>40+ backends: S3, B2, GCS, Drive<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

Each tool fills one slot in the pipeline. rsync mirrors directories; restic stores encrypted snapshots you can restore to any moment in time; rclone syncs the snapshot repository to cheap object storage so a total VPS loss still leaves you with a recoverable copy.<\/p>\n\n\n\n

The pipeline is deliberately layered rather than redundant: rsync gives you a current, browseable copy, restic gives you history with encryption at rest, and rclone gives you geographic separation. If any single layer fails \u2014 a dead backup disk, a corrupted repository, a full cloud bucket \u2014 the other two still cover you. That layering is what turns a backup script into a backup strategy.<\/p>\n\n\n\n

Before automating anything, decide what actually needs backing up. Web roots, upload directories, database dumps, and \/etc<\/code> configuration are the obvious candidates; package caches, session files, and build artifacts are not. If deleting it costs you more than an hour to rebuild, it belongs in the pipeline \u2014 that list becomes the --exclude<\/code>\/--include<\/code> rules you maintain for years.<\/p>\n\n\n\n

Installation on Ubuntu 24.04<\/h2>\n\n\n\n
apt update && apt install -y rsync restic rclone\nrestic self-update || true\nrclone version   # confirm all three are present<\/code><\/pre>\n\n\n\n
All three tools live in the default Ubuntu repositories, so installation is a single command. restic also ships a self-update helper that keeps the binary current between OS releases.<\/p>\n\n\n\n
rsync: Daily File-Level Sync<\/h2>\n\n\n\n
rsync -avz --delete \/var\/www\/ backup@remote:\/backups\/www\/ \\\n  --exclude cache\/ --exclude tmp\/<\/code><\/pre>\n\n\n\n