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:
The Backup Exec for Windows console would generate the following alert:
- 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 - http://www.symantec.com/docs/276073
- 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 - http://www.symantec.com/docs/318243
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.
Note: 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 - http://www.microsoft.com/downloads/details.aspx?FamilyId=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en
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.
- Also Verify that SQL SERVER (INSTANCENAME) Service is running as Local System and not the Domain Administrator.
Confirm that the Backup Exec database or the Backup Exec dlo database are not set as compressed databases.
- Go to the destination folder where Backup Exec databases reside. For default it will be in: C:\Program Files\Symantec\Backup Exec\Data
- Confirm first that the root directory 'C' or 'D' (where ever Backup Exec is installed) is not set to be compressed. Right click on the drive itself and select properties. On the 'General' tab confirm that the "compress drive to save disk space" is not selected.
- Confirm that the folders that contain the data files are not set for compression. Right click on the folder itself and select properties.On the 'General' tab select the button for 'Advanced" on the lower right side. Confirm that the "compress drive to save disk space" is not selected.
- Confirm that the database files themselves are not set for compression. Right click on the database file itself and select properties. (Do this for the both database file and the log file for each of the databases: bedb_data.mdf and bedb_log.ldf and the be_dlo.mdf and the be_dlo_log.ldf) On the 'General' tab select the button for 'Advanced" on the lower right side.Confirm that the "compress drive to save disk space" is not selected
- Start all services for Backup Exec to confirm that they start on the machine.