Error 3169 The Backed-up Database Has On-disk Structure Version 611
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: Restoring SQL Server 2005 backup to SQL server 2000 SQL Server > SQL Server restore headeronly is terminating abnormally microsoft sql server error 3013 Database Engine Question 0 Sign in to vote I have a the media family on device is incorrectly formed sql 2008 sql 2005 backup that I am trying to restore in sql 2000. I get the following error.. Error:3169 The backed msg 3013 level 16 state 1 line 1 restore database is terminating abnormally up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Restore filelist is terminating abnormally. Is there a workaround for this? Vyanki Friday,
Msg 3241 Sql Server
June 09, 2006 10:22 AM Reply | Quote Answers 0 Sign in to vote No, there is no workaround. SQL Server 2005 does not support downgrades or restores to SQL Server 2000. Friday, June 09, 2006 2:53 PM Reply | Quote All replies 0 Sign in to vote No, there is no workaround. SQL Server 2005 does not support downgrades or restores to SQL Server 2000. Friday, the media family on device is incorrectly formed sql server cannot process this media family June 09, 2006 2:53 PM Reply | Quote 0 Sign in to vote thanks. what way can be come true the case. Friday, September 15, 2006 10:10 AM Reply | Quote 0 Sign in to vote There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000:Right-click on DB -> tasks -> generate scriptsselect DB and click "script all objects...", hit nextselect any options you want, specifically changing "script for server version" to SQL Server 2000next through and run the scriptNow just export data from the 2005 database to the newly-created 2000 database.Right-click on DB -> tasks -> export...set source and hit nextset destination and hit nextselect "copy data from one or more tables", hit nextselect all, check "optimize for many tables" and "run in a transaction"you may have to edit each table mapping and check "enable identity insert"next through to finish Friday, September 15, 2006 1:58 PM Reply | Quote 0 Sign in to vote Jonathan Fife wrote:There is no "Restore" functionality, but there is a workaround to copy 2005 databases to 2000:Right-click on DB -> tasks -> generate scriptsselect DB and click "script all objects
up Recent PostsRecent Posts Popular TopicsPopular Topics Home Search Members Calendar Who's On Home » SQL Server 2005 » Backups » Restore Dadabase From .bak Files 13 posts,Page 1 of 212»» Restore Dadabase From .bak Files Rate Topic Display Mode Topic Options Author Message sumanthchowdary.ksumanthchowdary.k Posted Thursday, July 17, 2008 10:00 AM Forum Newbie Group: General Forum Members Last Login: Monday, June 1, 2009 10:25 PM Points: 5, Visits: 14 HiOne https://social.msdn.microsoft.com/Forums/sqlserver/en-US/4c263da0-21f3-4434-8f10-6804a7c0a5bc/restoring-sql-server-2005-backup-to-sql-server-2000?forum=sqldatabaseengine of my cus send the Database file(.bak only).He is using the SQL Server 2005 (Enterprise Edition).I am Unable ADD the Same to My SQL Server 2005(Developer Edition)I Tried Several Ways To add the Database BUT I am to DO SOI am Getting the ERROR MSG As"Msg 3241, Level 16, State 7, Line 1The media family on device 'E:\Program Files\Microsoft http://www.sqlservercentral.com/Forums/Topic536132-357-1.aspx SQL Server\MSSQL.1\MSSQL\Backup\Hills.bak' is incorrectly formed. SQL Server cannot process this media family.Msg 3013, Level 16, State 1, Line 1RESTORE DATABASE is terminating abnormally."Plz help to solve the issueThanks & RegardsSumanth Post #536132 MANU-J.MANU-J. Posted Thursday, July 17, 2008 11:10 AM SSCommitted Group: General Forum Members Last Login: Thursday, May 22, 2014 7:04 AM Points: 1,688, Visits: 8,766 Whats the output of restore verifyonly fom disk='Backupfilenamewithpath'?Manu Post #536180 Carl FederlCarl Federl Posted Thursday, July 17, 2008 11:31 AM SSCrazy Group: General Forum Members Last Login: Tuesday, September 20, 2016 9:44 AM Points: 2,316, Visits: 4,345 The backup file may be corrupted such as by FTPing with char mode instead of binary and can be checked by running:RESTORE VERIFYONLYfrom disk = 'E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\Hills.bak'Your version of SQL Server may be a lower version than the client's and a restore to a lower version is not supported. The version used for the backup can be obtained by running:restore headeronly from disk = 'E:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\Hills.bak' SQL = Scarcely Qualifies as a Language Post #536185 sumanthc
and shrinking the transaction log Backing up the tail Inside the transaction log So, what's in a backup file? Test: A full backup does not contain deleted data Verifying backup files Verifying backup files on a budget Cumulative backups Recovering individual http://www.sqlbackuprestore.com/errormessageswhenrestoring.htm tables Backup and restore history details Backup reads and writes Speeding up backups Backup speed http://venkatsangusqldba.blogspot.com/2015/05/error-messages-when-restoring-from.html details Speeding up restores Restore state affects speed too Backup and restore rights Log shipping Log shipping in SQL Server 2000 Setting up log shipping using Enterprise Manager Checking the set up Failover Log shipping in SQL Server 2005 Setting up log shipping using Management Studio Checking the set up Log shipping status report Failover Log shipping in SQL Backup sql server Using the CopyTool utility Failover 3rd party backup applications VDI VDI versions VDI errors SQL Backup - beyond compression Restoring a chain of transaction log backups Restoring to the latest possible state Backing up multiple databases Backup retention Making a copy of the backup file Backup file naming conventions Restoring the latest backup set Network resilience Encryption Integrated database verification Database file relocation Improved backup retention RESTORE HELP High-availability group support Common SQL Backup is terminating abnormally issues Installation checklist Setting up rights Configuring service rights Backup data Hanging issues Common backup and restore errors Error 3201 - when performing a backup to a network share Full database backup file is larger than database size Error 3205 - Too many backup devices specified for backup or restore Error 4305 - an earlier transaction log backup is required Bringing a database that is in recovery or read-only mode online Using bulk-logged recovery model but transaction log backup is still large Error 14274 - unable to delete SQL Server Agent job Error messages when restoring from different versions of SQL Server. Pending vdi error codes Restore speed details Help, my transaction log file is huge! Mirror or log ship You cannot restore a backup created with a newer version of SQL Server on an instance running an older version of SQL Server. Unfortunately, the error messages that are displayed may not always tell you that it is a versioning problem. These are some of the error messages raised when trying to restore a backup file that is not backwards compatible. SQL Server 2008 R2 to SQL Server 2008 Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. E
Server 2008 Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 R2 to SQL Server 2005 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device 'f:\temp\test001_sql2008r2.bak' is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 R2 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 661. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 to SQL Server 2005 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device 'f:\temp\test001_sql2008.bak' is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 655. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2005 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. Posted by s vr at 9:13 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Administration, History, MSSQL Admin, Rename database, SQL 2000/2005/2008/2008R2/2012/2014, SQL DBA, SQL Server 2012, venkatsangusqldba.blogspot.in Newer Post Older Post Home Subscribe to: Post Comments (Atom) Blog Arc