Recover: GWSCLI / S3
No signal importantOffsite object storage. Last line of defence for backups; the only copy that survives loss of the home rack.
- Owner
- homelab-operator
- Target RTO
- 4h
- Last heartbeat
- never
- Dependent entities
- 1
Recovery readiness70/100
Procedure
Read fully before acting.- Credentials live in /etc/jarvisos/config.env — never copy them into a ticket, log or status page.
- Verify object listing before trusting the 'last backup' timestamp; a successful upload job is not a verified restore.
- Restore drills should target a scratch path, never the live NAS dataset.
Bring-up order
Dependencies first — starting out of order is a common second incident.- GWSCLI / S3 Node target
What this affects
Impacted if this stays down, or while you restart it.
Downstream
Offsite backup replica
Readiness breakdown
- Documented runbook 20 pts
- Vendor-managed (no local backup expected) 50 pts
- No failover target configured 30 pts