Choosing An All-Flash Array
Today's storage market is crowded with AFAs. Here are some shopping guidelines.
August 9, 2016
![Network Computing logo Network Computing logo](https://eu-images.contentstack.com/v3/assets/bltde8121fc52c5c8f3/blt3f3d0318f746b1c2/65a530e4187606040a1d8b8c/placeholder.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
With vendors constantly touting new features in a hotly contested market segment, choosing an all-flash array (AFA) can be a daunting challenge. While the segment is growing rapidly and AFAs are well accepted in the enterprise, there are those who keep resetting their buying decision as these new features appear. Since all-flash arrays will continue to evolve, it's better not to wait on the sidelines since the benefits AFAs provide an IT operation today are phenomenal.
AFAs sit on a SAN as an accelerator for IO. There are two ways to use them. They can be used as a cache layer buffering the hard-disk drive RAID arrays or they can serve as a new primary tier of network storage. Caching and tiering tend to blur into each other, as additional services such as compression and encryption have become common to both. In the early days of the all-flash array market, the battleground was over speed and capacity. More recently, the maturation of the AFA segment has brought vendors closer together on these metrics, though another burst of competition is due soon based on advances in 3D NAND.
So, what to look for in an AFA? Given that the purpose of an AFA is speed, look at IOPS. The current benchmark is two to four million IOPS, but that presupposes that you’ve built a fast enough network to connect to all the ports and spread the data out to servers using it.
This brings up the whole connection issue, because AFAs have grown out of their original Fibre Channel-SAN environment and now come in iSCSI or NAS configurations too. In fact, the fastest AFAs generally are based on Ethernet, using multiple 40 GbE links, and we’ll soon see Ethernet extending its lead to include RDMA and NVMe over Ethernet support and 100 GbE. An alternative is to use InfiniBand, which is more expensive and harder to manage, but which claims an edge in latency.
storage concept.jpg
Once feeds and speeds are understood, and adequate networks planned, the issue is raw capacity and price per terabyte. Raw capacity measures the space you are buying, but the actual storage capacity depends on whether the array supports compression, since this can grow capacity from 5x to much more, depending on your data types.
Compression involves loading data into a journal file in a mirrored area of the flash and then compression takes place as an asynchronous background job. The result is that both the flash space on the AFA then the data stored on secondary storage are expanded above raw capacity. The compressed data also speeds up transmission between the layers.
Here are some other considerations and questions to ask when shopping for an AFA:
There is a good chance your storage network will migrate to Ethernet, due to hybrid clouds, so an AFA should be able to handle high-bandwidth Ethernet links, even if you're plugging the AFA into a Fibre-Channel SAN today.
A good choice has Fibre Channel or Ethernet for a backend link to secondary storage, and if you plan to migrate from FC to Ethernet, having both is essential.
You have a choice between traditional Fibre-Channel AFAs, where EMC’s XtremeIO and Pure Storage are duking it out for leadership in a large pack of players, or iSCSI products from Pure, Nimble Storage, and Violin Memory. While most AFAs address block IO, some like ones from NetApp and Violin also support NAS, though with somewhat different approaches. NetApp has a filer with SSDs and Violin added Windows Storage Server to its AFA. Of course, there are others to look at, and some are very competitive with those named above.
If you are a VMware shop, extensions to interoperate with VMware are very useful.
Rank the products on the maximum IOPS they can deliver to your planned network. Then build a ranking on cost per IOPS and cost per raw terabyte of capacity. (I would not look much at arrays lacking compression!)
Next, look at the cost of expansion. I’m a firm believer in not buying more than is necessary. If you have two arrays at the same price per terabyte and one holds the 64 TB you need, while the other can hold 256 TB. I’d buy the latter with just 64 TB populated. This is important, because appliance sizes and maximum capacities are all over the place.
Once you’ve gotten down to two or three products on your shortlist, check references and the media coverage. Shifting of executives, financial issues, and mergers impact companies, which could reduce the level of support you get.
The most important thing is to make a decision! Don’t wait for yet another generation and miss all the benefits.
About the Author
You May Also Like
Maximizing cloud potential: Building and operating an effective Cloud Center of Excellence (CCoE)
September 10, 2024Radical Automation of ITSM
September 19, 2024Unleash the power of the browser to secure any device in minutes
September 24, 2024