|
Randy,
Check the archives for clustering. There has been a lot
of discussion on these topics, but I haven't seen anyone implement such a
configuration. due to the challenges involved:
1) File locking on shared storage devices (DAS, NAS &
SAN). All sorts of potential problems here. While most of the time
this may not be an issue, it's those rare exceptions that are difficult to
manage without getting unexpected results. This problem could be
significantly reduced if IMail's storage were block-level or record level
instead of file-level (as with most clustered solutions like Exchange, Domino /
Notes, and even opensource like Cyrus MURDER clusters).
2) System configuration management (must duplicate registry
settings between the two machines). Configured as the same IMail 'host',
or different hosts / same domain? Whatever mechanism you use to duplicate
settings will most likely involve working with the registry directly as only a
subset of those keys will need to be replicated. This becomes a
particular issue for user management where settings are stored in the
registry. Would you then have to create a registry replication engine
(event driven instead of batch)? This could be improved if Ipswitch would
open this up to an API that could be implemented on a shared DB backend (or
LDAP, or MS AD / ADAM - ADAM is cool by the way, the beta is very
interesting).
*** As our implementation is AD for integrated account
authentication, I would love to see Ipswitch make use of SQL, LDAP, or MS ADAM
for server configurations in an enterprise line of IMail.
3) So far as I know, the only way of effectively sharing user
authentication and information is via shared SQL tables between the IMail
servers. This binds you to a particular data store, unless using a
replacement LDAP DLL for the regular external DB mechanism (not really available
yet, although some are tinkering).
4) You need to have an intelligent load-balancer in order to
know if one of the servers has stopped functioning properly (not just simply
unavailable). With Linux LVS this is easy, but if you're running Linux why
not consider something like Cyrus in the first place?
The type of functionality I believe you are looking for can be
found in the following product (implemented with LDAP and *NIX).
You can get the same functionality out of Cyrus MURDER
clusters. Many larger universities are going this route because of the
cost / performance value.
Give it a shot and see how it works, I think a few of us are
curious to see what you come up with. Which iSCSI products were you
looking at?
-ives
|
Title: Message
- RE: [IMail Forum] upgr... Oblio
- RE: [IMail Forum] upgr... John Tolmachoff \(Lists\)
- RE: [IMail Forum] upgr... Oblio
- [IMail Forum] upgrd v6... Oblio
- RE: [IMail Forum] upgr... John Tolmachoff \(Lists\)
- RE: [IMail Forum] upgr... Oblio
- Re: [IMail Forum] Imail High Availability Setup Len Conrad
- Re: [IMail Forum] Imail High Availability S... Randy Leiker
- RE: [IMail Forum] Imail High Availabili... Charles Frolick
- Re: [IMail Forum] Imail High Availa... Randy Leiker
- Ives Stoddard
