# IT Pro Partner — Per-Server Disaster Recovery Plan (REDACTED)

**Author:** Sho'Nuff / Network Services Team
**Date:** July 9, 2026
**Version:** 1.0 — Redacted for 3rd Party Review

---

## Architecture Overview

11 servers total. 1 primary (dedicated EPYC), 10 Hetzner cloud VPSes.
1 warm standby. Shared dependencies: S3-compatible storage, Cloudflare DNS, SSH key auth.

## DR Classification

| Tier | Count | RTO | RPO |
|------|-------|-----|-----|
| Critical | 2 | 5 min - 2 hours | 15 min - 24 hours |
| Important | 4 | 4 hours | 24 hours |
| Standard | 4 | 8 hours | 24 hours |
| Standby | 1 | 2 min | 15 min |

## Key Findings

1. AI/LLM server disk at 92% — cleanup needed before migration
2. Docker volume backups not automated to S3
3. Database dumps not scheduled for most servers
4. Hermes warm standby functional via S3 sync + WireGuard tunnel

## Full version
Full DR plans with IPs, credentials, and detailed restore procedures are stored internally at /root/.hermes/references/server-dr-plans.md and available on request.
