Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Network Performance Monitor (NPM) > VM showing host unkown

VM showing host unkown

Table of contents

Issue

VM Showing Host Unkown

Cause

Using VEEAM or other backup systems create duplicate UUIDS. NPM/SAM requires UUIDs to be unique.

Workaround

  1. For all VMs that have a duplicate UUID from being backed up or cloned, go to the Vcenter and right-click on the offline clone.
  2. Select "Remove from Inventory."  This removes the duplicate VM from the Vcenter database.
  3. Re-run discovery on the VMWare environment in NPM/SAM.
  4. Re-register all of the duplicate VMs that were removed from the inventory in Step 1 using the following command on the ESXi host:

    vim-cmd solo/registervm /vmfs/vol/datastore/dir/vm.vmx 
    (For example,  vim-cmd solo/registervm /vmfs/volumes/VMSERVERS-B/APP01_b/APP01.vmx)

Reference: Tips for editing a .vmx file (1714) (© 2017 VMware Inc, available at https://kb.vmware.com, obtained on July 18, 2017.)

Last modified

Tags

Classifications

Public