I'm working on a Disaster recovery strategy for one of my clients. There are various recommended approaches like cold, warm and hot standby. I'm trying to setup a DR strategy that is similar to Hot Standby (http://technet.microsoft.com/en-us/library/ff628971(v=office.14).aspx#Section3) but it is slightly different based on the current environment of my client.
At present we have a SharePoint and database server. The SharePoint server has all the WFE and Application services running on it and DNS server is configured to the SharePoint IP address. Incase of disaster to SharePoint server (not the database server) the portal will not be available. To overcome this scenario and to bring the portal up and running in few minutes I want to have another SharePoint Server that is joined to this farm that has all the WFE, Application services, Central Administration Site and customisation on it. So when the main server is down I need to just change the IP address in DNS and the portal will be up and running once the DNS changes are propogated to computers.
Just for the sake of argument we can assume that the Database server will never crash.
Question 1: Is this a recommended approach and what are the issues with this approach?
Question 2: My client said he wanted to have a NLB and add both the servers to it so even if one fails the other will continue to work in Active-Active manner. What are the issues with this approach?