If Duty Mode is enabled on the servers, the complete synchronization process works slightly differently—there are additional steps to allow the comparison of data between the Standby and Main servers and the merging of data into the Main server.
As with the complete synchronization process when Duty Mode is disabled, the process takes place when:
- A Main server establishes or re-establishes a connection with another server
- ClearSCADA is started on a Standby server that is connected to a Main server that is already running.
If Duty Mode is enabled on the servers, the complete synchronization process consists of these steps (which are performed in order):
- The Main server transfers some of its Boolean (Enabled/Disabled) server configuration settings to the Standby server: Exclusive Control, Event Journal, Historic Data, Historic Validation, Historic Files, Alarms & Events, Quality Classification, Alarm Response, and Configuration Changes Auditing. Only the Enabled/Disabled settings are transferred, the other settings for each of the features need to be configured manually.
- The Main server transfers any metadata (custom fields) to the Standby server.
- The Main server transfers the database structure to the Standby server. The database structure is the hierarchy of groups, database items etc.
- Configuration CRC (Cyclic Redundancy Checks) values are calculated from the specific configuration details of the database items. The Main server retrieves the configuration CRCs from the Standby server and compares them to the configuration CRCs on the Main server.
- Any configuration data on the Main server that has different CRCs to the configuration on the Standby server is transferred to the Standby server. This means that the configuration data is the same on both the Main server and Standby server.
- The time stamps of the data on the Main server and Standby server are compared. The data for each database item is examined individually, and the data with the most recent time stamps is used; the data with older time stamps is disregarded.
- Non-configuration data such as point states, time stamps, quality values etc., for database items is transferred from the Main server to the Standby server.
- Alarm data and event data is transferred from the Main server to the Standby server.
-
NOTE: Steps 1-8 inclusive are referred to as the ‘initial’ synchronization. When steps 1-8 have taken place, clients can connect to the Standby server and the remaining steps 9-14 continue in the background.
- Alarm Redirection data is transferred from the Main server to the Standby server.
- The historic files on the Standby server are compared to the historic files on the Main server. If the Standby server has historic files that are different to those on the Main server, the files are retrieved from the Standby server and merged into the Main server’s data.
- The Main server queries the file sizes and modified times of the historic files on the Standby server.
- Any historic files on the Main server that are different to the historic files on the Standby server are transferred to the Standby server. This will include files that have been modified for events logged since the last synchronization as well as any new historic files that have been created.
- The Event Journal files on the Standby server are compared to the Event Journal files on the Main server. If the Standby server has Event Journal files that are different to those on the Main server, the files are retrieved from the Standby server and merged into the Main server’s data.
- The Main server queries the file sizes and modified time stamps of the Event Journal data files on the Standby server.
- ClearSCADA detects if there are event journal files on the Main server that are different to the event journal files on the Standby server. If there are, the files that are different are transferred from the Main server to the Standby server. This will include files that have been modified for events logged since the last synchronization as well as any new files that have been created.
- The Main server transfers the historic files (generated reports) to the Standby server.
Each time a Main server connects to another server, the synchronization process has to take place. This means that the other server is regularly updated with the data on the Main server. The first time that this synchronization takes place is called a ‘first pass’. Following the completion of the ‘first pass’, the Main server and the other server will continue to synchronize on a regular basis. Each of these continuous synchronisations is called a ‘short pass’. A ‘short pass’ consists of the same steps as a ‘first pass’ but is completed more quickly as there is less data to be transferred and so the synchronization takes less time to complete.
During the ‘first pass’, steps 1-8 of the synchronization has to be completed before the Standby server can connect to the Main server (when Duty Mode is enabled). After step 8 has been completed, the Standby server can be used to access the database on the Main server. The remaining steps of the ‘first pass’ will continue to take place.
When the ‘first pass’ has completed, the Main server and the Standby server will continue to synchronize on a regular basis. The frequency of the continued synchronizations is set via the Transfer Interval and Interleave settings on the Partners section of the Server Configuration Tool (see Define the Transfer Interval and Transfer Timeouts).
The ongoing synchronizations that take place after the ‘first pass’ are called ‘short passes’ (see Short Pass’ Synchronization Process).
Further Information
‘First Pass’ Synchronization Process (Duty Mode Disabled)