| Author |
Message |
MoiToo
Guest
|
 Posted:
Mon Nov 07, 2005 8:50 am Post subject:
Newbie clustering question |
|
|
I am new to clusering in exchange (although have done NLB for other
services).
I want to:
1) Have redundant copies of mailboxes (or entire private stores). i.e.
Each store exists on each server within the cluster, and contains identical
data
2) That exchange std. cannot be part of a cluster (regardless of w2k3
ent/std windows)
I believe that replication of mailboxes is still not supported in exchange,
even in clusters/nlb without using 3rd party software - is this correct?
I also believe that exchange can be in NLB on std and ent versions of 2003
server, and be in genuine cluster only on enterprise - is this also correct?
Thanks
|
|
| Back to top |
|
 |
Bharat Suneja
Guest
|
| Posted:
Mon Nov 07, 2005 5:58 pm Post subject:
Re: Newbie clustering question |
|
|
1) Not possible to have redundant copies of mailboxes. Stores/volumes can be
replicated using 3rd party sw, Exchange 12 reported to have replication
2) Right, Exchange Std. Ed. cannot be part of a High Availability/MSCS
cluster, Ent only
3) Exchange and Windows Std. Edition can also do NLB
4) Cluster Services and NLB serve 2 different purposes.
Cluster Services (MSCS):
- 2 nodes (Win2K Adv) / 4 nodes (Win2K Datacenter) / 8 nodes (Windows Server
2003 Ent and Datacenter)
- Exchange Enterprise only
- shared storage, Stores reside on shared storage, no replication of stores
or load-balancing
- Clusters are used for mailbox (aka "back-end") servers.
- Only one node can host a particular "Exchange Virtual Server" at one time,
are failed over to other nodes in the cluster when the (then) active node
fails. EVS appears as an Exchange server in Exchange System Manager and to
users.
NLB (Network Load Balancing):
- 2 or more servers (up to 32) listen on a virtual IP address (as opposed to
presenting a virtual server to users and to Exchange management tools in
MSCS clusters)
- requests on particular port(s) setup to be load-balanced, are sent to any
of the servers in a NLB "cluster"
- As far as Exchange is concerned, NLB can be used to load-balance Front-End
servers. Exchange installed on all FEs in a NLB cluster, all show up in ESM
as separate servers and reachable individually
- Can do NLB on Std. Ed. as well
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:u8qihR04FHA.1148@tk2msftngp13.phx.gbl...
| Quote: | I am new to clusering in exchange (although have done NLB for other
services).
I want to:
1) Have redundant copies of mailboxes (or entire private stores). i.e.
Each store exists on each server within the cluster, and contains
identical data
2) That exchange std. cannot be part of a cluster (regardless of w2k3
ent/std windows)
I believe that replication of mailboxes is still not supported in
exchange, even in clusters/nlb without using 3rd party software - is this
correct?
I also believe that exchange can be in NLB on std and ent versions of 2003
server, and be in genuine cluster only on enterprise - is this also
correct?
Thanks
|
|
|
| Back to top |
|
|
MoiToo
Guest
|
| Posted:
Tue Nov 08, 2005 9:58 am Post subject:
Re: Newbie clustering question |
|
|
Thanks!
So if I understand, NLB are used as load balancing (duh!), and according to
ESM are individual servers (clients can access using virtual IP). This is
good for front-end only.
MSCS clusters are for backend servers, and appear to be only one server to
ESM (because there is only one physical database).
MSCS doesn't support load balancing - so its only purpose is for server
redundancy? If this is correct, would there be any (real) reason to use
more than 2 servers in a cluster?
There is no way I assume to have 2 MSCS clusers running in NLB (kind of like
RAID 10!)
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23Z4S6x64FHA.1416@TK2MSFTNGP09.phx.gbl...
| Quote: | 1) Not possible to have redundant copies of mailboxes. Stores/volumes can
be replicated using 3rd party sw, Exchange 12 reported to have replication
2) Right, Exchange Std. Ed. cannot be part of a High Availability/MSCS
cluster, Ent only
3) Exchange and Windows Std. Edition can also do NLB
4) Cluster Services and NLB serve 2 different purposes.
Cluster Services (MSCS):
- 2 nodes (Win2K Adv) / 4 nodes (Win2K Datacenter) / 8 nodes (Windows
Server 2003 Ent and Datacenter)
- Exchange Enterprise only
- shared storage, Stores reside on shared storage, no replication of
stores or load-balancing
- Clusters are used for mailbox (aka "back-end") servers.
- Only one node can host a particular "Exchange Virtual Server" at one
time, are failed over to other nodes in the cluster when the (then) active
node fails. EVS appears as an Exchange server in Exchange System Manager
and to users.
NLB (Network Load Balancing):
- 2 or more servers (up to 32) listen on a virtual IP address (as opposed
to presenting a virtual server to users and to Exchange management tools
in MSCS clusters)
- requests on particular port(s) setup to be load-balanced, are sent to
any of the servers in a NLB "cluster"
- As far as Exchange is concerned, NLB can be used to load-balance
Front-End servers. Exchange installed on all FEs in a NLB cluster, all
show up in ESM as separate servers and reachable individually
- Can do NLB on Std. Ed. as well
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:u8qihR04FHA.1148@tk2msftngp13.phx.gbl...
I am new to clusering in exchange (although have done NLB for other
services).
I want to:
1) Have redundant copies of mailboxes (or entire private stores).
i.e. Each store exists on each server within the cluster, and contains
identical data
2) That exchange std. cannot be part of a cluster (regardless of w2k3
ent/std windows)
I believe that replication of mailboxes is still not supported in
exchange, even in clusters/nlb without using 3rd party software - is this
correct?
I also believe that exchange can be in NLB on std and ent versions of
2003 server, and be in genuine cluster only on enterprise - is this also
correct?
Thanks
|
|
|
| Back to top |
|
|
Bharat Suneja
Guest
|
| Posted:
Tue Nov 08, 2005 4:51 pm Post subject:
Re: Newbie clustering question |
|
|
If you only want to create one EVS (i.e. "one Exchange server"), you only
need 2 nodes. The EVS is owned by one node at a time, called an active node,
and can failover to the passive node - a "active/passive" config.
You can also create 2 EVSes in a 2-node config - each node hosts an EVS.
This is known as an "active/active" config. If one node fails, the EVS
hosted on that node is failed over to the other node, which is also "active"
(it's hosting another EVS). It has severe limitations in scalability and
isn't recommended by Microsoft. Active/Active is only supported in 2-node
clusters.
In clusters with more than 2 nodes, the maximum number of EVSes is n-1,
where n is number of nodes. No node can host more than 1 EVS at a time.
Docs:
Technical Overview of Windows Server 2003 Clustering Services
http://www.microsoft.com/windowsserver2003/techinfo/overview/clustering.mspx
Planning for Exchange Clustering
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3HighAvGuide/99353155-7908-4d44-a609-48199919f188.mspx
Deploying Exchange Server 2003 in a Cluster (Exchange Server Deployment
Guide)
http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/9f5b91cd-d7c2-409d-81a0-033a23e1faee.mspx
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:e8cD3VE5FHA.1140@tk2msftngp13.phx.gbl...
| Quote: | Thanks!
So if I understand, NLB are used as load balancing (duh!), and according
to ESM are individual servers (clients can access using virtual IP). This
is good for front-end only.
MSCS clusters are for backend servers, and appear to be only one server to
ESM (because there is only one physical database).
MSCS doesn't support load balancing - so its only purpose is for server
redundancy? If this is correct, would there be any (real) reason to use
more than 2 servers in a cluster?
There is no way I assume to have 2 MSCS clusers running in NLB (kind of
like RAID 10!)
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23Z4S6x64FHA.1416@TK2MSFTNGP09.phx.gbl...
1) Not possible to have redundant copies of mailboxes. Stores/volumes can
be replicated using 3rd party sw, Exchange 12 reported to have
replication
2) Right, Exchange Std. Ed. cannot be part of a High Availability/MSCS
cluster, Ent only
3) Exchange and Windows Std. Edition can also do NLB
4) Cluster Services and NLB serve 2 different purposes.
Cluster Services (MSCS):
- 2 nodes (Win2K Adv) / 4 nodes (Win2K Datacenter) / 8 nodes (Windows
Server 2003 Ent and Datacenter)
- Exchange Enterprise only
- shared storage, Stores reside on shared storage, no replication of
stores or load-balancing
- Clusters are used for mailbox (aka "back-end") servers.
- Only one node can host a particular "Exchange Virtual Server" at one
time, are failed over to other nodes in the cluster when the (then)
active node fails. EVS appears as an Exchange server in Exchange System
Manager and to users.
NLB (Network Load Balancing):
- 2 or more servers (up to 32) listen on a virtual IP address (as opposed
to presenting a virtual server to users and to Exchange management tools
in MSCS clusters)
- requests on particular port(s) setup to be load-balanced, are sent to
any of the servers in a NLB "cluster"
- As far as Exchange is concerned, NLB can be used to load-balance
Front-End servers. Exchange installed on all FEs in a NLB cluster, all
show up in ESM as separate servers and reachable individually
- Can do NLB on Std. Ed. as well
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:u8qihR04FHA.1148@tk2msftngp13.phx.gbl...
I am new to clusering in exchange (although have done NLB for other
services).
I want to:
1) Have redundant copies of mailboxes (or entire private stores).
i.e. Each store exists on each server within the cluster, and contains
identical data
2) That exchange std. cannot be part of a cluster (regardless of w2k3
ent/std windows)
I believe that replication of mailboxes is still not supported in
exchange, even in clusters/nlb without using 3rd party software - is
this correct?
I also believe that exchange can be in NLB on std and ent versions of
2003 server, and be in genuine cluster only on enterprise - is this also
correct?
Thanks
|
|
|
| Back to top |
|
|
MoiToo
Guest
|
| Posted:
Wed Nov 09, 2005 9:58 am Post subject:
Re: Newbie clustering question |
|
|
Thank you very much - very helpful, and most interesting.
"Bharat Suneja" <bharatsuneja@no.spam.org> wrote in message
news:eOK7oJF5FHA.1000@tk2msftngp13.phx.gbl...
| Quote: | If you only want to create one EVS (i.e. "one Exchange server"), you only
need 2 nodes. The EVS is owned by one node at a time, called an active
node, and can failover to the passive node - a "active/passive" config.
You can also create 2 EVSes in a 2-node config - each node hosts an EVS.
This is known as an "active/active" config. If one node fails, the EVS
hosted on that node is failed over to the other node, which is also
"active" (it's hosting another EVS). It has severe limitations in
scalability and isn't recommended by Microsoft. Active/Active is only
supported in 2-node clusters.
In clusters with more than 2 nodes, the maximum number of EVSes is n-1,
where n is number of nodes. No node can host more than 1 EVS at a time.
Docs:
Technical Overview of Windows Server 2003 Clustering Services
http://www.microsoft.com/windowsserver2003/techinfo/overview/clustering.mspx
Planning for Exchange Clustering
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3HighAvGuide/99353155-7908-4d44-a609-48199919f188.mspx
Deploying Exchange Server 2003 in a Cluster (Exchange Server Deployment
Guide)
http://www.microsoft.com/technet/prodtechnol/exchange/guides/Ex2k3DepGuide/9f5b91cd-d7c2-409d-81a0-033a23e1faee.mspx
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------------
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:e8cD3VE5FHA.1140@tk2msftngp13.phx.gbl...
Thanks!
So if I understand, NLB are used as load balancing (duh!), and according
to ESM are individual servers (clients can access using virtual IP).
This is good for front-end only.
MSCS clusters are for backend servers, and appear to be only one server
to ESM (because there is only one physical database).
MSCS doesn't support load balancing - so its only purpose is for server
redundancy? If this is correct, would there be any (real) reason to use
more than 2 servers in a cluster?
There is no way I assume to have 2 MSCS clusers running in NLB (kind of
like RAID 10!)
"Bharat Suneja" <bharat@nospam.org> wrote in message
news:%23Z4S6x64FHA.1416@TK2MSFTNGP09.phx.gbl...
1) Not possible to have redundant copies of mailboxes. Stores/volumes
can be replicated using 3rd party sw, Exchange 12 reported to have
replication
2) Right, Exchange Std. Ed. cannot be part of a High Availability/MSCS
cluster, Ent only
3) Exchange and Windows Std. Edition can also do NLB
4) Cluster Services and NLB serve 2 different purposes.
Cluster Services (MSCS):
- 2 nodes (Win2K Adv) / 4 nodes (Win2K Datacenter) / 8 nodes (Windows
Server 2003 Ent and Datacenter)
- Exchange Enterprise only
- shared storage, Stores reside on shared storage, no replication of
stores or load-balancing
- Clusters are used for mailbox (aka "back-end") servers.
- Only one node can host a particular "Exchange Virtual Server" at one
time, are failed over to other nodes in the cluster when the (then)
active node fails. EVS appears as an Exchange server in Exchange System
Manager and to users.
NLB (Network Load Balancing):
- 2 or more servers (up to 32) listen on a virtual IP address (as
opposed to presenting a virtual server to users and to Exchange
management tools in MSCS clusters)
- requests on particular port(s) setup to be load-balanced, are sent to
any of the servers in a NLB "cluster"
- As far as Exchange is concerned, NLB can be used to load-balance
Front-End servers. Exchange installed on all FEs in a NLB cluster, all
show up in ESM as separate servers and reachable individually
- Can do NLB on Std. Ed. as well
--
Bharat Suneja
MCSE, MCT
www.zenprise.com
blog: www.suneja.com/blog
-----------------------------------
"MoiToo" <newsgroups@dodo.com.au> wrote in message
news:u8qihR04FHA.1148@tk2msftngp13.phx.gbl...
I am new to clusering in exchange (although have done NLB for other
services).
I want to:
1) Have redundant copies of mailboxes (or entire private stores).
i.e. Each store exists on each server within the cluster, and contains
identical data
2) That exchange std. cannot be part of a cluster (regardless of
w2k3 ent/std windows)
I believe that replication of mailboxes is still not supported in
exchange, even in clusters/nlb without using 3rd party software - is
this correct?
I also believe that exchange can be in NLB on std and ent versions of
2003 server, and be in genuine cluster only on enterprise - is this
also correct?
Thanks
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in