VPS Backup Strategy: The 3-2-1 Rule and Best Tools

1. Why You Need a Clear Backup Strategy

Data loss on a VPS can come from many sources — both preventable and unpreventable: hardware failure, ransomware, human error (accidental deletion), or OS corruption after a failed upgrade.

Sobering statistics from data security research:

• 60% of small businesses that suffer data loss without backup close within 6 months
• Average ransomware downtime is 16–21 days
• Snapshots that have never been tested fail at a rate of up to 34% on first restore attempt

AsiaGB VPS includes twice-monthly automated backups (on the 1st and 15th of each month) as a provider-level safety net. But for data that changes daily, you need your own backup strategy on top of that.

2. What Is the 3-2-1 Backup Rule?

The 3-2-1 Rule is an industry-standard approach used worldwide:

3-2-1 in Practice for Your VPS

• Copy 1: Live data on VPS (SSD)
• Copy 2: Local backup on a separate partition or volume
• Copy 3: Remote backup to Object Storage or another VPS

3. Backup Types: Full, Incremental, Differential

4. Recommended VPS Backup Tools

5. Setting Up Backup with rsync + cron

rsync is the best starting point — no dependencies, and easy to understand.

Step 1: Set Up SSH Key Authentication

# On your VPS, create a key pair
ssh-keygen -t ed25519 -C "backup-key" -f ~/.ssh/backup_key -N ""

# Copy public key to backup server
ssh-copy-id -i ~/.ssh/backup_key.pub user@backup-server

Step 2: Create a Backup Script

#!/bin/bash
# /usr/local/bin/vps-backup.sh
DATE=$(date +%Y-%m-%d)
BACKUP_USER="backup"
BACKUP_HOST="backup-server.example.com"
BACKUP_PATH="/backups/myvps/$DATE"
LOG="/var/log/backup.log"

echo "[$DATE] Starting backup..." >> $LOG

rsync -avz --delete \
  -e "ssh -i /root/.ssh/backup_key -o StrictHostKeyChecking=no" \
  /var/www/ /etc/ /home/ \
  $BACKUP_USER@$BACKUP_HOST:$BACKUP_PATH/ >> $LOG 2>&1

if [ $? -eq 0 ]; then
  echo "[$DATE] Backup completed successfully" >> $LOG
else
  echo "[$DATE] Backup FAILED!" >> $LOG
fi

Step 3: Schedule with cron

# crontab -e
# Run every night at 2:00 AM
0 2 * * * /usr/local/bin/vps-backup.sh

6. BorgBackup: Deduplication Backup for VPS

BorgBackup is ideal for VPS servers that need long backup history without ballooning storage costs. Its deduplication system stores identical data only once, typically saving 40–60% on storage.

Install and Use BorgBackup

# Install
apt install borgbackup -y

# Initialize repository (once)
borg init --encryption=repokey user@backup-server:/backups/borg-repo

# Create backup
borg create --stats --progress \
  user@backup-server:/backups/borg-repo::$(date +%Y-%m-%d) \
  /var/www /etc /home

# List all archives
borg list user@backup-server:/backups/borg-repo

# Restore a single file from specific date
borg extract user@backup-server:/backups/borg-repo::2026-09-20 \
  var/www/html/important.php

Automatic Pruning of Old Archives

# Keep 7 daily, 4 weekly, 6 monthly archives
borg prune --keep-daily=7 --keep-weekly=4 --keep-monthly=6 \
  user@backup-server:/backups/borg-repo

7. Backup Frequency Best Practices

8. Restore Testing: What Most People Skip

Having a backup without testing restore is like buying insurance without reading the policy — you don't know if it actually works until disaster strikes.

Restore Testing Checklist (Every 3 Months)

• ✅ Restore a single file from backup and verify its content is correct
• ✅ Restore database to a test server and run queries to validate data
• ✅ Check backup logs for errors or permission issues
• ✅ Compare file counts between source and backup destination
• ✅ Full drill: spin up a fresh VPS, restore everything from scratch, time it

9. Frequently Asked Questions