Overwrote a File, No Backup? The Left-Luggage Counter

2026-10-28

Tomasz is standing at a left-luggage counter in a train station, holding a ticket for a bag he has not yet handed over.

He is not thinking about the bag. He is thinking about the laptop under his arm.

This morning, at 8:10, he saved a file. The wrong file, into the wrong folder, with the right name. Eleven days of work on a client's 3D visualisation was replaced by a near-empty template. The save bar finished. The window closed. Nothing flashed red. That was the worst part: it all looked perfectly normal.

The review call is at ten.

(Tomasz is an illustrative character. The scene is made up, but you may know the feeling.)

The quiet after the click

He opens the folder again. Maybe he misread it. He hasn't.

The modified time says 08:10. The file size is a fraction of what it was. He right-clicks, looks for "previous versions", and finds nothing. He checks the recycle bin, which is useless because nothing was deleted. Something was replaced, and that is a different kind of gone.

Then he looks for the backup.

He remembers one. A drive, a plan, a Sunday evening back in spring when he told himself he'd set it up properly. He finds a folder with a promising name. The newest thing in it is from April.

The man at the counter asks, "Next, please?" Tomasz steps aside and lets someone go ahead of him.

What it costs that nobody writes down

The file itself is only part of it.

There is the call at ten, where he will have to say something true and uncomfortable to a client who pays him to be the calm one. There is the arithmetic he can't stop doing: eleven days, a deadline on Friday, an invoice that now can't go out. There is the small, hot shame of a person who looks after other people's deadlines and did not look after his own files.

And under that, the thing freelancers rarely say out loud: there is nobody else here. No IT department. No colleague who says "oh, we have last night's copy." Just you, a screen, and a decision you made months ago to deal with it "next week".

He pays for the coffee he doesn't drink. He opens the email to the client and types, Something has come up with the files. He deletes it. He types it again.

The part where it turns

Here is where we could tell you the file was recovered by a miracle. Sometimes that happens. Often it doesn't, and a story that depends on luck is not much use to you.

So let us tell you a different Tomasz instead, a few months later. Same station, same kind of morning, same mistake. A tired hand, a wrong folder, a Save that went through.

He feels the same stomach drop for about four seconds.

Then he remembers that last night, while he was asleep, his laptop quietly took a snapshot of that folder. And the night before, and the night before that. He didn't do anything heroic to make that so. He set it up once, on a calm afternoon, and it has been taking care of itself ever since.

He goes and finds yesterday's version. He looks at it. It is exactly what he remembers. He copies it back, drinks his coffee, and takes the ten o'clock call with nothing to confess.

The mistake was identical. What changed is that it stopped being a crisis and became a small, boring correction.

What a normal Monday feels like after

There is a particular quiet to it.

You sit down, open the laptop, and you don't scan the folders with a faint dread. You don't have a mental list of "things I should really copy somewhere." You work, you save, you overwrite things the way people do, and the ground under you holds.

Once in a while you glance at a plain little log file. It says, in dull language, that the last run finished and what it kept. It is the most reassuring boring text you will read all week.

You also know you can ask the system what it would do before it does anything, so you never have to trust it blindly. For someone who works alone, that matters more than it sounds.

Nobody congratulates you for this. There is no applause for the disaster that didn't happen. But your shoulders sit a little lower, and you sleep better on the night before a delivery.

If you recognise the folder from April

Maybe you have your own version of that folder. The backup that was going to happen. The drive in the drawer. The plan that lives in your head and nowhere else.

There is a small, calm set of scripts for Windows and Linux built for exactly this: incremental snapshots, sensible retention, tidy log rotation, scheduling, a dry-run mode so you can see what will happen first, and a logfile for every run. It is the kind of thing you set up once on a quiet afternoon so that a bad morning stays a small one.

If you'd like to look, it's here: Backup & Log Rotation Scripts (PowerShell + Bash). If it doesn't help, there's a 30-day money-back promise, no questions.

And if the bad morning has already happened: be kind to yourself. Send the honest email, then make the afternoon calm.

An illustrative story, written with AI assistance.