Regular backups are essential for disaster recovery and data integrity. This guide explains how to create full and partial backups in cPanel, configure automated backup schedules, and securely store backups offsite.
Why Backups Are Critical
- Disaster Recovery: Protect against accidental deletions, malware, or server crashes.
 - Compliance: Many industries require regular backups for data protection.
 - Migration: Backups simplify moving your site to a new server.
 
Step 1: Manual Full Backup
- Log in to cPanel.
 - Navigate to Files → Backup.
 - Under Full Backup, click Download a Full Website Backup.
 - Choose Backup Destination:
- Home Directory (default)
 - Remote FTP Server (for offsite storage)
 
 - Enter your email to receive completion notifications.
 - Click Generate Backup.
 - Once complete, download the backup file from 
/home/username/. 
Step 2: Partial Backups
- Use Backup Wizard for:
- Home Directory Backup (website files)
 - MySQL Database Backup
 - Email Forwarders & Filters
 
 - This is useful for restoring specific components without overwriting everything.
 
Step 3: Automating Backups with Cron Jobs
To schedule backups:
- Go to Advanced → Cron Jobs.
 - Add a new cron job:
- Runs daily at 2 AM.
 
 - Verify backup settings in WHM → Backup Configuration (if you have root access).
 
Step 4: Offsite Backup Storage
- FTP/SFTP: Configure remote destination in backup settings.
 - Cloud Storage: Use scripts or plugins to push backups to:
- Amazon S3
 - Google Drive
 - Dropbox
 
 - Example using 
rclone: 
Step 5: Encrypt Your Backups
Before uploading backups offsite:
- Use 
gpgfor encryption: - Store encryption keys securely.
 
Step 6: Verify Backup Integrity
- Check file size and logs.
 - Test restore on a staging environment:
- Upload backup via File Manager.
 - Restore database via phpMyAdmin.
 
 
Troubleshooting
- Backup Fails: Check disk space and permissions.
 - Slow Backup: Exclude large log files or cache directories.
 - Restore Errors: Ensure correct PHP version and database credentials.
 
Security Best Practices
- Never store backups in 
public_html. - Rotate backups (keep at least 3 versions).
 - Monitor backup logs for errors.