Extend the Duration Historic Data Online is Retained

When you extend the Keep online for period you need to consider the configuration of your system and whether you have any existing historical data in the system.

Stand-alone Server

The procedure for a stand-alone server is described in see Specify the Duration to Retain Historic Data Online. If you extended the period it has no effect on any existing data on the system.

Multi-server system

The combination of servers you have configured in a multi-server system and the amount of data that you have in the system will determine the procedure in extending the Keep online for period. Before you proceed we advise you to refer to the topic Protect the Permanent Standby Servers

NOTICE

loss of data

When you extend the Keep online for period in a multi-server configuration you need to be aware of the effect of the Protect the Permanent Standby Servers when increasing online feature on the synchronization of data between Hot Standby Servers. If this is not carried out correctly you may lose online data.
Failure to follow these instructions can result in loss of data.

Extend the Keep online for period in a Multi-server system

 

This example illustrates how to extend the Keep online for period in a replacement Hot Standby server within a multi-server configuration consisting of 3 Hot standby servers only. We are extending the amount of Historic Data that will be kept online. The same procedure applies to Alarm Summary, Configuration Changes Auditing and Event Journal.

We have three hot standby servers with an existing Keep online for period of 156 weeks.

The replacement server is newly installed with ClearSCADA and has a default Keep online for period of 52 weeks.

To create the additional extended period of two years, which is active use the following procedure:

  1. Access the ClearSCADA Server Configuration Tool.
  2. Expand the Historic Configuration branch.
  3. Select the Historic data type.
  4. Enter the amended amount of time (in weeks) for the historic data to be retained in the Keep online fornweeks field.

  5. When you have defined the Keep online for period and deselected the Protect the Permanent Standby Servers when increasing online checkbox:

    Apply the changes to the server.

    In a multi-server system you need to ensure that the Protect the Permanent Standby Servers when increasing online check box is NOT selected on the server that you are configuring.

    At this stage the settings have been applied to the registry settings for the server, the settings do not take effect until you restart the servers.

  6. Once you have applied the changes you need to reset the Protect the Permanent Standby Servers when increasing online check box on the server that you are configuring.

    Apply the changes to the server.

    At this stage the settings have been applied to the registry settings for the server, the settings do not take effect until you restart the server. You need to connect the replacement server to the system network and restart the server to implement the new settings and synchronize the data.

  7. Check that the configuration is the same for each server.

Using the Server Status tool to verify the changes

When all the servers have restarted you can also check that the configuration is correct by using the Server Status tool. This check allows you to ensure that the Keep online for period was extended correctly.

  1. Access the ClearSCADA Server Status tool.
  2. For each of the servers expand the Historic branch.
  3. Select the Historian status information, the display should be similar to that shown below:

    For the example described where the Keep online for period has be extended without a protected period the Protected Period column should be clear.

    Typical view for a correctly configured system in this example.

    Typical view for an incorrectly configure system in this example.

    If you have configured the extended period with a protected period the Protected Period column indicates the length of the protected period.

    In the example described above this would not be a desirable outcome for any of the servers.

 


Disclaimer

ClearSCADA 2017 R3