The NETx Server does not synchronize the data that is stored within the SQL database. This includes trending values and test results of the NETx LaMPS module. However, it is possible to use synchronization features of the SQL database to provide a synchronization of the SQL data.
In principle, there are 2 two possible scenarios for using an SQL database with a main / backup solutions.
...
Within this scenario, the main and backup server are using the same SQL server instance. The following figure shows the situation where the main server is online:
| Drawio | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
In this situation, the main server is connected to the SQL instance. The backup server is inactive and thus not connected to the SQL instance. Now, consider that the main fails and the backup server is getting active. In this case, the backup opens the connection to the single SQL instance:
| Drawio | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
This solution has the advantage that is easy to configure. In addition, only 1 one SQL instance is required and no additional license fees for a an SQL synchronization are necessary. The drawback is that the SQL instance is a single point of failure. If the SQL instance fails, the data is not available for BMS functions like reporting. To increase the reliability of a single SQL instance, hardware redundant server systems or fail-safe virtual machines can be used.
...