Please enter search query.
Search <book_title>...
Cluster Server 7.4.1 Implementation Guide for Microsoft Exchange 2010 - Windows
Last Published:
2019-02-01
Product(s):
InfoScale & Storage Foundation (7.4.1)
Platform: 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
How the VCS agents make Exchange highly available
The VCS database agent for Exchange detects a failure in case of a system failure or if the Exchange Mailbox Server becomes unavailable on a node. VCS moves the mailbox databases configured on that node to the next available cluster node in the service group's system list. The agent also starts the critical Exchange 2010 services on that node, if required. The databases then become active on the new node. The client requests are then handled by the Mailbox Server on the new node, thus maintaining continuous availability of the Exchange 2010 mailbox databases.
The following topics describe how the agents migrate Exchange Server to another node in local clusters and in global disaster recovery environments.