Restored VM not visible in VMware Cloud Director after backup recovery

Products

• VMware Cloud Director

Issue/Introduction

• A VM restored from backup appears in VCD under a new name
• The original VM, though present in vCenter, is not visible in VCD
• Attempts to power on the correct VM fail due to VCD disassociation

Environment

VMware Cloud Director.
Any backup solution with VCD restore capability (e.g., Veeam, Avamar).

Cause

• The issue typically arises when a backup solution restores a VM into vCenter without correctly associating it with its previous vApp or VCD metadata.
• This results in a new VM being visible in VCD, while the original remains unregistered.

Resolution

To re-establish the correct VM in VCD:

• Remove or delete the newly restored (incorrect) VM from the vApp in VCD.
• Import the original VM back into the vApp from VC via the VCD UI.

Steps to Import VM to vApp:

• In VCD, go to the vApp where the original VM should reside.
• Click Actions > Import from vCenter.
• Select the correct VM from the VC inventory.
• Complete the wizard to add it to the vApp.

 

Additional Information

If the backup solution caused this due to plugin limitations or restore options, contact the backup vendor for guidance on restoring VMs with proper VCD mappings.