Most SharePoint consultants are faced with a situation where the clients ask for maximum (say 99%) uptime which is quite logical because in such enterprise
level organizations, a little downtime period can result in huge loss of business activities. Some of them need the ability to fail over to a different server
farm in case of a disaster. Customers also dream for a design that can considerably optimize performance of the system. Keeping all the above high end
requirements in focus, they still insist that the constraints of budget, hardware and software licenses do apply.
Other facets of High Availability
- Capacity - the science and art of estimating the space, computer hardware, software and connection infrastructure resources
- Disaster Recovery/Failover - allows MOSS at location A to go offline and automatically fail over to location B with no or minimal downtime.
Availability, by definition is the extent to which the solution is responsive to the requests and tolerant to failure.
If the availability requirements for a particular system are too high, the server farm designs can be modified to use redundant servers at the WFE and the database level.
This is the typical criteria for deciding the number of servers in a server farm. This should normally also result in a high performing system as NLB technique on the WFE servers can result in a better performance in peak times.