Configuring Hub/Spoke Sync Environment with Dedicated Master Directory

When syncing 2 LDAP directories, only 2 connections are typically needed to sync directly between them:

• ServerA to ServerB
• ServerB to ServerA

When syncing 3 or more directories you would need to create 6 (or more) connections to sync each directory between the other individually. Every additional local directory adds another set of required connections to do a full sync between all directories:

• ServerA to ServerB
• ServerA to ServerC
• ServerB to ServerA
• ServerB to ServerC
• ServerC to ServerA
• ServerC to ServerB

When syncing 3 or more directories, a Hub/Spoke configuration is recommended instead.

Summary of Hub/Spoke implementation:

The Hub/Spoke configuration allows you to minimize the number of connections and create a local centralized email directory. The Hub server may be an additional standalone directory, or you may utilize one of your spoke LDAP directories to also act as the Master. The Hub/Spoke solution syncs each Spoke into the Master Directory on the Hub server into a unique OU (Structure Name and/or Placement DN). Then, all entries from the Master are synced back to each individual Spoke (excluding those entries that originated from that Spoke to avoid looping).

The following is an example of a Hub/Spoke UnitySync configuration for 3 directories, in which a separate (additional) directory acts as the dedicated Master Directory. To see an example that utilizes a Spoke Directory as Master Directory, refer to Configuring Master/Spoke Sync Environment with Local Spoke acting as Master Directory.

Details of Master/Spoke implementation using a Dedicated Master Directory:

The additional dedicated directory to act as Master will be called Master. The connections required for this configuration are as follows:

• ServerA to Master
• ServerB to Master
• ServerC to Master
• Master to ServerA
• Master to ServerB
• Master to ServerC

Each connection that syncs into the Master Directory should be configured with a unique Structure Name (Destination tab). Structure Name defines the OU to be created on the Master and populated with contacts for that connection. This OU structure can later be used for selection of Source objects when pulling from the master to avoid directory looping. The Structure Name itself may also be used, via custom mapping, to append an Origin tag to your displayName of contacts synced back to spokes.

Each connection that syncs from the Master Directory will sync all objects that need to be synced back to each Spoke. When syncing back to each spoke, configuration should be such to avoid directory looping.

If you would like to implement this solution and need assistance with the configuration for your unique environment, please contact our Technical Support team.