SQL Server transaction log backup failing

[kyoon@casusa.com]

Hello,

We had a job consist of 8 SQL VMs also backup SQL logs.

I delete one of them VM from the job and created dedicated backup job for the VM to use it with Veeam Cloud Connector.

Since then, Regular backup job is running fine however, SQL Server transaction log backup is keep failing and I get following log stating the old backup job is still responsible for the log backup.

"Failed to prepare guest for SQL transaction log backup Details: Job Backup Job 3 - SQL VMs is responsible for SQL transaction logs backup"

I double checked the VM is not part of old backup job anymore. What am I missing here? Your input is much appreciated. Thanks.

VEEAM CASE #: 00880477

[Gostev]

Hi, Ken. As per Release Notes, SQL transaction log backup to a cloud repository is not supported. Thanks!

[foggy]

However in this specific case, the message is caused by the fact that this VM was previously backed up within another job. By default, the new job will not perform logs backup during 7 days after last successful logs backup performed by another (existing) job.

[Gostev]

Right - I missed that part of the issue, sorry.

[Clemens Bertram]

Hello Gostev,

please have a look at Case 02086028

We are facing the same Issue.

Basically that is a "No Go" for Veeam in our Environment because we are running Enterprise Applications on MS-SQL in our Environment.

[Mike Resseler]

Hi Clemens,

My German is a bit rusty but from what I can read in the support case it is solved now?

Let me know
Mike

[Clemens Bertram]

Hi Mike,

the case is closed because the Support told us that this behavior is by Design.
The only thing we can do is set the value from 7 Days to 1 Day.

Kind regards
Clemens

[foggy]

Yes, the behavior is currently expected and designed to protect from thoughtless decisions. You can set the registry value to 0 to disable it though.

[Clemens Bertram]

Hi

sorry but the value 0 is not possible.
We discussed that with the Support.

Value "0" would fix our Problem.

[foggy]

Hi Clemens, we've checked internally, the registry value set to 0 should work. Make sure you're using the correct value and specify it in the backup server and please refer to this KB article for details.