Exchange 2007 SP1 CCR / LCR / SCR – Transaction Log Roll

Recently there have been some questions about transaction log rolling and continuous replication.  In some cases these questions often surround storage group copy status showing an initializing state (http://blogs.technet.com/timmcmic/archive/2009/01/26/get-storagegroupcopystatus-initializing.aspx). Under normal circumstances, the only time that log would roll, is when we’ve reached a log full condition.  If the server is being utilized, this is…

0

When to use restore-storagegroupcopy with the –force switch and standby continuous replication (SCR)

Recently there was a lively internal debate regarding how to use restore-storagegroupcopy and the –force switch. The documentation regarding the restore-storagegroupcopy command can be found at http://technet.microsoft.com/en-us/library/aa996024.aspx. According to the TechNet documentation: “The Force parameter can be used when the task is run programmatically and prompting for administrative input is inappropriate. If Force is not…

0

Evicting an Exchange 2007 clustered node.

There maybe time in either Windows 2003 or Windows 2008 where it may become necessary to evict a clustered node that has Exchange 2007 installed on it. Under normal circumstances evicting a clustered node is a benign procedure.  When the node has Exchange 2007 installed on it special precautions must be taken. When Exchange 2007…

1

Testing SCR in a production environment.

Occasionally I have an opportunity to work with our Exchange MVPs.  Neil Hobson, one of our Exchange MVPs, has recently started a series on how to test SCR in a production environment.  If you have the time I would suggest checking it out! Part 1:  http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/testing-scr-production-environment-part1.html   Part 2:  http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/testing-scr-production-environment-part2.html   Look for parts 3…

0

ExBPA incorrectly flags Windows 2003 cluster rules on Windows 2008

When running ExBPA against a Windows 2008 cluster (either CCR or SCC) the following best practices may be flagged: “Cluster dedicated heartbeat network priority set incorrectly” – http://technet.microsoft.com/en-us/library/aa997088.aspx “Dedicated cluster heartbeat not found” – http://technet.microsoft.com/en-us/library/aa998726.aspx “Quorum log too small” – http://technet.microsoft.com/en-us/library/aa995830.aspx These rules only apply to Windows 2003 clusters and the recommendations should not be…

1

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