Issue
We noticed that DirSync Synchronization stuck in “Syncing” or "Canceling" very often when we configure it to run using the scheduler.
What are your recommendations to avoid this?
Solution
1 Check the Windows Event Viewer Log on the Dirsync console server to determine if there are any errors recorded
2 Confirm the Dirsync Logs are set to roll over.
This setting can be found under the Logs and Reports > Sync Logs >Clear and then verify that the Clear log automatically is enabled and that there is a time-period selected for the setting.
3 Verify there are no active sync's in progress and make a note of the schedule for the sync profile and then set that to Manual.
4 Restart the BTDirsync task on the Domino server:
Issue the following command at the Domino console
Tell BTDirsync quit
When complete issue the following command
Load BTDirsync
5 Restart the BT Dirsync Windows service on the DirSync console server.
6 Run a Manual sync of the profile using the Synchronization > PushPull option.
7 Allow the sync to complete (verify if there are any errors on the Domino console or in the Windows Event log) and then check the accounts.
8 Re-enable the Scheduled Sync.
If syncs are stopping periodically on the Domino server. This can indicate there may be a problem writing to SQL or the schedule is too frequent for the data volume to be processed.
Dirsync will only process 1 sync profile at a time, if a sync does not complete before another sync profile is due to start then the second profile will wait (but not show as Idle) for the current profile to complete before starting its processing.
Review how long the syncs take to complete and adjust the schedules to allow each sync to complete.
Additionally. some Domino maintenance is recommended, this mainly just a periodic restart of the Domino server. For example, a quarterly system restart to ensure that there are no Domino and/or Windows related issues which may have an impact on processing. This can typically follow your organization's Domino maintenance policies.
Finally, performing some SQL maintenance is also good to consider. Backing up of the two Dirsync databases to disk (in SQL Management Studio, right click the DB and choose Tasks > Backup).
Dirsync does not hold data other than the configuration that cannot be retrieved (the data is in Domino and AD) so you do not typically need to retain sequential backups of the SQL Databases, but a single monthly or quarterly backup is good to hold in case a system restore is needed. This also has the benefit of clearing the SQL transaction logging.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Términos de uso Privacidad Cookie Preference Center