After a vRealize Operations Manager migration, you might notice certain changes to vCenter Operations Manager data and features.

Metrics status

Metrics that were disabled in version 5.x attribute packages will be enabled in the corresponding policy on the target if there are enabled symptoms defined that are based on those metrics.

Health, risk, and efficiency badges

After migration, health, risk, and efficiency might vary when compared to version 5.x. Version 5.x percentages were computed based on values and formulas that have different counterparts in this version.

For example, in version 5.x, efficiency was computed based on waste and density. In this version, it is based on highest criticality of all efficiency alerts on an object.

Capacity related badges

The workload, capacity, time remaining, stress, reclaimable capacity, and density badges might vary when compared to version 5.x because of changes in computations and the data set being considered.

For example, badges in version 5.x might be computed based on few months of data, but this version bases them on the last 30 days.

Authorization data; including user accounts, user groups, LDAP, and mapped privileges

Imported user privileges and configurations might be slightly different because of interface changes between vCenter Operations Manager 5.x and this version.

Super metric names

Migrated super metrics having the same name on the source become unique by having numbers appended to the names on the target.

Before:

superMetric
superMetric
superMetric

After:

superMetric
superMetric_1
superMetric_2

Super metric and resource kind association

Instead of associating super metric packages with resource kinds, super metrics are directly associated to resource kinds as shown in the following example for super metrics s1 and s2, and super metric attribute packages pk1 and pk2:

Before:

In pk1, s1 checked, s2 unchecked
pk1 associated with virtual machine resource kind
In pk2, s1 checked, s2 checked
pk2 associated with host resource kind

After:

s1 migrated and associated with virtual machine resource kind, host resource kind
s2 migrated and associated with host resource kind

Migrated super metrics can be enabled or disabled according to policy but are set by default at migration to disabled.

Policy names

Migrated policies having the same name on the source become unique by having numbers appended to the names on the target. The number corresponds to an internal policy ID on the source and can be used for troubleshooting between the target and source.

Migrated policies are also prefixed with the source IP address.

Dashboard contents

If a source dashboard widget displays data for a resource, and the resource is not migrated for any reason, the migrated widget will not display data.

For example, this happens when dashboard widgets display data from multiple adapters, and some source adapters did not have their target counterparts installed. Other causes might include unmigrated or unsupported metrics that the widget was configured to display.

Adapter-managed custom groups

Adapter-managed custom groups, such as Folder, are migrated as normal resources instead of custom groups.