Hi I just wanted to know whats the best practice to make sure all Slave as same data as master. while reading on google, i got bellow command also 1 script to monitor ldap replication status.
[root@blob]# ldapsearch -x -b "cn=mapping tree,cn=config" -D "cn=Directory Manager" -w YOURPASSWORD objectClass=nsDS5ReplicationAgreement nsds5replicaLastUpdateStatus -LL
I have checked this against our 6 slave server and they all returned : nsds5replicaLastUpdateStatus: 0 Incremental update succeeded
but still one of the slave did not have same data as master , after I reinitialise the slave replication , the data was Ok So if i want to create a script to monitor slave replication status and wants to make sure that all slave as same data as master what will be the best practice ?? Thanks Fosiul
On 03/01/2013 04:40 AM, Fosiul Alam wrote:
Hi I just wanted to know whats the best practice to make sure all Slave as same data as master. while reading on google,
Best to read the docs
https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Directory_Server/9.0/...
i got bellow command also 1 script to monitor ldap replication status.
[root@blob]# ldapsearch -x -b "cn=mapping tree,cn=config" -D "cn=Directory Manager" -w YOURPASSWORD objectClass=nsDS5ReplicationAgreement nsds5replicaLastUpdateStatus -LL
I have checked this against our 6 slave server and they all returned : nsds5replicaLastUpdateStatus: 0 Incremental update succeeded
So the last replication session was successful.
but still one of the slave did not have same data as master ,
What did you use to check this?
after I reinitialise the slave replication , the data was Ok So if i want to create a script to monitor slave replication status and wants to make sure that all slave as same data as master what will be the best practice ?? Thanks
Fosiul
389 users mailing list 389-users@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/389-users
389-users@lists.fedoraproject.org