There are multiple reasons why Synchronization is always working. To verify that DSA is always busy, please monitor the dsa.log file on DSA machine that it constantly grows non stop. Sometimes, QMM console dirsync status may not reflect actual DSA one, which could be a symptom of completely different issue.
Here's the list of possible reasons for such behavior:
- DSA sleeping period was changed to the very short value, like 1 min. This can be changed in QMM console, Agent Manager, properties of DSA machine, Scheduling tab
- there is a lot of synchronized security groups with many members. Dirsync status will stay, while LinkResolver is working on AD objects' links, like managers and groups' memberships.
- DSA cache got corrupted, causing it to perform resync on all objects in scope over and over again, regardless if they were synchronized previously. Please note, that removal of DSA cache will require a full resync operation to be performed.
- there are 3rd party tools or scripts in the source domain, that constantly modifying AD objects. DSA depends on the AD objects modification timestamp. So once it's different from the cached value, object is synced again.
- DSA preferred DC/GC is set to the remote or slow DC, which takes time to respond. DSA issues a lot of LDAP queries and delay like this can contribute to overall slowness.
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center