Enabling Standby Continuous Replication to use an alternate network interface in Exchange 2007 SP1

Many customers have requested instructions on how to enable standby continuous replication to use an alternate network interface.  By design standby continuous replication always uses the “public” interface to ship logs and seed the database. Over the past few weeks we have been working with the Exchange product group on a “supported” method to allow…

1

Kerberos authentication, dns suffix lists, the replication service, and Exchange management commandlets…

When using any form of multi-machine Exchange 2007 replication (CCR / SCR) Kerberos authentication is very important.  We leverage the rights of Exchange server machine accounts for several functions including the ability to replicate log files and utilize the remote registry service for commandlets. Some Background… In terms of the replication service we copy logs…

0

Setting up a Windows 2008 cluster where nodes reside in a disjointed DNS namespace…

When attempting to establish the cluster services on nodes that utilize a dis-joint DNS namespace, the following errors may be encountered: Log Name: System Source: Microsoft-Windows-FailoverClustering Date: Date_Time Event ID: 1127 Task Category: None Level: Error Keywords: User: SYSTEM Computer: ComputerName Description: Cluster Network interface InterfaceName for cluster node NodeName on network NetworkName failed. Run…

0

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