We are still troubleshooting this and trying to recreate your error in our lab. Can you please provide the URL to the VMX file of the virtual machine that is not working and one that is?

1) Open Internet Explorer and go to https://IPADDRESSOFHOSTSERVER/ (e.g. https://192.168.241.53/)
2) Click on "Browse datastores in this host's inventory"
3) Browse to the directory that houses the virtual machine's files
4) Right-click on the virtual machine's VMX file and click "Copy Shortcut"
5) Right-click on your desktop and click "Paste Shortcut"
6) Right-click on the shortcut created in step 5 and click Properties
7) Copy the URL and paste it in your reply

The URL should look something like: https://192.168.241.53/folder/vlab5vm06/vlab5vm06.vmx?dcPath=ha%252ddatacenter&dsName=datastore1


Thank you,

vBackup Team

No. We do not need access to your VMX files. We just need to review the URLs (for one that is working and the one that is not).

vBackup uses https to transfer the VMX file during the backup process. We are trying to determine if the formatting of the URL is different somehow for the virtual machine you have that is not working and thus causing the backup job to not work properly.

If you feel more comfortable sending this information to us via secure e-mail you can send it to support(at)thinware.net.


Thank you,

vBackup Team

Problem solved offline with assistance from vBackup support team. The VM contains a "#" in its name which also appears in the storage folder. However the https connection vBackup uses to access the datastore does not encode the URL to take account of special characters.
Problem resolved by unregistering the VM, renaming the storage folder AND VMX file and finally re-registering the VM in vSphere.