Redundancy concept for drivers

[Asem Bani Salameh]

Good day all ,

We are facing an issue of wincc oa redundancy, that is the related to full servers switch over not a specific manager.

To illustrate more, as known in redundancy there is an active and passive servers each one holds the same managers , same config , etc.. , and in wincc you supply a feature of error state management .

My case is that if one of the servers has a corrupted manager assume BACnet driver and you suggest to put an error state for that driver such that wincc will detect that the error state of the active server is higher than the passive and will make a switch over to passive server . So currently the server that is running will have no corrupted managers .
But after a while another manger assume OPC or RDB manager is corrupted on the running server and I have configured the same or different error state .In that case I am between two options either to have a failure in bacnet driver or in OPC driver which is not logical or capable to have in any project .

So what I am asking about is if there is an option of having redundancy at the managers level , that means I can run the bacnet driver on server A while running the OPC driver on Server B simultaneously.

Regards and thank you

[leoknipp]

In WinCC OA only one server can be the active one.
The passive server will discard changes from the drivers as it is expected that the active server will get the messages and sends it to the passive one.

There is no possibility to get message from a driver which is running only at the passive server.
In that case you have to decide (by error state configuration) if a loss of connection for the BACnet driver is more critical than a loss of the OPC connection.

Best Regards
Leopold Knipp
Senior Support Specialist