Error Message when dumping to hard drive backup device

By Bill Graziano on 12 July 2000 | Tags: Backup/Restore


Justin writes "When I dump to a hard drive backup device, several of my database backups fail with the following information (in the event log of NT 4.0) . . .

Event ID: 17055
Source: MSSQLServer
Type: Information
Category: Kernel
Description: 3266: The Microsoft Tape Format (MTF) soft filemark database on backup device 'POD01_DUMP' cannot be read, inhibiting random access.

Basically, this error message reads like a tape drive problem, but I am dumping my files to hard drive using the "Dump Database....with INIT" commands within a job to do it. Technet has nothing to say on the matter, except to indicate that this an error of severity type 10, and I have also checked with other SQL sources to no avail.


After a couple of emails back and forth on this for more details the answer actually came from Spyder (Brent). Apparently the backup process was interrupted and this caused the BAK file to become corrupt. This also made it impossible to restore from the BAK file which was another reported symptom. The BAK files were deleted and recreated and all works fine now. Credit to Spyder.


Related Articles

Scheduling Jobs in SQL Server Express - Part 2 (1 December 2008)

Scheduling Jobs in SQL Server Express (27 August 2008)

Introduction to SQL Server 2005 Database Backups (19 December 2007)

BACKUP and RESTORE in SQL Server -- Full Backups (12 February 2007)

Database Backup Script (28 October 2002)

SQL Server administration best practices (20 September 2001)

Can I Backup Across the Network? (17 August 2000)

Other Recent Forum Posts

My informix Sql query retruns Null always (18h)

Vehicle availability query (1d)

SSDT - Unable to reference 'master' or 'msdb' with new sdk style project (1d)

Ola Hallengren backup jobs (2d)

Compare alpha results to INT after get values from a string (5d)

Query performance Call Center data (7d)

Looking for on Premises tool to read data from SQL logs and populate data warehouse (7d)

Possible SQL 2014 to 2016 Issue - Some Application Functions Slow/Failing (7d)

- Advertisement -