Hi Everyone
I am looking for some good advice on Exchange clustering. To give you some background
information..
SYSTEM SETUP
3 x Exchange 5.5 SP4 systems running in the same org and site:
Sever 1 IMC PRIV and PUB Stores
Server 2 PRIV Store
Server 3 PRIV Store
MY OBJECTIVE
Migrate Server 1 to a Highly Available Exchange cluster which should support a
concurrent userbase of 850 users and storage to support a userbase of 1000 users with
a 200MB quota.
Sever 1 is already attached to a Compaq SAN via Fibre Channel so the diskspace is not
a problem.
ADVICE:
Basically I can see three options, and with these options are pro's and cons..
Option 1 Run Exchange 5.5 on an NT4.0 cluster
Pros
The exchange system can be installed into the same site and the users can be simply
migrated to the new Highly Available (HA) system.
No change to global System layout
Cons
To upgrade from e5.5 to e2k there may be issues with doing a rolling upgrade on the
cluster.. I am no expert on performing a rolling upgrade on Exchange or win2k
Option 2 Run Exchange 5.5 on a W2k Cluster
Pros
The exchange org layout doesn't get changed and the users can be migrated
The cluster is running under w2k and can take advantage of the newer clustering / load
balancing technologies
Cons
There could be stabiltiy problems with running e5.5 on a w2k system (once again I have
never done this) with patches etc
Migration issues ??
Option 3 Migrate to ek2 and run a cluster
Pros
Org is running in full AD evironment and w2k cluster technologies
Cons
Have to migrate to w2k/ads before even attempting to migrate to e2k.
ADS implementation will take time and money
SoooOOo yeah there it is :) I would like to hear from anyone who has done or is in the
process of doing anything similar to what I am trying to acheive.
Thanks in advance
Dan Yarrow
NT/2000 Systems Administrator
Central Queensland University
Information Technology Division
Email: [EMAIL PROTECTED]
Ph: +61 7 4923 2151
Fax +61 7 4930 9254
List Charter and FAQ at:
http://www.sunbelt-software.com/exchange_list_charter.htm
