Not Logged In

You could:

Log in
Register

research notes
  • Wikitips
  • Professional Alerts
  • Case Studies
  • How-to Notes
  • Community Questions
research meetings
  • Peer Incite Podcasts
  • Peer Incite Archive
Events
  • Enterprise Architect Summit 2008
    Oct 4-6, 2008
  • Computerworld: Storage Networking World
    Oct 12-15, 2008
  • Energy Efficiency and Sustainability Symposium
    Nov 5-6, 2008
  • End-to-End Reliability: The Green Horizon
    Nov 15-18, 2008
  • Business Continuity Planning 2008: Architecting a Reliable Data Management and Protection Plan
    Nov 18, 3:00-7:30 AM

Announcements
  • 10-07-08 Peer Incite: Best practice in tape backup and recovery
  • IBM's stealth XIV announcement
  • Welcome to Wikibon 2.0!
  • The IBM XIV Storage System Model A14
  • Storage Customers Seeing Green with Conserve IT
Home Profile Peers Wiki Groups Feedback


  • Article
  • Comments (0)
  • Page Protected
  • History
  • Vault
Implementing tiered storage
  • Currently n/a/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
rate this
Last Update: Feb 20, 2008 | 11:05
Viewed 3089 times | Community Rating: n/a
Originating Author: David Vellante

Many organizations are experiencing rapid growth in the amount of information held on computer storage and storage costs are escalating.

Traditional methods of managing storage use either a “one size fits all” strategy, or a "Mix, Match and Manage" approach introducing many different storage pools. The challenge of the first technique is high equipment cost, whereas the latter often brings higher labor costs to manage the multiple storage pools all with different software, services and procedures.

Today's storage technologies span a spectrum from high density, low cost, low performance storage at one end to increasingly sophisticated data management functionality at the other. Creating storage tiers with more granularity with a single management approach begins to address the problems that one size does not fit all and storage pools are hard to manage.

Contents

  • 1 Tiered storage capability
  • 2 Specific operational goals of implementing tiered storage
  • 3 Risks of implementing tiered storage
  • 4 The tiered storage initiative
    • 4.1 Expectations (out-of-scope)
    • 4.2 Analyze phase
      • 4.2.1 Acceptance test considerations
      • 4.2.2 Key analysis milestones
    • 4.3 Design phase
      • 4.3.1 Acceptance test considerations
      • 4.3.2 Key design milestones
    • 4.4 Deploy phase
      • 4.4.1 Acceptance test considerations
      • 4.4.2 Key deployment milestones
  • 5 Tiered storage summary

Tiered storage capability

Tiered storage is the process of provisioning different types of storage media based on application requirements. Storage tier choice may be based on performance, cost, protection needed, speed of recovery, and many other considerations. Ideally, a common set of storage services and procedures can be applied as required to each tier, matching application requirements with storage tier characteristics. A more complete description can be found on the WikiBon entry for Tiered storage.

Tiered storage has the potential to reduce the costs of storage and storage management functionality for some applications and improve the performance, availability, and recovery capabilities of others. The primary initial costs associated with a tiered storage implementation include software to manage the environment, implementation expenses, and possibly write-down costs for hardware that will be retired.

Specific operational goals of implementing tiered storage

The likely investment required to implement tiered storage is between $0.5 million to $0.7 million, with an elapsed time of between 6 to 9 months. [Note: These figures assume a Standard WikiBon business model organization with $1B in revenue with 4,000 employees and an IT budget of $40M per year. The scenario assumes that 40 terabytes are installed, with a mixture of high performance SAN, mid-range storage solutions, some direct attached storage, and some NAS]. A successful tiered storage implementation will:

  • Allow consumers of storage to optimize the functionality, performance, and cost profile for storage that best fit the business need for each application by providing different tiers of storage.
  • Ideally, provide a common set of storage management tools, processes and procedures and services for all the storage tiers, including the ability to dynamically migrate storage to the optimal tier.

The major expected reductions in IT cost will normally include:

  • Fifteen percent (15%) reduction in cost of equipment and connectivity (~$200K/year).
  • Twenty percent (20%) reduction in cost of storage administration (~$150K/year).

Case studies indicate the major expected business productivity improvements (so-called intangibles) will yield an estimated gain that equates to ~.06% of revenue and normally be derived from the following:

  • Business benefits of accelerating time to implement new projects or speed changes (~$200k/year).
  • Business value of improving security measured in mitigated losses (~$100k/year).
  • Economic benefit of higher performance on user productivity (~$75k/year).
  • Business value of improved productivity from reduced application downtime (~$25k/year).
Figure 1 - Tiered Storage Rules of Thumb
Figure 1 - Tiered Storage Rules of Thumb

In addition to the investment in tiered storage, other potential impacts on an organization include:

  • Loss on books for storage equipment and software retired early.
  • The business impact of delaying some projects because of resources dedicated to storage.

An analysis of the need for tiered storage is likely to find that a business case including both IT and business benefits will be good (ROI and IRR>150%), while a business case with only IT benefits is likely to be deemed acceptable (ROI & IRR ~100%). The business cases will be improved if organizations align spending on storage services with the additional business value these services generate in the supported applications.

Risks of implementing tiered storage

Tiered storage is a medium risk initiative. In general, tiered storage technologies, software, processes and procedures are still immature. The industry has yet to agree a common definition of tiered storage. In particular the current storage management software that monitors service level agreements at the application level can best be described as inadequate. There are four major risks to a tiered storage initiative:

  1. Incorrectly defining the the number of tiers can increase costs.
  2. Incorrectly designing the service level capabilities for each tier can negatively impact cost and business value.
  3. Lack of tools to monitor and report storage on an application basis will negate the benefits of tiered storage.
  4. Migrating to a common set of storage services risks compromising service levels for certain applications in the near term.

The tiered storage initiative

The tiered storage will be implemented when the tiered storage infrastructure has been designed, built, tested, implemented and successfully handed over to operations so that it can run as specified without external support.

Expectations (out-of-scope)

The following factors that are not within the scope of the tiered storage initiative are vital to ensure a successful tiered storage outcome:

  • Application service level agreements are in place.
  • A charge-back mechanism is in place that can be changed to charge user departments according to storage used and storage tier.
  • Storage virtualization has been planned and/or implemented.
  • The IT organization will support consolidating the storage management services and procedures.
  • The primary storage vendors for the storage pools analyzed have solid tiered storage offerings.

Analyze phase

A fully detailed blueprint and step-by-step project outline for the analysis phase can be found at Analyzing tiered storage requirements.

Acceptance test considerations

The analyze phase will be completed when the initial business case has been accepted by the sponsor, and agreement has been reached to proceed to the design phase or kill the project.

Key analysis milestones

This phase should take about 4-6 weeks and 14-20 person days of effort.

  1. An effective sponsor of the initiative is identified
    • It is important that the sponsor can resolve any organizational issues
  2. Data collected
    • Determine the actual storage service level delivered for each of the major application groups
    • Determine the total costs of the storage, including complete staff costs, storage management costs, storage network costs, connectivity costs and (where applicable) telecommunication costs
    • Determine where there is either over provisioning or under-provisioning of storage services by application
    • Calculate the business and IT impact of that over/under-provisioning by application
  3. An initial tiered storage design built:
    • Construct a basic tiered storage design and cost structure (one-time and ongoing).
    • Rules of thumb are that the number of tiers should be between 4 and 6, and is very unlikely to be outside the range of 2-8. The cost/GB of each tier up should be ~50%-100% more expensive.
  4. Business case constructed:
    • Analyst constructs business case / cost benefit analysis detail.
  5. Initial Design and business case accepted by sponsor and any other stakeholders necessary

Design phase

Individuals interested in a detailed discussion of tiered storage design should check out Designing tiered storage.

Acceptance test considerations

The design phase will be completed when the design has been accepted by the sponsor and agreed to by the key application user groups, and agreement has been reached to proceed to the deploy phase or kill the initiative.

Key design milestones

This phase should take about 5-7 weeks and about 30 person days of effort.

  1. The number of storage tiers required established
    • There is a trade-off between the number of storage tiers provided, and the overhead of managing and migrating data between the different tiers. In practice, the number of tiers can be determined by:
      • Taking the key applications that support the business (e.g., CRM, Email, Finance, Reporting, etc.). Create a table with the characteristics required for each of the major key applications. The figures in the table are not what is currently provided, but a judgment on what the most appropriate storage service level is to support the efficiency of the users.
      • Group the applications into similar tiers, reducing the number of tiers. Usually, the number of tiers will be between three and six. In smaller installations it may be as low as 2, but should not be above 10 under almost any circumstances.
  2. The storage network implications analyzed and the costs/savings of additional/reduced ports, switches, and other network costs computed
  3. A storage cost/Gigabyte calculated for each tier, with a rule of thumb that each successive tier should be between 50%-100% more expensive
  4. The storage tier(s) appropriate for the major applications agreed with the user departments, together with the growth rates expected, and expected storage budgets and storage service levels set for each major application. This agreement process has been pushed down to the rest of the application groups

Deploy phase

Acceptance test considerations

The deploy phase will be completed when tiered storage is built, tested, and brought into service. The agreed service levels for each tier should have been met for at least 3 months, and the operations group able to operate independently of the design and implementation teams.

Key deployment milestones

This phase should take about 4-6 months and cost between $0.4million & $0.6million.

  1. Tiered storage built
    • A tiered storage system RFP should have been defined and issued, including (optimally) virtualization capabilities, common storage management capabilities, and the ability to migrate from the existing infrastructure to the tiers and between tiers without interruption
    • Installation of storage hardware and storage management functionality
    • Update and creation of new process and procedures, with full documentation
  2. Tiered storage tested
    • Testing of equipment, software, and procedures on historical data
    • Testing of tiers on some non-mission critical live applications
    • Testing of procedures for migration, backup, recovery, and disaster recovery
    • Tiers supporting key applications stress tested
  3. Migration & Cut-over to tiered storage completed
    • Phased migration cut-over to tiered storage
    • Extensive monitoring of performance, reliability, & storage efficiency metrics (storage utilization, administration efficiency, planned vs. actual allocation of storage to tiers)
  4. Tiered storage initiative wrapped up
    • Procedures set up for monitoring expected/actual achievement on key storage metrics
    • Procedures set up for adding additional storage & storage functionality
    • Final review of documentation
    • All project staff released and full hand-over to storage operations

Tiered storage summary

Tiered storage is a technology that makes intrinsic sense. Most organizations are likely to determine that a tiered storage implementation should be in their strategic plans. When organizations have the storage architecture foundations in place, such as centralization, virtualization, and a commitment to a single management suite, early implementation should be considered. If the foundations are immature, tiered storage may wait or be implemented in an a part of the organization ready to exploit the solution.

categories
How-To notes, Tiered storage
Contributors

Dab4168

Mrgood

PBurris

David Floyer

Comments (0)
Comments on 'Implementing tiered storage'
There are currently no comments. Be the first!
Post A Comment

You must be logged in to post a comment, please Sign in

Revision ID Author Timestamp Comment
14096 Dab4168 08 Feb 20 11:05:30 Removed category: Level 1
13799 Dab4168 08 Feb 16 18:56:35 removed category Author Dfloyer
10041 Dvellante 07 Aug 20 11:21:20 /* Risks of implementing tiered storage */
10040 Dvellante 07 Aug 20 11:21:08 /* Tiered storage summary */
10039 Dvellante 07 Aug 20 11:20:44
9723 Dvellante 07 Jul 31 11:33:47 revert back to original format
9722 Dvellante 07 Jul 31 11:19:48
9721 Dvellante 07 Jul 31 11:19:32
9720 Dvellante 07 Jul 31 11:19:20 finished piece
8940 Dab4168 07 Jun 12 09:47:48 misc
8939 Dab4168 07 Jun 12 09:47:21 misc
8938 Dab4168 07 Jun 12 09:46:57 added comment re protection of page
8937 Dab4168 07 Jun 12 09:44:55 Protected "[[Implementing tiered storage]]": excessive vandalism [edit=sysop:move=sysop]
8936 Dab4168 07 Jun 12 08:48:40 Reverted edits by [[Special:Contributions/121.140.227.47|121.140.227.47]] ([[User_talk:121.140.227.47|Talk]]); changed back to last version by [[User:Dab4168|Dab4168]]
8935 121.140.227.47 07 Jun 12 02:22:56
8934 Dab4168 07 Jun 11 08:38:13 Reverted edits by [[Special:Contributions/83.224.64.4|83.224.64.4]] ([[User_talk:83.224.64.4|Talk]]); changed back to last version by [[User:62.231.243.137|62.231.243.137]]
8933 83.224.64.4 07 Jun 10 16:29:44
8834 62.231.243.137 07 Jun 06 09:48:49
8533 Mrgood 07 May 17 09:53:34
8528 210.17.245.191 07 May 17 05:14:41
8433 PBurris 07 May 09 18:30:06
8432 Dvellante 07 May 09 18:26:03
8431 Dvellante 07 May 09 18:25:07 Reverted edits by [[Special:Contributions/66.202.41.205|66.202.41.205]] ([[User_talk:66.202.41.205|Talk]]); changed back to last version by [[User:Dvellante|Dvellante]]
8430 66.202.41.205 07 May 09 18:23:38
8429 Dvellante 07 May 09 09:41:31 Reverted edits by [[Special:Contributions/221.28.172.47|221.28.172.47]] ([[User_talk:221.28.172.47|Talk]]); changed back to last version by [[User:83.211.3.16|83.211.3.16]]
8428 221.28.172.47 07 May 09 06:14:58
8360 83.211.3.16 07 May 05 23:07:20
8003 200.238.102.170 07 Apr 10 14:35:41
7489 68.167.139.254 07 Mar 12 03:09:42
7416 Dab4168 07 Mar 08 17:48:34 Re-categorization
6214 Dvellante 07 Feb 16 13:11:46
5741 Dvellante 07 Feb 02 14:04:23
4677 Mrgood 07 Jan 04 14:03:22
4569 Dvellante 07 Jan 03 22:15:36
4568 Dvellante 07 Jan 03 22:15:15
4157 68.189.241.40 06 Dec 26 17:57:42 /* Tiered storage summary */
4156 68.189.241.40 06 Dec 26 17:57:13
4155 68.189.241.40 06 Dec 26 17:55:46 /* Risks of implementing tiered storage */
4154 68.189.241.40 06 Dec 26 17:55:20
4153 68.189.241.40 06 Dec 26 17:54:31 /* Tiered storage capability */
4152 68.189.241.40 06 Dec 26 17:53:28 /* The tiered storage initiative */
4151 68.189.241.40 06 Dec 26 17:51:03
4150 68.189.241.40 06 Dec 26 17:50:45 /* Tiered storage capability */
4149 68.189.241.40 06 Dec 26 17:49:59
4148 68.189.241.40 06 Dec 26 17:49:08 /* Tiered storage capability */
4147 68.189.241.40 06 Dec 26 17:48:49
4135 Dvellante 06 Dec 26 17:14:53
4133 68.189.241.40 06 Dec 26 17:06:35
3924 Mrgood 06 Dec 15 03:27:09
3923 Mrgood 06 Dec 15 03:26:26
3362 Dvellante 06 Dec 08 12:10:24 /* Specific operational goals of implementing tiered storage */
3361 Dvellante 06 Dec 08 12:03:04 /* Specific operational goals of implementing tiered storage */
3240 Dvellante 06 Dec 07 00:25:49 /* Tiered storage summary */
3239 Dvellante 06 Dec 07 00:23:31 /* Expectations (out-of-scope) */
3238 Dvellante 06 Dec 07 00:21:09 /* Tiered storage initiative */
3237 Dvellante 06 Dec 07 00:20:26 /* Risks of implementing tiered storage */
3236 Dvellante 06 Dec 07 00:19:20 /* Specific operational goals of implementing tiered storage */
3235 Dvellante 06 Dec 07 00:14:31 /* Specific operational goals of implementing tiered storage */
3234 Dvellante 06 Dec 07 00:13:50 /* Specific operational goals of implementing tiered storage */
3233 Dvellante 06 Dec 07 00:11:25 /* Specific operational goals of implementing tiered storage */
3232 Dvellante 06 Dec 07 00:09:41 /* Tiered storage capability */
3142 Dab4168 06 Dec 06 17:59:29 /* Specific operational goals of implementing tiered storage */ misc
3114 Dab4168 06 Dec 06 16:41:25 /* Specific operational goals of implementing tiered storage */ misc
3106 Dvellante 06 Dec 06 16:00:38 /* Risks of implementing tiered storage */
3105 Dvellante 06 Dec 06 16:00:03 /* Risks of implementing tiered storage */
3104 Dvellante 06 Dec 06 15:59:02 /* Risks of implementing tiered storage */
3102 66.202.41.205 06 Dec 06 15:50:03 /* Specific operational goals of implementing tiered storage */
3101 66.202.41.205 06 Dec 06 15:48:06 /* Tiered storage capability */
3098 66.202.41.205 06 Dec 06 15:44:34
3070 Mrgood 06 Dec 06 10:40:58
3067 Mrgood 06 Dec 06 10:38:33
3023 Dvellante 06 Dec 05 22:53:34 /* Design phase */
3019 Dvellante 06 Dec 05 22:36:20 /* Analyze phase */
3018 Dvellante 06 Dec 05 22:24:23 /* Analyze phase */
2932 66.202.41.205 06 Dec 04 08:31:25
2853 Dvellante 06 Nov 28 17:39:17 /* Tiered storage summary */
2852 Dvellante 06 Nov 28 17:36:53 /* Deploy Activities & Milestones */
2851 Dvellante 06 Nov 28 17:36:31 /* Deploy Acceptance Test Considerations */
2850 Dvellante 06 Nov 28 17:36:07 /* Design Activities & Milestones */
2849 Dvellante 06 Nov 28 17:35:27 /* Design Acceptance Test Considerations */
2848 Dvellante 06 Nov 28 17:35:05 /* Analysis phase */
2847 Dvellante 06 Nov 28 17:34:25 /* Out-of-Scope Expectations */
2846 Dvellante 06 Nov 28 17:34:02 /* Tiered storage initiative outline */
2845 Dvellante 06 Nov 28 17:33:49 /* Risks for implementing Tiered Storage */
2844 Dvellante 06 Nov 28 17:33:25 /* Specific operational goals of tiered storage */
2843 Dvellante 06 Nov 28 17:33:08 /* Operational Goals of Implementing Tiered Storage */
2842 Dvellante 06 Nov 28 17:30:50 /* Tiered storage capabilities */
2835 David Floyer 06 Nov 28 17:04:46
2832 David Floyer 06 Nov 28 16:54:09
2825 Dvellante 06 Nov 28 15:31:13 /* Tiered Storage Capabilities */
2819 David Floyer 06 Nov 28 08:32:11
2818 David Floyer 06 Nov 28 08:18:41
2817 David Floyer 06 Nov 28 08:12:06
2816 David Floyer 06 Nov 28 06:53:37
2815 David Floyer 06 Nov 28 06:51:20
2814 Dvellante 06 Nov 27 18:04:28 /* Operational Goals of Implementing Tiered Storage */
2813 Dvellante 06 Nov 27 18:04:02 /* Operational Goals of Implementing Tiered Storage */
2812 Dvellante 06 Nov 27 18:02:00 /* Tiered Storage Capabilities */
2811 Dvellante 06 Nov 27 18:00:15
2810 Dvellante 06 Nov 27 17:58:20

Search:

news feed
  • Latest from Computerworld - Ask.com upgrade to add improved relevance, speed
  • eWeek - RSS Feeds - Passports: Another Bad Use of Self-Signed Certificates
  • InfoWorld RSS Feed - Google, Yahoo delay ad deal over DOJ investigation
  • Byte and Switch: - Unitrends Enhances Rapid Recovery Backup Platform
  • SearchStorage: News and trends in the storage industry - FalconStor CEO: Recovering data is problem No. 1
all »
blogs
  • Hu Yoshida - This down turn requires a focus on ROA
  • NetApp - Dave's Blog - Lessons from the Last Crash
  • DrunkenData.com - XAM-it!
  • Storagezilla - Something on Rainfinity (And it's creator)
  • Paul Gillin's Blog - Can You Hear Me Now?
all »
companies
  • IBM
  • NetApp
  • Hitachi
  • XIV
  • EqualLogic
  • Dell
all »
Want a Wikibon
Peer Incite
newsletter?

Email: Privacy by Safe Subscribe
Storage Spectrum
Order Storage Spectrum
By Fred Moore
US & Canada Only!
Browse best practices . publish tips . access project tools . collaborate with peers . get help on RFP's . use privacy settings to control who sees your info . join a group and share experiences with colleagues . review case studies . read professional alerts
  • Cloud Computing
    Clustered storage, Storage services, WEB2.0
  • Companies
    3PAR, Compellent, Dell, EMC, EqualLogic, HP, Hitachi, IBM, LSI, LeftHand Networks, NetApp, STEC inc, Sun, XIV
  • Data Protection
    Backup and restore, Business compliance, CDP, Data deduplication, Storage disaster recovery, Storage security
  • Energy Efficiency
    Data deduplication, Green storage, MAID, Thin provisioning, Tiered storage, VMware, Virtual tape
  • Planning Design Implementation Management
    Backup and restore, Business compliance, Data classification, Green storage, Managing storage, ROI, SRM, Storage Design, Storage asset management, Storage capacity management, Storage capacity planning, Storage implementation, Storage management, Storage operations, Storage planning, Storage vendor management, Tiered storage
  • Storage networks
    Clustered storage, ISCSI, NAS, SAN, SRM, Storage consolidation, Tiered storage, VMware
  • Virtualization
    Clustered storage, Green storage, Storage consolidation, Storage virtualization, Thin provisioning, VMware, Virtual tape
© Wikibon 2008 About Wikibon l Contacts l Terms of Service l Disclaimers l Privacy l Help