Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > 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_ret on Mar 09, 2017

Views: 756 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