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

Uninstalling SQL after BE 10 Upgrade

Created: 28 Jan 2005 • Updated: 21 May 2010 | 6 comments

I have installed BackupExec 10 Upgrade over my 9.1 and all seems well so far. During the install I chose to locate the Database on one of my full blown SQL servers and it is running normally. However my qeustion is when I installed 9.1 it made be install some SQL or MSDE whatever 9.1 ran on on the BackupEXEC server. Can I uninstall that? Is that still in use it is MSSQL$BKUPEXEC that is the service that is running. Please advise and also advise is there anything special I need to do if I can uninstall?

Thank you
Norman

Comments 6 CommentsJump to latest comment

gaurav seth's picture

Greetings !!


Before going further, we would like to clarify that Backup Exec does provide an additional option to select an existing SQL instance. But, allowing Backup Exec to create its own instance is recommended.

You may use existing SQL instance if you are running low on system's resources and do not want to create any additional instance.

MSDE 2000 installation is embedded with our installation package via Microsoft supplied merge modules.
If we install a BKUPEXEC instance of MSDE 2000, then it will be removed when BEWS is uninstalled.


We recommend to use MSDE 2000 that comes with Backup Exec. One of the major advantage of using a separate MSDE engine for Backup Exec is that; if SQL
server crashes, then the Backup Exec functionality will stop as well and thereby you would be unable to restore the system.


Backup Exec v9.x and 10.0 for Windows Servers (BEWS) uses SQL 2000 MSDE database (named BEDB database) to store all device and media related information. Backup Exec DataBase (BEDB) is an SQL database that keeps the following information:

> Job History - Selections List, Job Setup, Job Template

> Alert History

> Device and Media Information

> Catalog Index


Apart from Backup Exec services, two other services are added MSSQL$BKUPEXEC and SQLAGENT$BKUPEXEC and both run with Local System Account.

Since you have upgraded to BEWS 10.0 and using MSDE from the SQL server instead of default one which you were using with BEWS 9.1 . We would like to know that after the upgrade to 10.0 could you see all the Job histories from an earlier version in 10.0 and other information which MSDE keeps as mentioned above.

Russ Perry's picture

Since the installation of SQL is tied with the Backup Exec installation, I would not recommend attempting to remove MSDE manually. If you wish, you can disable the mssql$bkupexec service.

Zerene Sangma's picture

Hello,

You may be able to uninstall the MSDE instance which is a manual procedure. However, do check the following before removing:

1. Stop the MSSQL$BKUPEXEC service and check if Backup exec 10.0 functions properly. Try to perform various jobs.

2. Check the Backup Exec services running on the Media server if any of the service is dependent on MSSQL$BKUPEXEC service. You can check it by viewing the service properties.

3. Open Enterprise Manager, and check for the BEDB database, it should be under the SQL instance.

If all the above have been checked and verfied that the present installation of Backup Exec is not dependent on the MSDE instance then you may be able to remove it.

Abhinav Bindroo's picture

Assuming the solution provided is correct. Also, there is no response from the customer within 2 days from the last reply by Veritas

Michael Wozniak's picture

How do I actually remove the MSSQL$BKUPEXECDLO instance? i don't see it in add/remove programs.