Skip to main content
InSource Solutions

TN - 1048 Upgrade Historian to 2020



This article from InSource shows...

  • Author: Mike Viteri
  • Published: 10/28/2020
  • Applies to: Historian 10 and later


When upgrading the Historian you have two different paths depending on the products that are storing to the Historian.

The first is storing data directly to the Historian using InTouch or IO/OI drivers. The other is storing data using Application Server.

This article assumes that a new Historian 2020 sever is already installed and running. It is also assumes you don't have any custom database tables in your runtime database.

To do the upgrades you will need the older Historians available as you will need files from them to finish performing the upgrade


Intouch IO/OI data


We will look at upgrading Historian using Intouch or IO/OI Servers first.

  1. First you will need to go to the old Historian and run the import "Configuration Export and Import".


2. You will export the configuration from your old Historian. Select "Export from Historian to a text file". Click Next.


3. You should be able to take all the defaults. Make sure all objects is checked.Click Next.


4. Click Next then Finish. The Historian configuration will now be exported to a text file.


5. Copy Historian Database configuration file to new 2020 server.


6. Run the "Configuration Export and Import".Make sure "Import from a text file to Historian" is selected. Click Next.


7. Browse to the location of the text file you copied over. Click Next.


8.This dialog is letting you know everything will be overwritten. Click Next.


9. The import will run and show you what database items have been updated. If you get any errors here you will need to address them. Click Finish.


10. You will now need to go into the SMC and commit pending changes.


11. All tags,IDAS,Topics should have been import. The History Block storage locations might show the old location (E:\). These needs to be updated to represent the correct drive and folders if they are wrong Historian might not start up. Also the IDAS connections and Tier2 prefix will need to be updated as they will still reference the old Historian name.Once everything is updated assuming the network is same all of the IDAS connection will start collecting data automatically.


12. Now copy over the History Blocks from the Old Historian Circular folder to Historian Circular Folder to restore the history. Once copied over the old should now be readable.


Application Server

1. You should have your Historian 2020 with your galaxy converted but undeployed. Make sure your engines have the correct Historian name configured.


2. Deploy the galaxy. Once you deploy all the tags will be created in the brand new runtime database. This can be confirmed by going into Data Acquisition under Historian Status or using the Trend tool to look at data.

3.Once its confirmed data is being stored in the system.The history blocks from the old Historian Circular folder should be copied into the new Historian Circular folder.

4.Shutdown the Historian

5. in the old Historian go to the following folder Historian->Data->Support We are looking for the following files. This files contain the linking to the History Blocks from the old Historian.

  • taginfo.dat
  • taginfo-tagid.idx

Copy these over to the New Historian


6. We need to copy these two files into the second oldest history blocks. 



7. Start the Historian. Historian will read these files and create the proper records within the tag history table. Now you should be able to trend any tag data old or new.


If don't see data sometimes it is necessary to run a reindex on the Historian. That techntoe can be found in the link below.