02-19-2010 04:45 AM
We just performed a complete Intelligent Disaster Recovery. Everything seemed to go well, the operating system and files are all there. But there seems to be a problem with the SQL-databases (we also have the Backup Exec SQL agent). Therefore I want to do a restore of the SQL user databases once more. But to do that, I need to access BackupExec 12.5 - and there is the problem. The services are not starting up!
Here you have two following error messages retrieved from the event-log
Log Name: Application
Source: MSSQLSERVER
Date: 2010-02-19 13:01:52
Event ID: 5123
Task Category: Server
Level: Error
Keywords: Classic
User: MIKROV\AdminSE
Computer: SVERIGESRV1.valhalla.local
Description:
CREATE FILE encountered operating system error 5(failed to retrieve text for this error. Reason: 15105) while attempting to open or create the physical file 'C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf'.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSSQLSERVER" />
<EventID Qualifiers="49152">5123</EventID>
<Level>2</Level>
<Task>2</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-02-19T12:01:52.000Z" />
<EventRecordID>20071</EventRecordID>
<Channel>Application</Channel>
<Computer>SVERIGESRV1.valhalla.local</Computer>
<Security UserID="S-1-5-21-2131191430-715879785-316617838-3683" />
</System>
<EventData>
<Data>5(failed to retrieve text for this error. Reason: 15105)</Data>
<Data>C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf</Data>
<Binary>03140000100000000C00000053005600450052004900470045005300520056003100000000000000</Binary>
</EventData>
</Event>
Error 2:
Log Name: Application
Source: Backup Exec
Date: 2010-02-19 13:01:52
Event ID: 58068
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SVERIGESRV1.valhalla.local
Description:
The Backup Exec Device and Media Service could not start because the database recovery has failed. Refer to the database recovery log for details.
For more information, click the following link:
http://eventlookup.veritas.com/eventlookup/EventLookup.jhtml
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Backup Exec" />
<EventID Qualifiers="8192">58068</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2010-02-19T12:01:52.000Z" />
<EventRecordID>20072</EventRecordID>
<Channel>Application</Channel>
<Computer>SVERIGESRV1.valhalla.local</Computer>
<Security />
</System>
<EventData>
</EventData>
</Event>
I tried to repair and recover the database with the BackupExec utility - but it didnt help. Can you please help me as soon as possible!
Regards,
André
02-19-2010 05:06 AM
I have found some more information about this issue, in another posts. But I still dont know exactly how to proceed. I found this in the recovery log:
GetDatabaseStatus
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=SVERIGESRV1;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
GetDatabaseStatus status=NOT EXIST
Database BEDB does not exist
File Exist Check: \\SVERIGESRV1\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: FALSE
File Exist Check: \\SVERIGESRV1\C$\Program Files\Symantec\Backup Exec\Data\BEDB.bak
File Exist: TRUE
Recover from backup file...
File Exist Check: \\SVERIGESRV1\C$\Program Files\Symantec\Backup Exec\Data\BEDB.bak
File Exist: TRUE
GetDatabaseStatus
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=SVERIGESRV1;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
GetDatabaseStatus status=NOT EXIST
Database BEDB does not exist
Fixing up any database linkage problems for 'BEDB'
Execute command: declare @@stemp as varchar(32)
select @@stemp = isnull(convert(varchar,databasepropertyex('BEDB','status')),'NOT EXIST')
print 'Database status: ' + @@stemp
if @@stemp <> 'ONLINE' and @@stemp <> 'NOT EXIST'
begin
print 'Forcing database detach'
EXEC sp_detach_db 'BEDB'
end
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=SVERIGESRV1;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
(null)
File Exist Check: \\SVERIGESRV1\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: FALSE
File Exist Check: \\SVERIGESRV1\C$\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
File Exist: FALSE
Create database BEDB
Execute command: create database BEDB on(name=BEDB_dat, filename='C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf') log on (name=BEDB_log, filename='C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf')
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=SVERIGESRV1;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
(null)
(null)
Execute command failed: 0x80040e14
OS ERROR: 0x80040e14 (-2147217900)
Deinitialize...
-----------------------------
Process completed
02/19/10 13:22:31
Status: DBU_ERROR_DATABASE_CREATE_FAILED
-------
So I now know that the files are missing, but what now?
02-19-2010 05:29 AM
02-19-2010 02:12 PM