Description

This article from InSource shows the process of backing up a Historian on an older server to use on a newer Historian Server.

• Author: Glenn Yancey
• Published: 05/07/2025
• Applies to: Aveva Historian 2020 and higher

Details

OLD Server 

Backup the Runtime DB and the History Blocks.

Runtime DB Backup

Runtime Database backup through the SQL Server Management Console. 

1. Under Databases, Right click on RUNTIME/TASKS/BACK UP.
   
2. Keep in mind the location of the .BAK file that has been created.    If you choose to create another location, select ADD.   If not, Choose OK to Back Up the Runtime Database.

History Block Storage Partition Backups

NOTE: Make sure you take note of the drives that are used for your Storage Partitions 

MAIN

Note: Most people only have data in the Circular directory.    That would be the directory to copy with its History Blocks.    Some also might have an Alternate Directory which is designed for cascading older History Blocks from the Circular directory, but by default is turned off, hence the “rr:\” placeholder for its drive. If the D drive is where your Circular data is kept, make sure that the new Server has that same drive already created.     The directory will be created on the new server through the Configurator tool.   It is still recommended that for EACH of the directories that you copy their contents.    DataIndex, DataIndexLog, and RevisionLog are located where they are optional to copy for MAIN. 

Today’s History Block will need to be copied over a later date as it is still in use by the Historian Server. 

AUTO SUMMARY

Note: The same thing for the MAIN partitions also applies for the AUTO SUMMARY locations.  It is RECOMMENDED to copy all of the contents for these directories as well.  AVEVA Historian maintains a separate auto-summary partition for storing automatically generated summaries used for faster retrieval over long time intervals. There, Historian generates a local replication entity and a one-hour summary tag for every analog tag in the system. As values arrive for an analog tag, Historian automatically computes and records a summary.

Auto-summary values are stored in their own History Blocks within the auto-summary partition. With auto-summarization, Historian can quickly and efficiently retrieve large-volume data for a long duration, even months or years.

NEW Server 

If using MS SQL Server Standard (Historian Tag Count more than 25,000 tags), THEN make sure that you install that PRIOR to install the AVEVA Historian Server.

OR

If using MS SQL Server Express (Historian Tag Count less than 25,000 tags), THEN it will install during the Historian Installation without need for a separate installation. 

CONFIGURATOR (1^st Time)

1. At the end of the installation, the AVEVA Configurator will open, we will make some modifications and then close out after these next steps.     
   1. Note: This technote is under the assumption that the System Management Server is turned ON.
      1. If other nodes in your system have the SMS turned off, then this Historian will need to have the SMS turned off as well.

Make sure that you have added your XML Entitlement File to the License Server through the License Manager on the License Server.  

This assumes that the License Server has already been setup and activated.    

2)  Select AVEVA Enterprise Licensing/Select License Server

Under the PRIMARY SERVER NAME, you will need to point to your License Server. 

Hit Test Connection and then Configuration.   

3) CLOSE out of the Configurator, which will require a REBOOT. 

4) Reboot New Server.

5) After reboot, Install the SQL Server Management Studio Tools (SSMS tools).   

LINK: https://go.microsoft.com/fwlink/?linkid=2257624&clcid=0x409

This is only required if you are using SQL Server Express…

This might require a REBOOT.

6) Restore the Runtime DB from its backup through the MS SQL Server Management Studio. 

Right click on a System Databases to Restore Database….

Choose Device, and point to the location of where you had restored the .BAK file that represents the RUNTIME Database backup.Select OK once it recognizes the Runtime databse. 

CONFIGURATOR (2^nd Time)

1. Start the Configurator on the New Server 
   1. (C:\ProgramData\Microsoft\Windows\Start Menu\Programs\AVEVA\Configurator).   
   2. Select SERVER under the AVEVA Historian Server.
   3. DO NOT SELECT to DROP AND CREATE NEW DATABASE as we are migrating from our existing Runtime DB.
   4. Select CONFIGURE.   This could take a few minutes.
   5. The DATA PATH is going to where you would restore your History Blocks in. 

2. Now Select Security under AVEVA Historian, and hit CONFIGURE

BEFORE YOU DO THE NEXT STEP, RESTORE Your History Blocks to the folders that mimicked.

3. Select Search and hit configure. 

4.  No need to select REPORTING and CONFIGURE as it will already be in green. 

5.  Select CLOSE and then REBOOT the Server.   

6.  After reboot, In the Operations Control Management Console tree, right-click the server (or group) and then click Edit Historian Registration Property. The Registered Historian Properties dialog box appears

a.  Enter your credentials for a user that has Administrator and aaAdministrator rights. 

b.  Keep “Use Windows integration authentication.

7.   Make sure that the IDAS references your Server name.    If not, RIGHT click on the IDAS to change its name through Properties. 

8.  Then RIGHT CLICK to COMMIT PENDING CHANGES.

9.  Now test using Trend to see if the Historian can access the Historian. You will need to copy today’s History block over TOMORROW to backfill for the time that the Historian was being migrated.  Trend files will need to be redirected to the new Historian. (NOTE: This shows Historian Client 2023)