Post reply

Complete SQL Server Recovery from Scratch - repost

  • April 6, 2005 at 8:00 am

    #88041

    Hi Guys, this is a repost of a topic I submitted to the backups forum last Friday but haven't received much response

    Hi guys we are testing a total recovery of a Windows server from scratch using the following tools Cristie Bare Metal Recovery, Tivoli Storage Mgr, and Total Data Protection for SQL Server.  The CBMR tool restores the OS in conjunction with TSM, TSM restores the application files and data. Now we are at the point we need to restore our SQL server environment using TDP, but since we have no databases restored (including master and msdb), SQL server will not start therefore TDP will not work. 

    What I need to know guys is what is the best means of recovering an SQL server environment to the point that I can load SQL server and then perform the restore using the TDP tool.  Does SQL server need to be re-installed or can I do this another way. Thanks.

    Essentially what I need is to be able to recover the environment from scratch. Has anybody attempted a similar approach to recovery (maybe using other tools).  Any input would be appreciated

    Regards

    Terry

  • April 6, 2005 at 10:29 am

    #550838

    1.  I would want to know what are your sql sever version on the old box. 

    2.  Reinstall sql server to that version.

    3.  restore master.

    4.  restore the rest of the databases.

     

    So what's the big deal?  as long as you have backups that's all it counts.

     

    mom

  • April 6, 2005 at 10:46 am

    #550848

    Once again, I'm in the position of seconding someone else.  "What she said".  The rebuild master utility is an option, but you'll still need to restore master to get back to where you were.  When you're dealing with restoring the system databases, you really need to follow Microsoft's instruction (see the Rebuild master utility, rebuilding, repairing, and restoring topics under master database in Books Online).  Once that's done, and you restore your user databases, you're done (assuming your DR box is configured exactly like your production box).  No need for any 3rd party tools that may just make things more difficult instead of making it easier.  Also, depending on your system restoration tools, you may be able to simply re-attach your databases rather than restoring, once the system databases are happy again.

    Steve

  • April 6, 2005 at 4:53 pm

    #550998

    hoo-t, I am not dis-agreeing with you with regards to the procedures that have been presented.  The reason for TDP is to backup directly to tape while SQL server is live. Initially the project entailed using EM to backup all critical databases to disk. Now the disk has not been provisioned and since we are using a Tivoli based backup, we cannot allocate the SAN based tape drives to EM for backup (since this is in a datacenter environment where TSM has total control over the tape library).

    Since this application's database can grow to 2TB (it's a Cisco application) they recommended a complete backup of the DB on a daily basis (yeah ouch!!). I think it's BS personally, but unfortunately this project does not have a DBA provisioned to oversee recovery of the databases.

    So now we have to make due with the tools that are provided to us and that includes TDP, and that is why I asked if anyone had been in a similar situation with regards to restoring an SQL server environment in this manner.

    I will review the Books Online section on recovery so we can "fine tune" this environment. Thank you for your responses

    Regards

    Terry

     

     

     

     

  • April 7, 2005 at 9:17 am

    #551192

    I haven't found a SQL Server Backup Agent (or Oracle for that matter) that I would trust to backup my dog's poo-poo.

    And bare metal restores (especially in a DataCenter environment) are unrealistic. We had a VP that insisted that it was possible and we fought for 3-5 years before a manager changed position and the new one backed him down.

    The best recovery possibility is to have a hot site with your older equipment. And with 2TB I would say files and filegroups. Differential backups and dumps. Maybe even log shipping.

    But that is just my $0.02.



    ----------------
    Jim P.

    A little bit of this and a little byte of that can cause bloatware.

  • April 7, 2005 at 11:00 am

    #551237

    I ran into a problem with a different 3rd party SQL backup agent.  We had been using it to backup a "large" (at that time) database.  In a disaster recovery test, I got a phone call that they couldn't restore the database.  I ended up taking a native backup and sent it to them to be restored so that they could continue with the test.  Haven't used 3rd party backup agents since.  Be sure you test!

    Steve

  • April 7, 2005 at 11:08 am

    #551238

    Full Backup of 2TB every day with 3rd party tools and to TAPE !!!

    exec sp_update_resume


    * Noel

  • April 7, 2005 at 11:58 am

    #551253

    Thanks for the replies guys especially Noel (for the laugh) .  I needed some real world examples of what other guys have done in the field in order to say that this won't work as planned.

    I guess in this case it is best effort in terms of recovery based on the proposed solution.  Thanks again

    Regards

    Terry

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

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