[ISS Support Case] Historian Migration How To 11.0 - 23.0

Description

The old Historian is still in production. Basically, the client is running both App Server 2012 R2 and System Platform 2023 at the same time. Everything is replicated, both the hardware and software. The last step is to get the new Historian to read all the data from the old Historian so that the old Historian (and all the App Server 2012 R2 hardware and software) can be decommissioned. The new Historian does have a few more tags, than the old one, but we dont have to worry about them because I can run a query on those few tags before migrating the old historian data to the new historian. I tried shutting down the new Historian, deleting all the history blocks, copying the history blocks from the old historian, then restarting the Historian. This almost works, however, the data is spotty nulls occur in places in time they shouldnt, for example. Since just copying the history blocks from the old to new didn't work, I attempted the method shown here https://knowledge.insourcess.com/Operational_Efficiency/Historian/Implement_and_Support/Support_Tickets/Installation_and_Configuration/Installation_and_Configuration14/68223_-_Unable_to_see_data_in_imported_History_Blocks I made a backup of the Runtime and Holding database one the old Historian, copied them to the new Historian, and then attempted to restore them to the new Historian. I detached the Runtime database on the new Historian and selected Restore data base, then pointed to the Runtime data from old Historian. However, I received an error message that the Runtime database cant be restored because it is being used by the Runtime 11 database. See attached screenshot. What should my next steps be?

• Author: Kevin Modlin
• Published: March 7th, 2025

Details: