Backup Exec CREATES SQL Database?

[t700701]

Something I don't understand on a 2000 Advanced server I'm learning to manage:

It has Backup Exec installed, and also MS SQL 7.0, but I don't think SQL is being used by the company. I say this because when I look in the MSSQL\data folder, all the databases show a modified date from over 2 years ago, with the exception of one called BENSE.mdf that's accessed everyday.

Sounds like Backup Exec Network Storage Executive to me, which I don't even use since there's only one media server.

Stupid question maybe, but like I said, I'm just learning this stuff and I'd rather ask a stupid question than spend all weekend recovering from a stupid mistake:

I want to uninstall both Network Storage Executive and SQL7.0 through add/remove programs and I wanted to double check and see if anyone knew any reason to not do that. Is there anything I have to do before uninstalling either?

I'll save all the other databases just in case. All I need there is the .mdf's .ldf's, is that right?

 

[PerryMc]

Surely there is someone there you can ask if they are using SQL? If not, make sure services MSDTC, SQLSERVER and SQLAGENT are all stopped then backup the whole server 2 or 3 times before you remove them. That way you can be sure to be able to return it to how it was. Always better to be safe than sorry.

Smile anyway,
Perry.

 

[t700701]

No one knows why MSSQL is installed/running and there are no services MSDTC or SQLAGENT running. Those two things together very well could mean that it's only being used by Network Storage Executive. I don't necessarily need to uninstall SQL, I'll be happy disabling it.

My main question was more about removing Network Storage Executive. The Veritas site has a knowledge base article about removing a media server from a NSE domain, but it's not clear if I have to do this before uninstalling NSE.

 

[PerryMc]

Sorry, can't help you there, we don't use NSE.

Smile anyway,
Perry.

 

[RSA]

If you are using Backup Exec 9 (Windows version), that uses SQL for it's database. IF there is an instance of SQL on the machine it is installed on, then it will use that, otherwise it will install the Desktop Edition of SQL.

The database name is the same as the NSE database, I can only assume this is for backward compatability, or lazy developers.