Two habits that protect each other
Updates and backups are often discussed separately, but they work as a pair. Updates reduce the chance that something goes wrong, and backups limit the damage when something does anyway. Skipping either one leaves the other doing more work than it should.
Things that can go wrong on a live site include a failed update, a hacked account, an accidental deletion, a hosting problem, or a change that turns out to be a mistake. In each case, the question is how quickly you can get back to a known good version.
What a website backup actually contains
A complete copy depends on how the site is built, but most sites have two kinds of material:
- Files: page templates, images, uploaded documents, themes, and any custom settings.
- Content storage: many sites keep posts, pages, comments and settings in a database, separate from the files.
If you back up only one of these, a restore may give you a site that looks wrong or is missing its content. A hosted site builder may handle some of this for you, but it is worth finding out exactly what the provider saves, how long it keeps copies and whether you can download your own. Providers differ, and a statement that backups exist does not tell you whether you can recover a single page from last month.
Also remember the pieces that live outside the site itself, such as your domain settings, email configuration and a list of the tools connected to the site. A short document describing them can save hours later.
How often to back up
The right frequency depends on how often the site changes. A useful way to think about it is to ask how much work you could stand to lose.
- A site that changes a few times a year may be fine with a copy after each change plus a monthly one.
- A site with frequent posts, comments or orders may want daily copies.
Keep more than one copy. If you have only the latest backup and it was taken after a problem began, it will contain the problem. Holding several older versions gives you somewhere clean to return to.
Where copies are stored matters as much as how often they are made. A backup kept only on the same server as the site can vanish with it. Aim for at least one copy in a different location, for example in cloud storage under a separate account or on a drive that is not always connected. The general ideas behind file backups for everyday users apply here too, including keeping copies in more than one place.
Why updates matter
Site software, themes and add-ons are updated for several reasons: to fix bugs, to close security weaknesses, and to stay compatible with newer browsers and server software. A weakness that has been publicly fixed is easier to exploit on sites that have not applied the fix, so delaying updates for long periods tends to increase risk. The same reasoning is behind why software updates matter on personal devices.
At the same time, updates are changes, and changes can break things. Two add-ons may stop working together, or a new version may alter how a page looks. That is the reason for a careful order of work.
A safe update routine
- Make a fresh backup and confirm that it finished.
- Read the update notes if they are provided, looking for warnings about compatibility.
- If you can, try the update on a copy of the site first. Some hosts offer a staging area for this.
- Apply updates one at a time, or in small groups, rather than all at once, so you can tell which one caused a problem.
- Check the home page, a few inner pages, any forms and the checkout or sign-in if your site has them.
- Check the site on a phone as well as a computer.
If something breaks, you can undo only that one change. Remove add-ons you no longer use rather than leaving them idle, since unused components still need updating and still count as something that can go wrong.
Test that a restore works
A backup you have never restored is a hope, not a safeguard. Backups can be empty, incomplete, corrupted or missing a piece such as the database, and you only find out when you need them.
Try a restore test at least once, and repeat it a few times a year:
- Choose a recent backup.
- Restore it to a separate location, such as a staging site or a local test setup, never over your live site.
- Open the restored version and look for missing images, missing pages, broken styling and errors.
- Check that recent content, such as your latest post, is there.
- Write down the steps you took and how long it took.
That written record is valuable. When something goes wrong, you will be tired and stressed, and clear notes are far easier to follow than memory. If you rely on a hosting company for restores, ask them how it works and how long it usually takes, so you know what to expect.
Keep access secure
Backup files can contain private information, such as customer messages or account details, so treat them with care. Protect the accounts that control your hosting and backup storage with strong, unique passwords, and use two-factor authentication if it is available. Do not leave backup archives in a public folder on your own site. Anyone who finds a downloadable archive may be able to read everything in it.
Putting it on a schedule
A simple plan is enough to start with: automatic backups at a frequency that suits the site, a monthly slot for updates preceded by a manual backup, and a restore test every few months. Put those dates in your calendar. Doing a small amount regularly is much easier than trying to repair a neglected site in a hurry, and it also keeps the rest of your site upkeep in better shape.
No routine can promise that nothing will ever go wrong. What it can do is make sure that when something does, you have a recent, tested copy and a clear idea of what to do next.