Post reply

recovery problem....

  • July 30, 2009 at 11:28 am

    #136833

    Hi All,

    I have backup files as below and I need to recover...

    Sunday : FULL BACKUP 1:00 AM -- Good condition

    Monday : Differential Backup 2:00 AM -- Good condition

    Tuesday : Differential Backup 2:00 AM -- Good condition

    Wednesday : Differential Backup 2:00 AM -- Corrupted

    On Wednesday Morning my DB got corrupted, Now I should start the DB restore process

    I will do as below

    1. Restore FULL Backup (Sunday : FULL BACKUP 1:00 AM ) with norecovery

    2. Restore Differential Backup (Tuesday : Differential Backup 2:00 AM) with recovery

    Here I assume that I can't restore upto the time of disaster, If so How do I restore and what are the options we have.

    Case 1: Assume that My db is in FULL recovery model and it is allowing me to take the Tail of Log backup will I be able to recover?

    What are all other options I have to recover...

    Rajesh Kasturi

  • July 30, 2009 at 12:28 pm

    #1032601

    What transaction log backups do you have?

    Since the DB is in full recovery, you must have some or that log would have long since grown out of control.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 1, 2009 at 9:31 am

    #1033354

    there is no T-Log backup

    Rajesh Kasturi

  • August 1, 2009 at 9:33 am

    #1033355

    You're in full recovery model and you have no transaction log backups? How on earth does that work without your log completely growing out of control?

    Are you truncating the transaction log before or after a backup (and if so, which)? Are you switching to simple recovery and back to full at all, and if so, when?

    If you were in full recovery, not backup the log up, not truncating the log and not ever switching to simple, your log would very quickly fill the hard drive. Since I gather that has not happened, you must be doing something with the log.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

  • August 3, 2009 at 5:55 am

    #1033598

    Dont mind my asking but is this a interview question ?

    "Keep Trying"

  • August 7, 2009 at 12:29 am

    #1035800

    No, This is not interview question...

    I am just searching find alternate ways to recover for different scenario.

    There might be solution

    Rajesh Kasturi

  • August 7, 2009 at 2:55 am

    #1035840

    Rajesh kasturi (8/7/2009)

    I am just searching find alternate ways to recover for different scenario.

    There might be solution

    Answer my questions about what you're doing with the transaction log and I'll tell you how to recover and what you're able to recover.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

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

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