Download the authoritative guide: Enterprise Data Storage 2018: Optimizing Your Storage Infrastructure
Determine SAN CostsThe proposed SAN infrastructure has to have completed a logical design that will capture the design parameters and the list of components for the baseline costs in order to develop the proper payback models for the business case. This can be accomplished with a variety of services that can provide rough order magnitude (ROM) designs and costs based on information gathered from workshops or an onsite assessment. A preliminary list of SAN components (h/w, s/w, middleware, cabling, integration labor, etc.) can be summarized and priced, once the design is roughed-out and blueprints are available.
A useful comparative review of design and operational needs is provided by applying ROI models on more than one topology. Some topology design options can be very similar in price, but yield different total cost of ownership (TCO) cost streams or ROI payback terms. A balanced financial approach to the analysis and cost/benefit determination is created by having two or three topology options (network attached storage (NAS), point-to-point (PtP), FC switch or director, etc.). Since storage growth is assumed to continue regardless of the attachment architecture (small computer system interface (SCSI), FC, SAN, Enterprise Systems Connection (ESCON), etc.), some (but not all) of the SAN ROI analysis is completed without considering the detailed cost of storage. Thus, the cost of additional or replacement storage may need to be separated from any new SAN infrastructure costs when selecting and implementing a payback model/option. In other words, most ROI cases are prepared from the perspective of justifying the new SAN infrastructure, not necessarily the attached storage.
The future price of SAN infrastructure can be normalized to NPV cost or the average year costs, if the enterprise needs to migrate to SAN via PtP and small fabric installations (i.e., Fibre Channel Arbitrated Loop (FC-AL) or small switch). Future year, incremental growth will need to factor price erosion of future SAN components. It is often best to show total costs per usable SAN port as a comparison in the phased implementation, if an incremental approach to SAN is planned. Otherwise, for each SAN development phase, a separate ROI calculation would be needed.
Now, let's very briefly look at a few of the business planning cases that enterprises can choose from (who are currently working in a DAS environment), when performing a SAN ROI exercise to determine whether they should consider a move to their first SAN. Not all cases are equal in value and applicability to the target environment. Some cases are more specific to very large or mature enterprise infrastructures. Others are best suited for small sites, any kind of service provider (XSP), decentralized sites, etc. Those considering a move to their first SAN should be familiar with the following options in order to choose those that best apply to the target environment.
SAN ROI Case SelectionsIn order to build a business plan/justification, most enterprise environments choose between six and nine ROI business planning cases. Depending on the payback methods needed in the analysis, each case has specific characteristics that may vary, such as:
- Achieving Service Level Agreement (SLA) targets.
- Growth attainment.
- Immediate cost reduction.
- Long-term TCO reduction.
- Operational efficiencies.
Next, let's look at these cases. In the interest of the length, only the most popular or widely used of the cases will be discussed in detail in this article.
Disk Utilization IncreaseImproved storage asset utilization is inherently provided by pooled storage. As shown below, DAS storage can vary by platform:
- Windows NT--20 to 40 percent average disk utilization.
- UNIX--30 to 40 percent average disk utilization.
- S/390--60 to 70 percent average utilization.