Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Backup and Recovery Community Blog

How to protect Backup Exec itself

Created: 28 Sep 2012 • Updated: 06 Oct 2012 • 2 comments
AmolB's picture
+3 3 Votes
Login to vote

Frequently there are posts on the connect site about protecting or recovering Backup Exec itself from a Disaster.

Below procedure explains what to backup and how to recover Backup Exec.


Everyday Backup Exec runs a database maintenance and creates a healthy copy of BE database.

This copy of database is saved in the form of BEDB.bak in the DATA folder, located in the installation

directory of BE. The option of database maintenance is enabled by default and it runs at 04:00 hours.

This option can be disabled (not recommended) and the schedule time of maintenance can be changed too.

In BE2010 and older versions, Database Maintenance option is avialable in the BE console -> Tools ->

Options -> Database Maintenance. In BE 2012 this option is avialable in BE console -> Backpu Exec

button (Top left hand corner) -> Configuration & Settings -> Backup Exec Settings ->Database Maintenance.

What to Backup?

To recover Backup Exec from a disaster you need latest copy of the Data & Catalogs folder. As mentioned

above BEDB.bak (latest good copy of BE database) is saved in the Data folder. About the Catalogs folder as

the name suggests it stores catalogs of the data which is being backed up daily by BE. Without catalogs you

cannot restore any data from the backup sets although catalogs can be generated by running a catalog job on the

media but its a time consuming process.  So you need to backup Data and Catalogs folder located in the

installation directory of BE. 

How to Recover?

If BE server crashes or if BE needs to be reinstalled than with the help of Data and Catalogs folder you can bring

backup BE to the state as it was prior to disaster. What you need to do is mentioned below in few simple steps.

  • Install Backup Exec.(same version and same server name)
  • Restore Data and Catalogs folder from the backups.(run inventory and catalog job before restoring) 
  • Replace existing Data and Catalogs folder with the Data & Catalogs folder from backups. 
  • Open BEUtility.exe -> Right click on the media server -> Select Recover Database -> Select "Drop existing database and reload from backup" (This will make sure that healthy database is used by Backup Exec)

Note: There are many ways to recover BE I have described 1 of them.

Comments 2 CommentsJump to latest comment

Steven Moran's picture

So - Are you suggesting that every single option, checkbox, setting, etc, that I can modify in the Admin Console are all entirely stored in the BEDB and that Backup Exec - as an application - has no other settings anywhere that I might need to back up?  Again, I'm not talking about Objects that I can create or use via the Admin Console, but all of the other things that I can configure from the BE menus like the defaults or the BE settings.

Login to vote
Armin Kerl's picture

In the BEDB Database is mostly the Job, Catalog and Device Configuration stored.

The Recover above help you, if the local BEDB is crasched and Services are not starting or something like this.

BE Programm Options are in the Regestry and License Information are in the License Files stored.

If you want to Recover /ReInstall or Move the complete BE Installation to a new Server look at this TechNote:

Login to vote