Phase 5: Updating Server_2 - Siemens SIMATIC PCS 7 Function Manual

Fault-tolerant process control systems (v8.1)
Hide thumbs Also See for SIMATIC PCS 7:
Table of Contents

Advertisement

Failure, Switchover and Return of Fault-tolerant Components
6.10 Guidelines for updating a redundant OS in runtime
● 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.
Interrupted redundancy
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> complete".
– Using a Process Historian:
● Make sure that at least one updated OS client is interconnected with Server_2.
If no OS client is interconnected with Server_2, your system cannot be operated while you
are updating Server_1.
222
CAUTION
The data from the circular archive of OS server 1 is transferred or migrated to Process
Historian.
You can find more information on this in the
Notes documentation.
SIMATIC; Process Historian Installation
Fault-tolerant Process Control Systems (V8.1)
Function Manual, 11/2014, A5E34878832-AA

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents