Collected SQL Server transaction logs do not match any existing database backup: SQLINSTANCE\DATABASE

KB ID: 2117
Product: Veeam Backup & Replication
Published: 2016-03-24
Last Modified: 2022-02-21
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please try again later.

Challenge

SQL Server Transaction Log Backup task fails with the error:
Collected SQL Server transaction logs do not match any existing database backup: SQLINSTANCE\DBNAME
Screenshot of error

Cause

This error occurs because the collected transaction logs do not match the existing backup of the server. The most common cause is that a SQL-level database backup or transaction backup has occurred that was not triggered by the Veeam SQL Server Transaction Log Backup job.

Note: Native SQL Backups cannot be taken in conjunction with Veeam's SQL Server Transaction Log Backup unless they are COPY ONLY. Other applications interacting with the Transaction logs will break the consistency of SQL Server Transaction Log Backup and cause the error documented in this article.

Solution

To resolve this issue, run the associated backup job to create a new restore point for the SQL server failing to be processed by the SQL Server Transaction Log Backup job.

 

For more information about how the SQL Server Transaction Log Backup works, review: How Microsoft SQL Server Log Backup Works

 

More information

The SQL Server Transaction Log Backup can be toggled between running states by disabling the associated backup job. When the job is disabled, the SQL Server Transaction Log Backup will stop.

If running the backup job causes the error to stop occurring, and the error returns in the future, review the scheduled tasks on the SQL server with your Database Administrator to ensure no other software interacts with the SQL Transaction Logs other than Veeam.

Click here to send feedback regarding this KB, or suggest content for a new KB.
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please try again later.