May 12, 2009 at 5:44 pm
Hi,
I am new to this site and I am stuck with login into SQL server 2005. I have veritas running and another application. Veritas has its own database, which is called BACKUPEXEC and the other application has its own databases.
Now I restored my server from disaster recovery and when I tried login into the server with database engine and machine name with windows credentials it will not let me in, but if I login with BACKUPEXEC as the instance name it will let me in.
I know I have to somehow restore the databases for the other application, but I am not able to start the MSSQLSERVER service. I can't even start it in single-mode. Any ideas? I would greatly appreciate all the help I can get. Thanks
May 12, 2009 at 8:12 pm
Can you provide any Event Viewer or SQL Log / SQL Agent Log errors?
--
Andrew Hatfield
May 12, 2009 at 8:46 pm
When you say you restored the server, how did you do that?
May 13, 2009 at 4:26 am
Thanks for your help. I have attached the event viewer log and the SQL log.
May 13, 2009 at 4:28 am
I used Veritas to restore my server. They have an add-in for disaster recovery, so I used that. Apparently it restored my BACKUPEXEC database in SQL server, but did not restore my other applicationd databases. Thanks.
May 13, 2009 at 4:34 am
Looks like it may not have restored the other instances.
Your event viewer shows
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
Does this file exist? does the account you are running the SQL Database Engine under have Full Control to the C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA directory and its contents?
--
Andrew Hatfield
May 13, 2009 at 4:56 am
You are right. That file does not exists. Apparently the backup did not restore that. How do I restore that now. Yes that folder does have full control.
May 13, 2009 at 5:12 am
I haven't used BackupExec in a while, but effectively you need to restore those files and any registry settings.
When you restored your server, did you do a full bare metal restore including the registry or did you reinstall windows and then restore files over the top?
Check services.msc - is the other SQL Instance listed?
If your backup includes the required files, restore them and then try starting the SQL instance.
--
Andrew Hatfield
May 13, 2009 at 8:42 am
And did you install SQL Server? Or does BackupExec do that in a bare metal restore?
Typically (non BackupExec) process is to install Windows (or restore), install SQL Server (or restore), then restore your databases into SQL Server, including master and msdb.
BackupExec might not have done this. Years ago (2001-timeframe), I had multiple issues with BackupExec doing this. What I changed to was using SQL Server to perform native backups and then using BackupExec to just pull these disk files to tape.
May 13, 2009 at 10:56 am
Steve,
No I did not install SQL server. BackupExec installed it for me when I ran the disaster recovery. Actually I do have the backups for all the databases. So you are telling me I have to uninstall SQL server 2005 from add/remove programs and then reinstall it? Could I just run the repair? Will that put back the master and msdb? What do you suggest? Thanks for your help so far.
May 13, 2009 at 11:04 am
Actually what I'd suggest if you call BackupExec and complain to them. It might be something simple.
I wouldn't necessarily uninstall and reinstall SQL, especially as I'm not sure how to pull back a master database restore from BE.
I will say that in a dozen or so attempts on different servers, I don't got one BE restore to work on a database, and never a system database. That's why I dropped their agent. It was too flaky for me. I know others have had better success, but a restore has to work 100% of the time, and easily, for me if the media can be read.
May 13, 2009 at 11:23 am
Andrew,
I installed Windows first, partitioned the drive. Then put the files back from the Tape. I believe all the servies are installed. Attached is the screenshot of the services. Do you see anything wrong that I am missing? thanks for your help so far.
May 13, 2009 at 11:26 am
Steve,
I don't they will answer the call because it did bring back the BACKUPEXEC database. They will probably tell me that we don't support the other application. Wish there was another way.
May 13, 2009 at 12:53 pm
They should support the restore of SQL. not the application, but the restore process.
It's more than services, there are registry settings along with the proper paths for files. If it's not all restored, it might not work.
you also need system databases restored for logins, jobs, etc.
May 13, 2009 at 3:40 pm
Steve,
I will give it a shot and see if they will give me support. Thanks for all your help so far. Will post back.
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply