Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > A duplicate cluster appears after renaming it

A duplicate cluster appears after renaming it

Table of contents
No headers

Renaming a cluster while Hyper9 is active creates a temporary situation in which the same cluster is listed under both the old and new names. This temporary duplication will exist for a day or two until the cluster name cache expires.

To immediately clear the name cache:
Remove the data source attached to the cluster and re-add it, this will force ONLY active objects to be put back on the web. No historical data will be removed.

Last modified

Tags

Classifications

Public