[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Failover and circular replication
Hello,
We want to set up multiple replication servers. We know that slapd 2.1
is able to manage a simple master-slave replication using slurpd.
But we need a more advanced setup, we want to have load balancing and a
failover solution. This means that clients must be able to send updates
to every server (there should be no dedicated master), and that any of
the servers should be "allowed" to fail for some time and catch up
later.
Is this possible by setting up multiple replication rules making every
server replicating to every other? Or will we create update loops this
way? (As I understand, the replication log contains timestamps, so it
should be possible by slurpd/slapd to achieve this goal, but I don't
know whether it is implemented in such a way.)
The docs are rather sparse wr/t replication. For the first step, we just
want to know whether this is the correct way to go before we spend weeks
with experiments.
Thanks,
Markus
--
-----------------------------------------------------------------------
| ScanPlus GmbH NOC Ulm Tel +49 731 92013 106 |
| Koenigstr. 78 * D 89077 Ulm Fax +49 731 92013 290 |
| http://www.scan-plus.de/ Amtsgericht Ulm HRB 3220 |
| mailto:info@scan-plus.de Geschaeftsf.: Juergen Hoermann |
-----------------------------------------------------------------------
Diese E-Mail koennte vertrauliche und/oder rechtlich geschuetzte
Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort
den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren
sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
-----------------------------------------------------------------------
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail
in error) please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.
-----------------------------------------------------------------------