A website without a reliable backup is a website waiting for a crisis. What backups are, why they are essential, and what you should be asking your hosting provider.
A website backup is a saved copy of everything that makes up your website — the files, the code, the images, and if applicable the database that stores your content. A backup taken at a given point in time allows the website to be restored to that state if something goes wrong with the live version.
Think of it in the same terms as backing up files on your computer. If your computer is stolen, corrupted, or fails, a recent backup means you can recover your work. Without one, it is gone. The same principle applies to a website — except that the consequences of losing a website can be considerably more serious for a business than losing personal files.
Websites — particularly those running on popular content management systems — are frequent targets for automated attacks. A compromised website may have files deleted, replaced, or corrupted. Without a clean backup to restore from, recovering from a successful attack can mean rebuilding the entire site from scratch.
A plugin update, a theme update, or a server software update can, in rare cases, cause a site to stop working entirely. If a backup exists from immediately before the update, the problem can be resolved in minutes. Without one, diagnosis and repair can take hours — or longer.
Accidentally deleting a page, overwriting content, or making a change that breaks something are all more common than most people anticipate. A backup makes these mistakes recoverable. Without one, the work may simply be lost.
Hosting providers can experience catastrophic server failures, data centre incidents, or — in rare cases — go out of business. Reputable providers maintain their own backup infrastructure, but relying solely on your hosting provider's backups without independent verification of what is backed up and how recently is a risk.
Important: Some budget hosting packages either do not include backups at all or include them as a paid add-on. Never assume your hosting provider is backing up your website — always confirm it explicitly, in writing if possible, and ask specifically how recent the backups are and how restoration works.
For a website whose content changes regularly — an active blog, an e-commerce site with changing product listings, or a site with a database of customer data — daily backups are appropriate. For a more static business website that changes infrequently, weekly backups may be sufficient, though daily is always preferable.
Keeping only the most recent backup is not enough. If a problem occurred three days ago but was not noticed until today, a backup from yesterday will contain the same problem. A good backup policy retains multiple versions — daily backups for the past two weeks, and weekly backups going back further — so that you can restore to a point before a problem occurred.
A backup stored on the same server as the website is of limited value if the server itself is the problem. Backups should be stored in a separate location — a different server, a different data centre, or cloud storage. Most reputable managed hosting providers handle this automatically.
A backup you have never tested restoring from is an assumption, not a safety net. Periodically verifying that backups can actually be restored — and that the restored site works correctly — is an important part of any serious backup strategy. Many businesses only discover their backups were not working correctly at the moment they need them most.
If your hosting provider cannot give you clear, confident answers to these questions, it is worth considering whether your current hosting arrangement is adequate. The cost of a hosting package that includes reliable backups is trivial compared to the cost of rebuilding a website from scratch.