Migrating Historical Data between Historians
- Assistance from IDX 8 Tag Manager: The first step in migrating data often involves ensuring the tags for the data to be migrated already exist or are setup in the new historian. IDX Tag Manager allows the tag configurations to be automatically synchronised between systems before the migration takes place thus averting having to perform this process manually.
- Source/Target Plugins: It is possible to migrate from any supported source historian to any supported target historian, which currently includes the Wonderware (InSQL) Historian, OSISoft Historian and IDX Historian. Plugins can be developed to meet other requirements on request.
- Jobs and Batches: The migration tool carves up the data under migration into various levels of repeatable work items. The first step is to define a job which runs as a Windows service that encompasses a configured set of tags over a specified time period. Once a job is configured, the migration tool automatically creates a set number of work batches to be executed that equally divides the job data to be migrated. The two principle advantages of using the job/batch approach are:
- Parallelisation: today’s computer hardware benefit from parallel operations. This speeds up the migration process considerably.
- Recoverability: because the migration process is divided into batches, any batch can be resumed, re-executed or analysed as required.
- Data Analysis and Reporting: Post migration, the migration tool provides the option of analysing and comparing the data from the source and target historians at the batch level, allowing for greatly simplified side-by-side data comparison. It can also be configured to automatically highlight anomalies in the migrated batches that require further investigation. The provided analysis reporting can be used to provide an overview of the result of the complete migration.
|Migration job summary page illustrating pre-creation of job batches and batch status|