By performing concurrent synchronizations, you can divide synchronization tasks between two or more administrators to create smaller workloads and reduce the amount of time it takes to synchronize a network or cluster of SDS elements. If you have a large network with many elements, you may want to use concurrent synchronizations to save time when you are bringing the element databases into sync for the first time.
Note: Concurrent synchronizations can result in distribution errors because when several synchronizations are run in parallel from several masters, the shared data updates sent from a given master are rejected by elements that are involved in an another synchronization.
CAUTION: Only perform synchronizations during periods of low traffic (off-business hours). The length of time required to sync each element is dependent on the size of the databases and the amount of shared data.
To perform concurrent synchronizations:
Review the conditions affecting concurrent synchronizations. See About Concurrent Synchronizations.
Identify the master elements in the network or cluster. They should have the most up-to-date databases in the network or cluster.
Assign Root Administrator A system administration policy that permits unrestricted access to the 3300 ICP System Administration Tool. Only users logged in to the tool as the Root Administrator have read/write access to all forms and can grant tool access to other users. access rights to each of the master elements (see Assigning Administrators).
At one of the master elements, add the cluster elements, define the network elements, and specify the shared data, and start sharing its database with all the other elements.
CAUTION: All the elements must be sharing data before you start synchronizing the data from the master elements to the slave elements.
In the Network Elements form on each master element, select the subset of slave elements that you want to synchronize from this master.
CAUTION: Each slave element should only appear in one master element's Confirm Sync list.
On each master element, click the Sync button.
After the synchronization operation is complete, check the Shared Data Update form on each master element:
Updates may have been rejected because a sync was in progress
Updates may have been detected as concurrent changes and failed as such
Carefully determine which updates fall in which category then correct using the Retry and Force Change buttons in the SDS Shared Data Updates form:
Retry updates that were rejected because a sync was in progress
Overwrite conflict detection for the updates that failed as concurrent changes.