Master/Slave Server Data Archive Synchronization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In technical systems with redundant operator station servers, such as those in process or manufacturing systems, the occurrence of a 'master/master scenario' leads to independent filling of measurement archives, resulting in potential data loss and increased storage needs when trying to synchronize data post-recovery.

Innovation Solution

A guiding system that continuously stores data received from the technical system in respective data archives on each operator station server, taking into account the health status and role (master or slave) of each server, to effectively synchronize the data archives and ensure high-quality data storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If both operator station servers independently store data in their respective data archives during a master/master scenario, then data availability is maintained, but data consistency deteriorates and storage requirements increase

Engineering Contradiction:
Improvedata availabilityVSAvoiddata consistency
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The system performs preliminary actions by continuously storing health status and master/slave role information in the data archives during normal operation. This preparatory data collection enables later synchronization and conflict resolution when master/master scenarios occur, as the archived health information allows the system to determine which server had better health status during the period of independent operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms by continuously monitoring and archiving the health status of each operator station server. This feedback information is then used during synchronization to resolve data conflicts - the server with better archived health status has its data prioritized, ensuring data consistency while maintaining availability during and after master/master scenarios.

Inventive Principle:
Principle #23Feedback

2Reliability

If both operator station servers independently store data in their respective data archives during a master/master scenario, then data availability is maintained, but storage requirements increase

Engineering Contradiction:
Improvedata availabilityVSAvoidstorage requirements
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system merges the data archives of both operator station servers during synchronization. By combining the archived data from both servers and using health status information to resolve conflicts, the system eliminates duplicate storage of identical data while maintaining availability. The synchronization process consolidates the separate archives into a unified data set.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If the slave takes over the function of the master immediately upon failure detection, then system availability is maintained, but data synchronization complexity increases

Engineering Contradiction:
Improvesystem availabilityVSAvoiddata synchronization complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by continuously archiving health status and role information before failures occur. When the slave takes over as master, this pre-stored information enables automatic synchronization without complex real-time negotiations. The slave can immediately assume the master role and later synchronize using the archived health data to resolve any discrepancies.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4141594B1Detailed comparison of local archives in master/master scenarios of servers of a technical facility
Publication Date: 2025.04.30 SIEMENS AG
  • EP4141594B1 patent drawingFigure 1
  • EP4141594B1 patent drawingFigure 2
  • EP4141594B1 patent drawingFigure 3

AI summary

A control system (12) for a technical plant, in particular a process or manufacturing plant, is proposed, comprising a first operator station server (13) and a second operator station server, wherein one of these operator station servers (13) is configured to operate as a master and the other of these operator station servers (13) is configured to operate as a slave, and wherein the slave is configured to take over the function of the master in the event of the master failure, and wherein a first data archive (21) is implemented on the first operator station server (13), and wherein a second data archive is implemented on the second operator station server, and wherein the first operator station server (13) and the second operator station server are configured to receive data from the technical plant and to store it in the respective data archive (21).and wherein the first Operator Station Server (13) and the second Operator Station Server are each configured to determine a respective health status. The control system (12) is characterized in that the first Operator Station Server (13) and the second Operator Station Server are configured to continuously store in the respective data archive (21) at defined time intervals (t1, t2, t3, t4, t5, t6) the health status of the respective Operator Station Server (13) when receiving and storing the data of the technical system, and whether the respective Operator Station Server (13) functions as a master or as a slave in the respective time interval (t1, t2, t3, t4, t5, t6).