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 disaster recovery configuration
You configure SQL Server for disaster recovery before configuring SharePoint Server.
Configuring SQL Server for disaster recovery is covered in the SQL Server solutions guides.
The following figure shows an example SharePoint Server disaster recovery configuration.
Table: Sample Disaster Recovery configuration objects
Object Name | Description |
|---|---|
SYSTEM1 & SYSTEM2 | first and second nodes of the primary site |
CLUS1 | separate SharePoint cluster, if not using the SQL Server cluster |
SP_SG | SharePoint service group |
SYSTEM3 & SYSTEM4 | First and second nodes of the secondary site |
CLUS1 | separate SharePoint cluster, if not using the SQL Server cluster |
SP_SG | SharePoint service group |
The example configuration for SharePoint disaster recovery shows SharePoint configured in a separate cluster from SQL Server. However, you can optionally configure SharePoint Server in the same cluster as SQL Server if all systems use the same operating system.
In the example setup, there are eight SharePoint servers, four for the primary site and four for the secondary site. This is an example only; any supported farm configuration can be used. The SharePoint nodes will form two separate clusters, one at the primary site and one at the secondary site.
Note:
You do not need to configure the same number of SharePoint web servers or application servers on the secondary site as on the primary site. However, you should provide for all required services to be available on the secondary site.
The sample setup for SQL Server has four servers, two for the primary site and two for the secondary site. The nodes will form two separate clusters, one at the primary site and one at the secondary site. Disaster recovery configuration for SQL Server configures a global cluster with replication of the databases from the primary to the secondary site.
If the SQL Server primary site fails, the replicated SQL Server databases on the secondary site come online, along with SQL Server. In addition, the SharePoint Servers on the secondary site will automatically start responding to clients.
If the SharePoint Servers fail on the primary site, but SQL Server remains online on the primary site, you would need to manually switch the SQL Server service group to the secondary site. This would be necessary for the secondary site SharePoint servers to respond to clients.