Hybrid Rsync and Rclone Architecture
The hybrid model gives you both fast local recovery and durable cloud copies.
Architecture
Example Workflow
hybrid-workflow.sh
# Step 1: Local snapshot
rsync -a --delete /srv/app/ /backup/local/app/current/
# Step 2: Cloud replication
rclone sync /backup/local/app/current/ remote-prod:backup/app/current --progress
# Step 3: Verification
rclone check /backup/local/app/current/ remote-prod:backup/app/current --one-way
Why It Works
| Layer | Strength |
|---|---|
| Local rsync copy | Fast restores and LAN speed |
| Rclone cloud mirror | Offsite resilience and provider portability |
info
This pattern is especially effective for WordPress/media-heavy stacks where local restore speed matters.
Common Pitfalls
| Pitfall | Effect | Fix |
|---|---|---|
| Skipping local snapshot verification | Bad data propagated to cloud | Validate locally before upload |
| One giant monolithic backup path | Hard partial restore | Split by dataset |
| No recovery drill | Architecture unproven | Schedule quarterly restore tests |