Warning - Unable to truncate transaction logs

[Yuki]

We've just had an issue on the network: NAS that receives backups became unresponsive and caused the backup to hang. We had to force stop all the Veeam services in order to cancel the job, then manually clean up snapshot and lock files on VMFS for that VM. After that we've ran an "Active Full" backup to repopulate the CBT data and to make a good backup of the server again.

When the job completed it displayed this error:
"Warning - Unable to truncate transaction logs. Details: KeepSnapshot error: [Freeze job already stopped.]"

Server is a file server based on Windows 2012 Standard and does not contain any databases. An incremental run did not produce any warnings or errors. Anything we should be contacting support about?

[veremin]

For some reason, probably just a glitch, during a first full backup run this VM was treated as the one where the log truncation is needed.

However, providing incremental runs went smoothly, I believe you shouldn’t be worried about it.

Hope this helps.
Thanks.

[Vitaliy S.]

Log truncation can happen on either full or incremental, it doesn't matter. Since the second run didn't have any errors, there is no need to contact the support team.