I don't think its a case of "Fixing" anything as much as Exchange server being a
scenario where clustering generally offers a very poor return on the investment in
time and money you spend setting one up and tweaking it. Quite a lot of errors I've
seen with exchange relate to people doing stupid things and also to databases becoming
corrupted. Neither problem is especially solvable with clustering.
This is true of clustering no matter what platform you are clustering on and what
process you are trying to support with your cluster. Some things take to it like a
duck to beer, other applications are downright hostile to clustering environments, and
still more others don't give you much benefit from clustering one way or another
because they require a lot of tuning to run on a cluster and that app's major weakness
isn't something that is solved by a cluster.
Regards
Rob Moir
-----Original Message-----
From: Finch Brett [mailto:[EMAIL PROTECTED]
Sent: Thu 05/06/2003 17:38
To: Exchange Discussions
Cc:
Subject: RE: Real world experience
You mean you don't believe MS has fixed this in Exchange2K3 ? :) Thanks
-----Original Message-----
From: Hutchins, Mike [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2003 10:12
To: Exchange Discussions
Subject: RE: Real world experience
Friends don't let friends cluster Exchange...
(Am I sounding a little repetitive here? I seem to say that alot)
-----Original Message-----
From: Finch Brett [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 05, 2003 9:47 AM
To: Exchange Discussions
I will spare the gory 'political' details as we are in the midst of trying
to consolidate 35 '5.5' Exchange servers in 35 domains to as little servers
as possible. We're looking at an Exchange 2K3 rollout and probably a hybrid
AD using MS's meta directory (maybe). The real question is I am looking for
real world experience with something similar to what we are going to from a
Exchange 2K shop. Essentially we'll be looking at 5,000 users (.5 GB per
mailbox) to start with another 5,000 in phase 2 and 5,000 more in phase 3.
With a new 2K3 AD, we'll probably consider at least 2 DC's and one dedicated
server for OWA. The main mail servers and storage is really the number
cruncher. It's looking like a 3 server cluster and external storage (AV also
has to be factored). All client stations will be on at least 10 if not 100
switched lines, GB speed on the WAN backbone. I have gone to Dell and other
places to run the traditional load 'configuration wizard' and I have always
preferred to error on the side of you can never have too much power. I
would like to hear from people using SAN's or the like to account for TB
size storage and backup. How close was the configuration load wizards to
what you really required. Thanks
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&;
lang=english
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang
=english
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
_________________________________________________________________
List posting FAQ: http://www.swinc.com/resource/exch_faq.htm
Web Interface:
http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english
To unsubscribe: mailto:[EMAIL PROTECTED]
Exchange List admin: [EMAIL PROTECTED]
.+--xm
,)r( \ٖy'iǡ)l+-rrʸWZ{fץjx
b{.n+j)mWrl &!jx .+-i٢Xf{0y
