PRB: BACKUP with NO_TRUNCATE Not Possible with Missing Primary Data File

ID: Q218739

The information in this article applies to:

SYMPTOMS

If the primary data file (.mdf) for a database is inaccessible and a transaction log backup using NO_TRUNCATE is attempted, the following series of error messages will be generated:

Server: Msg 3446, Level 16, State 1, Line 1
Primary file not available for database 'pubs'.

Server: Msg 3013, Level 16, State 1, Line 1
Backup or restore operation terminating abnormally.

Any log records written since the previous log backup cannot be accessed or restored when a new database is brought online.


WORKAROUND

To work around this problem, ensure redundancy for any drive used to store the primary data file. For example, you can make the primary data file relatively small and store it on a mirrored drive, or you can create the file on a RAID 5 array. If you used either of these methods, multiple drive failures would have to occur for you to lose the file.

Additional query words: dump load catastrophic failure hot backup 


Keywords          : kberrmsg SSrvAdmin 
Version           : winnt:7.0
Platform          : winnt 
Issue type        : kbprb

Last Reviewed: March 4, 1999