Our backup software has been failing for weeks and nobody noticed
This is how you discover you do not have a backup. Open the logs now, before the real disaster.
Try this first
- 1Open the backup tool and look for the last "success" run. More than a week ago is a problem.
- 2Read the error literally; it usually states what went wrong. "Disk full", "credentials invalid", "VSS snapshot failed": all fixable.
- 3For "disk full": delete old backups beyond retention. Or tighten retention. Then start a new run immediately.
- 4For "credentials invalid": refresh the service account password in the backup software. Often someone's AD password expired.
- 5Set a weekly check email so this cannot drift unnoticed for three weeks again.
When to bring us in
Cannot read the logs, or the error is beyond the above? Drop us a line. Failing backups are more urgent than they look.
See also
- We have backups but we do not know if they workA backup that cannot be restored is not a backup. Testing matters as much as taking the backup.
- Suspected ransomware: what to do RIGHT NOWThe first 30 minutes are critical. One wrong move spreads the damage. Read before acting.
- Someone accidentally deleted an important folderUsually fine to recover. The trick: do not save anything new on that drive until you know how.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.