Summary

In this chapter we discussed several primary variables of availability that should help to capture your high availability requirements much more cleanly and precisely. These variables included a basic uptime requirement, time to recovery, tolerance of recovery, data resiliency, application resiliency, performance/scalability, and the costs of downtime (loss). You can then take this information, couple it with your hardware/software configurations, several Microsoft-based technology offerings, and your allowable upgrade budget, and determine exactly which high availability solution you should implement that best supports your needs. In addition, a general “one-two” punch approach of establishing a proper high availability foundation in your environment should be done as soon as possible. Once completed, a knock-out punch that matches the proper high availability solution for your application's needs can be administered—getting it right the first time.