Back to Blog

Safeguard Your WordPress Site with Complete Backup Solutions

TL;DRWordPress has no built-in backup feature, so you need your host’s backups, a backup plugin or service, or both. A complete backup includes the database and the wp-content files plus wp-config.php. Follow the 3-2-1 rule: three copies, on two different types of storage, with one kept offsite and away from your hosting account. Always take a fresh backup before updates and migrations, keep enough history to roll back past a problem you didn’t notice immediately, and test restores regularly.

Most site owners only think about backups after something goes wrong: a failed update, a compromised plugin, a host outage or an accidental deletion. By then it is too late to start. A dependable backup routine takes little time to set up and turns a serious incident into a routine restore.

Illustration for a guide to WordPress backup solutions

This guide covers what to back up, how often, where to store it, which tools to use and how to make sure your backups actually work.

What a WordPress backup needs to include

A WordPress site has two parts, and you need both to restore it:

  • The database. Posts, pages, users, comments, settings, ACF field values, WooCommerce orders and customers, and plugin data all live in MySQL or MariaDB.
  • The files. The wp-content directory holds your themes, plugins and uploaded media. Also include wp-config.php and any custom .htaccess or server rules.

WordPress core files can be downloaded again, so they are optional, but including them makes a full restore simpler. If your theme or custom plugins live in a Git repository, that is version control for code, not a backup of the site. You still need the database and uploads.

The 3-2-1 backup rule

The 3-2-1 rule is the standard approach for protecting data, and it applies directly to websites:

  • Keep three copies. The live site plus at least two backups.
  • Use two types of storage. For example, your host’s backup system and a separate cloud storage service.
  • Keep one copy offsite. At least one backup should live outside your hosting account, with separate credentials.

The offsite copy matters more than it may seem. If the only backups are inside your hosting account, a billing dispute, an account compromise or a platform-wide incident can take your site and your backups out at the same time.

Full and incremental backups

A full backup copies the entire site each time. It is simple and self-contained, but on large sites it is slow, uses a lot of storage and puts load on the server while it runs.

An incremental backup copies only what changed since the previous backup. It is faster, lighter on the server and makes frequent backups practical, including near real-time backups for busy WooCommerce stores. Restoring depends on the backup tool rebuilding the full site from the chain of increments, which good services handle automatically. Services such as BlogVault and Jetpack VaultPress Backup are built around incremental backups.

How often to back up and how long to keep backups

Match frequency to how much data you could afford to lose:

  • Brochure sites that change occasionally: daily backups are usually enough.
  • Busy content sites and membership sites: daily at minimum, more often when publishing heavily.
  • WooCommerce stores: hourly or real-time database backups, because every order between backups is data you would lose in a rollback.

Retention matters as much as frequency. Malware, a broken plugin or corrupted data may go unnoticed for weeks, and if every backup you hold was taken after the problem started, none of them help. A common pattern is to keep daily backups for at least 30 days, plus weekly or monthly copies for longer. Check your host’s and plugin’s retention limits and make sure they match your needs.

Host backups and plugin backups

Managed host backups

Managed WordPress hosts take automatic daily backups and let you restore with a few clicks. WP Engine runs daily backups and lets you create on-demand backup points before changes, and restore to production or staging. Kinsta runs daily automatic backups, lets you create manual backups, and offers more frequent backups as an add-on. These are the fastest way to roll back, and you should use them.

Their limitation is that they live with the host. They usually can’t be restored to a different provider directly, and they don’t satisfy the offsite part of the 3-2-1 rule on their own. Most managed hosts let you download a backup archive, and some can send copies to your own cloud storage.

Backup plugins and services

  • UpdraftPlus. A widely used plugin that schedules backups and sends them to remote storage such as Amazon S3, Google Drive, Dropbox or Backblaze B2. The premium version adds incremental backups, migration tools and more storage destinations.
  • BlogVault. A backup service that stores incremental backups on its own servers rather than yours, with staging, one-click restores and migration tools. Because the work happens off your server, it suits larger sites.
  • Jetpack VaultPress Backup. Automattic’s backup service, with real-time backups that capture each change, including WooCommerce orders, and an activity log for choosing a restore point.

Check your host’s policy before installing a backup plugin. Some managed hosts restrict backup plugins that store archives on the server, because those archives consume disk space and can create load. Never keep backup archives in a publicly accessible folder such as wp-content/uploads, where anyone who guesses the filename can download your database.

A sound setup for most business sites is host backups for quick rollbacks, plus a plugin or service sending encrypted copies to separate offsite storage.

Back up before updates and migrations, not after

Always take a fresh backup immediately before you change anything significant. That includes:

  • WordPress core, plugin and theme updates.
  • PHP version upgrades.
  • Migrations to a new host or domain.
  • Bulk content changes, imports and search-and-replace operations on the database.
  • Deploying new features or custom code.

The scheduled overnight backup isn’t enough here, because anything that changed since then, including new orders and form entries, would be lost if you have to roll back. On WP Engine and Kinsta, a manual backup takes moments. With WP-CLI, wp db export creates a database snapshot before you run a risky command.

Manual backups

Manual backups are useful as a one-off safety copy or when you are moving a site. To take one:

  1. Export the database. Use wp db export over SSH, phpMyAdmin’s export function, or your host’s database tools.
  2. Download the files. Use SFTP or rsync to copy wp-content and wp-config.php. Avoid plain FTP, which sends credentials unencrypted.
  3. Store the copy securely. Keep it in encrypted cloud storage or on an encrypted drive, because it contains user data and credentials.

Manual backups depend on someone remembering to take them, so they should supplement automated backups, not replace them.

Test your restores

A backup you have never restored is an assumption. Test a restore on a schedule, such as quarterly, and after changing backup tools or hosts:

  1. Restore a recent backup to a staging site or a local environment, never over production.
  2. Check that pages, media, menus and forms work, users can log in, and recent content is present.
  3. On WooCommerce sites, confirm recent orders and customer records are there.
  4. Note how long the restore took, so you know your realistic recovery time.

Restoring a site from backup

When you need to restore for real, work methodically:

  1. Identify the cause. If the site was hacked, a restore alone won’t close the hole. Find and fix the entry point, or the site will be compromised again.
  2. Choose the right restore point. Pick the most recent backup taken before the problem began, and note what data changed since, such as orders or form entries, so you can recover it separately.
  3. Restore files and database together unless you are certain only one was affected.
  4. Clear all caches and test the site thoroughly before announcing it is back.
  5. Review your setup. Use what happened to adjust backup frequency, retention or security.

Backups for agencies managing multiple sites

Agencies need consistency across every client site: the same backup standard, central monitoring of backup status, alerts when a backup fails, and a documented restore process anyone on the team can follow. Agree with each client who owns the hosting account and the offsite storage, so backups remain accessible if the relationship changes.

Frequently asked questions

Does WordPress have a built-in backup feature?

No. WordPress’s export tool only exports content as XML and doesn’t include media files, settings or plugin data. Use your host’s backups, a backup plugin or service, or both.

Are my host’s daily backups enough?

They are a good first layer, but they live with your host. Keep at least one additional copy in separate offsite storage to follow the 3-2-1 rule, and check how long your host retains backups.

Should I back up before or after updating plugins?

Before. Take a fresh backup immediately before updating so you can roll back cleanly if the update breaks something. Ideally, test updates on a staging site first.

How often should I test a backup restore?

At least quarterly, and whenever you change backup tools or hosts. Restore to staging or a local environment and check that content, media, logins and forms all work.

Leave backups to a team that checks them

Backups only help if they run, are stored safely and restore correctly. Our WordPress maintenance service includes daily backups to secure cloud storage, alongside carefully tested core, theme and plugin updates. Get a proposal for your site.

Get started now

Start with a risk-free, no obligation proposal delivered to your inbox in one business day or less.

Get Started
  • 5-Star Rated Technical Partner
  • 100% White-Label - Sign our NDA
  • 90-Day Code Guarantee
Hey Reliable logo

Welcome to Hey Reliable

We’d love to hear from you. Please use the form below or email info@heyreliable.com.

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Secret Link