Unable to truncate transaction logs.

[Moebius]

Ok, I'm still working with the Support, but this is what we've found so far.

Support said:

Before v8 we always used SYSTEM account to perform operations in SQL Server.
But starting from v8, we're impersonating under account specified under "Guest processing".

I guess there have been good reasons to make such a change, but this can potentially have an impact on some managed systems (as it had in our case) and should have been pointed out in capital letters in the release notes IMHO. But anyway.

It turned out that in our case the account specified under "Guest processing", while being a local admin on all vms, had been denied the right to log on interactively for security reasons. In this case any backup with guest processing enabled throws the warning:
"Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate SQL logs
Failed to logon user [<domain>\<user>]
Win32 error:Logon failure: the user has not been granted the requested logon type at this computer.
Code: 1385"

The Windows Security Event log shows 3 times for each backup run the event 4625 ("An account failed to log on") with Logon Type 2 (interactive).

Once granted the account the right to log on interactively, all the warnings disappeared.

[Moebius]

I forgot to add that all the above also happens when the vm is not a SQL server, and even when there are no SQL components at all installed on the vm.

[foggy]

Lucio, reasons for changing the impersonation parameters in v8 are explained here. However, the fact that the issue is observed on VMs with no SQL/Exchange Server installed is still under investigation.

[foggy]

Seems the issue was finally tracked down and will be addressed in Patch 2.

[rbushe]

Seems the issue was finally tracked down and will be addressed in Patch 2.

thanks for the update, is there any sort of ETA or timeframe for this patch(beta or official)?

[veremin]

No ETA at the moment.

[Franco13]

Same here.
No SQL Server on VM.
With Veeam 7 no problem, with Veeam 8: Unable to truncate SQL server transaction logs....

Hope Patch 2 will fix it.

[veremin]

According to the plan, it should be. So, stay tuned.

[Alan_ORiordan]

I also experienced this message after my initial seed of my SQL Server to the DR site:

08/03/2015 01:25:02 :: Unable to truncate Exchange transaction logs. Details: RPC function call failed. Function name: [BlobCall]. Target machine: [192.168.x.xxx].
RPC error:There are no more endpoints available from the endpoint mapper.
Code: 1753

I am also running V8 Patch 1, backups still seem to work but perhaps that is because I am not truncating logs during the backup?

However I also have COPY ONLY set in the replication job settings so why the difference between the backup job and the replication job?

Should I open a support case for this?

[Vitaliy S.]

Yes, with all technical issues it's better to open a support case and verify job configuration and check the debug logs.

[Alan_ORiordan]

Support case 00826465 opened

[Alan_ORiordan]

Case results:

Case # 00826465

I spoke to Igor Kassihin, who advised during a WebEx session that the Warning is a UI bug only in the latest release. I was advised simply to continue the replication schedule

[masonit]

Hi

We have the same issue. A lot of vms complain even though they don't have SQL installed:

Code: Select all

2015-03-16 20:36:50 :: Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate SQL logs
Failed to logon user [xxxx\xxxx]
Win32 error:Logon failure: unknown user name or bad password.
 Code: 1326 

Should I contact support or just wait for patch 2?

\Masonit

[foggy]

Magnus, you can just wait for the patch, it should fix the issue for you.

[ortoscale]

I'm having same issue. I guess I should wait for patch.

[PariPari]

Having this issue on several customer sites with vms with no sql or exchange whatsoever installed. Another reason to look forward to patch 2

[Tomsyr]

Hi everyone,
I just discovered the same issue on a brand new install of Veeam and the server that was backed up.
"4/9/2015 4:14:40 AM :: Unable to truncate Exchange transaction logs. Details: Cannot finish snapshot: no job found. "

This new server does not have exchange on it - it's a new file and print server. This is the very first backup, and the only backup so far at this site, so the log file I submitted is pretty small
Support ticket is:
00874124

I did a test restore of a file so the backup itself is good, but this should help identify the phantom exchange error.
Tom

[foggy]

Thanks for submitting a case, Tom, much appreciated. Please apply the next update once it is available and verify whether the issue goes away.

[jim.montgomery]

Has anyone resolved this issue for Veeam 8?

[foggy]

Jim, the issue is addressed in the update coming later this month.

[jim.montgomery]

Foggy, thanks for the quick response. So it can be ignored for now then?

[foggy]

Meanwhile you can contact support to make sure you're experiencing the same behavior.

[yamy125]

Still having this issue with v8 Update 2 installed for reference.

[foggy]

Tom, could you please describe the issue in more detail as there are actually several issues regarding logs truncation being discussed in this and a couple of adjacent threads? Have you contacted support already?

[yamy125]

Hi Foggy,

I've got the job logged, but strange thing is it ran OK again overnight. I was getting repeat warnings as per below on retries yesterday:

"Unable to truncate SQL server transaction logs. Details: RPC function call failed. Function name: [BlobCall]. Target machine: [*.*.*.*].
RPC error:There are no more endpoints available from the endpoint mapper.
Code: 1753"

Seems to have gone OK overnight with scheduled runs, so I'm just going to see if things settle down a bit now. I've advised the Veeam rep in job of overnight results.

Cheers,

Tom

[alanbolte]

"There are no more endpoints available from the endpoint mapper"
In my experience that tends to mean that the in-guest helper process is no longer running as expected at truncation time; such as if that process crashes for some reason, or if the VM being backed up reboots.

[init-s]

I can confirm I started to have this issue after Update 2.
Ticket opened 00882225.

Anyway, I'm waiting for an update from 7 May.

[foggy]

Andrea, I can see that you've just been contacted by your engineer and arranging a webex, so please kindly keep us posted on how investigation goes. Thanks.

[init-s]

Hi foggy,

the engineer verified the problem and asked me to collect some more logs.
The problem occurr on every SQL Server (even with Windows Internal Database).
I'll update as soon as possibile.

[briggs]

I'm having this issue now too. Updated to patch 2, no difference. Am I to open a support case also?