Discussions specific to the VMware vSphere hypervisor
Post Reply
Funki
Novice
Posts: 7
Liked: 1 time
Joined: Feb 09, 2015 8:22 am
Full Name: Alex

SQL Server Backup failed sometimes

Post by Funki » Aug 08, 2016 12:02 pm

Hello,

Cas: ID# 01870435

2 SQL Servers (running on Windows 2008 R2) have sometimes Problems with the Backup, as far as i can see in the Logs most oft the Time because of a timeout and also "Blobcall":

SQL Server1:

Code: Select all

Unable to truncate Microsoft SQL Server transaction logs. Details: Error code: 0x80004005 Failed to invoke func [TruncateSqlLogs]: Unbekannter Fehler. Failed to process 'TruncateSQLLog' command. Failed to truncate SQL server transaction logs for instances: . See guest helper log. . Error code: 0x80004005 Failed to invoke func [TruncateSqlLogs]: Unbekannter Fehler. Failed to process 'TruncateSQLLog' command. Failed to truncate SQL server transaction logs for instances: . See guest helper log. . 

SQL Server 2:

Code: Select all

 Unable to truncate Microsoft SQL Server transaction logs. Details: Error code: 0xe06d7363 Failed to invoke func [TruncateSqlLogs]: Unknown error 0xE06D7363. RPC function call failed. Function name: [BlobCall]. Target machine: [10.170.0.51]. RPC error: Code: -529697949 Error code: 0xe06d7363 Failed to invoke func [TruncateSqlLogs]: Unknown error 0xE06D7363. RPC function call failed. Function name: [BlobCall]. Target machine: [10.170.0.51]. RPC error: Code: -529697949 im guest helper log finde ich auch den eintrag fuer den ifa-spsql1 WARN Cannot truncate SQL logs for database: Intranet_Content. Code = 0x80040e31 02.08.2016 19:27:52 18676 WARN Code meaning = IDispatch error #3121 02.08.2016 19:27:52 18676 WARN Source = Microsoft OLE DB Provider for SQL Server 02.08.2016 19:27:52 18676 WARN Description = Timeout abgelaufen 02.08.2016 19:27:52 18676 WARN No OLE DB Error Information found: hr = 0x80004005 02.08.2016 19:27:52 18676 Truncating database logs (SQL instance: )
support offered me 2 different Solutions until now:

https://www.veeam.com/kb1813

Problem here, there ist no sc delete VeeamVssSupport possible because the Service is not installed, also delting the folder is impossible, the Folder doesnt exist.


Second Solution:

Code: Select all

Set this Reg Keys on the SQL:

Name: SqlExecTimeout

Type: DWORD

Value: 600

 
Name: SqlLogBackupTimeout

Type: DWORD

Value: 3600

 Name: SqlConnectionTimeout

Type: DWORD

Value: 300
 

 HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication\
but this entry isnt there on both sql servers.

Any Ideas how to fix the Problem?

Thanks.

Vitaliy S.
Product Manager
Posts: 22289
Liked: 1413 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: SQL Server Backup failed sometimes

Post by Vitaliy S. » Aug 08, 2016 4:29 pm

Hi Alex, the registry modification has to be done on the backup server itself, not in the backed up SQL Server VMs. Thanks!

blithespirit
Veeam Software
Posts: 57
Liked: 9 times
Joined: May 03, 2016 2:06 pm
Full Name: Paul Szelsi
Contact:

Re: SQL Server Backup failed sometimes

Post by blithespirit » Aug 08, 2016 9:28 pm

Please follow Vitally's suggestion but in regard to the VeeamVssSupport service, you will only see this when the service is running, the Veeam Installer will automatically install and run the service only for the duration of the job. Once complete it disappears.

fluxblocker
Novice
Posts: 3
Liked: 1 time
Joined: Dec 16, 2014 5:57 pm
Full Name: Samuel L Sanders Jr
Contact:

Re: SQL Server Backup failed sometimes

Post by fluxblocker » Apr 06, 2017 1:41 pm

In the registry settings; are the entries supposed to be 32-bit DWORD values or 64-bit? Also, are the values supposed to be decimal or hex? Many thanks.

foggy
Veeam Software
Posts: 17712
Liked: 1481 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: SQL Server Backup failed sometimes

Post by foggy » Apr 06, 2017 3:42 pm

Hi Samuel, the values need to be placed both under HKLM\SOFTWARE\Veeam\Veeam Backup and Replication and HKLM\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication and are decimal.

websterd13
Novice
Posts: 3
Liked: 1 time
Joined: Jan 30, 2019 7:23 pm
Full Name: David Webster
Contact:

Re: SQL Server Backup failed sometimes

Post by websterd13 » Jan 30, 2019 9:06 pm

This was also from a support ticket Case# 01704611. The keys are on the SQL SERVER. If they are not there, you create them. 32Bit DWORD - Decimal

I want to see if we can add additional registry keys on the SQL server which should include our timeouts regarding truncation:

Hive: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VeeaM\Veeam Backup and Replication\
and HKEY_LOCAL_MACHINE\SOFTWARE\VeeaM\Veeam Backup and Replication\

Name: SqlExecTimeout
Type: DWORD
Value: 600

Name: SqlLogBackupTimeout
Type: DWORD
Value: 3600

Name: SqlConnectionTimeout
Type: DWORD
Value: 300

NOTE: These values are decimal values. I also had to add the following keys to the Wow6432Node\ hive: VeeaM\Veeam Backup and Replication\ **Yes that is how it is supposed to be spelled with a capital M on the VeeaM key, according to support.

Post Reply

Who is online

Users browsing this forum: AdsBot [Google] and 9 guests