cancel
Showing results for 
Search instead for 
Did you mean: 

migration backup exec 2010 r2

vdvas
Level 3

hi.

I migrate backup exec 2010 r2 from windows server 2008 r2 to another same version server.

All windows update and backup exec update are installed before migration.

I follow the instruction on the site.

But after migration i get error when i started the service "backup exec server"

The Backup Exec Server Service detected a schema version mismatch

The Backup Exec Server Service did not start. An internal error (-536813108)  occurred in object 1

i use bemig and start the service again, but got the error.

I tried to restore BE to another server and got the same problem.

Can anybody help me?

29 REPLIES 29

VJware
Level 6
Employee Accredited Certified

Do ensure the BE account has full rights to access the BE' registry keys. Using BEUtility, also "Grant Database Access" to the BE account.

Secondly, was BKUPEXEC available in the dropdown for new instance or was it typed manually while using BEUtility ?

 

vdvas
Level 3

i provided full access to BE account in registry hive:

hklm\software\symantec

hcu\software\symantec

I provided access using beutility to BE account.

I get error when change sql instanse using beutility.

BKUPEXEC is not available in dropdown menu. I typed it manually.

VJware
Level 6
Employee Accredited Certified

Is BKUPEXEC instance actually available (installed) ?

If yes, do ensure named connections & tcp/ip protocols are enabled.

vdvas
Level 3

What do you mean by your question

Is BKUPEXEC instance actually available (installed) ?

VJware
Level 6
Employee Accredited Certified

Check the list of available / installed SQL instances on the server and see if a named instance BKUPEXEC was created or not ?

By default, BKUPEXEC doesn't created unless you chose so.

vdvas
Level 3

I reinstall the sql server and have a name of instanse - bkupexec.

In services.msc i have 2 service of mssqlserver with different instanse name.

I run beutility and change sql instanse to BKUPEXEC. it's ok.

When i run backup exec i get error 

"user interface backup exec can be performed only as a fully trusted application, the security policy of .NET"

In logo of backupexec i see a inscription "trial version"

When i run ms sql management studio and connect to instanse BKUPEXEC in database list i see base BEDB.

When i connect to instanse MSSQLSERVER i see base BE_DLO.

 

vdvas
Level 3

i run the file "C:\Program Files\Symantec\Backup Exec\bkupexec.exe" as administrator and sbe is run.

I stop backupexec services

I rename value to "BKUPEXEC" in HKEY_LOCAL_MACHINE\SOFTWARE\Symantec\DLO\3.0\DB\DBInstance

I detach the BE_DLO from instance "MSSQLSERVER"

I attach BE_DLO in instance "BKUPEXEC"

I run the backupexec services, but "backup exec dlo administration service" is not run.

VJware
Level 6
Employee Accredited Certified

Are you using DLO along with BE ?

 

vdvas
Level 3

yes.

vdvas
Level 3

In panel of backupexec i run services Backup Exec.

Start all services

In windows log i see 3 error:

FCB::Open: Operating system error 32(Процесс не может получить доступ к файлу, так как этот файл занят другим процессом.) occurred while creating or opening file 'D:\SQL_bases\BE_DLO.mdf'. Diagnose and correct the operating system error, and retry the operation.

FCB::Open failed: Could not open file D:\SQL_bases\BE_DLO.mdf for file number 0.  OS error: 32(Процесс не может получить доступ к файлу, так как этот файл занят другим процессом.).

Database exception caught at line 460 of shadow\Server\consolesvc\consolesvc.cpp with error code 0x80040E14: ADODBError-_com_error: foundationerror=80040e14, comerr=80040e14, nativeerror=4294967295, conn=, query=, msg=IDispatch error #3092, src=Microsoft OLE DB Provider for SQL Server, desc=Unable to open the physical file "D:\SQL_bases\BE_DLO.mdf". Operating system error 32: "32(Процесс не может получить доступ к файлу, так как этот файл занят другим процессом.)"..

 

Translate the russian language:

The process can not access the file because the file is in use by another process