10-07-2009 05:37 PM
Hi,
We are using Backup Exec V11d with SP4 on an application server. The application server had MS SQL server 2000, and we installed Backup Exec V11d on the server with a separate DB instance, and everything was working fine.
Our DBA upgraded MS SQL server 2000 to 2005, and after that all the Backup Exec services except "Device & Media servcie" can't be started on the server.
We have a test application server which has MS SQL server 2005, and I installed the same version(11d) of Backup Exec on the test server. Everything is working fine on this test server.
Please advise.
Thanks,
Anthony
Solved! Go to Solution.
10-21-2009 08:34 PM
10-07-2009 08:11 PM
Please let me know the error message you get when you try to start the servcie . also check the error in the event log ...
10-07-2009 09:35 PM
Hi
Thank you for the reply.
There is no relevant event logs.
The 2 following services status is "Starting" and it never ends, but I can see the 2 running processes(beserver.exe and beremote.exe) for the 2 services in the tassk manger.
- Backup Exec Server
- Backup Exec Remote Agent for Windows
Backup Exec Device & Media is running OK.
Backup Exec Job Engine and Backup Exec Agent Browser can't be started due to the service dependencies with Backup Exec Server service.
Anthony
10-07-2009 11:44 PM
10-08-2009 12:39 AM
10-08-2009 12:48 AM
10-08-2009 01:06 AM
Hi,
Here is the dbrecover.log.
Thanks,
Anthony
--------------------------------------------------------------------------------------------------------------------------
Backup Exec Database Recovery
10/08/09 08:44:19
-----------------------------
Initializing...
BEGetComputerName = 'KORSVR48700'
GetBeVirtualServerName = ''
Using node name for media server
CDBUtility::TrialConnectToSQL: sSQLServerInstanceName=KORSVR48700\BkupExec
Data for BE database:
Structure size: 6500
Media Server : KORSVR48700
Node, if clust:
SQL Server : KORSVR48700
Instance Name : BkupExec
SQL Instance : KORSVR48700\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..
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Database BEDB is ONLINE
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Getting files for database 'BEDB'
GetDatabaseFiles: GetNextResult success dbRowCount=-1
Database exists - nothing to do
Setting up for IDR...
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Getting files for database 'master'
GetDatabaseFiles: GetNextResult success dbRowCount=-1
OpenFromInitializationString Connection String = Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=master;Data Source=korsvr48700\BkupExec;Locale Identifier=1033;Application Name=BEWS DBUTIL hr=0x0
Getting files for database 'model'
GetDatabaseFiles: GetNextResult success dbRowCount=-1
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master$4idr
File Exist: TRUE
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog$4idr
File Exist: TRUE
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\model$4idr
File Exist: TRUE
File Exist Check: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\modellog$4idr
File Exist: TRUE
Deinitialize...
-----------------------------
Process completed
10/08/09 08:44:20
Status: DBU_SUCCESS
-----------------------------
10-08-2009 02:06 AM
10-08-2009 04:56 PM
10-08-2009 08:47 PM
10-08-2009 11:06 PM
10-21-2009 06:25 AM
10-21-2009 06:34 AM
10-21-2009 06:24 PM
Hi,
Our DBA has confirmed that the BACKUPEXEC instance is working fine, and the dbrecover.log looks OK.
Any others can cause the Backup Exec server service and Backup Exec remote agent service hang(The service status is "Starting")
One interesting thing is that the processes(beserver.exe and beremote.exe) for the 2 services are running(I can see the processes in task manager), but the startup status of the 2 services is "Starting"
Any advices would be highly appreciated.
Anthony
10-21-2009 08:34 PM
10-22-2009 12:06 AM
10-22-2009 12:27 AM