# SDS - Synchronization Rules

The following rules apply to synchronization operations:

- Do not perform synchronization from MiVoice Business Release 9.0 to a pre-9.0 release.

- 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.

- When adding a new node to the network or cluster, do the sync (and sharing too) from an established element in the network or cluster (ideally the master element), not from the new node. The synch works best from the master as the new node has no current information other than basic connection data. If the synch is carried out from the new node, it repeats all the "new" data to all the other nodes. These nodes already have this data, so it's wasted processing effort, and the more nodes there are in the network or cluster the longer it takes to sync.

- During a Start Sharing or Sync operation, all system administration tools sessions (System Administration Tool, Group Administration Tool, Desktop Tool, and MiXML sessions) on the local (master) node are terminated and subsequent sessions are blocked until the synchronization finishes. On the remote (slave) node, all System Administration Tool sessions remain active during the synchronization process. The user remains logged in with read-only access to the shared forms. All maintenance commands on the slave are disabled, but the administrator can log in, read data, and change data that is not shared.

- 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-3849-01068 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.

- Automatic full synchronization is performed after a Start Sharing operation to a single MSL Server-type network element (such as, MiCollab) completes successfully.

NOTE: This rule does not apply when multiple network elements (of any type, but without a MiCollab server) are selected for Start Sharing.

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.

The following rules apply when you synchronize with a MiCollab server. Synchronization will fail if any of these rules do not pass the verification.

- The local MiVoice Business node must be able to share data with MiCollab, that is, it must be software version 7.2 or up and the MiCollab server must be software version 7.0 or up.

- All data-sharing network elements must be able to share with an MSL Server-type network element.

- There can be only one or no cluster in the network.

NOTE: One cluster, but not all nodes in the cluster configuration is supported.

- There can be only one MiCollab server in the network. Sharing with multiple MiCollab servers is not supported.

NOTE: Only single MiCollab server and no other network element can be selected for Start Sharing. Otherwise, the operation will be rejected.

- Automatic full synchronization (without the option to manually cancel it) will be performed after the Start Sharing operation is completed.

- If the Service Hosting data is shared at the "Admin Group Members" scope, all cluster elements must be in the same admin group.

- If errors or conflicts with data on MiCollab server are detected, the system creates a software log and displays an appropriate error message advising you to log into the MiCollab server and run the Reconcile Wizard. See the MiCollab documentation on the Mitel Customer documentation site (https://www.mitel.com/document-center/business-phone-systems/mivoice-business) for more information.

Related Topics

- About_Sharing and Synchronizing Data

- About Synchronizing User and Device Data

- Migrate User and Device Data

- Repairing Data

- Synchronizing Data