Log Shipping broken by Veeam

Question

Log Shipping broken by Veeam

bgalway

Ten Centuries

Points: 1158
More actions
November 4, 2013 at 1:24 pm

#285481

WE are moving into SQL 2012 and concurrently moving to Veeam for Virtual Server backup. We have found that our log shipping breaks every day when the Veeam image backup of the SQL 2012 Server occurs. Has anybody else experienced this? Any known fixes?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

TheSQLGuru SSC Guru Points: 134017 More actions · Answer 1

a simple Binoogle search for 'veeam and transaction log shipping' will reveal several relevant pages about the "Do not truncate logs" setting.

Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service

bgalway Ten Centuries Points: 1158 More actions · Answer 2

Saw that but our (new) version of Veeam does not (apparently) allow "no truncation"...we ARE trying to get Veeam to help and will let the group know the result. In the meantime we are still looking for ideas.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

You've got to set Veeam to not backup and truncate the transaction logs, that or stop log shipping and use something like mirroring or availability groups. There's got to be some way to stop it from backing up the logs.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

WorkasDBA SSCommitted Points: 1684 More actions · Answer 4

VEEAM provides backup at the VM or Virtual Server Level. While log shipping is at the SQL Server or application level. If you do not want to rely on the VM level backup for the SQL Server application,

1. do not select 'application aware quiescing' (assuming SQL Server is the only app running). The Veeam backup will be a dirty backup with regards to SQL Server. When the service id/pwd is not provided to the job it cannot do the truncation.

2. Assuming that SQL Server files(mdf & ldf) are in different drives, do not select those drives as part of the Veeam backup. Needs to be tested.

bgalway Ten Centuries Points: 1158 More actions · Answer 5

I appreciate the replies. As promised, this is an explanation of how this was fixed (using the latest version of Veeam): Under Guest Processing, choose the option of "Enable application-aware image processing"