|
Currently we only put like servers in a cluster. For example we have three clusters: Cluster Member NOTES01CLUSTER NOTES01 NOTES02 LDAPCLUSTER LDAP01 LDAP02 SAMETIMECLUSTER SAMETIME01 SAMETIME02 We do clustering for failover reasons. The problem I am having is that users are strongly encouraged to change their internet passwords in the NAB on NOTES01 only. However, when they then access applications that use this internet password such as Sametime, or other web based applications using the LDAP server their password isn't synced yet. Does anyone not think that putting this all into one cluster is a good idea? Cluster Member NOTES01CLUSTER NOTES01 NOTES02 LDAP01 LDAP02 SAMETIME01 SAMETIME02 We would still control what databases get created on what server, and on which servers replica copies are made. I thought about doing connection documents between them all, specifying the replication of only names.nsf, and a short interval of just a few minutes. However, to a user, a few minutes is a lifetime. Rob Berendt -- "All creatures will make merry... under pain of death." -Ming the Merciless (Flash Gordon)
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.