Backups that actually save you after an attack.

A backup is only useful if it is recent, complete and stored somewhere safe. Here is how to get it right.

In this article

›
›
›
Backups that actually save you after an attack.
ripple_devadmin
min read

The backup most sites think they have

Many business owners assume their host is backing up their website. Sometimes that is true, but backups may only be kept for a few days, may not include the database, or may be stored on the same server that was compromised.

When a hack is discovered weeks later, a short backup history can mean every copy is already infected.

Worth remembering

A backup you have never tested restoring is a hope, not a plan.

Follow the 3-2-1 approach

Keep at least three copies of your site, on two different types of storage, with one stored off-site. For most websites that means host backups plus an automatic copy to cloud storage.

Make sure every backup includes both the website files and the database, as one is useless without the other.

Keep enough history

Hold daily backups for at least 30 days so you can roll back to a point before any infection began. Busy shops or booking sites may need more frequent backups.

Once or twice a year, practise restoring a backup to a staging site so you know the process works and how long it takes.

Your practical checklist

  • Confirm what your host backs up and for how long.
  • Set up automatic off-site backups.
  • Include both files and the database every time.
  • Keep at least 30 days of backup history.
  • Test a full restore at least once a year.

Client Connect

Connect Right Now

Tell us about your business. We’ll reply in real time by text or email.







    How should we reach you?


    No obligation. By submitting, you agree to be contacted by text or email about your enquiry.