Disaster Recovery¶
Scenario: Complete Proxmox Host Failure¶
1. Reinstall Proxmox¶
- Install Proxmox VE on new hardware
- Set hostname (e.g.
pve) - Configure network (same IP if possible)
2. Restore Storage Connection (Synology)¶
- Add NFS storage:
- Datacenter → Storage → Add → NFS
Example: - Server: 192.168.0.143 - Export: /volume1/proxmox-backups
- Add additional shares if needed:
- paperless (NFS)
- other data shares
3. Restore Backup Storage¶
- Verify:
synology-backupsis available- Expected content:
- vzdump backups (VMs + CTs)
4. Restore Containers (Order matters)¶
- CT 101 (Docker)
- CT 102 (AdGuard)
- CT 103 (Paperless)
- CT 104 (Unbound)
- CT 105 (Cloudflared)
Restore via: - Datacenter → Storage → Backups → Restore
5. Restore Virtual Machines¶
- VM 100 (Home Assistant)
- VM 200 (Windows, optional)
6. Validate Core Services¶
Network & DNS¶
- AdGuard reachable: http://adguard.home
- DNS resolution working
- Clients receive correct IPs
Docker Services¶
- Portainer
- Code Server
- Tandoor
- Plex
Check:
bash
docker ps
Paperless¶
- Access: http://paperless.home
- Documents available
Home Assistant¶
- Access: http://ha.home
Optional: - Restore HA backup if needed
7. Cloudflare Tunnel¶
Check container:
bash
docker ps | grep cloudflared
Test external URLs: - ha.salassi.de - paperless.salassi.de - pdf.salassi.de
8. Validate Backup System¶
- Proxmox backup job configured
- HA Samba Backup active
- Hyper Backup running
- Cloud Sync active
Recovery Priority¶
- Network / DNS (AdGuard)
- Docker Host (CT 101)
- Cloudflared (external access)
- Home Assistant
- Paperless
- Remaining services
Notes¶
- Media (Plex) stored on Synology → no restore needed
- Critical data:
- Home Assistant
- Paperless documents
- Docker configs
HA-Only Recovery¶
If only Home Assistant fails:
- Create new HA VM
- Connect SMB share
- Restore backup
Goal¶
- Core services: < 1 hour
- Full system: < 2–3 hours