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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Bacup Exec 8.6 Sql Server Agent - Can not see Sql Server

Status
Not open for further replies.

jas244

Programmer
Jul 24, 2001
9
US
Hello,

I used the BackupExec Trial version of 8.6 for the last 60 days and it worked great, so I decided to upgrade from 7.3 to 8.6 I purchased the upgrade through Dell (upgrade for Win NT/2000 Server, upgrade for SQL Agent, upgrade for Exchange Server Agent and 3 Remote Agents).

In order to install the upgrades, I uninstalled BackupExec 8.6 trial version, installed Backup Exec 7.3 and then upgraded to 8.6.

I can see multiple servers, the Exchange server (which is on the BE server), and can run backups on other workstations/servers on the network; however, my sole problem is with SQL Server. I can not even see the SQL server on the network.

Here are some things I already tried. Confirmed SQL agent is installed under Help->About (I see my serial number and then Agent for Microsoft SQL Server, not SQL 2000 Agent as I've seen on Veritas' support website). Connected to SQL server through Enterprise manager on the BE server (works fine) with the service account for the BE services. Turned on the Enable SQL support under Tools->Options for BE. Edited the registry HKLM->Software->Veritas->Engine->AnnonymousConnections set it to 1 from 0. I even copied over the new besql2.dll for multiple instances of SQL Server 2000 (which I don't have, I only have 1 instance of SQL server 2000 per server).

I'm fresh out of ideas. Any help? Thanks in advance,

Sincerely,

--Justin Steel

 
justin - cheat!

get sql to drop the data to disk and backup the flat file. i've covered this regularly in this forum - one day I'll finish the faq...
 
I solved the problem after being charged $90 by Veritas for technical support, even though I just bought the upgrade 3 weeks ago. The problem was I had the SQL Agent 7.0 and not 2000 installed. I entered in the Serial Number for the SQL Agent 2000, rebooted and voila the problem was solved.

Zelandakh, yes I could've done that, but with 50 Gig with of DB files it would've been a bit too much. Thanks for the reply :)
 
Why is it too much with 50 Gig of files? I have 180 GB of data and I am backing up to disk via SQL Server 2000 and then using Veritas BE 8.6 to copy the backup files to tape.

-SQLBill
 
It's a space consideration. If I threw everything to disk we would near capacity on our disk drives that's all. I'm not saying that having SQL Server throw the data to disk and then back it up that way isn't a viable option. It just isn't an option for us.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top