Storage Foundation and High Availability Solutions 7.4.1 HA and DR Solutions Guide for Microsoft SharePoint 2010 - Windows
- Introducing Storage Foundation and High Availability Solutions for SharePoint 2010
- About high availability support for SharePoint Server
- Introducing the VCS agent for SharePoint Server 2010
- Configuration workflows for SharePoint Server 2010
- Reviewing the HA configuration
- Notes and recommendations for cluster and application configuration
- Configuring the cluster using the Cluster Configuration Wizard
- Using the Solutions Configuration Center
- Installing and configuring SharePoint Server 2010 for high availability
- Configuring disaster recovery for SharePoint Server 2010
- Introducing the VCS agent for SharePoint Search Service Application
- About the VCS agent for SharePoint Search service application
- Configuring the SharePoint Search Service Application service group
- Verifying the application service group
- Administering the SharePoint Search Service Application service group
- Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
How a high availability solution works
Keeping data and applications functioning 24 hours a day and seven days a week is the desired norm for critical applications today. Clustered systems have several advantages over standalone servers, including fault tolerance, high availability, scalability, simplified management, and support for rolling upgrades.
Using Storage Foundation HA for Windows as a local high availability solution paves the way for a wide-area disaster recovery solution in the future.
A high availability solution is built on top of a backup strategy and provides the following benefits:
Reduces planned and unplanned downtime.
Serves as a local and wide-area failover (rather than load-balancing) solution. Enables failover between sites or between clusters.
Manages applications and provides an orderly way to bring processes online and take them offline.
Consolidates hardware in larger clusters. The HA environment accommodates flexible fail over policies, active-active configurations, and shared standby servers.