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

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. Still broken? Server Export Photos Safely

BAK-002: No off-site backup confirmed

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. Still broken? Handover First 24 Hours

BAK-003: Snapshot restore overwrote new work

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. Still broken? Server Export Photos Safely

BAK-004: How to create snapshot before upgrade

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. Still broken? Home Truenas Basics

BAK-005: Snapshot task not running

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. Still broken? Server Export Photos Safely

BAK-006: Too many snapshots — pool full

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. Still broken? Server Check Disk Space

BAK-007: Restore single photo from snapshot

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. Still broken? Using Photos Basics

BAK-008: Restore Jellyfin metadata not needed

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. Still broken? Using Jellyfin For Beginners

BAK-009: App config lost — *arr empty

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. Still broken? Server Restart Docker App

BAK-010: Vaultwarden vault backup

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. Still broken? Access Open Vaultwarden

BAK-011: Authentik users lost after DB wipe

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. Still broken? External Authentik Add User

BAK-012: Cloudflare config not on NAS

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. Still broken? External Cloudflare Account Access

BAK-013: NPM certificates after rebuild

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. Still broken? Basics All Important Urls

BAK-014: Export photos to external drive

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. Still broken? Server Export Photos Safely

BAK-015: Windows PC backup not NAS

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. Still broken? Home Windows Pc Basics

BAK-016: Ransomware fear on SMB share

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:. Still broken? Handover First 24 Hours

BAK-017: Snapshot visible to SMB users

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. Still broken? Server Export Photos Safely

BAK-018: Clone dataset for testing restore

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. Still broken? Server Export Photos Safely

BAK-019: Backup during degraded pool

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. Still broken? Server When Pool Degraded

BAK-020: GitHub has SaxDocs — not media

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. Still broken? External Github If Saxon Dies

BAK-021: Restore after pool total loss

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. Still broken? Handover First 24 Hours

BAK-022: TrueNAS config backup

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. Still broken? Home Truenas Basics

BAK-023: Docker app volumes which to snapshot

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. Still broken?* Server Restart Docker App

BAK-024: Version mismatch after restore old snapshot

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. Still broken? Server Restart Docker App

BAK-025: Encrypted dataset forgot passphrase

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. Still broken? Access Open Vaultwarden

BAK-026: Backup qBittorrent torrent list

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. Still broken? Using Qbittorrent Dont Touch

BAK-027: Family photos only copy on NAS

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. Still broken? Handover Who Gets What

BAK-028: Restore from Synology era backup

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. Still broken? Basics What Is Truenas

BAK-029: Test restore never done — is snapshot OK?

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. Still broken? Server Export Photos Safely

BAK-030: Replication to cloud slow/failing

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. Still broken? Server Export Photos Safely

BAK-031: Immutable snapshots needed?

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. Still broken? Server Export Photos Safely

BAK-032: Deleted dataset by mistake

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. Still broken? Handover First 24 Hours

BAK-033: Backup windows maintenance overlap

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. Still broken? Server Run Pool Scrub

BAK-034: Export media list for insurance

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. Still broken? Handover Notify Insurance And Utilities

BAK-035: Will mentions Ryan gets tech — backup duty?

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. Still broken? Handover Who Gets What

BAK-036: Restore Authentik without breaking SSO

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. Still broken? External Authentik Add User

BAK-037: Partial file restore corrupted

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. Still broken? Using Jellyfin For Beginners

BAK-038: Backup encryption password lost

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. Still broken? Access Open Vaultwarden

BAK-039: 3-2-1 rule for this homelab

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. Still broken? Handover First 24 Hours

BAK-040: Everything lost — emotional reset

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. Still broken? Handover First 24 Hours