Storage Foundation and High Availability Solutions 7.4 HA and DR Solutions Guide for Microsoft Exchange 2010 - Windows
- Section I. Introduction and Concepts
- Introducing Storage Foundation and High Availability Solutions for Microsoft Exchange Server
- About clustering solutions with InfoScale products
- About high availability
- How a high availability solution works
- How VCS monitors storage components
- Shared storage - if you use NetApp filers
- Shared storage - if you use SFW to manage cluster dynamic disk groups
- Shared storage - if you use Windows LDM to manage shared disks
- Non-shared storage - if you use SFW to manage dynamic disk groups
- Non-shared storage - if you use Windows LDM to manage local disks
- Non-shared storage - if you use VMware storage
- About SFW HA support for Exchange Server 2010
- About campus clusters
- Differences between campus clusters and local clusters
- Sample campus cluster configuration
- What you can do with a campus cluster
- About replication
- About a replicated data cluster
- How VCS replicated data clusters work
- About disaster recovery
- What you can do with a disaster recovery solution
- Typical disaster recovery configuration
- Introducing the VCS agent for Exchange 2010
- About the VCS database agent for Microsoft Exchange 2010
- Exchange 2010 database agent functions
- Exchange 2010 database agent state definitions
- Exchange 2010 database agent resource type definition
- Exchange 2010 database agent attribute definitions
- Exchange 2010 service group resource dependency graph
- Exchange 2010 service group sample configuration
- Introducing Storage Foundation and High Availability Solutions for Microsoft Exchange Server
- Section II. Configuration Workflows
- Configuring high availability for Exchange Server with InfoScale Enterprise
- Reviewing the HA configuration
- Reviewing a standalone Exchange Server configuration
- Reviewing the campus cluster configuration
- Reviewing the Replicated Data Cluster configuration
- Reviewing the disaster recovery configuration
- Following the HA workflow in the Solutions Configuration Center
- VCS campus cluster configuration
- VCS Replicated Data Cluster configuration
- Disaster recovery configuration
- About installing the Veritas InfoScale products
- Notes and recommendations for cluster and application configuration
- Campus cluster failover using the ForceImport attribute
- Configuring the storage hardware and network
- Configuring disk groups and volumes for Exchange Server
- About cluster disk groups and volumes
- Prerequisites for configuring cluster disk groups and volumes
- Considerations for a fast failover configuration
- Considerations for converting existing shared storage to cluster disk groups and volumes
- Considerations when creating disks and volumes for campus clusters
- Considerations for volumes for a Volume Replicator configuration
- Sample disk group and volume configuration for Exchange 2010
- Viewing the available disk storage
- Creating a dynamic disk group
- Adding disks to campus cluster sites
- Creating volumes for high availability clusters
- Creating volumes for campus clusters
- About managing disk groups and volumes
- 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
- Configuring high availability for Exchange Server with InfoScale Enterprise
- Section III. Deployment
- Installing Exchange Server 2010
- Configuring Exchange Server for failover
- Tasks for configuring a new server for high availability
- Tasks for configuring an existing server for high availability
- About configuring the Exchange 2010 service group
- Prerequisites for configuring the Exchange Server service group
- Creating the Exchange Server 2010 service group
- Configuring the service group in a non-shared storage environment
- Verifying the Exchange Server cluster configuration
- Determining additional steps needed
- Configuring campus clusters for Exchange Server
- Configuring Replicated Data Clusters for Exchange Server
- Tasks for configuring Replicated Data Clusters for Exchange Server
- Creating the primary system zone for the application service group
- Creating a parallel environment in the secondary zone
- Setting up security for Volume Replicator
- Setting up the Replicated Data Sets (RDS)
- Configuring a RVG service group for replication
- Creating the RVG service group
- Configuring the resources in the RVG service group for RDC replication
- Configuring the IP and NIC resources
- Configuring the VMDg or VMNSDg resources for the disk groups
- Modifying the DGGuid attribute for the new disk group resource in the RVG service group
- Adding the Volume Replicator RVG resources for the disk groups
- Linking the Volume Replicator RVG resources to establish dependencies
- Deleting the VMDg or VMNSDg resource from the Exchange Server service group
- Configuring the RVG Primary resources
- Configuring the primary system zone for the RVG service group
- Setting a dependency between the service groups
- Adding the nodes from the secondary zone to the RDC
- Adding the nodes from the secondary zone to the RVG service group
- Configuring secondary zone nodes in the RVG service group
- Configuring the RVG service group NIC resource for fail over (VMNSDg only)
- Configuring the RVG service group IP resource for failover
- Configuring the RVG service group VMNSDg resources for fail over
- Adding the nodes from the secondary zone to the Exchange Server service group
- Configuring the zones in the Exchange Server service group
- Configuring the application service group IP resource for fail over (VMNSDg only)
- Configuring the application service group NIC resource for fail over (VMNSDg only)
- Verifying the RDC configuration
- Additional instructions for GCO disaster recovery
- Deploying disaster recovery for Exchange Server
- Tasks for deploying a disaster recovery configuration of Microsoft Exchange
- Tasks for setting up DR in a non-shared storage environment
- Reviewing the disaster recovery configuration
- Setting up the secondary site: Installing InfoScale Enterprise and configuring a cluster
- Verifying your primary site configuration
- Setting up your replication environment
- Assigning user privileges (secure clusters only)
- About configuring disaster recovery with the DR wizard
- Configuring disaster recovery with the DR wizard
- Cloning the storage on the secondary site using the DR wizard (Volume Replicator replication option)
- Creating temporary storage on the secondary site using the DR wizard (array-based replication)
- Installing Exchange 2010
- Cloning the service group configuration from the primary site to the secondary site
- Configuring the Exchange service group in a non-shared storage environment
- Configuring replication and global clustering
- Creating the replicated data sets (RDS) for Volume Replicator replication
- Creating the Volume Replicator RVG service group for replication
- Configuring the global cluster option for wide-area failover
- Verifying the disaster recovery configuration
- Establishing secure communication within the global cluster (optional)
- Adding multiple DR sites (optional)
- Recovery procedures for service group dependencies
- Possible task after creating the DR environment: Adding a new failover node to a Volume Replicator environment
- Testing fault readiness by running a fire drill
- About disaster recovery fire drills
- About the Fire Drill Wizard
- About post-fire drill scripts
- Tasks for configuring and running fire drills
- Prerequisites for a fire drill
- Preparing the fire drill configuration
- System Selection panel details
- Service Group Selection panel details
- Secondary System Selection panel details
- Disk Selection panel details
- Hitachi TrueCopy Path Information panel details
- HTCSnap Resource Configuration panel details
- SRDFSnap Resource Configuration panel details
- Fire Drill Preparation panel details
- Running a fire drill
- Re-creating a fire drill configuration that has changed
- Restoring the fire drill system to a prepared state
- Deleting the fire drill configuration
- Considerations for switching over fire drill service groups
- Section IV. Reference
- 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
- Appendix B. Troubleshooting
- Appendix A. Using Veritas AppProtect for vSphere
Establishing secure communication within the global cluster (optional)
A global cluster is created in non-secure mode by default. You may continue to allow the global cluster to run in non-secure mode or choose to establish secure communication between clusters.
The following prerequisites are required for establishing secure communication within a global cluster:
The clusters within the global cluster must be running in secure mode.
You must have Administrator privileges for the domain.
The following information is required for adding secure communication to a global cluster:
The active host name or IP address of each cluster in the global configuration.
The user name and password of the administrator for each cluster in the configuration.
If the local clusters do not point to the same root broker, the host name and port address of each root broker.
Adding secure communication involves the following tasks:
Taking the ClusterService-Proc (wac) resource in the ClusterService group offline on the clusters in the global environment.
Adding the -secure option to the StartProgram attribute on each node.
Establishing trust between root brokers if the local clusters do not point to the same root broker.
Bringing the ClusterService-Proc (wac) resource online on the clusters in the global cluster.
To take the ClusterService-Proc (wac) resource offline on all clusters
- From Cluster Monitor, log on to a cluster in the global cluster.
- In the Service Groups tab of the Cluster Explorer configuration tree, expand the ClusterService group and the Process agent.
- Right-click the ClusterService-Proc resource, click Offline, and click the appropriate system from the menu.
- Repeat all the previous steps for the additional clusters in the global cluster.
To add the -secure option to the StartProgram resource
- In the Service Groups tab of the Cluster Explorer configuration tree, right-click the ClusterService-Proc resource under the Process type in the ClusterService group.
- Click View > Properties view.
- Click the Edit icon to edit the StartProgram attribute.
- In the Edit Attribute dialog box, add -secure switch to the path of the executable Scalar Value.
For example:
"C:\Program Files\Veritas\Cluster Server\bin\wac.exe" -secure
- Repeat the previous step for each system in the cluster.
- Click OK to close the Edit Attribute dialog box.
- Click the Save and Close Configuration icon in the tool bar.
- Repeat all the previous steps for each cluster in the global cluster.
To establish trust between root brokers if there is more than one root broker
- Establishing trust between root brokers is only required if the local clusters do not point to the same root broker.
Log on to the root broker for each cluster and set up trust to the other root brokers in the global cluster.
The complete syntax of the command is:
vssat setuptrust --broker host:port --securitylevel [low|medium|high] [--hashfile fileName | --hash rootHashInHex]
For example, to establish trust with a low security level in a global cluster comprised of Cluster1 pointing to RB1 and Cluster2 pointing to RB2 use the following commands:
From RB1, type:
vssat setuptrust --broker RB2:14141 --securitylevel low
From RB2, type:
vssat setuptrust --broker RB1:14141 --securitylevel low
To bring the ClusterService-Proc (wac) resource online on all clusters
- In the Service Groups tab of the Cluster Explorer configuration tree, expand the ClusterService group and the Process agent.
- Right-click the ClusterService-Proc resource, click Online, and click the appropriate system from the menu.
- Repeat all the previous steps for the additional clusters in the global cluster.