When you create a backup with Microsoft Sql Server, the resulting file is in Microsoft Tape Format.
Different versions of SQL Server apparently use different version of this format.
Which version of SQL server is required to restore a given file with a specific format version?
Can I somehow influence the version SQL server uses when creating a backup?
Background:
I am currently trying to restore a database backup created with an unknown version of SQL server, probably 2012. I have SQL Server Express 2008 R2. When executing the command
RESTORE VERIFYONLY FROM DISK='C:\myfile.bak'
I get the error
The media family on device 'C:\myfile.bak' was created
using Microsoft Tape Format version 1.8.
SQL Server supports version 1.0.
I guess this is simply a case of being unable to restore a database with an older version of SQL server, and there is nothing to be done about that besides upgrading. However I found no information about which MS tape format version corresponds to which sql server, and the error message is not very enlightening.
Therefore, in order to understand such error messages, I am interested in some general information about this format, in particular the exact correspondences between tape format version numbers to SQL Server version numbers.
Update:
It seems this is not simply a problem with the wrong version of SQL Server.
Restoring on SQL Server 2012 Express failed with the same error.
When executing a RESTORE HEADERONLY the resulting headers where
BackupName: *** INCOMPLETE ***
Position: 1
Every other column: NULL
I am currently in the process of acquiring another copy of the file.
Best Answer
The problem was indeed a corrupted backup, as Kin correctly deduced. Most likely the corruption was introduced during an ftp transfer.
So, when you get the error "The media family on device 'C:\myfile.bak' was created using Microsoft Tape Format version 1.8. SQL Server supports version 1.0." or the error "Specified cast is not valid. (SqlManagerUI)" when using the SQL Management studio Gui to restore a backup, you most likely have a corrupted backup file.
In my case, zipping the file before ftp transfer solved the problem.
You would think that backup files always contain a checksum, and if the file was later modified that sql server would report this incorrect checksum, but you would be wrong.