Applies to Riva 2.4.42 or higher.
The Riva Synchronization Platform, in its simplest deployment, consists of one Riva On-Premise instance on one virtual or physical host system. That server handles the entire synchronization process.
A single Riva instance can handle the synchronization of several thousand mailboxes. For deployments looking to ensure the configuration is fault-resilient with no single points of failure or if there is a need to scale the deployment in order to synchronize more than 10,000 mailboxes, a multi-deployment configuration is available and recommended.
Some use cases require a multiple-server configuration:
Meeting those targets requires deploying additional services into a cluster of multiple virtual or physical host systems.
This is a primary service that is responsible for the synchronization of data. This service is responsible for
This service provides the command and control center for a multi-node deployment of Riva. This service is responsible for maintaining load distribution.
Note: This is a passive service that does not need access to the synchronization connections or policies used by the sync service nodes. No "synchronization data" is sent to this service.
Configuration: Configure the Global Sync Configuration settings in the Configure Remote Management window.
Run-time management: Use remote management in the Riva CRM Service Monitor.
This service is responsible for reading the configuration to determine which users or mailboxes should be synchronized. Specifically, the User Gatherer collects users from sync policies (static lists), from the CRM (CRM Gather) or mail groups (Mail Gather). After the users are detected as being active, they are registered with the GSC.
Configuration: In the Configure Remote Management window, configure a Client Global Sync Configuration node to be a Provider.
Used to share calendar entry registrations between many users.
Note: This is a passive service that does not need any synchronization connections or policies.
This service has also been known as Calendar Management, Global Management, Global ID, or Global Calendar.
Configuration: Configure the Calendar GlobalID Manager settings in the Configure Remote Management window.
This service is also known as the Global Destination Entity Registry.
A significant risk to the system's integrity is possible if an individual mailbox started to synchronize
The GDR is used as a fail-safe component with the sole objective of preventing a mailbox from starting to synchronize on another node in the cluster because of misconfiguration or system failure.
Example scenario: if the GSC was lost or somehow corrupted, the GDR would prevent a user from synchronizing on a different node that may not have copies of the historical transactions.
Configuration: Configure the Global Sync Destination Registry settings in the Configure Remote Management window.
Tip: When the GDR has been activated, the detection of a misplaced transaction metadata folder can be used to prevent the sync. For more information, see Detect when transactions metadata has been misplaced.
Available in Riva 2.4.44 or higher, under every Riva Shared Service (RSS) node.
The List Service lists all of the instances of RSS's that are present on a RSS node, including the List Service itself.
Under the List Service folder, the Global Sync Configuration, Global Sync Destination Registry, or Global Calendar Management (GCM) can be selected to put it into maintenance mode, create a snapshot of its database, and put it back into production mode (by stopping maintenance mode). While in maintenance mode, the GCM database can also be cleaned up.
Configuration: The List Service requires no configuration.