A warm standby is a secondary environment that is already running and receiving data from the primary, but at reduced capacity. To take over, it must be scaled up or finish a few preparation steps before it can carry full production traffic.
Why it matters
Warm standby sits between hot and cold standby in both cost and recovery time. You pay for a small fraction of production, yet recovery takes minutes instead of hours. It suits sites where a short outage is tolerable but a day-long rebuild is not, and it is a common pattern for cross-region disaster recovery.
Example
A site runs ten application servers in region A. In region B it keeps two small servers and a database replica. If region A fails, the team:
- Promotes the database replica.
- Scales region B from two servers to ten.
- Switches DNS or the traffic manager to region B.
The scale-up step is the part a hot standby does not need, so recovery time is longer but cheaper to maintain.
Common mistakes
- Sizing the standby so small that it cannot reach full capacity quickly because of quota limits or missing instance availability.
- Letting configuration and deployments drift, so the standby runs old code.
- Skipping a regular failover drill, which is the only proof the scale-up works.
Related
Get notified when this term updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.