Migrating an offline cluster to a new major version

To migrate a high-availability cluster to a new major version, you must stop the servers in a specific order, and then you migrate the primary server. During migration, the database server automatically removes secondary servers. After you migrate the primary server, you must rebuild the cluster by recreating all secondary servers. This procedure also applies if you want to upgrade a cluster to a new PID or fix pack that requires standard conversion procedures.

To migrate to a new version with high-availability clusters:

1. Stop the Connection Manager by issuing the oncmsm -k connection_manager_name command.
2. If you are using a High-availability Data Replication (HDR) secondary server as a backup server in case of contingencies:
   1. Quiesce the primary server by issuing an onmode -sy command to prevent user connections to the server.
   2. Force a checkpoint by issuing an onmode –c command on the primary server.
3. Stop the secondary servers in the cluster in the following order:
   1. If you have remote standalone (RS) secondary servers, stop them by issuing the onmode -ky command.
   2. If you have shared disk (SD) servers, stop them by issuing the onmode -ky command.
   3. If you have an HDR secondary server, stop it by issuing the onmode -ky command.
4. Stop the primary server by issuing the onmode -ky command.
5. On each server, set the INFORMIXDIR environment variable to the full path name for the target installation.
6. Ensure that all of the necessary configuration files are available in the target installation.
7. Optional: Enable quick reversion to a consistent restore point if the migration fails. Do this by setting the CONVERSION_GUARD and RESTORE_POINT_DIR configuration parameters. (For more information, see Configuring for recovery of restore point data in case an upgrade fails.)
8. Start the primary server by issuing an oninit command.
9. Ensure that the conversion to the target server was successful and that the server is in multi-user mode.
10. Start the Connection Manager by issuing an oncmsm command.
11. If you are migrating from pre-11.10 versions of Informix and need SD secondary servers on the primary server in a shared-disk cluster, set the primary server by issuing the onmode -d set SDS primary primary_server_name command.
12. Start SD secondary servers by issuing oninit commands.
13. Start the servers in the cluster and perform additional tasks in the following order:
14. Back up all logs. Then use ON–Bar or ontape to make a level-0 backup on the primary server to use to reestablish the RS and HDR secondary servers if necessary.
15. If you have RS secondary servers:
    1. Add RS entries on the primary server by issuing onmode –d add RSS rss_server_name commands.
    2. Start RS secondary servers with level-0 restore operations from the level 0 backup that was made on the primary server after migration.
    3. On RS secondary servers, run the onmode -d RSS primary_server_name command, and wait for the "RSS secondary server operational" message to appear after each command.
16. If you have an HDR secondary server:
    1. Reestablish the pair on the primary server by issuing an onmode -d primary hdr_secondary_server_name command.
    2. Start the HDR secondary server with level-0 restore operations from the level 0 backup that was made on the primary server after migration.
    3. On the HDR secondary server, run the onmode -d secondary primary_server_name command, and wait for the "HDR secondary server operational" message to appear after each command.
17. Perform any additional standard migration tasks described in Migrating to the new version of Informix and in Completing required post-migration tasks.
18. If you have Connection Manager configuration files that you created with a version of HCL Informix Client Software Development Kit (Client SDK) that is prior to version 3.70.xC3, you must convert the files. You must convert them because the older files are incompatible with the current version of the Connection Manager. For more information, see Converting older formats of the Connection Manager configuration file to the current format.