Backup Exec database corrupt

[Andrew_McHale]

Hi all,

I recently suffered a corrupt backup exec database (no idea how it happened) and couldn't find any forum posts that contained information. So I thought I'd post how I resolved it so it might help someone else in a panic.

Symptoms:

Backup Exec Media Server client wont open because services aren't running.
Backup Exec services wont start complaining of a dependency issue.
Event Viewer reports 5173 errors with MSSQL$BKUPEXEC as the source.
BEUtility cannot repair/recover database claiming it is corrupt.

Applies to:

Windows Server 2003 SP SP2
Backup Exec 12.5

Resolution:

Whilst following the instructions of Symantec KB254014 (http://seer.entsupport.symantec.com/docs/254014.htm) I spotted that I could choose to "Drop existing database and reload from backup", instead of creating a new one although as the KB suggests. Of course this requires you to have backups of your media server within Backup Exec.

After this ran I could open up Backup Exec again and all my jobs etc were still available.

Hope this helps someone

Andrew

[Ben_L_]

Andrew,

Backup Exec does it's own backup of the Backup Exec database every night when the maintenance is run.  So if you select reload from backup in that menu it reloads the database from the last backup that performed during maintenance.  The backup file for the database is stored in the same directory as the database and is named BEDB.bak.