]> git.sur5r.net Git - openldap/commitdiff
Clarify MM config example.
authorGavin Henry <ghenry@openldap.org>
Wed, 8 Oct 2008 21:16:09 +0000 (21:16 +0000)
committerGavin Henry <ghenry@openldap.org>
Wed, 8 Oct 2008 21:16:09 +0000 (21:16 +0000)
doc/guide/admin/replication.sdf

index 6d58f4df68537aa7fca4507f12cb67abfca62c2c..d9c4f2ebbd1f5fa76f0a2b24cf849f43cfabd51c 100644 (file)
@@ -612,7 +612,7 @@ H3: MirrorMode replication
 MirrorMode is a hybrid configuration that provides all of the consistency
 guarantees of single-master replication, while also providing the high
 availability of multi-master. In MirrorMode two masters are set up to
-replicate from each other (as a multi-master configuration) but an
+replicate from each other (as a multi-master configuration), but an
 external frontend is employed to direct all writes to only one of
 the two servers. The second master will only be used for writes if
 the first master crashes, at which point the frontend will switch to
@@ -1025,7 +1025,8 @@ different and add it as a global configuration option.
 
 H4: Mirror Node Configuration
 
-This is the same as the {{SECT:Set up the provider slapd}} section.
+The first step is to configure the syncrepl provider the same as in the 
+{{SECT:Set up the provider slapd}} section.
 
 Note: Delta-syncrepl is not yet supported with MirrorMode.
 
@@ -1038,18 +1039,8 @@ MirrorMode node 1:
 >       serverID    1
 >       # database section
 >       
->       # syncrepl directives    \r
+>       # syncrepl directive    \r
 >       syncrepl      rid=001\r
->                     provider=ldap://ldap-ridr1.example.com\r
->                     bindmethod=simple\r
->                     binddn="cn=mirrormode,dc=example,dc=com"\r
->                     credentials=mirrormode\r
->                     searchbase="dc=example,dc=com"\r
->                     schemachecking=on\r
->                     type=refreshAndPersist\r
->                     retry="60 +"\r
->
->       syncrepl      rid=002\r
 >                     provider=ldap://ldap-rid2.example.com\r
 >                     bindmethod=simple\r
 >                     binddn="cn=mirrormode,dc=example,dc=com"\r
@@ -1058,7 +1049,7 @@ MirrorMode node 1:
 >                     schemachecking=on\r
 >                     type=refreshAndPersist\r
 >                     retry="60 +"\r
->       \r
+>
 >       mirrormode on
 
 MirrorMode node 2:
@@ -1067,19 +1058,9 @@ MirrorMode node 2:
 >       serverID    2
 >       # database section
 >       
->       # syncrepl directives\r
->       syncrepl      rid=001\r
->                     provider=ldap://ldap-ridr1.example.com\r
->                     bindmethod=simple\r
->                     binddn="cn=mirrormode,dc=example,dc=com"\r
->                     credentials=mirrormode\r
->                     searchbase="dc=example,dc=com"\r
->                     schemachecking=on\r
->                     type=refreshAndPersist\r
->                     retry="60 +"\r
->
+>       # syncrepl directive\r
 >       syncrepl      rid=002\r
->                     provider=ldap://ldap-rid2.example.com\r
+>                     provider=ldap://ldap-rid1.example.com\r
 >                     bindmethod=simple\r
 >                     binddn="cn=mirrormode,dc=example,dc=com"\r
 >                     credentials=mirrormode\r
@@ -1091,7 +1072,8 @@ MirrorMode node 2:
 >       mirrormode on
 
 It's simple really; each MirrorMode node is setup {{B:exactly}} the same, except
-that the {{serverID}} is unique.
+that the {{serverID}} and {{rid}} are unique, and that the {{provider}} is pointed to 
+the other server.
 
 H5: Failover Configuration