---
title: "A folder rename that turned up one saved copy labeled initial"
canonical: https://dxdev.com/everyday-ai/backup-that-had-not-run-for-three/
datePublished: 2026-04-23
---
The only saved copy of our system was dated April 2 and labeled `initial`. We were looking at it on the day we renamed the folder where a lot of our work lived. A copy was supposed to be made every Sunday at 4 a.m., so one copy meant the [weekly backup had not been running](/everyday-ai/three-weeks-and-a-check-mark/) for three weeks.

A backup is a spare copy of important work, kept somewhere else so a mistake, a broken computer or a lost file does not become a disaster. We thought this one was being made automatically. The schedule still existed and the old setup was still sitting there. From a distance, everything looked settled.

## A boring cleanup

We expected that day to be dull. One large work folder was being split into five smaller ones, each with a clearer job. One held the routines and instructions. Another held private notes and drafts. Another held material meant for the public. A fourth held original source material that should not be edited. The old setup was frozen in place, like a box of receipts you keep because you may need to understand how something used to work.

We started by changing 43 files that still pointed to the old folder address. That part went fine, but it did not solve the problem we thought we were solving. We assumed that once the addresses inside the folder were fixed, the routine around it would be fine too. It was not. The day we thought we were spending on a rename became an audit of things that had been left behind.

## What was left behind

The first clue was six cron entries. A cron is a list of small jobs a computer has been told to do at certain times. There were also seven programs set to start automatically when the computer turned on, two leftover helper programs, and one retired database program. Some still referred to the old folder. Others belonged to older projects that had outlived anyone paying attention to them.

The backup was the part that made our stomachs drop. It had not been sending a loud warning. It had been trying to run and writing an error into a log nobody read. From the outside it still looked scheduled. From the inside it had stopped doing the one thing it existed to do.

A second routine had been collecting no useful information every 30 minutes for weeks. It depended on another program that had not been restarted after the computer rebooted. Again there was no dramatic failure, only a small message repeated over and over in a place nobody was checking.

A thing can be broken without looking broken. A calendar reminder can still be on the calendar. A store's security camera can still have a green light. A scheduled payment can still appear in an app. None of those signs prove the job itself happened.

The cost was a day we had expected to spend moving folders, plus the risk that important work had gone unprotected for three weeks. There was also the ordinary, expensive cost of false comfort. Nothing had obviously failed, so we had no reason to panic. We just had something we trusted that nobody had ever actually checked.

## A list that admits what is missing

Once the old pieces were cleared out, we made a small checker to look through the project folders and list what was still active, what was paused, and what had been deliberately put away. On its first pass it found 23 projects: 10 active, 2 for clients, 7 dormant and 4 frozen. It also called out any project that was missing from the list instead of silently skipping it.

That last detail matters. A forgotten thing does not become safer because it is absent from the report. Putting it in a separate "needs a decision" pile forces an honest choice: keep it, restart it, archive it, or remove the pieces that are still running. Two half-finished projects turned up with old startup instructions still pointing at them. They were not part of the folder move. They were separate reminders that unfinished work can keep taking up space long after attention has moved on.

You do not need a wall of computer commands to recognize this pattern. You may have a paper filing system, a shared drive, a payroll reminder, a spare key, a sprinkler timer or a business phone line. The question is the same: when did someone last check that it actually did the job, rather than checking that it still looked like it was set up?

## On Monday

Pick one thing you count on happening automatically and ask for the last successful proof, with a date. Ask for the proof, not the schedule or the settings page. If nobody can show it to you, you have found the next thing worth checking.