Can SQL Server Mirroring Create a Standalone Backup of HistorianStorage?
Do not treat an independently configured SQL Server mirror of HistorianStorage as a supported Process Historian backup without a version-specific Siemens procedure. Siemens documents Process Historian's own SQL Server Mirroring design as a principal/mirror/witness redundancy system. That synchronized high-availability mechanism is distinct from an independently restorable backup; define the recovery objective and use the installed release's Process Historian Backup/Restore procedure.
Table of Contents
- Distinguish redundancy from backup
- Use Process Historian-managed recovery functions
- Define the recovery objective
- Verification
- Limitations and Operational Precautions
- Engineer FAQ
- Technical References
- Related Articles
- Related Tags
Distinguish redundancy from backup
The Process Historian System Manual (07/2024) describes Process Historian's own redundancy as Microsoft SQL Server Mirroring managed through a principal, mirror and witness. The principal writes configuration and runtime data; Process Historian synchronizes the database to the mirror. This is the product's redundancy architecture, not documentation for an independently administered second SQL instance that acts only as a no-failover clone.
Use Process Historian-managed recovery functions
For a supported high-availability design, follow the exact-version Process Historian redundancy configuration procedure, including its principal, mirror and witness requirements. For backup and retention, use the supported Process Historian Backup/Restore functions applicable to the installed release. The historical discussion does not identify the Process Historian version or SQL build, so a database-level schedule or restore procedure cannot be prescribed here.
Define the recovery objective
Specify whether the requirement is high availability, point-in-time backup, archive retention, or an exportable copy for disaster recovery. Establish acceptable data loss and recovery time, and confirm that the chosen PH version's documented feature meets it. A synchronized database copy may share corruption or accidental changes; do not call it an independent backup without a tested recovery design.
Verification
Test the chosen mechanism by restoring into an isolated supported environment and validating the expected historian time range through Process Historian clients or Information Server. Record backup age, completeness and recovery results; a successful SQL synchronization state alone does not prove a usable Process Historian restore.
Limitations and Operational Precautions
The official 2024 manual describes product-managed redundancy but does not document the requested standalone SQL mirroring arrangement. The question gives no Process Historian version, SQL Server version, size or RPO/RTO. Obtain Siemens confirmation before configuring SQL-level mirroring outside Process Historian; preserve an independently restorable backup.
Engineer FAQ
Does Process Historian use SQL Server Mirroring? Yes, its manual describes that as part of the built-in PH redundancy concept, with principal, mirror and witness roles.
Can I treat that mirror as an offline backup? No. The mirror is synchronized redundancy; a separate verified backup/restore plan addresses recovery.
Technical References
- SIMATIC Process Historian System Manual, 07/2024, A5E53524470-AA, section 3.3.2.7 “Useful information on the redundant Process Historian,” pp. 101–102; opened and read.
- SIMATIC Process Historian System Manual, 10/2022, A5E52028712-AA, administration and redundancy sections; opened for version-context cross-check.
Related Articles
Related Tags
SIMATIC Process Historian, SQL Server Mirroring, backup and restore