Migration Path to migrate from 1.6/1.7 to

Migration Path to migrate from 1.6/1.7 to 2.3

There is no RPM update support to this version from 1.7 or lower versions. You can migrate from older version (1.6 or 1.7) to the version 2.3 release using the Backup and Restore path. Also, the migration path is only supported from version 1.6 and 1.7. If you are at a lower version than 1.6, you will have to upgrade your appliance to the supported version before you perform the migration to OpenManage Integration for VMware vCenter version 2.3.

Do the following to migrate from older version to the OpenManage Integration for VMware vCenter 2.3 version:

1.Take a Backup of the database for the older release. For more information, See the section, Managing Backup and Restore in this guide.

2.Power off the older appliance from the vCenter.

NOTE: Do not unregister the Plug-in from the vCenter. Unregistering the plug-in from the vCenter will remove all the Alarms registered on the vCenter by the plug-in and remove all the customizing performed on the alarms like actions and so on, on the vCenter. For more information, see the section How to recover if I have unregistered the older plugin after the backup in this guide if you have already unregistered the Plug-ins after the backup.

3.Deploy the new OpenManage Integration version 2.3 OVF. For more information, see the section Deploying the OpenManage Integration for VMware vCenter OVF Using the vSphere Client in this guide to deploy the OVF.

4.Power on the OpenManage Integration version 2.3 appliance.

5.Setup the network, time zone and so on to the appliance. It is recommended that the new OpenManage Integration version 2.3 appliance has the same IP address as the old appliance. To setup the network details, see the section, Registering OpenManage Integration for VMware vCenter And Importing The License File in this guide.

6.Restore the database to the new appliance. For more information, see the section, Restoring The Database From A Backup in this guide.

7.Upload the new license file. For more information, see the section, Registering OpenManage Integration for VMware vCenter And Importing The License File in OpenManage Integration Version 2.3 Quick Install Guide.

8.Verify the appliance. For more information, see the section Installation Verification in this guide to ensure the database migration is successful.

9.Run the Inventory on all the registered vCenters.

NOTE:

It is recommended that you run the inventory on all the hosts managed by the plug-in again after the upgrade. For more information, see the section Running Inventory Jobs for steps to run the inventory on demand.

If the IP address of the new OpenManage Integration version 2.3 appliance has changed from that of the old appliance, the trap destination for the SNMP traps must be configured to point to the new appliance. For 12th generation and higher generation servers, this will be fixed by running the Inventory on these hosts. For all 11th generation or lower generation hosts that were earlier complaint, this IP change will show up as non- complaint and will require configuring OMSA. For more information, see the section, Running the Fix Non- Compliant vSphere hosts Wizard to fix the host compliance in the this guide.