SQL truncate requested/good, but didn't happen

[pkelly_sts]

I've been having the well-known issue of SQL Logs not truncating due to lack of permissions. Having finally got the DBA to configure permissions as requested I'm now getting all green backups within Veeam, but he's reported (and I've verified myself) that the logs haven't actually truncated on all DBs, but have on some?

What could cause this scenario? I can see the veeam guest helper logs successfully claiming that all relevant (Full recovery mode) DBs have truncated as below (db2/db3 are simple mode):

22/05/2017 18:39:22 1512 Database tempdb: skipped transaction log truncation.
22/05/2017 18:39:22 1512 Database model: transation logs have been truncated.
22/05/2017 18:39:22 1512 Database msdb: skipped transaction log truncation.
22/05/2017 18:39:22 1512 Database <db1>: transation logs have been truncated.
22/05/2017 18:39:22 1512 Database <db2>: skipped transaction log truncation.
22/05/2017 18:39:22 1512 Database <db3>: skipped transaction log truncation.
22/05/2017 18:39:22 1512 Database <db4-didn't-truncate>: transation logs have been truncated.
22/05/2017 18:39:22 1512 Database <db5-didn't-truncate>: transation logs have been truncated.

DB1 did truncate as expected & the DBA was able to shrink this TL (it had grown to 40Gb over a period of time)
DB's 4 & 5 would expect to have a huge amount of white space now but don't.

Oh, & I just spotted a typo in your log generation "transation" rather than "transaction"

[foggy]

Thanks, the typo will be fixed. As for the truncation issue, I'd let our tech staff review the logs. Do you see the corresponding "logs backed up" event in the Event Viewer logs on the SQL server, btw?

[pkelly_sts]

Thanks for the pointer, yes, I can see an event 18265 "Log was backed up" for each of the DBs so again, it appears as though everything has worked, except the truncation itself didn't seem to occur for two DBs.

I wasn't sure about opening a case with support as it seems to me that Veeam has done its job: requested a snapshot, done a backup, released snapshot etc. so more of a SQL issue?

[foggy]

Our engineers will be able to advise anyway.