-
Notifications
You must be signed in to change notification settings - Fork 2
Backup Playbooks
Alex Stoyanov edited this page Mar 4, 2026
·
2 revisions
Use these scenarios after you understand the strategy choices in Backup Workflow.
Codec baseline for these playbooks:
payload_codec = "auto"qr_payload_codec = "raw"
If your policy requires different codec behavior, set it in config defaults before running a scenario.
Use when you are a single operator and want the simplest setup.
ethernity backup \
--input ./seed-phrase.txt \
--output-dir ./ops/single-secret \
--paper A4 \
--design forgeChecklist:
- Confirm the input file is exactly what you intend to protect.
- Keep QR/recovery docs and passphrase in separate places.
- Run one full recovery drill from this exact artifact set.
Use when one person must not recover alone.
ethernity backup \
--input-dir ./team-secrets \
--output-dir ./ops/team-sharded \
--shard-threshold 2 \
--shard-count 3 \
--signing-key-mode embeddedChecklist:
- Threshold/count values match team policy.
- Each custodian gets only assigned shard docs.
- Minimum quorum recovery drill (2 shards) succeeds.
Use when policy requires separate control for passphrase and signing identity material.
ethernity backup \
--input-dir ./critical-config \
--output-dir ./ops/high-assurance \
--shard-threshold 3 \
--shard-count 5 \
--signing-key-mode sharded \
--signing-key-shard-threshold 3 \
--signing-key-shard-count 5Checklist:
- Passphrase and signing-key shards are stored under different custody paths.
- Custody map and incident quorum process are documented.
- Minimum quorum recovery drill succeeds for both shard types.
Use when payload confidentiality controls need a sealed artifact policy.
ethernity backup \
--input ./sensitive.bin \
--output-dir ./ops/sealed \
--sealed \
--design ledgerChecklist:
- Confirm sealed mode matches your policy before distribution.
- Run a full restore drill with current operator instructions.
- Keep an independent non-Ethernity backup path.