How to Perform Complete System Backups, Parameter Readbacks, and Version Trail Archiving in SIMATIC PCS 7

In SIMATIC PCS 7, performing an effective backup of an S7-400 DCS requires a three-tiered approach: first, execute a CFC Parameter Readback (Chart > Readback) to upload live, online-tuned parameters (such as PID gains and alarm limits) from the controller into the offline engineering charts; second, generate a full multi-project archive (File > Archive) in SIMATIC Manager to package all AS, OS, and client databases into a compressed archive; and third, for regulated plants requiring FDA 21 CFR Part 11 compliance, utilize SIMATIC Version Trail to create timestamped, version-controlled audit archives.

The Three Tiers of DCS Backup: Parameters, Projects, and Audit Trails

Unlike standalone PLCs where a simple memory upload recovers the running program, a SIMATIC PCS 7 distributed control system cannot be restored merely by uploading blocks from the S7-400 CPU:
* An S7-400 CPU upload contains raw compiled machine code without chart structures, technological hierarchies, or WinCC graphic links.
* A true DCS backup must capture the complete engineering database—including hardware configurations, CFC charts, SFC state machines, and WinCC SQL databases.
* Furthermore, during normal plant operation, operators and process engineers continuously tune parameters online (adjusting PID gains, alarm thresholds, and totalizer scaling) via WinCC faceplates. If a project is archived without reading back these parameters, an eventual download will overwrite months of operational tuning with stale engineering values.

Tier 1: CFC Parameter Readback (Saving Live Controller Values)

To synchronize online operational parameters from the running S7-400 CPU into the offline engineering database:

Open CFC Editor:
* Open any CFC chart in the target AS program.
Execute Chart Readback:
* Select menu Chart > Readback....
Select Readback Scope:
* OCM parameters: Reads back only parameters marked with the Operator Control and Monitoring attribute (S7_m_c := 'true'). This captures setpoints, alarm limits, and tuning parameters adjusted via WinCC faceplates.
* All parameters: Reads back every parameter across all blocks (used during major plant commissioning).
Compile and Download Changes:
* Once readback finishes, execute Chart > Compile > Changes Only.
* Perform an AS download: PLC > Download > Changes Only. This synchronizes the offline and online compilation timestamps, ensuring subsequent online edits do not require a full CPU stop.

Tier 2: Multi-Project Archiving via SIMATIC Manager

To create a complete, transportable backup of the entire control system:

Open SIMATIC Manager:
* Ensure WinCC projects are closed on all engineering and server stations to allow SQL databases to detach cleanly.
Execute Archiving:
* Select menu File > Archive....
* In the dialog, select the Multi-projects tab.
* Select the active multi-project and click OK.
Configure Archive Destination:
* Choose a secure target directory on a local secondary drive (e.g., D:\PCS7_Backups\Site_PlantA_20161019.zip).
* Allow the compression engine (Internal PKZip or WinZip) to package the multi-project.
* The resulting single .zip file contains all AS programs, hardware configurations, OS server databases, and client projects.

Tier 3: Regulatory Compliance with SIMATIC Version Trail

In pharmaceutical, chemical, and nuclear facilities requiring strict compliance with FDA 21 CFR Part 11:

SIMATIC Version Trail:
An optional PCS 7 engineering package that integrates with SIMATIC Logon.
In Component View, select File > Versioned project > Archive....
Version Trail prompts the engineer for an electronic signature, version tag (e.g., v2.4.1), and a mandatory change description.
It stores the archive in a secure, tamper-evident repository and automatically records who created the backup, the exact timestamp, and the justification into the system audit trail.

Comparison of PCS 7 Backup and Archiving Methods

The table below compares the functional scope of the three PCS 7 backup mechanisms.

Backup MechanismScope of Data CapturedCaptures Live Tuning?Captures OS Projects?Compliance / AuditingCFC Parameter ReadbackController block parameters onlyYes (Online values)NoEngineering synchronizationMulti-Project ArchiveEntire multi-project (AS + OS + NetPro)Only if Readback was runYes (Full databases)Standard engineering backupSIMATIC Version TrailVersioned multi-project with audit logsOnly if Readback was runYes (Full databases)FDA 21 CFR Part 11 compliantCPU Block Upload (Upload to PG)Raw STL/DB code (No CFC charts)Yes (Memory image)NoEmergency disaster recovery only

Verification

To confirm that the backup is valid and restorable:
1. After performing CFC Readback, open a tuned PID controller in CFC: confirm that Gain and TI match the live values displayed on the WinCC faceplate.
2. Check the generated .zip archive file size: verify that it is consistent with previous healthy backups (typically 500 MB to 5 GB).
3. Test retrieval in a sandbox directory: select File > Retrieve... in SIMATIC Manager and extract the archive to a temporary path.
4. Open the retrieved project: verify that HW Config, CFC charts, and WinCC OS projects open cleanly without missing file errors.

Limitations and Operational Precautions

Never attempt to backup a PCS 7 project by right-clicking the project folder in Windows Explorer and creating a zip file while WinCC is active; active SQL Server database locks will result in a corrupted archive.
Always perform CFC Parameter Readback before archiving; failure to do so guarantees that restoring the project will overwrite all site-tuned parameters with older values.
Ensure adequate disk space: archiving a multi-project requires temporary scratch space equal to at least 1.5 times the uncompressed project size.
When using Version Trail, validate licensing against the applicable Siemens catalog and authorized distributor quotation before deploying compliance features.

Engineer FAQ

Why should I not rely on 'Upload to PG' from the S7-400 CPU?

In PCS 7, the engineering system compiles high-level CFC and SFC charts into anonymous machine code blocks (OBs, DBs, FCs). Uploading from the CPU recovers only this raw code without chart structures, variable names, or WinCC linkages. You cannot continue engineering a PCS 7 plant from a raw CPU upload.

What is the difference between reading back 'OCM parameters' vs 'All parameters'?

'OCM parameters' reads back only values that operators can modify from WinCC faceplates (setpoints, limits, modes). 'All parameters' reads back internal algorithm variables as well. Reading back OCM parameters is faster and safer for standard operational synchronization.

Why does CFC require a compile and download after Readback?

Readback updates the offline database with online values. Compiling and downloading 'Changes Only' harmonizes the offline and online time stamps without altering CPU memory, ensuring subsequent changes can be downloaded bump-free.