Document the disks you see that have the 000000# in the name.
Check that the directory for this Guest VM does not contain other snapshots (VMDK files that have the 00000#). A quick way to get to the data store is to use the Summary page for the Guest VM, right click on the datastore and select "Browse".
in VMware, view the Datastore for the disk (you will see it in the path. Unitrends can not backup a VM with a snapshot because of how the Hypervisor manages the delta. Record the path to the current disk listed for your records. 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).
0 kommentar(er)
