log files and recovery strategy

  • Is it possible to restore the "current" transaction log without first backing it up?

    I'm devising a backup/restore strategy for our new SQL Server 2000 system. I intend to put data files on one disk drive, and log files on another. In event of failure of the data disk, I would restore a database backup to a new drive, and then re-apply the transactions from the current log. This is standard practice with other DBMSs I've used.

    But all the documentation I've found on restore refers to restoring a backup (or several, 2-hourly, backups) of the log, not the log file actually in use at the time of failure. Is there really this restriction?

    Any help welcome

    Iain

  • You can backup the currently active transaction log even if the database file is damaged, provided that the transaction log file is still accessible.

    Backup Log <database_name> to Disk = <device_name> With NO_TRUNCATE

     

     

  • You still will need all other log backups prior to the current one as well as since the last full/diff backup.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply