Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Virtualization Manager (VMAN) > Duplicate VMs and ESX host appear after it was moved to another vCenter

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

Created by Roger Lofamia, last modified by Rodim Suarez on Mar 09, 2017

Views: 147 Votes: 0 Revisions: 3

Updated March 9, 2017

Overview

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

Environment

VMan 6.x

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.


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.

 

 

 

Last modified

Tags

Classifications

Public