How to Verify WinCC Redundancy Synchronization in PCS 7
To verify WinCC redundancy synchronization, check the synchronization status in the WinCC redundancy diagnostics and correlate it with the OS messages and archive state on both servers. If synchronization remains active after restoring a server, verify that the redundancy connection uses the intended network adapter in SIMATIC Shell and the WinCC redundancy configuration. In the reported case, correcting the SIMATIC Shell card configuration resolved the issue, but that observation is not a universal diagnosis.
Table of Contents
- What to observe
- Check the redundancy connection
- Check synchronization evidence
- Interpret the reported resolution
- Operational precautions
- Limitations and Operational Precautions
- Verification
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
What to observe
Distinguish a synchronization process that has started from one that has completed. The ticket refers to REDRT process alarms for synchronization start and finish and to archive files under the project's ArchiveManager folders. Those are diagnostic clues; inspect them in context with the active server and the project's configured archives.
Check the redundancy connection
The WinCC redundancy documentation states that the network adapter used for redundancy status synchronization must be selected in the redundancy settings. Compare the selected interface with the physical network path intended for server-to-server redundancy. Use the WinCC/SIMATIC Shell configuration appropriate to the installed version; do not change the adapter while relying on the redundant pair for production continuity.
Check synchronization evidence
- Record which server is active and when synchronization began.
- Review process alarms for the synchronization start and finish messages.
- Inspect the WinCC redundancy status on both nodes and confirm that it reaches the completed/synchronized state.
- Check whether expected archive data is being synchronized in the configured Tag Logging and Alarm Logging archive paths.
- If synchronization stalls, compare the SIMATIC Shell redundancy adapter and network connectivity on both servers.
Interpret the reported resolution
The original poster later reported that the SIMATIC Shell card configuration was the cause. That is evidence for this installation only. The thread does not identify the exact adapter setting or provide a reproducible before/after configuration, so engineers should compare against their own approved topology and Siemens manual.
Operational precautions
Restoring a server, changing redundancy links, and testing failover can affect operator availability and archive continuity. Preserve logs and current settings, follow site change control, and perform any connection or switchover test in a controlled window.
Limitations and Operational Precautions
Confirm version applicability and operational impact before changes to a running control system. Use approved backup, testing, change-control and rollback procedures.
Verification
Verify configuration and observable runtime behavior against the intended process requirements.
Engineer FAQ
What should be checked first? Start with the exact product version, affected station, recent changes, and the first timestamped diagnostic evidence.
Does one successful restart prove the fault is fixed? No. Confirm stable operation over the conditions that previously exposed the problem.
Should settings be changed on a running plant? Use the site change-control process and schedule a controlled test with a rollback plan.
Can one symptom identify the root cause? No. Correlate the symptom with logs and configuration from the affected components.
What information should be recorded? Record versions, topology, timestamps, relevant logs, configuration state, and the result of each controlled test.
Is a forum workaround a manufacturer procedure? No. Treat an individual report as an observation unless applicable manufacturer documentation confirms it.
Should both redundant nodes be checked? Yes. Compare their versions, network configuration, service state, and event records.
Does a green status icon prove end-to-end operation? No. Verify the actual communication or process behavior that matters to the application.
What is a safe way to test a proposed correction? Use a representative test environment or approved maintenance window, and verify recovery before returning to service.
When should the issue be escalated? Escalate with reproducible steps, exact versions, event logs, topology, and evidence from both affected and healthy states.