Hi I have just created a CCR cluster on Windows 2003 Server. If I go to Cluster Administrator, I notice there are two Cluster Groups: ExchangeCCR: Exchange IS, System Attendant, First Storage Group, IP Address etc Cluster Group: Cluster IP Address, Cluster Name, Majority Node Set Could someone explain the difference between the two? Also, when I set the Cluster up, I had to enter an IP address and name for the Cluster, which was different to the CMS/address name. Should this have been the case? If so. what does it represent? Finally, does anyone know a way to find out which physical node a CCR server is on by viewing the Exchange Console? Say for instance I had multiple CCR clusters set up globally, and I wanted to check which node the one in Japan was on, how could I see that? So far, the only way seems to be log onto the CMS and open the Cluster Administrator

On Wed, 20 Oct 2010 19:13:52 +0000, Neil4933 wrote: >Hi I have just created a CCR cluster on Windows 2003 Server. If I go to Cluster Administrator, I notice there are two Cluster Groups: ExchangeCCR: Exchange IS, System Attendant, First Storage Group, IP Address etc Cluster Group: Cluster IP Address, Cluster Name, Majority Node Set Could someone explain the difference between the two? One represents the CMS. The other the cluster and FSW. When you move the CMS to another node you should make sure the cluster group is moved with it. >Also, when I set the Cluster up, I had to enter an IP address and name for the Cluster, which was different to the CMS/address name. Should this have been the case? Yes. Managing the cluster isn't the same as accessing the CMS. >If so. what does it represent? Finally, does anyone know a way to find out which physical node a CCR server is on by viewing the Exchange Console? Say for instance I had multiple CCR clusters set up globally, and I wanted to check which node the one in Japan was on, how could I see that? So far, the only way seems to be log onto the CMS and open the Cluster Administrator Use the "Get-ClusteredMailboxServerStatus" cmdlet. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Hi Rich Thanks for answering.. >Hi I have just created a CCR cluster on Windows 2003 Server. If I go to Cluster Administrator, I notice there are two Cluster Groups: ExchangeCCR: Exchange IS, System Attendant, First Storage Group, IP Address etc Cluster Group: Cluster IP Address, Cluster Name, Majority Node Set Could someone explain the difference between the two? >>One represents the CMS. The other the cluster and FSW. When you move the CMS to another node you should make sure the cluster group is moved with it. You are saying that if I move Exchange resources to another node, then I should also access the Cluster Manager and move the Cluster resources? What is the effect of not doing this? >Also, when I set the Cluster up, I had to enter an IP address and name for the Cluster, which was different to the CMS/address name. Should this have been the case? >>Yes. Managing the cluster isn't the same as accessing the CMS Still not sure what you mean here, what does the 'cluster' name/IP actually represent? Thanks again for answering.

On Thu, 21 Oct 2010 19:46:33 +0000, Neil4933 wrote: >Thanks for answering.. >>>Hi I have just created a CCR cluster on Windows 2003 Server. If I go to Cluster Administrator, I notice there are two Cluster Groups: ExchangeCCR: Exchange IS, System Attendant, First Storage Group, IP Address etc Cluster Group: Cluster IP Address, Cluster Name, Majority Node Set Could someone explain the difference between the two? >>One represents the CMS. The other the cluster and FSW. When you move the CMS to another node you should make sure the cluster group is moved with it. >You are saying that if I move Exchange resources to another node, then I should also access the Cluster Manager and move the Cluster resources? What is the effect of not doing this? Provided that the owner of the FSW doesn't disappear, nothing bad will happen. But why take that chance? >>>Also, when I set the Cluster up, I had to enter an IP address and name for the Cluster, which was different to the CMS/address name. Should this have been the case? >>Yes. Managing the cluster isn't the same as accessing the CMS >Still not sure what you mean here, what does the 'cluster' name/IP actually represent? The MNS cluster has nothing to do with Exchange. Managing the cluster, and the resources assigned to the cluster, should be independant of the resources that run on the cluster. So while Outlook and Exchange uses the CMS name, the MNS they run on should be managed independantly. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

Thanks Rich. One last question :) You mention it would be recommended to move the Windows Cluster Group resources when failing over, along with the Exchange resources. So just wanted to check if failing over was recommended to be a two step process (move Exchange resources using Exchange Management Console and then move Windows resources using Cluster Admin)? Alternatively, we could just reboot the active node and this would move *everything* over to the passive?

On Sun, 24 Oct 2010 09:37:11 +0000, Neil4933 wrote: >You mention it would be recommended to move the Windows Cluster Group resources when failing over, along with the Exchange resources. So just wanted to check if failing over was recommended to be a two step process (move Exchange resources using Exchange Management Console and then move Windows resources using Cluster Admin)? Yes, assuming that the cluster group wasn't already moved. Try this: http://www.expta.com/2009/06/failure-of-fsw-causes-cluster-group-to.html --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP