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
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.
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.
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:
1. Wait the 7 day timeout.
2. Change the TimeOut to a lower setting with the following registry key.
HKLM\SOFTWARE\Veeam\Veeam Backup & Replication\
DWORD: SqlBackupLogsAgeDaysToSkipLogBackup or SqlBackupLogsAgeDaysToSkipTruncate
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 existed 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.
3. 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.