backup-and-recovery

# Backup and recovery Nobody wants backups; they want restores. The distinction is not pedantic — organizations discover the difference during the only event that matters. Recovery objectives and which processes must survive are set by `operations:business-continuity-and-resilience`. This skill delivers against them. ## Coverage is where it fails first Most backup gaps are things nobody thought to include: a database somebody stood up outside the standard process, configuration that only exists in a running system, data in a SaaS platform assumed to be the vendor's responsibility, or a developer's machine holding the only copy of something. Reconcile backup coverage against the asset register from `it-operations:it-asset-management` on a cadence and treat the difference as a finding. An untested assumption of coverage is the normal state of affairs. Note that SaaS providers protect against **their** failures, not against your deletion or a malicious insider. Read what the contract actually commits to, rather than what the marketing implies. ## The 3-2-1 shape, and why the offline copy matters Three copies, two media or platforms, one off-site — and, since ransomware, **one immutable or offline**. Modern ransomware deliberately targets backups first, using the credentials it found on the way in. A backup system reachable with production credentials will be encrypted alongside production. Immutable storage or genuinely offline copies are what survive this, and it is th...