1. Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING) Click the link to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This message will disappear after you have made at least 12 posts. Thank you for your cooperation.

Emergency SQL Restore Question

Discussion in 'Microsoft SQL Server' started by GregE, May 18, 2012.

  1. GregE

    GregE Senior Member

    Joined:
    May 12, 2006
    Messages:
    2,100
    Likes Received:
    31
    I backup a database FULL weekly.............DIFF daily...........LOG hourly.

    I am restoring this database up to this morning May 18, at 06:00.

    If I use "tdpsqlc restore FULL....." with the /RESTOREDate and /RESTORETime parameters, will this bring everything up to the time/date I specify, OR is that ONLY going to look at the most recent FULL, which is 5/14, in which case I then need to do DIFF and LOG restores to bring it forward and use those same date/time parameters in each of those commands?
     
    Last edited: May 18, 2012
  2.  
  3. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,189
    Likes Received:
    277
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    The restore should bring everything back to the time and date specifed including the log files.
     
  4. GregE

    GregE Senior Member

    Joined:
    May 12, 2006
    Messages:
    2,100
    Likes Received:
    31
    Thank you. The documentation wasn't quite clear to me on that.
     
  5. GregE

    GregE Senior Member

    Joined:
    May 12, 2006
    Messages:
    2,100
    Likes Received:
    31
    Curious..........we restored to 6:00am because they saw corruption around 7:30am.

    Let's say corruption actually occurred before that and the 6:00am log backup also contained corrupt data. Would I have to restore the entire DB again or could we restore only the previous log? I think the whole thing, but correct me if there is another way.
     
  6. moon-buddy

    moon-buddy Moderator

    Joined:
    Aug 24, 2005
    Messages:
    6,189
    Likes Received:
    277
    Occupation:
    Electronics Engineer, Security Professional
    Location:
    Somewhere in the US
    Depends. If the corruption hit the 0600H log, then you have to restore before that. If there is no LOG to restore, then TSM will restore the last FULL backup.
     
  7. GregE

    GregE Senior Member

    Joined:
    May 12, 2006
    Messages:
    2,100
    Likes Received:
    31
    So they're not happy with what has been restored and they want an earlier restore.

    There are logs before that 0600H log. So I can restore ONLY a 0500H log file to this currently restored database and the DBA can just send us back an hour with that alone? If so, that's a HUGE time saver.
     
    Last edited: May 18, 2012
  8. GregE

    GregE Senior Member

    Joined:
    May 12, 2006
    Messages:
    2,100
    Likes Received:
    31
    Ok, yesterday during the day I restored a complete SQL db back to 10PM Thursday. It ran well, around 45MB/sec

    Last night we had to do that again, but restoring it to a different server. Same data, on same tapes (no reclamation or tape moves occurred on the storage pool). Ran it during the night when TSM was under load (during some short stretches, there was little load), and it ran at 150Kb/sec (not a typo), and I had to eventually kill it. We may not need it anyway at this point, and I'm going to try an identical restore during the day today to see if it goes back to a normal speed.

    What in the heck would bring it to it's knees if it is the same data as it was when it ran normal? If it was TSM server load at night causing it, I would have expected a massive speedup during the times where TSM had a break in it's backup activities, but that did not happen.
     

Share This Page