Truncating SQL transaction logs - SUDDENLY trouble

[frankive]

We also see thsi on a few VMs in our hosted environment just for a reference.
I will get in contact with support to eventually get a fix.
Thanks.

[Shestakov]

Tom, Frank,
please post your support case numbers for the tracking purposes. Thanks!

[hucmat]

Also having this issue with the : MICROSOFT##WID database. Veeam has only started reporting it since we have updated to Update 3 (8.0.2084). Support Case ID 01090546

[hucmat]

Just thought I'd let everyone know that Veeam support provided a hotfix and it looks like it has solved my issue with the Microsoft WID database. If anyone else is having issues, log a support job and you should get the hotfix pretty quickly.

[Funki]

ask veeam support for the patch. i got it last week, from the support you will receive a zip file with some *.dll included. change this *.dll on the backup server and retry the job.
my problem was solved with this change.

[cffit]

The hotfix worked for me as well.

[xy16644]

I have installed the trial of Veeam B&R with patch 3 and after setting up a WSUS VM I am not getting the error mentioned in this post:

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

I have tried giving my account sysadmin rights in SQL but this hasn't helped.

How can I get the hotfix? I'd like to see if this resolve the issue.

Thanks!

[foggy]

Please contact technical support to get it. Thanks.

[djesko]

Hi

Same problem here after update

case : 01252488

Br Niklas

[Ink]

Yep, same issue with us. When can we expect update 4? There have been a lot of niggly bugs in Veeam over the past few months and no updates since October 2015.
Far too many resources seem to be going into Veeam 9 while current customers are struggling along having to install hotfixes all over the place.
Issue 54622 springs to mind.

[ftbug]

Hi, we are currently using a domain admin account for backup, however, with certain machines we are getting the following errors;

Testing admin share accessibility via VIX Error: cannot upload file to admin share [C:\Windows] cannot create folder in guest C:\

Testing admin share accessibility via VIX Error: Cannot upload file to admin share [C:\Windows]. Cannot create folder in guest: [C:\Windows\VeeamGuestHelpersTest].VIX Error: You do not have access rights to this file Code: 13

along with;

25/08/2016 19:54:26 :: Unable to truncate SQL server transaction logs. Details: Failed to process 'TruncateSQLLog' command.
Failed to truncate transaction logs for SQL instances: SP1. Possible reasons: lack of permissions, or transaction log corruption.

What permissions does the user account actually require in order to pass the permissions test correctly, and to resolve the SQL permissions issues?

[Shestakov]

Hi, have you tried to contact Veeam support with the issue?
By the way, what product version are you at?
Thanks!

[ftbug]

We have not contacted support yet, and are using v8.

I would mainly like to just know what sorts of permissions are required for the user account on SQL databases and on the exchange machine (Testing admin share accessibility via VIX Error: Cannot upload file to admin share [C:\Windows]. Cannot create folder in guest: [C:\Windows\VeeamGuestHelpersTest].VIX Error: You do not have access rights to this file Code: 13)

thanks

[Shestakov]

And what version of v8? There was a bug fixed in v8u3.
Answering your question, you must specify a user account that will be used to connect to the VM guest OS and deploy the runtime process. By default, Veeam Backup & Replication uses the same credentials for all VMs in the job. If some VM requires a different user account, click Credentials and enter custom credentials for the VM.
Note that credentials for application-aware processing for Microsoft Windows VMs must be specified as: DOMAIN\Username for Active Directory accounts and Username or HOST\Username for local accounts.

[foggy]

Actually, if you're seeing errors just for the VIX part of the permissions check, while the network part passes without issues, you're good to go with the backup itself, since this means you have enough permission to perform backup. There're additional requirements for application-aware backup in networkless mode (over VIX), where UAC should be disabled on the VM or built-in administrator account should be used, you can check UAC settings on the affected VMs to make sure.

[Kader]

Hello,

I have encountered this warning and wondered if anybody can shed light on it.

Code: Select all

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

It's Veeam Backup & Replication 8.0.2084 running on a Windows 2012 R2 physical server.The job is backing up 1 VM.

Thanks for your help

[foggy]

Hi Kader, please see above for details.

[Kader]

Hi,

have browsed the forum but I have not found an answer to my problem.

[foggy]

This thread discusses similar issues and mentions the hotfix for this problem was available. Any reason why you do not upgrade to a more recent version? I doubt v8 is still supported, but most likely the issue was fixed in the later ones.