All Guides
Security + Infrastructure

Set Up Website Backup & Recovery

Configure automated backups so you can restore your site in minutes if anything goes wrong.

Most managed WordPress hosts include daily backups. Check your hosting dashboard first—you might already be covered.

This guide covers: How to check if you have backups, how to set them up if you don’t, and how to verify they actually work.

What this covers: Checking if your host already provides backups, setting up UpdraftPlus with off-site storage, choosing backup frequency by site type, and testing your restore process to verify backups actually work.

Who it’s for: WordPress site owners who need reliable backups and a tested recovery plan in case of data loss, hacks, or failed updates.

Key outcome: You’ll have automated daily database backups and weekly file backups stored off-site, with a verified restore process you’ve tested at least once.

Time to read: 5 minutes

Part of: Security & Infrastructure series

Check Your Current Backup Status

Managed WordPress hosts (usually automatic):

  • WP Engine – Daily backups, 40+ checkpoints, one-click restore
  • Kinsta – Daily automatic + manual, 14-30 day retention
  • SiteGround – Daily backups in Site Tools → Security → Backups
  • Bluehost – Check My Sites → Backups

E-commerce platforms (usually automatic):

  • Shopify – Automatic product/order data backup
  • BigCommerce – Daily store backups
  • WooCommerce – Depends on your host

If your host does daily backups: You’re covered for most scenarios. Consider adding an off-site backup (see below) for extra safety.

Set Up Backups (If Needed)

For WordPress sites without host-provided backups:

Option 1: UpdraftPlus (Recommended)

  1. Install UpdraftPlus (free)
  2. Go to Settings → UpdraftPlus Backups
  3. Click “Settings” tab
  4. Set backup schedule:
    • Files: Weekly
    • Database: Daily
  5. Choose remote storage (Dropbox, Google Drive, or Amazon S3)
  6. Save and run your first backup

Why remote storage matters: If your server dies, your backup dies with it. Always store backups off-site.

Option 2: BlogVault (Premium)

BlogVault ($89/year) offers:

  • Real-time incremental backups
  • One-click restore
  • Staging environment included
  • 365-day backup history

Worth it if backups are critical to your business.

Option 3: Jetpack Backup

Jetpack Backup ($10/month) includes real-time backups and easy restore through WordPress.com interface.

What Gets Backed Up

A complete backup includes:

  • Database: Posts, pages, comments, users, settings
  • wp-content/uploads: Media files, images
  • wp-content/themes: Your theme files
  • wp-content/plugins: All installed plugins
  • wp-config.php: Site configuration

Not typically backed up: WordPress core files (you can reinstall these).

Test Your Restore

A backup you haven’t tested isn’t a backup.

Once a quarter, verify your backup works:

  1. Set up a staging site or local environment
  2. Download your latest backup
  3. Restore it to the test environment
  4. Verify the site works (check pages, posts, media, functionality)

Managed hosts make this easy: Most have “restore to staging” buttons.

Backup Frequency Guidelines

Site Type Database Backup Files Backup
Blog (few updates/week) Daily Weekly
Business site (regular updates) Daily Daily
E-commerce (orders/transactions) Real-time or hourly Daily
Membership site Real-time or hourly Daily

Off-Site Backup Storage

Store backups in at least one location separate from your hosting:

Free options:

  • Google Drive (15GB free)
  • Dropbox (2GB free)

Better options:

  • Amazon S3 ($0.023/GB/month)
  • Backblaze B2 ($0.005/GB/month)

UpdraftPlus connects to all of these directly.

When Disaster Strikes

If you need to restore:

  1. Don’t panic. Your backup has you covered.
  2. Access your backup: Host dashboard, UpdraftPlus, or your remote storage
  3. Restore database first: This brings back your content
  4. Restore files: This brings back media and customizations
  5. Verify: Check that everything works
  6. Update passwords: If the issue was a hack

Testing Your Backup and Restore

  • Daily database backups are running
  • Weekly (or more frequent) file backups are running
  • Backups are stored off-site (not just on your server)
  • You’ve tested a restore at least once
  • You know how to access and restore from your backups

Sources

Website Backup Questions Answered

How often should I back up my website?

Daily for sites with frequent content changes (blogs, e-commerce). Weekly for mostly-static sites. Always run a manual backup before updates, theme changes, or plugin installations. Store at least 30 days of backup history.

Where should I store website backups?

Off-site, in a different location from your hosting server. Use cloud storage like Amazon S3, Google Cloud Storage, or Dropbox. Never rely solely on your host”s backups. Follow the 3-2-1 rule: 3 copies, 2 different media types, 1 off-site.

How do I test if my backup actually works?

Restore your backup to a staging environment at least quarterly. A backup you have never tested is not a backup. Most managed WordPress hosts offer one-click staging. For manual setups, restore to a subdomain and verify all pages, forms, and functionality work.

Does my hosting provider back up my site automatically?

Most managed hosts (WP Engine, Kinsta, SiteGround) include daily backups. Cheap shared hosting often does not, or only keeps 1-2 days. Always verify your host”s backup policy in writing and maintain your own independent backups regardless.

✓ Your Backup and Recovery System Is Tested and Running

  • Automated daily backups are running and include both the database and all site files
  • Backups are stored in at least two separate locations (e.g., server + offsite cloud storage)
  • You have successfully completed a full test restore to a staging environment
  • Backup retention keeps at least 30 days of daily snapshots and 3 months of weekly snapshots
  • Backup completion notifications are configured and someone is monitoring them

Test it: Download your most recent backup, restore it to a local or staging environment, and verify the site loads correctly with all content and functionality intact.