Disaster Recovery to the Cloud
The second data centre gives way to a recovery region: servers copied in the background, recovery servers started only for a drill or a disaster.
The second data centre, kept only for disaster recovery, gives way to a recovery region in the cloud. Every protected server is copied over the private link into a low-cost staging area, and recovery servers are launched only for a drill or a real disaster, when DNS moves the names across. A locked backup vault keeps copies no one can change, for the day replication has copied the damage too.
Point at a component to light its links; select it for what it does here and the practice that makes it right on AWS.
When to use it
- A second site kept only for disaster recovery, full of standby servers
- Recovery targets (RTO, RPO) that restoring from backup alone cannot meet
- A first, low-risk step into the cloud: production stays put, only the standby moves
Where FleziLift fits
The DR servers sit in the AS-IS inventory like any other, each fact graded by evidence from L0 to L3. The 7R rule tree decides each one, with its target service, readiness and risk, and a treatment the customer has stated wins first; standby servers being retired leave the waves, marked Retired by Go / No-Go rule R1. The architect places the DR work in the Wave Plan, and the playbook lists it with each cloud's own tool: replication, backups kept apart, a full DR test, then closing the old site. FleziLift plans it; the DR services replicate and recover.
Cloud TransformationThe same pattern, the way each provider builds it
Each cloud's own framework and guidance.
