Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Backing up Backup Exec

Created: 22 Sep 2009 • Updated: 21 May 2010 | 4 comments
This issue has been solved. See solution.

I am looking for a way to backup my critical information from Backup Exec information (catalog, license files, database, ect...) to a portable hard drive in the event I have to rebuild a Backup Media Server in the event of a disaster. Please give me your thoughts or how you manage this process

Questions:

  1. What critical items do I need and the location of them?
    1. Catalog Files
    2. Database
    3. License File
    4. What else would I need?
  1. Catalog Files, how do I copy all the files while the Backup Exec Service is running and the files seem to locked/in use
  2. Database, can the database be dumped automatically
  3. License File, location of the file(s) needed

Comments 4 CommentsJump to latest comment

CraigV's picture

Hi there,

I normally backup the SQL database that is used by BE, but there are also 2 additional folders namely...:

%installationdir%\Symantec\Backup Exec\Catalogs

%installationdir%\Symantec\Backup Exec\Data

...that you can also add in if you don't have the SQL agent installed. That will back up your catalogs (meaning you won't lose data such as tape information etc) and the flat-file SQL DB which is in the Data folder.

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Colin Weaver's picture

 As per Craig V but a little more specific detail

%installationdir%\Symantec\Backup Exec\Catalogs
because this contains the catalogs to  needed to restores your other data

%installationdir%\Symantec\Backup Exec\Data
contains the Backup Exec Database and the job log files - in theory to get back you only really need to backup the BEDB.BAK (assuming you are not using DLO, CPS etc) and bearing in mind that the BEDB.BAK is created (by default) at 4:00am every day as a backup of your Backup Exec database
If you want the job logs as well then the xml files in the data folder need backing up.
You don't need the SQL agent as the BEDB.BAK gives you that info but it is worth checking that the BEDB.BAK is being updated every day (check file dates/times) as you may have a problem if it is not. Change the database Maintenance timings in Tools --> Options in the Backup Exec console if you want to make the database backup happen just before you start your backup job (or start the Backup job at 4:10am)

Finally the licenses are in a file in your windows (or winnt) folder called besernum.xml - just back this up and it can be used with the import button on the licenses screen (which saves typing too)

A word of warning, make sure you keep a record of which tapes are used to backup this data as if you don't you will end up in a catch 22 of needing the catalogs folder to find out which tape the backup exec data is on in order to get back the catalogs for the rest of the data.

Also BEUTILITY.EXE is used to return the bedb.bak to being the live version of the database.


SOLUTION
Ken Putnam's picture

What Colin said, except that BESERNUM.XML is in

C:\Documents and Settings\All Users\Application Data\Symantec\Backup Exec

for v12.5

If this response answers your concern, please mark it as a "solution"

Colin Weaver's picture

 Oops forgot they changed that in later versions