SQL Transaction Log behavior after Move from VMs

[WinstonWolf]

Hello ,

I have configured an SQL Server Transaction Log Backup on two VMs in Backup Job A
Then i moved the both VMs to another Backup Job B .
When i then start in Job B on these both VMs the SQL Transaction Log Backup i becomme the following warning :

Failed to prepare guest for SQL Server transaction log backup Details: Job A owns SQL Server transaction logs backup

What can be the Problem ?

Michael

[foggy]

Michael, transaction logs backup for the specific VM can be performed by a single job only, Veeam B&R prevents other jobs from touching the logs of the same VM. By default, there's a 7 days delay until another job will be able to backup logs of this VM. However, if you need to start backing them up immediately, you can create the SqlBackupLogsAgeDaysToSkipLogBackup registry value and set it to 0.

[WinstonWolf]

[PROBLEM SOLVED]

So much thanks for this Tipp , it works like charm

Perfekt , now my two VMs are in the right Backup Job and the SQL Transaction Log Backup works fine .

[firewall68]

Hello togehter have the same issue when i split on Job with 2 Machines into 2 Jobs.
Can you please tell me where i can find the registry entry or where exactly i have to set the new entry?
Because right now i get the message that job B hold the Transact Logs of Job A.

Thx in Advance
Regards from Austria (no Kangaroos )
Mike

[firewall68]

Found it thx: https://www.veeam.com/kb2029

[Sk1310]

Do I add this registry key to the SQL server, or the Veeam B&R Server?

[veremin]

or the Veeam B&R Server?

This

[Iain_Green]

Hi,

We had a SQL server that was in an application aware backup with a number of other servers, however there were times we wanted to perform active full backups and not for the whole job.
So I moved the Server to a dedicated backup, basically I cloned the existing and removed all the other servers.

In the old job I also added the exclusion for the SQL server and disabled application aware as it was only the SQL server that was using.

The new job had all the application awares settings and an active full was run. Now when the Tranaction backup runs I always see the below warning.

13/07/2018 10:24:49 :: Failed to prepare guest for SQL Server transaction log backup Details: Job <OLD JOB> owns SQL Server transaction logs backup

None of the 11 databases are protected!

Have I missed something??

[Vitaliy S.]

Hi Ian, please follow the steps from the KB article posted above to fix it. Thanks!

[PKaufmann]

same issue here
I added the regkey with value 1 for 1 day, but still not working..
After setting the regkey, do I need to restart the veeam backup services ?
Do I need to disable / enable the new job to kinda restart the log backup process?

[PKaufmann]

is this still working? Just noticed that the KB only shows Version: 8.x

I can confirm it is still working, no restart required

[Vitaliy S.]

Yes, the KB still shows version 8, but it should be applicable to later releases too. Thanks for confirming that services restart is not required.