Practice the part a policy binder cannot prove: can your team select a recovery point, restore into a safe scratch location using its own backup tool, and compare the resulting files with an expected inventory? SECOND COPY is a focused rehearsal kit for small teams that want to practice decisions and capture useful follow-up without pretending that paperwork is a recovery test.

INSIDE THE DOWNLOAD

A 45-minute facilitator run-sheet with timed segments, scenario injects, stop conditions and debrief prompts; Python standard-library command-line utility for SHA-256 manifests and read-only candidate verification; five passing unit tests; fictional sample backup/restored folders; blank CSV templates for assets, role-based contacts, evidence and corrective actions; RTO/RPO worksheet with a clearly labelled fictional example; safety guidance; source notes; three actual-content previews; and single-buyer license.

HOW THE PRACTICE WORKS

An authorized operator performs a restore using the organization's own backup product into a new, empty, isolated scratch target. The script compares ordinary files against the expected manifest and reports byte/hash matches, missing files, changed files and extra files. It does not restore, repair, delete or edit source files. Manifest creation writes only a new explicitly named JSON file and refuses to overwrite an existing one.

TESTED FICTIONAL EXAMPLE

The included verification demonstration reports one match, one changed file, one missing file and one unlisted extra; exit code 2 signals discrepancies. These are intentionally planted training differences, not a real recovery result. All five unit tests passed.

REQUIREMENTS

Python 3.9+ and a terminal on Windows, macOS or Linux. Standard library only: no API key, network access, third-party packages or subscription required for the CLI and tests. Markdown and CSV worksheets open in common text editors and spreadsheet apps. You need your own authorized backup/restore tool for a real scratch restore; no backup service is included.

IMPORTANT SAFETY LIMITS

A checksum match is not ransomware detection, malware scanning, provenance, compliance evidence by itself, application validation, a security guarantee or proof that a business service has recovered. Symlinks and special files are not checked; metadata, permissions, databases, dependencies and application behavior require separate validation. The buyer remains responsible for authorization, isolation, safe scoping, backup-tool operation and business acceptance. Never use production as a rehearsal target.

FAQ

Does the script restore or fix files? No. It only reads candidate files and reports comparison results.

Does a clean report mean the system is safe? No. It only means the checked ordinary file bytes matched the supplied manifest at that moment.

Can I use this at work? Yes, under the single-buyer internal/commercial license. Client-facing adaptation must not redistribute the source/template pack and remains subject to that license.

DELIVERY AND LICENSE

Digital ZIP only; no online service, physical product, consulting or subscription. Internal commercial use and adaptation allowed; no resale, redistribution, sublicensing or standalone publication of the source bundle. No exclusivity or results guarantee. See the included license.