Backup & Recovery Tools
Systems and practices for protecting data against loss and restoring it after failure.
Partly. Signed control-plane backups verify offline and restore after total control-plane loss (tested). Volumes are snapshotted and restored from peers after host loss (tested). A full export → import round trip is not yet tested automatically.
Backup vs. failover -- a distinction worth being precise about
These solve different failure modes and are easy to conflate. Failover keeps a service running when a machine dies, by moving the workload elsewhere -- it says nothing about data that only existed on the dead machine's disk. Backup protects against data loss specifically -- corruption, accidental deletion, ransomware -- by keeping point-in-time copies you can restore from, independent of whether the original service is still running. A system can have excellent failover and zero real backup, or vice versa; a mature setup needs both, and the classic 3-2-1 rule (3 copies, 2 different media, 1 offsite) is really about backup, not uptime.
Systems and practices for protecting data against loss and restoring it after failure. Partly. Signed control-plane backups verify offline and restore after total control-plane loss (tested). Volumes are snapshotted and restored from peers after host loss (tested). A full export → import round trip is not yet tested automatically.