Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Break old SQL dependency

Status
Not open for further replies.

Roadki11

MIS
Mar 23, 2005
1,097
US
I am having an issue I hope someone can help with. First the back story. I have a 2003 server where MS SQL 2005 Standard was installed then Backup Exec 11d was installed and integrated with the SQL 2005. In lies my problem, I wanted to stop the SQL 2005 services and use Backup Exec to do a flat file backup of the SQL 2005 databases. However, I soon figured out that if I stopped the SQL 2005 services Backup Exec wouldn’t work as it was dependent on the SQL 2005 service. So I figured no problem, I uninstall Backup Exec and reinstalled it to use SQL Express thinking this would eliminate the SQL 2005 dependency. Unfortunately Backup Exec is still dependent on the SQL 2005 service even though it has its own SQL Express DB instance. Is there any way to break this dependency so I can stop the SQL 2005 service and still use Backup Exec? I have googled the heck out of this and can’t find anything relevant.

Thanks,


RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen
 
OK, obviously not a very active forum. I have solved my own problem and will provide the solution to my issue in case some other poor sap runs into the same issue.

Ended up being a simple registry issue. I did some research on how dependencies are set on the services and they come from the registry. So... I started digging around in the \hkey_local_machine\system\currentcontrolset\services\backupexecdevicemediaservice key and found an entry for DependOnService that still reflected MSSQLSERVER service, I took out MSSQLSERVER and replaced it with BKUPEXEC sql instance. I rebooted the server and I was able to shutdown the SQL 2005 service without killing Backup Exec and all was well.


RoadKi11

"This apparent fear reaction is typical, rather than try to solve technical problems technically, policy solutions are often chosen." - Fred Cohen
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top