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.

Is it possible

Created: 12 Jan 2011 | 4 comments
sdcadmin's picture
0 0 Votes
Login to vote

I want to point BE 2010 to an external 2008 SQL Server as the database server.  Is this possible?

Thanks,

William

Comments

BEsymc's picture
12
Jan
2011
2 Votes +2
Login to vote

Yes, it is possible. During

Yes, it is possible. During install, you get an option to specify the SQL instance in which you plan to store the database. Although, you need to understand that you are storing Backup Exec's database on a SQL instance which you may need to recover at some point while Backup Exec itself would be down. So, typically keeping Backup Exec out of your production SQL server would be good.

Please mark it a solution, if this is useful.

Thanks

sdcadmin's picture
12
Jan
2011
0 Votes 0
Login to vote

Hi BEsymc, This can only be

Hi BEsymc,

This can only be done during installation?

Thanks,

William

Ken Putnam's picture
12
Jan
2011
0 Votes 0
Login to vote

RE: Hi BEsymc, This can only be

You can also use BEUTIL to point to a new database location

 

See http://www.symantec.com/docs/TECH37752

How to change the Backup Exec Database (BEDB) location using BEUTILITY

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

Colin Weaver's picture
13
Jan
2011
1 Vote +1
Login to vote

Just to clarify something

Just to clarify something BESymc said - we do recommend not adding the Backup Exec database to  a SQL instance that contains key production applications - however you can install a second instance on the same SQL server and use that instance for Backup Exec. It is the instance that is critical not specifically the server for this recommendation.

Also note you can't put more than one Backup Exec database into an instance as the database itself has to always be called BEDB

Oh and because of something I ran into some time ago - don't call the instance BKUPEXEC as this has sometimes has issues with updates thinking it is one of our defeult instances (so call it something else)