Presentation is loading. Please wait.

Presentation is loading. Please wait.

March 2003 Copyright University of Michigan How the University of Michigans SAN Pays For Itself University of Michigan Administrative Information Services.

Similar presentations


Presentation on theme: "March 2003 Copyright University of Michigan How the University of Michigans SAN Pays For Itself University of Michigan Administrative Information Services."— Presentation transcript:

1 March 2003 Copyright University of Michigan How the University of Michigans SAN Pays For Itself University of Michigan Administrative Information Services Chris Wood Nancy Medd March 26, 2003 Copyright University of Michigan This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.

2 March 2003 Copyright University of Michigan About the University of Michigan Founded in 1817 Three campuses – Ann Arbor – 19 schools & colleges, University Hospitals & Health Centers Dearborn – 4 schools & colleges Flint – 4 schools & colleges Research & Educational Units 35 Centers 18 Institutes University of Michigan Administrative Information Services

3 March 2003 Copyright University of Michigan University ProfileFall 2002 Student enrollment – 54,131 Faculty – 5,977 Staff – 23,123 University of Michigan Administrative Information Services

4 March 2003 Copyright University of Michigan Introduction Michigan Administrative Information Services Administrative computing arm of the University of Michigan NOT login servers, research, student systems, hospital…

5 March 2003 Copyright University of Michigan Pre-SAN Environment … PeopleSoft Financials Higher Education Human Resources Oracle (55 databases) AIX (35 servers) Windows (61 servers)

6 March 2003 Copyright University of Michigan … Pre-SAN Environment 22 Terabytes of attached storage 14 TB unprotected 8 TB protected with mirrors (3.5 TB usable) 2100 SSA disks 13 TB occupied 9 TB allocated but not occupied 58% of allocated storage was occupied

7 March 2003 Copyright University of Michigan

8 March 2003 Copyright University of Michigan Problems We Faced… Machine room was full (floor space and UPS) Large numbers, sizes and speeds of disks were hard to manage and inventory Disk failures were more common as the number of disks increased (129 failures in the past 12 months) Hardware maintenance costs increased

9 March 2003 Copyright University of Michigan …Problems We Faced Databases were multiplying, both in size and number Unused storage was rarely where it was needed Database replication between hosts was slow Disaster Recovery was increasingly important

10 March 2003 Copyright University of Michigan We Purchased a SAN SAN=Storage Area Network Smart disk arrays Fiber channel directors Host adapters connecting all of the pieces

11 March 2003 Copyright University of Michigan Post-SAN Environment PeopleSoft, Oracle, AIX 2 McData directors 3 IBM ESS 800s (sharks) 19 TB of storage, all protected 352 disk on sharks 32 SSA disks 70% occupied FlashCopy on one shark

12 March 2003 Copyright University of Michigan

13 March 2003 Copyright University of Michigan The Implementation

14 March 2003 Copyright University of Michigan Where we are in the Implementation Completed design (3 months) Halfway through implementation (3 months into 6 month plan) All test and development servers are complete Some production servers have moved

15 March 2003 Copyright University of Michigan Implementation Timeline

16 March 2003 Copyright University of Michigan Implementation: What We Expected Steep learning curve to master management of the new equipment Lots of mistakes in the initial configuration Migration process would quickly become trivial Minimal disruption to hosts Lots of DBA resistance Not many people outside system support and database administration would care

17 March 2003 Copyright University of Michigan Implementation Surprises: Bad… Machine room couldnt handle the new equipment Insufficient floor space Not enough UPS power Floor wasnt strong enough Migrations never became trivial More outages than expected Software installation Data moves

18 March 2003 Copyright University of Michigan …Implementation Surprises: Bad Security concerns caused us to drop some servers from the SAN plan Aggressive implementation schedule left little time to train remainder of the team Database administrators were suspicious of both reliability and performance on the SAN Many people in the organization were interested in all of the details (the spotlight is on)

19 March 2003 Copyright University of Michigan Implementation Surprises: Good… Many people in the organization were interested in the SAN It was easier than expected to learn to manage the new hardware There were no large scale design mistakes

20 March 2003 Copyright University of Michigan …Implementation Surprises: Good The changes that forced outages for each data move allowed us to rethink our data layouts We could migrate some test databases during scheduled refreshes While the database administrators are still skeptical, theyre softening

21 March 2003 Copyright University of Michigan Implementation: What Wed Do Differently Address security earlier to avoid planning moves for machines that never should have moved to the SAN Spread the implementation over more time Train all system support staff earlier so the workload could be distributed

22 March 2003 Copyright University of Michigan Changes to the way we work Restructured databases so ongoing space management is easier Increased thresholds for when we add space since it is easier and faster to allocate SAN storage Developed new storage request tracking procedures Began to proactively order disk

23 March 2003 Copyright University of Michigan Scorecard How did we do?

24 March 2003 Copyright University of Michigan Problems we didnt solve… Storage needs are still increasing Database replication isnt, in general, faster Didnt buy FlashCopy for all sharks t Software is expensive t Additional disks to support FlashCopy are expensive t Additional disks would have meant more frames FlashCopy only works within a shark

25 March 2003 Copyright University of Michigan …Problems we didnt solve Our DR situation hasnt improved; however, we expect it to once the SAN implementation is complete.

26 March 2003 Copyright University of Michigan Problems we solved… Machine room space and power situation has improved Storage management is much easier since software, not hardware controls it all Increasing storage needs are met with fewer physical disks Larger capacity disks Less wasted space

27 March 2003 Copyright University of Michigan …Problems we solved Disk failures are less common (0 in 5 months) Saved money on maintenance Prepaid, so prices are locked in Maintenance costs are lower on new disks than old Fewer physical disks reduces costs Nightly replication of production databases is faster

28 March 2003 Copyright University of Michigan Unexpected Wins Many fewer hardware error calls to system support Fewer outages Maintenance windows are shorter because systems boot faster Performance features in the disk arrays allow use of much larger capacity disks

29 March 2003 Copyright University of Michigan Features for the Future Peer-to-Peer Remote Copy to copy one shark to another for disaster recovery LAN-free backup to move backup traffic from the LAN to the SAN Server-free backup to move backup processing from servers to a dedicated SAN-aware backup engine

30 March 2003 Copyright University of Michigan How the SAN pays for itself…

31 March 2003 Copyright University of Michigan … How the SAN pays for itself … Projected SAN payback of 4.5 years

32 March 2003 Copyright University of Michigan … How the SAN pays for itself Were ahead of schedule for payback Using disk space more efficiently Requiring justification for disk requests results in better storage planning Increased thresholds for when we add space since it is easier and faster to allocate SAN storage

33 March 2003 Copyright University of Michigan Questions?


Download ppt "March 2003 Copyright University of Michigan How the University of Michigans SAN Pays For Itself University of Michigan Administrative Information Services."

Similar presentations


Ads by Google