How Often Should You Back Up Your Website?
Your website might contain years of work. Pages, blog posts, photographs, customer enquiries, product information and other important data can all be stored there. Yet website backups are one of those things many small business owners don’t think about until something goes wrong.
A website can be damaged by a failed update, human error, malware, hacking, a hosting problem or an accidental deletion. If you have a recent working backup, the problem may be recoverable. Without one, getting the website back could be much harder.
The question isn’t simply whether you should back up your website. You also need to decide how often those backups should happen, where they should be stored and how long previous copies should be kept.
Quick Answer
Most small business websites should be backed up at least weekly, while websites that change regularly should normally be backed up daily. Ecommerce, membership, booking and other busy websites may need more frequent backups because new information can be added throughout the day.
A useful way to decide is to ask yourself: if my website disappeared right now, how much recent information could I afford to lose? If losing a week’s worth of website changes would be a serious problem, weekly backups aren’t frequent enough. Backups should also be stored separately from the live website and regularly checked to make sure they can actually be restored.
Why Do Website Backups Matter?
A backup gives you another copy of your website that can be used if the live version becomes damaged, deleted or unavailable. Think of it as a safety net. You hope you never need it, but if something serious happens, you may be very glad it exists.
The UK’s National Cyber Security Centre advises organisations to back up the data they need to operate and specifically includes websites among the business information that may need protecting. It also recommends knowing how to restore that data rather than simply assuming a backup exists.
A website problem doesn’t always mean somebody has hacked it. A plugin or theme update could cause an unexpected problem. Someone with administrator access might accidentally remove something important. Files can become corrupted, or a business may make a large set of changes and later discover that something has gone wrong.
For a small business, the effect can go beyond the website itself. If a plumber’s website stops accepting quote requests, a restaurant loses its online menu, or an online shop stops taking orders, the problem can start affecting the business very quickly.
How Often Should You Back Up Your Website?
There isn’t one backup schedule that suits every website. The right frequency depends mainly on how often your website changes and how much information you could reasonably afford to lose.
WordPress guidance suggests weekly backups for smaller websites with fewer posts and daily backups for high-activity websites with lots of posts. It also recommends backing up the database before an upgrade.
For many ordinary small business websites, this gives us a sensible starting point:
| Type of Website | Typical Starting Point | Why |
|---|---|---|
| Small brochure website that rarely changes | Weekly | Very little new information is normally added between backups. |
| Business website updated regularly | Daily | Reduces the amount of recent work that could be lost. |
| Active blog or news website | Daily | New posts, comments and other changes may be made frequently. |
| Ecommerce website | Daily or more frequently | Orders, accounts and other information may change throughout the day. |
| Membership or community website | Daily or more frequently | User information and website activity may change continuously. |
| Booking or appointment website | Daily or more frequently | New bookings and changes may happen throughout the day. |
These aren’t fixed rules. A small five-page website that receives important form submissions or makes frequent content changes might need daily backups. A larger website that barely changes might not need the same schedule.
A better way to make the decision is to work backwards from the amount of data you’re prepared to lose. If your last backup was taken 24 hours ago, could your business cope with losing everything added since then? If the answer is no, you need a shorter backup interval.
Different Websites Need Different Backup Schedules
A Small Local Business Website
Imagine a local electrician with a website containing service pages, photographs, contact details and a few blog posts. The content may only change once or twice a month. In this situation, an automatic weekly backup could be reasonable, provided an additional backup is made before important changes or updates.
An Active Business Blog
If a business publishes several new articles every week and regularly edits existing pages, daily backups make more sense. Otherwise, a problem near the end of the week could potentially mean losing several days of work.
An Ecommerce Website
An online shop is very different because its database can change every time somebody places an order, creates an account or performs another action that stores information. Depending on the level of activity, once-a-day backups may still leave too large a gap.
For example, if a shop takes 30 orders after its most recent backup and the website later has to be restored to that backup, those later transactions may not exist in the restored database. This is why busy transactional websites often need a more carefully planned backup and recovery system than a simple brochure website.
Membership and Booking Websites
The same principle applies to membership sites, online communities and booking systems. The website may be changing even when the owner isn’t editing pages. Members could be registering, customers could be making bookings, and information could be changing in the background.
For these websites, backup frequency should be based on website activity rather than how often the owner logs into WordPress.
What Should a Website Backup Include?
A useful website backup normally needs more than a copy of the visible pages. For a WordPress website, for example, the website is made up of both files and a database.
The files can include your WordPress installation, themes, plugins, uploaded images and other website files. The database can contain posts, pages, settings and other information needed by the website.
WordPress recommends treating the files and database as one backup set so they can be restored together from around the same point in time.
Depending on the type of website, a complete backup may therefore need to cover:
- The website database
- Website pages and posts
- Uploaded images and documents
- Theme files
- Plugin files
- Configuration information
- Custom website files or code
If you’re paying somebody to manage your website, it’s worth asking exactly what is included in their backup rather than simply asking, “Do you back it up?”
Should You Back Up Before Updating Your Website?
Yes. Taking a fresh backup before significant website updates or changes is a sensible precaution, even if your normal automatic backup isn’t due yet. WordPress specifically advises backing up the database before an upgrade.
This is particularly useful before updating WordPress itself, installing or updating important plugins, changing a theme, editing website code, making major design changes or carrying out substantial work on the database.
If the change causes a serious problem, having a backup from immediately before the work began can make recovery much easier. Otherwise, your most recent automatic backup might already be several hours or days old.
Can You Rely on Your Hosting Company’s Backups?
Some hosting companies provide automatic website backups, but you should understand exactly what the service includes. Backup frequency, storage location, retention periods and restoration options can vary between providers and hosting packages.
Find out how often backups are created, how long they’re retained and whether you can restore them yourself. You should also know whether both your files and database are included and what happens to your backups if there is a problem with your hosting account.
The National Cyber Security Centre advises organisations not to rely solely on recovery mechanisms within a single cloud service for critical information. It recommends keeping an independent copy in another safe place or service.
That principle is useful for websites too. A hosting backup can be an important part of your protection, but having another independent copy reduces your dependence on one provider or system.
Where Should Website Backups Be Stored?
Keeping a backup in exactly the same place as your live website creates an obvious weakness. If the server, hosting account or website is compromised, your backup could potentially be affected as well.
The National Cyber Security Centre recommends multiple copies of important information in different locations and discusses the widely used 3-2-1 approach: at least three copies, on two devices or storage types, with one copy kept offsite. It also recommends keeping an offline backup separate from the main network or using a cloud service designed for backup purposes.
For a small business website, the exact setup will depend on the website and the level of risk, but the underlying idea is straightforward: don’t allow one failure to destroy both your live website and every copy you have available for recovery.
How Many Backups Should You Keep?
Keeping only the latest backup can create another problem. Imagine malware gets into your website but nobody notices for several days. If every new backup replaces the previous one, you could eventually discover that your only available backup already contains the problem.
The National Cyber Security Centre advises retaining backups for a period of time rather than relying on one rolling backup. The important point is to consider how long a problem might remain unnoticed and make sure older recovery points are available.
WordPress guidance also recommends keeping several recent backups in different locations. The aim isn’t to collect unlimited copies forever. It’s to have enough history to give yourself a realistic choice of restore points if a recent version turns out to be unusable.
A business might, for example, keep a series of daily backups for a period and then retain less frequent older copies. The right retention policy depends on how quickly the website changes, available storage, the importance of the information and any data-retention obligations affecting the business.
Should Website Backups Be Automatic?
For most business websites, automatic backups are far safer than relying entirely on somebody remembering to create them manually. People get busy, staff go on holiday, and a manual weekly backup can easily become a monthly one without anybody noticing.
Automation allows backups to run according to a planned schedule without somebody having to remember each time. A busy website can therefore create daily or more frequent restore points consistently.
However, automation doesn’t mean you can forget about backups completely. You still need to check that the backup system is running, that enough previous versions are being retained and that the files being produced can actually be restored.
Why Testing Your Backups Matters
A backup isn’t much use if you discover during an emergency that it’s incomplete or corrupted. This is why testing should form part of a proper backup process.
The National Cyber Security Centre recommends regularly testing backups and making sure you know how to restore your information before you need to do it for real. Its ransomware-resistant backup guidance also recommends having a way to test whether stored backup data is corrupted.
You don’t necessarily need to restore your live website every week just to prove the backup works. The important point is that there should be a safe process for checking backups and testing restoration without putting the live website at unnecessary risk.
You should know who would restore the website, where the backup files are stored, what access details would be required and roughly what the recovery process involves. Finding those answers during an emergency wastes valuable time.
Expert Insight From Daren Ward
Daren Ward – Founder, A to Z Website Solutions
From my experience working with business websites, one of the biggest mistakes is thinking about backups only after something has gone wrong. A backup isn’t exciting and it doesn’t bring visitors to your website, so it’s easy for it to sit near the bottom of the priority list.
I would normally recommend looking at backup frequency from the point of view of potential loss. Ask yourself what would happen if you had to restore the website to yesterday, last week or last month. What pages, orders, bookings, enquiries or other information could disappear?
I’d also want to know where the backups are stored and whether anybody has checked that they can actually be restored. Seeing the word “backup” in a hosting control panel isn’t quite the same as having a recovery plan. The real test is whether you can get the website back when you need it.
Warning: Don’t Keep Your Only Backup With Your Live Website
If your only backup can be accessed through the same compromised account or system as your website, a serious cyber attack could potentially affect both. The National Cyber Security Centre warns that ransomware attackers may deliberately target backups to make recovery harder.
Keep independent copies where appropriate, protect access to backup systems and use strong account security. Your backup should help you recover from a problem, not disappear along with the website it was supposed to protect.
Website Backup Action Checklist
- Find out whether your website is currently being backed up.
- Check exactly how often automatic backups are created.
- Decide how much recent website data your business could realistically afford to lose.
- Make sure both the website files and database are covered where required.
- Check where your backups are stored.
- Avoid relying entirely on a single copy or one storage location for important website data.
- Find out how long previous backups are retained.
- Take a fresh backup before significant website updates or changes.
- Make sure access to backup systems is properly protected.
- Check periodically that backups are completing successfully.
- Test the restoration process safely.
- Make sure you know who is responsible for restoring the website if something goes wrong.
Frequently Asked Questions
How often should a small business website be backed up?
A small business website that doesn’t change very often may be adequately served by weekly backups. If pages, posts, enquiries or other information change regularly, daily backups are usually a better starting point. The right schedule should reflect how much recent information the business could afford to lose.
Should I back up my website every day?
Daily backups make sense for many active business websites. They’re particularly useful where content changes frequently or the website stores new information. A simple brochure website that changes only occasionally may not require the same frequency.
How often should an ecommerce website be backed up?
An ecommerce website may need daily or more frequent backups because new orders, accounts and other database changes can happen throughout the day. The busier the shop, the more important it becomes to reduce the gap between recoverable versions.
Do I need a backup before updating WordPress?
Yes. Taking a fresh backup before important WordPress updates is sensible. WordPress recommends regularly backing up the database and backing it up before an upgrade. This gives you a recent restore point if an update causes a serious problem.
Does a WordPress backup include my images?
It depends on the type of backup. Your WordPress database alone doesn’t contain all the files that make up the website. A complete backup strategy should account for both the database and the necessary website files, including uploaded images and other media.
Is my hosting company’s backup enough?
It may provide valuable protection, but you shouldn’t simply assume it covers everything you need. Check the frequency, retention period, contents and restoration process. For important business information, maintaining an independent copy can provide another layer of protection.
How long should website backups be kept?
There isn’t one retention period suitable for every website. Keeping several historical restore points is useful because a problem may not be discovered immediately. Your retention period should take into account how long a problem could remain unnoticed and how far back you might realistically need to restore the website.
Can I automate website backups?
Yes. Website backups can often be automated through hosting systems, website management tools or dedicated backup services. Automation is usually preferable to relying solely on somebody remembering to perform backups manually.
How do I know whether my website backup works?
You need to check it and periodically test the restoration process in a safe environment. A backup job reporting that it completed successfully is useful, but a tested restore gives you much greater confidence that the backup can actually be used.
Should backups be stored on the same server as my website?
Your only backup shouldn’t depend on the same system as your live website. Keeping independent copies in separate locations can protect you if the main server, hosting account or backup location is damaged or compromised.
What happens if I don’t back up my website?
If the website is damaged or important information is lost, you may have no recent version to restore. Depending on the website, that could mean rebuilding pages, re-uploading content or losing information that can’t easily be recreated.
Summary
There is no single backup frequency that is right for every small business website. A website that changes once a month doesn’t have the same requirements as an online shop processing orders throughout the day.
Weekly backups can be a reasonable starting point for a small, low-activity website. Daily backups are more appropriate for websites that change regularly, while busy ecommerce, membership and booking websites may require more frequent protection.
Frequency is only part of the picture. A reliable backup plan should also consider what is being backed up, where the copies are stored, how long previous versions are retained and whether the backups have been tested.
The simplest question to ask is: how much could my business afford to lose? Your backup schedule should make sure the answer isn’t more than you’re comfortable with.
Need Help Looking After Your Website?
A business website needs more than good design. Keeping the software maintained, protecting the website and having suitable backups can all help reduce the problems that come with running an important business asset.
A to Z Website Solutions has been providing website design and online marketing services since 2004. If you’d like help looking after your business website, maintaining WordPress or reviewing how your website is currently managed, get in touch and we can discuss what you need.
Key Takeaways
- Small, low-activity websites may be suitable for weekly backups.
- Websites that change regularly should normally be backed up at least daily.
- Busy ecommerce, membership and booking websites may require more frequent backups.
- Take a fresh backup before important website updates or major changes.
- A WordPress backup strategy should cover the database and the website files needed for recovery.
- Don’t rely on one backup stored in the same place as your live website.
- Keep historical restore points rather than continually replacing your only backup.
- Regularly check and test your backups so you know they can actually be restored.