A Simple Change Log for What You Just Copied

A backup you cannot describe is a backup you will not trust in a crisis. Did the spare get the scans from April, or only the photos? Did you skip the phone because it was in another room? A change log is a few lines written at the end of the session, in an ordinary text file, saying what you did. It is not a journal of your feelings about storage. It is how the next session starts from fact instead of from a vibe that you are probably fine.

Keep one note in a place you will actually open

Put a text file called backup-log in the archive folder and a copy of the latest lines in the same paper folder where you keep other household notes if you want a version that is not on the disk. One file is better than a new document every week, which you will not find. Add entries in the same place each time, either always at the top or always at the end. The file should open in any editor, which is why plain text fits the advice in notes worth keeping as text. If the log lives only inside a backup program's history, you cannot read it when that program is the thing that failed.

Write the date, the destination, and the sources

Each entry needs the date, where the copy went, and which sources you touched. A source can be the phone, a memory card, the downloads inbox, or a finished project folder. Name the ones you skipped on purpose. Skipped is useful information. It tells future you that the club laptop was not included, so the absence is not a mystery. You do not need file counts unless they helped you notice a problem. A sentence is enough: copied May phone photos and the scans inbox to the home spare, did not copy the work laptop because it was at the office. That sentence is the whole point of the log.

Record the check, including a weak one

If you opened a file from the destination, name it. If you did not check, write that you did not check. An honest blank is safer than a memory that upgrades itself into confidence. The Sunday habit of opening one new file is the kind of check worth logging in a single clause. If a copy failed partway, write where it stopped and do not smooth the story into a success. The log is allowed to be dull. It is not allowed to be promotional. You are not persuading a reader that the household is organized. You are leaving a breadcrumb.

Use the log at the start of the next session

The next time you sit down, read the last entry before you plug anything in. It will tell you the gap. If the phone was skipped, the phone is first today. If the spare was the destination last week, you know which drive should be on the shelf. This is cheaper than reconstructing the gap from file dates scattered across devices. It also helps when more than one person touches the archive. A shared folder's owners can read the same lines and see who copied what. Without the log, each person assumes the other did the boring part.

Do not let the log become a second project

If the entry takes more than a couple of minutes, you are writing too much. Keep details of a rescue or a failure, and keep ordinary weeks short. The log does not replace labels on drives, a shelf map, or the copies themselves. It explains them. When the file gets long, you may move old years to an archive section of the same file or a dated sibling file. Do not delete the history the moment it scrolls off the screen. The day you need to know whether a drive ever held the scans, last year's lines are the answer. Write them as if you will be slightly panicked when you read them. Panic likes short sentences.

Frequently asked questions

What if I forget to write the log? Write the next entry anyway, and say you are unsure about the previous week. Do not fabricate a session. A gap in the log is information. A fictional backup is how you stop looking for the files.

Can the log live in a spreadsheet? Yes, if you also keep it simple and you export a copy you can read without the spreadsheet when you care. A text file is harder to break and easier to open on a strange computer.

Should I log automatic backups? Log the moments you confirmed they worked, and log the days you noticed they did not. An automatic system with no human line for a year is an unattended claim. A monthly line that says you opened a file from it is enough.