Skip to main contentdfsdf

      • Настройка репликации между двумя серверами

    • dsreplication enable \  --host1 host1 --port1 1389 --bindDN1 "cn=Directory Manager" \  --bindPassword1 password --replicationPort1 8989 \  --host2 host2 --port2 2389 --bindDN2 "cn=Directory Manager" \  --bindPassword2 password --replicationPort2 8990 \  --adminUID admin --adminPassword password --baseDN "dc=example,dc=com"
      • ./dsreplication status -h 188.72.66.139 -p 4444 --adminUID admin --adminPassword demis

    • Configuring Large Replication Topologies
    • To Configure a Dedicated Directory Server

       

      To configure a dedicated directory server, use the --noReplicationServer1 or --noReplicationServer2 option when you enable replication between two directory servers. This example configures replication between the directory server instances A and B in the previous illustration. 

       
      $ dsreplication enable \   --host1 host1 --port1 4444 --bindDN1 "cn=Directory Manager" \   --bindPassword1 password --replicationPort1 8989 \   --host2 host2 --port2 4444 --bindDN2 "cn=Directory Manager" \   --bindPassword2 password  --noReplicationServer2 \   --adminUID admin --adminPassword password --baseDN "dc=example,dc=com" -X -n 
       

       

      To Configure a Dedicated Replication Server

       

      To configure a dedicated replication server, use the --onlyReplicationServer1 or --onlyReplicationServer2 option when you enable replication between two servers. This example configures replication between Directory Server C and Replication Server 2 in the previous illustration. 

       
      $ dsreplication enable \   --host1 host3 --port1 4444 --bindDN1 "cn=Directory Manager" \   --bindPassword1 password --noReplicationServer1 \   --host2 host4 --port2 4444 --bindDN2 "cn=Directory Manager" \   --bindPassword2 password --onlyReplicationServer2 \   --replicationPort2 8989 --adminUID admin --adminPassword password \   --baseDN "dc=example,dc=com" -X -n
  • Oct 10, 11

    Specifying the Schema Source

    When you configure replication with the dsreplication enable command, you can specify that the schema of the second directory server be used to initialize the schema of the first server. If you do not specify an option, the schema of the first directory server is used by default.

    In the following example, the data of host1 is used to initialize host2 but the schema of host2 is used to initialize the schema on host1:

    $ dsreplication enable --host1 host1 --port1 4444 --bindDN1 "cn=Directory Manager" \
    --bindPassword1 password --replicationPort1 8989 --host2 host2 --port2 4444 \
    --bindDN2 "cn=Directory Manager" --bindPassword2 password --replicationPort2 8990 \
    --adminUID admin --adminPassword password --baseDN "dc=example,dc=com" \
    --useSecondServerAsSchemaSource -X

    • Specifying the Schema Source

         

      When you configure replication with the dsreplication enable command, you can specify that the schema of the second directory server be used to initialize the schema of the first server. If you do not specify an option, the schema of the first directory server is used by default.

        

      In the following example, the data of host1 is used to initialize host2 but the schema of host2 is used to initialize the schema on host1:

      $ dsreplication enable --host1 host1 --port1 4444 --bindDN1 "cn=Directory Manager" \   --bindPassword1 password --replicationPort1 8989 --host2 host2 --port2 4444 \   --bindDN2 "cn=Directory Manager" --bindPassword2 password --replicationPort2 8990 \   --adminUID admin --adminPassword password --baseDN "dc=example,dc=com" \   --useSecondServerAsSchemaSource -X
    • Large replication topologies
      • he new arguments for the enable subcommand are: 

         
        • --noReplicationServer1

            Specifies not to have a replication port and changelog on the first server.  The first server will only contain replicated data but no changelog with  the modifications made to the replicated data. At least two servers with a  changelog are required in the replication topology to avoid a single point  of failure 
        • --onlyReplicationServer1

            Specifies to only have a changelog (with a replication port) on the first  server. The first server will not contain replicated data but only a  changelog with the modifications made in the data contained in other  servers 
        • --noReplicationServer2

            Specifies not to have a replication port and changelog on the second  server. The second server will only contain replicated data but no  changelog with the modifications made to the replicated data. At least two  servers with a changelog are required in the replication topology to avoid  a single point of failure 
        • --onlyReplicationServer2

            Specifies to only have a changelog (with a replication port) on the second  server. The second server will not contain replicated data but only a  changelog with the modifications made in the data contained in other  servers 

         

        The two new arguments for the disable subcommand are: 

         
        • --disableReplicationServerArg

            Disable the replication server. The replication port and changelog will be  disabled on the specified server 
        • --disableAll

            Disable all the replication configuration in the specified server. The  contents of the server will no longer be replicated and the replication  server (changelog and replication port) will be disabled if it is  configured 

        There is a new configuration argument: 

         
        • --advanced
    • dsreplication — manage OpenDJ directory data replication
    • $ dsreplication enable -I admin -w password -X -n -b dc=example,dc=com --host1 `hostname` --port1 4444 --bindDN1 "cn=Directory Manager" --bindPassword1 password --replicationPort1 8989 --host2 `hostname` --port2 5444 --bindDN2 "cn=Directory Manager" --bindPassword2 password --replicationPort2 9989
1 - 10 of 10
20 items/page
List Comments (0)