Add a replication server

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 Add 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, CONNECT data services, and AVEVA PI Server.

• Add AVEVA Historian as a replication server

• Add AVEVA Insight as a replication server

• Add AVEVA CONNECT as a replication server

• Add AVEVA PI Server as a replication server

Use a proxy server such as DMZ Secure Link between your local Historian server and replication server.

You may want to use a proxy server, that is, a server that is an intermediary between your local Historian server and the replication server. DMZ Secure Link uses a transparent proxy where an allowlist, maintained by AVEVA, enables connections from an on-premise system to AVEVA CONNECT easily and securely. This solution requires minimal configuration and no extra administration while offering the following advantages:

• DMZ Secure Link facilitates using AVEVA SaaS solutions in a segmented network architecture without exposing systems to the entire internet.

• DMZ Secure Link supports compliance and regulatory requirements.

• DMZ Secure Link can work with additional proxy servers to protect your network infrastructure.

To learn more about how to install and configure the product, see the DMZ Secure Link documentation.