redundant BATCH server. Inconsistent BATCH process cell data between redundant partners
could lead to the following situations, for example:
● Messages and measured values are recorded on the master (CDV on) but not on its standby
(CDV off).
● Communication between the redundant BATCH servers may be faulty.
● Errors may occur in the recording of messages and measured values by the PCS 7 OS.
● Completely different BATCH process cells may be present on the two BATCH servers
because the databases are not synchronized.
Additional information
BATCH engineering (Page 178)
3.5.5.9 Automatic hot restart
What safety strategies are there when using redundancy?
A redundant server pair provides protection for your process against failure. New mechanisms
are available to ensure that there is a failover and hot restart if a problem occurs.
● Prevention on exiting a SIMATIC server application with redundancy
● Automatic hot restart of server applications after problem; cannot be recognized by the user
● Isolation of SIMATIC BATCH server in an error state
● Isolation of the server applications in an error state
● Automatic hot restart of a SIMATIC BATCH server after status check of the partner server
Prevention on exiting a SIMATIC server application
If you want to exit a SIMATIC server application (WinCC server, BATCH server, Route Control
server) for whatever reason, you must make sure that the partner server is fully capable of
taking over. In other words, all the applications running on the server must also run on the
partner server and be ready for operation.
If the result of the application check is negative, a warning dialog is displayed when you exit
a server application informing you that the partner server is not fully capable of taking over
and you will be asked whether you really want a redundancy changeover to the partner server.
If you click "Yes", the server application will be exited even though the partner server is not
ready to take over.
If you click "No", the dialog will be closed without any action being taken.
Automatic hot restart of SIMATIC server application
An automatic hot restart does not require any operator control. The process runs in the
background. The BATCH server applications can be restarted automatically when a problem
occurred. This does not affect redundancy.
Product introduction and installation
3.5 Possible configurations
SIMATIC BATCH V8.2
64 Operating Manual, 02/2016, A5E35958174-AA
To Next Page
Loading...
Need help?
General
