when could this restore scenario happen

From: chris (chris_at_noemail.com)
Date: 05/12/04 

Date: Tue, 11 May 2004 20:15:39 -0700

Backup scenario:

Monday full 9pm
Tues tlog 6pm
Wed full 9pm
Thur tlog 6pm
Fri full 9pm
Sat crash 5:30 pm

According to sources, if the active tlog is available after the crash, I
should be able to do a tlog backup, restore Fridays full and then restore
the new tlog backup using the stopat clause @ 5:29 pm. So my question is,
what kind of failure would enable me to still do a tlog backup after the
crash to avoid losing all that data? I did lots of disaster recovery testing
a few years back but really don't recall how this could happen.

TIA, Chris

Relevant Pages

  • Re: Problem restoring transaction log
    ... As there is no space to do a backup to, ... >You have to restore the database before you can restore ... >> No dump device was created when backing up Tlog. ... >> I have to specify a file as the TLog is not backed up ...
    (microsoft.public.sqlserver.server)
  • Re: IndexDefrag Production Impact
    ... I totally agree & in case this isn't clear for Jaxon - the .tlog grows ... the backup device / file might be substantially larger that it would have ... > Tibor Karaszi, SQL Server MVP ...
    (microsoft.public.sqlserver.server)
  • Re: LDF files keep growing back....
    ... you are invalidating your transaction log and the tlog will only be ... valid again after you do a full backup (any tlog backup you do between ... which would do what you're asking for (as well as periodically shrink ...
    (microsoft.public.sqlserver.server)
  • Re: how to roll forward(point in time)
    ... >alter database pit set recovery full ... >Jasper Smith (SQL Server MVP) ... >> Tues tlog 6pm ... >> after the crash, I should be able to do a tlog backup, ...
    (microsoft.public.sqlserver.server)
  • Re: Problem restoring transaction log
    ... You have to restore the database before you can restore the log. ... database backup and all log backups before that t-log backup using ... > No dump device was created when backing up Tlog. ... > The preceding restore operation did not specify WITH ...
    (microsoft.public.sqlserver.server)
Loading