Backup Plan Not Respecting Version 11 Setting

After some initial testing, I cleared out all of our backup tasks and created 4 new standard VM backup plans.

One of the things I cam across in my initial testing was the fact that using version 11 for the actual backup files is necessary if you want to maintain your backups in separate files.  This is necessary for us because we periodically upload every single backup file to Google Drive.  Although our storage is unlimited, Google Drive imposes a 750 GB per day file transfer limit and there's no integration between Google Drive and Acronis.

If we were to use a single backup file, it would quickly grow to multiple TB in size and we would have to upload the entire thing in one shot.  Google Drive will let you do this (the 750 GB limit doesn't trigger in the middle of a file transfer, as far as we've seen), but it would take forever to upload our new backup sets every time we do it.

So, we're using version 11 for the actual backup files.

Am I correct in assuming that a file ending in .TIB is a version 11 (or older) file, and a file ending in .TIBX is a version 12 (or later) file?

I've noticed that this setting seems to be respected for our ESXi Configuration backups.  We get a new .TIB file every time, and we get a single XML file alongside it that is updated every time the job is run.

For our VM backups, one thing I noticed is that when I create a task, the setting reverts itself to "Automatic", and I can't change it.  So one of the last things I do before clicking the button to create the task is make sure that the version is set to 11.

However, this doesn't seem to work.  Every backup task I've created still creates and updates a single .TIBX file, and looking in the settings shows that it's set to "Automatic".

Any ideas?