Cron Backup Stopped After Server Update? The Bouncy Castle

2026-11-03

The bouncy castle man is still unrolling the cables when your phone buzzes.

It is Saturday, 11:20. Your nephew turns six today. There are twenty children in the garden, a table of paper plates, and a cousin asking whether anyone has seen the lighter for the candles.

The message is from Karin, who runs a small ceramics shop. You built her site and you look after the little server it lives on.

Hi Jonas, sorry to bother you on a weekend. I think I deleted the product photos by accident. Can you bring back yesterday's version? The market is tomorrow and I need the shop up.

Your stomach does something small and cold.

"Yesterday's version" should be easy. You set up a nightly backup months ago. You remember it clearly: a tidy little job, a folder with dates in the names. You haven't thought about it since, and that was the whole point.

The folder you open standing next to the cake

You walk to the side of the house where the signal is better. You log in from your phone, thumbs too big for the keys, and list the backup folder.

The newest entry is nineteen days old.

You read the date again. Then you count backwards, as if the number might change. Nineteen days ago is the evening you ran the server updates. You remember that evening. Everything restarted, the websites came back, you closed the laptop and felt quietly virtuous.

Nothing told you otherwise. No error. No email. No red anything. The job simply stopped, the way a clock stops in a room you don't often enter.

From the garden, someone shouts that the castle is ready. Twenty children cheer.

You stand by the recycling bins and type a careful reply to Karin. You say you're looking into it. You don't say that you may have nothing recent to give her. You don't say that for nineteen days you believed in something that wasn't there.

What it quietly costs

The photos, as it turns out, are recoverable. An older copy, a few files Karin still has on her phone, an hour of patching things together on a plastic garden chair while someone hands you a paper cup of lemonade.

But the afternoon is already spoiled in a small, specific way. You smile at the party. You clap when the candles go out. Part of your mind sits in a folder listing, doing sums about which other clients' sites sit on that same server, and how many days of their work were unprotected too.

That is the part nobody tells you about working alone. You are the IT department, the one who is supposed to notice. And the only alarm you ever set was your own memory.

It isn't really about the nineteen days. It's the thought that came with them: what else have I assumed is fine?

The moment it stops being a mystery

Late that afternoon, with the children finally sugar-quiet and the castle deflating with a long sigh, you realise something that is almost funny.

The update didn't do anything dramatic. It changed a small thing underneath, and a job that had run faithfully for months simply had no way to tell you it wasn't running. Nobody was watching because the job was the only thing watching.

You don't need a cleverer memory. You need a setup where every run leaves a trace. A plain logfile, written each time, so that silence itself looks wrong. You need a way to try a change without risking anything, and old copies that tidy themselves away instead of piling up until the disk fills.

That's all. Not a big system. Just something that says "I ran, here is what I did" every single time, and makes the absence of that sentence easy to spot.

An ordinary Monday, afterwards

Picture the Monday after you've put that in place.

It's 8:40. Coffee is still too hot to drink. You open the logs folder and glance down the list: one file per run, one line at the bottom of each saying it finished. It takes about as long as reading a shop receipt.

The server updates again that week, because servers do. You don't hold your breath. You look at the next morning's log, see it there, and carry on with your day.

When Karin writes at the weekend, you read the message with curiosity instead of dread. If she's deleted something, you know roughly where yesterday's copy is, because you saw it appear.

The party garden, the paper cups, the cold stomach by the bins: those belong to a different version of your life. In this one, backups are boring again. That is the highest compliment you can pay a backup.

If you recognise the folder

If you've ever opened a backup directory and found it quietly weeks behind, you're in good company. It happens to careful people, usually right after they've done something responsible like updating.

We put together Backup & Log Rotation Scripts (PowerShell + Bash) for exactly this: incremental snapshot backups, retention, log rotation and scheduling for Windows and Linux. There's a dry-run mode so you can see what would happen before it happens, and a logfile for every run, so a stopped job doesn't stay invisible.

It won't make decisions about your data for you, and it's worth testing a restore once, calmly, on a quiet day. But it can make the question "did it run?" take five seconds instead of a ruined Saturday.

If that sounds like the Monday you'd like, you can take a look here. There's a 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

An illustrative story, written with AI assistance.