The worst backup call we take on the workshop bench isn’t the one where a Tranent business owner phones to say the drive has died. It’s the one that comes twenty minutes later, when they open their “working” backup and discover the Sage file inside it is three months out of date, the Outlook mailbox never made it in at all, and the last useful restore point was some time in April. Silent backup failure — where the software cheerfully reports success while quietly skipping the files that actually matter — is one of the most common problems we see in small businesses across East Lothian.
If you’re running a small operation in Tranent, Prestonpans or Musselburgh and you’ve never actually tested a restore, this guide is for you. If you already suspect something is wrong, our business IT support team can audit what you have in place.
What Silent Backup Failure Actually Is
A backup fails silently when the software believes it has completed the job successfully — the log says green, the email report goes out clean, the dashboard shows a tidy line of ticks — but the resulting backup set cannot be used to restore the data the business would need in a real emergency. There is no error message. There is no red icon. There is just a growing folder of near-useless snapshots, and a very unpleasant surprise on the day you finally try to use them.
The reason this happens so often is that most backup software is written to keep going after any single-file problem. Skipping a locked file, timing out on a mailbox, or failing to snapshot a volume are all treated as warnings, not failures. The overall job still exits with status “success”, and nothing on the dashboard tells you the useful bits were missed.
The Ways Backups Quietly Break
After years of restoring for businesses across the Lothians, the same handful of failure modes come up again and again. Any one of them will happily sit undetected for months.
Locked database files
Sage, QuickBooks, Outlook PST/OST files, MYOB, and any accounting or line-of-business database that stays open all day will typically be held open by the application. A basic file-copy backup can’t read a file that’s locked, so it skips it, logs a warning, and moves on. Every night. The backup runs green, and the one file the business actually cares about — the accounts — is never in it.
Destination drive full, or quietly disconnected
An external USB drive filled to the last byte three months ago and has been overwriting the oldest snapshot to fit the newest ever since — so your retention is effectively about a fortnight, not the year you thought. Or the drive has been unplugged since the office was rearranged in June, and the software has been failing over to a stale cached copy without shouting about it. We’ve pulled dusty USB drives out from under Tranent office desks that hadn’t written a byte in eleven weeks.
VSS quiescing failure
Volume Shadow Copy Service is the Windows mechanism that lets a backup capture a consistent point-in-time snapshot of a running system — databases included. When VSS fails (usually because a writer service has crashed or a previous snapshot didn’t clean up), backup software will often fall back to a plain file copy and continue. The job still reports success. The database inside the resulting backup is now “crash-consistent” at best — sometimes restorable, sometimes not, and you won’t know which until you try.
Retention set wrong
A cloud sync tool is not a backup. If a member of staff deletes a file and the sync client cheerfully mirrors that deletion to the cloud, you have nothing to restore unless the service has proper versioning turned on and the retention window is long enough. Our post on cloud storage services compared goes into the difference in depth.
How to Tell If Yours Is Actually Working
You cannot tell from the dashboard. The only reliable answer comes from a test restore. Pick a file the business genuinely depends on — last month’s Sage backup, a specific customer’s folder, the shared Outlook mailbox — and try to restore it to a scratch location. If it comes back cleanly and opens in its parent application without complaint, that path works. If it doesn’t, you’ve just discovered the problem while you still have the original, which is exactly the right time.
Do this quarterly. Not annually. Storage devices fail on their own timeline, and so do backup jobs.
The 3‑2‑1 Rule, Made Practical
The industry shorthand is three copies of the data, on two different types of media, with one copy off-site. In practice, for a small Tranent business, that usually looks like: the live copy on the server or PC, an on-site backup to a NAS or external drive, and an off-site backup to a proper cloud backup service (not a folder-sync tool). The off-site copy is what protects you from fire, flood, theft and ransomware — the three things that will otherwise take your on-site backup with them. Our detailed small business backup plan guide walks through the choices in detail.
When to Bring in Business IT Support
If your backup is critical, if you handle client data, or if you’ve been asked to demonstrate resilience for something like Cyber Essentials certification, don’t leave verification to a monthly diary reminder that never happens. A proper business backup routine includes automated test restores, off-site encryption, and monitoring that flags a warning as a warning — not as green. We set these up for businesses across Tranent, Prestonpans, Musselburgh and Haddington, and either monitor them via remote support or come out to audit them in person.
If the Worst Has Already Happened
If you’ve just discovered a bad backup and you still have the failed source drive, stop using it and stop running further backups over the top of it. The best chance of recovering the missing files is usually from the original media, not from the useless backup set. We handle these calls every week under our Tranent data recovery service, and our wider data recovery service covers the rest of the Lothians. Our post on how to back up your PC data properly is the version of this article to hand to a colleague who’s never had to think about backups before.
Silent backup failure isn’t a rare edge case. It’s the default outcome of setting up a backup once, ticking “done”, and never opening the software again. Ten minutes of testing every three months is what stops it becoming an eight-hour disaster.
Last updated: 8 August 2026