1-800-691-1991 | 9am - 8pm ET
EN

SQL Transaction Log Backup - Failed to prepare guest for SQL transaction log backup Details: is responsible for SQL transaction logs backup

KB ID: 2029
Product: Veeam Backup & Replication | 8.0 | 9.0 | 9.5 | 10 | 11
Published: 2015-04-27
Last Modified: 2021-08-02
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.

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

Transaction Log Backup status on a job displays the following warning.
 
Failed to prepare guest for SQL transaction log backup Details: <Other Job> is responsible for SQL transaction logs backup

Cause

Veeam Backup & Replication is designed to only allow one Backup Job to be responsible for a SQL servers log backup. This is done to prevent possible restore issues. In order to prevent another job from attempting to take over the SQL log backup process there is a 7 day timeout in which the job currently responsible for the SQL log backup must not run.
Note Regarding SQL Always On availability groups

When backing up an Always On availability group's nodes it is best practice to have all the nodes in the same job.

Veeam Backup & Replication will display the warning related to this KB if it detects that the server being backed up is part of a SQL Always On group and another node in that group is already being processed by SQL Transaction Log Backup.

Further reading on this topic:

Solution

If the job displaying this warning is not intended to be the primary SQL log backup job, disable the transaction log backup for that VM within that job.

 

 

Else if the job displaying this warning is intended to be backing up the SQL transaction logs, after disabling transaction log backup for the VM in the other job, the following three options are available:

Option 1: Wait

Wait the 7 day timeout. The timer will start from the last day the VM was processed by the old job.

 

Option 2: Change the timeout

Change the TimeOut to a lower setting with the following registry keys on the server where Veeam Backup & Replication is installed. Reboot is not required, changes are detected instantly.

Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD: SqlBackupLogsAgeDaysToSkipLogBackup
Value: x

Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
DWORD: SqlBackupLogsAgeDaysToSkipTruncate
Value: x

Where is x is the number of days.

Log truncate will be skipped for a VM if there are SQL logs of this VM collected last X day (defined in the registry as value SqlBackupLogsAgeDaysToSkipTruncate/default is 7) by another existing job.

SQL log backup will be skipped for a VM if there are SQL logs of this VM collected last X day (defined in the registry as value SqlBackupLogsAgeDaysToSkipLogBackup/default is 7) by another existed job.

 

Option 3: Force removal of all SQL Transaction Log Backups from the Old Job

As a forceful workaround you Force Veeam to not consider the old job by expanding the old backup set and removing the transaction logs from the job. Doing so will remove all transaction logs for the SQL VMs in that backup set that were collected after the most recent restore point was created. You will still have point-in-time restores for all restore points leading up to the most recent backup. 

User-added image

 

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 Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
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.