Rainfinity has added automation capabilities to its RainStorage NAS management appliance, allowing it to plug into storage resource management (SRM) tools.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
Called GridSwitch, the addition means that an SRM tool can use RainStorage to move data volumes from one NAS server to another, as the first one fills up or slows down because of overloading, without the users being made aware.
Once a volume has been moved, it remains available (and synchronised) in both old and new locations until all the relevant clients have updated their mappings to the new location. GridSwitch tracks the remapping process and automatically drops the original copy once it is complete.
The technology in effect virtualises NAS servers, allowing them to be part of an information lifecycle management (ILM) strategy, according to Dr Chenggong Charles Fan, Rainfinity's cofounder and CTO.
"I think there's a huge market opportunity on file-level storage. People liked NAS because of its simplicity, but then storage started to grow and filers became islands. There has been a demand for virtualisation of the NAS filer for a while," he says.
"GridSwitch is automatic data movement for capacity provisioning and storage management. RainStorage is user-initiated, GridSwitch automates the process and allows it to integrate with SRM."
Fan said that Rainfinity already works with several other companies to move NAS data as part of an ILM strategy, including Network Appliance and CreekPath Systems. "I think the reason ILM is not happening is the lack of tools to do transparent data management," he added. "They can tell you what to move but there's no mechanism to actually do it."
Yankee Group analyst Jamie Gruener agreed. "Data movement without network disruption is a key building block for ILM. It's really about data access - data cannot be moved unless it's accessible 24 by 7, and management cannot be considered automated if the first step is to negotiate user and application downtime."
Bryan Betts writes for Techworld.com