A backup zone is a separate environment prepared to take over when the active zone fails. Disaster recovery may use one or several backup zones; with only one, failover consumes the remaining safety net. section 8.4
Plan a backup zone around the decisions that determine whether failover will be useful:
- Set the organization’s downtime tolerance and decide whether recovery requires full or partial service. section 8.4
- Decide whether the organization will fail forward to a new primary or eventually return to the original environment. section 8.4
- Test what the backup zone knows about completed work, because failover can create duplicates, omissions, or manual database and file-reconciliation tasks. section 8.4.2
Partial service during failover
An online store might let customers view products and add items to a cart while disabling checkout. Less visible functions, such as logging, reporting, and scheduled administration, may also be deferred. A fully serviced takeover is harder: interrupted email batches may need investigation, and duplicate emails may be acceptable. section 8.4.2
Use the foundations diagram to compare downtime tolerance, service scope, and failover direction when shaping a disaster-recovery strategy. section 8.4
