Backup Stopped Weeks Ago? The Laptop Repair Counter

2026-10-20

It is Tuesday, 11:20, and you are standing at a repair counter that smells of solder and instant coffee.

Your laptop lies on a grey anti-static mat. The screen flickers, goes black, flickers again. The technician, a young man with a lanyard and a patient face, turns it over and says, "Could be the board. Could be nothing. Before I open it: when did you last have a backup?"

You answer fast. "Oh, it runs every night."

You say it the way you say "I'm fine" to a neighbour. It is automatic and mostly true.

The answer you were sure about

"Great," he says. "Can you show me?"

You borrow the counter's spare monitor and plug in the external drive you keep in your bag. You open the folder where the nightly copies live and sort by date.

The newest one says 2 September.

You look at the calendar on the wall behind him. It is the end of October.

You do the sum quietly, the way you do when you don't want anyone else to hear it. Seven weeks. Seven weeks of invoices, drafts, a finished project, a folder of client photos you finally sorted. All of it lives in exactly one place, and that place is currently flickering on a grey mat.

"Ah," says the technician, kindly. He has seen your face before, on other people.

What it quietly costs

Here is the part nobody says out loud. The backup didn't fail with an alarm. It simply stopped, and nothing told you. Maybe an update changed a setting. Maybe the drive went to sleep. Maybe a password expired somewhere. You will never know, because nothing was written down anywhere you would look.

For seven weeks you felt safe. That is the odd cost: you spent seven weeks trusting something that wasn't there.

Now the safety is gone and the worry arrives all at once. You think about the client who needs the final files on Friday. You think about the work you can't redo. You think about the sentence you may have to write: "I'm sorry, there's been a technical problem." You think about how it sounds from someone who is supposed to run a real business.

The technician is professional about it. "I'll try not to touch anything until I know what's wrong. Give me an hour."

An hour. You go and stand outside.

One hour on a bench

There is a bench by the tram stop across the road. You sit on it with a paper cup and don't open your phone.

You are not thinking about the laptop. You are thinking about the habit: I set it up once, years ago, and I never looked at it again. You were proud of that setup. It felt like the grown-up thing to have done.

But a job you never look at is a job you only hope is running. And hope is a thin thing to keep your whole working life on.

The tram comes and goes. A woman next to you eats a pretzel. Slowly something shifts, and it isn't panic any more. It is a plain, quiet thought:

It doesn't have to be like this. I don't need to be a systems person. I need to be told, simply, whether last night happened.

The good news, and the better one

The technician waves you back in. The fault was a loose connector. He reseated it, the screen holds steady, and everything is still there.

You breathe out for what feels like the first time since eleven.

He doesn't lecture you. He just says, "Lucky one." Then he turns the laptop around, and you both look at it, and neither of you says anything for a moment.

That is the real turning point. It isn't the fright. It is the relief that arrives after the fright, which makes you finally ready to fix the thing properly instead of promising yourself you will.

What a calm Monday looks like instead

Picture a different ordinary week.

On Monday morning you open one small file, a plain logfile, and read one line: last run, last night, finished, nothing missing. It takes ten seconds. You close it and move on to your coffee.

If something had gone wrong, it would say so there, in words you can read, with the date. A quiet gap would not stay quiet for seven weeks.

Older copies tidy themselves away on a schedule, so the drive doesn't quietly fill up and stop. When you change something, you can try it as a rehearsal first and see what would happen before it touches a single file.

None of that is exciting. That is the point. The best backup is the one you stop thinking about, because you can see it working.

And the sentence you never had to write, I'm sorry, there's been a technical problem, stays unwritten.

A gentle next step

If you recognised yourself at that counter, there is a small set of scripts made for exactly this: incremental snapshot backups, tidy retention, log rotation and scheduling for both Windows (PowerShell) and Linux (Bash). It has a dry-run mode so you can rehearse before anything real happens, and a logfile for every run so you can see what happened instead of hoping. It is made with AI, checked automatically and refined by real use.

It comes with a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

Backup & Log Rotation Scripts (PowerShell + Bash)

You don't need to fix everything today. Just make sure the next time someone asks, "When did you last have a backup?", you can answer with something better than "it runs every night."

An illustrative story, written with AI assistance.