Add AVEVA PI server as a replication server
- Last UpdatedSep 16, 2025
- 2 minute read
If you want to connect from AVEVA Historian to AVEVA PI Server as a next-tier server, follow these steps. Historian supports up to three total replication server connections to PI Server and CONNECT.
Note: If a tag's raw type is Integer but its minimum or maximum value is configured as a float value, the raw type will be changed to Float when it is replicated to PI Server. This applies to replication servers added in Historian SP2023 R2 SP1 and later. If a replication server was added in an earlier version of Historian, the raw type will not be changed from Integer to Float. Re-add the replication server if you want a tag’s raw type to be changed to Float from Integer if its minimum or maximum value is configured as a float value.
In order for the PI server to send data using the PI Web API:
-
PI Web API 2021 SP2 (1.16) or higher must be installed.
-
We recommend PI Web API 2023 SP1 or later to avoid a potential PI Adapter error: "The Send operation timed out."
-
Open Message Format (OMF) Services should be enabled. See OMF with PI Web API.
If you are already using the PI Connector for AVEVA Historian and you want to migrate to using AVEVA Historian replication instead, to avoid data gaps in the PI system you should leave the PI Connector running while configuring replication to AVEVA PI Server.
Follow these steps to migrate from using the PI Connector to using AVEVA Historian replication to PI Server:
-
Ensure the PI Connector for AVEVA Historian is running.
-
Configure all required tags for replication. See Configure tags to be replicated for more details.
Note: The Destination Tag Name for each replicated tag must match the existing tag name used by the PI Connector.
-
Verify that all tags are replicating correctly.
-
Shut down the PI Connector for AVEVA Historian.