Windows 2008 / Multi-subnet clusters and using static routes.

=========================================================== ***SEE UPDATE*** =========================================================== With the enhancements in Windows 2008 to allow for multi-subnet clustering it is becoming more common to see this utilized with Exchange 2007 SP1 installations.  When implementing a clustered solution, it is a requirement that there be a minimum of two interfaces on each node, and that each node can maintain…

23

One thing not to do when Exchange 2007 cluster setup fails…

There are times where cluster setup operations fail during the active clustered mailbox server installation. Depending on where the failure occurred, when reviewing the resources in cluster administrator, it may appear that setup has fully completed.   For example – there is an IP, Name, System Attendant, Information Store, and Database Instance resources.  When a setup…

0

EXTRA!! EXTRA!! Read all about it…get your SCR fixes here (aka Exchange 2007 SP1 RU7 released!)

Exchange 2007 SP1 RU7 released today.   The following important SCR (Standby Continuous Replication) fixes are now available. KB 961281 Update Rollup 5 for Exchange Server 2007 Service Pack 1 introduced an error when you enable SCR for a storage group in an environment with a parent/child domain structure. See Tim’s blog post for more info….

2

Running setup.com /clearLocalCMS on a Windows 2008 cluster disables the machine accounted (VCO) associated with the CMS name.

The setup.com /clearLocalCMS is responsible for purging the clustered configuration for Exchange resources without making any changes to the active directory for the Exchange instance.  This command is commonly used to clean the cluster configuration on the source Exchange cluster prior to running setup.com /recoverCMS or to clear the clustered resources from the target Exchange…

0

Exchange 2007 /newCMS or /recoverCMS fails when installing on Windows 2003 clusters.

When running Exchange 2007 /newCMS or /recoverCMS on a Windows 2003 clustered node, the following error may be noted in the setup command. [ERROR] The computer account ‘<CMSName>’ was created on the domain controller ‘\\PDCEmulator.domain.com, but has not replicated to the desired domain controller (LocalDC.domain.com) after waiting approximately 60 seconds. Please wait for the account…

1

A lossy failover causes duplicate mails to be delivered to clients from the hub transport dumpster when using Exchange 2007 SP1 Cluster Continuous Replication (CCR).

In the recent weeks I have worked with some customers that have experienced duplicate mails in the Outlook client after a CCR cluster experiences a lossy failover. A lossy failover occurs when the Exchange resources move between nodes and logs exist on the source that could not be copied to the target.  Depending on settings…

1

Using Standby Continuous Replication in both single node cluster implementation and database portability implementation when only a single machine is available.

Last week I received an interesting question from one of our Exchange MVPs.  “Can I use a single node cluster as an SCR target for both recovering the entire cluster or recovering just a single database?” My original thoughts on this was no…when implementing SCR you have to make a choice.  Are you implementing a…

1

Restore-StorageGroupCopy –standbymachine requires use of –force in order to complete successfully when activating a Standby Continuous Replication target in Exchange 2007 SP1.

When attempt to run restore-storagegroupcopy on an SCR target you may receive the following error (note this is with verbose output): [PS] C:\Windows\System32>Restore-StorageGroupCopy MBX-4\MBX-4-SG1 -StandbyMachine MBX-3 -Verbose > output.txt VERBOSE: Restore-StorageGroupCopy : Beginning processing. VERBOSE: Restore-StorageGroupCopy : Searching objects "MBX-4\MBX-4-SG1" of type "StorageGroup" under the root "$null". VERBOSE: Restore-StorageGroupCopy : Previous operation run on domain…

0

Permissions recommended for the CNO (Cluster Name Object) in Windows 2008 for Exchange 2007 SP1 setup operations.

In Windows 2003 when cluster would attempt to create or modify Kerberos enabled machine accounts it would do so by leveraging the rights assigned to the cluster service account.  The Windows 2003 cluster service would use this domain account for the logon right at service startup. In Windows 2008 when the cluster attempts to create…

4