Despite only a few months into 2023, this year has already seen high-profile data breaches. From Twitter and JD Sports to GoDaddy, even the biggest names can be vulnerable to online ambushes.
But regardless of size, it’s important to protect your business from the ever-present threat of cyber attacks.
For your annual reminder to keep your data safe and sound, World Backup Day lands on Friday, 31st March. And in the spirit of “it’s better safe than sorry”, domain and hosting provider Fasthosts has put together a handy, easy-to-follow guide on backing up your website.
What does backing up mean?
A backup is a digital copy of your website that can be restored if something goes wrong with the live version. What the backup includes depends on whether you have a static website or use a CMS like WordPress and how you’re backing up your site. As a general rule of thumb, the more files you can keep safe, the better.
If you’re wondering why website backups are important, it’s simple – they’re a plan B that protects you against data loss that can occur from cyber threats or human error.
When should you back up?
We recommend you always have a recent website backup, ideally at least daily or weekly. That will change depending on how frequently you update your website, but the longer you leave it, the more work you’ll likely lose if something happens.
It also depends on your site – smaller, static websites should be fine without regular backups. But online stores, blogs and bigger websites need consistent backups. It’s good practice to back up your entire website before making significant changes, moving it to a new host, or changing your domain.
What needs backing up?
Two parts of a website need backing up – its web files and its database. Website files are stored in the main directory, sometimes known as “public_html” or “htdocs”. They include core files, images, code files, static web pages, and plugins and themes if you use a content management system (CMS).
The database stores site data NOT included in the site files, like user info, application data and CMS data, including posts, shop content, and comments. So for most sites, a full backup requires you to back up both the website files and the database.
Types of backups
A full backup is a complete copy of all data in a single instance.
A differential backup will include any changes since the last full backup, even if the changes have already been included in a previous differential backup.
An incremental backup will include any changes or new content since the last full or incremental backup.
Consider what to back up
Your backups will not always need to contain all of your data, especially if you have multiple backups going daily and weekly. If the data you’re backing up is not regularly changed or is completely static, then you can get by with periodic full backups
If you are making changes more often, you might consider incremental or differential backups, or partial data backups, including changes since previous backups. Implementing these methods can allow you to save space and time.
Automate and schedule backups
In some systems, irregular and/or manual backups can be enough, but you should implement automatic and scheduled backups where possible. This means you’re less likely to run into issues due to human error and will have consistent backups.
Have multiple backups
Having a single backup is a great start. However, especially when backups are automated, this can result in issues in the original content being copied into the sole backup – leaving you with nothing to restore from. How many backups, how often and how long you can keep them will vary based on how often you make changes and how critical the backup is.
Backup to multiple locations
When backing up data, at the very least, it should be in a different location from any original/live content. If the backup and original are stored in the same place, then both could be lost if there are any issues.
You may consider keeping one backup on a local system and one off-site backup, such as a remote server or online storage provider.