Check VMware trace log file and we see that the partition on the VM is GPT
Extract from trace file:
4 VOLUME :05820 1 0 095309.516375 First Partition on Disk [DATASTORE(LOCAL)] test/test-000002.vmdk is a GPT Partition <<< Recognise GPT markers at the start of the disk.
4 VOLUME :05820 2 0 095309.516375 Read Primary GPT Header at offset 100754967781966336 <<< GPT information is at the end of the disk
4 VOLUME :05820 3 0 095309.516375 Read Backup GPT Header at offset 85899345408 <<< Read additional GPT information.
0 VDDK :05820 138 0 095309.516375 VDDK error encountered: code 16007
0 VDDK :05820 52 0 095309.516375 VDDK error message is 'You have requested access to an area of the virtual disk that is out of bounds' <<< Not really a fatal error.
4 VOLUME :05820 17 0 095309.516375 Identifying GPT Partitions on Disk [DATASTORE(LOCAL)] test/test-000002.vmdk <<< plugin hangs trying to investigate partition
NetVault VMware plugin was trying to perform file indexing on a GPT partitioned volume which is currently not support.
Do not use file level indexing on VM’s with GPT partitioned volumes
If file level indexing is required use one of the following options:
1/ with volumes under 2TB in size you and use the VMware file level backup option. To use this see VMware user guide, section performing file-level backups.
See URL below:
2/ install NetVault client on the VM and backup the required volumes where file level restore is required using the file system plugin.
This will only be necessary until Enhancement request has been implemented to the plugin.
Enhancement #22397 has been raised to add support for GPT partitioned volume
