The source and target deployments of a vRealize Operations Manager migration interact before and during the importing of data.

You can import multiple vCenter Operations Manager deployments to a single target, resulting in a combined deployment that monitors all of the previous resources.

You can import from the same or different deployment operating system. vRealize Operations Manager supports the following variations:

Source virtual appliance to target virtual appliance

Source Windows deployment to target virtual appliance

Source Linux deployment to target virtual appliance

Source Linux deployment to target Linux deployment

Source Windows deployment into target Windows deployment

You can continue to run the earlier, source version and new, target version of vRealize Operations Manager in parallel, even after you perform a migration. You cannot perform a second migration between the same source and target, however.

At import, vRealize Operations Manager measures the available target resources and might warn you that more nodes or disk are needed before enough space is available to import the source.

At import, vRealize Operations Manager notifies you if any adapters are installed on the source that are not installed on the target.

The process might take hours or even days to complete. The number of resources, number of metrics, length of history, and size of the FSDB all contribute to the time needed for migration. During internal testing, an inventory of 13,000 resources with 2.5 years of history took about 44 hours to migrate. A guideline of 1 hour per 10 GB of FSDB data is a good starting point but might be influenced by network performance or other factors.