Most home labs run on memory. Then a drive fails, the router resets, and nobody remembers which port forwards to what. A one-hour documentation pass fixes that. Here is the structure I use.
1. Network overview
Record ISP speed, router model and IP, subnet, DHCP range, DNS servers, VPN method, and your DDNS name. Ten lines, once.
2. IP address plan
Give every always-on device a static address or a DHCP reservation. List IP, hostname, type and notes. Keep infrastructure in a low range (.2-.50) and servers in the next block so the plan stays readable.
3. Services and ports
For every service write host, port, URL and whether it is exposed to the internet. Review the exposed column every few months. Anything exposed that you do not use should be closed.
4. Backups, with a restore test
Log what is backed up, where it goes and when you last restored from it. A backup you never restored is a guess. Aim for 3 copies, 2 media types, 1 off-site.
5. Where secrets live (not the secrets)
Write which password manager entry holds each credential, the 2FA method and where recovery codes are stored. Never put the passwords on the page.
6. Maintenance schedule
Monthly: OS updates, SMART check, backup job check. Twice a year: restore test, dust, UPS battery, certificate and domain renewals.
7. Incident log
When something breaks, write what broke, the cause and the fix. Next time it is a five minute job.
I turned this into a printable binder (network overview, IP plan, inventory, services and ports, backup log, secrets map, maintenance schedule, incident log): https://payhip.com/b/kHNd9
If you run a 3D printer, there is a matching printer log with filament inventory, per-material settings and cost per print: https://payhip.com/b/jRS84
I post more guides and early access to new tools and printables on Patreon: https://www.patreon.com/123black
Top comments (0)