How to Set Up Offsite Weekly Backups for Your Small Business Website
Summary
This guide helps you troubleshoot and resolve: How to Set Up Offsite Weekly Backups for Your Small Business Website. Follow the steps below to fix the issue.
Common Causes
Relying on a single hosting provider for your website's data creates a single point of failure. If your infrastructure provider experiences a permanent failure or enters liquidation, your website assets could be lost permanently. Implementing automated offsite weekly backups ensures your business can recover quickly from hosting failures, accidental deletions, or provider collapses by storing copies of your data in a geographically separate location.
Detailed Instructions
1. Identify Critical Website Assets
Before scheduling backups, determine which files and databases are essential for your website's operation. Typically, this includes your website root directory, configuration files, and your database (such as MySQL or MariaDB).
2. Choose an Offsite Destination
Store your backups away from your primary hosting environment. Recommended options include:
- Object storage services (e.g., Amazon S3 or Google Cloud Storage).
- A separate remote server via SFTP.
- Dedicated backup cloud providers.
3. Configure Automated Weekly Backups
If you use a control panel like cPanel, follow these steps:
- Log in to your hosting control panel.
- Navigate to Files > Backup or click the Backup Wizard icon.
- Select Full Backup to include all website files and databases.
- Choose your offsite destination and enter your remote server credentials.
- Enable encryption using AES-256 or a similar industry-standard encryption protocol for all offsite data.
- Set the schedule to Weekly. For Australian small businesses, a low-traffic time is typically between 11:00 PM and 4:00 AM AEST/AEDT on weekdays, or weekends if your traffic patterns allow.
- Define a retention policy to keep between 4 and 8 weekly backups. This ensures you have approximately two months of recovery points.
- Click Save or Schedule Backup.
For command-line users or non-cPanel environments, automate this using a cron job and a shell script that utilises tar for files and mysqldump for databases. Ensure your script includes flags for encryption and handles large databases by utilising --single-transaction to avoid locking tables and prevent timeouts.
4. Bandwidth and Connection Considerations
When backing up to offsite destinations from Australia, consider your available upload bandwidth. Large backup files may saturate your connection during the transfer window. If you use SFTP, ensure that SSL/TLS is enabled to encrypt the connection tunnel in addition to the file-level encryption.
5. Verify Backup Integrity
After the first automated run, verify that the backup file exists at your offsite destination and that the file size is consistent with your website's data volume. Check your backup logs for any error messages regarding failed connections, permission denied errors, or mid-process failures.
6. Monitoring and Alerting
Configure monitoring and alerting for backup failures. Set up email notifications or integrate your backup tool with a monitoring service to alert you immediately if a scheduled backup does not complete successfully. This prevents you from discovering a backup gap only during an emergency.
7. Perform Independent Restoration Testing
A backup is only useful if it can be restored. Schedule a quarterly test to restore your website to a staging environment or a local machine using phpMyAdmin for the database and an FTP client for the files.
- Restore the database and verify database integrity by running
CHECK TABLEcommands or ensuring the application can connect and read data without errors. - Restore website files and verify data integrity by opening random files and checking that content matches the production environment.
- Update database connection strings in your configuration files (e.g.,
wp-config.phpor.env) to reflect the new staging environment's database host, username, and password. - Check file permissions and ownership. Ensure the web server user (e.g.,
www-dataorapache) owns the restored files and that directory permissions are set correctly (typically 755 for directories and 644 for files).
8. Managing Destination Credentials
If your offsite destination credentials change, update them immediately in your backup configuration. Failed authentication will cause backups to fail silently if not monitored. Re-verify the connection after updating credentials to ensure the next scheduled run completes successfully.
If you encounter issues configuring your offsite backups or require assistance with a restoration, Open a Ticket.
Still Having Issues?
💻 Open a Ticket