Migrating data from PostgreSQL database 15.x to 17.x

Starting with the BMC Helix IT Operations Management version 25.2, we only support PostgreSQL database version 17.x. Therefore, you must use the PostgreSQL migration utility to migrate your data from PostgreSQL database to 17.x. 

Before you begin

• Make sure you run the Upgrade configuration utility.
• During the migration process, both versions of PostgreSQL (15.x and 17.x) will be running along with multiple other pods. For the migration to be successful, you must provision additional processors, memory, and storage.
  See sizing considerations for more information about the resources required for the migration.
• You can reclaim the resources after the upgrade.

To migrate data from PostgreSQL database version 15.x to 17.x

1. Navigate to helix-on-prem-deployment-manager/utilities/migration/postgres and locate the patroni-pg-migration.sh file.

2. To migrate your data from PostgreSQL database 15.x to 17.x, run the following command:

   ./patroni-pg-migration.sh migrate

   If you have turned on disaster recovery, the system will prompt you to turn it off. Type y to continue.
   
   PostgreSQL database version 17.x gets deployed, and data from PostgreSQL database 15.x is backed up and restored on PostgreSQL database 17.x.
   The time taken to migrate the data depends on the size of your data and your environment.
   
   After the migration, you will get the following message:
   The PostgreSQL database migration was completed successfully.

3. Perform a user acceptance test to make sure all data from PostgreSQL database version 15.x is migrated to 17.x.

   After the migration, application data continues to be sent to PostgreSQL database 17.x. 
   * To make sure there is no data gap, you must upgrade to BMC Helix ITOM 25.2 immediately after migration.

   * If you encounter an issue during the migration, please contact BMC Support.

Where to go from here