How Do You Know If Your Backup Actually Ran?
What I set up after a client's nightly backup missed two mornings without a word, and the steps to check your own this week.
If someone set up your backup years ago, you need a way to know it still runs each night. In my experience, that takes two alarms: a warning inside the job that explains a failure where someone will see it, and a separate daily check for today's copy. The separate check catches the morning when the backup never started at all, so it couldn't report its own failure.
Key takeaways
- A failure message in a window that immediately closes gives you very little help.
- Compare the newest copy's date and size with the copies before it.
- A warning should stay visible after the program that created it stops.
- A second, separate check catches the night the backup never started.
- Label a warning test clearly so nobody mistakes it for a real problem.
What happened to the backup I built?
A backup I built and run for a small firm missed two mornings in October 2026, and nothing told me. Their web app keeps its records in a database, basically an organized collection of information, at a hosting company. Every morning, my PC was supposed to copy that database into a Google Drive folder. I found the missing copies by chance two days later and made one by hand.
The hosting company had signed everyone out of a tool the backup depended on. My program printed "FAILED" with the reason and stopped without overwriting the last good copy, which is exactly what I'd written it to do. When someone asked how I felt finding that out, my answer was "Scared."
Why didn't anyone notice?
The backup started through a scheduled task, the Windows feature that runs a program at a set time without anyone clicking anything. Its failure message appeared in a window that closed as soon as the program stopped. This happened early in the morning while everyone was asleep. Windows also recorded a failure code, on a screen nobody opens.
So the program reported the failure correctly, but I hadn't made that report useful to a person. There's a related checking problem in how to tell if AI actually did the work. With that kind of tool, you're checking whether "done" matches what happened. With this backup, I needed to make sure someone saw "failed."
What does the first alarm do?
The backup now gives a plain-English reason and a fix when something goes wrong. It covers things like the hosting tool signing out, no internet, Google Drive not running or a copy coming back too small. A problem that might clear on its own gets one retry after 60 seconds. Every run also adds a dated line to a log file, a plain text record of what happened.
I chose a warning window that stays above the other windows until someone clicks it. Every failure so far needed attention on that PC anyway, so the warning sits where the fix happens. For this setup, an email would have needed an extra mailbox password stored on that computer, and a phone notification would have added another app and another service.
The warning also has to survive after the backup stops. Windows ends this scheduled task after 30 minutes and can close anything the task opened. So I made the warning open as a separate program, and tested through the real scheduler that it stays visible after the backup program exits. I also cut the copy's time limit from 15 minutes to 5, since a copy takes about five seconds, so the whole run finishes well inside those 30 minutes even with a retry.
Why does it need a second alarm?
A separate task now checks at 9:00 every morning and 15 minutes after I sign in. It looks for today's backup file. If there isn't one, it displays "No backup of the app was taken today." It stays quiet if the backup already reported a failure that morning, so I don't get the same warning twice.
This catches a different set of problems: the PC was off, someone switched the task off or something it needed moved. The check runs on its own, asks a different question and is written in a different programming language from the backup, so one broken piece is much less likely to silence both. Both still run on the same PC, though, so neither can warn me while that computer is off.
My own LinkedIn posting queue ran empty twice without telling me, once for nine days. Now a small program reports how many days of posts remain whenever I start a work session on my computer. It checks the queue separately from the tool that posts, so I can see an empty week before it happens.
How do you check your own backup this week?
The Federal Trade Commission's Cybersecurity for Small Business page says to "make it a habit to back up important files regularly." That's the advice you've probably heard already. These steps help you find out whether the backup you arranged is still happening.
- Find where a failure gets reported today. Look for an email, a log file or a status screen in the backup software. Until someone shows you where warnings go, treat them as unverified.
- Look at the newest backup. If it isn't a file you can see, ask your provider or whoever maintains it to show you the latest one that finished. Check that it's from when it should be and that its size makes sense compared with earlier copies.
- Get every failure message explained in plain words, with what to do about it. If the software can't change its messages, a short written note next to each code does the job.
- Put the warning where someone will see it. Ideally, that's where the person can also fix the problem, and everyone agrees who it goes to.
- Add a separate check at a set time, after the backup should have finished. Ask your provider or whoever maintains it to turn on a missed-backup alert or set one up, with one question to answer: "Is the latest backup there?"
- Test both warnings on purpose, the failure warning and the missing-backup warning. Label each test TEST, change nothing live, and confirm it appears where you expect.
- Now and then, ask whoever maintains it to restore one file somewhere safe, without replacing anything live. A date and a size can flag a problem, but only a restore shows the copy works.
How did I check that the warnings worked?
I checked the plain-English explanations against 15 sample error messages without changing anything live, and all 15 came out right. Then I ran a real copy of the live database without saving it anywhere, and ran the warning through the real Windows scheduler. Its title said "TEST, nothing is wrong."
I also tested the morning check with a backup present and with one missing. It stayed quiet when it should and showed the expected warning when the file wasn't there. The backup folder's instructions now include a section called "If it fails, you will know," showing what the window looks like.
Frequently asked questions
Isn't an email alert enough?
An email can carry the failure warning, but it still needs something to send it. If the backup never starts, its own email warning never starts either. That's why I added a separate check.
How often should I check my backup?
For this daily backup, I set the separate check to run every morning at 9:00 and 15 minutes after I sign in. That checks for the copy expected that day.
What if my backup is a plugin or a cloud service?
Ask where it reports a failure and whether anything separately checks that today's copy exists. You can give those questions to whoever looks after the website or computers, even if you didn't set the backup up yourself.
Will the warning work if the computer is off?
The warnings on my PC can't appear while it's off. The extra check 15 minutes after sign-in gives it another chance to tell me that today's copy is missing.
Do I need to cause a real failure to test the warning?
I tested the error explanations with sample messages and ran the warning window separately through Windows. That let me check the message and where it appeared without changing the live records.
Help with a job that runs on its own
I build and run custom AI tools and business automation for small businesses, including jobs like this backup. If you need help checking one, tell me what it's supposed to do and when it should run. Start by asking the person who maintains it to show you where a failure would appear.
Want a system built for your business?
Everything here comes out of real work, mine and my clients'. If you want something custom, let's talk.
Get in touch