Making the Switch to iSCSI Storage

Click here to receive your FREE subscription to Campus Technology

Home > Making the Switch to iSCSI Storage

Focus

Making the Switch to iSCSI Storage

1/31/2008

By Dian Schaffhauser

Client by client, iSCSI is claiming ground against fibre channel in the external storage wars. For Queensborough Community College in Bayside, NY, that day of reckoning came a week or so before Thanksgiving 2006 when the school's fibre channel storage system went down.

But that wasn't the first warning the Office of Information Technology had about the need for a possible switch in platform. According to information systems specialist Bryan Farr, that signal had occurred a few months earlier during a meeting with the school's previous vendor, where the school learned the fibre channel storage area network (SAN) they'd installed just a year and a half earlier was coming off end of life in the not-too-distant future.

The Queensborough campus, part of The City University of New York (CUNY), serves 12,000 students a semester from atop a former golf course, with about 15 buildings over 35 acres. A gigabit Ethernet network with Cisco switches powers between 140 and 150 servers, most from Dell. More recently, the school has begun buying IBM BladeCenter servers running VMware Infrastructure 3 to migrate legacy applications off of computers nearing their end of life. Rather than purchasing new individual servers for each application, QCC is pooling them on VMware.

While the main student information is housed at a CUNY central office, the community college maintains e-mail for staff, faculty and students, as well as application databases for various departments, a total of about 2 or 3 terabytes worth. Farr said e-mail consumes the biggest share of the data store.

And that was the clue to Farr and his colleagues that something had gone wrong. Suddenly, people were calling because they couldn't access their e-mail. "It disturbed a lot of things," he said. "We had to call departments and tell them what happened, explain to people, 'Yeah, it's down. We're working on it.'"

All they could tell was that the main controller for the SAN had an issue. Along the way the problem--whatever it was--poisoned the failover controller. They were, as Farr described it, "dead in the water."

It would take three days of being on the phone constantly to vendor support to work through the technical problems. The computer company sent a support person, but, like the internal staff, he had to sit and await instructions. "One of their tech support [people] was saying it was hardware," recalled Farr. "So they sent new hard drives. We popped those in. Didn't bring it up." Next, software and drivers were checked. Eventually, with a lot of recoding, the SAN was resurrected.

But the team knew it had to change out the campus' storage switches. That posed a follow-on problem. Not only would the school have to swallow the expense of replacing two switches, but if it stayed with fibre channel it would have additional costs related to moving from its existing 1 gigabit fibre channel infrastructure to the newer 2 gigabit. Also, nobody on staff was fully trained on fibre channel. "We knew how to get through some of the volume parts," said Farr. "But setting up targets and fibre channel worldwide addressing--we knew nothing on that level, which you'd need a technician or somebody fully certified to install."