The FIRM Guide

The Backup and Synchronize Module

How your data stays consistent and survivable across devices and locations — what is synced or backed up, with which tools, on what schedule, and how recovery works.

Where this Module fits

S-06 Module 6 of 6 in the System area — step 1 of 4 on the dependency ladder (System → At-Home → Financial → Estate).

Sixth — makes the whole structure survivable; the module that turns good organization into genuine recoverability.

Adds to The Secure Guide: One entry per backup or sync arrangement — scope, encryption, offline copy, recovery steps, last tested.

Adds to The Family Guide: A copy at home and a copy offsite; start with the README.

Every Module adds one section to each guide — that is how the two guides assemble as you work. See what you're building.

Download Text File Nothing is entered on this page — you fill the template in privately.

Text file — the flexible one. Use it as-is, paste it into a spreadsheet, open it in any editor, or paste it into an AI tool to reshape the blank form to fit your family: rename a field, add a row, drop one you don't need.

Print / PDF — the ready-to-use one. Print it and fill it in by hand, or choose Save as PDF and complete it in your own offline PDF app. Either way it stays with you — the finished Secure Guide template goes inside your Vault.

One rule: only ever give an AI tool the blank template. Never paste your real information — passwords, account numbers, anything you'd keep secret — into an AI tool, an online service, or anywhere outside your own Vault. Customizing an empty form is fine; filling it in happens privately, offline. That's the same rule this site follows: nothing sensitive ever leaves your hands.

Secure Guide Starter Template — Backup and Synchronize

Store this inside your Vault. Create one entry per sync or backup arrangement. Update at the quarterly verification.

The rule here is 3-2-1: three copies of anything critical, on two kinds of media, one offsite — and encrypt before you sync. Priority goes to the FIRM tier first: the Vault, and The FIRM Directory which contains The Secure Guide and The Family Guide; everything else is secondary. Two things families learn the hard way: synchronization is not backup (a sync deletes everywhere; a backup is an independent copy), and a backup you have never tested is a backup you cannot trust — the Last Tested field is the point of this whole record.

The tool or service, one entry per arrangement — e.g., zero-knowledge cloud service, OS backup tool, peer-to-peer sync.
What is included in this arrangement (the encrypted Vault container, the documents folder, the Family Guide PDF).
Which devices take part (cross-reference the Devices Module).
Yes/No — and whether contents are encrypted before they leave the device. Account credentials: password manager.
The tool protecting the copies (see the Encryption Module). Keys: password manager.
Realtime / weekly / quarterly manual.
The disconnected copy and where it lives.
What happens on mismatch (newest wins, manual merge) — decided now, not during a crisis.
The documented restore procedure, or a pointer to it.
Date of the last successful test restore.
Backup and Synchronize; secure-guide; family-guide; System

Family Guide Starter Template — Backup and Synchronize

This template contains no sensitive information. It can be stored with household documents.

In the matching Secure Guide section: one entry per backup or sync arrangement — scope, encryption, offline copy, recovery steps, last tested.

That detail is what makes recovery possible — and it is protected in the Vault, which opens with The Vault Key. The key is never written here, by design. The people listed on this page know how it is kept, and the steward's job is to keep that path current, so this page never leads to a locked door.

One sentence of reassurance (e.g., "Everything important is backed up: a copy at home in the safe and a copy offsite").
In general terms, how the family's copies work: the important files keep themselves backed up on a schedule; one copy lives at home, one lives away from the house; nobody has to do anything daily for this to stay true.
The services and tools by name with orientation pointers — the shared cloud folder has a Family Guide PDF and README; the home backup drive is in the safe.
Steward and cadence; a test restore has been done.
First steps in a recovery — start with the README in the shared cloud folder.

Anything this page's reader should know that the sections above didn't ask for — the exceptions, the house quirks, the thing you would say out loud while handing this page over.

Worked example — Frank's family

Months into the system, Frank noticed the gap: the Secure Guide existed only on his laptop, the Family Guide was one printed binder, and the external drive in the desk drawer hadn't been connected in a year. One weekend later, everything foundational satisfies 3-2-1 — three copies, two kinds of media, one offsite — and every copy has been proven to open. Three of his entries:

All details are fictional and illustrative. The assembled example guides live at the example Secure Guide and the example Family Guide.

Secure Guide — Frank's entry

One entry per sync or backup arrangement, verified quarterly. Account credentials and encryption keys are referenced to the password manager — never written here.

Entry 1 — The Vault's offsite copy

SafeHarbor Sync — zero-knowledge, so files are encrypted before they leave the device and the service cannot read them (this arrangement: the Vault's offsite copy)
The FrankSecure encrypted container — the digital half of The Secure Guide
Frank-Laptop (the only editor); restorable to any device with the container tool installed
Yes — double-wrapped: the container's own encryption inside SafeHarbor. Account login in the password manager, highest authentication tier.
The container tool (see the Encryption entry); key in the password manager
Automatic, continuous
Entry 2 — the external drive in the fire safe
The container is edited on one device only. If a conflicted copy ever appears, the laptop version wins and the cause gets investigated before anything is deleted.
FrankSecure/System/restore-procedure.md — clean device, install the tools, sign in to the cloud account, download, open with the container passphrase
2026-01 — container opened from the cloud copy on Sarah's MacBook
Backup and Synchronize; secure-guide; family-guide; System

Entry 2 — The offline copy

Windows File History (built into the OS) — this arrangement: the offline copy to FireSafe-SSD, encrypted, in the fire safe
Frank-Laptop's full documents folder, including the container; a yearly archive folder that is never overwritten
Frank-Laptop; the drive lives in the fire safe and is connected only during backups — the disconnected copy nothing automated can reach
No — this is the offline half of 3-2-1
BitLocker To Go, full-drive; recovery key in the password manager
Weekly when connected; quarterly manual verify
Fire safe, home office
n/a — one-way backup; archives accumulate, never replace
Connect to any machine, unlock with the recovery key, restore with the OS tool; prior years live in the archive folders
2026-04 quarterly — drive unlocked, one file spot-restored
Backup and Synchronize; secure-guide; family-guide; System

Entry 3 — The orientation copy

A SafeHarbor shared folder — deliberately link-readable (this arrangement: the orientation copy)
The Family Guide as PDF, plus README-FIRST.txt explaining the system and the restore order
Readable from anywhere; shared with Sarah and the executor
Yes — and unencrypted by design: it must open on the worst day, and it contains orientation only, no credentials
None — by design (everything sensitive is in Entries 1 and 2)
Re-exported whenever the binder version changes
The printed binder itself, home office
The binder is authoritative; the PDF is re-exported from it
This is where recovery starts: read the README first — it walks through restoring everything in order
2026-01 — Sarah opened the folder from her own account
Backup and Synchronize; secure-guide; family-guide; System

A fourth entry covers the password manager's annual encrypted export — sealed with the recovery materials in the fire safe (see the Passwords and Passkeys entries).

Family Guide — Frank's entry

This entry sits in the household reference binder. It contains no account names and no keys.

Everything important is backed up — a copy at home in the fire safe and a copy offsite. Three copies, two kinds of media, one away from the house.
It runs itself: the computers back up on a schedule, the important container copies itself to the cloud in encrypted form, and once a year Dad proves a copy opens. Nobody does anything daily to keep this true.
The shared cloud folder (SafeHarbor) holds the Family Guide PDF and a README; the home backup drive is in the fire safe. No passwords in either place.
Frank — the backups run automatically; he verifies quarterly and does a real test-restore every January.
Start with the README in the shared cloud folder — it walks through restoring everything in order. Sarah and the executor already have access to that folder.
The yearly archive folder is allowed to look old — that is the point. Don't tidy it, don't delete 'duplicates' from it.