A website can disappear in more ways than you would think. A bad update breaks it. A hacker locks it. A host shuts down, or closes your account over a billing mistake. Someone deletes the wrong page, or the wrong folder, or everything. Occasionally a data center has a fire.
When it happens, one question matters: can you get it back, and how long will that take? The answer depends on whether you have a backup, and whether you have ever checked that it works.
A backup is a copy you can restore from
That sentence has two halves. A backup is a copy, and the copy is only worth something if you can restore from it. Plenty of businesses discover on the worst day that their “backup” was a file nobody could open, a folder that stopped updating a year ago, or a service they canceled.
So a backup has three jobs: be recent enough, be somewhere else, and actually work.
What a website is made of
You cannot back up what you cannot name. Most sites have some or all of these parts:
The files. The pages, styles, scripts and images that make up the site.
The content. On a site with an editor (WordPress, a builder, a CMS), your pages and posts live in a database, not in files. Backing up the files without the database gets you an empty shell.
The uploads. Photos, PDFs and videos you added over the years. They are often the largest part, and the hardest to replace.
The settings. Plugin settings, theme options, form setups, redirects, the list of users.
The domain and its records. The DNS records tell the world where your site and your email live. If you lose them, rebuilding them from memory is painful. A screenshot or an export saves hours.
The things around it. Your email list, your form submissions, your orders, your reviews. These often live in other services, and they have their own backups, or do not.
When someone asks “do you have a backup?”, ask back: of which parts?
Does your host already back it up?
Often yes, partly. This is where trouble hides.
Many hosting plans run automatic backups. Read what yours actually says. Questions to find out:
- How often? Daily, weekly, or only on a higher plan?
- How long are they kept? A backup from yesterday does not help if you notice the damage in three weeks.
- Where are they kept? If the backup sits on the same server as the site, a server failure takes both.
- Can you restore them yourself, or do you open a ticket and wait?
- Do they cover the database as well as the files?
- What happens if your account is closed? Then the backups usually go with it.
A website builder (Squarespace, Wix and similar) has its own copy and handles failures at their end, which is reassuring. But it usually cannot give you a backup of the whole site that you can take elsewhere. You can export your text and images, and the rest is rebuilt if you leave. Do the exports, and keep them.
If your site is built from plain files, with the code stored in a version-control system such as Git and hosted somewhere like GitHub, the history is itself a backup of the site. Keep the content and uploads in there too, or somewhere equally safe.
The three-copies rule
Backup people repeat an old rule because it works: 3-2-1.
- 3 copies of anything that matters: the live one and two backups.
- 2 different kinds of place, for example your host and a separate cloud storage account, or a cloud account and an external drive.
- 1 copy somewhere else, far enough from the others that one disaster cannot reach all of them. Another provider counts as “elsewhere.”
For a small business site, this can be simple. The live site is copy one. Your host’s automatic backup is copy two. A monthly download to your own cloud storage or a drive is copy three, and it is in an account you control.
The reason for the third one is control. A backup that lives only inside your host’s account is only as safe as that account. If the host closes it, or someone locks you out, both disappear together.
How often
Match the schedule to how fast the site changes.
A brochure site that changes twice a year needs a backup after each change, and one copy kept safe in between.
A site with a blog, bookings or a store changes daily. Back up daily, and keep at least a few weeks of copies, so you can go back to before a mistake.
A rule of thumb: how much work are you willing to redo? If the answer is “a day,” back up daily. If it is “a month,” monthly is fine. Orders and form submissions are the sharp case, because you cannot ask customers to place them again. Check where those are stored and how they are copied.
Test the restore
This is the step almost everyone skips, and it is the one that matters most.
A backup you have never restored is a hope. Once or twice a year, try to bring the site back somewhere else: on a test address, in a staging copy, on your own computer. Check that the pages load, the images show, the forms work and the content is recent.
If your host offers a “restore” button, find it and read what it will do before you need it. Some restores overwrite everything, including work you did since the backup. Know that in advance.
Testing is also how you learn how long a restore takes. “We can be back in an hour” and “we can be back in three days” are very different businesses, and you want to know which you are.
Back up the parts that live elsewhere
A modern site leans on other services, and each one holds something you would miss. Your email list sits in your email tool. Orders sit in your store or payment provider. Appointments sit in a booking tool. Reviews sit on Google. Your site’s backup does not include any of them.
For each, find the export button. Most tools let you download a list as a spreadsheet. Do it every few months for the lists you cannot rebuild, and above all for your customer list and your email subscribers. Treat those files with care, because they hold personal details: keep them in your own storage, not in a shared folder open to anyone with the link.
Keep a recovery page
Even with perfect backups, a bad day is easier when the steps are written down. Keep a single page, on paper and in a place that does not depend on the website, with:
- Where the site is hosted, and the login (in your password manager, with a note on where).
- Where the domain is registered, and who the account belongs to.
- Where the backups are kept, how often, and how to get them.
- How to restore, step by step, and who can help.
- The DNS records, copied out.
- Who to call: your web person, your host’s support, your domain registrar.
When something breaks at 6 p.m. on a Friday, this page is the difference between a calm hour and a panicked weekend.
A word about hacked sites
If a site is hacked, a backup helps, but with a catch. Restoring a backup from before the hack gets rid of the damage, but if the hole the attacker used is still open, they will come back. Restore, then fix the cause: update the software and its plugins, change every password, remove users you do not recognize, and turn on two-step sign-in.
Also check the date of the backup. If the site was infected for months before you noticed, your recent backups carry the infection too. That is a reason to keep backups going back several weeks, not only the latest one.
Ten minutes: see what you have
Do this today.
- Find out where your site is hosted, and log in. If you cannot, that is the first problem. Fix it before anything else.
- Look for a backup section in your host’s dashboard. Write down how often it runs, how long it keeps copies, and whether it covers the database.
- Download one full copy of the site, files and database if there is one, plus a copy of your photos. Put it in cloud storage in your own account, or on a drive.
- Take a screenshot or export of your domain’s DNS records and save it with the backup.
- Put a reminder in your calendar, for three months from now, to try a restore.
That is copy three, and a plan.
What to take away
A backup is not a feature you switch on. It is a habit with three parts: copies in more than one place, one of them under your own control, and a restore you have tried.
You will probably never need it. When you do, you will be glad you spent the afternoon.
