Applications Systems

Duplicate VMs and ESX host appear after it was moved to another vCenter

This article will provide solution when duplicate VMs and ESX hosts appear after moving the ESX hosts to another vCenter.

First published date

10/31/2018 7:51 PM

Last published date

5/1/2020 2:53 AM

Overview

This article will provide solution when duplicate VMs and ESX hosts appear after moving the ESX hosts to another vCenter.

Product section

Virtualization Manager

Cause

VMan creates duplicates when you move your ESX hosts to another vCenter or move VMs on to another ESX host. This is due to the change of the vCenter or ESX host identity on the VMAN server.

Resolution

Remove the added vCenter or ESX hosts on the VMan datasource then run a manual database maintenance and re-add the vCenter or ESX host on the VMAN datasource:

Remove the vCenters or ESX hosts:

  1. Login to the VMAN Web Console > Setup > Data Sources.
  2. Click and delete the vCenter or ESX hosts

Note: Delete all entries on the datasource.

 

Run the VMAN manual database maintenance jobs:

  1. Login to the VMAN Web Console > Setup > Advanced Setup > System Maintenance.
  2. Run the following maintenance jobs:
    • Run Trends
    • Run Depletion
    • Clear Job Trackers
    • Rebuild Indexes

Note: This will not remove or delete any historical data.
Note the above refers to the VMAN Appliance , for VMAN Orion Maintenance please go to 
C:\Program Files (x86)\SolarWinds\Orion\Database-Maint.exe


Re-add back your vCenter or ESX host:

  1. Login to the VMAN Web Console > Setup > Data Sources.
  2. Add your vCenter or ESX hosts.
  3. Go to Collection Schedule then enable all configuration and performance collection jobs.

Note: once you enable the collection jobs it will automatically run.


You will need to let the collection jobs finish so that VMAN will be populated with updated data from the datasources.