A backup is the one thing that turns a disaster into an inconvenience. A hacked plugin, a failed update, a deleted database or a dead server will all hurt a business website, but with a recent, tested backup you can recover. Without one, you may lose orders, customers and content you cannot recreate.
This WordPress backup strategy guide explains what to back up, how often, where to keep it and how to prove that it works. It draws on WordPress.org’s official backup guidance and on the CISA ransomware guide, which also covers offline backups. It is written for store owners, with clear steps your developer or host can follow.
| Backup question | Guidance |
|---|---|
| What to back up | Database and files (core, plugins, themes, uploads, config) |
| How often | Weekly for small sites, daily for busy ones, and before any upgrade |
| Where | At least 3-5 recent copies in different locations, including off-site |
| How to trust it | Keep offline, encrypted copies and test restores regularly |
What a WordPress backup strategy must contain
According to WordPress’s backup documentation, a WordPress site has two parts, and you need both to fully restore it:
- The database, which holds posts, pages, comments, orders and settings. It is stored separately from your web files, so downloading the WordPress folder does not capture it. You export it as a dump file, for example in SQL format.
- The files, meaning WordPress core, plugins, themes, uploads and configuration files such as
wp-config.phpand.htaccess.
The documentation says to back up the database first, then the files, and keep both in the same backup set created around the same time. On restore, put the files back first and then import the database.
Recovery point and recovery time in plain words
Two phrases from disaster planning make backup choices easier. Recovery point is how much recent data you can afford to lose, measured in time. If your backup runs at midnight and your site fails at 5pm, you lose 17 hours of orders and edits. Recovery time is how long you can be offline before the damage becomes serious.
A small brochure site may happily accept a weekly backup and a day of downtime. A busy store may need database backups every few hours and a restore within an hour. Writing the two numbers down turns a vague worry into a design target for your WordPress backup strategy, and it tells your host or developer exactly what to build.
How often should you back up?
WordPress’s guidance is simple: small sites with few changes can back up roughly weekly, high-activity sites daily, and you should always back up before an upgrade or a move. For a store, the right frequency depends on how many orders you can afford to lose. If you take orders all day, daily backups may still be too little, and you should ask your host or developer about more frequent database backups.
Where to keep copies
The WordPress guidance recommends keeping at least three to five recent backups in different locations, such as your hosting server, cloud storage and your own computer, and using different media where possible. A widely used rule of thumb is three copies, on two kinds of storage, with one stored off-site.
The CISA ransomware guide, written by CISA and MS-ISAC with the FBI and NSA, adds an important point: maintain offline, encrypted backups of critical data and test them regularly. Its reasoning is that many ransomware variants try to find and delete or encrypt accessible backups, so a backup that lives on the same server as the site may disappear with it. The guide also advises caution with immutable storage, which does not meet compliance criteria for certain regulations.
What a backup plugin should do
Whether your WordPress backup strategy relies on a plugin or a host tool, check that it does the following:
- Backs up both the database and the files, on a schedule you control.
- Sends copies to storage outside your web server, such as a separate cloud account.
- Keeps several restore points, not only the latest one.
- Encrypts the backup or lets you protect it with a password.
- Notifies you by email when a backup fails, so you do not find out during a crisis.
- Offers a straightforward restore, ideally to a staging site as well as to production.
Be careful with large uploads folders and big databases, since some tools time out on cheap hosting. Run a manual backup once to confirm that it completes, and note how long it takes.
Why host backups are not enough
Many hosts offer backups, and they are useful, but WordPress’s guidance notes that hosts usually back up the whole server and that getting a copy of your site back from them can be slow. You also depend on the host’s retention period and on a support ticket during a crisis. Treat host backups as one layer of your WordPress backup strategy, and keep your own as well.
What to do with WooCommerce orders between backups
A store changes constantly, and orders placed between two backups are the ones you can lose. If you restore last night’s backup, the orders taken since then may be missing from your site, even though the payment gateway recorded the money. That is a painful mismatch.
Two habits reduce the risk. First, increase the database backup frequency during busy periods. Second, keep your payment gateway and email records, because they let you rebuild missing orders by hand if needed. After any restore, compare recent gateway payments with the orders in WooCommerce, and contact customers if something is missing. Build this process into your WordPress backup strategy in advance, so you are not inventing it in the middle of an incident.
Five steps to a WordPress backup strategy that works
Step 1: Decide what you can afford to lose
For this WordPress backup strategy, choose a recovery point (how much recent data you can lose) and a recovery time (how long you can be offline). A store taking daily orders may accept losing at most a few hours of data and a few hours of downtime. These two numbers drive everything else.
Step 2: Automate the backups
Use a backup plugin or a host-level tool to run backups on a schedule. WordPress’s documentation recommends also making an occasional manual backup to confirm the automated process really works.
Step 3: Store copies in separate places
Send backups to storage outside your web server, in a different account. Keep at least one copy that your main WordPress login cannot delete or encrypt, in line with CISA’s advice about offline copies.
Step 4: Protect the copies
Encrypt backups, restrict who can access them and use strong credentials, because a backup contains customer data. Our guide to IT outsourcing data checks in the UAE covers who should have access.
Step 5: Test a restore
Restore your latest backup to a staging site and check that pages, products, orders and the admin all work. CISA’s guide says to regularly test the availability and integrity of backups in a disaster recovery scenario. A WordPress backup strategy that has never been restored is a hope, not a plan.
When your WordPress backup strategy needs extra backups
- Before any WordPress, plugin, theme or PHP update.
- Before a sale or major campaign, as in our White Friday readiness guide.
- Before moving host, domain or CDN.
- After a security incident, once the site is clean.
WordPress backup strategy and security
A backup helps you recover from an attack, but it does not stop one. Combine it with the steps in our guides to WordPress plugin security and the PHP vulnerability, and keep a note of your backup locations and who can restore them.
Our website maintenance service sets up automated off-site backups and tests restores for you.
Retention: how long should you keep backups?
Keeping every backup forever is costly, and keeping too few leaves you stuck if a problem is found late. A common approach is to keep daily copies for a couple of weeks, weekly copies for a couple of months and a monthly copy for longer. This lets you go back before a slow-burning problem began, such as malware that was installed weeks ago.
Check with your accountant or lawyer whether any records you hold must be kept for a minimum period, and whether backups containing customer data need to be deleted on request. Document the retention rule as part of your WordPress backup strategy, and make sure the storage account that holds the copies has its own strong password and two-factor login.
A one-page recovery runbook
Write a single page, the heart of any WordPress backup strategy, that anyone on your team can follow in a crisis. List where the backups live, who has access, how to restore to staging and to production, who to call at the host and how to check that orders and customer data are complete afterwards. Include the order of steps from the WordPress documentation: files first, then the database.
Print it or store it somewhere that does not depend on your own website being online. During an outage, a clear page is worth far more than a clever tool, and the exercise of writing it often reveals gaps you can fix while everything is calm.
Backups for sites with large media libraries
A WordPress backup strategy has to cope with size: stores with thousands of product images create backups that are slow and expensive to store. Consider incremental backups that copy only what changed, store the uploads folder separately from the database and check that your backup tool does not time out. Remember that regenerated image sizes can be rebuilt, but original files cannot, so protect the originals first. Review storage costs every quarter and delete old restore points according to your retention rule.
Want backups you can actually restore?
We can set up automated off-site backups, protect them and rehearse a restore on staging so you know recovery works before you need it.
Frequently Asked Questions
What should a WordPress backup include?
Both the database and the files. WordPress’s documentation says you need both to fully restore a typical site, including core, plugins, themes, uploads and configuration files.
How often should I back up my WooCommerce store?
WordPress suggests weekly for small sites and daily for high-activity ones, and always before upgrades. A store with frequent orders may need more frequent database backups, so set it by how much data you can afford to lose.
Are host backups enough?
They help, but they are one layer. Keep your own off-site copies, including one that your site login cannot delete, and test restoring them.

