Cluster Server 7.4.1 Implementation Guide for Microsoft Exchange 2010 - Windows

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.1)
Platform: Windows
  1. Introducing the VCS agents for Exchange and NetApp
    1.  
      About VCS support for Exchange 2010 and NetApp
    2. About the VCS database agent for Exchange 2010
      1.  
        Agent functions
      2.  
        Agent state definitions
    3. About the VCS hardware replication agent for NetApp
      1.  
        About the NetApp Filer agent
      2.  
        About the NetApp SnapDrive agent
      3.  
        About the NetApp SnapMirror agent
    4. How the VCS agents make Exchange highly available
      1.  
        Local cluster configuration
      2.  
        Disaster recovery configuration
    5. Typical Exchange configurations in a VCS cluster
      1.  
        Active-Active failover configuration
      2.  
        Disaster recovery configuration for Exchange
  2. Installing the product and configuring a VCS cluster
    1.  
      About installing the VCS agents
    2. Configuring the cluster using the Cluster Configuration Wizard
      1.  
        Configuring notification
      2.  
        Configuring Wide-Area Connector process for global clusters
  3. Installing Microsoft Exchange Server 2010
    1.  
      About installing Exchange 2010 in a VCS environment
    2. Before you install Exchange 2010
      1.  
        Configuring Microsoft iSCSI initiator
    3. Managing storage using NetApp filer
      1.  
        Connecting virtual disks to the cluster node
      2.  
        Disconnecting virtual disks from the cluster nodes
    4. Managing storage using Windows Logical Disk Manager
      1.  
        Reserving disks (if you use Windows LDM)
      2.  
        Creating volumes (if you use Windows LDM)
      3.  
        Mounting volumes (if you use Windows LDM)
      4.  
        Unassigning a drive letter
      5.  
        Releasing disks (if you use Windows LDM)
    5. Installing Exchange Server 2010
      1.  
        Creating mailbox databases on shared storage
  4. Configuring the Exchange database service group
    1.  
      About configuring the Exchange service group
    2.  
      Prerequisites for configuring the Exchange database service group
    3. Creating the Exchange database service group
      1.  
        Running SnapManager for Exchange
      2.  
        About the modifications required for tagged VLAN or teamed network
    4. About verifying the service group configuration
      1.  
        Bringing the service group online
      2.  
        Taking the service group offline
      3.  
        Switching the service group
    5. About modifying the Exchange database service group configuration
      1.  
        Prerequisites for modifying an Exchange database service group
      2.  
        Modifying the Exchange database service group
    6.  
      Deleting the Exchange service group
  5. Making a standalone Exchange server highly available
    1.  
      High availability configuration for a standalone server
    2.  
      Moving mailbox databases to shared storage
  6. Deploying Disaster Recovery for Exchange Server
    1.  
      About disaster recovery configuration
    2.  
      Setting up disaster recovery configuration
    3.  
      Configure replication using NetApp SnapMirror
    4.  
      Configure NetAppSnapMirror resources at the primary site
    5.  
      Configure NetAppSnapMirror resources at the secondary site
  7. Removing the software components
    1.  
      About removing the software components
    2. Remove Microsoft Exchange
      1.  
        Removing a node without removing Microsoft Exchange
      2.  
        Removing a node and removing Microsoft Exchange
  8. Troubleshooting
    1.  
      About troubleshooting VCS agents for Exchange
    2.  
      VCS logging
    3.  
      VCS Cluster Configuration Wizard (VCW) logs
    4.  
      VCWsilent logs
    5.  
      NetApp agents error messages
  9. Appendix A. Resource type definitions
    1.  
      About resource type definitions
    2. Exchange database agent
      1.  
        Exchange 2010 database agent resource type definition
      2.  
        Exchange 2010 database agent attribute definitions
      3.  
        Dependency graph for an Exchange cluster
  10. Appendix B. Sample Configurations
    1.  
      About the sample configurations
    2.  
      Sample service group configuration

Prerequisites for configuring the Exchange database service group

Ensure that the following prerequisites are met before configuring the service group:

  • Verify that InfoScale Availability is installed on all cluster nodes.

    Refer to the Veritas InfoScale Installation and Upgrade Guide.

  • Verify the cluster is configured.

  • Verify your DNS server settings. Make sure a static DNS entry maps the virtual IP address with the virtual computer name.

  • You must be a Cluster Administrator to create and configure service groups.

  • You must be a local Administrator on the node where you run the wizard.

  • You must be an Administrator for the NetApp Filer containing the LUNs created to store Exchange data components.

  • Verify that Command Server service (CmdServer) is running on all nodes in the cluster. Select Services on the Administrative Tools menu and verify that the Veritas Command Server shows that it is started.

  • On the node on which you run the wizard, select Services on the Administrative Tools menu and verify that the Veritas High Availability Engine service is running.

  • Verify the volumes or the virtual disks (LUNs) created to store the following data components are mounted or connected to the node where you run the wizard and dismounted or disconnected from other nodes in the cluster:

    • Exchange database

    • Transaction logs

  • If you have configured a firewall, add the required ports and services to the Firewall Exception list.

    For a detailed list of services and ports used, refer to the Veritas InfoScale Installation and Upgrade Guide.

  • In an IPv6 environment, the Lanman agent relies on the DNS records to validate the virtual server name on the network. If the virtual servers configured in the cluster use IPv6 addresses, you must specify the DNS server IP, either in the network adapter settings or in the Lanman agent's AdditionalDNSServers attribute.