| Author |
Message |
SM
Guest
|
 Posted:
Wed Dec 01, 2004 4:44 am Post subject:
Exchange 2k3 cluster as your only BackEnd? |
|
|
Are there any known problems running an Exchange 2003 cluster as your only
Back End server?
Currently we are planning on having 2 FE servers and 1 A/P Backend cluster.
I know you can't have connectors and such on a cluster, but in reading "The
Experts Guide for Exchange 2003" (free from Quest Software - Google for it
if you want) the author mentions that the following should not be installed
on a cluster:
Recipient Update Service
Routing Group Master
System Public folders
In a paragraph about installing the the first Ex2003 server he says the
following:
"Some roles, such as the Recipient Update Service (RUS), Routing Group
Master, and system public folder server are assumed for the first server and
don't work correctly in a clustered environment." (ch.4 page68)
He doesn't go on to say why they don't work correctly, but it got me a
little worried. Will we need an additional stand alone BE server to support
these roles or are they okay running on a cluster?
Thanks in advance for any feedback.
-SM
|
|
| Back to top |
|
 |
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Wed Dec 01, 2004 5:05 am Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
Answer inline below...
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"SM" <sm@mail.org> wrote in message
news:erwMh4y1EHA.3504@TK2MSFTNGP12.phx.gbl...
| Quote: | Are there any known problems running an Exchange 2003 cluster as your only
Back End server?
|
If you can afford and understand the value of clustering. You can afford and
understand the need to have a FE server or two :) That said, since below you
mention having FE's, the backend can indeed only be clusters. As long as 5.5
is not involved in the mix.
| Quote: |
Currently we are planning on having 2 FE servers and 1 A/P Backend
cluster.
I know you can't have connectors and such on a cluster, but in reading
"The
Experts Guide for Exchange 2003" (free from Quest Software - Google for it
if you want) the author mentions that the following should not be
installed
on a cluster:
Recipient Update Service
Routing Group Master
System Public folders
In a paragraph about installing the the first Ex2003 server he says the
following:
"Some roles, such as the Recipient Update Service (RUS), Routing Group
Master, and system public folder server are assumed for the first server
and
don't work correctly in a clustered environment." (ch.4 page68)
|
This is simply not true. I think they meant Server Replication Service
(SRS).
The RUS can run anywhere.
Routing Groups are like sites, any server can be the master, cluster or not.
FE's typically don't have a Public Folder store.
| Quote: |
He doesn't go on to say why they don't work correctly, but it got me a
little worried. Will we need an additional stand alone BE server to
support
these roles or are they okay running on a cluster?
Thanks in advance for any feedback.
-SM
|
|
|
| Back to top |
|
|
Russ Kaufmann [MCT]
Guest
|
| Posted:
Wed Dec 01, 2004 6:39 am Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:%23grXNEz1EHA.3236@TK2MSFTNGP15.phx.gbl...
| Quote: | Are there any known problems running an Exchange 2003 cluster as your
only
Back End server?
If you can afford and understand the value of clustering. You can afford
and understand the need to have a FE server or two :) That said, since
below you mention having FE's, the backend can indeed only be clusters. As
long as 5.5 is not involved in the mix.
|
Or unless you have the need for IMF or some other service that won't run on
a cluster. I have worked with many companies that have only FEs and
clustered BEs.
| Quote: | Currently we are planning on having 2 FE servers and 1 A/P Backend
cluster.
I know you can't have connectors and such on a cluster, but in reading
"The
Experts Guide for Exchange 2003" (free from Quest Software - Google for
it
if you want) the author mentions that the following should not be
installed
on a cluster:
Recipient Update Service
Routing Group Master
System Public folders
In a paragraph about installing the the first Ex2003 server he says the
following:
"Some roles, such as the Recipient Update Service (RUS), Routing Group
Master, and system public folder server are assumed for the first server
and
don't work correctly in a clustered environment." (ch.4 page68)
This is simply not true. I think they meant Server Replication Service
(SRS).
The RUS can run anywhere.
|
mmmm, I am pretty sure we hit this earlier. I think I will have to disagree
with you, Rod, it can't be an FE and I am pretty sure there are problems
with it on a cluster. Remember when Evan Dodds backed me up by stating:
"Whoa, wait a sec. I'm not sure how KB.313646 didn't address this question.
Here's what it says:"
"...In this situation, the following services no longer run on the Exchange
Server computer that is defined as a front-end server: . DSProxy
. Offline Address List Generation
. Recipient Update Service
. Free and Busy Tasks
. Mailbox Cleanup Agent
. The Event Service
. Site Replication Service (SRS)"
|
|
| Back to top |
|
|
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Wed Dec 01, 2004 9:36 am Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
My mailbox resides on a cluster. The clustered nodes run the RUS. Trust me
it works just fine on the BE.
Rod
"Russ Kaufmann [MCT]" <russ@exchangemct.nospam.com> wrote in message
news:eE3JD4z1EHA.2156@TK2MSFTNGP10.phx.gbl...
| Quote: | "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:%23grXNEz1EHA.3236@TK2MSFTNGP15.phx.gbl...
Are there any known problems running an Exchange 2003 cluster as your
only
Back End server?
If you can afford and understand the value of clustering. You can afford
and understand the need to have a FE server or two :) That said, since
below you mention having FE's, the backend can indeed only be clusters.
As long as 5.5 is not involved in the mix.
Or unless you have the need for IMF or some other service that won't run
on a cluster. I have worked with many companies that have only FEs and
clustered BEs.
Currently we are planning on having 2 FE servers and 1 A/P Backend
cluster.
I know you can't have connectors and such on a cluster, but in reading
"The
Experts Guide for Exchange 2003" (free from Quest Software - Google for
it
if you want) the author mentions that the following should not be
installed
on a cluster:
Recipient Update Service
Routing Group Master
System Public folders
In a paragraph about installing the the first Ex2003 server he says the
following:
"Some roles, such as the Recipient Update Service (RUS), Routing Group
Master, and system public folder server are assumed for the first server
and
don't work correctly in a clustered environment." (ch.4 page68)
This is simply not true. I think they meant Server Replication Service
(SRS).
The RUS can run anywhere.
mmmm, I am pretty sure we hit this earlier. I think I will have to
disagree with you, Rod, it can't be an FE and I am pretty sure there are
problems with it on a cluster. Remember when Evan Dodds backed me up by
stating:
"Whoa, wait a sec. I'm not sure how KB.313646 didn't address this
question.
Here's what it says:"
"...In this situation, the following services no longer run on the
Exchange
Server computer that is defined as a front-end server: . DSProxy
. Offline Address List Generation
. Recipient Update Service
. Free and Busy Tasks
. Mailbox Cleanup Agent
. The Event Service
. Site Replication Service (SRS)"
|
|
|
| Back to top |
|
|
SM
Guest
|
| Posted:
Thu Dec 02, 2004 12:27 am Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
Thank you both for the feedback!
-SM
"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:%23t8Dyb11EHA.3340@TK2MSFTNGP10.phx.gbl...
| Quote: | My mailbox resides on a cluster. The clustered nodes run the RUS. Trust me
it works just fine on the BE.
Rod
"Russ Kaufmann [MCT]" <russ@exchangemct.nospam.com> wrote in message
news:eE3JD4z1EHA.2156@TK2MSFTNGP10.phx.gbl...
"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:%23grXNEz1EHA.3236@TK2MSFTNGP15.phx.gbl...
Are there any known problems running an Exchange 2003 cluster as your
only
Back End server?
If you can afford and understand the value of clustering. You can
afford
and understand the need to have a FE server or two :) That said, since
below you mention having FE's, the backend can indeed only be clusters.
As long as 5.5 is not involved in the mix.
Or unless you have the need for IMF or some other service that won't run
on a cluster. I have worked with many companies that have only FEs and
clustered BEs.
Currently we are planning on having 2 FE servers and 1 A/P Backend
cluster.
I know you can't have connectors and such on a cluster, but in reading
"The
Experts Guide for Exchange 2003" (free from Quest Software - Google
for
it
if you want) the author mentions that the following should not be
installed
on a cluster:
Recipient Update Service
Routing Group Master
System Public folders
In a paragraph about installing the the first Ex2003 server he says
the
following:
"Some roles, such as the Recipient Update Service (RUS), Routing Group
Master, and system public folder server are assumed for the first
server
and
don't work correctly in a clustered environment." (ch.4 page68)
This is simply not true. I think they meant Server Replication Service
(SRS).
The RUS can run anywhere.
mmmm, I am pretty sure we hit this earlier. I think I will have to
disagree with you, Rod, it can't be an FE and I am pretty sure there are
problems with it on a cluster. Remember when Evan Dodds backed me up by
stating:
"Whoa, wait a sec. I'm not sure how KB.313646 didn't address this
question.
Here's what it says:"
"...In this situation, the following services no longer run on the
Exchange
Server computer that is defined as a front-end server: . DSProxy
. Offline Address List Generation
. Recipient Update Service
. Free and Busy Tasks
. Mailbox Cleanup Agent
. The Event Service
. Site Replication Service (SRS)"
|
|
|
| Back to top |
|
|
Evan Dodds [MSFT]
Guest
|
| Posted:
Thu Dec 02, 2004 12:28 am Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
I think we're all talking about two different things here...
FE != Cluster.
FE servers have non-supported components (including the RUS) listed in
KB.313646.
Cluster servers have non-supported components listed in KB.259197.
The Cluster article is written from a slightly different perspective and
doesn't mention the RUS (presumably since it's not an independent
component -- it doesn't mention the SRS either), but rest assured it works
fine on cluster. :)
--
Evan Dodds
Microsoft Exchange Support
****** Disclaimer ******
This posting is provided "AS IS" with no warranties, and confers no rights.
Note: Please do not reply to this e-mail address. It is used for newsgroup
purposes only.
"Russ Kaufmann [MCT]" <russ@exchangemct.nospam.com> wrote in message
news:eE3JD4z1EHA.2156@TK2MSFTNGP10.phx.gbl...
| Quote: | "Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:%23grXNEz1EHA.3236@TK2MSFTNGP15.phx.gbl...
Are there any known problems running an Exchange 2003 cluster as your
only
Back End server?
If you can afford and understand the value of clustering. You can afford
and understand the need to have a FE server or two :) That said, since
below you mention having FE's, the backend can indeed only be clusters.
As long as 5.5 is not involved in the mix.
Or unless you have the need for IMF or some other service that won't run
on a cluster. I have worked with many companies that have only FEs and
clustered BEs.
Currently we are planning on having 2 FE servers and 1 A/P Backend
cluster.
I know you can't have connectors and such on a cluster, but in reading
"The
Experts Guide for Exchange 2003" (free from Quest Software - Google for
it
if you want) the author mentions that the following should not be
installed
on a cluster:
Recipient Update Service
Routing Group Master
System Public folders
In a paragraph about installing the the first Ex2003 server he says the
following:
"Some roles, such as the Recipient Update Service (RUS), Routing Group
Master, and system public folder server are assumed for the first server
and
don't work correctly in a clustered environment." (ch.4 page68)
This is simply not true. I think they meant Server Replication Service
(SRS).
The RUS can run anywhere.
mmmm, I am pretty sure we hit this earlier. I think I will have to
disagree with you, Rod, it can't be an FE and I am pretty sure there are
problems with it on a cluster. Remember when Evan Dodds backed me up by
stating:
"Whoa, wait a sec. I'm not sure how KB.313646 didn't address this
question.
Here's what it says:"
"...In this situation, the following services no longer run on the
Exchange
Server computer that is defined as a front-end server: . DSProxy
. Offline Address List Generation
. Recipient Update Service
. Free and Busy Tasks
. Mailbox Cleanup Agent
. The Event Service
. Site Replication Service (SRS)"
|
|
|
| Back to top |
|
|
Russ Kaufmann [MCT]
Guest
|
| Posted:
Thu Dec 02, 2004 10:48 pm Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
"Evan Dodds [MSFT]" <evand@online.microsoft.com> wrote in message
news:%23SE6NO91EHA.1204@TK2MSFTNGP10.phx.gbl...
| Quote: | I think we're all talking about two different things here...
FE != Cluster.
FE servers have non-supported components (including the RUS) listed in
KB.313646.
Cluster servers have non-supported components listed in KB.259197.
The Cluster article is written from a slightly different perspective and
doesn't mention the RUS (presumably since it's not an independent
component -- it doesn't mention the SRS either), but rest assured it works
fine on cluster. :)
|
Thank you for the response.
I have seen, first hand, a couple of clusters where RUS would not work. In
each case, calls to PSS resulted in, "Sorry, but you will probably have to
install it on a separate server" answers.
Thanks again. |
|
| Back to top |
|
|
Rodney R. Fournier [MVP]
Guest
|
| Posted:
Thu Dec 02, 2004 10:55 pm Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
Come on down to Huntsville, Alabama and turn NASA with me bud. I will prove
to you that it works on the Windows Exchange Server 2003 cluster, against a
Windows Server 2003 DC.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering
http://msmvps.com/clustering - Blog
"Russ Kaufmann [MCT]" <russ@exchangemct.nospam.com> wrote in message
news:%23tUHV6I2EHA.4028@TK2MSFTNGP15.phx.gbl...
| Quote: | "Evan Dodds [MSFT]" <evand@online.microsoft.com> wrote in message
news:%23SE6NO91EHA.1204@TK2MSFTNGP10.phx.gbl...
I think we're all talking about two different things here...
FE != Cluster.
FE servers have non-supported components (including the RUS) listed in
KB.313646.
Cluster servers have non-supported components listed in KB.259197.
The Cluster article is written from a slightly different perspective and
doesn't mention the RUS (presumably since it's not an independent
component -- it doesn't mention the SRS either), but rest assured it
works fine on cluster. :)
Thank you for the response.
I have seen, first hand, a couple of clusters where RUS would not work. In
each case, calls to PSS resulted in, "Sorry, but you will probably have to
install it on a separate server" answers.
Thanks again.
|
|
|
| Back to top |
|
|
Russ Kaufmann [MCT]
Guest
|
| Posted:
Fri Dec 03, 2004 2:37 am Post subject:
Re: Exchange 2k3 cluster as your only BackEnd? |
|
|
"Rodney R. Fournier [MVP]" <rod@die.spam.die.nw-america.com> wrote in
message news:uYv06%23I2EHA.2156@TK2MSFTNGP10.phx.gbl...
| Quote: | Come on down to Huntsville, Alabama and turn NASA with me bud. I will
prove to you that it works on the Windows Exchange Server 2003 cluster,
against a Windows Server 2003 DC.
|
Alabama? No way. <G>
But, I do believe you that it works there. I have seen it work in other
places, too. I have also seen it not work in other places. Perhaps it just
needed a better admin. <G> |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in