Key Takeaways
- Multiple backup copies in different locations (3-2-1 rule)
- Backup both files AND database—they're separate
- Test restores regularly—untested backups aren't reliable
- Automate backups but verify they're running
- Know your Recovery Time Objective (RTO) and plan accordingly
When Backups Save You
I've had the call. The panicked call where someone's site is completely gone—hacked, corrupted, or accidentally deleted. In the best cases, we restore from backup and they lose a day's work. In the worst cases, they have no backup. Or they have a backup from six months ago. Or they have a backup they've never tested and it doesn't work.
Backup strategy isn't exciting until you need it. Then it's the most important thing in the world. A proper strategy means you can recover from almost any disaster—and know how long that recovery will take.
The 3-2-1 Rule
Keep at least 3 copies of your data, on 2 different types of storage, with 1 copy offsite. For WordPress: your live site, a local backup, and a cloud backup. If any one fails, you still have copies.
What to Backup
WordPress File System
- wp-content/themes/: Your theme files (especially custom themes)
- wp-content/plugins/: All installed plugins
- wp-content/uploads/: Media library, often the largest folder
- wp-config.php: Database credentials and site configuration
- .htaccess: Server configuration rules
WordPress Database
- All posts, pages, and custom post types
- Comments and user data
- Plugin settings and options
- Widget configurations
- Menu structures
Files Without Database = Broken Site
| Component | Changes How Often | Backup Priority |
|---|---|---|
| Database | Every content update | Critical - backup frequently |
| Uploads folder | When media added | Important - can be large |
| Theme files | Occasionally | Important - hard to recreate |
| Plugin files | On updates | Moderate - can reinstall |
| WordPress core | On updates | Low - easily reinstalled |
Backup Storage Options
Cloud Storage Services
- Amazon S3: Industry standard, highly reliable, pay for what you use
- Google Cloud Storage: Similar to S3, good integration with Google services
- Dropbox/Google Drive: Easy setup, may have storage limits
- Backblaze B2: Cost-effective S3 alternative
Local/Server Storage
- Server backup directory: Fast but same risk as live site
- Different server: Better isolation
- Local download: Manual but fully controlled
Managed Backup Services
- BlogVault: Real-time backups, easy restores
- VaultPress/Jetpack: Automattic's backup solution
- ManageWP: Multi-site management with backups
Geographic Separation
Store backups in a different geographic region than your hosting. If your hosting provider's data center has problems, your backups shouldn't be affected.
Encryption
Encrypt backups, especially if stored in the cloud. Your backup contains database credentials, user information, and potentially sensitive content. Protect it accordingly.
Backup Plugins
Popular Options
- UpdraftPlus: Most popular free option, many storage destinations
- BackWPup: Flexible scheduling, multiple backup jobs
- Duplicator: Great for migrations, also does backups
- All-in-One WP Migration: Simple export/import
Plugin Selection Criteria
- Supports your preferred storage destination
- Handles your site size (large sites need incremental backups)
- Scheduling flexibility matches your needs
- Restore process is straightforward
- Good track record and active development
Beyond Plugins: Server-Level Backups
For critical sites, consider server-level backup tools:
- cPanel/Plesk built-in backups
- Hosting provider backup services
- Custom scripts (mysqldump + rsync)
Backup Schedule
-
Determine backup frequency
How much data can you afford to lose? Daily backups mean at most one day's work lost.
-
Set retention policy
How many backups to keep? Daily backups for a week, weekly for a month, monthly for a year is common.
-
Schedule off-peak times
Run backups during low-traffic periods. Backups use server resources.
-
Verify automation
Check regularly that scheduled backups are actually running and completing.
| Site Type | Recommended Frequency | Retention |
|---|---|---|
| E-commerce | Real-time/hourly | 30+ days |
| Active blog | Daily | 14-30 days |
| Business site | Daily | 14-30 days |
| Portfolio/brochure | Weekly | 30 days |
| Development/staging | Before major changes | 7 days |
Testing and Recovery
Test Your Restores
A backup you haven't tested is a backup you can't trust.
- Set up a staging environment for restore testing
- Actually restore a backup—don't just assume it works
- Verify all functionality after restore
- Document the restore process
- Time how long restore takes
Recovery Objectives
- RTO (Recovery Time Objective): How quickly must you be back online?
- RPO (Recovery Point Objective): How much data can you afford to lose?
Your backup strategy should meet both objectives. If you need to be back online in an hour, make sure you can actually restore that quickly.
Disaster Recovery Plan
- Document step-by-step recovery procedures
- List who does what during recovery
- Include credentials and access information
- Test the plan periodically
Quarterly Restore Tests
Common Backup Mistakes
Mistakes to Avoid
- Only backing up files or only database: Need both
- Storing backups only on the same server: Server failure loses everything
- Never testing restores: Untested backups may not work
- Keeping backups forever: Fills up storage, makes finding right backup harder
- Not encrypting sensitive backups: Security risk if backup is accessed
- Assuming host backups are enough: You don't control them
- Not backing up before updates: Updates can break things
Before Any Major Change
Backup Strategy Checklist
A solid backup strategy isn't complicated, but it requires attention. Automate what you can, verify regularly, and test your restores. The time you spend on backup strategy is an investment in peace of mind.
When disaster strikes—and eventually it will—you'll be glad you can say "no problem, we'll restore from backup" instead of starting over from scratch.
Your Backup Checklist
- ✓ Database and files backed up together
- ✓ Backups stored in multiple locations
- ✓ At least one offsite copy
- ✓ Automated backup schedule
- ✓ Retention policy defined
- ✓ Restore process documented
- ✓ Regular restore tests scheduled
Frequently Asked Questions
How often should I backup my WordPress site?
Is my hosting provider's backup enough?
What's the difference between full and incremental backups?
How do I test if my backups work?
Need help with WordPress backup strategy?
I help organizations implement reliable backup systems for their WordPress sites. Let's discuss your disaster recovery needs.