Most business owners assume their website has backups because someone, at some point, said it does. Very few have ever watched one get restored. That gap between assuming backups work and knowing they work is where a lot of businesses find out what a hosting failure or hacked site costs them.
What “we have backups” usually means
In practice it usually means a backup job runs automatically overnight, an addon or plugin takes a database snapshot, or the hosting provider includes backups as part of the package. All of those things can be true and the backups can still be useless the day they're needed. Nobody has opened one to check what's actually inside it.
Where backups fail
A few problems show up again and again. The backup job stops running quietly, months before anyone notices, and the most recent file is older than anyone realises. The database dump completes but is missing tables or corrupted partway through, something that only becomes obvious on restore. Uploaded images and files are stored separately from the database and never get backed up alongside it, so a restored site ends up with broken images throughout. The retention window is short enough that a problem sitting unnoticed for a few weeks gets backed up over the last good copy.
Why nobody finds out until it's an emergency
Backups run quietly in the background, and a working backup looks identical to a broken one until someone tries to use it. Most hosting setups don't alert anyone when a backup job fails, so the first time a business finds out their backups don't work is during the exact moment they need them.
What a tested restore actually looks like
Testing a restore means running the process itself, not just checking that a backup file exists: restoring the most recent backup to a separate environment, confirming the site loads correctly, and checking that recent content and orders are present. Timing how long the whole thing takes matters too. A six-hour restore on a business-critical site is six hours of downtime worth planning for, not discovering partway through an outage.
If you're not sure your backups have ever actually been tested, get in touch with Karl to find out.
Most businesses with an ExpressionEngine site didn’t choose ExpressionEngine themselves. A web agency built the site, recommended the CMS, and handled everything from launch onward. That arrangement works well until it doesn’t, and there are several ways it can stop working.
Many businesses pay a monthly fee for website support without being clear on what that covers. Here is what a proper ExpressionEngine or Craft CMS retainer should include.
Plenty of ExpressionEngine and Craft CMS sites run on a single relationship: a freelancer who built the site years ago and has quietly maintained it since, or an in-house hire who set everything up and never wrote any of it down. That works fine for years. Then that person goes on holiday during a launch, gets a new job, or stops replying to emails, and the business finds out how much depended on one inbox.
Most clients come to us when their site has started to feel like a risk rather than an asset. Whether the agency relationship has ended, an upgrade has been delayed, or the site has simply grown beyond what it can handle, a conversation costs nothing.