Konsultant może mieć w tym przypadku rację. Jeśli założymy, że pliki archiwum nie są uszkodzone, to oznacza to, że na tamtym komputerze (z XP) była nowsza wersja SQL Servera. Przy czym musisz wiedzieć, że ma znaczenie również wersja service pack-a. Mogło być tak, że w XP razem z aktualizacjami pobrał się SP do SQL-a, a na nowym kompie jeszcze nie masz tego SP. Czyli zainstaluj SP do SQL-a, który masz teraz i sprawdź jeszcze raz dearchiwizację.

Błąd wyskakuje taki:
Aktualizacja windows 7 zainstalowane.
Server SQL pobrałem :  2008R2

są zainstalowane.

Logi:


2016-05-25 08:51:16  Server  Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
   Jun 17 2011 00:54:03
   Copyright (c) Microsoft Corporation
   Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)

2016-05-25 08:51:17  Server  (c) Microsoft Corporation.
2016-05-25 08:51:17  Server  All rights reserved.
2016-05-25 08:51:17  Server  Server process ID is 1308.
2016-05-25 08:51:17  Server  System Manufacturer: 'To Be Filled By O.E.M.', System Model: 'To Be Filled By O.E.M.'.
2016-05-25 08:51:17  Server  Authentication mode is MIXED.
2016-05-25 08:51:17  Server  Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG'.
2016-05-25 08:51:17  Server  This instance of SQL Server last reported using a process ID of 3768 at 2016-05-24 21:13:11 (local) 2016-05-24 19:13:11 (UTC). This is an informational message only; no user action is required.
2016-05-25 08:51:17  Server  Registry startup parameters:
    -d c:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\master.mdf
    -e c:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\Log\ERRORLOG
    -l c:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\mastlog.ldf
2016-05-25 08:51:18  Server  SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2016-05-25 08:51:18  Server  Detected 2 CPUs. This is an informational message; no user action is required.
2016-05-25 08:51:22  Server  Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2016-05-25 08:51:30  Server  Node configuration: node 0: CPU mask: 0x0000000000000003:0 Active CPU mask: 0x0000000000000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2016-05-25 08:51:34  spid7s  Starting up database 'master'.
2016-05-25 08:51:35  spid7s  The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes.  1536 bytes at offset 543232 in file c:\Program Files\Microsoft SQL Server\MSSQL10_50.INSERTGT\MSSQL\DATA\mastlog.ldf will be written.
2016-05-25 08:51:36  spid7s  Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2016-05-25 08:51:36  spid7s  Recovery completed for database master (database ID 1) in 1 second(s) (analysis 285 ms, redo 67 ms, undo 150 ms.) This is an informational message only. No user action is required.
2016-05-25 08:51:38  spid7s  FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'INSERTGT'.
2016-05-25 08:51:42  spid7s  SQL Trace ID 1 was started by login "sa".
2016-05-25 08:51:42  spid7s  Starting up database 'mssqlsystemresource'.
2016-05-25 08:51:42  spid7s  The resource database build version is 10.50.2500. This is an informational message only. No user action is required.
2016-05-25 08:51:45  spid10s  Starting up database 'model'.
2016-05-25 08:51:46  spid7s  Server name is 'TOMSAT-KOMPUTER\INSERTGT'. This is an informational message only. No user action is required.
2016-05-25 08:51:46  spid7s  Informational: No full-text supported languages found.
2016-05-25 08:51:46  spid7s  Starting up database 'msdb'.
2016-05-25 08:51:48  Server  A self-generated certificate was successfully loaded for encryption.
2016-05-25 08:51:48  Server  Server is listening on [ 'any' <ipv6> 52251].
2016-05-25 08:51:48  Server  Server is listening on [ 'any' <ipv4> 52251].
2016-05-25 08:51:48  Server  Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\INSERTGT ].
2016-05-25 08:51:48  Server  Server named pipe provider is ready to accept connection on [ \\.\pipe\MSSQL$INSERTGT\sql\query ].
2016-05-25 08:51:48  Server  Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2016-05-25 08:51:48  Server  The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2016-05-25 08:51:48  Server  SQL Server is now ready for client connections. This is an informational message; no user action is required.
2016-05-25 08:51:48  spid10s  Clearing tempdb database.
2016-05-25 08:51:52  spid10s  Starting up database 'tempdb'.
2016-05-25 08:51:52  spid13s  The Service Broker protocol transport is disabled or not configured.
2016-05-25 08:51:52  spid13s  The Database Mirroring protocol transport is disabled or not configured.
2016-05-25 08:51:53  spid13s  Service Broker manager has started.
2016-05-25 08:51:53  spid7s  Recovery is complete. This is an informational message only. No user action is required.
2016-05-25 08:57:09  spid51  Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2016-05-25 08:57:09  spid51  Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.

Jak już byłby SSMS (najlepiej w wysokiej wersji) to można wykonać:

restore headeronly from disk='c:\katalog_backupu\archiwum.bak'
Odczytujemy następnie kolumny 'SoftwareVersionMajor' i 'SoftwareVersionMinor' ,które wskażą z jakiej wersji pochodzi backup.