Failure, Switchover and Return of Fault-tolerant Components
6.10 Guidelines for updating a redundant OS in runtime
The system reacts as follows:
● Client_1 is connected to Server_2 or deactivated.
Result after Phase 4
● Server_1 is master server in the PCS 7 project.
● The updated Server_2 is standby server in the updated PCS 7 project.
● Client_1 is updated (deactivated or connected to Server_2).
● OS Client_2 is interconnected with its preferred Server_2.
6.10.7
Phase 5: Updating Server_2
Introduction
While you perform the steps in phase 5, your system runs only with Server_2. The system
remains controllable from the OS clients that were updated in phases 2 and 4.
Perform the steps without extended interruptions because the redundancy is not available
during the update.
Initial situation before phase 5
● Server_1 is master server in the PCS 7 project.
● The updated Server_2 is standby server in the updated PCS 7 project.
● Client_1 is updated (deactivated or connected to Server_2).
● OS Client_2 is interconnected with its preferred Server_2.
Requirements
● The PCS 7 project you are updating has already been updated on the ES.
● Archive synchronization is complete. Message: "REDRT: <Name of the OS server>
● If you are using storage (StoragePlus), make sure that storage is complete.
● Make sure that at least one updated OS client is interconnected with Server_2.
204
CAUTION
complete".
If no OS client is interconnected with Server_2, your system is not controllable while you
are updating Server_1.
Fault-tolerant Process Control Systems (V8.0)
Function Manual, 03/2012, A5E02779471-02