InfoStor Article Categories:
![]() |
![]() |
|
|
|
|
![]() |
|
InfoStor Online Article
|
|||||||||||||||||||||||||||||||
Block virtualization case study #3: EMC Invista Storage virtualization helps Purdue University manage storage complexity, facilitate change, and reduced costs. By Dave Vellante and David Floyer Background IT support for research is decentralized, with only shared networks centralized. The IT support for teaching and business applications is centralized, and there is close alignment between IT and users. Business applications supported include typical university applications providing services to students and faculty. Eighteen months ago, storage management was "out of control", according to Jon Miller, storage administrator at Purdue. Utilization was very low, and most of the SAN-based storage was not appropriately tiered. Moreover, the application staff was too heavily involved in the management of storage. There were 14 separate SAN switches and a lack of continuity in storage management, which led to a fragmented design and inefficient administration of resources. The SAN fabric was of a mesh design, and switch ports were consumed in multiple interswitch links (ISLs). To bring this under control, the SAN fabric was redesigned into a core/edge topology, with two Brocade director-class switches implemented at the core. Appropriate tiering was implemented on mainly EMC DMX and Clariion arrays. File services were centralized on EMC Celerra NAS systems, and archiving was managed on EMC Centera platforms. While this strategy helped to improve efficiency, the IT department still found it difficult to optimize the allocation and management of storage on the SAN. Once storage was allocated, it was extremely time-consuming to add capacity and move it. These tasks required significant planning and the help and cooperation of the platform administration groups to achieve any change. The Purdue IT department decided that the next stage of storage infrastructure improvement was to virtualize the storage environment. This would enable Purdue to centralize storage management and to allow storage to be migrated seamlessly without impacting users. Importantly, it would also allow lower-cost storage arrays and storage management software to be deployed. The Purdue IT department looked at virtualization offerings from EMC, Hitachi Data Systems, and IBM and chose EMC's Invista as the least disruptive and lowest risk option. The Invista platform will eventually support all SAN arrays except Exchange e-mail and backup. Invista is at an early stage of production deployment and will be fully deployed over the next six months. Installed environment The applications supported by the SAN include e-mail, financial, educational applications, HR, housing and food services, physical facilities, student support systems, and other applications. The main database systems supported on the SAN are Oracle 9i and Oracle 10g. The main ERP system is SAP. Additional details can be found at www.itap.purdue.edu/business/. Pain points
Solution strategy Purdue is investigating upgrading the two Brocade core switches with a special blade to enhance performance if needed. Most of the current storage management software from the DMX and Clariion arrays is being retained, allowing the least change to existing application and storage management procedures. Business continuance procedures that use EMC's Symmetrix-based SRDF are being modified to use either native Oracle 9i or 10G database support for remote replication or Invista-based remote replication. (See table, below.) Adoption issues Purdue's storage group must establish a track record of efficiency, responsiveness, and competency so that platform, application, and user groups are confident that storage provisioned meets requirements. Similarly, the storage group must ensure user satisfaction with business continuance after any move from SRDF to Invista-based remote replication or other solutions. Finally, if Purdue chooses to add blades in the Brocade switches, further testing and integration will be required. Notably, this upgrade will require Purdue to migrate from Invista 2.0 to Invista 2.1, and it is unclear how EMC plans to support migration non-disruptively. Benefits The project has also begun to reduce dramatically the number of people who are aware of changes to storage, especially where migrations are involved. Thus far, Purdue has seen advantages in terms of the storage group's being more responsive and less of an obstacle. In addition, Purdue plans to achieve much higher utilization of its SAN-connected storage assets at a significantly reduced cost and use this success to reduce the amount of storage consumed. Purdue also hopes to avoid increased staff to manage platforms and storage as a result of the project. Best practice
Conclusions While Purdue was happy with the performance and reliability of Tier-1 Symmetrix arrays, it wanted to use lower-cost Clariion arrays where possible. The university has confidence in EMC as its supplier and wanted to leverage existing relationships. EMC created a financially attractive offering by packaging additional Symmetrix boxes with Invista together with deep educational discounts. EMC successfully sold the potential scalability of Invista using the split-path architecture as a competitive differentiator. Because Purdue's applications do not all require SRDF resilience, recovery can now be satisfied with less expensive methods. The organization is reducing its software costs by using remote replication with Invista, for example. However, Wikibon believes that there are three weak points in the strategy:
On balance, however, Wikibon concludes Purdue University made a sound business decision in electing to implement Invista from its established supplier. All the proposed vendor solutions were viable, but the EMC solution was low risk because of the least change required to existing processes and procedures, and familiarity and comfort with how EMC operates. Purdue is implementing a strategy that, if well-executed, will put in place a significantly more cost-effective storage infrastructure. It should improve storage utilization and flexibility and should enable storage to be potentially handled more efficiently by storage administrators, rather than by system administrators. (Note: Also see case studies on Hitachi's USP and IBM's SVC.) Dave Vellante and David Floyer are co-founders of The Wikibon Project, an open community of practitioners, consultants, and researchers dedicated to improving technology adoption. The authors can be contacted at david.vellante@wikibon.org or david.floyer@wikibon.org. Page 1 of 1
|
|
||||||||||||||||||||||||||||||
|
|
|