Hey Everyone

Very broad request here. I have a future client that has asked the following:

With the advent of Microsoft SQL 2005 and 2008 there now exists a replication feature 
that we would like to implement. We would like to replicate to a “warm” server and be
virtually up-to-date should we encounter a problem with the production server. A procedure will
be necessary to switch the enterprise between the “production” and “warm” servers. We would
continue to backup the system to magnetic tape. We would like your company to design and price
this operational model.  In addition, your company will be required to create a disaster recovery
plan.

1. Does anyone have a sample disaster recovery document in word that they would be willing to share, specifically in regards to SQL server?

2. Has anyone been using a "warm" server. Any information on the setup of one and how the setup between the live and warm server stay in sync would be greatly appreciated. I used to think the "warm" server was just a physical copy of the original server, but not actually turned on but the software loaded and everything ready for when the production server died, then you fired up the "warm" server, uploaded the last backup of the production server, and set the IP to be the old server production address and then let it roll. I'm not sure if that was the right then or now. If it's replicating to the warm server then the warm is on, and receiving data all the time.

Thanks for any help

Kirk