Discussions specific to the VMware vSphere hypervisor
Post Reply
WinstonWolf
Expert
Posts: 187
Liked: 4 times
Joined: Jan 06, 2011 8:33 am
Contact:

SQL Transaction Log behavior after Move from VMs

Post by WinstonWolf » Jan 29, 2016 11:53 am

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
Veeam Software
Posts: 16957
Liked: 1380 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by foggy » Jan 29, 2016 1:36 pm

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
Expert
Posts: 187
Liked: 4 times
Joined: Jan 06, 2011 8:33 am
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by WinstonWolf » Jan 30, 2016 6:41 am 1 person likes this post

[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
Influencer
Posts: 12
Liked: never
Joined: Jan 04, 2017 1:16 pm
Full Name: Mike
Location: Austria
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by firewall68 » Feb 02, 2017 1:50 pm

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
Influencer
Posts: 12
Liked: never
Joined: Jan 04, 2017 1:16 pm
Full Name: Mike
Location: Austria
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by firewall68 » Feb 03, 2017 7:41 am


Sk1310
Novice
Posts: 3
Liked: never
Joined: Jun 27, 2017 1:27 pm
Full Name: Sunny Khan
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by Sk1310 » Sep 05, 2017 3:32 pm

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

v.Eremin
Veeam Software
Posts: 15234
Liked: 1146 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by v.Eremin » Sep 05, 2017 3:34 pm

or the Veeam B&R Server?
This

Iain_Green
Service Provider
Posts: 137
Liked: 8 times
Joined: Dec 05, 2014 2:13 pm
Full Name: Iain Green
Contact:

[MERGED] Moving application aware SQL backups

Post by Iain_Green » Jul 13, 2018 9:30 am

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??
Many thanks

Iain Green

Vitaliy S.
Veeam Software
Posts: 21631
Liked: 1297 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: SQL Transaction Log behavior after Move from VMs

Post by Vitaliy S. » Jul 13, 2018 10:34 am

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

Post Reply

Who is online

Users browsing this forum: Bing [Bot], Edage and 18 guests