21 October 2006 07:37
tonyrogerson
MCS Clustering, now in reach of the SME (< £17,000 )
Recently I was asked to cost up a new cluster and I was astonished at how cheap it is now - HP Cluster, 5GB per machine, 7 x 146GB disks for under £17,000.
The cost of creating and using a Microsoft Cluster has significantly dropped of late, in fact, in my honest opinion its now practical for Small – Medium size businesses or systems.
Take the HP ProLiant DL380 G4 Packaged Cluster with MSA500 G2 for instance, places like Inmac and PC World are kicking the base configuration (2 x DL380’s and the MSA500) for a mere £4,781, ok that is with 1GB of RAM and no disks and no software but that price is really good.
A 146GB 10Krpm Ultra320 SCSI disk knocks out at around £215 and memory – a 2GB kit you can get for £300 (£600 for 2 machines).
Windows 2003 Enterprise R2 x64 version knocks out at around £2,100 of which you’ll need two copies and SQL 2005 Standard x64 will set you will cost you £4000 per physical processor and if you a) only have 1 physical processor (remember, you don’t pay for cores) and b) only use the cluster in an active/passive scenario (SQL Server is only running on one of the machines at a time) then you only need pay £4000.
Two node clustering is included with the standard edition of SQL Server 2005!
So, an average system: 7 x 146GB disks, 4 in RAID 10 and 2 in RAID 1 and 1 hot spare, 5GB of RAM will cost you:
Package base £4,781
7 disks £1,505
4 2GB kits £1,200
Windows 2003 £2,000
SQL 2005 £4,000
Kit Total £13,486
Ok, there are still some bits on top of that that you need to consider – racking, cabling into existing infrastructure, keyboard, mouse and monitor if required; but a complete working cluster for under £15,000 is special!
If you wanted me to come build it for you, it usually takes me 2 days to install, configure and commission (test) and that will set you back another £1,700.
So, to conclude – clustering really is in the price range of everybody now.
The actual architecture I recommend to people is cluster your production server and have a hot standby if possible but definitely have a remote disaster recovery server, the hot standby would sit next to the cluster and would protect you in case the MSA500 itself fails, you use database mirroring (full safety) for that, the remote DR server you need to log ship to because its usually across a link that has lower latency (don’t mix bandwidth available with throughput) and because standard edition of SQL Server doesn’t do asynchronous mirroring then you need to use log shipping.
If I get time I’ll knock a diagram up, any questions?
Filed under: SQL Server