How historian is configured in connectivity server and where are the files stored.

The purpose is to configure historian in a connectivity server. I know there are log templates in library structure, Basic history service in service structure and log configuration aspect for data logging of desired object. But i want to know where the historain files are maintained and what method is used for archiving and restoration of data. To be clear, we wont be using a separate historain server.

Could you please help in this regard and refer some documents.

Also please mention what are the limitations to use historain on connectivity server.

Comments (0) New comment

sana Rank: 1005

Asked 5 years ago

Answer this question Follow

Voted best answer

The old "hard" statement of maximum retention period of 90 days for Basic History is no longer valid. Nowadays its only a recommendation, but frankly speaking - you can log several years with Basic History. It has been drastically underestimated.

If the answer is "No" to both questions below, go for the free & lightweight Basic History rather than anything else:

Q1) Is archiving of log data to an external archive media required?

Q2) Do you need to store more than 10 years worth of data?

Recommendations:

- Offload OperateITData from the C:\ drive

If at 5.1, use System Configuration Console to move Basic History storage off C:\

Before 5.1 the same can be done via registry and manual file copying (search AKS)

- Use a separate harddisk / logical volume for the logging (free from other usage)

- Use professional equipment (proper servers with some RAID redundancy level, write caching and high performance hard disks, e.g. SAS 15k rev)

- Do not use deadband compaction (exception deviation)

- Do not set Max Time equal to Min Time (always use 2x or more for Max Time if extrapolation is desired).

- Do not use inheritance or Auto-Instantiate for log configuration roll out. Use Bulk Data manager to create logs.

- Do not use Momentary Treatment in trends. Default trend treatment shall be Time Average. For shorter time periods (scopes) ExtMomentary can be used.

- For backup / restore / forced synchronization, consider plain file copying as an alternative to Backup External data in 800xA. Compression can do wonders on large files while performing backup. Do not move files in or out while the local Basic History service provider is enabled.

- The advhtarchivetool.exe (actually an online upgrade tool) can be used to merge data from a backup in to a running log.

- Settings like Min Time, Max Time, Storage Period, etc are *dynamic* values when using Basic History and can be adjusted at any time you like! Just remember what would happen immediately if Storage Period is changed from 520w to 52w...

/Stefan

Comments (6) New comment

by sana Rank: 1005 on 3/18/2015 11:36:12 PM | Like (0) | Report

Thanks for your insight.How historical data stored in OperateIT is restored in the 800xA system. Is advharchivetool a part of 800xA. How this tool is used?

by Stefan Stromqvist AKS expert

Rank: 1 on 3/19/2015 12:21:00 AM | Like (0) | Report

"How historical data stored in OperateIT is restored in the 800xA system" - I'm sorry but I don't fully understand your question here. Please explain further.

The use of the advhtarchivetool.exe is described in the upgrade user's guide. The tool's principal use is to inject missing data from the old system after online upgrade has been made. There is a short time gap during the upgrade where no logging takes place; the tool can fill the "gap" in the logs in the new system with data from the old system (that is kept running until the upgrade has completed).

by sana Rank: 1005 on 3/19/2015 1:21:33 AM | Like (0) | Report

Lets take a scenario where i have moved the historical log files into a separate hard drive. Now i want to retrieve the log data in the 800xA System, which tool\method would i use?
Also is there any application to view ".log" files?
Another query for my understanding: I have configured In.IOValue and Out.Forward.Value for log configuration, the log files saved in C drive would be separate for individual parameter (In.IOValue and Out.Value)and would be update on regular basis. Is that correct? Also What would be the maximum size of that file; is there a restriction on maximum size of .log file?

Another query: for AS+CS combined, there is a restriction of 1500 history logs. Is 1500 the total number of log configuration files? For our project, we need configuration of 2500 log files (3 properties per individual log configuration aspect)

Thanks in advance.

by Stefan Stromqvist AKS expert

Rank: 1 on 3/19/2015 10:05:42 AM | Like (0) | Report

The logs maintained by Basic History is best viewed/accessed from an OPC HDA client, e.g. the trend display aspect or the trend primitive in PG2/VBPG. Also Excel DataDirect and Smart Client can be used to view the logged data.

There is an offline viewing tool that can be used to view the log files (if Basic History has been stopped): AdvHtLogDataViewer.exe

There will be an individual log file for each logged property and log. A log template with 1 primary and 2 secondary (aggregated) logs, e.g. 1sec/1week raw into 1min/1month average into 10mins/2years will result in three (3) files per logged property.

Hard disk storage dissipated is roughly 25 bytes per logged data point.

There is no physical limit on size of log file. I have created 1s/10yrs logs (86400 x 365 x 10 = 315 million samples and 7700 MB file size. Such large logs might take a significant time to backup and to synchronize.

AS/CS combined restricted to 1500 logs, yes its true. But it is not stated if the log sample at 1second to 10seconds.

1500 1second logs equal 15000 10second logs...

With adequate hardware (with dedicated 15000 RPM SAS disks configured with a decent RAID level and write cache could probably buy you some extra capacity...)

If you are in doubt, please ask your regional ABB sales representative to assist you with getting a Temporary Sales Authorization, TSA approved for what is deviating from the System Guide rule set.

by sana Rank: 1005 on 3/19/2015 11:15:30 PM | Like (0) | Report

Thanks so much for the insight.
I just have a small confusion about "1500 history logs". Does it mean that C drive would not allow more than 1500 log files? Or it means only 1500 log properties (e.g. 1500 IO.Value for analog input) can be configured in AS+CS combined system.
Our requirement is to configure 3000 log properties (1500 IO.Value for AI and 1500 Out.Forward.Value for AI) and each log property has 1 primary log-1min/2days and 2 secondary logs-1hour/100days and 1day/300days.
Would it be possible to configure this much on AS+CS combined.

by Stefan Stromqvist AKS expert

Rank: 1 on 3/20/2015 1:34:57 AM | Like (0) | Report

There is no physical limitations. The amount of hard disk space available depends on how many hard disks you buy, not the number of roles you assign to the node (AS only or AS+CS).

The lesser number of logs permitted is connected to the additional duties a combined server need to handle - however there is more to it than just combined or not.

E.g.
Option 1:
1x Intel Xeon, Quad core, 2 GHz
No RAID. 7200 rpm SATA disks

Option 2:
2 x Intel Xeon Hexacore, 3 GHz.
RAID with write cache. 15000 rpm SAS disks.

In my view, option 2 with combined roles will be able to handle much more than option 1 and no combined roles.

With adequate hardware you should not have a problem with a few more logs than what is stated in the system guide.

Add new comment

Stefan Stromqvist AKS expert

Rank: 1

Answered 5 years ago

Answers

The historian files are kept in \industrial it data\history

Archiving is not possible you can not reload old data to have a look at it again. There is backup and restore, but that's for disaster recovery. Backup is configured in the maintenance structure (Backup definition aspect > change scope tab backup type to external services). Basic history is good for 90 days of data if I remember correct.

Please have a look in 3BSE038018 System 800xA System Guide Functional Description and in 3BSE038018 System 800xA System Guide Technical Data and Configuration

System Guide

Technical Data and Configuration

Comments (8) New comment

by sana Rank: 1005 on 3/18/2015 1:02:35 AM | Like (0) | Report

Since we don't have a historian server, would you recommend any work around?
Such as scheduling reports?

by sana Rank: 1005 on 3/18/2015 1:08:23 AM | Like (0) | Report

Also there is an 'Action' button in Status tab of 'Log Configuration' which gives four options: (Import data from file, Export data to file, Copy data to Clipboard, Restore log from backup); i think this option is helpful in archiving history manually.

by WvanWees AKS expert

Rank: 7 on 3/18/2015 1:09:34 AM | Like (0) | Report

If you want to save the data for later you could use scheduled reports. But that only works if you don't want to save a lot of information.

by sana Rank: 1005 on 3/18/2015 1:10:37 AM | Like (0) | Report

For Auto-archiving, I am thinking of using 'Action Aspect' in Job Description object in Scheduling structure. We can configure Action Aspect for 'Backup Action' and define desired archiving period. Would that work?

by WvanWees AKS expert

Rank: 7 on 3/18/2015 1:15:44 AM | Like (0) | Report

You can schedule the backup, but a backup is not the same as an archive. An archive can be used to view data from e.g. two years ago.

by sana Rank: 1005 on 3/18/2015 2:57:33 AM | Like (0) | Report

Since we are working towards a work around, would it be possible to schedule reports and make reports for lets say every 90 days. We could then work towards "archiving" a greater range of data back up this way?
Did I make any sense? :)

by WvanWees AKS expert

Rank: 7 on 3/18/2015 3:17:37 AM | Like (0) | Report

You could try that but don't know if it will take to long, also if excel fails to create the report you will miss 90 days of data. I would do it more often e.g. every week.

by sana Rank: 1005 on 3/18/2015 3:23:49 AM | Like (0) | Report

Thanks for the support! :)
So as per the base system license we have Primary history Logs of 3 months, and i checked the data is being saved in the connectivity server. But we can configure data logging in the Log config Aspect for more than 3 months, please define then how is the restriction of 3 months applicable?

Add new comment