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.
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?
- 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...
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
Technical Data and Configuration