Blixwerk

Backup Hasn't Run in Weeks? The Lost Property Office

2026-10-21

The queue at the lost property office moves one umbrella at a time.

You are third in line, holding a numbered slip and a coffee that went lukewarm ten minutes ago. Yesterday you left your tote bag on the 17:42 train. A charger, a notebook and a pair of sunglasses you liked. Nothing that matters much. You tell yourself that twice.

To stop yourself staring at the shelves of single gloves, you take out your phone and open the little dashboard for your laptop backup. You don't know why. Habit, maybe. A way to feel organised while standing in a queue.

The dashboard says: Last successful backup: 36 days ago.

You read it again. The words don't change.

The quiet sort of dread

There is no alarm. No red banner. The thing never told you it had stopped. For five weeks it sat there looking like it was working, and you believed it, because why wouldn't you?

You are a freelance illustrator, and everything you have lives on that one laptop. Client files. Three half-finished brand packages. The signed contracts. The invoices you sent in September. The folder with the sketches for a children's book that you've never told anyone about.

The man at the counter calls "next, please" and the woman ahead of you steps forward. You don't hear what she says. You are doing arithmetic you don't want to do. Five weeks of work. How many files is that? Which clients? What would you say to the one with the Thursday deadline if the laptop simply did not turn on tomorrow?

Nobody warns you about this part of working for yourself. There is no IT department. There is no one who notices on your behalf. There is you, a laptop, and a promise you made to yourself once, in a calmer month, that it was handled.

What it quietly costs

You think about the last few weeks and what they would have felt like if you had known.

Probably the same, honestly. Deadlines, emails, a coffee on the balcony. That's the odd thing about this kind of problem. It doesn't hurt until, suddenly, it hurts completely. Until then it is just a small weight you carry without knowing, a faint "I should check that" that kept surfacing and getting pushed down again.

You remember it now. Three weeks ago, a pop-up. You clicked "remind me later." Of course you did. You were in the middle of a client call.

There is a particular embarrassment in this, too. You tell clients you are reliable. You are reliable. But a professional wouldn't have let this slide, you think, and then you notice the thought, and you try to put it down. It isn't fair. You were busy. You trusted a thing that was supposed to look after itself.

"Number forty-one?"

That's you. The man comes back from the shelves holding your tote bag. The charger is inside. So is the notebook. Even the sunglasses.

It is a small relief, and it makes the bigger one feel unfair by comparison. Some things you can get back by queueing patiently. Other things you only get back if you did something quiet and boring weeks ago.

The turning point, on a station bench

You sit on a bench outside, bag on your lap, and before you can talk yourself out of it, you plug in the external drive from your rucksack and copy the folders that matter. It takes eleven minutes. The progress bar creeps along while commuters stream past, and for the first time in an hour your shoulders drop.

And somewhere in those eleven minutes the real thought arrives, not the panic but the one underneath it: it doesn't have to be like this.

The problem was never that you forgot. It was that nothing ever told you. A backup that fails in silence is only a hope with a nice icon. What you want is something plainer. A snapshot every night. A short note that says what it did. The old copies tidied away so the drive doesn't fill up. And a record you can glance at, without trusting anything on faith.

You don't need to become a systems person for that. You just need it set up once, properly, by someone who thought about the dull parts.

A different Monday

Picture a Monday morning a few weeks from now. You carry your coffee to the desk, open the laptop, and there is a small logfile from last night. You open it. Three lines. Finished. Nothing went wrong. You close it again without a second thought.

That's the whole ceremony. Ten seconds.

Then you start on the client's logo revisions, and the sentence "I should check that" doesn't turn up at all. It's gone, like a tap you finally stopped hearing drip.

You might even do something you haven't done for ages: finish a day at six, close the lid, and not carry a faint hum of worry into dinner.

If you recognise yourself here

If you read that dashboard line and felt your stomach drop, you are in good company, and the fix is smaller than the dread suggests. We put together Backup & Log Rotation Scripts (PowerShell + Bash): incremental snapshot backups, retention, log rotation and scheduling for Windows and Linux. There is a dry-run mode so you can see what it would do before it touches anything, and a logfile for every run, so you never have to wonder again. It comes with a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

Have a look when you're ready: Backup & Log Rotation Scripts.

And today, copy the important folders somewhere safe. Eleven minutes on a bench is enough.

An illustrative story, written with AI assistance.

Sounds familiar? Backup & Log Rotation Scripts (PowerShell + Bash) – Incremental snapshot backups, retention, log rotation and scheduling for Windows and Linux. Dry-run mode and a logfile for every run.

Take a look