Efficient database synchronization between partner servers in Geo SCADA Expert is essential for maintaining system reliability and performance.
The Process of Synchronizing Redundant Servers - Schneider Electric Community
Large data transfers or inefficient sync processes can lead to delays, increased network load, and potential downtime. To minimize synchronization time, consider implementing the following strategies:
-
Network Optimization
Ensure a stable and high-speed network connection between partner servers. Low latency and sufficient bandwidth are essential for reducing transfer delays. Use dedicated links or VPNs for secure and consistent performance.
- Data Volume Management
Reducing the amount of data eligible for synchronization is the most effective way to shorten sync time. Geo SCADA partners often exchange historic data, alarms, and configuration changes.
How to Implement:
- Archive Old Data
Configure historic and event data to become read-only after a short period (e.g., 2 weeks). This prevents old data from being repeatedly synchronized.
Reference: Reduce Synchronization Time by Enabling Data Archiving - Schneider Electric Community - Filter Unnecessary Data
For DNP3 points, use the Logged Data section on the Point Type tab to specify which retrieved point data Geo SCADA logs historically and which data it processes for alarms.
Reference: ConfigureLoggedDataProperties - Reduce Index Size
Limit the preloaded historic index to recent data (e.g., last 1 year) instead of indexing decades of records. This reduces memory usage and speeds up server startup and minimizes the amount of historic data eligible for synchronization. Reference: ManagetheSizeofthePrimaryIndex - Apply Historic Data Compression
Apply Historic Data Compression on the point’s Historic tab to filter out minor changes or rapid updates. Compression indirectly reduces sync time because fewer samples are stored in the writable historic window. Combine compression with archiving for maximum effect.
Reference: Historic Data Compression - Tip from Design Guidelines: Implement historic compression or significant change deadbands to restrict logging for historic points to below absolute maximum of 4 records per minute for each point.
- Archive Old Data
- Incremental Synchronization
Instead of transferring the entire database during each sync, use incremental synchronization to send only changes since the last update:
- Configure Significant Change Deadbands to prevent excessive updates. This ensures only meaningful changes are recorded and synchronized. Reference: Define the Criteria for a Significant Change in Value
- Note: Significant Change applies only to current data, not logged data.
- Schedule Synchronization Perform synchronization during off-peak hours to avoid network congestion and reduce the impact on real-time operations.
Summary
Combining Data Volume Management (archiving, filtering, compression) with Incremental Synchronization (Significant Change deadbands) andnetwork optimization can dramatically improve synchronization between Geo SCADA partner servers. These strategies enhance performance, minimize downtime, and ensure system scalability.
