Adding a Replication Server
- Last UpdatedApr 10, 2026
- 2 minute read
A replication server is a next-tier historian that receives and stores replicated data. The "next" tier depends on where the data is being sent from. A tier-1 historian replicates to its next tier, tier 2. The tier-2 historian replicates to its next tier, tier 3, and so on.
A replication server is configured on the lower-tier historian; that is, the one sending the replication data:
-
The tier-2 replication server configuration is defined on the tier-1 historian.
-
Tier 3 is configured on tier 2, and so on.
When you define the configuration for a replication server, you set up replication schedules, groups, and tags for that next-tier historian.
Important: Replication is not supported between a case-sensitive historian and a case-insensitive next-tier historian.
If the next-tier historian doesn’t yet exist or can’t be reached over the network, the information is held until the lower-tier historian can connect with an instance of AVEVA Historian on the next-tier computer. If the lower-tier historian cannot communicate with the next-tier historian for any reason, data accumulates in the designated store-and-forward path.
By default, AVEVA Historian creates a local replication server (named Local Replication) as part of the installation process. You can create replication tags that use this local replication server or another replication server.
When you create a new replication server, the system automatically generates replication groups for analog summary and state summary replication types using default replication schedules. For more information, see Adding a Replication Group.
A few default replication schedules are also created for your new replication server, and you can use these schedules to create replication groups.
The system also creates a list of system tags for each replication server. For more information on the default system tags, see Replication Subsystem Tags in the AVEVA Historian Concepts Guide.
AVEVA Historian supports replication to another AVEVA Historian, AVEVA Insight, AVEVA Data Hub, and AVEVA PI Server.