BackupExec 10.0 5520 Upgrading to Sp1 rolls back!

Hello,

Please check for return value 3 in the bkupinst.log and paste the exact error message for further troubleshooting.

Bkupinst.log : located C:\WINDOWS


Note:- if we do not receive your reply within two business days, this post would be assumed answered and archived.

Hi

cant find a return code 3 in the log however this was in the last entry

01-16-2006,12:00:43 : Installing BE services.

01-16-2006,12:00:43 : Installing BE database.

01-16-2006,12:00:43 : Executing Attach_BEDB.
01-16-2006,12:00:43 : DRIVER={SQL Server};SERVER=ANC2003DC02;Trusted_Connection=Yes
01-16-2006,12:00:44 : Connected to SQL Server.
01-16-2006,12:00:44 : A previous BEDB database was found. Detaching current BEDB database now.
01-16-2006,12:00:44 : Database BEDB has been taken offline.
01-16-2006,12:00:44 : The original BEDB database was detached. The new BEDB database will now be attached.
01-16-2006,12:00:44 : Attaching BEDB to SQL Server.
01-16-2006,12:00:44 : EXEC sp_attach_db 'BEDB',@filename1 = N'e:\data\CRM\MSSQL\data\BEDB_Dat.mdf', @filename2 = N'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Log.ldf'
01-16-2006,12:00:44 : ERROR: Device activation error. The physical file name 'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Log.ldf' may be incorrect.


sql:EXEC sp_attach_db 'BEDB',@filename1 = N'e:\data\CRM\MSSQL\data\BEDB_Dat.mdf', @filename2 = N'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Log.ldf'


01-16-2006,12:00:58 : Rolling back stop of BE services.

Any ideas?

Jonathon

Just to add to my last post, I am not where the upgrade path is getting this entry for the location of the DB and log file as they do not reside in the c: location, but actually the e location.

01-16-2006,12:00:44 : EXEC sp_attach_db 'BEDB',@filename1 = N'e:\data\CRM\MSSQL\data\BEDB_Dat.mdf', @filename2 = N'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Log.ldf'
01-16-2006,12:00:44 : ERROR: Device activation error. The physical file name 'C:\Program Files\VERITAS\Backup Exec\NT\Data\BEDB_Log.ldf' may be incorrect.

Hello,

To resolve the issue please do the following:

Go to Start | Run

2. Type REGEDIT and press to open the Registry Editor
Note: Incorrect use of the Windows Registry Editor can have disastrous results on a server operating system. Great care should be taken when making changes to a Windows Registry. Registry modifications should only be carried-out by persons experienced in the use of the Registry Editor application.

3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\BEDatabase\Server Database Log Path. If the key does not exist, create one

a. Right-click on BEDatabase, select New | String Value, and enter the name Server Database Log Path . Type the path of the BEDB_Log.ldf file, where the path of the Database log file will be the path of the BEDB_Log.ldf .

Eg. If SQL is installed on the D drive with the default directory structure, add to the above registry the following path.

D:\Program Files\Microsoft SQL Server\MSSQL\Data


Thanks,

NOTE : If we do not receive your reply within two business days, this post would be marked assumed answered and would be moved to answered questions pool.

Thanks for the info, however the database is on a different server from the Backup Exec server. Does this key accept UNC paths?

Jonathon

Hello,

The key will accept the path. Do update us if the steps suggested by Sharvari have helped resolve the problem.

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.

Regards.