Website Backups for a Small Business: What to Save and How Often
Short answer: Back up three things every time: the website files, the database that holds your pages and orders, and the uploads such as product photos and PDFs. Take a full copy at least once a week, and take an extra copy before every update, plugin change or redesign. Keep one copy outside your hosting account, and test a restore every quarter on a spare folder so you know the copy works before you need it.
Why a website needs its own backup routine
Most hosting companies keep copies of your site, but those copies are there for their own recovery, not yours. If a plugin update breaks the checkout, or someone plants a hidden page in your files, the host may restore an older snapshot that is a day or a week behind. You then lose everything published or sold since that snapshot. A backup you control is the only copy you can choose the date of.
A website also differs from cloud office data. Your files, your database and your uploads work together. Saving one of them without the others gives you a site that cannot start up again.
The four parts to save
- Files. The folders that run the site: theme or template files, plugin or application code, and the configuration files that tell the server how to run it.
- Database. Where pages, blog posts, customer accounts, orders and form entries are stored. Files alone cannot rebuild these.
- Uploads. Images, PDFs, downloads and anything staff or visitors added through the admin area. These often make up most of the storage space.
- Settings records. The domain details, email sending settings and payment links that connect the other parts. Keep the actual values in a password manager, not in a shared spreadsheet.
How often to back up
How often you copy the site depends on how often its content changes. Use this table as a starting point:
| Site type | Example | Full backup |
|---|---|---|
| Brochure site, edited a few times a month | A joinery firm's portfolio pages | Weekly, plus before any change |
| Site with a news page or enquiry form | A dental clinic with a booking form | Daily |
| Online shop or booking site | A bakery taking weekend orders | Daily, plus a database copy after busy days |
Whatever the table says, take a manual backup before every update, plugin change or theme edit. Those are the moments when problems usually start.
Keep a history too. A hack discovered three weeks after it happened will not be fixed by last night's copy, because last night's copy already contains the problem. A common pattern for a small site is the last seven daily copies, the last four weekly copies and one monthly copy from the past year.
Setting up the backup step by step
- Choose storage outside the hosting account. Use a cloud drive folder under a separate login, or an external drive you disconnect after each copy. A simple version of the 3-2-1 idea works here: three copies of the data, on two kinds of storage, with one copy kept somewhere else.
- Run the export. Many hosts and content management plugins have a backup button. Check that the output contains all four parts, not only the database.
- Name each file with the date and the site. For example,
2026-11-05-bakery-full.zipis easier to find thanbackup (3).zip. - Set a schedule and a reminder. Automatic copies handle the routine. Add a calendar reminder for the manual copy before updates.
- Check each new file. Open the archive, confirm the folders and the database file are there, and compare the size with the previous copy. An archive that is suddenly tiny is the most common silent failure.
Test a restore every quarter
A backup you have never restored is a guess. Once a quarter, set aside an hour:
- Create a spare copy of the site on a test subdomain, or ask your developer to set one up.
- Restore the latest files and database into that copy.
- Open five pages, log in to the admin area and send a test enquiry to a test address.
- Write down how long the restore took and what was missing. Fix the gap before the next quarter.
Keep the restore notes with the backup files, so the steps are there when you are stressed and in a hurry.
Keep one copy out of reach
If an attacker gets into your hosting account, they can often delete backups stored inside it. Keep at least one copy in a different account, protected by a different password and two-step sign-in. Limit who can delete files from that storage, and do not let the copy sync to a device that also holds the admin login.
Common mistakes
- Backing up files but not the database, so pages and orders are missing after a restore.
- Keeping only one backup that is overwritten every night, which means a slow problem can overwrite every copy.
- Storing backups in the same folder as the live site, where a bad script can reach them.
- Never opening the archive after it was created.
FAQ
Is my host's backup enough?
Sometimes, but you cannot see the schedule, retention or restore process unless you ask. Treat the host's copy as a second layer and keep your own copy as the first layer you control.
Can I back up a site without a developer?
Yes, if your content management system or host provides an export button. The restore test is the step that usually needs help, so ask for a quick walkthrough the first time you run it.
What if a restore fails?
Check whether the database and the files come from the same date. Mismatched copies are the usual cause. If that is not the problem, keep the failed copy and check the error message against your host's documentation before trying again.
How much storage will this use?
Most small sites need only a few gigabytes per copy, but uploads can grow quickly. Review the old full copies every few months and delete the ones outside your retention pattern.
If you would like us to set up the routine, run the first restore test and leave you with a one-page checklist, tell us a little about your site.