5 Replies Latest reply: Oct 19, 2012 12:19 PM by John Prince RSS

    Multimaster Replication  insync

    Rodrigo0461
      hi


      I apply the following command:


      ./insync -D "cn=Directory Manager" -w admin123 -s server02:389

      shows this


      ReplicaDn Consumer Supplier Delay
      dc=clarochile,dc=cl server01:389 server02:389 0 * Disabled Replication Agreement: no subsequent warnings given

      * Disabled Replication Agreement: no subsequent warnings given: that means?

      Thanks
        • 1. Re: Multimaster Replication  insync
          Marco Milo
          Hi

          it means that both supplier and consumer were in sync (have the same RUVs) at the moment the 'insync' command has been executed.

          Moreover the status of the replication agreement between server02 (supplier) and server01 (consumer) is "disabled": which means that the changes generated on the supplier (server02) are not sent through this replication agreement to the consumer (server01), and so no warnings will be triggered in case the delay should start to increase.

          HTH,
          marco
          • 2. Re: Multimaster Replication  insync
            Rodrigo0461
            Thank you.

            shows the reverse process.

            ./insync -D "cn=Directory Manager" -w admin123 -s server01:389

            ReplicaDn Consumer Supplier Delay
            dc=clochile,dc=cl clarods02:389 clarods01:389 0

            this is right?


            I get the replication settings?

            that occupy command?

            THANKS marco
            • 3. Re: Multimaster Replication  insync
              Marco Milo
              Well, there is only a bit of confusion with the names...

              ./insync -D "cn=Directory Manager" -w admin123 -s server02:389

              ReplicaDn Consumer Supplier Delay
              dc=clarochile,dc=cl server01:389 server02:389 0 * Disabled Replication Agreement: no subsequent warnings given

              and:

              ./insync -D "cn=Directory Manager" -w admin123 -s server01:389

              ReplicaDn Consumer Supplier Delay
              dc=clochile,dc=cl clarods02:389 clarods01:389 0

              it seems that 'server02' resolves the two hostnames like 'server01' and 'server02', whereas the 'server01' resolves the names as 'clarods01' and 'clarods02'...

              but apart from that, the second command shows that the replication is in sync (when the insync command has been executed) and perfectly going (replication enabled) from clarods01:389 to clarods02:389 for the suffix "dc=clochile,dc=cl"

              HTH,
              marco.
              • 4. Re: Multimaster Replication  insync
                Rodrigo0461
                this

                ./dsconf show-repl-agmt-status dc=clachile,dc=cl clarods02:389

                indicates

                Configuration Status : OK
                Authentication Status : OK
                Initialization Status : OK

                Status : Enabled
                Last Update Date : Oct 17, 2012 3:21:51 PM

                but


                ./dsconf show-repl-agmt-status dc=clachile,dc=cl clarods01:389

                indicates

                "clarods01:389": replication agreement does not exist on dc=clarochile,dc=cl.


                means?
                • 5. Re: Multimaster Replication  insync
                  John Prince
                  Hi,

                  Please put complete replication topology, that will give us to help.

                  JPrince.