sam-4screen-desktop 2026-9-1:12:39:8

200 projects/220 Web Host Migration/Backup Action Plan — Close the Gaps + Restore.md

@@ -58,13 +58,12 @@ The original offsite S3 plan covered **photos + archive + .27 desktop** — but
   - `~/deployment` + voice/audio dirs → `home/...` (DEEP_ARCHIVE) — ~31G ≈ <$0.05/mo
 - [ ] First seed after Step 1 completes so .13's own config is offsite too
 
-### Step 3 — .35 restore path → S3 (DECISION NEEDED on scope)
-Given restic repo is 1.1T on .23, options:
-- **Option A (recommended, restore-focused):** Do NOT ship the whole 1.1T repo. Instead:
-  - Ship **Borg .13 archive copies on .23** (462G of borg-repos) → S3 DEEP_ARCHIVE (these are already dedup'd single-copy restorable archives) — the highest-value offsite target.
-  - For .35's restic/kopia, ship ONLY `mnt/hd` (Immich original photos — already in S3 via photos) — restic/kopia repos remain local (on .23) since .23 will be separately protected.
-- **Option B (complete):** Also ship restic/kopia repos → S3 (~1.1T+) — expensive (first 90 days Standard ≈ $40-80/mo then Deep Archive ≈ $1.6/mo). Only if you want full .35 restore from cloud.
-- **Decision:** pick A or B (recommend A).
+### Step 3 — Immich/photo offsite (REVISED 2026-09-01 after verification)
+**Key finding:** Immich originals live at `/mnt/hd/immich/upload` (407G, .35 My Passport) — separate store from .13 `by_date` (376G, already in S3). Kopia does NOT contain photos (only DB+configs). Restic contains /mnt/hd (407G).
+
+- [ ] Add `/mnt/hd/immich/upload` → S3 `photos/immich/` (DEEP_ARCHIVE) — 407G ≈ **$0.60/mo steady** (transient ~$15/mo first 90d in Standard)
+- [ ] Do NOT ship the 1.1T restic / 71G kopia repos (dedup DBs not directly restorable; target data directly instead)
+- [ ] Result: Immich originals + by_date master both offsite; .23 SPS closure for the highest-value data
 
 ### Step 4 — Protect .23 (the single point of failure)
 - [ ] Since .23 is the hub for ALL repo copies: either