The following rules apply to synchronization operations:
Only perform synchronizations during periods of low traffic (off-business hours). The time required to complete a synchronization depends on the size of the databases and the number of forms that are being shared.
All remote System Administration, Group Administration, Desktop Tool, and MiXML sessions are terminated after you start a synchronization and will remain blocked until the synchronization is complete. If the synchronization fails to complete, all sessions could remain blocked for up to 60 minutes from the time of the failure.
A synchronization may fail if you attempt to synchronize form data that has data dependencies in other forms. For example, you cannot complete the ARS Digits Dialed form until the changes to the ARS Routes form have been completed. To avoid this problem when you synchronize data from a form, include its dependent forms in the Start Sharing operation.
Ensure that you have installed the required Internet Explorer registry file on your PC. The registry file extends your Internet Explorer session and prevents it from timing out before a Start Sharing or Synchronization operation is complete. Refer to Mitel Knowledge Base article 07-3829-00006 on Mitel Online for instructions.
The system permits up to 500 synchronization errors for a sync session between a primary and secondary controller. If the number of errors against all forms exceeds 500, the system will stop the synchronization operation.
You can assign different Mailbox Numbers and Extension Numbers to the same user through the System Administration Tool. SDS cannot replicate data from this view unless these fields match. Ensure that the Mailbox Number and Extension Number are identical when you provision an embedded Voice Mailbox.
After
modifying the PNI of a network or cluster, you must wait until the PNI
has been updated on the member elements before you perform a sync operation;
otherwise, the sync operation may fail. Before performing the sync, check
the maintenance logs for a log similar to the following to ensure that
the PNI has been updated on the member elements:
50 INFO 2009/03/11 19:51:23 CorpDirUpdate Maintenance(0)
Updated 23 record(s) for PNI 520 to 510.
The following rules apply if you synchronize Clustered Call Pickup groups:
SDS does not share the group and member information with all the cluster elements. SDS shares group and member information only to cluster elements that have at least one local member programmed in the pickup group.
