Backup Solution for Continuity and Reliability
The backup systems of the NETx BMS Platform are essential for safeguarding configurations and data, ensuring operational continuity in case of failures or data loss. Regular backups cover all key components, including the Core Server, XLogic Editor, Web Manager, Visualizations, and SQL databases. Each component requires specific directories and files to be secured, such as configuration files, workspaces, and custom libraries. These backups enable seamless restoration of the system and support migration to new hardware or environments. By maintaining regular backups, the platform ensures data integrity, reliability, and minimal downtime.
Prevent Data Loss
Automated Processes
Many backup solutions allow for automated, scheduled backups, ensuring data is consistently updated without requiring manual intervention.
Quick Recovery
In the event of data corruption or loss, backups enable fast and efficient restoration, minimizing downtime and disruption.
Enhanced Security
Modern backup systems often include encryption and other advanced security features to protect data from unauthorized access and cyber threats.
Backups ensure data protection, quick recovery, automated updates, and enhanced security.
Backups ensure data protection, quick recovery, automated updates, and enhanced security.
Main/Backup Server Synchronization and Failover Process
Main/Backup Server Synchronization and Failover Process
1
When the main server is active, the backup server continuously synchronizes all data and stays up-to-date via the synchronization connection.
2
If the main server goes offline, the synchronization connection is interrupted, and the backup server seamlessly takes over full control, including communication with field devices and visualization clients.
3
Once the main server is back online, the backup server updates it with all current data before becoming inactive, allowing the main server to resume normal operation.
Technical Information
Technical Information
Two server instances operate on separate physical machines or virtual environments. The active server manages all tasks, while the standby server remains synchronized in real-time, ensuring it is fully prepared to take over if needed. This robust architecture ensures high reliability and uninterrupted system operations, with seamless transitions between main and backup servers, minimizing downtime and ensuring continuous system functionality.
- Active Server: Connects to the field network, communicates with devices, performs BMS functions (e.g., alarm management, scheduling, trend logging, and logic execution), and manages visualization client connections.
- Standby Server: Operates in parallel but does not perform tasks. It receives real-time status updates (e.g., datapoint values and configurations) from the active server via the synchronization connection, maintaining an identical system state.
- Main Server Failure: If the main server fails (e.g., hardware failure or restart), the backup server detects the lost synchronization connection and transitions to active mode. It assumes full control, connects to field devices, manages BMS functions, and handles visualization clients.
- Main Server Recovery: When the main server is restored, the backup server re-establishes synchronization, updates the main server with the latest data, and returns to standby mode, allowing the main server to resume control. Visualization clients automatically reconnect to the main server.
Synchronization capabilities vary depending on the interface or module:
- Fully Supported: KNX, BACnet, Modbus.
- Not Supported: Interfaces like VingCard, Kaba, and Salto lack software functionality for Main/Backup synchronization.
- PC-based Visualization: Fully supported, with automatic switching between main and backup servers. Only the active server accepts connections.
- Web-based Visualization:
- NETx Vision: Supports automatic switching with configurable connection settings.
- Standard Web Browsers: Requires DNS configuration for switching, as the standby server’s web port is inaccessible.
- Web Manager: Accessible on both servers, but the standby server allows only read-only access.
