How to resolve Backup Exec database query timeouts.

book

Article ID: 100047019

calendar_today

Updated On:

Description

Error Message

 

BESERVER: -1 SQLLog(1111347):Database Exception Context:m_QueryTimeoutInSeconds=30 sql={? = CALL DBO.CALCULATECAPACITYUSAGEGB(?)} Error:-536837662: :: -2147217871:Query timeout expired :: DB Error Set 0: native=0xffffffff source=Microsoft SQL Server Native Client 11.0 hr=0x80040e31 Query timeout expired
BESERVER:- 1 SQLLog(1111348):Current DbTimeoutValue=30
BESERVER: [01/23/20 19:21:47] [0000]     DATABASE EXCEPTION: -536837662: :: -2147217871:Query timeout expired (E00081E2)
BESERVER: [01/23/20 19:21:47] [0000]     0: 80040E31 Query timeout expired

 

Cause

Issue occurs when Backup Exec database (BEDB) SQL queries are not processed quickly due to large database size, large amount of information in the Backup Exec database,  or slow network connection.

Resolution

1 . Stop all the Backup Exec services.

2 . Create following registry keys on Backup Exec server. (If CAS-MBES environment the create them on both CAS and MBES servers)


WarningIncorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry is done prior to making any registry changes.
 

​"HKEY_LOCAL_MACHINE\Software\Veritas\Backup Exec for Windows\Backup Exec\Server\"

Value type DWORD = "Database Timeout in Seconds"

Value [Decimal] = 900 (which is 15 min)

 

"HKEY_LOCAL_MACHINE\Software\Veritas\Backup Exec for Windows\Backup Exec\Server\"

Value type DWORD​ = "Database Timeout for History Operations in Seconds"

Value [Decimal] = 900 (which is 15 min)

 

NOTE: The registry timeouts values may have to be increased to 1800 or 3600.

 

3. Additional Step if the registry settings do not change the timeout behavior : Increase the SQL "Remote Query Timeout" value to 900 (which is 15 min)

 

4 . Start all the Backup Exec services.

 

Issue/Introduction

Unable to Edit / Save jobs. Unable to run reports Jobs dispatched from CAS are stuck in "Ready, no writable devices available” or "Active" state.