Note :

Before you proceed, do not forget to back up the existing database ie. the entire Data directory from C:\Program Files\Veritas\Backup Exec\Data.  (BEDB_log.ldf, BEDB_dat.mdf, bedb.bak).

The backup copy of the Backup Exec Database (BEDB.Bak located in the \Program Files\Veritas\Backup Exec\Data or \Program Files\Symantec\Backup Exec\Data Folder) should be copied to an alternate location prior to performing the procedure below.  Backup Exec performs internal maintenance to “dump” aka “Backup” the Backup Exec database BEDB files to a SQL backup file bedb.bak daily.  If the issue is not resolved by replacing the database with a fresh copy, the previous database can be reloaded (See rolling back changes on the Backup Exec Database in the Related Documents below).  Be aware also that all the media (tape or backup-to-disk) will be presented to Backup Exec as Imported Media and could potentially be overwritten by a new backup job which runs after the database has been replaced with the fresh copy.  Consider moving all the Tape media into a Media Set which has some level of Overwrite Protection assigned to it and then only move the media which can be overwritten to the Scratch Media Set afterward prior to creating new backup jobs.

In case the Backup Exec Database is hosted on a different SQL instance other than the default instance the reload from base activity will affect the data files stored under that instance. In this scenario the data files under the Data folder of the Backup Exec`s installation directory will not be changed. Ensure a backup or copy of the SQL data files before running a recover database activity.

In scenarios where Backup Exec`s database is hosted on a SQL server instance where othere database are also attached the recover database activity will restart the SQL instance service and it may result in SQL database users or applications disconnected from the database and instance.

Dropping the existing database and reloading from base may be necessary if the Backup Exec Database (BEDB) has been corrupted.  We recommend running a "Dump" of the Backup Exec database before dropping the existing database.

Note:  Since the SQL database is new, Backup Exec logon accounts, jobs, media sets, storage, and other settings will have to be created/configured again.


1.  Open BEUtility.exe (X:\Program Files\Veritas\Backup Exec)

 

2.  In the Veritas Backup Exec dialog box, select Yes to continue
 

3.  Expand Known Computers and then All Backup Exec Servers. 

4.  Right-click your Backup Exec server and select Recover Database from the pop-up menu
 

5.  In the Recover Database dialog box, select the database instance that you want to reload.  Next select Drop existing database and reload from base and then click OK
 

6.  In the pop-up window, select Yes to continue with the drop and reload.
 

7.  The Operations Progress dialog box will appear indicating the progress of reloading the database.
 

8.  Once completed, click Close and exit out of BEUtility.
 

9.  Open the Backup Exec Console and create the System Logon Account then mark the account is a default account.

9-2. Click System Account to create the System Logon Account