Hi all,
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them: 1 - Master Server -> "hub" Server -> Slave Server 2 - Server1 <-> Server2 <-> Server 3
An other question: Is the replication with slurpd or SyncREPL supported over WAN ? Are there some restrictions ?
Rgds, Bruno.
<quote who="Bruno Lezoray EMSM">
Hi all,
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them: 1 - Master Server -> "hub" Server -> Slave Server
Expand on what you mean by "hub"?
2 - Server1 <-> Server2 <-> Server 3
This looks like Multi-Master?
An other question: Is the replication with slurpd or SyncREPL supported over WAN ?
Yes, but please try to use Syncrepl over slurpd
Are there some restrictions ?
Firewall/routing etc. Depends what you have setup/require.
Gavin.
Rgds, Bruno.
Gavin Henry wrote:
<quote who="Bruno Lezoray EMSM">
Hi all,
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them: 1 - Master Server -> "hub" Server -> Slave Server
Expand on what you mean by "hub"?
Hub comes from Sun Directory Server terminology which means a read-only server that receives/get updates to/from a master and send updates to a slave
2 - Server1 <-> Server2 <-> Server 3
This looks like Multi-Master?
Yes, except that Server1 isn't directly synchronized with Server3
An other question: Is the replication with slurpd or SyncREPL supported over WAN ?
Yes, but please try to use Syncrepl over slurpd
Are there some restrictions ?
Firewall/routing etc. Depends what you have setup/require.
Of course, these points must be configured correctly but, i supposed typically latency issues due to the distance or connection closed by a firewall due to inactivity.
Gavin.
Rgds, Bruno.
<quote who="Bruno Lezoray EMSM">
Gavin Henry wrote:
<quote who="Bruno Lezoray EMSM">
Hi all,
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them: 1 - Master Server -> "hub" Server -> Slave Server
Expand on what you mean by "hub"?
Hub comes from Sun Directory Server terminology which means a read-only server that receives/get updates to/from a master and send updates to a slave
Ah, a proxy. In our case that would be pushed based Syncrepl (slapd-ldap(8) and Syncrepl in refreshAndPersist mode).
2 - Server1 <-> Server2 <-> Server 3
This looks like Multi-Master?
Yes, except that Server1 isn't directly synchronized with Server3
An other question: Is the replication with slurpd or SyncREPL supported over WAN ?
Yes, but please try to use Syncrepl over slurpd
Are there some restrictions ?
Firewall/routing etc. Depends what you have setup/require.
Of course, these points must be configured correctly but, i supposed typically latency issues due to the distance or connection closed by a firewall due to inactivity.
Gavin.
Rgds, Bruno.
Gavin Henry wrote:
<quote who="Bruno Lezoray EMSM"> > Gavin Henry wrote: >> <quote who="Bruno Lezoray EMSM"> >> >>> i have a request from a customer about 2 replication architectures and >>> i >>> would like to know if it's possible to implement them: >>> 1 - Master Server -> "hub" Server -> Slave Server >>> >> Expand on what you mean by "hub"? >> >> > Hub comes from Sun Directory Server terminology which means a read-only > server that receives/get updates to/from a master and send updates to a > slave
Ah, a proxy.
Nope. In Sun's Directory Server terminology a "hub" is a normal replica with own database. I've read it was introduced to spread the replication load when having *very many* slave replicas. Or maybe it was introduced to sell more hardware... ;-)
Ciao, Michael.
On Tue, 17 Jul 2007, Bruno Lezoray EMSM wrote:
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them: 1 - Master Server -> "hub" Server -> Slave Server 2 - Server1 <-> Server2 <-> Server 3
Look in the tests directory for cascading syncrepl examples.
Is the replication with slurpd or SyncREPL supported over WAN ? Are there some restrictions ?
Both slurpd and syncrepl rely on TCP connections. If your WAN supports TCP connections, it should be fine. I don't think any particularly special restrictions apply versus whatever ones may be inherently present on your network.
Bruno Lezoray EMSM bruno.lezoray@wh-ces.gmessaging.net writes:
Hi all,
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them:
the tests suit provides 2 examples
1 - Master Server -> "hub" Server -> Slave Server
this would be solved by test045, syncreplication proxied
2 - Server1 <-> Server2 <-> Server 3
test019 syncreplication cascade
An other question: Is the replication with slurpd or SyncREPL supported over WAN ? Are there some restrictions ?
What transport protocol is required by the WAN? LDAP is a connection based protocol which requires tcp/ip.
-Dieter
<quote who="Dieter Kluenter">
Bruno Lezoray EMSM bruno.lezoray@wh-ces.gmessaging.net writes:
Hi all,
i have a request from a customer about 2 replication architectures and i would like to know if it's possible to implement them:
the tests suit provides 2 examples
1 - Master Server -> "hub" Server -> Slave Server
this would be solved by test045, syncreplication proxied
Of course, but only in 2.4/HEAD.
2 - Server1 <-> Server2 <-> Server 3
test019 syncreplication cascade
An other question: Is the replication with slurpd or SyncREPL supported over WAN ? Are there some restrictions ?
What transport protocol is required by the WAN? LDAP is a connection based protocol which requires tcp/ip.
-Dieter
-- Dieter Klünter | Systemberatung http://www.dkluenter.de GPG Key ID:8EF7B6C6
openldap-software@openldap.org
-
Aaron Richton -
Bruno Lezoray EMSM -
Dieter Kluenter -
Gavin Henry -
Michael Ströder