Central Management Store Replications

How Central Management Store Replications work?

 

 CMS is new in Lync and it is best enhancement because it reduces administrator work.

Administrator has to just see the CMS instead of else were. However CMS replication is main things which we need to understand properly otherwise you will face lot of issues.

All configurations are performed on the Central Management store master and all servers running Lync Server have a local replica of the Central Management store. Therefore, the replicas must be updated from the Central Management store master. The Central Management store replication process consists of writing the Central Management store information to a local folder structure on the Central Management store master, copying that information to the replicas, applying the changes received to the replica, and then reporting status back to the Central Management store master.

 

The Central Management store master uses a directory file structure shared with other Lync Server components in a network share that is defined by the topology document. The name of the top-level directory is the Service ID of the Central Management store master.

\\CMSFileStore\xds-master

 

1.    Is the name of the directory selected to be the FileStore used by the Central Management store in the topology document.

 

2.     Is the service ID of the Central Management store service in the topology document. The directory, xds-master, contains the following subdirectories: replicas and working. The replicas directory contains a subdirectory for each of the replicas. Each subdirectory is named after the FQDN of the replica server.

Within each replica directory are the subdirectories: from-replica and to-replica,

CMS1

Each replica uses a directory structure in the network share, \\\xds-replica, to synchronize with the Central Management store master, where is the FQDN of the replica. The xds-replica directory contains the following subdirectories: from-master, to-master, and working.

Things need to keep in mind-

1.    Every 60 seconds, the Central Management store master determines whether a configuration change has been made to the Central Management store master and needs to be replicated.

2.    The unit of replication is the changed XML document.

3.     If a dial plan with global scope is added, the full XML document containing dial plans with global scope will be replicated.

4.    All changes that are made since the last time the task was run are batched together into a data package (that is, the data.zip file).

5.    The size of the data package is small, typically less than 100 KB, which makes for fast replication across the network without any substantial impact on network bandwidth.

 The Master Replicator Agent service generates the data package containing new changes to Central Management store and stores a copy in each to-replica directory for every Lync Server replica.

The data package must be copied to all replicas. The Central Management store master, with the exception of the Edge Server, uses the Windows file copy Server Message Block (SMB) protocol to push the data packages to the replica.

 

Thank you.