- name
- NAS
- slug
- nas
- version
- 1.0.0
- description
- Configure, secure, and optimize network attached storage with proper backup strategy, remote access, and media serving.
- metadata
- {"clawdbot":{"emoji":"🗄️","requires":{"bins":[]},"os":["linux","darwin","win32"]}}
Quick Reference
| Topic | File |
|---|---|
| Backup strategy, 3-2-1 rule | backup.md |
| Remote access, VPN, security | security.md |
| Docker, home lab, apps | apps.md |
| Media server, indexing | media.md |
Scope
This skill covers NAS administration for Synology, QNAP, TrueNAS, Unraid, and DIY builds. For enterprise SAN/distributed storage, use specialized infrastructure skills.
Critical Rules
- RAID is not backup — RAID protects against drive failure, not ransomware, fire, or accidental deletion. Always maintain off-site backup.
- 3-2-1 backup rule is minimum — Three copies, two different media types, one off-site. Cloud sync to B2/S3/Glacier counts as off-site.
- SMB for Windows/Mac, NFS for Linux — Wrong protocol = permission chaos. AFP deprecated. Enable only protocols you actually use.
- Expose ZERO ports to internet — No DSM/QTS admin on public IP. Use VPN (WireGuard/Tailscale) or reverse proxy with auth.
- Test your backups quarterly — Untested backup is not a backup. Actually restore files to verify integrity.
- Disable admin account — Create named admin accounts. Default "admin" is first target for brute force.
- UPS mandatory — Power loss during write = corrupted pool. Budget for battery backup that signals clean shutdown.
- Snapshots are not backup — Same disks, same failure domain. Snapshots help with accidental delete, not disaster.
- Calculate TRUE storage capacity — RAID overhead, reserved space, filesystem overhead. 4x8TB drives ≠ 32TB usable.
- ARM NAS = limited Docker — Synology J-series, low-end QNAP run ARM. Many Docker images x86 only. Verify before buying.