Forum Discussion

KvKvK's avatar
KvKvK
Level 3
10 years ago
Solved

SQL DB Restore Problem

Hi, one of our clients currently has an error when trying to restore an SQL 2000 Database.

Here are the facts:

- The original Windows Server 2003, where the instance was active, is long gone and there is no system backup (there are databases on a tape from 2006, though).

- SQL Server 2000 with SP3 was installed to another Windows Server 2003 system.

- When performing the redirected restore the following error occurs after approx. 25 minutes:

0xE0000346 - The selected database appears to have been backed up from a newer version of SQL Server. Backups made from newer versions of SQL Server cannot be restored to older versions of SQL Server.

ID: V-79-57344-838

 

Of course, nothing is restored. So according to the error, there is a mismatch between the SQL Server versions. As per this article, the exact build number must match: https://support.symantec.com/en_US/article.TECH60821.html

As per this article, the SP level must match: https://support.symantec.com/en_US/article.TECH56694.html

There is a screenshot of the configuration of the database, which shows SQL version 8.00.760 (SP3) from January, 2006. The backup is from June, 2006.

 

So here is my question: Is there any way to find out which SQL build number is expected on the target machine, without performing the actual restore? Microsoft released more than 50 hotfixes / patches which change the SQL Server build number between SP3 (August 27, 2003) and June, 2006 and it would cause a devastating amount of effort to try every single patch level...

  • No,I haven't seen anything specific shown on an SQL, Exchange or other DB backup that shows the specific version number. By this I mean within BE itself.

    Are you also trying to restore the SQL 2000 DB onto something newer?

    Have you tried to duplicate the SQL DB to disk and then just mount it in SQL?

    THanks!

  • SGMon debugging on the BE server and the remote server will give you the version number which is expected on the target machine.
     

  • First of all, thanks to both of you for your answers. I forwarded the information and the client just replied with some logfiles which were captured with the SGMon tool on both of the servers.

    The only information concerning the SQL version can be found in the DC01-SGMon.log file. Please see the snippet below and the complete logfiles from both servers in the attachment.

    Edit: It's easy to misinterpret my post. What I meant to say was I can't find the expected SQL DB in the logfiles. Do you have any hint how to get the information with SGMon?

    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2_FindDrives - a default SQL Service is installed on DC01.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2_FindDrives - the default SQL Service appears to be SQL 2000.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - IsServiceClusterOk called on DC01
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - Found SOFTWARE\MICROSOFT\MSSQLServer in the registry.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 VCS cluster keys do not appear to be present in the registry
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 Failed to open VCS cluster ()
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2_CreateDLE - creating DC01.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL Version 2000
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - Found SOFTWARE\MICROSOFT\MSSQLSERVER in the registry.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\ese]           - [FSYS:ESE07]   FindDrives ... This is not an Exchange Server (0)
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [beutil]             - Input Error (       0) for Type: (43)
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\shared]        - FS_BlowOutMachine: entered -->DC01<--
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\shared]        - FS_BlowOutMachine: device already in DLE list
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2: Attempting attach with username ''
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2_Connect worked.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL Agent: Version String { 8.00.760 }
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL 2000 Service Pack 3.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - Build = 760
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL edition returned: Enterprise Edition
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\shared]        - Attach to DC01
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\shared]        - Detach from DC01
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL DBClose
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2_CleanUpSnapInfoList called.
    BEREMOTE: [04.27.15 14:52:20] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2: Attempting attach with username ''
    BEREMOTE: [04.27.15 14:52:21] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL2_Connect worked.
    BEREMOTE: [04.27.15 14:52:21] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL Agent: Version String { 8.00.760 }
    BEREMOTE: [04.27.15 14:52:21] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL 2000 Service Pack 3.
    BEREMOTE: [04.27.15 14:52:21] [0000]     04/27/15 14:52:18 [fsys\sql2]          - Build = 760
    BEREMOTE: [04.27.15 14:52:21] [0000]     04/27/15 14:52:18 [fsys\sql2]          - SQL edition returned: Enterprise Edition

     

  • This is the error-

     attempt to restore Version 539 database to Version 4 instance

    From BE 2012 onwards, we store version numbers as a single digit whereas older versions of BE used 3-digit version numbers. So if you are using BE 2012, pls ensure the media server and the remote agent are both patched with SP4 and then attempt the restore or, use an older version of BE to run the restore.

  • Hi VJware, thanks for your post! I got the reply that Backup Exec 2010 R3 is installed. If I read your post correctly, the restore should work with this version, right? Unfortunately, it doesn't work. :(

    Do you have any other ideas? Maybe the restore has to be started with the version which was used back in 2006 (I'm guessing some old version of Veritas Backup)?

     

    Edit: The exact version used to create the backup was: VERITAS Backup Exec 10.0.5484

  • The restore works with this version! Thank you so much VJware, you're a real lifesaver! :)