Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

How to Move backup exec 2010 R2 sql DB to SQL 2008

Created: 10 Jul 2012 • Updated: 20 Feb 2014 | 5 comments
Parkar's picture
This issue has been solved. See solution.

Hello;

At present we are planning to move  symantec backup exec 2010 SQL DB to the Sql 2008. the sql 2008 will be install on the same server & after migrating database, we will remove the sql express 2005 . below are the product details

1- Backup exec 2010 R2 x 4 with central admin x1

2- Licenses:

# SYMC BACKUP EXEC 2010 AGENT FOR WINDOWS SYSTEMS WIN PER SERVER BNDL STD LIC GOV BAND S ESSENTIAL 12 MONTHS 6
# SYMC BACKUP EXEC 2010 OPTION CENTRAL ADMIN SERVER WIN PER SERVER BNDL STD LIC GOV BAND S ESSENTIAL 12 MONTHS 1
# SYMC BACKUP EXEC 2010 OPTION SAN SHARED STORAGE WIN PER SERVER BNDL STD LIC GOV BAND S ESSENTIAL 12 MONTHS 6

i need best preactice guide, links to do the above task

Thank You,

Comments 5 CommentsJump to latest comment

RahulG's picture

You may refer the following document 

http://www.symantec.com/business/support/index?page=content&id=TECH37752

Its recommended to let your backup exec databse run on seprate SQL instacne . You have an option to move the database to different SQl server or SQl instance . You can Browse to C;progaram files/Symantec/Backup Exec  Look for utility name Beutility . You this utility u can move teh database to the different Sql instacne . But its not a good idea to have a backup exec databse on different Sql instance as if we peroform any maintainace or when u install the updates , it might stop the SQl servcie and You other production DB may loose connectiviy .

Parkar's picture

the below article for be 11d, which mentioned that if you installed SSO, dont perform the task, will it be the same for BE 2010?

http://www.symantec.com/business/support/index?page=content&id=TECH67768

CraigV's picture

Yes it is...check under the Product(s) section on the right side of the screen...as per that TN, your only option then is to reinstall.

Alternative ways to access Backup Exec Technical Support:

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

Colin Weaver's picture

Ok bearing in mind we recommend BE always has it's own instance a quick and dirty method to change to SQL 2008.

1) Stop the BE services and the Backup Exec SQL instance. (on all servers if using SSO/CASO)

2) Copy the Backup Exec\Data folder to somewhere safe. (this is just in case something goes wrong)

3) Uninstall the Backup Exec SQL Express instance (but do not uninstall Backup Exec)

4) Install SQL 2008 as an instance called BKUPEXEC (this must match the instance name of the 2005 instance that you uninstalled so if it was not BKUPEXEC make sure you know what it is and use that name)

5) Make sure all of the network protocols are enabled against this new SQL instance

6) Use SQL Studio to attach the BEDB located in the Backup Exec\Data folder into the new SQL 2008 instance

By keeping the instance name the same you should not have to repoint any registry settings for paths and instance names etc which should allow everything to start up as before.

SOLUTION