September 12, 2006 at 12:40 pm
Hi,
I have a web app running ASP.NET (2003, IIS6, SQL 2000 cluster). I need to build a disaster recovery site for this. What is best way to achieve high availability for the SQL Server (replication, mirror, log shipping)? Should I upgrade to SQL 2005? Thanks
September 12, 2006 at 1:33 pm
DR is based on your requirements and the expectation by the end users on How much data loss can your users tolerate and how long can the wait.
To begin with have a good backup plan and test if you are able to restore point in time. Just by upgrading to SQL 2005 is not going to do the magic.
Thanks
Sreejith
September 12, 2006 at 1:39 pm
Unfortunately the answer to your question is... It depends.
What is your ability for downtime (can you be down 1 minute, 2 or 15, up to an hour)? Are you talking about co location or slow network links that could cause you problems? What's you budget to accomplish this? How busy/big is your cluster? can one larger server handle all of the requests if you need to fail over for a short time or do you need to have the same exact thing in the DR site?
I'd suggest you read what MS has to say on the Subject.
http://www.microsoft.com/technet/prodtechnol/sql/2000/deploy/sqlhalp.mspx
Then once you have a good idea of the limitations and benefits of each, sit down with your team and ask the hard questions. Figure out which one has the most benefits to your org and which you couldn't possibly use and choose which fits best. Also keep in mind what regulations like SOX, hippa, etc have on your DR needs. It might not be a bad idea to talk to your legal dept and get thier buy-in on whatever solution you choose.
There are just too many options and variables for there to be 1 silver bullet of "this is the one to use".
-Luke.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply