Phase 2: Updating Os Clients Interconnected To Server_2 - Siemens Simatic PCS 7 Function Manual

● Server_2 can be either master or standby, depending on the configuration.
● The archives will be synchronized between Server_1 and Server_2.
● Client_1 is connected to Server_1.
● Client_2 is either deactivated or interconnected with Server_1 after you have changed the
preferred server setting. Client_2 cannot access the upgraded Server_2 as the preferred
server.
7.10.4

Phase 2: Updating OS clients interconnected to Server_2

Introduction
In Phase 2, you update the OS clients that were interconnected with Server_2.
The system can be controlled at all times using Client_1, which is interconnected with the not-
yet-updated Server_1.
The same PCS 7 version is running on the active OS server Server_1 and on Client_1. Mixed
operation between OS clients and OS servers of different PCS 7 versions is not possible.
Archive data and messages that have accrued on OS server Server_1 during the update
process are available on both OS servers. Synchronization of the archives is complete with
the following message: "REDRT: <name of the OS server> finished". If Process Historian is
used, check the recoveries at the Process Historian Server and wait until they are finished, if
there are any queuing.
Interrupted redundancy
Perform the steps without extended interruptions because the redundancy is not available
during the update.
Initial situation before phase 2
● 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 connected to Server_1.
● Client_2 is either deactivated or interconnected with Server_1 after you have changed the
preferred server setting. Client_2 cannot access the upgraded Server_2 as the preferred
server.
Requirement
The PCS 7 project you are updating has already been updated on the ES.
High Availability Process Control Systems (V9.0)
Function Manual, 05/2017, A5E39221836-AA
Failure, switchover and reintegration of high availability components
CAUTION
7.10 Guide to updating a redundant OS in runtime
227