Backups & recovery
Snapshots, restore steps, off-site copies, and what to do when files or apps are lost.
40 entries — IDs BAK-001 through BAK-040.
BAK-001: Accidentally deleted important file
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Delete without backup or snapshot. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: File gone from A: or Jellyfin library. Likely cause: Delete without backup or snapshot. Fix: 1. Check Windows Recycle Bin on A:. 2. TrueNAS → Snapshots → browse snapshot before delete time. 3. Restore file from snapshot if exists. 4. If no snapshot, check off-site backup if configured.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-002: No off-site backup confirmed
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Snapshots on same pool only — documented TODO. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Worried fire/theft kills everything. Likely cause: Snapshots on same pool only — documented TODO. Fix: 1. Treat pool as single location risk. 2. Plan USB or cloud copy for photos/finance critical data. 3. Read SaxDocs backups page for current strategy. 4. Ryan: prioritize documenting off-site in handover.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Export photos
BAK-003: Snapshot restore overwrote new work
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Rollback is destructive to newer data. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Rollback removed recent good changes. Likely cause: Rollback is destructive to newer data. Fix: 1. Restore individual files from snapshot browser instead of full rollback. 2. Copy needed files out, don't rollback whole dataset. 3. Lesson: snapshot before risky ops only.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-004: How to create snapshot before upgrade
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Manual snapshot not taken. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Want safety net before TrueNAS update. Likely cause: Manual snapshot not taken. Fix: 1. Storage → dataset → Take Snapshot. 2. Name with date and reason. 3. Proceed with upgrade. 4. Delete snapshot after week if stable.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Truenas Basics Deep dive: Export photos
BAK-005: Snapshot task not running
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Task disabled or pool full. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Scheduled snapshots missing. Likely cause: Task disabled or pool full. Fix: 1. Data Protection → Snapshot Tasks — enable. 2. Check pool space. 3. Run manual snapshot to test.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-006: Too many snapshots — pool full
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Retention too aggressive. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Snapshots consume terabytes. Likely cause: Retention too aggressive. Fix: 1. Review snapshot task retention (daily×7 etc.). 2. Delete oldest snapshots. 3. Balance safety vs space.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Check Disk Space Deep dive: Export photos
BAK-007: Restore single photo from snapshot
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Need granular restore. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: One photo deleted from library. Likely cause: Need granular restore. Fix: 1. Snapshots → browse photos dataset snapshot. 2. Navigate to file path. 3. Restore or copy file to active dataset.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Using Photos Basics Deep dive: Export photos
BAK-008: Restore Jellyfin metadata not needed
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Jellyfin recreates metadata on scan. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Only media files matter — metadata rebuilds. Likely cause: Jellyfin recreates metadata on scan. Fix: 1. Restore media files from snapshot. 2. Rescan Jellyfin library. 3. Don't panic over lost Jellyfin DB if media intact.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Using Jellyfin For Beginners Deep dive: Export photos
BAK-009: App config lost — *arr empty
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: App volume deleted or not backed up. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Sonarr shows no series after mishap. Likely cause: App volume deleted or not backed up. Fix: 1. Restore app dataset from snapshot if exists. 2. Re-point to media folders on A:. 3. Re-import from disk if no snapshot.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Restart Docker App Deep dive: Export photos
BAK-010: Vaultwarden vault backup
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Vaultwarden on NAS — need export routine. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Passwords must survive NAS death. Likely cause: Vaultwarden on NAS — need export routine. Fix: 1. Regularly export encrypted vault from Bitwarden client. 2. Store export off NAS (secure location). 3. Ryan must have independent vault access per handover.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Access Open Vaultwarden Deep dive: Export photos
BAK-011: Authentik users lost after DB wipe
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Postgres volume restored wrong or empty. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: SSO broken; users gone. Likely cause: Postgres volume restored wrong or empty. Fix: 1. Restore Authentik DB from snapshot. 2. Reconfigure providers from docs. 3. Users may need re-enrollment worst case.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? External Authentik Add User Deep dive: Export photos
BAK-012: Cloudflare config not on NAS
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Cloudflare is separate — good. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: DNS/tunnel survives NAS loss. Likely cause: Cloudflare is separate — good. Fix: 1. Document tunnel token backup in Vaultwarden. 2. NAS loss doesn't delete Cloudflare. 3. Rebuild NAS apps pointing to new LAN IP if needed.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? External Cloudflare Account Access Deep dive: Export photos
BAK-013: NPM certificates after rebuild
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Certs stored in NPM volume. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: SSL certs lost on NPM container. Likely cause: Certs stored in NPM volume. Fix: 1. Restore NPM volume from snapshot. 2. Or re-request Let's Encrypt in NPM. 3. Update DNS if IP changed.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics All Important Urls Deep dive: Export photos
BAK-014: Export photos to external drive
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Manual backup procedure. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Want USB copy of photos. Likely cause: Manual backup procedure. Fix: 1. Connect USB to NAS. 2. Use rsync or TrueNAS cloud sync to USB. 3. Verify random sample opens on PC. 4. Store USB off-site if disaster copy.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-015: Windows PC backup not NAS
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: PC has separate backup needs. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: PC files not on TrueNAS. Likely cause: PC has separate backup needs. Fix: 1. This FAQ covers NAS only. 2. Check Windows backup or OneDrive separately. 3. Media on A: is on NAS — back up personal PC docs elsewhere.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Windows Pc Basics Deep dive: Export photos
BAK-016: Ransomware fear on SMB share
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: PC malware encrypting network files. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Encrypted files appearing on A:. Likely cause: PC malware encrypting network files. Fix: 1. Disconnect infected PC from network immediately. 2. Restore from snapshot before infection time. 3. Do not pay ransom without expert advice. 4. Scan PC before remounting A:.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Export photos
BAK-017: Snapshot visible to SMB users
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Hidden snapshot dir exposed. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Users see .zfs snapshot folder. Likely cause: Hidden snapshot dir exposed. Fix: 1. Disable snapshot visibility on share if not needed. 2. Educate users not to delete snapshot folders. 3. Use admin restore instead.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-018: Clone dataset for testing restore
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: ZFS clone from snapshot. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Want test without touching production. Likely cause: ZFS clone from snapshot. Fix: 1. Advanced: create clone from snapshot. 2. Test restore on clone. 3. Destroy clone after test.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-019: Backup during degraded pool
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Pool stressed — extra reads hurt. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Should I backup while resilvering? Likely cause: Pool stressed — extra reads hurt. Fix: 1. Light backup of critical small files OK. 2. Avoid full pool copy during resilver. 3. Fix pool health first for big backup.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server When Pool Degraded Deep dive: Export photos
BAK-020: GitHub has SaxDocs — not media
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Code/docs yes; terabytes media no. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Docs site backed up on GitHub. Likely cause: Code/docs yes; terabytes media no. Fix: 1. Use GitHub for SaxDocs and configs in git. 2. Media needs NAS snapshots or separate backup. 3. Don't expect GitHub for Jellyfin library.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? External Github If Saxon Dies Deep dive: Export photos
BAK-021: Restore after pool total loss
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Multiple drive failure or catastrophic error. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Pool FAULTED unrecoverable. Likely cause: Multiple drive failure or catastrophic error. Fix: 1. Professional data recovery expensive. 2. Rebuild pool from scratch. 3. Restore from off-site if exists. 4. Ryan: read handover and will for priorities.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Export photos
BAK-022: TrueNAS config backup
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: TrueNAS can download system config. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: System settings export. Likely cause: TrueNAS can download system config. Fix: 1. System → General → Save Config. 2. Store in Vaultwarden attachment or secure USB. 3. Does not replace pool data backup.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Home Truenas Basics Deep dive: Export photos
BAK-023: Docker app volumes which to snapshot
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: App configs and databases critical. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Many ix-volumes — which matter? Likely cause: App configs and databases critical. Fix: 1. Snapshot datasets holding *arr DB, Authentik, Vaultwarden, NPM. 2. Media datasets snapshot optional (large). 3. Document paths in Server services doc.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Restart Docker App Deep dive: Export photos
BAK-024: Version mismatch after restore old snapshot
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: App updated since snapshot. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: App fails after restoring old snapshot. Likely cause: App updated since snapshot. Fix: 1. Restore snapshot matching app version. 2. Or restore snapshot then downgrade app chart. 3. Prefer file-level restore over whole volume.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Restart Docker App Deep dive: Export photos
BAK-025: Encrypted dataset forgot passphrase
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Encryption passphrase lost. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Locked dataset cannot mount. Likely cause: Encryption passphrase lost. Fix: 1. Without passphrase, data unrecoverable. 2. Check Vaultwarden for passphrase. 3. Do not enable encryption without storing key.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Access Open Vaultwarden Deep dive: Export photos
BAK-026: Backup qBittorrent torrent list
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: state not exported. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Reinstall loses torrent state. Likely cause: state not exported. Fix: 1. Backup qBittorrent config folder from app volume. 2. Or use built-in export in qBittorrent. 3. See qBittorrent guide — minimal changes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Using Qbittorrent Dont Touch Deep dive: Export photos
BAK-027: Family photos only copy on NAS
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: No second copy documented. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Risk if single pool. Likely cause: No second copy documented. Fix: 1. Priority: copy photos to external + cloud if possible. 2. Enable snapshot tasks on photos dataset. 3. Ryan should verify off-site plan early.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Who Gets What Deep dive: Export photos
BAK-028: Restore from Synology era backup
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Legacy backup format. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Old USB backup from DSM days. Likely cause: Legacy backup format. Fix: 1. Connect USB; copy files to current pool. 2. Do not import old Synology RAID onto TrueNAS disks. 3. Treat as file copy only.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Basics What Is Truenas Deep dive: Export photos
BAK-029: Test restore never done — is snapshot OK?
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Snapshots untested give false confidence. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Untested backup may fail. Likely cause: Snapshots untested give false confidence. Fix: 1. Quarterly: restore one random file from snapshot. 2. Verify opens correctly. 3. Log test date in personal notes.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-030: Replication to cloud slow/failing
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Bandwidth or API limits. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Cloud sync task errors. Likely cause: Bandwidth or API limits. Fix: 1. Run overnight. 2. Exclude large media if only configs needed. 3. Check credentials in Vaultwarden.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-031: Immutable snapshots needed?
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Advanced feature — may not be configured. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Ransomware protection question. Likely cause: Advanced feature — may not be configured. Fix: 1. Regular snapshots help if admin restores quickly. 2. Immutable requires extra setup. 3. Air-gapped USB still best for ransomware.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Export Photos Safely Deep dive: Export photos
BAK-032: Deleted dataset by mistake
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: No snapshot on that dataset. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Whole dataset gone. Likely cause: No snapshot on that dataset. Fix: 1. Stop writes to pool. 2. Restore dataset from snapshot if any. 3. Without snapshot, data recovery very hard. 4. Call expert before overwriting pool.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Export photos
BAK-033: Backup windows maintenance overlap
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Both IO heavy. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Backup runs during scrub. Likely cause: Both IO heavy. Fix: 1. Stagger schedules — scrub monthly, backup weekly different day. 2. Reduce load during resilver.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Server Run Pool Scrub Deep dive: Export photos
BAK-034: Export media list for insurance
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: No inventory. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Document library value. Likely cause: No inventory. Fix: 1. Export Jellyfin library or file list. 2. Store spreadsheet off NAS. 3. Useful for insurance claims.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Notify Insurance And Utilities Deep dive: Export photos
BAK-035: Will mentions Ryan gets tech — backup duty?
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Ryan inherits operation per will. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Legal handover of systems. Likely cause: Ryan inherits operation per will. Fix: 1. Ryan gets Vaultwarden and docs access. 2. Verify backup strategy in first month. 3. See handover who gets what guide.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover Who Gets What Deep dive: Export photos
BAK-036: Restore Authentik without breaking SSO
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Provider URLs or secrets changed. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: DB restore broke logins. Likely cause: Provider URLs or secrets changed. Fix: 1. Restore matching NPM and Authentik snapshots same time. 2. Clear browser cookies. 3. Test one app login before announcing fixed.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? External Authentik Add User Deep dive: Export photos
BAK-037: Partial file restore corrupted
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Incomplete copy or wrong snapshot. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Restored video won't play. Likely cause: Incomplete copy or wrong snapshot. Fix: 1. Try earlier snapshot. 2. Verify file size matches expected. 3. Re-copy from snapshot browser.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Using Jellyfin For Beginners Deep dive: Export photos
BAK-038: Backup encryption password lost
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Password only in head. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Encrypted backup file unreadable. Likely cause: Password only in head. Fix: 1. Check Vaultwarden secure notes. 2. Without password, backup useless — lesson learned. 3. Store encryption password with vault export.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Access Open Vaultwarden Deep dive: Export photos
BAK-039: 3-2-1 rule for this homelab
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: 3 copies, 2 media, 1 off-site — partially met. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Best practice confusion. Likely cause: 3 copies, 2 media, 1 off-site — partially met. Fix: 1. Snapshots = copy 2 on same disk pool. 2. Need off-site for true 3-2-1. 3. Prioritize photos, vault, configs for off-site.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Export photos
BAK-040: Everything lost — emotional reset
Stack context: Snapshots · off-site (document in Server) Integrated runbooks: NAS FAQ · backups
Why this happens: Multiple failures or no backups. Diagnose (2 min): 1. Confirm whether the problem is LAN-only, public URL, or both — see Outage runbook. 2. Check Service matrix for which app/host owns the broken URL. 3. If a single device only, retry from a second device on the same network.
Symptoms: Catastrophic data loss. Likely cause: Multiple failures or no backups. Fix: 1. Breathe — hardware replaceable. 2. Contact recovery pros if drives intact. 3. Rebuild services from SaxDocs guides. 4. Family memories: check phones, old USBs, cloud.
Verify: Repeat the original symptom check — it should be gone or clearly improved.
Still broken? Handover First 24 Hours Deep dive: Export photos