You can migrate the earlier versions of Lifecycle Manager to the latest versions.

You can migrate vRealize Suite Lifecycle Manager 2.1 to 8.x or later. The migration also requires inputs, such as legacy vRealize Suite Lifecycle Manager hostname, user name, password, and SSH password. For more information, watch the Migration of vRealize Suite Lifecycle Manager with Easy Installer video:

Prerequisites

  • Verify that you have vRealize Suite Lifecycle Manager 2.1 version or later.
  • Legacy vRealize Suite Lifecycle Manager must have SSH enabled for the root user.

Procedure

  1. From the Easy Installer wizard, click Migrate.
  2. Enter the vCenter details where the new vRealize Suite Lifecycle Manager 8.x is installed.
  3. Select the data center in the vCenter Server, Compute Resource, and Storage.
  4. Enter the network configuration details.
  5. In the Password configration, enter the password which can be set to the vRealize Suite Lifecycle Manager root and admin password.
  6. If you want to deploy Identity Manager, then enter the password for admin, sshuser, and root credential.
  7. Enter the vRealize Suite Lifecycle Manager 8.x VMname, Hostname, and the IP details.
  8. Enter the legacy vRealize Suite Lifecycle Manager Hostname, Username, and Password.
  9. Select New Identity Manager Installation or Import Existing Identity Manager.
    If you have selected to install New Identity Manager, then it is deployed in the same vCenter Server mentioned in step 2. If you import an existing Identity manager, verify that the identity manager is already registered in the vRealize Suite Lifecycle Manager legacy VM and identity manager SSH is enabled for the root user.
    Note: A new installation of vRealize Suite Lifecycle Manager 8.x supports only VMware Identity Manager 3.3.4. The earlier versions of VMware Identity Manager will be supported only for an existing vRealize Suite Lifecycle Manager instance that is being migrated to vRealize Suite Lifecycle Manager 8.x and later. Upgrade support from earlier VMware Identity Manager version to the latest is only available if they conform to the vRealize Suite Lifecycle Manager supported criteria. Any earlier versions of vRealize Suite Lifecycle Manager 8.x allows only single instance of VMware Identity Manager to be deployed with the embedded connector and embedded postgresql database. Upgrade of VMware Identity Manager within vRealize Suite Lifecycle Manager 8.x to the latest versions will be supported if it conforms to the mentioned criteria. Else the upgrade has to be performed outside vRealize Suite Lifecycle Manager. After you upgrade, it can any time be reimported by triggering Inventory Sync in vRealize Suite Lifecycle Manager 8.x.
  10. Click Submit.
  11. When the migration is successful, click the vRealize Suite Lifecycle Manager URL or the migration request to view the progress by logging in with admin@local with the password given in step 5.
  12. All the environments with data centers, vCenter Servers, Settings (such as NTP, DNS, and so on), content endpoints that are managed by older Lifecycle Manager are migrated and the environments are imported to the latest version.

Results

As part of migration, create a global environment based on installation or import when you import legacy vRealize Suite Lifecycle Manager VMware Identity Manager to vRealize Suite Lifecycle Manager 8.x. If there is a failure in the global environment, it can be due to the missing ssh user password in the legacy vRealize Suite Lifecycle Manager. Enter the SSH password details by selecting the correct password on retry and submit the changes to create a global environment. Once a global environment is created, you can resume the migration operation.

With migration you can create environments, settings, certificate and so on. You can check the status of migration on the Request status.
Note: If you import an existing VMware Identity Manager and if the admin password is different from the SSH user for the VMware Identity Manager, then the global environment request fails. In this case, add the SSH password in the locker app manually and retry the request with this password.