MichaelBalack
asked on
SQL Restoration failed, why ?
This is using a MS Windows 2008 with MS SQL 2008 R2, as a production DB server. Another server, using MS Windows 2003 with MS SQL 2008 R2, act as a DC and standby DB server. There is an important DB - ABC, is running in production, and a backup was scheduled to run every night. The backup was ran successfully.
Now, we want to verify that the standby server can be promoted as a production server when this original db production server is down. So, we did a test, by copy one of the *.bak file to this server, and select "restore Db", and follow the procedure. However, attempt to restore failed with following error:
ITLE: Microsoft SQL Server Management Studio
-------------------------- ----
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Conne ctionInfo)
-------------------------- ----
ADDITIONAL INFORMATION:
The media family on device 'C:\TradarBE_backup_2014_0 3_20_00003 9_0605782. bak' is incorrectly formed. SQL Server cannot process this media family.
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3241&LinkId=20476
-------------------------- ----
BUTTONS:
Please advise
Now, we want to verify that the standby server can be promoted as a production server when this original db production server is down. So, we did a test, by copy one of the *.bak file to this server, and select "restore Db", and follow the procedure. However, attempt to restore failed with following error:
ITLE: Microsoft SQL Server Management Studio
--------------------------
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.Conne
--------------------------
ADDITIONAL INFORMATION:
The media family on device 'C:\TradarBE_backup_2014_0
RESTORE HEADERONLY is terminating abnormally. (Microsoft SQL Server, Error: 3241)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.1399&EvtSrc=MSSQLServer&EvtID=3241&LinkId=20476
--------------------------
BUTTONS:
Please advise
Also, make sure the SQL Service Packs and Patches/Hotfixes/etc. are at exactly the same level on both servers. (Technically I guess the machine on which you restore could be a later version, but definitely not an earlier version.)
ASKER
Hi ScottPletcher,
Will check it.
Will check it.
ASKER
Hi ScottPletcher,
You are right. Production server is using MS SQL 2008 R2 w/SP 2 (10.50.4000.0), while the standby server is using MS SQL 2005 RTM (9.00.1399.06). So, does this means that I have to upgrade the standby server with MS SQL 2008 R2 w/SP2? BTW, can I upgrade directly?
You are right. Production server is using MS SQL 2008 R2 w/SP 2 (10.50.4000.0), while the standby server is using MS SQL 2005 RTM (9.00.1399.06). So, does this means that I have to upgrade the standby server with MS SQL 2008 R2 w/SP2? BTW, can I upgrade directly?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great!
other than that, the reason could be that the backup was configured to write to several files, and not just one.
you may want to try with a new, fresh, dedicated backup file