And then suddenly, I noticed something incredibly fishy.  In addition to being a CLARiiON only solution, RecoverPoint/SE also only supports Windows. (My reference material was outdated… RPSE apparently supports most major OSes now, my apologies)

It make sense that SMB shops used to run only Windows and CLARiiONs, so the “Value Edition” of RecoverPoint supports that particular combination.  But SMB shops nowadays are venturing out to FOSS solutions such as LAMP based Alfresco to save some $. But if that translates to having to fork over a lot more money for the RecoverPoint “Deluxe Version”, it’d probably make SMBs look into some other storage vendors with more FOSS friendly price quotes. (However, RPSE does only limit you to CLARiiON-only storage, so for those wanting to save money by using less expensive boxes from a competing vendor, EMC will make you pony up for the full veresion of RP) After all, not everyone needs a Mercedes C class when a Toyota/Honda/Mazda works just fine   Remember, Linux is your friend.

• NuView StorageX (acquired by Brocade, OEM’ed to NetApp and IBM, EOL’ed this year)
• Acopia ARX (acquired by F5)
• Neopath File Director (Acquired by Cisco, EOL’ed soon after)
• Rainfinity(?) (Acquired by EMC, sales force seems to have stopped pushing it, hinting the pending FAST for Celerra release)

Out of the above 4 major players, 1 survived, (1.5 if counting Rainfinity)

What happened ?

NAS virtualization solves the scalability problem of NAS devices and provides an easy way to migrate files and/or volumes between dissimilar NAS devices. Most NAS devices back then were simple X86 file servers running code optimized for file serving. Although highly tuned, most of these NAS devices only scaled up to a active/passive fail-over cluster for HA, which improves the availability, but does nothing for scalability. The 32bit filesystems used in these NAS devices limited the volume size to ~ 16TB and can only hold less than a hundred K’s of inodes (file/directories). While the limitation is adequate for most organizations, it is a nightmare for those with large data sets (ie. HPC), or large number of small files (ie. Web based image serving sites). NAS virtualization broke the limitation by creating virtual volumes that span multiple NAS systems, effectively raising the capacity/inode ceiling.

The migration service lets customers move volumes around  NAS devices from same or different vendors. This alleviates the pain of running long robocopy or rsync sessions and reduces the cutover window.  Some of the migration services also comes with policy based file movements that moves  files around automatically  based on user defined terms (such as file age, size, last access time, file type) between faster ($$) tier and slower ($) tier.

(The net result is a relatively easy way to implement something like looks like distributed filesystem of the early late 90s … think IBM DCE/DFS, AFS and HPSS, minus the tape part and all the nerd quotient mandatory for implementation/support)

NAS virtualization hype seems to have completely deflated, considering that major NAS players are now selling devices with either built-in single name-space capability (NetApp), online migration mechanism (EMC, NetApp) and massive scalability (NetApp, Pillar). The only buyers of NAS virtualization would be organizations that have not standardize their NAS on a single platform and wants to move files around easily – A pretty small crowd.

However, NAS virtualization still has a chance, and this life line is Open Source – Cloud Storage.
Similar to the way SAN virtualization controllers (IBM SVC,  HDS USP-V) improves the performance of the physical arrays by adding more cache and spreading out volumes across more spindles, NAS virtaulization device can create high performance virtual NAS devices by distributing a virtual volume onto a number of inexpensive Open Source file servers. The NAS virtualization in this sense then provides replica service to allow users to access their files from any of the replicated filesets that is either less busy or closer to the user. Since the filesets are replicated can also exist in multiple sites, all the data is always available – instant BC/DR function.  Imagine – an easy and inexpensive way to build your own gfs (google, not RH’s). Slapping in a Amazon S3 or EMC Atmos interface, you now have both internal and public cloud all in a nifty device.

Maybe it’s time for a major linux vendor to venture into storage business ?