Subscribing is a smart move!
You can subscribe to this forum after you log in or create your free account.
First-time Install of ClearSCADA - Avoiding Protected Permanent Standby Historic streams' Protection
Geo SCADA Knowledge Base
Access vast amounts of technical know-how and pro tips from our community of Geo SCADA experts.
Invite a Co-worker
Send a co-worker an invite to the Exchange portal.Just enter their email address and we?ll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
📖 Home Back
A new feature, Protected Syncable Period, enables increases in historic data's syncable period on a Main server to be incrementally increased to protect a Permanent Standby server's older historic data.
However, this new feature makes a first-time install of a new/replacement hot standby server in a system more difficult. In short, when a new host is installed with ClearSCADA and the historic online/syncable life is increased to that already present in the system's other hot standby servers, the 'Protected Permanent Standby Servers when increasing online period' must be disabled for the duration of the initial configuration of the new server; once set-up the same as the other hot standby servers, the feature should be re-enabled.
The feature is described in the Help documentation, but let's just walk-through the set-up of Raw Historic Data on a newly installed host ...
NewServer_01_DefaultServerConfig_HRD.PNG
NewServer_02_DefaultServerStatus_Historic_p01_HRD.PNG
NewServer_03_DefaultServerStatus_Historic_p02_HRD.PNG
Oldest Writeable (and syncable) Record Time is 52 weeks before now (currently Jan 2018, 52 weeks earlier is Jan 2017)
NewServer_04_ServerConfigIncreaseOnline_HRD.PNG
On applying the change we have a warning that 104 weeks of protected Raw Historic data will exist.
NewServer_02_DefaultServerStatus_Historic_p01_HRD.PNG
NewServer_05_ServerStatus_IncreasedHistoricProtected_p02_HRD.PNG
Notice both the Raw and Suppression Historic streams are protected -- the configuration applied to both streams.
NewServer_06_ServerConfigRemoveProtection_HRD.PNG
Accept, 'Yes', the removal of the protected period, and restart the server and re-check the ServerStatus 'Historic | Historian' page:
NewServer_02_DefaultServerStatus_Historic_p01_HRD.PNG
NewServer_07_ServerStatus_IncreasedHistoricAvailable_p02_HRD.PNG
It is now possible to copy in the Raw Historic data, from the current time and back to Jan 2015.
It is advised that the 'Protected Permanent Standby...' feature is re-enabled immediately, so any further increases to the online/syncable period would result in protected periods.
This example merely examines Raw Historic Data, similar configuration exists for Journal (event) Historic, Configuration Change Historic and Alarm Summary Historic streams.
Go: Home Back
A new feature, Protected Syncable Period, enables increases in historic data's syncable period on a Main server to be incrementally increased to protect a Permanent Standby server's older historic data.
However, this new feature makes a first-time install of a new/replacement hot standby server in a system more difficult. In short, when a new host is installed with ClearSCADA and the historic online/syncable life is increased to that already present in the system's other hot standby servers, the 'Protected Permanent Standby Servers when increasing online period' must be disabled for the duration of the initial configuration of the new server; once set-up the same as the other hot standby servers, the feature should be re-enabled.
The feature is described in the Help documentation, but let's just walk-through the set-up of Raw Historic Data on a newly installed host ...
The initial online period is 52 weeks by default and the 'Protected Permanent Standby...' enabled, so the newly, first-time installed server will have:
NewServer_01_DefaultServerConfig_HRD.PNG
In ServerStatus we can see the highlighted 'Raw' streams active configuration matches the ServerConfiguration tool's settings
NewServer_02_DefaultServerStatus_Historic_p01_HRD.PNG
NewServer_03_DefaultServerStatus_Historic_p02_HRD.PNG
Oldest Writeable (and syncable) Record Time is 52 weeks before now (currently Jan 2018, 52 weeks earlier is Jan 2017)
Increasing the Raw Historic to 3 years (156 weeks) online, but with the feature still enabled,
NewServer_04_ServerConfigIncreaseOnline_HRD.PNG
On applying the change we have a warning that 104 weeks of protected Raw Historic data will exist.
Effectively, after a restart of the server, ServerStatus shows this protection is enabled,
NewServer_02_DefaultServerStatus_Historic_p01_HRD.PNG
NewServer_05_ServerStatus_IncreasedHistoricProtected_p02_HRD.PNG
Notice both the Raw and Suppression Historic streams are protected -- the configuration applied to both streams.
On a newly installed hot standby server, this is NOT the desired configuration. It is assumed that the 3 years' of historic data will be written to this new server, so the protected period needs to be removed ...
NewServer_06_ServerConfigRemoveProtection_HRD.PNG
Accept, 'Yes', the removal of the protected period, and restart the server and re-check the ServerStatus 'Historic | Historian' page:
The protection is removed, the highlighted Raw Historic data stream is now writeable and syncable for records up to 3 years old, to Jan 2015.
NewServer_02_DefaultServerStatus_Historic_p01_HRD.PNG
NewServer_07_ServerStatus_IncreasedHistoricAvailable_p02_HRD.PNG
It is now possible to copy in the Raw Historic data, from the current time and back to Jan 2015.
It is advised that the 'Protected Permanent Standby...' feature is re-enabled immediately, so any further increases to the online/syncable period would result in protected periods.
This example merely examines Raw Historic Data, similar configuration exists for Journal (event) Historic, Configuration Change Historic and Alarm Summary Historic streams.
Go: Home Back
Author
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.