I'm having some trouble wrapping my head around an issue I'm running into:

I have a 3 node exchange 2007 CCR environment running Version 8.1 (Build 240.6). Verified just now via command line. We're having a number of issues, and for obvious reasons (the dreaded 9667 being one of them).

I intend to install HeaderFilterAgent to fix this moving forward, and while I'm at it I want update to SP3, because I know it needs to happen. I've been reading the MS KB on this (https://technet.microsoft.com/en-us/library/Bb676320%28v=EXCHG.80%29.aspx) and I have a few questions:

1) While upgrading I see that I shutdown my clustered mailbox services and move them from my active node to my passive node after upgrading the active node. Doesn't the process of upgrading the active node disrupt the log file copy (get-storagegroupcopystatus)? If so how is my mailbox cluster going to move from my running passive node to my out of date node and come online after update without problems/corruption?

I just don't understand the situation/process. I'm trying, but it's illusive for me at the moment.

2) What does this mean " stop any services that have open handles to performance counters"?!

3) When I go to update my CAS/HT/UM, isn't that going to take my mailbox cluster offline (and possibly cause corruption if I don't shut down the cluster first)?

• Edited by KTAAdmin Monday, August 24, 2015 8:12 PM

Thanks for the information on the CAS/HT/UM box.

Regarding the Clustered Failover: This is where I get confused. I get that replication will stop when I stop the cluster services. But if my active node is Server2 and I go about updating Server3, then take my cluster offline, move it to Server3 then run /upgradecms how does it not cause problems with the MDB? Does it move the files from Server2 to Server3 prior to upgrading/updating the CMS? I'm asking because that's the only thing that makes sense in my mind, and our First Storage group is big (on the active node our Mailbox Datastore is 606G and on the passive node it's taking up 600G according to the files sizes. A discrepancy that scares me alone.).

Much appreciated all who try to help me understand!

• Edited by KTAAdmin Monday, August 24, 2015 8:23 PM

Looks like continuous replication only allows for one database per storage group.

Looks like I'll be making some more storage groups.

• Edited by KTAAdmin Monday, August 24, 2015 9:38 PM

I'd be more tempted to subscribe to the lifecycle newsletter and keep Exchange in a supported build.

Exchange 2007 SP1 went out of support in the year 2010:

http://blogs.technet.com/b/rmilne/archive/2012/03/26/exchange-2007-service-pack-3-is-required.aspx

You should be on SP3 RU17 at this point.