March 12, 2009 at 8:28 pm
I've got a bit of a dilemma here.
Windows 2003 R2 Standard (x64)
SQL Server 2000 SP4 (standard install, no named instances)
Backup Exec 11d
Everything has been working fine up until I rebooted last weekend to move the server. Now, my Backup Exec jobs fail because it can't find the local SQL Server. If I go to create a new backup job, my SQL server isn't shown in the selection list. I originally thought it was an issue with BE, but I went to install another 3rd party program that requires SQL Server and it said that it cannot install because it too can not find an instance of SQL Server running.
Both the SQL Server and SQL Server Agent are running under the Services window and all of our current database apps work properly both remotely and locally. I'm not sure how BE and this 3rd party software recognize that SQL Server is installed.
I'm starting to get a little nervous. I've been doing backups through EM and picking them up on tape nightly, but I haven't had a normal backup since last week.
Any suggestions?
Thanks,
Marty
March 12, 2009 at 9:02 pm
First the backups from SQL going to disk and then tape is way more stable and BE. Issues like this are one reason that the agent with BE makes me nervous. Have you pointed BE at another server and restored? I'd make sure of that.
Second, you need to determine how BE is connecting. I'd contact them. Might be some pending change in SQL that messed you up. Look in the SQL error log for the startup messages. These will tell you how it's listening for connections (protocols, IPs, ports, etc.)
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply