Unable to delete 0 KB Replica VM in vSphere Client
book
Article ID: 426317
calendar_today
Updated On:
Products
VMware vCenter Server
Issue/Introduction
Replica VM appears with 0 KB Size VMDKs in the vCenter inventory.
When attempting to remediate the issue, standard management operations, such as Delete from Disk, Snapshot Deletion, or Disk Consolidation fails
VM typically displays a 0 KB or 0 Size VMDK, indicating that the descriptor files are corrupted or inaccessible
Environment
VMware vCenter Server
Cause
If a replication cycle is interrupted due to network latency or storage timeouts, the descriptor files for the replica VMDKs may become corrupted, leading vCenter to report a 0 Size disk.
Active snapshots used for the replication process may leave persistent locks on the base VMDKs. Because vCenter perceives these disks as "in use" or "invalid," it prevents any deletion tasks to protect against accidental data loss.
Resolution
To resolve this safely detach a drive from Replica VM without deleting the actual vmdk files from the Datastore.
Follow the steps below:
Locate the Replica VM in the Host Client inventory.
Make sure Virtual Machine is on Powered Off State
Right-click the VM and select Edit Settings.
Identify all Hard Disks (VMDKs) associated with the Virtual Machine
Select the Hard Drive, Click on "X" mark on right hand side and Detach the drive (Make sure not to check the box, where it says, delete files from Datastore, leave it unchecked)
Click on Save and exit
Now Unregister the Replica Virtual Machine->right click and unregister the Virtual Machine from vCenter Inventory
Reinitiate the replication again to create a new replica Virtual Machine