DirWiz Logo

Article Tags

General Tab: Orphans

2019-08-21 14:36:33
AD LDS ADAM Troubleshooting UnitySync 

This feature allows you to log orphan objects with each Synchronization.

Occasionally, your Destination sync container may contain contacts that no longer appear on the Source. We call these objects “orphans”. An orphan is any object that exists in the Destination sync container but is no longer within the scope of the sync on the Source.

Most often, these are objects that were previously synced by UnitySync, then deleted on the Source but the deletion did not also occur on the Destination.

Sometimes, this is because you have opted to Ignore Deletes in your Delete Processing options on the Destination tab. Even when you choose to Process Deletes on the Destination tab, a delete of an object is only attempted once. If the delete cannot occur, for whatever reason, when it is attempted, it will not be attempted again.

As of UnitySync v2.0, if you select the option to Log orphans after Synchronization, UnitySync will identify orphans for you, producing a file that contains the DN’s of all orphaned objects. A list of orphans is also included just above the Run Summary in your sync log.

We do not recommend that you enable orphan logging on all syncs. Instead, only run the orphan check when you know or suspect your have orphaned objects on your Destination. Running orphan check on every sync will slow down your connection.

To identify orphans:
  • In the UI, select your connection and then the General tab.
  • In the Logs section, click the box to select Log orphans after Synchronization.
  • Click Save at the bottom of the tab.

Now when you run your connection, you will notice two things. First, you will see a list of orphaned objects in your sync log file just above the Run Summary. Also, the file orphans.txt will be created under your specific connection folder.

You may use the information in your log as a guide to manually examine and process the orphans on the Destination, deleting them if they are no longer needed.

IMPORTANT NOTE: The information identifying orphans is the comparison of database files of the current connection to the objects that exist in the Sync container on the Destination. So, if you are syncing more than one Source to a single Destination Sync Container, each connection will identify the objects that belong to the other connections scope as orphans.

The orphans.txt file generated can be used by UnitySync to automate the orphans deletion process. This is an undocumented feature which should be used with extreme caution and therefore, we insist that you contact our Technical Support Team before employing this option.

If you used an automated process via ldifde (or other LDAP utilities) to process the deletes with UnitySync versions 2.9 and earlier, please contact our Technical Support Team for guidance.

Share this article: Twitter reddit