| Playlist Position | Disaster Recovery | Cluster DB / Web Farm | High Availability / Hot Site | Redundant WAN | |
|---|---|---|---|---|---|
| Network Downtime | 100 | 100 | 100 | 50 | 100 |
| Severe Performance Degradation | 100 | 100 | 100 | 0 | 0 |
| Scheduled Upgrade | 100 | 0 | 0 | 0 | 0 |
| Time to Switchover | 100Seamless | 0Hours to Days | 100Seamless to Seconds | 50Hour(s) | 100 |
| Server Hardware Failure | 100 | 100 | 100 | 100 | 0 |
| Application Failure | 100 | 50 | 0 | 50 | 0 |
| Data Corruption | 100 | 100 | 0 | 50 | 0 |
| Cost | $$ | $$$ | $ | $$$$$ | $$$$ |
Indicates that the solution above only performs in limited scenarios. As an example, with application failure
a hot site would only function if the failure had not been replicated to the hot site servers, which depends on
the hot site configuration and timing of the failure.