MSSQL$BKUPEXEC Master.mdf missing

[VPCNC]

I can't start Backup Exec because one of the Services is not started.
MSSQL$BKUPEXEC

Using the Command Prompt I tried to Start the Service with the Following Command

"C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\Binn\sqlservr.exe" -sBKUPEXEC

It results in the Following Error

2006-01-24 11:37:08.54 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: )

2006-01-24 11:37:08.54 server Copyright (C) 1988-2002 Microsoft Corporation.

2006-01-24 11:37:08.56 server All rights reserved.
2006-01-24 11:37:08.56 server Server Process ID is 3152.
2006-01-24 11:37:08.56 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\ERRORLOG'.
2006-01-24 11:37:08.57 server initconfig: Error 2(The system cannot find the file specified.
)opening 'C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC\Data\master.mdf' for configuration information.

I was able to Locate the Master.MDF file in a folder called SAFE.

I copied the Files from the SAFE folder to the DATA folder and re-ran the Command.

This is the New Errors I get

Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.2 (Build 3790: )

2006-01-24 11:58:54.06 server Copyright (C) 1988-2002 Microsoft Corporation.

2006-01-24 11:58:54.06 server All rights reserved.
2006-01-24 11:58:54.07 server Server Process ID is 4172.
2006-01-24 11:58:54.07 server Logging SQL Server messages in file 'C:\Program
Files\Microsoft SQL Server\MSSQL$BKUPEXEC\LOG\ERRORLOG'.
2006-01-24 11:58:54.12 server SQL Server is starting at priority class 'norma
l'(2 CPUs detected).
2006-01-24 11:58:55.93 server SQL Server configured for thread mode processin
g.
2006-01-24 11:58:55.95 server Using dynamic lock allocation. Lock Block
s, Lock Owner Blocks.
2006-01-24 11:58:56.01 spid4 Starting up database 'master'.
2006-01-24 11:58:56.17 spid4 Error: 823, Severity: 24, State: 2.
2006-01-24 11:58:56.17 spid4 Error: 3313, Severity: 21, State: 2.
2006-01-24 11:58:56.18 spid4 Cannot recover the master database. Exiting.

How do I recover or Re-build the Master.MDF and other needed files so I can get the Service to Run?

[VPCNC]

I was able to Solve my Problem.

First I did a Repair Installation of Veritas 9.1 for Windows 2003 SBS
Reboot the Server.
Not sure this was needed but I did the repair just incase.

Next I had to Repair the 2000 MSDE version of MSSQL

Go to the Following Web Site and Download the SP4 patch

http://www.microsoft.com/downloads/details.aspx?familyid=8E2DFC8D-C20E-4446-99A9-B7F0213F8BC5&displaylang=en

After you download the installer run it and it will unpack itself to an Installation folder.

Shut down any service related to MSSQL server if they are running, and all of the BackupExec Services.

On the Server you want to Install it to, browse to the following Folder and re-name the folder to something else.

C:\Program Files\Microsoft SQL Server\MSSQL$BKUPEXEC

I changed the MSSQL$BKUPEXEC to xMSSQL$BKUPEXEC

Now you will have to open up a command prompt and then Change to the Directory where you unpacked the MSSQL installer to.

in my case it was
CD C:\SQL2KSP4\MSDE

Once in the correct Directory Execute the following command

setup INSTANCENAME="BKUPEXEC" SAPWD="PassWordHerer" /L*v C:\MSDELog.log

Replace the PassWordHere with a Strong Password of your own choice. You can't install MSSQL without a Strong password.

Once that is done, I was able to Start up all of the Services and get BackupExec working again.

I tried the Above without renaming the previous folder.
It failed because of the Previous installation was found and the database was corupt.
By Renaming the Folder / previous installation, I was able to preform a Clean Install using the Correct Instance name for BackupExec.