Scared of Ransomware, No Automatic Backup? The Tax Week Hum

2026-10-23

It is Tuesday, a little after eleven in the morning. The accountant's deadline is on Friday. You are standing in the small back room of your office, holding a mug that has gone lukewarm, and the server is humming under the desk like it always does.

You have never really listened to it before.

Three days ago a friend who runs a physiotherapy practice told you, almost in passing, about a neighbour's business whose files were locked overnight. Nothing more than a story over coffee. But it stuck. Now every sound the little box makes feels like a question.

And the question is simple. When was anything on this thing last copied somewhere else?

You don't know.

The answer you can't give

You sit down and open the shared folder. Invoices. Contracts. Client photos. Three years of quotes. Year-end files that your accountant will ask for on Friday.

You remember that someone, once, set up something. A script, maybe. Or a task. You think it was a colleague who has since moved on, or perhaps it was you on a quiet Sunday two summers ago. You can't say for sure that it still runs. You can't say where it puts things.

So you do what most people do. You decide not to think about it until after tax week.

But the thought keeps coming back, quietly, in the gaps. While you answer an email. While you stand in the kitchen waiting for the kettle. It is a small, steady weight. Not panic. More like a stone in your shoe that you keep walking on.

What it quietly costs

Nobody talks about this part. You are not losing money today. Nothing is broken. Yet something is being spent anyway.

It is the half second of dread when a file takes too long to open. It is the way you hesitate before installing an update. It is the lightness you don't feel on Friday evening, because part of your mind is still in that back room, listening.

It is also a small feeling of not being a proper business. Bigger companies have someone for this. You have a box under a desk and a vague memory.

And you are, of course, the someone. You always are.

The moment it shifts

Later that afternoon you stop trying to fix everything at once. You ask yourself a much smaller question instead.

What would I need to see, to stop worrying?

Not a lecture on security. Not a project. Just this: a copy of the important things, made on its own, kept for a sensible number of days, with a note every time it ran. A line you could glance at that says: yes, last night, it worked. And if it didn't, you would see that too, in plain words, instead of finding out in the worst possible week.

That is all. It isn't a fortress. It is a habit that happens without you.

The relief comes surprisingly fast, just from naming it. The stone in the shoe has a shape now, and a shape can be dealt with.

A different Tuesday

Picture the same room a few weeks later.

It is Monday morning, ten past nine. You come in, put your bag down, and open one small text file. It lists last night's run, the time it started, the time it ended, how many files were copied, and what it cleaned out because it was old. Four lines. Nothing red.

You close it and make your coffee.

The server hums under the desk, and it is just a sound again. You are thinking about the quote you need to send, about the call at ten, about whether to take Thursday afternoon off. The old question, the one that used to sit behind everything else, has gone quiet.

Nothing dramatic happened. Nothing was installed that you have to admire. It simply runs while you sleep, and tells you what it did.

That is what calm looks like in a small business. Not the absence of risk, because no one gets that, but the feeling that you have done the sensible, ordinary thing and can see that you have.

If you recognise the back room

Maybe your version is a Windows machine in a cupboard. Maybe it is a Linux box someone set up years ago. Either way, the feeling is probably familiar: you suspect there is a backup, you can't prove it, and you would rather not find out the hard way.

We put together a set of Backup & Log Rotation Scripts for exactly this moment, in PowerShell and Bash. They make incremental snapshot backups, keep them for as long as you choose, rotate the logs so the disk doesn't quietly fill up, and handle the scheduling. There is a dry-run mode, so you can see what would happen before anything is touched, and a logfile for every run, so you can see afterwards what did.

They are made with AI, checked automatically and refined by real use. They are a tool for organisation, so you stay in charge of what gets backed up and where it goes. If you are unsure about your setup, it is worth asking an IT professional to look it over.

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

If the hum under the desk has started to sound like a question, you can have a look here: Backup & Log Rotation Scripts.

An illustrative story, written with AI assistance.