Support has collected logs and also take a copy of my database for lab testing.
SQL Backup via Studio:https://www.veeam.com/kb1471
5th Logging Level:https://www.veeam.com/kb1247
They came back and asked me to create a temp database to test with.
To temporarily use a new database -
stop any veeam jobs
stop the veeam backup service
go to the registry HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication
for SqlDatabaseName fill in a new name like VeeamBackup_test and start the veeam backup service
When you open the console , you can add your cluster to the veeam db and create a dummy job with csv volumes as a source to see if we get the same result or not.
After the test you can stop the veeam backup service, fill in the original database name in the registry and start the service again.
Then today they had me edit my existing jobs to re-add my CSVs to each job. So I took the CSVs for that job out, added a different one, saved it, then re-edited and put the originals back in and saved again.
After this I am so far able to get the jobs to run. I'm only testing 1 out of the 6 and I'm going to let the rest run tonight on schedule.