Many website owners will tell you they have backups, but far fewer have ever restored one. That is the moment a problem appears: the backup sits on the same server that just failed, it holds files but not the database, it is months old or nobody remembers the password to open it. A backup you cannot restore is only a comforting idea. This guide explains what to back up, how to keep copies safe, how to test them and how to think about recovery time, building on our backup and disaster recovery guide.
What to Back Up
A complete website backup includes the files (code, themes, uploads and configuration) and the database, which holds your pages, products, orders and user accounts. Do not forget items stored elsewhere: DNS records, email accounts if they are hosted with the same provider, SSL certificate details and data held in third-party services such as a CRM or payment platform. Write down where each item lives and who can access it. Remember too that some hosts keep automatic backups for only a few days, so check the retention period rather than assuming. If you only back up the files, a restore will give you a site with no content. If you only back up the database, you may lose uploaded images and custom code.
The 3-2-1 Rule
A widely used guideline is the 3-2-1 rule: keep three copies of your data, on two different types of storage, with one copy stored offsite. In practice, that could be the live website, a daily backup on separate storage at your host and a weekly copy in cloud storage in another location. A backup stored only on the same server is lost with that server. Keep several versions rather than overwriting one, for example daily copies for two weeks and weekly copies for two months, so that you can go back to before an infection or a mistaken deletion. Encrypt backups and restrict who can open or delete them, because attackers target backups too.
How Often to Back Up
The right frequency depends on how quickly your data changes. A brochure website that you edit monthly may be fine with a weekly backup. An online shop that takes orders needs the database backed up far more often, perhaps several times a day, because a day of lost orders is expensive. Automation removes the risk of forgetting; see backup automation for how to set it up. Also take a manual backup before any update, a habit that supports the process in our staging environment guide. Good hosting helps, and our hosting guide and FAQ on web hosting explain what to ask your provider.
Test Your Restore
Every quarter, restore a recent backup to a staging site and treat it as a rehearsal. Check that pages and images appear, forms work, users can log in and the most recent content is present. Time the process, and write down each step, the credentials needed and who is responsible, so that the plan does not depend on one person's memory. Keep one copy of the restore instructions outside the website itself, such as in a shared document, because you will not be able to read them from a site that is down. Testing often reveals small problems, such as missing files or an incompatible server version, which are far cheaper to fix on a quiet afternoon than during an outage.
Recovery Time in Plain Language
Two terms help you decide how much protection you need. Recovery time is how long your site can be down before the business suffers. Recovery point is how much recent data you can afford to lose, such as a few hours of orders. Shorter targets cost more, so choose them deliberately rather than by accident. Infrastructure matters too, as described in how modern data centres protect against downtime. When something does go wrong, work through these steps in the first hour. Confirm whether the cause is hosting, a faulty update or an attack, and follow our hacked website response guide if you suspect a breach. Put up a maintenance page, preserve logs, restore from a clean backup, change all passwords and fix the cause before reopening, or the problem will simply return.
Backups are cheap compared with the cost of rebuilding a website from nothing. ANGLIA has supported clients across 5,000+ projects over 20+ years, and a tested backup plan is part of how we look after them. If you are not sure your current backups would actually restore, use our contact page and we can check them with you.






