Consider the following scenario:
- You enable the transparent data encryption (TDE)-compressed function in an instance of Microsoft SQL Server 2016 or 2017.
- You back up databases to a different server that uses Universal Naming Convention (UNC) paths.
- The backup on the disk uses the 512-byte Emulation advanced format.
- You use a nondefault MAXTRANSFERSIZE in the backup command to enable backup compression.
When you restore the backup In this scenario, the operation may be unsuccessful, and you receive error messages for some large databases that resemble the following:
Msg 3287, Level 16, State 1, Line LineNumber
The file ID 1 on device 'backup file path' is incorrectly formed and can not be read.
Msg 3013, Level 16, State 1, Line LineNumber
RESTORE DATABASE is terminating abnormally.
This fix is included in the following updates for SQL Server:
- This update must be applied on the server in which the backup originates.
- This update does not resolve the error if the backup has been taken prior to applying the update. In this situation, a new backup must be taken.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
To verify the kind of drive that you have, follow these steps:
- Install update KB 982018.
- Run the following command from elevated command prompt:
Fsutil fsinfo ntfsinfo <drive>Note <drive> represents the drive that you are checking.
- Use the values for Bytes per sector and Bytes per physical sector in the following tables to determine the kind of drive that you have.
Bytes per sector value Bytes per physical sector value Drive type 4096 4096 4K native 512 4096 Advanced Format (also known as 512E) 512 512 512-byte native