08-27-2009 05:02 PM
I simply changed the server name of our BE server from HUBBLE2 to HUBBLE and now BE won't start (except for the Remote Agent).
I get the following EventID:
Log Name: Application
Source: Backup Exec
Date: 8/27/2009 2:46:09 PM
Event ID: 58068
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HUBBLE.ourdomain.com
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.
I looked online for the Event as well as other KB articles and performed the following:
1) I tried to use the BEUtility as one of the KB articles pointed out, and it displays my current server name with no info. If I try to reconfigure it or change the system account it fails trying to start the services. I'm afraid to delete it and it it back.
2) One of the articles I found suggested modifying the registry. Sure enough, there were several hardcoded paths with the old server name. I modified the registry (after exporting the HKLM\Software\Symantec\Backup Exec\ key) to change all instances of HUBBLE2 to HUBBLE. Tried BEUtility and no change. Tried to start the services manually and no change.
This is a very simple setup. The media server and BE (along with everything else in the suite) is installed locally, in the default folders.
Someone please help! I've spent months configuring this and I would have to uninstall/reinstall. Thanks in advance!
Here is what the databsae recovery log shows (dbrecover.log):
-----------------------------
Backup Exec Database Recovery
08/27/09 14:57:14
-----------------------------
Initializing...
BEGetComputerName = 'HUBBLE'
GetBeVirtualServerName = ''
Using node name for media server
Data for BE database:
Structure size: 6500
Media Server : HUBBLE
Node, if clust:
SQL Server : HUBBLE
Instance Name : BkupExec
SQL Instance : HUBBLE\BkupExec
SQL Service : MSSQL$BkupExec
Database : BEDB
App Data Path : C:\Program Files\Symantec\Backup Exec\Data
Database Path :
Database Log :
Database File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
Database Log : C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
Backup File : C:\Program Files\Symantec\Backup Exec\Data\BEDB.bak
Base File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.bak
Base Log File : C:\Program Files\Symantec\Backup Exec\Data\BEDB_log.bak
Is Local : TRUE
IsDatabaseMgr : TRUE
Recover database using best method..
GetDatabaseStatus
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=HUBBLE\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80004005
Error connecting to master database: hr = 0x80004005
OS ERROR: 0x80004005 (-2147467259)
Status of database BEDB is unknown
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=HUBBLE\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80004005
Error connecting to master database: hr = 0x80004005
Execute command failed: 0x80004005
Drop database BEDB
Execute command: drop database BEDB
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=HUBBLE\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80004005
Error connecting to master database: hr = 0x80004005
Execute command failed: 0x80004005
OS ERROR: 0x80004005 (-2147467259)
GetDatabaseStatus
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=HUBBLE\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80004005
Error connecting to master database: hr = 0x80004005
OS ERROR: 0x80004005 (-2147467259)
Status of database BEDB is unknown
File Exist Check: \\HUBBLE\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: TRUE
File Exist Check: \\HUBBLE\C$\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
File Exist: TRUE
Attach database BEDB
File Exist Check: \\HUBBLE\C$\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf
File Exist: TRUE
File Exist Check: \\HUBBLE\C$\Program Files\Symantec\Backup Exec\Data\BEDB_log.ldf
File Exist: TRUE
Execute command: sp_attach_db 'BEDB','C:\Program Files\Symantec\Backup Exec\Data\BEDB_dat.mdf','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=HUBBLE\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x80004005
Error connecting to master database: hr = 0x80004005
Execute command failed: 0x80004005
OS ERROR: 0x80004005 (-2147467259)
Deinitialize...
-----------------------------
Process completed
08/27/09 14:59:21
Status: DBU_ERROR_DATABASE_ATTACH_FAILED
-----------------------------
Solved! Go to Solution.
08-31-2009 10:08 PM
08-27-2009 05:05 PM
08-28-2009 11:37 AM
08-28-2009 10:48 PM
Please go through the following document:
http://seer.entsupport.symantec.com/docs/274102.htm
Please post the errors you receive on this. Change the path in the commands as per your current path where bedb_dat.mdf and bedb_log.ldf files are located.
Thanks
08-29-2009 01:13 PM
08-31-2009 10:59 AM
08-31-2009 01:20 PM
08-31-2009 01:47 PM
08-31-2009 10:08 PM