Foldwren

Website backups: your safety net

Learn what a website backup should include, how often to take one, where to keep copies, and why testing a restore matters more than you think.

Every website will eventually have a bad day. An update goes wrong, someone deletes the wrong page, a hosting company has a failure, or an attacker gets in. On that day, the only thing that matters is whether you have a recent, complete copy of the site and whether you can put it back.

That copy is a backup. Most business owners assume they have one. Fewer have checked.

What a backup needs to include

A website is more than the pages you can see. A proper backup captures all the pieces needed to rebuild it from nothing.

  • The files. The code, the design templates, and every image, PDF and video you have uploaded.
  • The database. On sites built with a content management system, the actual words, product details, orders, form entries and settings are stored in a database, separate from the files. A backup of files without the database is a shell with no contents.
  • The configuration. Settings that connect the site to other things, such as payment providers or email delivery.

There are also things a website backup usually does not include, and people are often surprised by them.

  • Your email. Mailboxes are a separate system, even when they are with the same company.
  • Your domain and DNS settings. These live with your registrar or DNS provider.
  • Content on other platforms. Your booking system, your newsletter list, your online store if it runs on a hosted service. Each of those has its own export or backup arrangements.

It is worth listing the systems your business depends on and asking, for each one, where the copy is.

How often should backups run?

The right frequency depends on how much you could stand to lose. Ask yourself: if the site were wound back to the last backup, what would be missing?

  • A brochure site that changes a few times a year. Say a builder with a gallery and a contact page. A weekly backup is usually plenty, with an extra one before any changes.
  • A site updated regularly. A cafe posting weekly specials, or a clinic adding articles. Daily makes sense.
  • An online shop or booking site. Orders and bookings arrive at any hour. Losing even a day of them is a real problem, so you want daily at minimum and more often if your setup allows.

Whatever the schedule, take a fresh backup immediately before any significant change: software updates, a redesign, a move to a new host. That is when things are most likely to go wrong.

Where the copies are kept matters

A backup stored on the same server as the website is a spare key kept inside the locked house. If the server fails or is compromised, the backup goes with it.

Good practice is to keep copies in a separate location, ideally with a different provider, and to keep more than one version. That second part is easy to overlook. If your site was quietly infected three weeks ago and you only keep the last seven days of backups, every copy you have contains the infection. Holding a few weeks of daily copies, plus some older monthly ones, gives you a clean point to return to.

The part everyone skips: testing a restore

A backup has one job, which is to be restored. Until someone has actually done that, you do not know whether it works.

Backups fail in quiet ways. The job stopped running months ago when a password changed. The storage filled up. The database was being skipped because it grew too large. The files are all there but nobody knows the steps to put them back. You find out about all of these at the worst possible moment unless you go looking first.

A restore test does not need to touch your live site. Whoever manages the site can restore the latest backup to a private test location and confirm that the pages load, the images appear and the recent content is present. It also tells you how long a restore takes, which is useful to know in advance. "About an hour" and "probably a couple of days" call for very different plans.

Do not rely on your host's backups alone

Many hosts take backups, and that is a good thing. Read what they promise, though. Often those backups are for the host's own disaster recovery, with no guarantee about restoring an individual customer's site on request, or with a fee to do so. Some keep only a few days.

Treat the host's backup as a bonus layer. Have at least one backup arrangement that you, or the person who looks after your site, controls directly.

Questions to ask whoever manages your site

You do not need to run backups yourself, but you should be able to get straight answers to these.

  • How often is my site backed up, and does that include the database?
  • Where are the backups stored?
  • How far back can we go?
  • When was a restore last tested?
  • If the site disappeared tonight, how long until it was back, and what would be lost?
  • Can I have a copy of a backup for my own records?

If the answers come quickly and specifically, relax. If there is a long pause before any of them, you have found a job for this week.

Your order