How to backup the transaction log when the database is damaged (Transact-SQL)

How to back up the transaction log when the database is damaged (Transact-SQL)

To create a backup of the currently active transaction log

1. Execute the BACKUP LOG statement to back up the currently active transaction log, specifying:
   • The name of the database to which the transaction log to back up belongs.
     
     
   • The backup device where the transaction log backup will be written.
     
     
   • The NO_TRUNCATE clause to back up the transaction log without truncating the inactive part of the transaction log.

     This clause allows the active part of the transaction log to be backed up even if the database is inaccessible, provided that the transaction log file(s) is accessible and undamaged.

2. Optionally, specify:
   • The INIT clause to overwrite the backup media, and write the backup as the first file on the backup media. If no existing media header exists, one is automatically written.
     
     
   • The SKIP and INIT clauses to overwrite the backup media, even if there are either backups on the backup media that have not yet expired, or the media name does not match the name on the backup media.
     
     
   • The FORMAT clause, when using media for the first time, to completely initialize the backup media and rewrite any existing media header.

     The INIT clause is not required if the FORMAT clause is specified.

Important  Use extreme caution when using the FORMAT or INIT clauses of the BACKUP statement as this will destroy any backups previously stored on the backup media.

Examples

This example backs up the currently active transaction log for the MyNwind database even though MyNwind has been damaged and is inaccessible. The transaction log, however, is undamaged and accessible:

BACKUP LOG MyNwind
   TO MyNwind_log1
   WITH NO_TRUNCATE
GO

See Also

BACKUP

Transaction Log Backups

Restoring a Database to a Prior State

Reducing Recovery Times

File and Filegroup Backup and Restore