Logic applied to prevent duplicate attribute names during upgrade:

• In the top-level domain, if the upgrader finds an existing attribute that has a name that is the same as a new system attribute (for example, Location) it creates the system attribute and populates it with the list of values from the existing attribute.

• For multi-tenancy environments where there are multiple domains, if an attribute is found in both a parent and child domain, the child domain will not inherit the values but instead, the values of the attribute in the child domain will remain intact. See also, Attribute inheritance overrides in the NetBackup IT Analytics User Guide.

• If multiple attributes with the same name are encountered in the same domain (for example, a host Location attribute and an array Location attribute), the values from all the attributes with the same name (for all objects) are merged into the system attribute.

• The upgrader lists the attributes with the list of values that will be merged into the new System Attributes. You can choose to let the upgrader merge the attributes or you can stop the upgrade and use the steps provided to rename existing attributes.

  See Steps to Rename Duplicate Attributes.

• Merging of values ensures that all objects that have been assigned the attribute will retain this attribute with its values and therefore, reports that use the attributes will continue to work as expected.