{"id":4293,"date":"2026-09-12T15:40:53","date_gmt":"2026-09-12T10:10:53","guid":{"rendered":"https:\/\/cpanelfree.com\/blog\/how-to-use-rsync-over-ssh-server-backups-guide\/"},"modified":"2026-09-12T15:41:11","modified_gmt":"2026-09-12T10:11:11","slug":"how-to-use-rsync-over-ssh-server-backups-guide","status":"publish","type":"post","link":"https:\/\/cpanelfree.com\/blog\/how-to-use-rsync-over-ssh-server-backups-guide\/","title":{"rendered":"How to Use Rsync Over SSH for Automated Server-to-Server Backups and Sync"},"content":{"rendered":"
\n Quick Technical Answer:<\/strong><\/p>\n

\n To synchronize files securely between two Linux VPS servers over SSH, use the standard command: rsync -avzP -e \"ssh -p 22\" \/local\/source\/ user@remote_ip:\/remote\/destination\/<\/code>. The flags -a<\/code> preserves permissions and timestamps, -v<\/code> enables verbose output, -z<\/code> enables gzip transmission compression, and -P<\/code> preserves partial transfers with a live progress bar. To make it automated, use passwordless Ed25519 SSH keys and schedule it inside crontab<\/code>.\n <\/p>\n<\/div>\n

Why Rsync Remains the King of Linux Backup & Migration Utilities<\/h2>\n

When moving large datasets\u2014such as multi-gigabyte WordPress media uploads, database dumps, and application assets\u2014between cloud servers, traditional tools like FTP, SCP, or raw tar archives transfer every single byte sequentially. If a 10GB transfer is interrupted at 99%, standard SCP forces you to re-upload the entire file from scratch.<\/p>\n

Rsync (Remote Sync)<\/strong> revolutionized data synchronization by introducing the rolling checksum delta-transfer algorithm<\/strong>. Rsync compares the source and destination directories, identifies which blocks of a file have changed, and transfers only the differential byte changes<\/em>. If a 5GB database backup file only has 50MB of new entries, rsync transmits only that 50MB delta\u2014slashing transfer times and bandwidth bills by over 95%.<\/p>\n

Tunneling rsync through an encrypted SSH connection provides end-to-end cryptographic protection, ensuring credentials and proprietary web assets cannot be intercepted in transit.<\/p>\n

Step 1: Anatomy of Essential Rsync Flags<\/h2>\n

Understanding rsync flags prevents catastrophic data loss errors (such as accidentally wiping destination files):<\/p>\n\n\n\n\n\n\n\n\n\n
Flag<\/th>\nFull Parameter<\/th>\nOperational Function<\/th>\n<\/tr>\n<\/thead>\n
-a<\/code><\/td>\n--archive<\/code><\/td>\nArchive mode; preserves file permissions, ownership, symlinks, timestamps, and recursively traverses subdirectories.<\/td>\n<\/tr>\n
-v<\/code><\/td>\n--verbose<\/code><\/td>\nProvides detailed console output listing each file being transferred.<\/td>\n<\/tr>\n
-z<\/code><\/td>\n--compress<\/code><\/td>\nCompresses data in flight using zlib to minimize network bandwidth consumption.<\/td>\n<\/tr>\n
-P<\/code><\/td>\n--partial --progress<\/code><\/td>\nShows a live progress bar and preserves partially transferred files so interrupted jobs resume without restart.<\/td>\n<\/tr>\n
--delete<\/code><\/td>\nMirror deletion<\/td>\nDeletes files on the remote destination if they no longer exist on the source, creating an exact mirror.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Step 2: The Critical Trailing Slash Rule<\/h2>\n
\n WARNING: The Trailing Slash Changes Behavior Completely!<\/strong><\/p>\n

\n rsync -a \/source\/folder \/dest\/<\/code> creates \/dest\/folder\/file.txt<\/code> (copies the folder itself).
\n rsync -a \/source\/folder\/ \/dest\/<\/code> creates \/dest\/file.txt<\/code> (copies only the contents<\/strong> of the folder).\n <\/p>\n<\/div>\n

Step 3: Setting Up Passwordless SSH Keys for Automation<\/h2>\n

To run rsync inside automated cron scripts, the source server must authenticate to the remote destination server without password prompts using high-security Ed25519 SSH keys:<\/p>\n

# Generate a dedicated backup keypair on the SOURCE server (no passphrase)\nssh-keygen -t ed25519 -f ~\/.ssh\/backup_key -N \"\"\n\n# Copy the public key to the REMOTE destination server\nssh-copy-id -i ~\/.ssh\/backup_key.pub -p 22 backupuser@remote_backup_ip\n\n# Test SSH connection without password\nssh -i ~\/.ssh\/backup_key -p 22 backupuser@remote_backup_ip \"echo SSH Connection Successful\"<\/code><\/pre>\n
Step 4: Real-World Synchronizations with Non-Standard Ports & Exclusions<\/h2>\n
If your remote backup server uses a hardened custom SSH port (e.g. port 2222<\/code>) and you want to exclude cache and temp files:<\/p>\n
# Rsync with custom SSH port and exclude filters\nrsync -avzP --delete   -e \"ssh -i \/root\/.ssh\/backup_key -p 2222\"   --exclude=\"wp-content\/cache\/*\"   --exclude=\"*.tmp\"   --exclude=\"node_modules\"   --bwlimit=10000   \/var\/www\/html\/   backupuser@remote_backup_ip:\/backups\/live_site\/<\/code><\/pre>\n
Note: --bwlimit=10000<\/code> caps transfer speeds at 10 MB\/s, preventing rsync from saturating server bandwidth during business hours.<\/em><\/p>\n
Step 5: Automated Nightly Backup Script with Crontab<\/h2>\n
Create a production bash backup script that logs all execution output:<\/p>\n
sudo nano \/usr\/local\/bin\/nightly-sync.sh<\/code><\/pre>\n
Insert the following automated script:<\/p>\n
#!\/bin\/bash\nset -e\n\nTIMESTAMP=$(date +\"%Y-%m-%d_%H-%M-%S\")\nLOG_FILE=\"\/var\/log\/rsync-backup.log\"\n\necho \"[${TIMESTAMP}] Starting Rsync Backup...\" >> \"$LOG_FILE\"\n\nrsync -aqz --delete   -e \"ssh -i \/root\/.ssh\/backup_key -p 22\"   --exclude=\"*.log\"   --exclude=\"cache\/*\"   \/var\/www\/html\/   backupuser@remote_backup_ip:\/backups\/current\/ >> \"$LOG_FILE\" 2>&1\n\necho \"[$(date +\"%Y-%m-%d_%H-%M-%S\")] Backup Completed Successfully.\" >> \"$LOG_FILE\"<\/code><\/pre>\n
Make the script executable and schedule it in crontab:<\/p>\n
# Grant execution permissions\nsudo chmod +x \/usr\/local\/bin\/nightly-sync.sh\n\n# Edit system crontab\nsudo crontab -e\n\n# Run every night at 2:30 AM\n30 2 * * * \/usr\/local\/bin\/nightly-sync.sh<\/code><\/pre>\n
Frequently Asked Questions (FAQ)<\/h2>\n
\n
How do I perform a safe dry run before running rsync with –delete?<\/h3>\n
Always add the -n<\/code> or --dry-run<\/code> flag: rsync -avzPn --delete ...<\/code>. Rsync will print exact logs of which files would be transferred or deleted without touching the actual disks.<\/p>\n
Can rsync preserve extended attributes and ACLs?<\/h3>\n
Yes. Add -A<\/code> (preserve Access Control Lists) and -X<\/code> (preserve extended attributes\/SELinux contexts) to your rsync command flags.<\/p>\n<\/div>\n
\n
\ud83d\udd17 Recommended Related Technical Guides<\/h3>\n