Installing SnapManager in an existing Windows cluster

You can install and configure SnapManager for Microsoft Exchange in an existing Windows cluster.

Before you begin

The shared LUNs must be physical disk resources in the cluster group that contains the Exchange virtual server that uses them.

You need to install Microsoft Management Console 3.0, Windows PowerShell 1.0 (x64 or x86) and Microsoft .NET 3.5 Framework (x64 or x86) on 64-bit and 32-bit operating system respectively, for SnapManager to work.

Prepare your SnapManager data configuration plan.

About this task

SnapManager adds the dependencies automatically for all the LUNs that Exchange uses, if the Configuration wizard detects that it is being run on a cluster. There are no dependencies set on the LUN physical disk resource in a Continuous Cluster Replication (CCR) configuration.

Steps

Verify that the Exchange virtual servers and the cluster services are functioning, by moving the Exchange virtual server from one cluster node to the other, and back.
If any errors occur, or if any of the cluster resources do not start correctly, resolve the issue before continuing.
Install or upgrade SnapDrive as required.
For details, see the SnapDrive documentation.
Create the shared LUNs to hold the Exchange databases and transaction log files, according to your SnapManager data configuration plan.
Create the shared LUNs from the node that owns the cluster group, which contains the Exchange virtual server.
For details, see your SnapDrive documentation.
Verify that dependencies for the System Attendant Resource are set correctly.
The System Attendant Resource depends on all the LUN physical disk resources, and the Network Name resource in this cluster group, for Exchange Server 2003 clusters and Exchange Server 2007 single copy cluster.
Verify that the Exchange virtual servers and the cluster services are functioning correctly by moving the cluster group containing the newly created Exchange virtual server to the other node and back.
Install SnapManager on all nodes, starting with the node that currently owns the cluster resources.
Use either the interactive installation procedure or the unattended installation procedure for a stand-alone Windows host system.
Start SnapManager.