To reach that conclusion, we must first start by defining what High Availability is. Ultimately, HA is the level of availability that an organization requires from a particular application (or set of applications). If you only need your systems five minutes a year, and the system is up for those five minutes (and no other), you have high availability. On the other hand, if, when your systems are down, airplanes fall out of the sky, no downtime at all is acceptable. Most likely, your critical systems fall someplace in between those two extremes.
You may decide that the cost of a full-blown DR solution is too high for your organization, and you'd be better served not implementing one at all. Ultimately, HA is a business decision, where you balance the cost of downtime against the cost of implementing the solution.
Hope this is helpful.
Dig Deeper on Disaster recovery planning - management
Related Q&A from Evan Marcus
Storage expert Evan Marcus compares software and hardware RAID and outlines the benefits and drawbacks of each. Continue Reading
This expert answer explains the purpose of creating LUNs and details reasons for creating multiple LUNs. Continue Reading
This advice details the hardware and software requirements for setting up two data servers in fail-safe cluster mode for high availability. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.