Australian cloud for business software — built and run in Sydney since 2002

NetLeverage
NetLeverage

SQL Server restore error 3169 or 3241: backup from a newer version, or a media family SQL Server cannot read

Technical article
Backup & Recovery

About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.

Error 3169 says the backup was taken on a newer SQL Server version than the server you are restoring to, and Microsoft is explicit that no backup can be restored to an earlier version. Error 3241 says "the media family on device is incorrectly formed". It is a different message with a less specific cause. Read the backup header first to see which version wrote the file, and restore on a server of the same or a newer version.

What the error means

Error 3169. Microsoft's MSSQLSERVER_3169 page (metadata date 2017-04-04) gives the message as: "The database was backed up on a server running version %ls. That version is incompatible with this server, which is running version %ls. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server." The page explains that certain features affect the structure of the database files, so the format may not be compatible with a different version of the engine. Its worked example is old: vardecimal storage restored to a version earlier than SQL Server 2005 SP2. Its user action is to determine the version on the originating server (right-click the server and choose Properties in SSMS, or run SELECT @@VERSION;).

The rule behind it is on the RESTORE page (metadata date 2023-05-18): "No SQL Server backup can be restored to an earlier version of SQL Server than the version on which the backup was created." The restore and recovery overview (metadata date 2024-12-04) repeats it as an Important note: this holds "regardless of the recovery model of a database". Backups of master, model and msdb created by an earlier version also "cannot be restored by SQL Server" on a later version, per the RESTORE page.

Restoring forward is allowed, but it is one-way. The SSMS restore page (metadata date 2023-12-08) says a restored older-version database "will automatically upgrade to the new version. This prevents the database from being used with an older version of the Database Engine." The RESTORE arguments page says the upgrade happens when WITH RECOVERY is specified.

Compatibility level is not the on-disk version. The compatibility level page (metadata date 2026-08-25) says the setting provides backward compatibility "in what relates to Transact-SQL and query optimization behaviors only". A database set to level 130 on a newer server still cannot be restored to an older server. The same page keeps the existing level for databases restored from earlier versions.

Error 3241. Microsoft's 3,000 to 3,999 error list gives the message as: "The media family on device '%ls' is incorrectly formed. SQL Server cannot process this media family." Microsoft gives no cause list for 3241 and has no dedicated page for it. The BACKUP page (metadata date 2026-03-02) describes striped sets: the number of devices in a stripe set must stay the same unless the media is reinitialised with FORMAT, and a device that is part of a stripe set cannot be used for a single-device backup without FORMAT. Microsoft does not document whether a damaged copy, a non-backup file or a missing stripe produces 3241 specifically; the table below lists them as checks to rule out.

Likely causes

Cause What you see How to confirm
Backup from a newer SQL Server version (3169) Message names both versions Compare SoftwareVersionMajor in RESTORE HEADERONLY with the target's @@VERSION
Backup from newer version reported as 3241 3241 on a backup that came from a newer server Same header comparison. Microsoft does not document this for 3241, but a version mismatch is a sensible first check
Backup written as a striped set but only some files supplied FROM lists fewer files than the backup used Count the files produced by the backup job and compare with the FROM DISK list
Incomplete or corrupted copy File size differs from the source file Compare size, and a checksum, with the source
File is not a native SQL Server backup RESTORE HEADERONLY fails or returns no useful rows Check which tool created the file
Feature-dependent format difference (3169) A newer feature is in use in the source database Per the 3169 page, check the features enabled on the original database

Prove the cause before changing anything

These checks follow the Microsoft pages cited. They have not been run or lab-tested.

  1. Record the target server's version:
SELECT @@VERSION;
  1. Read the backup header. RESTORE HEADERONLY (metadata date 2023-05-10) returns one row per backup set, with DatabaseName, ServerName, BackupFinishDate, DatabaseVersion, CompatibilityLevel, SoftwareVersionMajor, SoftwareVersionMinor, SoftwareVersionBuild, IsCopyOnly and Compressed. It requires CREATE DATABASE permission.
RESTORE HEADERONLY
FROM DISK = N'D:\Incoming\Sales_full.bak';

SoftwareVersionMajor is "the major version number of the server that created the backup set". Match it to the product using Microsoft's compatibility table: 17 is SQL Server 2025, 16 is 2022, 15 is 2019, 14 is 2017, 13 is 2016, 12 is 2014, 11 is 2012. Do not try to map the DatabaseVersion integer to a product. Microsoft's pages do not provide that mapping, and the CompatibilityLevel column describes the source database's behaviour setting, not the engine that wrote the file.

If HEADERONLY also fails on the target, run it on a server at the backup's version or newer, or ask the owner of the source server to read the header there. Microsoft does not document which errors HEADERONLY raises on an unreadable file. If it fails on every server, suspect the file itself.

  1. For a striped or multi-file backup, count the files the backup job produced and check that every file is named in the FROM clause. The HEADERONLY page notes that RESTORE HEADERONLY looks at all backup sets on the media.

  2. Compare the copied file's size, and ideally a checksum, with the source file. This is a practical step.

Fix

For 3169 (newer backup, older server). There is no downgrade restore. The choices are:

  1. Restore on a server running the backup's version or newer. If the target must stay on the old version, build or use a second server at the right version for the restore.
  2. Upgrade the target instance to the version in the header. This is a planned change with its own testing. Check the target's support dates first.
  3. Move the data back by scripting. Microsoft's Generate Scripts Wizard page (metadata date 2026-02-06) describes creating scripts "to transfer a database between instances of SQL Server". The advanced options include Script for server version ("Features new to a version can't be scripted for earlier versions"), Types of data to script (Data only, Schema only, or both; the default is Schema only) and Include unsupported statements. Run the wizard against the original newer server, choose the older target version and schema and data, then run the output on the target. Microsoft's page does not describe database size limits for data scripting, so test with a copy first. Large databases generate very large scripts, and features not supported by the older version are left out or flagged.

Changing the database's compatibility level does not help, per the compatibility page.

For 3241. Work through the checks in order. First compare versions as above. Then confirm the file copied completely, then confirm every part of a striped set is supplied. If another product wrote the file, its own restore tool is the route to read it. Do not run BACKUP ... WITH FORMAT against the source device to "repair" it. The BACKUP page says FORMAT "renders the entire media set unusable" if used on one volume of a set.

Confirm the fix

  • The restore completes and sys.databases shows state_desc ONLINE for the database.
  • The msdb restorehistory table (metadata date 2017-03-03) shows the restore row. Rows exist only on the instance that ran the restore.
  • The database kept its compatibility level, per the SSMS and compatibility pages (the level is kept only if it is at least the minimum allowed for that instance). If restored to SQL Server 2022 from an earlier version, Microsoft recommends running sp_updatestats on the database (RESTORE page). Plan a performance check, because upgrade can change plans.
  • Keep the original backup and the source server until the application owner has tested the restored copy. The upgrade is not reversible.

What to watch afterwards

  • Keep a short list of every instance's version, and make sure each disaster recovery or test restore target is the same or newer than every source.
  • Before an upgrade, restore a backup to a copy at the target version. This shows problems while the old server is still the production one.
  • If backups are copied between servers, record the size and a checksum at the source.
  • A repeat of 3169 after a patch cycle suggests servers drifted. Check for a server that was rebuilt on an older version.

Example (illustrative). A database backup Sales_full.bak from SQL01 is copied to SQL09 for a test restore. SQL09 returns error 3169. SELECT @@VERSION on SQL09 shows SQL Server 2019 (major version 15). RESTORE HEADERONLY on the file shows SoftwareVersionMajor 16, which is SQL Server 2022. The team restores on a SQL Server 2022 test server instead.

Risks and limits

  • These commands have not been run or lab-tested. Syntax comes from the pages cited.
  • Microsoft has no dedicated page for error 3241. The 3241 causes in the table are plausible readings of the message and of the documented stripe-set behaviour, not statements from Microsoft's documentation, so treat them as checks to rule out.
  • The 3169 page is dated 2017 and uses a pre-2005 example. The rule itself is restated in the 2023 and 2024 pages.
  • The scripting route has not been tested for large databases. A backup is the only full-fidelity copy of a database. Scripts do not carry everything.
  • Third-party backup products may write formats SQL Server cannot read. Microsoft does not document those formats.

Sources