


In VMware, for the Guest VM with the issue, edit the VM and look for virtual disks with a name that has many 00000#,vmdk, this is a snapshot.For the Guest VM with the issue, check the Snapshot Manager and see if the Hypervisor recorded a snapshot taken, and when it was taken.Please proceed to #2 if you do not see this occur. In many cases, after detaching the disks, the Hypervisor will perform the proper disk removal and consolidation. It is not normal for the Hypervisor to leave them behind after we have issued the command via APIs to drop the disks (see #7 below). If you see any foreign disks, verify that there are no backups associated with those disks, then detach them. On the Unitrends Backup Guest VM, edit the VM and look at the virtual disks attached (and their paths).
