Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments

Installing SnapManager and creating a new Windows cluster

This topic describes how to install and configure SnapManager 3.2 for Microsoft Exchange during the process of creating a new Windows cluster. See the following subtopics for more information:

Related topics

About Active/Passive configurations  Top

In an Active/Passive Exchange cluster, there are two to four clustered nodes and one virtual Exchange server. If the node running Exchange fails, the cluster transfers the virtual Exchange server to the other node, which takes over the disks previously used by the partner node.

For an Active/Passive Exchange cluster, assuming that your Exchange data is on a shared resource, your disk requirements are the same as for a stand-alone Exchange system, with the addition of one LUN for the quorum disk.

Note
The Active/Passive configuration is recommended by Microsoft to avoid performance degradation if a node fails.

About Active/Active configurations  Top

In an Active/Active two-node configuration, there are two clustered nodes and an Exchange virtual server running on each node. If one node fails, the other node takes over the virtual server running on the failed node.

Because both nodes need to be able to run an active Exchange instance, each node requires its own disks, as if it were a self-contained stand-alone system. In addition, one extra LUN is needed for the quorum disk.

Note
Exchange 2000 does not support more than two active nodes in the same cluster.

Installing SnapManager in a new Windows cluster  Top

The procedure for installing SnapManager 3.2 for Microsoft Exchange in a new Windows cluster assumes the following facts:

To create the cluster and install and configure SnapManager 3.2 for Microsoft Exchange as part of the cluster, complete the following steps.

Step

Action

1

Create the cluster by following the procedure in your SnapDrive documentation for creating a Windows cluster with a virtual quorum disk.

2

Install and configure Exchange on one node; then install Exchange on the remaining nodes.

Note
Exchange virtual servers are not created during this step. See the Microsoft documentation for information about installing Exchange in a cluster.

You do not have to use the default cluster group, but whatever group you use must contain an IP address resource, a network name resource, and at least one physical disk cluster resource (LUN).

3

Using Cluster Administrator, create an Exchange System Attendant Resource in the cluster group where the LUN physical disk resources that store the Exchange databases and transaction logs will reside.

Note
Do this from the node that owns the cluster group containing the LUN physical disk resources.

During this step you are prompted for an Exchange data directory. This directory is also where the Exchange system files are placed. You can accept the default location now; these system files can be moved in a later step, if necessary, using the Configuration Wizard.

Specify the LUN physical disk resources and the Network Name resource as dependencies for the Exchange System Attendant Resource.

Result

The required Exchange cluster resources are created.

4

Bring the cluster group online if it is not already, and verify that the Exchange cluster is functioning correctly by moving the cluster group containing the newly created Exchange virtual server to the other node and back.

5

Install SnapManager on all nodes, starting with the node that currently owns the cluster resources.

You can install SnapManager in interactive mode or in unattended mode. Procedures for both installation modes are described in Installing SnapManager on a stand-alone Windows host system.

6

Proceed to Chapter 4, Starting SnapManager for the First Time.

Library Table of Contents Index Previous Page (Alt-p) Next Page (Alt-n) Comments