Having a backup and having a reliable, restorable backup are two different things. Many business owners discover this when their site breaks and their backup turns out to be corrupt, incomplete, or gone. Here's how to do it correctly.
What to Back Up
A complete WordPress backup requires both: Files — your WordPress installation, wp-content folder (uploads, plugins, themes). Database — all your content, settings, users, and WooCommerce orders. Without both together, recovery is impossible.
How Often?
Daily minimum for any business WordPress site. WooCommerce stores processing orders: consider hourly database backups. Truly static informational sites: weekly may be acceptable.
Where to Store Backups
NEVER only on the same server as your site. If your server fails, both your site and your "backup" disappear simultaneously. Store backups offsite: Amazon S3, Google Drive, Dropbox, or Backblaze B2. Follow the 3-2-1 rule: 3 copies, on 2 different storage types, with 1 offsite.
How Long to Keep Backups
Minimum 30 days. Some hacks are not immediately obvious — you may not discover a compromise until weeks after it happened. Thirty days of history gives you a clean restore point.
Most Critical: Test Your Backups
An untested backup is not a backup you actually have. Untested backups fail more often than you'd expect. Test restoring from backup at least quarterly.
Recommended Plugins
UpdraftPlus: Most popular, reliable, free tier handles basics well. BackupBuddy: Premium, excellent for complete site backups. WPVivid: Solid free alternative with multiple remote destinations.
What Restoring From a Backup Actually Involves
Knowing you have a backup is only half the picture — restoring one under pressure is a different experience than making one on a calm afternoon. A full restore means replacing both your current files and your current database with the backup versions, which means anything created after that backup's timestamp (new orders, new comments, new content) will be lost unless you can recover it separately. Most backup plugins offer a one-click restore, but it's worth doing a full restore at least once in a low-stakes moment — to a staging site, not live — so you know exactly what the process looks like and how long it takes before you're doing it for real during an actual emergency.
How Backup Plugins Actually Work Behind the Scenes
Understanding what a backup plugin does in the background helps explain why some backups quietly fail. Every backup job actually does two separate things: it exports your database (running a series of queries similar to a mysqldump that turn each table into a text file) and it archives your files — themes, plugins, uploads — into a compressed zip. On a small site this finishes in seconds. On a large site with years of media uploads or a WooCommerce store with a long order history, it can take much longer, and that's where problems tend to start.
Shared hosting environments enforce strict limits on how long a single process can run and how much memory it can use. If a backup job runs past those limits partway through, many plugins simply stop or produce a partial, unusable archive — often without a clear error message pointing to what happened. This is one reason backups on larger sites are frequently split into smaller chunks rather than run as one continuous job, and why full backups are best scheduled during low-traffic hours rather than in the middle of a busy afternoon when server resources are already stretched thin.
It also helps to understand the difference between a full backup and an incremental one. A full backup captures everything from scratch every time — thorough, but slow and storage-heavy. An incremental backup captures only what changed since the last backup, then relies on the original full backup plus a chain of incremental snapshots to reconstruct a restore point. Incremental backups are lighter on your server and your storage bill, but the whole chain has to stay intact — if one file in the middle goes missing or gets corrupted, everything after it can become unusable. That's why most reliable strategies still run a fresh full backup on a regular cycle even when daily incrementals are also in place.
Common Questions
Does my hosting company's backup count as my only backup?
It shouldn't be your only one. Host-provided backups are convenient but live on the same infrastructure as your site — if your host has an outage or billing issue, you could lose access to both your site and its backups simultaneously. Keep at least one copy stored independently.
How long does a full restore usually take?
For a typical small business site, anywhere from a few minutes to about an hour, depending on site size and whether you're restoring through a plugin or manually via files and database. WooCommerce stores with large media libraries generally take longer.
Need help with your WordPress site?
If managing and testing backups yourself isn't how you want to spend your time, our WordPress support plans include daily automated backups with a 30-day history, plus security, speed, and expert support. Losing listing data is exactly why we back up real estate and property management sites daily. Contact us for a free evaluation.
Call (424) 234-8528 for a free evaluation →