| Event Id | 3266 |
| Source | MSSQLServer |
| Description | The backup data in %ls is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. |
| Event Information | CAUSE: A filemark in the backup device specified in the BACKUP or RESTORE operation could not be read. Possible reasons include: 1. A media failure on the device where the backup is located. 2. A write failure during the creation of the backup, for example, a loss of connectivity during a network backup. 3. Often an operating system error will also be reported, such as when the disk is out of space or the path is not found. If so, this will indicate the underlying cause of the error. RESOLUTIION: Follow these steps: 1. Check the output from your BACKUP or RESTORE command as well as the SQL Server error log for related errors and troubleshoot them. 2. Verify that the specified backup file is not damaged. 3. If the backup device specified in the BACKUP or RESTORE command is on a remote server, retry the operation when connectivity between the machines will not be a problem, or move the backup device to the local server. 4. You can not add more backups to a disk file in this condition. If you want to back up to this disk file, use WITH FORMAT to overwrite it. If you want to restore from the damaged backup file, and there is more than one backup set in the file, some of those backup sets may be usable. Use 5. RESTORE HEADERONLY or RESTORE VERIFYONLY to find out what is in that backup file and whether any of the backup sets are usable. |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 3266 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.