Set Up High Availability of the Historian Server

About this task

In a cluster environment, multiple servers are installed, which share the same data. Each of these servers is called a node. One of them acts as the primary server, while the others are standby servers. If the primary server is down, one of the standby servers is used.

Historian works with Microsoft Failover Cluster Manager to ensure high availability of the server.

Before you begin

  1. Ensure that your network is enabled for multicast traffic.
  2. Create a shared drive on your network that all the servers in the cluster can access, and create a database folder in that drive.
  3. On each node that you want to add to the cluster:
    1. Install the Failover Clustering feature.
    2. Install the Historian server. During the installation, in the Historian Data Path field, enter the path to the folder on the shared drive that you have created.

  4. If you are upgrading the Historian server on a passive node, an error message may appear behind the installer screen, stating that the Archives directory is not created. You can ignore this message, or you can make the node active before upgrading the Historian server.

Procedure

  1. If you have upgraded the Historian server, on all the cluster nodes:
    1. Right-click the cluster, and then select Properties > Resource Types.
    2. If the user-defined resource types are not available, select Add.
    3. Select <Installation folder of the Historian server>/x64/Server/Historian.dll as the resource DLL path with Historian and AlarmArchiver as both the resource type names and display names.
    The Historian servers are now part of the cluster, thus achieving high availability. The remaining steps are required only for first-time installation of the Historian server (not upgrade).
  2. Access the primary node of the cluster.
  3. Create a failover cluster.
  4. Add a storage to the failover cluster.
  5. Add user-defined resource types, Historian and AlarmArchiver, to the cluster. These resources are created when you install the Historian server.
    1. Right-click the cluster, and then select Properties > Resource Types.
    2. If the user-defined resource types are not available, select Add.
    3. Select <Installation folder of the Historian server>/x64/Server/Historian.dll as the resource DLL path with Historian and AlarmArchiver as both the resource type names and display names.
  6. Select Roles > Create Empty Role.
    A role is created.
  7. Add the Historian application to the cluster:
    1. Select the role.
    2. In the Actions section, select Add Resource > Historian.
    3. Follow the on-screen instructions to add the new Historian resource to the role.
  8. Add a client access point to the role:
    1. Select the role.
    2. In the Actions section, select Add Resource > Client Access Point.
    3. Follow the on-screen instructions to add a client access point to the role.
  9. Add a storage to the role:
    1. Select the role.
    2. In the Actions section, select Add Storage.
    3. Follow the on-screen instructions to add the storage that you have created in step 3. You can use a storage only once.
  10. Add the following dependencies to the Historian resource:
    1. Double-click the Historian resource.
      The Historian Properties window appears.
    2. Select Dependencies.
    3. Select Insert, and add the following dependencies using the AND operation.
      • Client access point
      • IP address
      • Storage
  11. Add the Alarm Archiver resource to the cluster:
    1. Select the role.
    2. In the Actions section, select Add Resource > Alarm Archiver.
    3. Follow the on-screen instructions to add the alarm archiver resource to the role.
    4. Double-click the Alarm Archiver resource.
      The Alarm Archiver Properties window appears.
    5. Select Dependencies.
    6. Select Insert, and then add the Historian service as a dependency. You do not need to add the cluster disk and IP address as dependencies.
  12. Add generic services.
    1. In the Summary section of the Historian role, right-click the Client Manager resource, and then select Properties > Dependencies.
    2. Add the IP address as a dependency, and then select Apply.
    3. Select General, select the Use Network Name for Computer Name check box, and then select OK.
  13. Repeat the previous step for the following services:
    • Configuration Manager
    • Diagnostics Manager
    • Historian Embedded PostgreSQL Database
    • Historian Embedded Tomcat Container
    • Historian Indexing Service
    The services appear under the Historian role.

  14. Select the Historian role, and then in the Actions section, select Start Role.
    The Historian servers are now part of the cluster, thus achieving high availability.