Migrating from 2.6.5 to 2.7.0

You cannot upgrade an IBM® Cloud Pak for Network Automation 2.6.5 instance to version 2.7.0. Instead, you must migrate your orchestration data to 2.7.0 by backing up the data in your 2.6.5 instance and restoring the data in a newly installed 2.7.0 instance.

About this task

Because the foundational software that underpins the IBM Cloud Pak® changed significantly for version 2.7.0, you must follow this backup-restore process to migrate your orchestration data. This limitation applies to version 2.6.5 installations in both connected and disconnected clusters.

Procedure

On the cluster where version 2.6.5 is installed, back up and verify the data.
1. Set up an S3-compatible bucket to contain your backup data. For more information, see Setting up S3 storage for backups.
2. Configure the backup custom resource settings in the orchestration CR. For more information, see Configuring backups by using the CLI or Configuring backups by using the console.
3. Create an orchestration data backup to run immediately. For more information, see Backing up by using the CLI or Backing up by using the console.
4. Shut down the IBM Cloud Pak instance. For more information, see Shutting down IBM Cloud Pak for Network Automation by using the CLI or Shutting down IBM Cloud Pak for Network Automation by using the console.
5. Verify that the backup data is good. For more information, see Verifying backup orchestration data.
Migrate your data to version 2.7.0 by completing one of these optional procedures:
- Optional: Migrate on the same cluster where version 2.6.5 is installed.
  1. Uninstall version 2.6.5. For more information, see Uninstalling.
  2. Install version 2.7.0. For more information, see Installing.
  3. Restore the data from the backup. For more information, see Restoring orchestration data.
  4. Restart the IBM Cloud Pak. For more information, see Restarting IBM Cloud Pak for Network Automation by using the CLI or Restarting IBM Cloud Pak for Network Automation by using the console.
  5. Update the PostgreSQL credentials in Vault, then verify that the IBM Cloud Pak is available. For more information, see Updating the PostgreSQL credentials.
- Optional: Migrate to a separate cluster where version 2.7.0 is installed.
  Attention: For this scenario, the terms primary cluster and recovery cluster apply, with the following definitions:
  - The primary cluster is the cluster where version 2.6.5 is installed.
  - The recovery cluster is the cluster where version 2.7.0 is installed.
  On the recovery cluster, restore the backup data by completing the steps in Recovering your primary cluster. You can ignore the requirement that the recovery and primary clusters must have the same IBM Cloud Pak operator version.