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

VCS logging

VCS generates two error message logs: the engine logs and the agent logs. Log file names are appended by letters. The letter A indicates the first log file, B indicates the second, C indicates the third, and so on.

The agent log is located at: %VCS_HOME%\log\agent_A.txt.

The format of agent log messages is: Timestamp (YYYY/MM/DD) | Mnemonic | Severity | UMI | Agent Type | Resource Name | Entry Point | Message Text.

The following table describes the agent log message components and their descriptions.

Table: Log message components and their description

Log message component

Description

Timestamp

Denotes the date and time when the message was logged.

Mnemonic

Denotes which Veritas product logs the message. For Cluster Server, the mnemonic is 'VCS'.

Severity

Denotes the severity of the message. Severity is classified into the following types:

  • CRITICAL indicates a critical error within a VCS process. Contact Technical Support immediately.

  • ERROR indicates failure of a cluster component, unanticipated state change, or termination or unsuccessful completion of a VCS action.

  • WARNING indicates a warning or error, but not an actual fault.

  • NOTE informs the user that VCS has initiated an action.

  • INFO informs the user of various state messages or comments.

    Among these, CRITICAL, ERROR, and WARNING indicate actual errors. NOTE and INFO provide additional information.

UMI or Unique Message ID

UMI is a combination of Originator ID, Category ID, and Message ID. For example, the UMI for a message generated by the ExchService agent would resemble: V-16-20024-13. Originator ID for all VCS products is 'V-16.' Category ID for ExchProtocol agent is 20023 while that for ExchService agent is 20024. Message ID is a unique number assigned to the message text.

Message Text

Denotes the actual message string.

You can view these message logs using Notepad or any text editor. All messages are logged to the engine and the agent logs. Messages of type CRITICAL and ERROR are written to the Windows event log.