LEARN. PRACTICE. GROW.Concept and mechanism
Backup and restore, pilot light, warm standby, and active-active describe different ways to prepare recovery. In the pilot-light example, data and core components exist at the destination, but parts of the application still need creation or activation before serving. Warm standby already functions at reduced capacity and may need scale-up. One successful test request does not prove peak capacity. Active-active serves from multiple locations, requiring consistency and conflict design when concurrent writes occur. Vendor indicative ranges are not guarantees for your workload. Validate data, capacity, dependencies, and actual time needed to recover the agreed function.
Guided application
Geographic protection does not replace recoverable history. An incorrect deletion can quickly reach a replica. In a fictional case, both regions are synchronized with precisely the wrong state; moving traffic does not recover earlier records. Preserve valid points and validate PITR or versioning, including reconciliation of legitimate subsequent changes. Deletion protection also has a defined scope. In AWS Backup Vault Lock, governance permits removal with appropriate permissions; compliance after grace time has different immutability restrictions. Neither state independently demonstrates functional recoverability or accessible keys. Define retention from approved requirements without turning vendor examples into universal legal obligations. Keep the recovery strategy and data-protection strategy aligned with the failure being addressed.
A synchronized replica can contain the same accidental deletion as its source.
Common pitfalls
Warm standby as full capacity; active-active as conflict-free; replica as history; lock as guaranteed restore.
Related topics: Objectives and dependencies · Backups and recoverable points · Recovery-site readiness and configuration
Choose required readiness and also protect against logical data loss.
Reference: Recovery strategies and data disasters · DR recovery 2026-09; PostgreSQL 18, etcd 3.6 and selected AWS/Azure behavior