Unable to truncate transaction logs.

Availability for the Always-On Enterprise

Re: Unable to truncate transaction logs.

Veeam Logoby foggy » Fri May 22, 2015 1:32 pm

Yes, please.
foggy
Veeam Software
 
Posts: 14560
Liked: 1060 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Unable to truncate transaction logs.

Veeam Logoby MAA » Tue May 26, 2015 3:44 pm

After change vCenter Server from 5.5 (Windows) to 6.0 (appliance) on one of my SQL server job i get this warning:
Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MSSQLSERVER. Possible reasons: lack of permissions, or transaction log corruption.
MAA
Enthusiast
 
Posts: 38
Liked: never
Joined: Sat Apr 27, 2013 12:10 pm

Re: Unable to truncate transaction logs.

Veeam Logoby foggy » Tue May 26, 2015 4:30 pm

Does this SQL server hold vCenter database or some unrelated one? Better contact support to take a look at guest logs.
foggy
Veeam Software
 
Posts: 14560
Liked: 1060 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Unable to truncate transaction logs.

Veeam Logoby jroot » Fri May 29, 2015 4:49 am

Foggy, I had the same error as MAA on a Windows 2003 server with SQL 2005 but I was able to correct it by editing the job, going to Guest Processing, clicking Applications, Highlighting the object, clicking Edit, Selecting the SQL tab, Checking "Do not truncate logs (requires simple recovery model), OK twice and Finish. The databases I have on this server all have circular logging and don't require truncation so it was blowing this warning every time the job ran. As soon as I made this change, the job completed successfully without this same warning. :D
Hope this helps,
Jim
jroot
Influencer
 
Posts: 15
Liked: never
Joined: Fri Jan 29, 2010 2:30 pm
Full Name: Jim Root

Re: Unable to truncate transaction logs.

Veeam Logoby foggy » Fri May 29, 2015 10:02 am

Jim, this is expected, if logs truncation is disabled, there's nothing to fail. ;)
foggy
Veeam Software
 
Posts: 14560
Liked: 1060 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

[MERGED] Receiving 'Failed to truncate transaction logs

Veeam Logoby DavidDarts » Thu Jul 09, 2015 3:10 am

Hi Everyone,

I am using VEEAM Backup & Replication 8 (v8.0.0.2030) to backup a Windows Server 2003 VM which is running MS SQL Server.

My backup job is failing with the warning message shown below -

Failed to finalize guest processing. Details: Failed to process 'TruncateSQLLog' command. Failed to truncate transaction logs for SQL instances: MSSQLSERVER. Possible reasons: lack of permissions, or transaction log corruption.

If anybody can suggest how to fix this issue it will be greatly appreciated.

Kind Regards,

David
DavidDarts
Novice
 
Posts: 9
Liked: never
Joined: Thu Jul 09, 2015 3:03 am
Full Name: David Dartnell

Re: Unable to truncate transaction logs.

Veeam Logoby Vitaliy S. » Thu Jul 09, 2015 9:38 am

Did you have any successful job runs prior this failure? Can you please check that this SQL Server instance is up and running on the target VM?
Vitaliy S.
Veeam Software
 
Posts: 19450
Liked: 1092 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Unable to truncate transaction logs.

Veeam Logoby DavidDarts » Thu Jul 09, 2015 10:47 pm

Hi Vitaliy,

I have checked, and the SQL Server instance is running. I have also determined that I am running Microsoft SQL Server 2000 (v 8.00.760).

Kind Regards,

David
DavidDarts
Novice
 
Posts: 9
Liked: never
Joined: Thu Jul 09, 2015 3:03 am
Full Name: David Dartnell

Re: Unable to truncate transaction logs.

Veeam Logoby alanbolte » Fri Jul 10, 2015 12:48 am 2 people like this post

SQL Server 2000 is not supported for log backup or truncation. If needed, you can create a support case to request a hotfix that will cause Veeam to skip unsupported and not-running instances of MS SQL. Otherwise, you can disable Application Aware Processing and use native SQL backup tools to deal with transaction logs. That said, you're talking about a SQL version that's End-of-Life, and an OS that's a week away, so if possible I'd recommend migrating the databases to something more recent.
alanbolte
Expert
 
Posts: 635
Liked: 170 times
Joined: Mon Jun 18, 2012 8:58 pm
Full Name: Alan Bolte

Re: Unable to truncate transaction logs.

Veeam Logoby dlieshout@client.nl » Tue Jul 14, 2015 2:31 pm

I did have a case ID# 00942559.
We do have lots of VM's at several customers with this warning since v8 Update 1/1a/1b. All VM's without any SQL or anything.

Final statement from Veeam: "So the workaround is to disable truncate for this particular VM. I realize that this is not good way to do this manually. This issue will be fixed in next release (or update)".
So we have to wait until Veeam will revert this warning-issue as it was before Update 1.
dlieshout@client.nl
Service Provider
 
Posts: 42
Liked: 11 times
Joined: Tue Dec 15, 2009 12:41 pm
Full Name: DaLi

Re: Unable to truncate transaction logs.

Veeam Logoby ITP-Stan » Wed Jul 15, 2015 2:22 pm

I had a similar issue on a couple of VM's that were terminal services hosts (RDP farm) after v8.0 Update2b. There was no SQL (express or standard) installed but there was a Windows Internal Database insalled together with the Server Resource Manager. The service was however disabled and not running, still VEEAM complained about the SQL transaction logs. I just set ignore SQL transaction log failures for these VM's since there is no real SQL on it.
ITP-Stan
Veeam ProPartner
 
Posts: 66
Liked: 5 times
Joined: Mon Feb 18, 2013 10:45 am
Full Name: Stan (IF-IT4U)

Re: Unable to truncate transaction logs.

Veeam Logoby Vitaliy S. » Thu Jul 16, 2015 12:22 pm

Stan,

I just had a quick discussion with our dev team regarding this issue. We should have a private hotfix that skips/ignores all stopped SQL Server instances and does not try to truncate logs for databases hosted on these instances. You can open a support case and try this hotfix in your infrastructure.

Thanks!
Vitaliy S.
Veeam Software
 
Posts: 19450
Liked: 1092 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Unable to truncate transaction logs.

Veeam Logoby ITP-Stan » Mon Jul 20, 2015 9:40 am

I still have another (unrelated) support case open with VEEAM for a couple of weeks now. I'll have to wait for that one to get an update (if ever) before opening yet another case.
ITP-Stan
Veeam ProPartner
 
Posts: 66
Liked: 5 times
Joined: Mon Feb 18, 2013 10:45 am
Full Name: Stan (IF-IT4U)

Re: Unable to truncate transaction logs.

Veeam Logoby foggy » Mon Jul 20, 2015 11:07 am

dlieshout@client.nl wrote:I did have a case ID# 00942559.
We do have lots of VM's at several customers with this warning since v8 Update 1/1a/1b. All VM's without any SQL or anything.

Final statement from Veeam: "So the workaround is to disable truncate for this particular VM. I realize that this is not good way to do this manually. This issue will be fixed in next release (or update)".

I'd check with support regarding applicability of this hotfix (mentioned by Vitaliy above).
foggy
Veeam Software
 
Posts: 14560
Liked: 1060 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Unable to truncate transaction logs.

Veeam Logoby Tomsyr » Thu Oct 15, 2015 11:09 am

We needed to move service accounts with DA rights into a special group that now has deny 'interactive logins', so now we get unable to truncate SQL server transaction logs, etc... 'Win32 error:Logon failure: the user has not been granted the requested logon type at this computer.'.
Due to passwords expiring, we need to have service accounts NOT expire, and since service accounts have 'known' passwords, we need to prevent interactive logins.
It sounds like we're not alone with needing to implement this security best practice, so is there a work around?
TIA,
Tom
Tomsyr
Influencer
 
Posts: 22
Liked: never
Joined: Tue Jul 01, 2014 3:39 pm
Full Name: Tom Conklin

PreviousNext

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Google [Bot] and 15 guests