Home / Blog / Business Applications and Automation / How to Plan Backups for an Online Store
For a brochure site, a backup is a convenience. For an online store, it is the difference between a bad day and a business-ending one. Orders, customer records, stock levels, payment data and product content all change constantly, and every hour without a backup is an hour of orders that cannot be recovered if the server fails, the database corrupts, or ransomware encrypts the store.
This guide helps you plan backups for a store in business terms first — how much you can lose, and how fast you must recover — and then turns those answers into a schedule, a storage plan, and a test routine.
Every backup plan rests on two decisions, and they should be made by the business owner, not by the server:
Write both numbers down and get them agreed. They decide the frequency, the storage, and the budget — and they stop the backup conversation from being about gigabytes instead of about the business.
A store has more moving parts than its files. Your backup must cover all of these:
wp-content/uploads directory — product images, downloadable products, and media. A store with many product images can have a large uploads folder; do not discover its size during a restore.There is no universal schedule, but the principle is simple: the busier the store, the more often the database must be backed up.
| Store profile | Database | Full files + database |
|---|---|---|
| A few orders a week | Daily | Daily or every other day |
| Tens of orders a day | Every 6 hours, or hourly at peak | Daily |
| Hundreds of orders a day | Hourly, or continuous replication plus hourly dumps | Daily, with weekly full copies retained longer |
| Seasonal peaks and sales | Increase frequency before the sale, and keep a pre-sale backup | Before and after the sale |
Files change less often than the database, so a daily full backup usually covers them — but a store that adds products daily should back up files daily too. The key rule is that a backup taken before a big change (a sale, a plugin update, a migration) is worth more than one taken after it. Take a snapshot before risky changes as well — see Server Snapshots vs Backups — but remember that a snapshot is not a backup.
Follow the 3-2-1 rule: three copies of your data, on two different systems, with one copy off-site. For a store, that means:
Three rules make the copies real rather than theoretical:
Keep more than the last backup. A common retention ladder for a store is:
Longer retention matters because corruption and compromise are not always noticed immediately. Ransomware can sit quietly for days before it encrypts; a database error can corrupt data gradually. If you only keep the last two days, every copy you have may already contain the problem. A monthly copy from before the incident is the one that saves you.
Check any legal or tax requirement for how long order and customer records must be retained in your jurisdiction — that requirement may set the minimum, not your preference.
A backup plan that depends on someone remembering is not a plan.
Take a fresh, verified backup immediately before any of these events, and keep it separately labelled. A backup taken five minutes before a major plugin update is the fastest way back if the update breaks checkout. The same applies before a migration — see How to Migrate an E-commerce Store with Less Downtime — and before a sale, when order volume makes any data loss expensive.
For a typical growing store: hourly or six-hourly database backups and daily full backups, stored off the server with one copy in another region, retained on a daily/weekly/monthly ladder, with failure alerts, and a restore tested on staging every quarter and timed. That plan costs a little time and storage. The alternative — discovering during an outage that the last good backup is three weeks old, on the same dead server — costs far more.
Plan backups from the business numbers: how many orders you can lose (RPO) and how long you can be down (RTO). Back up the database often, the files daily, and the configuration always. Store copies off the server and off-site, keep them long enough to predate silent corruption, alert on failure, and prove the restore works before you need it. A backup you have tested is a plan. A backup you have not tested is a hope.
For hosting with the storage and reliability a store’s backup plan needs, see our WooCommerce hosting plans. [TO BE CONFIRMED: whether Offshore Hosting offers managed or off-site backups for WooCommerce plans, retention, and immutability options.]
Email on your own domain looks professional and stays yours when you change providers. This guide explains what business email hosting involves, how it differs from free webmail, and the DNS and deliverability pieces that make it work.
Latency figures are widely quoted and widely misunderstood. This guide explains what ping measures, which hop actually matters, and the limits of what a VPS can do.
Webhooks, queue mode, and execution retention decide whether n8n stays fast or slowly fills its database. This guide explains each one and the settings that matter.