Emergency servicesFlorida blood service upgrades storage systems

Published 1 February 2012

Florida Blood Services has replaced three disparate storage systems with the Nimble CS240 converged storage array; FBS says the new storage operation allows FBS more efficient and centralized storage for FBS’s headquarters and forty field offices

Irvine, California-based Nimble Storage, a storage solutions specialist, announced that Florida Blood Services (FBS), a nonprofit provider of blood for critical care, has replaced three disparate storage systems with the Nimble CS240 converged storage array. FBS says the new storage operation allows FBS more efficient and centralized storage for FBS’s headquarters and forty field offices – in addition to reducing system backups from days to seconds. By replacing lengthy system backups with frequent incremental snapshots, the service has improved its Recovery Time Objectives (RTOs), an important concern for emergency services in a regulated environment.

The company notes that two Nimble arrays at the company’s St. Petersburg headquarters host primary storage, house 160 virtual machines, and provide a direct connection to forty offices in Florida and Georgia. Two additional Nimble arrays, targeted for disaster recovery, are situated in FBS’s nearby Lakeland, Florida, office. FBS’s new storage architecture represents a “three-to-one consolidation that has worked magnificently for us,” said Calvin Levy, senior systems engineer.

With FBS’s previous system, performance degradation was a major challenge. Of the approximately 150 virtual machines (VMs) under deployment, the storage team could back up only thirteen VMs per night without affecting performance for the majority of its users. Backups would require more than forty hours, starting at 7:00 p.m. Friday and ending at approximately 3:00 p.m. on Sunday.

“With Nimble, we’re able to back up all of our volumes in a matter of seconds and make intermediate, scheduled snapshots that take no toll on performance,” said Levy.

Storage snapshots, important in maintaining an organization’s RTOs, had long been an issue for FBS, a 24×7 operation requiring data access in real-time. With FBS’s previous storage architecture, once a snapshot was placed on a storage server, users would experience noticeable performance degradation. Following a required firmware update, the situation became critical, said Levy. “Regardless of whether we tried to take 20 snapshots or 200, our performance was significantly hampered. Our fall-back position, and not a great alternative, was to rely exclusively on full backups.”

Today, Levy and his team use Nimble’s integral snapshots. “Across all of our volumes, we have thousands and thousands of snapshots on the system, and we’ve seen no degradation in performance. We’ve been so happy with the Nimble snapshotting system that we are pushing for a system-wide 15-minute backup frequency.”

According to Dan Higley, a senior systems engineer for FBS, the architecture and sequential file system of Nimble storage arrays distinguish Nimble from other storage models. “Nimble has taken flash into account and created a cost-effective device that stages data properly, both in flash and disk-based storage, to provide the highest performance at the lowest cost.”

He added that the system-wide redundancy of the Nimble array provides an additional measure of assurance. Noting the 24×7 nature of FBS, he said that his team had replaced a controller and tested a new controller without having to power down the array. “Staying 100 percent operational is critically important in our environment.”