Disaster recovery
Disaster recovery is the planned restoration of technology systems, data, and services after a serious disruption.
A successful backup job is a starting point. Recovery also needs the infrastructure, configuration, application code, and access required to make the service work again.
AWS describes several recovery strategies, from restoring backups to keeping recovery environments partly or fully running. The right choice depends on business requirements and the cost of meeting them.
Two objectives make those requirements concrete. The recovery time objective, or RTO, sets the acceptable interruption before service is restored. The recovery point objective, or RPO, sets the acceptable data-loss window, expressed in time. These are targets to test, not guarantees supplied by naming a backup product.
Restore the service, not just its files
Test the dependencies and normal business operations as well as the restore itself. A database that starts successfully is not enough if the application cannot authenticate or reach it.
The backup-protection article covers requests that could weaken recovery safeguards. It is one part of recovery planning, rather than a complete disaster recovery procedure.
Recovery and incident investigation may also continue together. Restoring availability does not resolve whether information was stolen; the extortion-claim article addresses that separate question. Business continuity covers how essential work continues while systems are unavailable.