Tag Archives: EMC

unity

Unity – EMC’s new unified storage array

Unity,

As you may know, EMC released their new unified storage array for block and file called Unity.  I wanted to go over it a bit to help people understand where this array fits within the storage landscape to see if it might be a good fit for them.

What exactly is Unity?

Unity is a block and file unified array.  It’s very similar to both the VNXe and VNX models of the past.  Like most of those, Unity supports both Fiber Channel and iSCSI protocols for block storage.  It also supports CIFS and NFS for File protocols as well.

It is a dual storage processor ALUA array for redundancy, with dual processors, redundant components across the board.

For IO ports, it includes 2x 1GbE ports and 2 Converged Network Adapters (CNAs) per storage processor.  The CNA’s at the factory can be configured to act as 10GbE adapters for iSCSI or NFS, or as up to 16Gb fibre channel interfaces.  Note those modes cannot be switched after the device is shipped.  You can also add up to two IO modules per storage processor in identical pairs to provide additional IO ports, including 1GbE, 10GbE, or FC.  All unity arrays also have 2 SAS ports to connect to additional racks of disks called DAEs (just like the VNX).  The 500 and 600 arrays can have additional SAS ports installed as an IO module to approach their maximum supported disk configurations as well.

The Unity arrays effectively replace all the VNXe storage arrays going forward.  In addition, they replace most VNX storage arrays.  The only exception are the VNX 7600 and 8000 arrays, which will continue due to their higher scalability relative to the Unity models.

Unity has all the other features you come to expect from EMC, including secure remote support and monitoring in ESRS, FAST Cache using SSDs as a third layer of cache for storage acceleration, FAST VP auto storage tiering, and more.

Also, the Unity arrays have all flash models for each of the models as well for the performance conscious.

Improvements Over the VNX/VNXe

There are quite a few improvements I wanted to point out over the VNX and/or VNXe.

  • HTML5 based Unisphere – YES!  TAKE THAT JAVA!
  • Simplified and easier to use interface
  • Significantly smaller rack footprint when offering  both block and file
    • Within the VNX line, you had to have Storage Processors, X-blade data movers, and Control Stations typically to offer both protocols.  taking up way more rack space and power.  Now, just the DPE provides the same functionality!
  • Support for both block and file VMware vVols
  • Easy setup of ESRS within the array, similar to the VNXe did, but not the VNX
  • All arrays come with IO ports that could potentially bring both iSCSI and FC support without requiring any additional IO cards
  • Far faster setup
  • Better remote monitoring and data analytics of the storage array
  • Ability to run Unity as a virtual storage appliance for dev/test, potentially even for free!

That’s quite a jump from the VNX/VNXe, even though the concepts of the two arrays are the same.

Where can I learn more?

There actually is an abundance of learning resources about the Unity arrays already available.  I would suggest checking out the following: