Configuring Master/Spoke Sync Environment with Local Spoke acting as Master Directory and Hub

Created: 2012-04-20 08:09:59
Modified: 2017-06-04 11:01:44
Tags: Master/Spoke UnitySync

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 ServerA acts as the Master Directory in addition to being one of the Spokes. To see an example that utilizes a separate Master Directory as Master Directory, refer to Configuring Master/Spoke Sync Environment with Local Spoke acting as Master Directory and Hub.

Details of Master/Spoke implementation using a Spoke Server as Master:

The connections required for this configuration are as follows:

  • ServerB to ServerA (Master)
  • ServerC to ServerA (Master)
  • ServerA (Master) to ServerB
  • ServerA (Master) to ServerC

Note: As you might guess, in this configuration there is no need to load ServerA entries since ServerA is acting as the Master.

Each connection that syncs into ServerA (Master) should be configured with a unique Struct 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 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 ServerA (Master) will sync all objects from the Master that need to be synced back to each Spoke. This includes the local ServerA entries as well as the Spoke entries loaded by the first two connections into unique OUs. 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.

Share this article:

  1. Directify - Self Service

  2. Mimic - Replication

  3. UnitySync - Sync
  1. emPass - Sync
  1. Profiler
  2. SimpleSync