When you use Exchange message tracking in an Microsoft Cluster Services (MSCS) configuration, place the message tracking directory on a shared LUN that does not store a database. If you specify a shared LUN with stored database, SnapManager restores an old copy of the message tracking log during the restore operation.
To create an Exchange virtual server in an MSCS configuration, install the Exchange binaries on both nodes and then create a new System Attendant cluster resource. As part of creating the System Attendant cluster resource, Exchange prompts you as follows:
Enter [a] path to the data directory.
Exchange places the new databases and other related files (including the SMTP and Message Transfer Agent (MTA) queues, message tracking logs, and Microsoft Search files, if configured) on this path on a shared disk.
Suppose that the path that you specify for the data directory at the System Attendant cluster resource is a shared LUN that is also specified for a database using the SnapManager Configuration wizard later. In this case, the Exchange message tracking log and the Exchange database are on the same LUN.
SnapManager does not prevent this configuration, nor does this configuration pose an immediate problem. During a subsequent restore operation, SnapManager restores the entire LUN from the Snapshot copy, with the desired database and an old copy of the message tracking log.
If you already created a System Attendant cluster resource with the data directory on a shared LUN with a stored database, you can move the message tracking location to a different location on a shared disk. For a description of how to move the message tracking location in Exchange Server 2003, see Microsoft Knowledge Base article 841089.