The way VMAN reads orphaned VMDK files is basically driven by relationship established between VM and related disk files when the API polling discovers that relationship via VM itself.
There can be cases when Virtualization Admins create a copy of VM folder or add subfolders directly from vCenter. The .VMDK files in those folders go unnoticed to VMAN.
When manually identifying the Orphaned VMDK files, below is the logic. Please implement VMAN to handle this method of identfying the orphan VMDK files.
Referenced_VMDKs = VM.LayoutEx.File
Datastore_VMDKs = SearchDatastoreSubFolders("*.vmdk")
Orphans = Datastore_VMDKs - Referenced_VMDKs
Support Case#: 02126317
