I have a vBackup machine that's been nacking up several VM's for a few months now. I have a new VM to add to the backup rotations, so I added the new VM into my vBackup inventory and created a new backup job.
When I try to execute the new servers backup job, it gives an error saying: "Error executing job 'servername'. File not found." If I try to look at the backup logs, it fails because the job never created the servername folder in the backup storage path.

Fixed. Might I add the support from Thinware was most excellent.

The issue was the GUI executible was running as a normal user but the command line executible was set to run as administrator in the compatibility settings.
Jeremy assisted with identifying the issue and all it took to resolve was setting both files to run as a normal level user.

As well, just for informational purposes: When making backups of linux servers using EFI bios, you may have an issue getting restored VM instances to start. The fix is to manually keep a copy of all of your VMs server.nvram files on hand and manually overwrite the restored VM's .nvram file.

I cannot fault Thinware for this being an issue, as the issue was even experienced if using the vmware converter to do the restore directly, without the Thinware front end. (I would suggest using the Thinware front end for the restores though, as it gives you an extra option of changing the UUID in cases where you are making a copy of the machine, where vmware converter does not).