Backup Exec Database Maintenance is failing because the database grew too large

Backup Exec Database Maintenance is failing because the database grew too large

  • Article ID:100041448
  • Last Published:
  • Product(s):Backup Exec

Problem

The Backup Exec Database Maintenance is failing because the database grew too large

 

Error Message

Maintenance has failed: -2147418113, native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x8000ffff Connection failure.


Event viewer report:

Event ID:      57348
Decsription:
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 11442.00 MB to 5421.69 MB
* Deleted expired data for BEDB database:
0 expired audit logs were deleted
0 empty legacy backup-to-disk folders were deleted
0 expired reports were deleted
0 expired job histories were deleted
15 expired alert histories were deleted
1 expired job logs were deleted
Maintenance has failed: -2147418113, native=0xffffffff source=Microsoft OLE DB Provider for SQL Server hr=0x8000ffff


Cause

Issue is caused by the fact that the Audit log table grew to large

 

Solution

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

 

In case you increased the amount of days to keep certain alerts within the Database maintenance settings, please verify this configuration and reduce the amount of days to ensure this issue will not happen again in the future.

 

Was this content helpful?