Different jobs uploading to Google Drive create duplicate folders

[sheardd]

I've got multiple backup jobs configured to upload to the same folder on Google Drive, the ideal outcome being that I should have a single "Backups" directory on Google Drive that holds the backup folders for each of my different jobs. However, every time I run a job it creates its own version of the same folder with an identical name, so instead I end up with two dozen different "Backups" directories on Google Drive, each of which contains a backup folder for a single job. I've tried creating the folder first and pointing all the jobs to it explicitly by editing the configuration (both on the FBackup credentials and on individual jobs) but every job insists on creating its own copy of the folder, regardless of whether I've created the folder on Google Drive first or whether other FBackup jobs have created a folder with the name.

It also only creates these folders at Google Drive's root level when previously I've tried specifiying a sub-folder, but that's a less pressing issue. If they have to go at the root of G drive I can live with that; I just don't want two dozen different folders cluttering up my Google Drive's root directory (I'm running a lot of jobs as they're all individual project folders for different clients).

[Adrian (Softland)]

Hi,

I was not able to reproduce the problem using the latest version of FBackup 9.9.975.
Please make sure you have the latest version.

Please send us to info[at]fbackup[dot]com for such a job:
- the backup catalog
- the last backup log