View Source

From version 3.0.0 onward, iDNA Applications upgrade packages will not be backwards compatible with the CentOS-based appliance that was used with iDNA v2.x. This article outlines the necessary steps to set up a v3 Alma Linux appliance and migrate data from the old appliance.

Our previous operating system CentOS Linux 7 will reach end of life (EOL) on June 30, 2024. Please see the official announcement by Red Hat for more details.

panagenda provides new virtual images based on Alma Linux 9, a RHEL based open source Linux distribution. We encourage all customers to migrate their installations to the new virtual image.

Download the new iDNA v3 Alma Appliance

VMWare: OVA File / MD5 Checksum

Deploying the new Appliance

Resource requirements are similar to the CentOS appliance so sizing should be similar as well
- The backup files created during the migration will take up 10-30% of additional disk space on the /opt/panagenda/pgdata partition of the new appliance and should be considered when sizing the new disk.
- Contrary to CentOS guidelines, the new recommendation for partitioning the Alma appliance is to extend a single disk to the required size. Adding additional disks is still possible, but there should slight performance edge with a single disk.
Disk Partitioning Guide
Initial OS Configuration Guide

Data and Configuration Migration

Both appliances need to be running at the same time and the old appliance has to be reachable from the new appliance on ports 22 and 5432
iDNA_Applications_v3_MigrationGuide.pdf

Post-migration Tasks

Like in conventional version updates it will require one run of the nightly processing tasks on the new appliance for all features to be available.
After successful migration, iDNA should not be re-started on the old appliance. However, panagenda recommends not to decommission it until all functionality (including data collection) has been verified on the new appliance.