Backup Exec 2012 Database Maintenance fails on Audit Logs, BEDB.DAT file may grow to 4GB in size.

Article:TECH201551  |  Created: 2013-01-10  |  Updated: 2013-11-25  |  Article URL http://www.symantec.com/docs/TECH201551
Article Type
Technical Solution

Product(s)

Issue



When the Backup Exec Database Maintenance occurs at (4 AM) and alert is generated that the maintenance has failed.   The Database Maintenance grooms job history, alerts, audit log information, and other items out of the Backup Exec database according to the setting under "Configuration and Settings - Backup Exec Settings - Database Maintenance".  

NOTE: Additionally, with the Backup Exec Database growing to 4GB in size,  no jobs can be executed or created. 

 


Error



Backup Exec alert

Database Maintenance Failure
(Server: "SERVERNAME") (Job: "Database Maintenance") Summary of database maintenance activity:

* Performed database consistency check for BEDB database
* Saved contents of BEDB database
* Optimized BEDB database size from 2500.38 MB to 2167.06 MB
* Deleted expired data for BEDB database:
     0 empty legacy backup-to-disk folders were deleted
     0 expired reports were deleted
     1216 expired job histories were deleted
     229 expired alert histories were deleted
     0 expired job logs were deleted

Maintenance has failed: -536837662, -536837662: :: -2147217871:Query timeout expired

Application Log

Log Name:      Application
Source:        Backup Exec
Event ID:      57348
Task Category: None
Level:         Error
Keywords:      Classic
Description:
Backup Exec Alert: Database Maintenance Failure
(Server: "HONSHU") (Job: "Database Maintenance") Summary of database maintenance activity:

* Performed database consistency check for BEDB database
* Saved contents of BEDB database
* Optimized BEDB database size from 4610.38 MB to 2167.06 MB
* Deleted expired data for BEDB database:
     0 empty legacy backup-to-disk folders were deleted
     0 expired reports were deleted
     1216 expired job histories were deleted
     229 expired alert histories were deleted
     0 expired job logs were deleted

Maintenance has failed: -536837662, -536837662: :: -2147217871:Query timeout expired
Total elapsed time: 00:05:55


Log Name:      Application
Source:        Backup Exec
Event ID:      57345
Task Category: (65535)
Level:         Information
Keywords:      Classic
Description:
Database Exception Context:Age/Purge Audit Log Error:-536837662: :: -2147217871:Query timeout expired :: DB Error Set 0: native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x80040e31 Query timeout expired


Log Name:      Application
Source:        Backup Exec
Event ID:      57345
Task Category: (65535)
Level:         Information
Keywords:      Classic
Description:
Current DbTimeoutValue=30


Log Name:      Application
Source:        Backup Exec
Event ID:      57345
Task Category: (65535)
Level:         Information
Keywords:      Classic
Description:
Database Exception Context:m_QueryTimeoutInSeconds=30 sql=SELECT [ParentID],[ObjectID],[OperationID],[TimeStamp],[UserName],[Message]  FROM  [DBO].[BELog] a1  WHERE [TimeStamp]<=? Error:-536837662: :: -2147217871:Query timeout expired :: DB Error Set 0: native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x80040e31 Query timeout expired 


Environment



Backup Exec 2012

 

 


Cause



Excessive audit log entries. 


Solution



A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.

Backup Exec 2012 Rev 1798 Service Pack 3 (TECH205351).

 

NOTE: The above Service Pack prevents the issue once installed.

If the Backup Exe database is 4GB in size or the Database Maintenance is failing pre Service Pack installation please perform the following Workaround:

 

 

Workaround: Truncate the Audit Log table Follow the steps below to perform an audit log truncation. 

WARNING: Incorrect use of the Microsoft SQL Server Management Studio Express may prevent Backup Exec from functioning properly. Great care should be taken when making changes to a Backup Exec database (BEDB). Changes to a Backup Exec database should only be carried-out by persons experienced in the use of the Microsoft SQL Server Management Studio Express application. It is recommended that a complete backup of the Backup Exec database be made prior to making any Backup Exec database changes. To perform a backup of the BEDB stop the SQL server service use for Backup Exec instance and copy the DATA folder use by Backup Exec (default location is c:\Program files\Symantec\Backup Exec\Data) then restart the SQL server service to begin the procedure below.

1. Launch the Microsoft SQL Server Management Studio Express and connect to the \BKUPEXEC instance.

2. Navigate to Databases | BEDB.

3. Click the New Query button.

4. Enter the following query:

use BEDB 
truncate TABLE BElog
select Count(*) from BElog
DBCC SHRINKDATABASE (BEDB,5)

5. Click the Execute button.

 


Supplemental Materials

SourceETrack
Value3047529
Description

Backup Exec 2012 Database Maintenance fails on Audit Log table.




Article URL http://www.symantec.com/docs/TECH201551


Terms of use for this information are found in Legal Notices