Post reply

Restoration Issue

  • November 6, 2007 at 3:52 pm

    #183615

    Hi all,

    Please find the following details and give me appropriate solution.

    Full backup: everyday :00:30 hrs

    Differential backup: everyday 20:00 hrs

    Transction log backup: every 30 mins

    Database size is 150+ GB

    Lastday one of our disk got crashed which had contains data and log file of the database at 22:25. Now my client wants all of the data till 22:25.

    I can recover data till 22:00 but how could I recover last 25 minutes data.

    Please help ASAP

  • November 6, 2007 at 4:20 pm

    #748912

    Using the strategy that you've posted, you can only recover up to every half hour. This means that if your database crashes at :29 past the hour (or :25 in your case) that you lose the data modifications since the last update. If the crash would have happened at :31 past the hour, you could recover up to :30. You would still lose 1 minute of data.

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • November 6, 2007 at 4:35 pm

    #748917

    Thanks John,

    So according to you I'll not able to recover last 25 min data

    Regards,

    Austin

  • November 6, 2007 at 7:56 pm

    #748929

    Are you able to get to the log file for the database ?

    If you can, you can backup the log and get the last 25 minutes of transactions with a command similar to

    BACKUP LOG MyDatabaseName TO DISK = ‘C:\MyDatabaseName_LogTail.trn’ WITH NORECOVERY, NO_TRUNCATE

    Have a look at topic "Tail-Log Backups" in SQL 2005 Books Online

  • November 7, 2007 at 7:42 am

    #749103

    Austin_123 (11/6/2007)

    Thanks John,

    So according to you I'll not able to recover last 25 min data

    Regards,

    Austin

    Not unless you can to what Happycat59 is suggesting, but from the sounds of your initial post, your database is lost/corrupt.

    John Rowan

    ======================================================
    ======================================================
    Forum Etiquette: How to post data/code on a forum to get the best help[/url] - by Jeff Moden

  • November 7, 2007 at 6:18 pm

    #749293

    It's not really any more log space to run backups every 5 minutes. You might want to change that.

  • November 11, 2007 at 9:58 pm

    #750134

    dear Ausstin,

    tail log back up is option to solve your problem...

    take the tail Log Back up using the syantax

    use master

    go

    sp_adddumpdevice 'disk',' '

    backup log

    to

    with norecovery

    this statement take the backup of your log till last differential backup to the time went your database become suspect...

    than retore your database using full->diffrential->Tail log backup...

    you got your problem solved.......

    regards

    Varun Jha

  • November 12, 2007 at 7:15 am

    #750238

    You may want to also consider adding either database mirroring or log shipping to your backup strategy to prevent a similar issue in future.

    Thanks,

    Phillip Cox

Viewing 8 posts - 1 through 7 (of 7 total)

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