Challenge
Microsoft SQL Server Log Backup job displays the following warning:
Failed to prepare guest for SQL Server transaction log backup Details: Job <job_name> owns SQL Server transaction logs backup
Cause
Veeam Backup & Replication is designed only to allow one Backup Job to be responsible for a server's log backup. This is done to prevent possible restore issues. To prevent another job from attempting to take over the log backup process, there is a 7-day timeout in which the job currently responsible for the log backup must not run.
Solution
Scenario 1: Unintended Duplicate Transaction Log Backup
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.
Scenario 2: Transaction Log Responsibility Migration
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 can then back up the logs.The timer will start from the last day the VM was processed by the old job.
Option 2: Delete all Log Backups created by the Old Job
*This option is not available for PostgreSQL Transaction Log Backups.
This option will remove all transaction/archive logs for the SQL /Oracle VMs in that backup set collected after the most recent restore point was created. You will still have point-in-time restores for all restore points leading to the most recent backup.
