Blixwerk

Backup Overwrites Yesterday's Copy? The Hotel Lobby Wi-Fi

2026-10-29

The hotel lobby smells of coffee and wet umbrellas. You are on a sofa that is too low, laptop on your knees, trying to look like someone who is not on holiday.

You are, technically. Three days at the coast with your partner. But a client wrote at 8:15: "Hi, the pricing page looks different from last week. Can you put back what we had on Tuesday?"

Easy, you think. You wrote a backup script months ago. It runs every night. You feel a small, quiet pride about that.

You connect to the server over the hotel Wi-Fi, which drops every ninety seconds. You open the backup folder.

There is one folder in it. One. Its date says this morning at 03:00.

The folder that only remembers today

You refresh. You scroll. You look for a second folder, a zip, anything with Tuesday's date.

Nothing. Every night the script copies the current state over the previous copy. Same name, same place. It has never failed, not once. It has also never kept anything.

The backup is a mirror. And the mirror shows what the pricing page looks like right now, which is exactly the thing your client wants to undo.

Your stomach does a slow, small drop, like a lift starting down.

A waiter sets a cup next to you. You say thank you without hearing yourself.

The worry nobody says out loud

It is not only about the pricing page. That one you can probably rebuild from memory and a screenshot in the client's inbox.

It is the thought underneath. If this is how it works, what else have I been trusting?

The invoice folder. The project files from the spring. The database you export "when you remember". You have been telling yourself for months that you have a backup. You have had a copy, which is something else, and you did not know it until a client asked a normal question.

The cost is quiet. You write back, "Let me look into it and come back to you this afternoon," in a voice that sounds calmer than you are. You stop reading the sea through the window. Lunch is a sandwich you do not taste. Your partner asks if everything is okay and you say "just work," which is true and tells them nothing.

You also feel a little foolish. Real businesses have real backups, you think. Not a script that quietly eats its own yesterday.

Not a failure, just a missing second day

That evening, on the balcony with the laptop closed for once, the thought arrives slowly.

You did not do something terrible. You did the first half of a good idea. The script runs. The files land. What was missing was memory: a few days kept, a few weeks, the older ones tidied away on their own, and a note of what happened each night.

You realise you have been treating "I have a backup" as a yes or no question. It is closer to a different one: how far back can I go, and would I know if it stopped?

That is much easier to live with than the first question. It has an answer you can look at.

You rebuild the pricing page from the client's own email thread. It takes forty minutes. You send it with a short, honest note, nothing dramatic. They reply with a thumbs-up and "thanks, looks right." The world did not end. But you do not forget the feeling of that folder with one date in it.

What a normal Monday could feel like

Picture the Monday after the trip. Coffee, the window half open, the neighbour's radio somewhere below.

You open the backup location, not because something broke, but because you like looking. There are folders for the last several days, one for each week, a few older ones. You do not have to remember what is in them. You are not guarding anything.

There is a small text file for every run. It says what was copied, what was skipped, and whether anything went wrong. You skim last night's in ten seconds, the way you glance at a weather app.

When a client says "can you go back to how it was on Tuesday?", the answer is a calm "yes, give me a few minutes." Not a stalling email from a hotel sofa.

The disk does not quietly fill up either, because old copies and old logs tidy themselves away on a schedule you chose once and then stopped thinking about.

Nothing about that is exciting. That is the point. It is the feeling of a door that is locked, and you know it, without checking it three times.

If you recognised the folder

If your own backup folder has just one date in it, you are in very ordinary company. Most of us build the copy first and the memory later, usually after the first question we cannot answer.

We put together Backup & Log Rotation Scripts (PowerShell + Bash) for exactly this stage: incremental snapshot backups that keep earlier days, 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. It was made with AI, checked automatically and refined by real use, and it organises your files. It does not replace thinking about what matters most to you.

If it does not help, there is a 30-day money-back promise, no questions.

You can have a look here: Backup & Log Rotation Scripts

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