SQL Log backup - truncate settings

[bertdhont]

Hello,

Currently, we use Veeam to bakcup SQL logs every hour.
That implies that - after the daily image level backup is done - Veeam performs a truncate of the SQL transaction logs on the SQL server.

We now have another application that needs those logfiles.
Is there a possibilty that Veeam only truncates old SQL transaction logs, but leaves the most recent logfiles?

[PetrM]

Hi Bert,

No, there is no such option. However, you may consider using backup in Copy-only mode, in this case, Veeam will not touch any logs at all.

Thanks!

[jamesf391]

Hi Petr,
I was working with the same customer as Bert where this question came up as I work for the other application. We replicate data from the DBs to other locations (Data Warehouses, Data lakes, other databases etc.) using the Transaction Log files rather than CDC/CT tables or SQL commands as it produces the lowest overhead on the source DB when doing it this way.
Our product team are wondering if we might be able to explore a technical session with your equivalent team to allow both products to work in parallel in their most optimum state. As you mentioned below, if they wanted to run our solution they would potentially need to change to Copy Only. I know there is a way for the Veeam application to kick off other jobs as pre/post processes for the backup procedure so that may be an option but I think our product team would be interested in providing a potential native integration to the Veeam software so our joint customer base would not need to make any configuration changes to the application/DB when using both of us.
Could you let me know if there was a person to reach out to / introduce me to the PM who may facilitate that and I can try move a partnership forward?
Thanks
James

[PetrM]

Hi James,

I believe that this PM is me I will send you a message and we can discuss.

Thanks!