Given your scenario - if you did a restore then you would get an error message of something like NSMMReplicationPlugin - agmt="cn=master-t01-to-master-t02" (ldap-master-t02:389): Replica has a different generation ID than the local data. Yes, I just did this. Then you would want to conduct an online initialization to bring the replica back into sync. Given this, all you need to do is monitor that replication is working. Under normal operations you won't have a problem. If you start doing exceptional things like mucking directly with the DB file, then this is how you might get into the trouble you describe and the solution is to re-init the replica. i hope this helps. /mrg On Mar 28, 2012, at 7:47, Manel Gimeno Zaragozá wrote: |
-- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users