Disaster Recovery - testing and documenting

  • I need to test and document disaster recovery

    1. To make sure I know how to do it, should the worst happen

    2. Leave instructions in case I am not around

    Currently all system databases and Production database are backed up nightly. Production transaction logs are also backed up hourly.

    All backups are to a network share.

    The network share is mirrored via Solaro offsite. The network share is also backed up offsite using TSM every night and stored for 60 days.

    We also have a hot swop image of the Server hard drive stored in a fireproof site which is updated every time a significant change to Raid 1

    I have a test server to practise on. In the event of a disaster our techies would build a new server with Windows 2000 Server and also make available on a network share the latest backup sets.

    Would appreciate advice on steps involved and any advice in documenting this e.g. at high level

    1. Install SQL Server Standard

    - screen by screen instructions

    e.g. change default data directory

    Change account type

    Mixed mode

    2. Update to compatible Service Pack (3a)

    3. Restore databases

    - In which order or doesn't this matter?

    - Can I do this using Enterprise Manager from a network share or does this have to be done in code?

    - Do I have to create empty databases and restore over the top of them.?

    4. Check Server, agent etc running

  • there is a very good artical about the disaster recovery.

    i wish it helps.

    ~~~~~~~~~~~~~~~~~

    InstantDoc #39657

    Recovering from Isolated Corruption

    What's the fastest way to get your system running again?

    http://www.sqlmag.com/Articles/Index.cfm?ArticleID=39657&

  • Thanks for the link - unfortunately I can not read the article unless I subscribe. Also I want to document and test a total disaster this article seems to be about a partial restore.

    quote:


    But in this article, I talk about recovering from isolated disasters—specifically, failures that affect only part of your database.


  • may be u can simplify your plan by ommiting installation instructions, by creating setup settings files ( *.iss ) refer to BOL or setup disks for this.


    -- Amit



    "There is no 'patch' for stupidity."



    Download the Updated SQL Server 2005 Books Online.

  • quote:


    unfortunately I can not read the article unless I subscribe


    Hi, StefanJ,

    I could summit a request to http://www.sqlmag.com e-mail you this artical if you want. the following statement is from that side.

    -----------------------------

    EMAIL THIS ARTICLE

    Recovering from Isolated Corruption

    Spread the word! Complete this form and we will send an email letting your friends and colleagues know about this article. Email addresses are used only for this notification service and are not stored or used for any other purpose.

    NOTE: Only subscribers have access to this article, however, you may still send this referral to anyone, including non-subscribers. In the email, we will send the recipient a description of the article and will indicate that the article is subscriber-only.

    ------------------------------------------

  • xyz, I think emailing them will only let me see the summary as I can already do.

    amitjethva, I really need to understand and document the steps before I try and script it.

    I am making some progress but more by trial and error. I have got as far as restoring master databases and found this very difficult until I found this link

    http://techrepublic.com.com/5100-6268-5025441.html

    Would be good to find a step by step idiots guide like this which covered all the steps.

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

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