MikeO
Thu May 08 13:12:00 CDT 2008
Thanks. I think I'll just leave things as they are and use a script..
"Bharat Suneja [MSFT]" wrote:
> It's not supported to have Exchange resources in the cluster group.
> Resources will fail to come online because multiple Network Name resources
> exist in the group.
>
> See
http://technet.microsoft.com/en-us/library/bb123996(EXCHG.80).aspx:
>
> "Do not install, create, or move any resources from the default cluster
> group to the resource group containing the clustered mailbox server. In
> addition, do not install, create, or move any resources from the group
> containing the clustered mailbox server to the default cluster group. The
> default cluster group should contain only the cluster IP Address, Network
> Name, and quorum resources. Moving or combining resources to or with the
> default cluster group is not supported."
> --
> Bharat Suneja
> Microsoft Corporation
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
> ----------------------------
>
> "Andy David {MVP}" <adavid@pleasekeepinngcheesebucket.com> wrote in message
> news:dpq524t2j6usotfoi2v9kscjldbtgt6bvb@4ax.com...
> > On Wed, 7 May 2008 22:09:48 -0400, "Mike O" <put_the_spam@the.can>
> > wrote:
> >
> >>Thanks, I'll look into setting up a script.
> >>
> >>Just curious, why would it be "intended to be separate"? What would be
> >>the
> >>situation when you would want the Exchange mailboxes to be active on one
> >>node, but the management items to be on the other node?
> >
> > Because the windows clustering services are separate from the Exchange
> > clustering services :) Dont think it was intentional as much as the
> > Exch stuff is newer and designed separately. I cant think of any time
> > when you would want them active on seperate nodes except for testing,
> > but thats the way it is.
> >
> >
> >>
> >>Mainly it when I need to do work on a server (updates, etc.) and I want to
> >>fail it over to the inactive node. I was looking for a simple way to
> >>switch
> >>all the resources at once instead of going to the Exchange console for the
> >>Exchange items, then cluster admin for the other group. The shell script
> >>sounds like what I'm looking for.
> >
> > Script yes :) Of course, moving the Windows cluster takes but a few
> > seconds and no one notices.
> >
> >
> >
> >
> >>
> >>
> >>"Bharat Suneja [MSFT]" <bsuneja@online.microsoft.com> wrote in message
> >>news:O$9V4UAsIHA.3456@TK2MSFTNGP05.phx.gbl...
> >>> Both groups are intended to be separate. A (resource) group is a unit of
> >>> failover. The cluster group provides a connection point (network name,
> >>> ip
> >>> address) to manage the cluster, and owns the quorum.
> >>>
> >>> You can invoke both commands (1. move-clusteredmailboxserver and 2.
> >>> cluster group "CLUSTERGROUPNAME" /move "NODE NAME") from a single shell
> >>> script, if that helps.
> >>> --
> >>> Bharat Suneja
> >>> Microsoft Corporation
> >>> ------------------------
> >>> This posting is provided "AS IS" with no warranties, and confers no
> >>> rights. Please do not send email directly to this alias. This alias is
> >>> for
> >>> newsgroup purposes only.
> >>>
> >>>
> >>> "Mike O" <put_the_spam@the.can> wrote in message
> >>> news:OO68AF$rIHA.2068@TK2MSFTNGP05.phx.gbl...
> >>>>I have a new Windows 2007 setup with two mailbox servers (Windows 2003
> >>>>R2
> >>>>x64) in a CCR/Minority node set cluster with file share witness and I
> >>>>have
> >>>>a question about the cluster group. The servers only have a few users
> >>>>on
> >>>>it at this time, but we're getting ready to start migrating our existing
> >>>>users from our 2003 system.
> >>>>
> >>>> The mailbox cluster is called EXMBC1. The two nodes are EXMBC1a and
> >>>> EXMBC1b (these are not the real names).
> >>>> The cluster admin shows two groups, the "EXMBC1" group with all the
> >>>> Exchange stuff in it, and the "Cluster Group" with the name and IP of
> >>>> the
> >>>> management name (EXMBC1M), and the MNS witness resource.
> >>>>
> >>>> When we do a manual failover of the Exchange group (from the Exchanage
> >>>> console and/or management shell), the Exchange group switches to the
> >>>> other node, but the cluster management IP and name stay on the original
> >>>> server (unless I move it from the Cluster Admin)
> >>>>
> >>>> What I'm trying to find out is if I can put the "cluster group"
> >>>> resources
> >>>> in the Exchange mailbox cluster group so that if I do a manual failover
> >>>> of the Exchange group, the "cluster group" fails over too.
> >>>>
> >>>> Any suggestions would be appreciated.
> >>>>
> >>>> Mike O.
> >>>
>
>