Forum Discussion

Ron_Russell's avatar
15 years ago
Solved

Database Scheme Version Mismatch

Server failed.  Rebuilt server and reinstalled Backup Exec 12.5 (on the server before it failed) with the intent of using the existing SQL database on an external SQL Server.  Detached the database and log and moved to safe location.  Installed 12.5 and SP4.  Detached the new database and log and moved.  Copied the old database and log back to original location (same as the new one was created).  Attached the old database.  Get the following error:

The Backup Exec Device and Media Service cannot start because it detected a database scheme version mismatch.

I was hoping to use the old database to save time.  Any suggestions on how I might get the version to match.  I read a little on BEMIG but it seemed to pertain to the SQL database on the local machine.

  • Thanks for all the replies.  I tried the first two but no success.  I didn't get a chance to try the last suggestion.  I went to the SQL server and viewed the SQL instance BEDB.  I found the version number to be BE 12.0 so I reinstalled version 12.0 and it picked up the database without creating a new one.  Of course this gives me more than I had but I will still have to catalog the tapes because there is no histrory under the restore tab.
  • Try using the BEutility and Use the copy database option and see if that helps ...

  • Try running bemig.exe on the new media server. With you changing the version of the service pack, your old DB wouldn't have been upgraded.
    Bemig would carry those changes through.
    Should that not work, leave your services stopped, and then run SP4's installation again. As long as you have another copy of the DB, this won't affect anything as you can always copy the backup version back again...
  • Perform the following steps on the new Backup Exec media server:

    1. Stop all Backup Exec services
    2. Stop the SQL Service
    3. Copy  your BEDB_DAT.MDF and BEDB_LOG.LDF files to the DATA folder in the default location
    4. Rename the DataPartition name for the Backup Exec Database that was copied.

    Refer to the steps mentioned below for renaming the DataPartition:

    a. Start the SQL Server (BKUPEXEC) service or SQL Service where Backup Exec is installed.
    b. Open a command prompt and type Sqlcmd -E -S servername\BKUPEXEC
    c. If successfully connected to the server, the following prompt appears: 1>  This indicates a connection to the Backup Exec instance using Sqlcmd.

    Run the following query from either Sqlcmd or from the SQL Management tools:
     
    Use bedb
    <Press enter>
    Type go
    <Press enter>
    SELECT partitionname FROM datapartition
    <Press enter>
    Type go
    <Press enter>

     
    After pressing ENTER the original server name is listed.  Running this query will yield the current database partition name that the database has (which is the old one)
    Change this name from the original server name to the new Backup Exec  server name by typing the command below. This will update the database with the partition name of the new server.
     
    UPDATE DataPartition SET PartitionName='<this server name>' WHERE PartitionID =0
    <Press enter>
    Type go
    <Press enter>
     
    Run the select statement again and verify that the name was changed to the new server name:

     
    SELECT PartitionName FROM DataPartition
    <Press enter>
    Type go
    <Press enter>



    Type quit to exit Sqlcmd


    5. Start all Backup Exec services - Start all the Backup Exec services which were stopped in Step 1.


  • Thanks for all the replies.  I tried the first two but no success.  I didn't get a chance to try the last suggestion.  I went to the SQL server and viewed the SQL instance BEDB.  I found the version number to be BE 12.0 so I reinstalled version 12.0 and it picked up the database without creating a new one.  Of course this gives me more than I had but I will still have to catalog the tapes because there is no histrory under the restore tab.