WooCommerce automated backups: database or full backups, where to store them and how to test restoration

November and December are when a WooCommerce store generates the most revenue and faces the highest risk. More orders per day means more data changing every hour: if there is no backup, or if it cannot be restored, a technical problem during Black Friday isn't just an inconvenience—it's lost revenue. This guide is for store managers who aren't sysadmins: no command lines, just the right questions to ask yourself before you actually need them.

Database backup or full backup: they are not the same thing

WooCommerce's database contains orders, customers, products and settings. But it does not contain product images, the theme, installed plugins and their configuration files: those live in the server's wp-content folder as files. A backup that copies only the database, if the site is lost, will bring it back with the right content but without photos, without the theme and without plugins to reinstall one by one. For an e-commerce store you need a backup covering both: files and database, in the same package and at the same moment, so that the references between them remain consistent.

How often: based on daily orders

There is no single backup frequency that works for all stores. The practical criterion is simple: how many orders are you willing to lose if the most recent backup is also the last one available.

Orders per day	Recommended minimum frequency	What happens otherwise
Up to 5–10	Daily backup	You lose at most one day of orders
10–30	Daily backup + copy before every update	A failed plugin update rolls back just a few hours
Over 30, or November–December peak season	Multiple backups per day or real-time	With only one daily backup you risk losing dozens of paid orders

To give a sense of what this means in financial terms, BlogVault provides a calculator on their site that links daily orders and average order value to the cost of a day's lost sales: with 40 orders a day and an average order value of $60, a day's revenue is $2,400—a figure to compare against the annual cost of a more robust backup plan.

Where to store copies: never on the same server

A backup saved in the same folder as the site, on the same hosting account, protects you from nothing: if the server fails, goes down under attack, or the host suspends the account for a payment issue, the backup disappears along with the site. The copy must always go to separate external storage: a cloud storage service (Google Drive, Dropbox, Amazon S3 or equivalent), or the backup plugin provider's own servers, if that service is offered.

Setting up automated backup: two approaches

Using a WordPress plugin

The most widely used WordPress backup plugins handle both files and database together, with scheduled automation and delivery to external storage. Comparing the official pages of major providers:

Plugin	Verified starting price	What it includes for a store
UpdraftPlus Premium	$70/year for 2 sites (Personal plan)	Scheduled file+database backups, delivery to external storage, incremental backups only in paid version
Jetpack Security	€8.95/month first year (then €18.95/month), annual billing	Real-time backups, 10 GB storage, one-click restore, malware scanning
BlogVault Personal	$49.50/year per site (discounted price, then $99)	Daily backup, 30 days history, 1-day staging site included
BlogVault WooCommerce	$249.50/year per site (discounted price, then $499)	Real-time backups, 365 days history, 6-month staging

BlogVault plans above the basic tier add more frequent backups and larger staging environments: according to their official pricing page, the Business plan includes backups every 12 hours, 90 days history and 30 days of staging site, whilst the WooCommerce plan goes up to customisable hourly backups with 365 days history and 6 months of staging. None of these plans is "right" in absolute terms: your choice depends on your daily order volume from the table above.

From your hosting control panel

Many hosting providers include an integrated automated backup system in their control panel, with adjustable frequency (daily or multiple times daily) and copies retained for a set number of days. The advantage is that you do not need to install anything on your site and backups happen at server level, covering everything without needing to configure files and database separately. Before relying on this alone, verify two things in your control panel: where the copies are stored (they must be on separate storage from your main site disk) and for how many days they remain available before being overwritten.

The restoration test: the step almost nobody does

A backup that has never been restored is a gamble, not a safety net. The file could be incomplete, the database could be corrupted, the restoration procedure could require steps no one has ever tried. The only way to know before you need it is to test on a staging site: a copy of your store separate from the live one, where you can upload the backup and verify that the site comes back with products, orders and theme intact, without touching the site your customers see.

Several of the plugins mentioned include integrated staging: BlogVault offers it on all plans, ranging from 1 day on the Personal plan to 6 months on the WooCommerce plan according to their official pricing page. Others, like UpdraftPlus, require a separate add-on to clone your site to a test environment. If your hosting provides a staging environment in the control panel, that works fine too: what matters is doing it, not which tool you use.

Before November–December: the essential checklist

• Verify that the backup covers files and database together, not just the database.
• Check that the copy is stored outside your site's server.
• Increase frequency if daily orders exceed 20–30.
• Run at least one restoration test on staging before traffic rises, not during.

UpdraftPlus, Jetpack and BlogVault are third-party products cited as market reference points.