Backup verification checklist: prove the copy before signoff
A practical checklist for checking scope, copy results, missing files, checksums, and the evidence you keep before retiring the source.
Safe Archive guide
Keep the copy, keep the context, and keep a record of what arrived.
Founder of ARCED Foundation, ARCED International, and Solutions of Things Lab (SoTLab). Built FolderManifest to help teams protect file integrity and stay audit-ready.
Published August 20, 2026
Scope first
Decide what you are allowed to copy before starting the archive.
Copy second
Use a destination that will remain available after access changes.
Verify last
Keep a report that names the files copied, converted, skipped, or failed.
Quick answer
Verify a backup in three passes: define what should be copied, inspect the result, and keep a report that explains the exceptions. Do not retire the source based only on a success message or a matching folder size.
Before the copy
Write down the expected set before the backup begins. A reviewer cannot identify a missing folder if nobody recorded that it was expected.
- Record the source path, Drive folder, or share name.
- Record the destination and its owner.
- List exclusions, permissions, and file types that need conversion.
- Set the archive date, retention rule, and approval owner.
- Create a baseline manifest when the source needs later comparison.
During the copy
Use a copy workflow that records progress and exceptions. Safe Archive writes a journal while it runs, resumes partial work, and keeps the source untouched. For Google Drive, the report also records native-file exports and items that cannot be archived as ordinary files.
- Confirm the source and destination before starting.
- Watch for permission, path, quota, and connection errors.
- Do not treat skipped files as successful copies.
- Keep the report in the destination with the archived folder.
After the copy
Read the HTML report and inspect the CSV report. Check that the expected folders are present, that failures are empty or explained, and that converted files open in the format you selected.
When the source and destination are both accessible, run a second comparison. The folder integrity checksum guide explains how to identify added, changed, and missing files.
Make the archive reviewable
FolderManifest copies the folder locally or to a supported destination, then creates a report with the files that arrived and the files that need attention.
Keep the evidence with the decision
A verification packet should contain the scope list, the archive report, exception notes, and the approval to retire or transfer the source. Store it where the next owner can find it. If the archive is part of Google Drive offboarding, pair this checklist with the Google Drive offboarding checklist.
Print this page or copy the checklist into the team's runbook. The value is in repeating the same checks before each high-stakes backup, not in keeping a checklist that no one uses.
Frequently asked questions
What does a backup verification checklist prove?
It records the expected scope, the copy result, missing or failed items, content checks, and the person who approved the result. It turns a backup task into a reviewable record.
Should a backup checklist include checksums?
Yes when content integrity matters. A checksum gives you a way to detect changed bytes later, while names, sizes, and timestamps only describe metadata.
Should I delete the original after the checklist passes?
Not immediately. Follow the retention and approval process for the project. A passing report supports the decision, but it does not replace the decision itself.
Can FolderManifest create the verification evidence?
Yes. FolderManifest can scan a folder, create a manifest, archive a folder, and write HTML or CSV reports that name file status and SHA-256 values.