Cluster Server 7.4.1 Implementation Guide for Microsoft Exchange 2010 - Windows
- Introducing the VCS agents for Exchange and NetApp
- Installing the product and configuring a VCS cluster
- Installing Microsoft Exchange Server 2010
- Configuring the Exchange database service group
- Creating the Exchange database service group
- About verifying the service group configuration
- About modifying the Exchange database service group configuration
- Making a standalone Exchange server highly available
- Deploying Disaster Recovery for Exchange Server
- Removing the software components
- Troubleshooting
- Appendix A. Resource type definitions
- Appendix B. Sample Configurations
About VCS support for Exchange 2010 and NetApp
VCS support for Exchange Server 2010 includes high availability for Exchange 2010 mailbox databases.
VCS provides a database agent for Exchange 2010 that monitors the mailbox databases configured on shared storage. You must install the Exchange 2010 Mailbox Server role to allow VCS to make the databases highly available. The agent internally monitors a critical set of Exchange 2010 services to verify the availability of the Mailbox Server and the configured databases.
VCS however does not provide high availability support for public folders. VCS also does not provide high availability support for mailbox databases that are configured in an Exchange 2010 Data Availability Group (DAG). If you wish to make those databases highly available with VCS, you must first remove them from the DAG.
The VCS agent for NetApp SnapMirror enables configuring NetApp filers over an iSCSI or Fibre Channel (FC) connection in a VCS cluster environment. Both agents work together to provide high availability and disaster recovery to Exchange databases in environments using NetApp filers for shared storage. The agents also support disaster recovery configurations set up using the VCS Global Cluster Option and NetApp SnapMirror for data replication.
In a typical configuration, the agents are installed on each node in the cluster. The nodes are connected to the NetApp filers through a dedicated (private) storage network. VCS nodes are physically attached to the NetApp filer via an ethernet cable supporting iSCSI or Fibre Channel (FC) as the transport protocol.
The following figure illustrates a typical VCS cluster configuration in a NetApp storage environment.
For more information about the agents refer to their resource type definitions and attribute definitions.
More Information