Sophos and Veeam Backup Agent - Can't we just get along? - "Failed to update meta"

After upgrading a series of PCs from old versions of Veeam Backup Agent (version 4 or 5) to current,  and upgrading the target file server at the same time, I started seeing failures from Veeam.   The common message was

Failed to save backup meta to '\\networkHost\filePath\Backup Job\Backup Job.vbm'.
The request is not supported. 
Failed to delete file: [\\networkHost\filePath\Backup Job\Backup Job.vbm]

Starting a brand new backup chain (toss the existing backup job and data and start over)  it would complete once, just fine.  Then fail on the next backup run, almost right away (within a minute or two of starting).

I have seen a couple of threads here and on the Veeam forums about issues with A/V, and when I opened a ticket with Veeam they pointed me at https://www.veeam.com/kb2034    - see also the links at the bottom of that page for other similar Veeam  software products.

However, after putting I believe the whole series of file and process exceptions in place they mention, I was still having the issue.

After much trial and error and head pounding, I realized if I used the admin override on a PC, and disabled the 'Ransomware Protection', the backups started completing.

So in Central, under Global Exclusions, I removed all the file and process exclusions from the Veeam article I had added, then put only a single ransomware exclusion rule in place, to the network folder path that represents the backup destination.  So far this looks to have fixed the problem.

But honestly, turning off ransomware protection on the one darned place I'd like it the most, seems less than optimal...

Has anyone else seen this issue or is it just me?