Exchange 2010: Two HA features which are no longer present…

As many probably already know Microsoft has announced the next version of Exchange – Exchange Server 2010. Since I like to write about high availability, I thought I’d let you know of two things that are no longer present in Exchange 2010 from a high availability standpoint. Local Continuous Replication Single Copy Clusters In Exchange…

1

Network port design and Exchange 2007 clusters.

(An Exchange 2010 version of this article can be found here: http://blogs.technet.com/b/timmcmic/archive/2010/05/30/network-port-design-and-exchange-2010-database-availability-groups.aspx) A question that I often see come up is how many network ports should I have in my clustered nodes and how should I use them. I generally see three different hardware configurations: Two network ports. Usually 2 onboard or 1 onboard /…

1

File Share Witness (FSW) placement and the cluster group.

With Exchange 2007 Cluster Continuous Replication clusters the recommended quorum type for the host cluster is Majority Node Set with File Share Witness (Windows 2003) or Node Majority and File Share Witness (Windows 2008). In this blog post I want to talk about two things that have an influence on these decisions. (Note:  All information…

1

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