Title: Message
Eric,
We are
running E2K SP2 in an active/active cluster with TrenMicro 6.0. We are not
seeing any issues in our logs. I just went back through to double
check.
--kev
Kevin
Violette
UNCW
-Original Message-From: Sabo, Eric
[mailto:[EMAIL PROTECTED]]Sent:
Title: Message
We had
the same problem here. Upgraded the firmware and drivers and have not seen
it since. Thought the firmware flash and driver update was not as
"straight forward" as the instructions stated. It took a couple of tries
to get the procedure right.
Kevin
-Original
Title: Message
Also
after the firmware flash, powerdown the box not just a
reboot.
-Original Message-From: MHR(Michael Ross)
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002 3:11
PMTo: MS-Exchange Admin IssuesSubject: RE:
datbase
Ive
found my drivers were
Title: Message
We did
not run into any data loss.
Kevin
-Original Message-From: Zangara, Jim
[mailto:[EMAIL PROTECTED]]Sent: Wednesday, March 27, 2002
2:48 PMTo: MS-Exchange Admin IssuesSubject: RE:
datbase
bet this is what caused
my corruption as well.
When the
Title: Message
I
fully understand the management by rag routine. And related the known (to
me) limitations of clusters both active/active and active/passive. But we
got the active/active cluster. Currently the processors are well under the
40% (only 700 users currently).
How
ever the
Title: Message
Well
hellI'veread the XchSP2cl doc a few time in the past (unfortunately),
and that the 1900 concurrent users per node never made it to my brain.
Time to re-read. The good thing is that y'all brought this to my
attention. Also the vast majority of the 15000 users is a 2nd
Title: Message
Yep...already entered the thinkinghowever most are using a "webmail"
client (IMAP over web), the administrative push is OWA for most of the
interaction. Or using the current "rather lite" webmail via IMAP to the
student mbx.
just
need to do some rethinking, reading,
Title: Message
We
have been using the active/active cluster for about a year now and are going
though a VERY controlled migration to Exchange from VMS so the Ex5.5 to E2K
hurdles were not an issue. Most of the issues came from the front-end
back-end setup and not the cluster setup. I think
