I recently resolved a case regarding some of my VMs not being backed up by my SQL Server Trans Log jobs. One of the bigger concerns that came out of this case was the fact that Veeam treats databases not backed up by trans log jobs as a Warning, not an Error.

Example:
Here is the "warning" message that shows up in the Statistics Windows for the trans log job:

In my opinion, these should show up as Errors. Not Warnings. Is there a way for me to update our deployment so that these messages come across as errors? Or can I submit this as a Bug so that it can be fixed in a future release?

May I ask you for the case number you mention in the beginning? And would it be possible that you post a screenshot just to make sure we are talking about the same thing (I guess I know what you mean, but just to make sure)

I can't see where I can attach an image. Can you tell me how to do that?

The logs are located under the statistics of the running Transaction Log Backup job.

I also understand that this is the designed behavior. My main point is that if a transaction log backup fails, it should be flagged as an error. It is very difficult to monitor our backups and report on them if we can't track errors like this.

Ah, gotcha. Thanks HannesK!
Here's the screenshot of what I am referring to.

Most of the databases in the underlined 'Warning' message should have been backed up by the transaction log job. My main issue with this showing as a warning is that these databases are now outside the recovery service level agreement for our business. I also discussed this with the technical support analyst of the case I was working on, and he agreed that these type of messages should be flagged as errors instead of warnings.

According to the support analyst, the fact that it never gets flagged as an error is the expected behavior. I am requesting that the expected behavior be changed. If a transaction log backup fails, it should throw an error.

Also, here is an example of a day's worth of logs for when we had the transaction log issues. You can see that the whole day, it could not backup all of the databases on the SQL Server, yet it never errored:

Thanks for providing additional information, we will review the case closer next week, once we're in the office. So far it looks like unexpected situation, but let's wait till we take a thorough look at it.