First some general remarks.

• Yes, SLDMS is the process that takes the initiative to synchronize files both in the cluster and in a failover-pair.  This happens in real-time or scheduled:
  • Real-time: when agents have contact with eachoter, file changes are exchanged immediately.  This is the default behavior.
  • Scheduled:
    • when re-connecting: when 2 DataMiner nodes lose contact, and file changes happened during that time, upon reconnecting the necessary files get synched.
    • at midnight, 2 DataMiner nodes that have contact validate the current sync status, and where needed take action.
• Communication between 2 DataMiner nodes (via SLNet process) is from version 10.0.13 by default encrypted.  On the older versions, you can also activate this encryption.  How to do it is specified here.

To repeat your specific questions:

1. Is the SLDMS process also responsible for Failover’s data synchronization?
   • yes, it keeps track of what needs to be synched and takes initiative to get it synchronized.
2. Is data synchronization by DataMiner done by a secure protocol?
   • yes, by default since 10.0.13 but can be activated
3. How often and when is the data synced?
   • by default in real-time when the change happens, but some backup mechanisms are in place.

Additionally about a Failover configuration:

1. Is data synchronization by DataMiner done by a secure protocol?
   • yes, by default since 10.0.13 but can be activated
2. How often and when is the data synced?
   • by default in real-time when the change happens, but some backup mechanisms are in place.
   • In a failover setup, we also have the database.
     • MySQL setups: there is an intermediate file offload on the online DMA which gets pushed every minute to the offline DMA, where it then gets pushed to the database.
     • Cassandra setups: the 2 Cassandra nodes form one cluster, so the data is available in both in real-time.

Regards