Maximum tolerable downtime is the longest period an organization can accept without service during recovery. The target may be minutes, hours, or days, depending on client needs and the economics of disruption. section 8.4.1
Set the tolerance by answering:
- Whether recovery requires full service or only partial service. section 8.4
- Whether the organization will fail forward to a new primary or eventually return to the original environment. section 8.4
- Whether the cost of near-continuous availability is justified by the consequences of downtime. section 8.4.1
Hot or cold standby
A hot standby keeps servers running and data continually synchronized, minimizing downtime but consuming power, bandwidth, and hardware lifetime. A cold standby costs less but requires machines to boot and synchronize after failover, making it slower yet acceptable for some situations. section 8.4.1
Use the DR foundations figure to place downtime tolerance alongside service scope, failover direction, and backup-zone choices. section 8.4
Use the downtime economics figure to compare the financial consequences of tolerance levels and standby configurations. section 8.4.1
