.bak file is incorrectly formed error

I create a backup file in Enterprise Manager on SQL Server 2000. When I try
to restore this file using SQL Server 2005 Express on another machine, I get
the error "The media family on [my .bak file] is incorrectly formed. SQL
Server cannot process this media family. RESTORE HEADER is terminating
abnormally. (Error 3241)."
This same process has worked successfully several times, the last time in
September 2007. A backup file created in December 2006 will restore. What
has changed to cause this error now and how can it be fixed?
Thanking you in anticipation.I'd re-create the backup file, this should work. And, to be certain that the right steps are taken,
I'd do both the backup and the restore using TSQL commands instead of the GUI (BACKUP DTABASE and
RESTORE DATABASE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Roger Withnell" <RogerWithnell@.discussions.microsoft.com> wrote in message
news:481F37E4-F944-4F1C-A738-0075F7E2BD05@.microsoft.com...
>I create a backup file in Enterprise Manager on SQL Server 2000. When I try
> to restore this file using SQL Server 2005 Express on another machine, I get
> the error "The media family on [my .bak file] is incorrectly formed. SQL
> Server cannot process this media family. RESTORE HEADER is terminating
> abnormally. (Error 3241)."
> This same process has worked successfully several times, the last time in
> September 2007. A backup file created in December 2006 will restore. What
> has changed to cause this error now and how can it be fixed?
> Thanking you in anticipation.|||Thanks for this, but it didn't fix the problem.
Process is:
1 Use DTS to make a copy of operational database into laptop1 (this has SQL
server 2000). (Use of BACKUP DATABASE is prohibited on the operational
server, which is in a shared environment).
2 Make a backup with TSQL in laptop1 (I can restore from this backup in
laptop1 successfully).
3 Restore with this backup on laptop2 (running SQL Server 2005) using TSQL
gives the same error.
TSQL used is simply BACKUP/RESTORE DATABASE dbname TO/FROM DISK ='C:\...\file.bak
This process has worked successfully in the past. Last accomplished in
September 2007.
Thanking you in anticipation.
Roger
"Tibor Karaszi" wrote:
> I'd re-create the backup file, this should work. And, to be certain that the right steps are taken,
> I'd do both the backup and the restore using TSQL commands instead of the GUI (BACKUP DTABASE and
> RESTORE DATABASE).
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Roger Withnell" <RogerWithnell@.discussions.microsoft.com> wrote in message
> news:481F37E4-F944-4F1C-A738-0075F7E2BD05@.microsoft.com...
> >I create a backup file in Enterprise Manager on SQL Server 2000. When I try
> > to restore this file using SQL Server 2005 Express on another machine, I get
> > the error "The media family on [my .bak file] is incorrectly formed. SQL
> > Server cannot process this media family. RESTORE HEADER is terminating
> > abnormally. (Error 3241)."
> >
> > This same process has worked successfully several times, the last time in
> > September 2007. A backup file created in December 2006 will restore. What
> > has changed to cause this error now and how can it be fixed?
> >
> > Thanking you in anticipation.
>|||I see. So you have a 2000 backup, which restores successfully on 2000. But the same backup file
generates below error if you try to restore on 2005:
"The media family on [my .bak file] is incorrectly formed. SQL Server cannot process this media
family. RESTORE HEADER is terminating abnormally. (Error 3241)."
I would either assume that you don't really restore from the same file, or that some file copy
operation from laptop 1 to laptop 2 was unsuccessful. If you are 100% certain that it really is the
same file, then I'd open a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Roger Withnell" <RogerWithnell@.discussions.microsoft.com> wrote in message
news:F9BB51AA-2EE6-4C2E-98FB-62A3423BB0A4@.microsoft.com...
> Thanks for this, but it didn't fix the problem.
> Process is:
> 1 Use DTS to make a copy of operational database into laptop1 (this has SQL
> server 2000). (Use of BACKUP DATABASE is prohibited on the operational
> server, which is in a shared environment).
> 2 Make a backup with TSQL in laptop1 (I can restore from this backup in
> laptop1 successfully).
> 3 Restore with this backup on laptop2 (running SQL Server 2005) using TSQL
> gives the same error.
> TSQL used is simply BACKUP/RESTORE DATABASE dbname TO/FROM DISK => 'C:\...\file.bak
> This process has worked successfully in the past. Last accomplished in
> September 2007.
> Thanking you in anticipation.
> Roger
> "Tibor Karaszi" wrote:
>> I'd re-create the backup file, this should work. And, to be certain that the right steps are
>> taken,
>> I'd do both the backup and the restore using TSQL commands instead of the GUI (BACKUP DTABASE and
>> RESTORE DATABASE).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Roger Withnell" <RogerWithnell@.discussions.microsoft.com> wrote in message
>> news:481F37E4-F944-4F1C-A738-0075F7E2BD05@.microsoft.com...
>> >I create a backup file in Enterprise Manager on SQL Server 2000. When I try
>> > to restore this file using SQL Server 2005 Express on another machine, I get
>> > the error "The media family on [my .bak file] is incorrectly formed. SQL
>> > Server cannot process this media family. RESTORE HEADER is terminating
>> > abnormally. (Error 3241)."
>> >
>> > This same process has worked successfully several times, the last time in
>> > September 2007. A backup file created in December 2006 will restore. What
>> > has changed to cause this error now and how can it be fixed?
>> >
>> > Thanking you in anticipation.|||"Roger Withnell" <RogerWithnell@.discussions.microsoft.com> wrote in message
news:F9BB51AA-2EE6-4C2E-98FB-62A3423BB0A4@.microsoft.com...
> Thanks for this, but it didn't fix the problem.
> Process is:
> 1 Use DTS to make a copy of operational database into laptop1 (this has
> SQL
> server 2000). (Use of BACKUP DATABASE is prohibited on the operational
> server, which is in a shared environment).
I'm curious why BACKUP DATABASE is prohibited.
In my experience DTS never quite got the "copy db" process down well.
> 2 Make a backup with TSQL in laptop1 (I can restore from this backup in
> laptop1 successfully).
> 3 Restore with this backup on laptop2 (running SQL Server 2005) using
> TSQL
> gives the same error.
Hmm, obvious questions, like "32 bit vs 64 bit?" or different language?
And compression on the 2nd laptop?
> TSQL used is simply BACKUP/RESTORE DATABASE dbname TO/FROM DISK => 'C:\...\file.bak
> This process has worked successfully in the past. Last accomplished in
> September 2007.
> Thanking you in anticipation.
> Roger
> "Tibor Karaszi" wrote:
>> I'd re-create the backup file, this should work. And, to be certain that
>> the right steps are taken,
>> I'd do both the backup and the restore using TSQL commands instead of the
>> GUI (BACKUP DTABASE and
>> RESTORE DATABASE).
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://sqlblog.com/blogs/tibor_karaszi
>>
>> "Roger Withnell" <RogerWithnell@.discussions.microsoft.com> wrote in
>> message
>> news:481F37E4-F944-4F1C-A738-0075F7E2BD05@.microsoft.com...
>> >I create a backup file in Enterprise Manager on SQL Server 2000. When I
>> >try
>> > to restore this file using SQL Server 2005 Express on another machine,
>> > I get
>> > the error "The media family on [my .bak file] is incorrectly formed.
>> > SQL
>> > Server cannot process this media family. RESTORE HEADER is terminating
>> > abnormally. (Error 3241)."
>> >
>> > This same process has worked successfully several times, the last time
>> > in
>> > September 2007. A backup file created in December 2006 will restore.
>> > What
>> > has changed to cause this error now and how can it be fixed?
>> >
>> > Thanking you in anticipation.
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html