Mark Crispin writes:
> Unlike the NFS monolith, we have no single point of failure that loses the
> entire IMAP service. The worst case scenario is that a small percentage
> of the user community is temporarily (a matter of minutes) offline while
> we deploy a replacement.
A quick procedure question - how do you do this? I understand how
you spread users across servers via DNS, etc., but what happens to the data
of users on that down server? Assuming it's more that a simple hang/ reboot
problem, do you move the hard drives to the replacement system, share via
SAN, reload from backup, etc? Also, approximately how many servers do you
have for your 80,000 (?) email users.
And how does an organization phase from a "mail.lehigh.edu" to
"user.m.lehigh.edu" structure without a lot of pain? It would have been
simple 8 years ago with <100 IMAP users. Now...
Thanks,
Steve
----------------------------------------------------------------------------
Steve Roseman
Lehigh University Computing Center
[EMAIL PROTECTED]
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
