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 clustering solutions with SFW HA
- About high availability
- How a high availability solution works
- About replication
- About disaster recovery
- What you can do with a disaster recovery solution
- Typical disaster recovery configuration
- About high availability support for SharePoint Server
- About the SharePoint Search service application
- Introducing the VCS agent for SharePoint Server 2010
- Configuration workflows for SharePoint Server 2010
- Reviewing the HA configuration
- Reviewing the disaster recovery configuration
- High availability (HA) configuration
- Disaster recovery configuration
- Notes and recommendations for cluster and application configuration
- Configuring the storage hardware and network
- Configuring the cluster using the Cluster Configuration Wizard
- Using the Solutions Configuration Center
- About the Solutions Configuration Center
- Starting the Solutions Configuration Center
- Options in the Solutions Configuration Center
- About launching wizards from the Solutions Configuration Center
- Remote and local access to Solutions wizards
- Solutions wizards and logs
- Workflows in 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
- Prerequisites for configuring a service group for a SharePoint Search service application
- Installing and configuring SharePoint Server 2010
- Changing the index location of the Crawl and Query components
- Configuring a service group for a SharePoint Search service application manually
- Configuring the service group for a Search service application using the wizard
- Verifying the application service group
- Configuring a Search service application for disaster recovery
- Administering the SharePoint Search Service Application service group
- Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
- About Just In Time Availability
- Prerequisites
- Setting up a plan
- Deleting a plan
- Managing a plan
- Viewing the history tab
- Limitations of Just In Time Availability
- Getting started with Just In Time Availability
- Supported operating systems and configurations
- Viewing the properties
- Log files
- Plan states
- Troubleshooting Just In Time Availability
Reviewing the HA configuration
Veritas recommends as a best practice to configure SQL Server for high availability before configuring SharePoint Server.
Configuring SQL Server for high availability is covered in the SQL Server solutions guides.
In a typical example of a SharePoint Server high availability environment, SharePoint Web Applications and Service Applications are configured on a separate set of cluster nodes. A VCS parallel service group manages the Web Applications residing on the Web servers and local service groups manage the application servers. The SharePoint databases are made highly available using the SQL Server service group. The databases reside on shared storage that is accessible from all the SharePoint server nodes in the cluster.
The following figure illustrates a typical SharePoint Server configuration. The SharePoint farm layout is as follows:
Nodes N1, N2, and N3 are the Web front end servers
Nodes N4 and N5 are the application servers
Nodes N6 and N7 host the SharePoint SQL databases
The graphic displays SQL and SharePoint Servers in different clusters. However, if the SharePoint Servers and SQL Servers are using the same operating system and platform, you can configure both SQL and SharePoint nodes in the same cluster.
The SharePoint Web Applications are configured in a parallel service group that is online on Nodes N1, N2, and N3. The application servers host SharePoint services such as Access Services and Excel Services that are used by the Web servers. These application services are configured in local service groups on nodes N4 and N5 separately. If any of the configured Web or Service applications become unavailable, the SharePoint agent attempts to restart those components in the cluster. If the component fails to come online, the agent declares the resource as faulted.
The databases are made highly available by the SQL service group that is configured on nodes N6 and N7. The databases are configured on the shared storage. The SQL virtual server is online on node N6. All client requests are handled by node N6. N7 waits in a warm standby state as a backup node, prepared to begin handling client requests if N6 becomes unavailable. If N6 fails, N7 becomes the active node and the SQL virtual server comes online on N7. From the user's perspective there will be a small delay as the backup node comes online, but the interruption in effective service is minimized.