Server Disk Full Again? Old Log Files and a 7:45 Client Call

2026-10-15

7:45 on a Monday, standing at the bus shelter

Your phone buzzes with a message from a client. Two words: "Site down?"

You are standing at the bus shelter with a coffee that is still too hot. Rain on the glass. You open the laptop bag on your knee, which is not a good idea, but you do it anyway.

You know before you log in. You have known for weeks, somewhere in the back of your head.

The disk is full. Again.

The folder nobody opened

You connect over SSH on mobile data, one bar, typing with your thumbs. The command comes back with a number that makes your stomach drop. One hundred percent. No space left on device.

You look for the cause, and there it is. A folder of logs. Months of them. Every night the server wrote a little more, and every night nobody looked.

You remember the last time. You deleted a pile of old files in a hurry, promised yourself you would set something up properly, and then a project landed and the promise slid to the bottom of the list.

Now the bus is late and the client is waiting. You delete files with your heart in your throat, because one wrong path and you would be explaining something much worse than a full disk.

What it quietly costs

The site comes back after ten minutes. The client writes, "Thanks, all good now?" and you answer, "Yes, fixed."

It is true. But it does not feel true.

Because the cost was never the ten minutes. It was the cold feeling at the bus stop. It was the small lie of the word "fixed" when you know it will happen again in three months. It was the way you spent the first hour of your week feeling like someone who is winging it.

You work for yourself. There is no colleague who says, "Oh, I'll look after that." The server, the backups, the logs, the quiet jobs that nobody sees until they fail: all of it is yours.

And there is a second worry behind the first one, the one you rarely say out loud. If the disk can fill up without you noticing, what else is quietly piling up? Are the backups really running? When did you last check that one actually worked?

The small thought on the way home

That evening you sit on the sofa with tea and no laptop. You are not angry, just tired in a specific way.

A thought arrives, quite gently. This does not have to be a thing you remember. It could be a thing that simply happens, every night, the same way, and leaves a note saying what it did.

Not a clever setup. Not a weekend project. Just a boring routine: old logs get tidied away on a schedule, a fresh copy of what matters is kept, and anything older than you need is let go. A routine that tells you what it would do before it does it, so you are never afraid of the delete key. And a small record of every run, so you can read it in thirty seconds instead of guessing.

You realise that what you want is not a fix. It is permission to stop thinking about it.

A different Monday

Picture the same week, a few weeks later.

It is 7:45 again. You are at the same bus shelter, the same coffee, the same drizzle. Your phone buzzes, and it is a client asking about a deadline. Nothing else.

You answer it in two lines. The bus arrives on time, which feels almost like a bonus.

On the ride you don't open the laptop. You look out of the window. Somewhere a server is quietly doing its small, dull job: logs rotated overnight, older ones compressed and cleared, a snapshot taken, a line written in a file saying all went well.

Later, at your desk, you glance at that file the way you glance at the weather. Green. Fine. You close it.

There is a particular kind of calm in that. Not excitement. Just the absence of a knot you had gotten so used to that you forgot it was there.

When a client asks, "Are our backups okay?" you can answer plainly, because you have looked, and there is a record. That is what feeling like a real business is made of, more than any logo or invoice template. It is the dull, reliable things behind the scenes.

If you recognise the bus shelter

Maybe your version is a different place. A queue, a kitchen, a car park with one bar of signal. The disk is full, the logs are old, and you are sure you will deal with it properly "soon".

If that is you, there is a small set of ready-made scripts for exactly this: Backup & Log Rotation Scripts (PowerShell + Bash). They cover incremental snapshot backups, retention, log rotation and scheduling for Windows and Linux. 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 always know what happened.

They are a starting point, not magic. You still decide what to keep and for how long, and it is worth testing them on a non-critical folder first. But the blank page is already filled in.

If it does not help, the 30-day money-back promise means you can ask for a full refund, no questions.

Have a look at the Backup & Log Rotation Scripts

The next time your phone buzzes at 7:45, you might just let it be a question about a deadline.

An illustrative story, written with AI assistance.