Gmorning Mark, Thank you again for fast reply, do I stilll need to create a rep agreement ? the 389 RH console option does not mention this step , please see the link bellow. ( The concern I have but I have not tested: while initial supplier goes offline hard/crash and I start making the consumer as new supplier when original/old supplier comes online after X days do not have replication change log conflicts , would this case be avoided?) https://access.redhat.com/documentation/en-US/Red_Hat_Directory_Server/8.1/html/Administration_Guide/Managing_Replication-Making_a_Replica_Updatable.htmlOn 11/12/2015 12:31 PM, ghiureai wrote: > Hi List , > > I'm looking for cmd line steps to make a dedicated consumer in a > supplier in single master replication ( if original master goes > offline), I have the steps from Admin GUI , > I would like to hase same steps but using cmd's line : > - add the new changelog entry at to be supplier host , > next how can I disable dedicated consumer and re-enable as single > master/supplier ( would changing > nsds5replicatype: to 3 be sufficient ? ) , -reboot DS - no agreements > needs to be created. Are this steps sufficient? Almost... Here are the steps using ldapmodify (you will need to modify some of the values to match your installation): Create a changelog dn: cn=changelog5,cn=config changetype: add objectclass: top objectClass: extensibleObject cn: changelog5 nsslapd-changelogdir: /var/lib/dirsrv/slapd-YOUR_INSTANCE/changelogdb Modify the replica entry (this example uses "dc=example,dc=com" as the suffix): dn: cn=replica,cn=dc\3Dexample\2Cdc\3Dcom,cn=mapping tree,cn=config changetype: modify replace: nsDS5ReplicaType nsDS5ReplicaType: 3 - replace: nsDS5Flags nsDS5Flags: 1 - replace: nsDS5ReplicaId nsDS5ReplicaId: <some number less than 65535) Then you can create replication agreements. Mark On 11/12/2015 09:31 AM, ghiureai wrote: Hi List , |
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
