Error message when you perform a database backup to disk or tape or a database restore from disk or tape: "3266," "3013" (290787)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
- Microsoft SQL Server 2005 Standard Edition
- Microsoft SQL Server 2005 Developer Edition
- Microsoft SQL Server 2005 Enterprise Edition
- Microsoft SQL Server 2005 Express Edition
- Microsoft SQL Server 2005 Workgroup
This article was previously published under Q290787 SYMPTOMS When you perform a database backup to disk or tape, or a
restore from disk or tape, the following error message may occur: SQL Server 7.0 Server: Msg 3266, Level 16,
State 1, Line 1 The Microsoft Tape Format (MTF) soft filemark database on
backup device 'devicename' cannot be read, inhibiting random access.
Server: Msg 3013, Level 16, State 1, Line 1 Backup or restore operation
terminating abnormally. SQL Server 2000 Server: Msg 3266, Level 16,
State 1, Line 1 The backup data in 'devicename' is incorrectly formatted.
Backups cannot be appended, but existing backup sets may still be usable.
Server: Msg 3013, Level 16, State 1, Line 1 BACKUP DATABASE is terminating
abnormally. SQL Server 2005Server: Msg 3013, Level 16, State 1, Line 1 The backup data at the end of 'devicename' is incorrectly formatted. Backup sets on the media might be damaged and unusable. To determine the backup sets on the media, use RESTORE HEADERONLY. To determine the usability of the backup sets, run RESTORE VERIFYONLY. If all of the backup sets are incomplete, reformat the media using BACKUP WITH FORMAT, which destroys all the backup sets. Server: Msg 3013, Level 16, State 1, Line 1
BACKUP DATABASE is terminating abnormally. CAUSE A filemark in the backup device could not be read. There
are many reasons why you may encounter a filemark error. Some of the
reasons include the following : - A media failure may occur on the device where the backup is
located.
- A write failure may occur during the creation of the backup.
For
example, a loss of connectivity may occur during a network backup. Or, a failure of the IO path to flush the write to disk may occur after the write to disk was reported to SQL server as successful.
WORKAROUND To allow SQL Server to perform new backups to the backup
device, you must manually delete or erase the device by using the following
command:
BACKUP DATABASE mydatabase TO DISK='C:\MyDatabase.bak' with FORMAT
If the error message occurs during a restore operation, it may be
possible to retrieve other backup sets from the device by specifying the file
number. For example, if three (3) backups were on one (1) backup device, backup
sets 1 and 2 may be usable. To determine if multiple backup sets are on a
device, run the following code from Query Analyzer:
RESTORE HEADERONLY FROM DISK='C:\MyDatabase.bak'
Each backup set has 1 entry in the output. To indicate a specific
backup set, use this code:
RESTORE DATABASE mydatabase FROM DISK='C:\MyDatabase.bak WITH FILE = FileNumber
Note FileNumber is the backup set number you want to restore.
Modification Type: | Major | Last Reviewed: | 12/20/2005 |
---|
Keywords: | kbBug kbpending kbprb KB290787 |
---|
|