You can start
with a fresh deployment of the v4.1 OVF after uninstalling an earlier version and then migrate the data from earlier version (3.x) to 4.1
version by using backup and restore path.
To migrate
from an earlier version to the OMIVV 4.1 version, perform the following
steps:
Steps
Take a backup of the database for an earlier (v3.x) release.
For more information about backup, see OpenManage Integration
for VMware vCenter User’s Guide available at Dell.com/support/manuals.
Power off the older appliance from vCenter.
NOTE Do not unregister the OMIVV plug-in from vCenter. Unregistering the
plug-in from vCenter removes all the alarms registered on vCenter
by the OMIVV plug-in and all the customization that is performed on
the alarms such as, actions and so on. For more information, see OpenManage Integration for VMware vCenter Quick Installation Guide for vSphere Web Client Version 4.1, if you
have unregistered the plug-in after the backup.
Deploy the new OpenManage Integration version 4.1 OVF.
For more information about deploying the OVF, see OpenManage Integration for VMware vCenter Quick Installation Guide for vSphere Web Client Version 4.1.
Power on the OpenManage Integration version 4.1 appliance.
Set up the network and time zone on the OMIVV appliance.
Ensure that the new OpenManage Integration version 4.1 appliance has the same IP address as the old appliance. To set
up the network details, see OpenManage Integration for VMware vCenter Quick Installation Guide for vSphere Web Client Version 4.1.
NOTE The OMIVV plug-in might
not work properly if the IP address for the OMIVV 4.1 appliance is
different from the IP address of the older appliance. In such a scenario,
unregister and re-register all the vCenter instances.
Restore the database to the new OMIVV appliance.
NOTE If you have enabled Proactive HA on clusters, OMIVV unregisters the Dell Inc provider for those clusters and re-registers the Dell Inc provider after restore. Hence, health updates for the Dell hosts are not available until restore is complete.
For more information, see Restoring the OMIVV
database from a backup in the OpenManage Integration for VMware
vCenter User’s Guide available at Dell.com/support/manuals.
Upload the new license file.
For more information about licensing, see OpenManage Integration for VMware vCenter Quick Installation Guide for vSphere Web Client Version 4.1.
Verify the appliance.
For more information about appliance verification, see the OpenManage Integration for VMware vCenter Quick Installation Guide for vSphere Web Client Version 4.1 to ensure that the database migration
is successful.
Run the Inventory on all the hosts.
NOTE
It is recommended that after the upgrade, you run the
inventory again on all the hosts that the OMIVV manages. For more
information, see the Running inventory jobs in OpenManage
Integration for VMware vCenter User’s Guide.
If the IP address of the new OMIVV version 4.1 appliance is changed
from the old appliance, configure the trap destination for the SNMP
traps to point to the new appliance. For 12th generation and higher
generation servers, the IP change is fixed by running inventory on
these hosts. For hosts earlier than 12th generation that were compliant
with earlier versions, the IP change is displayed as noncompliant
and requires you to configure Dell EMC OpenManage Server Administrator
(OMSA). For more information on fixing the host compliance, see Reporting and fixing compliance for vSphere hosts in OpenManage
Integration for VMware vCenter User’s Guide available at Dell.com/support/manuals.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\