Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

News

9/29/2008
09:20 AM
George Crump
George Crump
Commentary
50%
50%

The Death Of The Dual Controller Architecture?

Clustered storage is everywhere; are we seeing the end of the dual controller architecture?

Clustered storage is everywhere; are we seeing the end of the dual controller architecture?The traditional dual controller storage architecture has been with us for a long time, but with IBM's acquisition of XIV we are now seeing clustered architectures in every part of the storage marketplace. Almost every new storage supplier in recent years has started with a clustered storage platform. Add to this that almost every traditional storage provider has delivered a clustered solution in that same time frame.

Why is everyone jumping on the clustered storage bandwagon? In my opinion, it is granularity that provides a "pay as you go" scaling of performance and capacity. With a dual controller architecture, the storage manufacturer needs to build enough processing power in the controllers to power the performance and capacity expectations of a fully loaded system. With a cluster storage system, not only can you add either I/O performance or capacity independently from each other, but you can do so as you need it. Also unlike many dual controller systems that essentially hit a wall on performance, forcing an upgrade to the next controller platform, clustered storage is basically self-upgrading. By adding new nodes to the cluster you are essentially adding more performance or capacity and extending its reach. The clustered architecture should be able to handle mixed nodes and as a result will self-upgrade to newer, more power-efficient components, over time.

Most cluster storage solutions today are NAS based, focusing on file services. They make ideal targets for cloud computing and archiving. Clustered storage is moving into prime time and companies such as Isilon and OnStor make a clustered storage solution for primary NAS storage. So how does this threaten the dual controller architecture? The next frontier is in block storage, companies like 3PAR and IBM's XIV are offering block-based clustered storage, bringing this self-upgrading granular application of performance and capacity to databases and other block-based needs.

There won't be a dual controller vs. clustered architecture battle like there was with SAN vs. NAS or iSCSI vs. Fibre Channel. There is little anti-cluster sentiment out there. It seems to be more a matter of when, not if. Dual controller still has a place today. It has the appearance of being simpler on installation (no cluster to get working, which can sometimes be an issue) and if you know that your performance and capacity limits are going to be well-handled by a dual controller system, it may also be less expensive.

As always, determine what is important to you and make your choice from there.

For more on cloud storage, sign up for today's Webcast at 12 p.m. CST: Cloud Storage 101.

Track us on Twitter: http://twitter.com/storageswiss.

Subscribe to our RSS feed.

George Crump is founder of Storage Switzerland, an analyst firm focused on the virtualization and storage marketplaces. It provides strategic consulting and analysis to storage users, suppliers, and integrators. An industry veteran of more than 25 years, Crump has held engineering and sales positions at various IT industry manufacturers and integrators. Prior to Storage Switzerland, he was CTO at one of the nation's largest integrators.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
Black Hat Q&A: Hacking a '90s Sports Car
Black Hat Staff, ,  11/7/2019
The Cold Truth about Cyber Insurance
Chris Kennedy, CISO & VP Customer Success, AttackIQ,  11/7/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-16863
PUBLISHED: 2019-11-14
STMicroelectronics ST33TPHF2ESPI TPM devices before 2019-09-12 allow attackers to extract the ECDSA private key via a side-channel timing attack because ECDSA scalar multiplication is mishandled, aka TPM-FAIL.
CVE-2019-18949
PUBLISHED: 2019-11-14
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.
CVE-2011-1930
PUBLISHED: 2019-11-14
In klibc 1.5.20 and 1.5.21, the DHCP options written by ipconfig to /tmp/net-$DEVICE.conf are not properly escaped. This may allow a remote attacker to send a specially crafted DHCP reply which could execute arbitrary code with the privileges of any process which sources DHCP options.
CVE-2011-1145
PUBLISHED: 2019-11-14
The SQLDriverConnect() function in unixODBC before 2.2.14p2 have a possible buffer overflow condition when specifying a large value for SAVEFILE parameter in the connection string.
CVE-2011-1488
PUBLISHED: 2019-11-14
A memory leak in rsyslog before 5.7.6 was found in the way deamon processed log messages are logged when $RepeatedMsgReduction was enabled. A local attacker could use this flaw to cause a denial of the rsyslogd daemon service by crashing the service via a sequence of repeated log messages sent withi...