Backup Exec for Windows Servers (BEWS) SQL Express Database Maintenance fails with Error "Dump Database failed."

Article:TECH64797  |  Created: 2008-01-05  |  Updated: 2014-05-21  |  Article URL
Article Type
Technical Solution



When running Database Maintenance on the Backup Exec for Windows Servers (BEWS) SQL Express Database, it fails with the following error



"Dump Database failed."

The Windows Event Viewer shows the following information:

Figure 1:


Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57348
User: N/A
Backup Exec Alert: Database Maintenance Failure
(Server: "SERVER 01") (Job: "Database Maintenance") Summary of database maintenance activity:
* Saved contents of BEDB database
Maintenance has failed: 10, Dump database failed

The Backup Exec for Windows console would generate the following alert:

Figure 2:

In BEUtility the following error is observed :

Figure 3: 


Note: It is always important to obtain a backup copy before making changes to the Backup Exec database. Stop the "SQL SERVER (BKUPEXEC)" service, copy X:\Program Files\Symantec\Backup Exec\Data to a separate location prior to completing the steps below. Restart the SQL SERVER (BKUPEXEC)" service and all dependencies
  1. Run a Database Consistency Check using BEUtility to check if the BEDB database or the BE_DLO database is failing with database consistency errors.  Please refer the following document for more information::

    How to check the Backup Exec database for consistency when a Backup Exec service pack will not install, or a repair will not complete successfully -

  2. If the Backup Exec database fails on the consistency check, run an extensive repair of the Backup Exec Database (BEDB and/or BE_DLO). Please refer the following document for the same:

    How to run a extensive database repair and cleanup of the Backup Exec database when it is found to be inconsistent

    If the extensive repair fails on the BEDB database or the BE_DLO database, launch BEUTILITY and perform a 'Recover Database' and 'Reload from Backup' on the corresponding database and again run a consistency check using BEUtility. If the consistency check completes successfully, run the "Dump database" command.

    It is not recommended to recover the database from base without opening a support case with Symantec to determine if this is the best course of action, because this will put a blank database in place.  If the consistency check, repair, or backup (dump) of the database continues to fail with the same error, download/install the SQL Management Studio.Express Tools, and attempt to run backup with this Native SQL Backup Utility.

    Microsoft SQL Server Management Studio Express -

    If the backups or other SQL Maintenance operations still fail with the SQL Native Backup Utility, check the Windows Application Event Viewer Logs for SQL errors and warnings that may help further diagnose the failure.  
  3. Also Verify that SQL SERVER (INSTANCENAME) Service is running as Local System and not the Domain Administrator.


Supplemental Materials

SourceEvent ID

Maintenance has failed: 10, Dump database failed


Dump database failed

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices