Robocopy Backup Failed for Weeks? The Vineyard Terrace

2026-10-30

Lena has a glass of cold white wine in one hand and her phone in the other. It is a Thursday, a little after four, on a terrace above a vineyard.

This is a holiday, sort of. Her partner booked the week months ago. She promised, truly promised, to leave the laptop shut. Then a client asked for one "tiny" change to a set of illustrations, and the laptop came along in the bag, just in case.

Now it is open on the stone table. The change took twenty minutes. She is almost proud of herself.

Then the project folder stops opening.

The folder that wouldn't open

At first it is only a grey spinner. Then a small window says the file or directory is corrupted and unreadable. Lena tries again. She restarts. She breathes out slowly, the way you do when you decide not to panic yet.

Then she remembers: I have a backup.

Years ago she wrote a little robocopy script, a few lines that copy her work folder to an external drive every night. She was pleased with it at the time. It felt grown-up. It felt like something a real business would have. Since then she has not thought about it once, which is exactly what she wanted.

She plugs in the drive she brought along, mostly out of habit. The folders look right. The names look right.

She sorts by date modified.

The newest file is from the ninth of September.

It is the second week of October.

Five weeks of nothing

You probably know this feeling, or you can guess it. It starts in the stomach and moves up.

She does the arithmetic anyway, because her brain insists. Five weeks. Three finished commissions. A whole children's book project, all the layered files, every revision. Sitting on one drive, on one laptop, which has just told her it can't read its own folder.

The scheduled task still shows "last run result: completed." It had been running all along. Every night it woke up, looked for a drive that was no longer called what the script expected, found nothing, wrote a short complaint into a log file in a folder she had never opened, and went back to sleep.

No email. No pop-up. No red light anywhere. The task did its job faithfully and the failure sat in a text file for five weeks, politely waiting for someone to ask.

She opens the log. It is full of the same line, repeated every night. It is not even a dramatic line. It is almost gentle.

What it cost, quietly

The files came back, in the end. A recovery tool, two long hours, and a cousin of her partner's who "knows computers" and was kind enough to stay on the phone. Most of it was fine. One illustration was gone, and she redrew it on the train home.

But the real cost wasn't the files.

It was the rest of that holiday. Her partner pointing at the view and Lena nodding, not seeing it. It was lying awake that night doing sums about what she would have said to a client: "I'm so sorry, I lost your work." It was the small, hot embarrassment of being the person who builds a safety net and never checks that it's there.

It was the thought she had on the terrace and could not shake: I'm supposed to be running a real business.

Nobody had told her the worst part. It wasn't that the backup failed. Things fail. It was that she didn't know for five weeks.

The turning point

On the way home she did not decide to become a systems person. She just wanted one thing: to never again find out by accident.

She wanted a copy that kept yesterday's version and last week's version, not only the latest one. She wanted a record for every single run, written in plain words, so "it ran" and "it worked" could finally be two different statements. She wanted to try the whole thing in a harmless practice mode first, to see what it would do before it touched anything real. And she wanted the old logs to tidy themselves away, so that reading them wasn't a chore she'd quietly stop doing.

That was it. Not a grand setup. Just a routine she could trust enough to forget, and still look at in ten seconds.

A different Monday

Picture the next ordinary Monday morning instead.

Lena sits down with coffee. She opens the folder where the run logs live. Today's file is there, dated this morning, the last line saying the copy finished and how many files it touched. She reads it the way you glance at a clock, and closes it.

The drive is plugged in. Last week's snapshot is there if she needs it, and so is the one before. If a file ever goes strange, she knows where to look and what she will find.

She does not think about backups for the rest of the day. She draws. She answers a client. At six she shuts the laptop and means it.

That is the whole difference. Not more technology. Just a quiet "yes, it worked" you can see, instead of a silence you have to trust.

If you recognise the terrace

Maybe your script is one you wrote years ago and haven't opened since. Maybe the task scheduler says everything is fine, and you would like to believe it. If a small cold feeling just crossed your stomach, you may not need a lecture. You may just need a calmer setup than the one you have.

We put together Backup & Log Rotation Scripts: PowerShell and Bash, with incremental snapshot backups, retention, log rotation and scheduling for Windows and Linux. There is a dry-run mode so you can see what will happen first, and a logfile for every run, so you can see what did.

It is here if you'd like to look: Backup & Log Rotation Scripts.

And if not today, do one small thing anyway. Open your backup drive and sort it by date modified. It takes ten seconds, and either answer is better known than guessed.

An illustrative story, written with AI assistance.