The SCC MediaServer Replication Module uses a Publish-Subscribe model for distributing data from a "Publisher" MediaServer system to a second "Subscriber" MediaServer system located at a remote site or alternate cloud zone for disaster recovery purposes.
 
The Publisher is the primary MediaServer system and is the source of the data to be replicated. The Subscriber is a separate SCC MediaServer system that receives the data being replicated from the Publisher. One or more Subscriber servers can be connected to a single Publisher.
 
In the event that the Publisher MediaServer becomes inaccessible, one of the Subscriber MediaServers can easily be promoted to become the new primary server taking on the role of the Publisher.
 
The Replication Module distributes Publisher data to each Subscriber so that new insertions, object updates, stored documents, user account additions and changes, project changes, and library definitions on the Publisher are reflected in the state of each Subscriber.
 
Replication is performed as a ‘lazy’ (delayed) operation so that replication work does not interfere with the timing and performance of the Publisher’s normal operations. For example, if a Publisher must update two records, it does not have to wait for the first update to be replicated before the second update is begun. Instead, changes on the Publisher are marked and recorded as they occur and in the order they occur with little or no impact on Publisher performance.
 
At any time, the Replication Channel can be stopped and later restarted to resume its operations, independently for each Subscriber.
 
High resolution files (stored documents) are also copied to the Subscriber using a ‘lazy’ (delayed) operation, and this can be configured for near immediate, delayed, or at a scheduled time.
 
Administrative functions for the Replication Module are contained in the SCC MediaServer Administration Utility. This utility automatically detects the server mode (Standalone, Publisher, or Subscriber).
 
For Publishers, the utility will list available subscribers and allow registration of new subscribers to the publisher. For Subscribers, the utility will list the server’s libraries so that the administrator can select which libraries are to be replicated at which time it verifies compatibility of the selected libraries with the corresponding Publisher libraries.