Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Backup Exec 2010 Database Usage

Updated: 01 Nov 2010 | 3 comments
anbeier's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

While I am currently planning the Installation of Backup Exec 2010, I do have a quick question about the database (server) backup exec will use.

Currently there are 2 SQL 2005 instances and 1 SQL express (WSUS) instances already running on the server (Win 2008 R2, Enterprise Edt.).

Is it possible to install the BE 2010 databse(s) on one of the currently running SQL databases?

Thanks in advance

Andreas

Comments

CraigV's picture
09
Feb
2010
2 Votes +2
Login to vote

Hi there, yes you can...Check

Hi there,

yes you can...Check out the link if you want to read the full guide, otherwise just what I copied and pasted below:

http://seer.entsupport.symantec.com/docs/341837.htm

To create a local Backup Exec SQL Express instance

Do the following in the order listed:

  • Click Create a local Backup Exec SQL Express instance to store the database on.

  • To change the location of the Backup Exec SQL Express instance, click Browse.

  • Select the location, and then click OK.

To use an existing SQL Server 2005 or SQL Server 2008 instance

Do the following in the order listed:

  • Click Use an existing instance of SQL Server 2005 (SP3a or later) or SQL Server 2008 on the network to store the database on.

  • Select the instance.

When Backup Exec is installed into an existing instance, the automated master database restore feature is not available. To recover the Master database, replace it with the Master database copy that Backup Exec automatically creates and updates when the Master database is backed up.

Caution:
During the installation process and upgrade process, Backup Exec stops and starts the SQL service several times. Other user-created databases that use the SQL Server instance are unavailable during the process. To avoid such conflicts, you should install Backup Exec into its own SQL instance.

Laters!

If you find this is a solution, please mark it as such.

anbeier's picture
12
Feb
2010
0 Votes 0
Login to vote

Thank you very much. I'll try

Thank you very much. I'll try it that way.

CraigV's picture
12
Feb
2010
0 Votes 0
Login to vote

Cool, no worries!

Cool, no worries!

If you find this is a solution, please mark it as such.