ACCIDENTALLY REWROTE THE PRODUCTION DATABASE

  • Time to think about it at least...

  • LOL!!


    * Noel

  • Thanks...

  • Sorry,

    I never meant to be rude just that the post above was funny. I have been in your position before and is not pleasant.

    Please, accept my apologies


    * Noel

  • Oh That's OK...I didn't even think it that way..

    But ya..This problem is solved now by bringing data from some other resources ...and the company thinks to bring in new stratagies for back ups.Specially regarding the transaction logs.

    Thanks for all help and keep posted about any new methods for disaster recovery.

  • So how much data was lost in the end?

  • Everything is back to normal now.That data is stored in some staging tables too.Package ran for 8 tables.Only 2 tables were not in staging ..So we had to work again on the same transactions for those 1 and half days.

     

    Thanks.

  • k, it's not the worst case scenario then... the good news is that you'll be able to restore the db next time a problem occurs. you tested the new backups you're taking right???

  • Ya...

    This is the plan the company wants to execute-

    1. A full database backup on Sunday night.

    2. A set of transaction log backups'll be  made every four hours during the day,

      

    3. Each night a differential backup will be taken

    working good so far.and tested well.

    Let me know about any other ideas.

  • How about differential every 4 hours and log back ups every 15 minutes?? Can't lose more than 15 minutes of data that way.

Viewing 10 posts - 16 through 24 (of 24 total)

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