For vVOL datastore VM folder internally represented as symbolic link.
when we backup this VM internally represented with symbolic link VM folder like
[NimbleVVOL1] rfc4122.538dd5d5-ed7a-4f33-b570-0c05f493c845/NimbleVVOL1gk1_2-000002.vmdk
[Nimtest] rfc4122.fd693e3d-26de-480a-a334-b52fc62229d3/NimbleVVOL1gk1-000002.vmdk
through VMware MOB we dont get relation between NimblevVolgk2k8-RestoreTod -> rfc4122.6c28f736-85b6-4d25-a161-0822d24d7bc6
AttachDisk API doesnt work on this symbolic link reference.
lrwxr-xr-x 1 root root 44 May 5 17:02 NimblevVolgk2k8-RestoreTod -> rfc4122.6c28f736-85b6-4d25-a161-0822d24d7bc6
lrwxr-xr-x 1 root root 44 May 5 17:02 NimblevVolgk2k8 -> rfc4122.5ddbf3f3-2524-4d25-b5a3-31f15f8c7a18
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVVOL3 -> rfc4122.b8d99613-41b0-4a2b-8883-6ce7d901ded4
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVVOL2-restore-test -> rfc4122.da2324ec-3dce-4554-a75d-ac2588abb853
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVVOL2 -> rfc4122.c558709a-80e2-40a9-ad10-3cc2f2a8c128
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVVOL1gk1-rst -> rfc4122.6ebd815e-86c1-432e-8e05-f076ea7ccc14
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVVOL1gk1 -> rfc4122.538dd5d5-ed7a-4f33-b570-0c05f493c845
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVVOL1 -> rfc4122.b97e790d-9bf0-47c4-b705-086251528746
lrwxr-xr-x 1 root root 44 May 5 17:02 NimbleVM1 -> rfc4122.05a2ddbc-15a6-43f5-b381-e30490506c65
lrwxr-xr-x 1 root root 44 May 5 17:02 BS_Nimble_Vvol1 -> rfc4122.a94fc4ca-f3f5-443b-8c74-59eeb1495f73
lrwxr-xr-x 1 root root 44 May 5 17:02 Ash-W2K8 -> rfc4122.2185334f-b5af-45eb-acdd-c62f49a01bcd
-Ashwin