September 28, 2004 at 6:04 am
I've been asked to look into resilence with regard to providing 24/7/365 database service for an entirely database driven web content management system.
Virtually all my experience is as a development DBA/data analyst so I'm in over my head here.
If you have a cluster will service continue if either one of the servers fail or is there a primary node that can act as a single point of failure?
When would I use Active/Active and Active/Passive?
For this particular application I am thinking along the lines of having a completely separate SQL Server (cluster) looking after content maintenance and then the final data being replicated across to a SQL server (cluster) looking after the actual surfing of the site.
I know that RAID 5 has some issues with write performance, plus I read somewhere that when the drives begin to degrade there is a risk of RAID 5 copying the bad blocks across the array.
What I was considering was having the content maintenance database server using RAID 1+0 but the live server using RAID 5 as the content server will have a lot of writing taking place as part of the content processing where as the front end server will only have the results of the processing written across.
What should I consider with regard to other points of failure?
September 28, 2004 at 7:21 am
please see the below link for response:
http://www.sqlservercentral.com/forums/post.aspx?forumid=54&messageid=139052
Good Hunting!
AJ Ahrens
webmaster@kritter.net
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply