Veeam Transaction Log Settings: Microsoft SQL Server Question

We are using Veeam to backup our MSSQL servers and there is a setting under application-aware processing that allows us to Truncate the log files.  Currently we have both Simple and Full databases (which we backup log files throughout the day). If we were to chose Truncate logs would this only change the logs on the Veeam backup or does it Truncate the files on our MSSQL server first and than backs up the server? Would this cause any issues with our full databases when we are taking log back ups?
Thanks

1.JPG2.JPG
LVL 8
ITSysTechSenior Systems AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mark WillsTopic AdvisorCommented:
I dont use Veeam, but having a quick read of : https://helpcenter.veeam.com/docs/backup/hyperv/backup_job_vss_sql_hv.html?ver=95 it sounds as if it is talking about the VM logs, not the actual DB logs.

Will be interesting to get a definitive answer....

FWIW : I would never allow a process to truncate 'live' transaction logs. You need to be managing any log growth / activity proactively.

https://www.experts-exchange.com/articles/657/Managing-the-Transaction-Log-for-the-Accidental-DBA.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Scott PletcherSenior DBACommented:
Some of that wording doesn't make sense for SQL Server.  Once a log is backed up, SQL Server will truncate it, assuming it's not required for replication or some other specific process.  Truncation in SQL Server simply means marking the log space as available to be written over.

"Do not truncate logs (requires simple recovery model)" is again nonsensical in SQL Server.  In simple mode, (1) you can't back up a SQL log, and (2) truncation occurs automatically at database checkpoints (again, unless some other specific process requires the log data).
0
Mark WillsTopic AdvisorCommented:
>> Some of that wording doesn't make sense for SQL Server.

Agreed.  Hence my comment about VM

But not sure why a backup would offer the option.... Maybe the replication aspect of Veeam ?
0
ITSysTechSenior Systems AdministratorAuthor Commented:
Thanks for your help.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Veeam

From novice to tech pro — start learning today.