https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMTE3IiwiaGFzaCI6ImY5MDM3YzlhLTNmZGMtNDcxOS05OGM5LWNiNTgwMTMwODYxNyJ9
1-800-691-1991 | 9am - 8pm ET
EN

SQL Server Transaction logs do not match any existing database backup: [DB Name]

Challenge

You have a Periodic SQL Logs Backup within a Backup Job.  You receive the following error:
 
"Collected SQL Server transaction logs do not match any existing database backup: [DB Name]

User-added image
 

Cause

The Periodic SQL Log Backup does not have a Full backup to reference.

Solution

Start the Backup Job (right click the job > Start).

This will provide a Full SQL backup for the Transaction log backup to reference.

More information

Please Note:
  • Native SQL Backups cannot be taken in conjunction with Veeam SQL Log backups unless they are COPY ONLY. Multiple applications interacting with the Transaction logs will break the consistency and prevent proper restores.


For a Visual Guide on how to stop SQL Transaction Log Backup Job:
 User-added image
 
  •  
KB ID:
2117
Product:
Veeam Backup & Replication
Version:
8.x, 9.x
Published:
2016-03-24
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.
Your report was sent to the responsible team. Our representative will contact you by email you provided.
We're working on it please try again later