Video Screencast Help

Explanation of BE 2012

Created: 12 Sep 2012 • Updated: 19 Sep 2012 | 7 comments
This issue has been solved. See solution.

Hi, can somebody help answer me with some explanation on Backup Exec. We are still using Backup Exec 2010 R2 and with it we had an issue everytime when we had to do a restore of a 700GB plus database, the restore would just fail by counting down.

Now I would like to know if BE 2012 is not going to do the same and also has anyone done a test on it before for large databases?

Comments 7 CommentsJump to latest comment

SuperBrain's picture

What type of database are you referring to here? Exchange? SQL? Oracle? LotusDomino?

And your restores failed with which error?

thabopm's picture

They are SQL Databases and unfortunately I did not record the error message, but we were using BE 2010 R2 and the databases were being backed up to a Data Domain DD630.

CraigV's picture

Check under the Alerts might still have them there. Do the upgrade though and see if you get the same issue. Just grab copies of the Data/Catalogs folders before doing so!

Alternative ways to access Backup Exec Technical Support:

CraigV's picture


Much over muchness really. I haven't seen anything around this on BE 2012 being logged on the forum. However, what error message did you get (I could restore a 4.5TB SAP R/3 DB based on SQL to a QAS server with no hassles).

Whether or not you get the same issue with BE 2012 is open to interpretation. Download the trial version, install it and try running a restore.

That said, BE 2010 R2 was replaced by BE 2010 R3 which fixed a number of issues. Consider the free upgrade (you can use your current licenses) and try the restore again.

Also make sure your AV isn't actively scanning the BE services, and if so, put in exclusions for them.

Trialware download:


Alternative ways to access Backup Exec Technical Support:

thabopm's picture

Good Day Craig

I will try and download the trial and test the restore again. 

Unfortunately I did not record the error message at that time as I could not find possibls solutions from the net. The only thing I noticed though was the fact that the "job rate" was counting backwards instead of going  forward and eventually the job would just fail. 

By the way we are using Backup Exec 2010 R2


pkh's picture

Before you try out BE 2012, I would suggest that you upgrade to BE 2010 R3 which is the latest version and fixes a lot of problems. Your existing licence keys will work.  You can download BE 2010 R3 from either the fileconnect site or
After your upgrade, do not forget to run LiveUpdate a couple of time to update it to SP2 and the latest hotfixes.
After you have upgraded to R3, push out the remote agent again.
thabopm's picture

Thank you all for your comments, hopefully the R3 one works.