- Back up most WordPress sites daily, and an active WooCommerce store every hour or on every order.
- A complete backup has both the files (uploads, themes, plugins) and the database. One without the other cannot restore a working site.
- Follow the 3-2-1 rule: 3 copies, on 2 kinds of storage or locations, with 1 copy off-site.
- A backup you have never restored is a guess. Test it by restoring into a separate copy of the site.
- Even on managed hosting, keep one copy you own, so you can leave any host with your data.
How often should I back up a WordPress site?
Back up most WordPress sites once a day. Back up an active WooCommerce store more often: every hour, or on every order, because a daily backup can lose a full day of sales. A brochure site that rarely changes can be backed up weekly. Match the interval to how much work you can afford to lose.
Behind "how often" is a business question: how many hours of orders, posts or comments could you redo by hand? That number is your recovery point, the most data you can afford to lose. If losing four hours of orders would hurt, a nightly backup is not enough. Choose the interval first, then a host and tools that can meet it.
| Site type | How often to back up | How long to keep it |
|---|---|---|
| Brochure or low-change site | Weekly, plus before every change | 30 days |
| Business site or active blog | Daily | 30 to 60 days |
| Active WooCommerce store | Hourly, or on every order | 60 to 90 days |
| Membership or forum site | Hourly to daily, by activity | 60 to 90 days |
A starting point. Back up more often when losing an hour of data would cost you money or trust.
Take a manual backup right before any risky change: a plugin update, a theme swap, a bulk edit or a PHP version change. Scheduled backups protect you from accidents. A backup taken just before a change protects you from that change.
What is the best WordPress backup strategy?
The best strategy has four parts. It runs on a schedule without you. It keeps copies away from the server it protects. It captures files and database together. And it is proved by restoring. Miss one and you have a backup that looks fine in a dashboard but fails on the day you need it.
Many site owners install a backup plugin, set it to run nightly and never look again. That leaves two gaps. A backup stored on the same machine as the site is lost with that machine. And a job that reports success has only proved a file was written, not that the file can rebuild your site.
What is the 3-2-1 backup rule in plain terms?
Keep 3 copies of your data, on 2 different kinds of storage or locations, with 1 copy off-site. The live site counts as one copy. So you need at least two more, and one of them must be somewhere a failure of your server cannot reach.
| Rule | In plain terms | A WordPress example |
|---|---|---|
| 3 copies | The live site plus two backups | The running site, a backup with your host, and a copy elsewhere |
| 2 kinds of storage or locations | Do not keep every copy in one place | One backup with your host, one in separate cloud storage |
| 1 off-site | One copy your server cannot destroy | A copy in storage you control, with a different provider |
The point of 3-2-1: no single failure (a bad disk, a hack, a deleted account) can wipe out every copy at once.
A backup on the same server is not enough
If your only backup sits on the machine that runs your site, one disk failure, one ransomware attack or one compromised account takes both. The off-site copy is the point of the rule.
What does a complete WordPress backup include?
Two parts, captured together: the files and the database. The files are your uploads, themes, plugins and configuration. The database holds your posts, pages, products, orders, users, settings and comments. Restore one without the other and the site will not work.
| Part of the site | Where it lives | What you lose without it |
|---|---|---|
| Media and uploads | wp-content/uploads | Every image, PDF and attachment on the site |
| Themes and plugins | wp-content/themes, wp-content/plugins | Your design and all custom features |
| Configuration | wp-config.php and related files | Database login details, security keys and site settings |
| Content and settings | The MySQL or MariaDB database | All posts, pages, products, orders, users and options |
A files-only backup restores an empty shell. A database-only backup restores content with no images and no theme.
Check your backup has both
This is a common backup mistake. A plugin backs up wp-content but skips the database, or exports the database but not the uploads folder. Open your latest backup and confirm both are there, taken at the same time.
Why do untested backups fail when you need them?
Because a backup job reports success when a file is written, not when that file can rebuild your site. The archive can be cut short. The database copy can be inconsistent. A plugin can run out of memory or time halfway through. The dashboard still shows a green tick, and you find out during a restore.
On a large site, a backup plugin can hit PHP's memory or time limit and stop mid-archive, leaving a file that looks the right size but is incomplete. A database copy taken while orders are being written can catch a half-finished transaction. Nothing flags either, because nothing tested the copy.
How G7Cloud tests its backups
Every night we restore a rotating sample of backups into a throwaway sandbox, load the database and check the files came back. Completed backups also get a nightly integrity check. A bad copy shows up in our checks, not on the day you need it.
“Ask your host one question: when was the last successful test restore? If the answer is a shrug, you do not have backups. You have hope.”
How long should I keep WordPress backups?
Keep at least 30 days for a typical business site, and 60 to 90 days for a shop or membership site. The damage you most need to undo (malware, a bad plugin, slow data corruption) often goes unnoticed for days. Keep only three days and every copy may already contain the problem.
Layered retention handles this well: daily backups for recent weeks, weekly ones for a few months and a monthly one for the year. You can undo a recent mistake precisely and still reach far back for a problem found late. G7Cloud keeps backups this way: 14 daily, 8 weekly and 12 monthly copies, so about a year of history.
Match retention to your risk, not to storage cost
Storage is cheap. A shop that cannot roll back to before a fraud is expensive. If you handle orders or personal data, keep 90 days or more, and catch problems sooner with the practices in our WordPress security guide.
How do I run a restore drill without breaking my live site?
Restore a backup into a separate copy of the site, never over the live one. A drill proves your backup rebuilds a working site, and it takes about half an hour. The rule that keeps it safe: restore into a new environment, check it there, and never point the restore at your live files or database.
| Step | What you do | What it proves |
|---|---|---|
| 1. Pick a backup | Choose a recent scheduled backup, not a fresh manual one | The routine backups are the ones you rely on |
| 2. Create a staging site | Set up an empty staging site or a local copy, separate from the live one | The restore never touches your live site |
| 3. Restore into it | Restore the files and database into the staging copy | The archive and database copy are complete and readable |
| 4. Log in and click around | Load the home page, an inner page and wp-admin; check the images | The site works, rather than only unpacking |
| 5. Note the time | Record how long the restore took from start to finish | You know your recovery time before an incident |
Do this once a quarter. The first drill almost always finds something: a missing upload, a wrong URL, or a slower restore than you expected.
Never test by restoring over the live site
If the backup is bad, restoring it over your live site can destroy the good data you still have. Restore into a staging or local copy instead. If your host can restore a single file, practise with one file first.
Do I still need my own backups on managed hosting?
Yes. Keep at least one copy you own, away from your host. Host backups protect you from server failure. Your own copy protects you from rarer problems: a billing dispute, a suspended account, or simply deciding to leave. If every copy lives with one provider, that provider controls your exit.
A host that does backups well removes most day-to-day risk, which is one of the main differences between managed and shared hosting. The 3-2-1 rule still applies, and the off-site copy is the one to hold yourself.
Backups on G7Cloud
G7Cloud is hosted in the UK, on servers we own and run ourselves. Every site is backed up daily to our UK servers, and a monthly disaster-recovery copy is stored with Cloudflare in the EU. From the dashboard you can restore the whole site, just the files, just the database, or a single file or folder, and download any backup to keep a copy of your own. See how our backups work.
Judging a host's recovery promises rather than your own? How to read a hosting SLA explains what recovery targets commit a provider to, and which exclusions matter.
Frequently asked questions
How often should I back up my WordPress site?
Back up most WordPress sites daily. Back up an active WooCommerce store hourly or on every order, because a daily backup can lose a full day of sales. A brochure site that rarely changes can be backed up weekly, as long as you also take a manual backup before any change.
What is the 3-2-1 backup rule for WordPress?
Keep 3 copies of your data, on 2 different kinds of storage or locations, with 1 copy off-site. Your live site is one copy, so you need at least two more, and one must be somewhere a failure of your server cannot reach, such as your own cloud storage.
Does a WordPress backup include the database?
It must. A complete backup captures the files (uploads, themes, plugins, configuration) and the database (posts, pages, products, orders, users and settings) at the same time. A files-only backup restores an empty shell, and a database-only backup restores content with no images or theme.
How do I test a WordPress backup?
Restore a recent scheduled backup into a separate staging or local copy, never over the live site. Log in, load a few pages, and check the images and admin area work. This proves the backup rebuilds a working site and tells you how long recovery takes. Do it once a quarter.
Do I need my own backups if my host already backs up my site?
Yes. Host backups protect you from server failure, but keep at least one copy you control, for example a downloaded backup in your own cloud storage. It protects you from a suspended account, a billing dispute or simply choosing to leave, and it covers the off-site part of the 3-2-1 rule.
How long should I keep WordPress backups?
At least 30 days for a typical business site and 60 to 90 days for a shop or membership site. Malware and data corruption often go unnoticed for days, so a short window can leave every copy already affected. Layer daily, weekly and monthly backups to reach back further without keeping every day.
About G7Cloud Engineering
Articles written by the engineers who build and run G7Cloud: UK managed hosting and the AI Website Builder. We write about what we operate every day: containers, backups, databases, and the small-business websites that run on them.
More about G7Cloud →