Installing Historian in a Cluster Environment

Important: You do not have the latest version of Historian! You are missing out on the newest capabilities and enhanced security. For information on all the latest features, see the Historian product page. For more information on upgrades, contact your GE Digital sales agent or e-mail GE Digital Sales Support. For the most up-to-date documentation, go here.

Installing Historian in a Cluster Environment

Historian works with the Microsoft Cluster Service Manager to ensure high availability of the Historian server. If the primary Historian node in the cluster experiences difficulties, Historian is automatically started on another node to take over. Server high availability is managed through the Microsoft Cluster Service Manager.
  • Read the Important Product Information document and verify that all the prerequisites are properly installed.
  • Configure a failover cluster in Windows Server 2008 R2. For more information, refer to Configuring Clusters section in the Using Historian Administrator ebook.
  • To use Historian Alarms and Events in a cluster environment, select the appropriate SQL Server for both the Cluster Nodes.
  1. In Windows, go to All Programs > Administrative Tools > Failover Cluster Manager on any of the cluster nodes and make it the primary node.
  2. Install Historian on that node.
  3. Change the Historian Data path to the Cluster Shared Disk.
  4. Enter valid SQL Server details.
  5. Complete the Historian installation.
  6. After installing Historian on Cluster Node1, repeat steps from 1 to 5 for Node 2.

Configuring Historian Cluster Service on Windows Server 2008

Complete all of the following tasks to configure Historian Cluster Service.

Adding User-defined Resource Types to the Cluster Instance

If Failover Clustering is enabled on a machine, the Historian install will register two user-defined resource types in the cluster.

To ensure that the user-defined resource types are added to the cluster instance:

  1. In Windows, go to All Programs > Administrative Tools > Failover Cluster Manager.
  2. Right click the cluster instance and select Properties:
  3. If the Historian User defined resource types are not available, click the Add button.
    Select [HistorianInstallDir]/x64/Server/Historian.dll as the resource DLL with Historian and AlarmArchiver as both the resource type names and display names.

Adding Historian Service to the Cluster

  1. In the Failover Cluster Manager, right-click the cluster instance, and choose More Actions > Create Empty Service or Application..


  2. Rename the newly created, empty service. For example: Historian.
  3. Right-click the Historian empty service and choose Add a resource > More resources > 3 - Add Historian 7.1.
  4. Right-click the Historian empty service and choose Add a storage.
  5. Create the IP address and network name that allow access to a clustered Historian instance regardless of the actual node the Historian server resides on.
    1. Right-click the Historian empty service and choose Add a resource > 1 - Client Access Point.
    2. Enter the IP Address that will be used for clustered Historian.
  6. Add Historian resource dependencies:
    1. Right-click Properties on the New Historian 7.1 resource in the Historian service summary list.
    2. Click the Dependencies tab and add all three resources as dependencies to New Historian 7.1.


      You can now bring the Historian service online.

Adding Alarm Archiver Resource to the Cluster

  1. Right-click the Historian empty service and choose Add a resource > More resources > 1 - Add Alarm Archiver.
  2. Right-click Properties on the New Alarm Archiver resource in the Historian service summary list.
  3. Click the Dependencies tab and add New Historian 7.1 as a dependency.


    It should now be possible to bring the Alarm Archiver service online.
    Note: he Alarm Archiver resource does not require other dependencies like Cluster Disk and IP Address.

Configuring Generic Services

To configure Client Manager, Configuration Manager, Diagnostic Manager, Historian Embedded PostgreSQL Database, Historian Embedded Tomcat Container, and Historian Indexing Service, you must configure them as Generic Services in the Failover cluster as shown below:


Begin with configuring the Client Manager Resource Dependency, and then repeat the steps for the Configuration Manager, Diagnostic Manager, Historian Embedded PostgreSQL Database, Historian Embedded Tomcat Container and Historian Indexing Service.

  1. Right-click Properties on the Client Manager resource in the Historian service summary list.
  2. Click the Dependencies tab and add the IP Address dependency:


  3. Click Apply and click OK.
  4. Right-click Properties on the Client Manager resource in the Historian service summary list.
  5. Click the General tab and select the Use Network Name for Computer Name option:


  6. Click OK.
  7. Repeat the steps in this procedure for the Configuration Manager, Diagnostic Manager, Historian Embedded PostgreSQL Database, Historian Embedded Tomcat Container and Historian Indexing Service.
    You can now bring the Historian service online: