- Veeam Support Knowledge Base
- SQL Transaction Log Backup - Failed to prepare guest for SQL transaction log backup Details: is responsible for SQL transaction logs backup
SQL Transaction Log Backup - Failed to prepare guest for SQL transaction log backup Details: is responsible for SQL transaction logs backup
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
Challenge
SQL 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
This issue can also occur for Oracle SQL Archived Log Backup, and will display the following warning:
Cannot delete Oracle archived logs because job <job_name> is active
Cause
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:
- https://helpcenter.veeam.com/docs/backup/vsphere/alwayson_support.html?ver=110
- https://forums.veeam.com/microsoft-hyper-v-f25/backup-logs-options-with-alwayson-ag-t32096.html
- https://forums.veeam.com/vmware-vsphere-f24/best-way-to-backup-always-on-sql-cluster-multi-istance-t71912.html
- https://forums.veeam.com/veeam-backup-replication-f2/sql-alwayson-in-2-datacenters-t37971.html
Solution
- If the job throwing the warning is not intended to manage the server's log backup operations, edit the backup job and disable the log backup function for that VM.
- If you are migrating the responsibility of log backup from one job to another job, disable log backup in the old job and then review the three options below:
- Option 1: Wait
Wait for the 7-day timeout to pass and the new job will then be able to backup the logs.
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 values on the Veeam Backup Server.
*No Reboot required.
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: SqlBackupLogsAgeDaysToSkipLogBackup
Value Type: DWORD (32-bit) Value
Value Data Default: 7
Where 'x' is the number of days.
Note: Log truncate will be skipped for a VM if there are SQL logs of this VM collected in the last X day (defined in the registry as value SqlBackupLogsAgeDaysToSkipTruncate/default is 7) by another existing job.
- Option 3: Delete all Log Backups created by the Old Job
Note: This option will remove all transaction/archive logs for the SQL /Oracle 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.
- Option 1: Wait
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
Spelling error in text
Thank you!
Your feedback has been received and will be reviewed.
Oops! Something went wrong.
Please try again later.
You have selected too large block!
Please try select less.
KB Feedback/Suggestion
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Thank you!
Your feedback has been received and will be reviewed.