备份 3-2-1 审核器

安装指南

1. ClawHub CLI 从源直接安装技能的最快方式。
   npx clawhub@latest install backup-3-2-1-auditor
2. 手动安装 将技能文件夹复制到以下位置之一
   全局模式
   ~/.openclaw/skills/
   工作区
   /skills/
   优先级：工作区 > 本地 > 内置
3. 提示词安装 将此提示词复制到 OpenClaw 即可自动安装。
   请帮我使用 Clawhub 安装 backup-3-2-1-auditor。如果尚未安装 Clawhub，请先安装（npm i -g clawhub）。
   更倾向于下载？
   获取包含原生技能文件的ZIP压缩包。
   下载技能 (.zip)

什么是

Backup 3-2-1 Auditor 是一款离线命令行工具，使用 Python 标准库构建，用于检查重要数据实际存放的位置，以及它们面对设备故障、盗窃、火灾和勒索软件时有多脆弱。它会逐项评估资产的副本数量、介质多样性、异地保护、版本管理和勒索软件暴露风险——因为同步副本可能会和原始文件一起被加密。
该工具会估算丢失每项资产可能造成的后果，制定最低成本冗余计划，并支持每季度进行还原演练。作为保障个人数据安全的实用 Openclaw Skills 之一，它能帮助你把对备份模糊的信心转化为有据可查的计划和经过测试的恢复流程。

应用场景

审查家庭照片、手机照片库、代码、税务记录和其他重要文件的存储位置。
检查云同步提供的是带版本管理的恢复能力，还是仅仅镜像更改和勒索软件加密结果。
在设备发生险情后、搬家前或报税季清理期间，检查备份准备情况。
为不可替代的文件规划经济实惠的异地和离线副本。
帮助家庭成员建立备份计划，并确保至少有一个副本不依赖在线账户。
安排每季度进行还原测试，以发现账户过期、硬盘已满或备份无法使用等问题。

工作原理

登记每项资产、当前副本位置及其价值类别：irreplaceable、painful 或 recreate-cheap。
运行审计，评估副本数量、介质多样性、异地状态，并给出 PASS、FRAGILE 或 FAIL 总体判定。
运行影响范围检查，识别从主计算机同步或挂载的副本，这些副本可能受到勒索软件影响。
查看每个资产类别的预计恢复成本和所需工作量。
生成最低成本计划，指出缺少的冗余措施，例如带版本管理的云存储或轮换使用的离线硬盘。
通过恢复示例文件并打开文件来进行还原演练，然后记录结果并检查下次演练的到期时间。

配置指南

该技能使用 Python 3 和标准库，可离线运行，并将登记信息作为 JSON 存储在本地。请在技能目录中运行命令，该目录中提供了 scripts/backup_auditor.py。此工具不需要外部 Python 软件包或在线账户。
python3 scripts/backup_auditor.py --help
python3 scripts/backup_auditor.py add --asset "family photos 2009-2026" \ --copies "laptop,icloud photos,external HDD in desk drawer" --value irreplaceable python3 scripts/backup_auditor.py audit
python3 scripts/backup_auditor.py blast
python3 scripts/backup_auditor.py price
python3 scripts/backup_auditor.py plan
python3 scripts/backup_auditor.py drill --asset "family photos" \ --result "restored 3 random files OK" python3 scripts/backup_auditor.py drill --due
登记实际的副本位置，而不是计划中的位置。进行还原演练时，请确认恢复的文件可以正确打开；仅仅成功复制文件并不能证明它们可以恢复。如果怀疑存在正在发生的勒索软件攻击，请先将受影响的系统与网络隔离，再用此工具进行后续审计。

数据架构

该审计器维护本地 JSON 登记信息，不需要云存储或外部服务。文档所述工作流程按资产组织信息，并记录位置、价值和还原演练历史。
记录 记录的信息
资产 资产名称，例如家庭照片或代码仓库
副本 每项资产申报的存储位置
价值类别 irreplaceable、painful 或 recreate-cheap
审计结果 副本数量、介质多样性、异地状态，以及 PASS / FRAGILE / FAIL 判定
影响分析 每个副本的暴露情况，包括副本是否从主计算机同步或挂载
还原演练 测试的资产及使用 drill --result 记录的结果；drill --due 会报告到期演练
审计采用 3-2-1 模型——三个副本、两种介质类型和一个异地副本——并同时考虑版本管理和气隙恢复。SKILL.md 说明使用本地 JSON 登记信息，但未定义其文件名或内部 JSON 字段布局。

高级特性

按资产给出的 3-2-1 判定会分别区分副本数量、存储介质多样性和异地覆盖情况。
勒索软件影响范围分析会标记与主计算机不独立的同步或挂载副本。
恢复成本估算可帮助了解潜在损失，包括不可替代数据的专业实验室恢复费用估算。
最低成本规划会按资产推荐冗余措施，而不是指定单一备份产品或品牌。
按季度记录还原演练，帮助验证备份是否确实可以恢复并打开。
离线运行、基于 Python 标准库的实现和本地 JSON 登记信息，让工作流程轻量且自成一体。
指南涵盖带版本管理的存储、轮换使用的拔线硬盘、设备多样性、手机照片库，以及用于遗产准备且不依赖账户的副本。

name: backup-3-2-1-auditor description: "Use when you realize your photos/code/documents exist in exactly one place (or your 'backup' is a external drive in the same room as the computer) — audits your actual data-loss risk against the 3-2-1 rule (3 copies, 2 media, 1 offsite) asset by asset, scores blast radius (ransomware encrypts synced copies too), prices honest recovery (professional recovery lab $300-3000 vs $0), generates the minimum-cost redundancy plan for YOUR asset list, and produces a restore-test drill because an untested backup is a hope, not a backup." version: 1.0.0
author: Denis Voronin
license: MIT
tags: [backup, data-loss, ransomware, photos, digital-safety, 3-2-1]

Backup 3-2-1 Auditor

An untested backup is a hope, not a backup. Most people discover their backup strategy failed at the exact moment they need it: the external drive died two years ago, the cloud sync encrypted along with the laptop (ransomware follows sync), the "backup" was the same disk. This tool audits what you ACTUALLY have, asset by asset, against the 3-2-1 rule and scores the real risk.

Overview

audit — register assets (family photos, code repos, tax documents, password vault...), declare where each lives (laptop + Time Machine + Google Drive...), get a per-asset 3-2-1 verdict with copy count, media diversity, offsite status.
blast — ransomware blast-radius analysis: which "backups" are reachable/synced from your main machine and die with it.
price — honest loss pricing per asset class: irrecoverable (baby photos), recoverable-at-cost (professional lab $300-3000, ~40% success), re-creatable (OS, apps, streamed media).
plan — minimum-cost redundancy plan from your audit: which assets need what (versioned cloud + unplugged offline copy vs sync is enough), with concrete product classes, not brands.
drill — the quarterly restore test: pick a random file class, actually restore it, log the result. The drill finds the silent failures (encrypted backups, expired accounts, full drives).

Stdlib Python, offline, local JSON registry.

When to Use

New Year / tax season / post-vacation "where do my photos actually live" moments
After a scare (drive clicking, phone in the lake, ransomware in the news at your employer)
Setting up a family member's first real backup
Before a big life event: moving, kid going to college with the family photo library, relative's estate (their accounts die with them)

Don't use for: enterprise backup policy (different tool class), or after active ransomware detection (isolate from network first, then this tool for the post-mortem).

How It Works — Numbered Steps
Register your assets and where each currently lives:

python3 scripts/backup_auditor.py add --asset "family photos 2009-2026" \

--copies "laptop,icloud photos,external HDD in desk drawer" --value irreplaceable

python3 scripts/backup_auditor.py add --asset "code repos" \

--copies "github,workstation" --value recreate-cheap

Audit against 3-2-1:

python3 scripts/backup_auditor.py audit

Per asset: copies count ✓/✗, media diversity ✓/✗, offsite ✓/✗, overall PASS / FRAGILE / FAIL.
Check ransomware blast radius:

python3 scripts/backup_auditor.py blast

Any copy that syncs from, or mounts on, your main machine is NOT an independent copy under ransomware. Verdicts per copy.
Price the downside honestly:

python3 scripts/backup_auditor.py price

Get the minimum-cost fix plan:

python3 scripts/backup_auditor.py plan

Run the restore drill quarterly and log it:

python3 scripts/backup_auditor.py drill --asset "family photos" --result "restored 3 random files OK"
python3 scripts/backup_auditor.py drill --due

The Rules Behind The Verdicts

Rule Means Common failure

3 copies primary + 2 backups "iCloud IS my backup" = 1.5 copies (sync ≠ backup) 2 media different device types laptop + external SSD plugged into the laptop = 1 media for surge/ransomware purposes 1 offsite survives fire/theft/flood external drive in the same desk ≠ offsite; cloud sync counts as offsite ONLY if versioned Versioned can roll back before encryption event plain sync mirrors ransomware's damage in seconds
Air-gapped unreachable from the network rotate two offline drives; one always unplugged

Asset value classes:

irreplaceable — baby photos, family video, life documents originals. Recovery lab $300-3000 at ~40% success if media intact.
painful — tax records, contracts, thesis drafts: rebuildable at days of work or agency-request loops.
recreate-cheap — code on GitHub, music re-ripped, OS/apps.

Common Pitfalls

Sync is not backup. Dropbox/Drive/iCloud sync the encrypted versions too. You need VERSIONING (roll back) or an offline copy. This is the #1 ransomware loss pattern.
The drawer drive. Two copies in one room = one fire/theft away from zero. Offsite can be: versioned cloud, bank safe deposit, relative's house (rotating drive).
No media diversity. Laptop SSD + external SSD on the same desk, same power strip: surge takes both. HDD + cloud, or SSD + tape-class cold storage, count; two identical SSDs on one desk don't.
Never tested restore. Backup software says "success" for years while writing garbage or the account expired. The drill (restore 3 random files, open them) is the only proof.
Forgetting the phone. For most families the phone IS the primary photo library now. Audit it as an asset with its own copy plan, not as a satellite of the laptop.
Backup drive always plugged in. Convenience kills the air gap. Rotate two drives: one attached this month, one in the drawer. Ransomware can't encrypt what isn't mounted.
Estate blindness. Cloud accounts with the only copy die with the owner (or lock behind 2FA). For irreplaceable family data, one copy must exist that doesn't require any account.

Example

$ backup_auditor.py audit
ASSET: family photos 2009-2026 [irreplaceable]
copies: laptop, iCloud Photos 3 copies: FAIL (2) media: FAIL (both live-sync from phone/laptop) offsite: PARTIAL (cloud but unversioned tier)
ransomware blast: BOTH copies reachable from phone/laptop — no rollback
VERDICT: FAIL — one device-loss or ransomware event from zero
recovery if lost: lab $300-3000, ~40% (photos on dead phone)

$ backup_auditor.py plan
MINIMUM-COST PLAN:
family photos: add (a) versioned cloud tier OR rotated 2-drive
offline pair — one unplugged at all times; (b) annual copy to
relative/bank. Result: 3 copies / 2 media / 1 offsite / rollback.
code repos: PASS (GitHub + workstation = fine for recreate-cheap).
NEXT DRILL DUE: 2026-12-10 (quarterly)

Verification Checklist

Every irreplaceable asset registered with real copy locations
Audit run: no FAIL/FRAGILE on irreplaceable assets
Blast radius: at least one copy unreachable from main machine
Versioned or offline rollback path exists per irreplaceable asset
Restore drill done this quarter — files OPENED, not just copied
One asset copy exists that requires no account (estate rule)

Slow Cooker Converter

Hark Pro 替代方案：生活仪表板与行动助手