VMs restored to a vSphere Supervisor Namespace with Third-Party Backup Solutions are not managed by VM Service
search cancel

VMs restored to a vSphere Supervisor Namespace with Third-Party Backup Solutions are not managed by VM Service

book

Article ID: 444849

calendar_today

Updated On:

Products

VMware vCenter Server VMware vSphere Kubernetes Service

Issue/Introduction

When restoring a virtual machine to a vSphere Supervisor namespace, the VM is restored to the namespace as expected but fails to be managed by the VM service.

Symptoms include:

  • In the vSphere Client VMs & Templates view, the restored VM does not appear under any folder.

  • The VM is not visible in VCFA for the Namespace

  • The VM is not listed when running kubectl get virtualmachine -n NS

Environment

vCenter Server 9.x

Resolution

Currently, there is no definitive resolution. A workaround exists to force the VM service to discover and manage the restored virtual machine:

  1. Log in to the vSphere Client.

  2. Locate the affected restored virtual machine.

  3. Perform a migration of the VM's management layer, targeting the exact same Supervisor namespace where the VM currently resides.

  4. Completing this migration workflow forces the VM service to detect, claim, and manage the VM.

Powered by Wolken Software