Veeam can (for example) take an image-level backup every day (or every 12 hours depending on your needs) and then every x minutes ship the logs. Truncation will happen when you do the image-level backup and with application aware processing veeam will take care of it.
As @Kubimike said, having different solutions doing backups and allowing them to play with the logs really can mess thing up and you will end up with broken things in the end. So you want to avoid that. You are going to have to make the call which solution is allowed to work with the logs. I'm certainly not going to try to convince you to choose for Veeam, but I am going to ask you to look at our SQL explorer (https://helpcenter.veeam.com/docs/backu ... tml?ver=95
) and I hope you will see that you are going to get a very powerful restore tool (and that is the reason why we backup right
If you have a DBA, I am sure he is going to like this also
Let us know what you think and don't hesitate to ask more questions.