fleet: uprootiny · INT-131944351 sources live ⟳
0 / 4
boxes protected
4
unprotected
0
stale · >7d old
—
soonest expiry
NONE
offsite copies
snapshots are same-DC, 30-day
not yet a 3-2-1 backup
not yet a 3-2-1 backup
| BOX | ROLE / IP | RESTORE PTS | FRESHEST | EXPIRES | KIND |
|---|---|---|---|---|---|
| 173.212.203.211 | box 173.212.203.211 173.212.203.211 | 0 restore pts | — | — auto-delete | IMAGE · SAME-DC no restore point |
⚙ control this box | |||||
| 45.90.121.59 | box 45.90.121.59 45.90.121.59 | 0 restore pts | — | — auto-delete | IMAGE · SAME-DC no restore point |
⚙ control this box | |||||
| 149.102.137.139 | box 149.102.137.139 149.102.137.139 | 0 restore pts | — | — auto-delete | IMAGE · SAME-DC no restore point |
⚙ control this box | |||||
| 5.189.145.105 | box 5.189.145.105 5.189.145.105 | 0 restore pts | — | — auto-delete | IMAGE · SAME-DC no restore point |
⚙ control this box | |||||
WHAT THESE BACKUPS COVER TIER 0
Contabo image snapshots — whole-disk restore points taken through the API. They protect against a broken box, a bad deploy, an accidental delete. Pick Snapshot on any row above (type the box name to confirm) to re-protect it.
They do NOT cover a Contabo-account or datacentre loss — they live on the same provider, in the same DC — and they are not file-level: you can't browse or de-duplicate inside one without restoring it. Each auto-deletes after ~30 days.
Real offsite, file-level, de-duplicated backup (restic → object storage in a second failure domain, with a tested restore) is the next step and needs SSH onto the boxes — FLEET-PLAN.md stage 1. This page never dresses a same-DC blob up as a 3-2-1 backup.