Recommendations on using single DSA agent with multiple domain pairs. (4209229)

In some complex migration scenarios involving multiple domains it is sometimes not possible to dedicate one DSA server per every domain pair. What are the best practices for such a setup?

It is possible by design to configure single a DSA agent for use with multiple domain pairs. Please refer to the Resolution section for some useful recommendations when following these types of scenarios. They are based on the experience from field engineers that are deploying QMM in complex environments.

1. Only one DSA installation per server is supported. If hardware resources allow, it is better to have at least one DSA server dedicated per single domain pair.
2. An optimal amount of domain pairs per single DSA is three to five depending on the size of source domain (from less then 1000 to about 4000 objects). While more is possible the performance may not be optimal.
3. Doing Full Resync (Initial Sync) on given domain pair significantly slows down other pairs delta synchronizations.
4. The Full Resync (Initial Sync) is very time and resource  intensive by itself and sometimes taking a very long time. It is best to have other synchronization jobs stopped in order to expedite this process.
5. DSA consists of five different windows services each following certain logic. Some cycles need to be completed successfully before the agent starts the next cycle. This may lead to the complete halt of all other domain pair synchronization sessions until the original issue with given domain pair sync is resolved. As an example it may be a loss of connectivity to a particular DC or GC.