neil4933
asked on
Exchange CCR Cluster resources
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
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
suriyaehnop
check this out:http://www.msexchange.org/tutorials/Installing-Configuring-Testing-Exchange-2007-Cluster-Continuous-Replication-Based-Mailbox-Server-Part1.html
ASKER
Yes, I've seen that but it doesn't answer my questions?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Grobbs, well explained...
Just one further question - if I was to fail over the Exchange resources from one node to another, should I also fail over the Windows Cluster group resources? I notice that if I use the Exchange Management Console to fail over, it doesn't move the Windows Cluster Group. 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?
Just one further question - if I was to fail over the Exchange resources from one node to another, should I also fail over the Windows Cluster group resources? I notice that if I use the Exchange Management Console to fail over, it doesn't move the Windows Cluster Group. 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?
Yes, it's a two-step process to fail over the cluster, just as you said: Exchange Mgmt Console to move Exchange resources, and Cluster Aministrator to move Cluster Group. It is recommended that you move the Cluster Group resources as well when you want to fail over to the other node, although I don't believe that's strictly necessary. Everything will keep working with one group on one server and the other group on the other server. But then both servers are really active, and you'll have to eventually fail over part of the cluster when you do maintenance (install patches, etc.). You may as well just keep both groups on the same server, so that you KNOW you can safely work on the passive node.
This used to be a single step with Exchange 2003, where the Exchange resources could also be moved using Cluster Administrator, but not with Exchange 2007.
It is possible to fail over your entire cluster by rebooting, but that's not recommended. Rebooting relies on the passive node to notice that the active node is down, which involves a small time delay, and it is seen as a failure. It's cleaner to move the resources before rebooting.
This used to be a single step with Exchange 2003, where the Exchange resources could also be moved using Cluster Administrator, but not with Exchange 2007.
It is possible to fail over your entire cluster by rebooting, but that's not recommended. Rebooting relies on the passive node to notice that the active node is down, which involves a small time delay, and it is seen as a failure. It's cleaner to move the resources before rebooting.