My client has a water supply network in south Carolina.

My client's System info:

PCS7 9.0

- Virtualized system (Vmware) with two separate physical independent servers MSH1 & MSH2.

a. MSH1 has the following Virtual machines:

- Virtual machine A1 : PCS 7 Engineering station

- Virtual Machine A2 : WINCC OS CLIENT

- Virtual machine A3 : Wincc OS SERVER (MASTER) - for redundancy

b.MSH2 has the following Virtual machines:

- Virtual Machine B1 : WINCC OS CLIENT

- Virtual machine B2 : Wincc OS SERVER (Standby) - for redundancy

My client made a snapshot from Vmware ESXI on an activated (Wincc standby OS server) running on Virtual Machine. As soon as he took a snapshot following happened: 

1. The server got stunned and state of the server was that Wincc  (standby OS) server runtime initiated deactivation of Wincc os runtime on the standby server.
2. The server Windows os restarted automatically after Wincc was deactivated on it. 
3. After the restart of the windows, Wincc server os runtime was activated and synchronization began/completed successfully.

will this incident affect my client's overall system performance in any manner now or in the future. My client is running a critical water supply network using pcs7.

Oreca

Hi,

The easiest answer: snapshots are not supported.

It looks like the main server has detected an outage of the redundant server because of the snapshot. This most likely issued a reboot.

So solution: Do not take snapshots of if you really want only without WinCC runtime but as said: snapshots are not supported.

 

 But will this incident effect his system performance in future ?

Hi Peter,

From your description it sounds like WinCC itself detected an error and did a gracefull reboot and got up and running again so it sounds unlikely that there will be future problems because of this one incident.

What you can do is stop runtime on this server (and close the project) and then open the SQL Management Studio.

If you look in the WINCC SQL Instance, then all the databases that the project normally attaches, should be gone. If any are left then WinCC has problem disconnecting the databases.

In that case you can run the command "reset_wincc" and then reboot Windows.