Six reasons why SMBs need iSCSI storage area networks (SANs)

Jacob Gsoedl, Storage contributor
Cheaper and easier to use than Fibre Channel, iSCSI is considered by many to be the next great storage technology for small to medium-sized businesses. Here are six popular reasons why.
  1. Why should SMBs look at iSCSI vs. Fibre Channel (FC) SANs?
    • iSCSI SANs are less expensive than FC SANs.
    • An iSCSI SAN is based on the familiar and ubiquitous TCP/IP protocol.
    • iSCSI SANs are less complex and easier to manage than FC SANs.

  2. How can iSCSI save you and your customers' money?

    iSCSI uses TCP/IP instead of a proprietary storage protocol such as FC. As a result, iSCSI SANs can be built with commodity network components, eliminating the need for costly FC host bus adapters (HBAs), which are typically priced between $800 and $1,200, and FC switches.

  3. How is iSCSI being used in SMBs vs. large enterprises?

    While SMBs use iSCSI SANs as their primary storage, large enterprises use iSCSI to complement their FC storage for less mission-critical departmental apps, remote offices and data protection. Typical applications for iSCSI are messaging apps like Microsoft Exchange, databases, Web apps, file serving and disk-to-disk backup.

  4. What iSCSI weaknesses should you consider when developing iSCSI services offerings?

    Storage management is one of the weaker aspects of iSCSI. Storage management vendors are just starting to add iSCSI support to their suites. While FC switches are well supported by all

    Requires Free Membership to View

  1. major storage management apps, only some aspects of Ethernet switches, like availability, are addressed by storage management suites.

    Security is another controversial aspect: Although FC proponents are quick to point out security concerns with iSCSI, in reality, iSCSI is an inherently more secure protocol than Fibre Channel.

    With the reliability and feature gap closed, the slower performance of iSCSI is now the primary technical argument FC advocates use for not considering iSCSI for enterprise-level applications. But iSCSI speeds are beginning to catch up with FC, and the two protocols are on a leap-frog path with each one boasting new product releases that bests the other, but not for very long. However, the FC protocol has a slightly lower latency than TCP/IP.

  2. Why iSCSI, why now?

    One could argue that the popularity of NAS was the main reason for the ever-increasing interest in iSCSI. NAS dependency on higher level file-system protocols (CIFS/NFS) makes NAS less suitable for block-based transactional applications like databases; as a result, NAS vendors are adding iSCSI support to their offerings. Because NAS and iSCSI are both based on TCP/IP, iSCSI is a more natural SAN supplement than FC in NAS environments.

    Furthermore, the number of innovations and companies developing for the TCP/IP and iSCSI space today greatly surpasses the number of FC developments. Besides 10GigE, network packet processors--from companies like Broadcom Corp. and Cavium Networks--for packet inspection, prioritization, encryption, compression and TCP optimization are the building blocks for next-generation TCP/IP and iSCSI products.

  3. Will iSCSI push FC out of the data center?

    There's no doubt iSCSI will dominate the SMB storage space and will be the preferred storage option for workgroup servers and, eventually, corporate desktops. What's still unclear is if iSCSI can push FC out of the enterprise data center. With FC's large installed base, long-standing support for mission-critical apps and the availability of 8Gb/sec FC, it's the preferred technology for most large data center storage. For a transition to happen, it will take large storage vendors like EMC, HP and IBM to recommend iSCSI over FC, which is unlikely to happen in the near future.

Find the rest of Gsoedl's article on Developing iSCSI SAN solutions for SMBs on SearchStorageChannel.com.

This was first published in January 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.