VMAN continues tracking VMDK files, listing all located orphan VMDK files with detailed information. You can select the datastore to review more information and determine if the VMDK should be deleted.
If you do not monitor all virtual systems as nodes in the Orion Web Console, the listed datastore files could be used by unmonitored hosts. Prior to deleting these datastores, verify if the VMDK file can be cleanly deleted.
In this example, you may review all orphaned VMDKs once a month to reclaim misused resources and remove obsolete data. With VMs removed, you no longer require these VMDK files. In this example, you review these VMDK files and remove those determined obsolete.
Locate the Orphaned VMDKs resource.
This resource lists the orphaned VMDKs per VM, including all associated VM datastore info, the size, and an option to delete the datastore. Reviewing this information, the rio-vcenter and riovcenter VMDKs should be removed. The VMs were deleted at the beginning of the month, leaving these files taking up a large amount of space with an associated VM.
To delete the orphans, click Delete datastore file for rio-vcenter.
A message displays verifying if you want to delete the VMDK.
Repeat the process for the Riovcenter VMDK. VMAN deletes the orphaned VMDK files from the environment.
Learn more about evaluating and getting the best usage out of your virtual environment: