Meeting Today’s Data Storage Needs

Meeting Today’s Data Storage Needs
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Meeting Today’s Data Storage Needs Module 1.1

Meeting Today’s Data Storage Needs
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Meeting Today’s Data Storage Needs Upon completion of this module, you will be able to: Describe who is creating data and the amount of data being created Describe the value of data to business Describe the challenges in data storage and data management List the solutions available for data storage In this module, we will look at the: Amount of data being created Consequent need for a storage solution, and Critical role that storage plays within the IT environment. Storage Systems Architecture - Introduction

Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved.
Data Creation Data is being created at an ever increasing rate Data creation/generation is growing at a rate in excess of 50% year-over-year The need to store the data over longer periods of time with improved accessibility is also growing Information Technology (IT) budgets are responding IT budgets typically have to account for expenditure on Servers, Networks, Storage, Personnel, etc. To keep up with data storage needs, IT expenditure on Storage has increased proportionally It is estimated that about 40% of the IT expenditure is Data Storage related With the current trend in data growth and the corresponding needs for storing and managing data, there is an increasing demand for personnel who understand data storage and the value of data to businesses. This role is still being defined, but we refer to it as a Storage Technologist. It would be beneficial to examine who is creating data, what types of data are being created and when data becomes information. Storage Systems Architecture - Introduction

Data Creation: Individuals
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Creation: Individuals What data is created by Individuals? Examples include: Photos Documents Spreadsheets Video Individuals and businesses create and maintain data. All of us continually create data such as pictures that we would like to have immediately available and stored forever. Storage Systems Architecture - Introduction

Data Creation: Individuals
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Creation: Individuals Where is this data stored? Storage can be in: Cameras MP3 players Laptop hard drives CDROM/DVDs USB drives The data that individuals generate is stored in a variety of locations. Managing these diverse pieces of data can be a challenge. Storage Systems Architecture - Introduction

Data Creation: Business
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Creation: Business What data is created by a business? Examples of data created by a business include: Product data: inventory, description, pricing, availability, sales numbers and projections Customer data: orders, shipping details Account data: banking, financial services industry Medical data: health care providers, insurance industry, hospitals Although individuals create a lot of data, businesses do too. The data that a business collects is about their customers, partners, products and services. Consider a bank with several million customers. Information about their accounts has to be maintained accurately, securely, and in such a way that it is accessible to those who need it “on-demand” (24X7). Storage Systems Architecture - Introduction

Data Creation: Business
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Creation: Business Where is this data stored? Business data can be stored on: Employee workstations Servers Disk arrays Tapes CDROM/DVDs Off-site libraries Where business data is stored depends on the size of the business. It may be on local, individual work stations or on centralized disk array systems. Storage Systems Architecture - Introduction

Value of Data to a Business: Information
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Value of Data to a Business: Information What do businesses “do” with the data they collect? They turn it into “information”. Examples of information include: Buying habits and patterns of customers GPS locations of delivery trucks Health history of patients Locations where a credit card is used Businesses collect data in order to create information. They “mine” the data to extract meaningful patterns or trends. Or they create information to better manage the business. Note: In the context of this course, we will treat “data” and “information” interchangeably. Storage Systems Architecture - Introduction

Value of Information to a Business
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Value of Information to a Business Identifying new business opportunities. For example: Buying/spending patterns: Internet stores, retail stores, supermarkets. Customer satisfaction/service: tracking shipments & deliveries. Identifying patterns that lead to changes in existing business. For example: Reduced cost: delivery service optimizing utilization of vehicles and gas. New products: MP3 player speaker systems. New services: security alerts for “stolen” credit card purchases. Targeted marketing campaigns: communicate to bank customers with high checking account balances about a special savings plan. Creating a competitive advantage! Traditionally businesses stored data because they had to. We all expect our respective banks to reflect our current balances accurately. What would happen if a bank were to discard historical information on account balances and transactions at the beginning of each statement period? For one thing, we would not be able to query our past statements, and the bank would not be able to defend its accounting accuracy. However, if the bank retains data, it could then analyze the balances in our accounts and target customers for new products/services. If some customers show a “high” balance in their savings account, the bank can then provide them with investment services with a potentially higher rate of return. The point is, while applications that can analyze data are important, availability of such data to analyze is even more critical. There is an ever increasing amount of data that is created/generated. And there is value to businesses in storing this over long term. Businesses can extract information from data for competitive advantage. Storage Systems Architecture - Introduction

Value of Individual Data to a Business
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Value of Individual Data to a Business What data, created by individuals, might be valuable to a business? Examples of business value from individuals’ data include: On-line resume storage and management service . On-line photo storage and organizer. Innovative businesses are being launched continually to use data in creative ways. As an example, let us consider our resumes example. In order to reach a wider set of prospective employers, we need to make this available to all of them. The job search businesses, in effect, “collect” our individual data and present it in a centrally accessible location to prospective employers (24x7). There are storage implications for this business. If each of our resumes is 4KB in size, one can compute the amount of storage required for this business to store millions of them. Now, add to that the jobs listing information from companies who post open job positions on the site. Finally, the job matching software is used to match key words from a resume to key words in a job description. In this fashion, the job search “engine” is using data but turning it into information. Storage Systems Architecture - Introduction

Information Availability - Downtime is Expensive
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Information Availability - Downtime is Expensive Millions of US Dollars per Hour in Lost Revenue Retail 1.1 Insurance 1.2 Information technology 1.3 Financial institutions 1.5 Manufacturing 1.6 Call location 1.6 Telecommunications 2.0 Credit card sales authorization 2.6 Energy 2.8 Accessibility and availability of data is becoming increasingly critical for businesses, and their customers. Consider the following: If one wishes to view photographs at home that were taken a few years ago, one can perhaps spend the time to locate the CDROM onto which the images have been recorded, load it into the appropriate drive on our personal computers and navigate to retrieve the image of interest. How ever, when we want to book a flight ticket, if the schedule/price/availability/seating information is not available to us in a reasonable time from a vendor of these services, we would perhaps go to another vendor or forgo the trip. Not only do businesses have to store data, they should also be able to make it available in an “uninterrupted” way. According to the META Group (2005), the cost of downtime is greater than ever, with outages in key industries costing millions of dollars per hour. Note that META’s analysis shows that outages are costly across a wide range of industries, including Financial Services, Telecommunications, Manufacturing, Retail, and Energy. Point of sale (POS) 3.6 Retail brokerage 6.5 Source Meta Group, 2005 Storage Systems Architecture - Introduction

Types of Data X-rays Images Data can be categorized as either structured or unstructured data. Over 80% of enterprise information is unstructured. (Fulcrum Research) What has been the traditional approach to storing all this data? Contracts Manuals Instant Messages Unstructured & Attachments Forms Structured Checks Rows and Columns PDFs Rich Media Documents Paper Data can be structured or unstructured. Structured data is formal, well organized and usually stored in a database or spreadsheet. Unstructured data is informal, possibly text (such as XML tagged content), disorganized or stored in files as whole documents or in content management systems. It is currently estimated that over 80% of enterprise information is unstructured. (Fulcrum Research, 2004) Data can be a mere collection of files or it can be organized into databases, more commonly relational databases. Unstructured data might require a lot more effort in searching for, retrieving, and presenting to the end-user, than structured data. Businesses generate unstructured data in the form of s, forms, marketing materials, web pages, etc. Claims Web Pages Audio & Video Records XML Invoices Storage Systems Architecture - Introduction

Storing Data: An Evolution
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Storing Data: An Evolution Centralized: terminals connected to a Mainframe computer which had connectivity to internal or external storage devices (disks, tapes). Decentralized: With the advent of Open Systems, business units within an enterprise adopted a Client-Server model. Centralized: Networked Storage (is the current “best practice” model being used in IT). Historically a centralized model for computing and data storage was the only available option. Processes had to be in place to access the data. This model introduced considerable delays in new application development and deployment. Access to data (such as a report request or for archived data) was predicated on business needs. Computational power was deemed more important than the immediacy of access. With advances in networking, the client-server model became prevalent. In this distributed model, business units within an enterprise could have access to their own servers and storage. Applications no longer had to wait in one central queue for data access and execution. However this leads to fragmentation of information. It also becomes difficult to enforce uniform processes and policies, as well as to manage these islands of information. The concept of Networked Storage grew out of these requirements. Production has its collection of clients, servers, and storage Finance has its collection of clients, servers, and storage Human Resources with its collection of clients, servers, and storage, etc. Note: Continued on next page… Storage Systems Architecture - Introduction

Worldwide Information Growth
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Worldwide Information Growth Annual Growth of Data Stored on Disk Arrays ~60% Average Growth Rate >70% in 2005 0% 40% 60% 80% 100% 120% 2001 2002 2003 2004 2005e The rate of information growth is plainly evident – more and more data is being created daily. This data is increasingly being stored on Storage Arrays. Storage Vendors are seeing the effects of this explosion in data growth as more and more organizations place their data on storage arrays. A survey conducted by IDC clearly demonstrates that more and more companies are standardizing data storage on disk arrays.. Data Source: IDC Storage Systems Architecture - Introduction

Key Information Management Challenges
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Key Information Management Challenges Planning for capacity growth Classifying data Address data availability Security Consolidation of data storage into centralized arrays is just a part of overall Information Management. Several challenges have to be addressed such as: Planning for capacity growth: information growth is relentless. With the explosion of data creation, the solutions deployed should be able to keep up with this ever increasing demand. Classifying data: the value of information changes over time. Data and information should be classified according to their value to the business. As we will see later, Storage Arrays come in different types and costs. Classification of data will enable the correct choice of storage array for each class of data. Supporting data availability: information is more strategic than ever. Assuring availability is a key management activity. Storage Systems Architecture - Introduction

Summary Topics covered in this lesson included: Who is creating data and the amount of data being created The value of data to business The challenges in data storage and data management The solutions available for data storage As we have seen, data is created by individuals and businesses and is proliferating and expanding rapidly. And, storage of this valuable business resource needs effective management. Storage Systems Architecture - Introduction

Data Storage Solutions
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Storage Solutions Module 1.2

Data Storage Solutions
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Storage Solutions Upon completion of this module, you will be able to: List the common storage media and solutions. Describe the three common storage environments. Large amounts of data can be stored on hard disks, tapes, and optical disks. Each of these media provides solutions that address specific data storage and retrieval needs. Networked storage comprised of disk arrays and networking components has become the dominant solution for most business data storage needs. In this module, we will look at each of these alternatives with a detailed look at the disk systems and interconnects. Storage Systems Architecture - Introduction

Lesson: Storage Solution Alternatives
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Lesson: Storage Solution Alternatives Upon completion of this lesson, you will be able to: Describe the different media and solutions available to address data storage needs of a business. Describe the role of each solution in the overall data storage needs. Describe the advantages of disk arrays. Internal or external to the server, the options available for storing data are Tape Optical Disks Hard Disks This lesson reviews the various storage media options and discusses the potential uses for each. Storage Systems Architecture - Introduction

Common Data Storage Media
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Common Data Storage Media Tape Library: A collection of tape drives and tapes Jukeboxes: A collection of optical disks and drives Disk Arrays: A collection hard disks Each solution addresses specific needs for data storage and management. Tape Library – Backup/Restore; Archival of data Jukeboxes – Typically to store non-changing content over long periods of time Disk Arrays – To store data that has to be immediately accessible and on-line In the early days of hard disk evolution, tapes provided the primary means of data storage. We have all perhaps seen pictures of computer centers with several tape drives stacked in a row with reels of tapes, and operators busy mounting/unmounting these reels. From being primary data storage solutions, tapes can now be regarded as secondary storage. As the need for storing large amount of data grows, each of these can be combined and housed in central units. Storage Systems Architecture - Introduction

Tape Storage Systems Tape based storage is relatively inexpensive, compared to disk arrays. They served as primary storage solutions in the early days. Tape drives use Read/Write heads to record bits of data onto magnetic material on the tape surface. This technology continues to evolve, providing higher storage capacity, greater reliability, and improved performance. One of the alternatives for storing the large amounts of data found in a typical business is to use magnetic tape. The data is stored on a thin polyester tape coated with magnetic particles. This medium has been used for data storage for over 50 years and has evolved from bulky reel-to-reel systems to smaller, compact cassette (or cartridge) based storage systems with automatic loaders and storage racks. While the formats have changed over time to allow for more data per reel and faster transfers rates, the basic uses of tape systems have remained remarkably constant. Modern tape libraries or silos can have thousands of cartridges and robotics to locate, load, and unload tapes into different drive units in the same frame. Storage Systems Architecture - Introduction

Storing Data on Tape Data is recorded sequentially from the beginning to end, one byte after another. Because data is stored linearly along the length of the tape, random access to specific bits of data is slow and time consuming. This severely limits tape as a medium for real-time, rapid access to data. Tapes cannot be shared among multiple users or applications. Access to, and manipulation of data on tape can be a time consuming process. As data is stored sequentially on tape, random access is not possible. In order to access a file on tape, the tape drive has to wind or rewind it to locate the file. Then the information is read into the computer’s memory. This process takes time. Typically tapes can perform reasonably well if the entire contents from start to finish has to be read from them and written to another location such as a hard disk. This makes them a prevalent low cost solution for backup and archival of data. It is interesting to note that prior to availability of CD-ROM, many vendors of Operating Systems and applications used to ship the software on tape cartridges. Storage Systems Architecture - Introduction

Optical Data Storage Popular in small, single-user computing environments. Frequently used by individuals to store and share data, or as backup solution. Also used as distribution medium for applications, or as a means of transferring small amounts of data from one self-contained system to another. With the emergence of Optical Disks came the advantage of “write-protected” data and random access. Large quantities of these disks were assembled into optical “jukeboxes”, solutions that provided relatively large capacity arrays of this media for centralized network-accessible storage. A single optical disk is still far lower in capacity than a tape or hard disks. Storage Systems Architecture - Introduction

Disk Based Storage From a historical perspective, we will explore the following disk based storage solutions: DASD: Direct Access Storage Device JBOD: “Just a Bunch Of Disks” Disk Arrays “Intelligent” Disk Arrays Disk drives, since their inception, have been the preferred media for storing data. The growth of data demanded larger and larger capacities of these drives leading to the media storage array. An array is capable of serving data to multiple severs concurrently. As data storage needs started exceeding the capacities of individual drives, solutions emerged to make a collection of drives available to either a single server or multiple servers. The components of the modern arrays with built-in intelligence will be discussed in Section 2. Storage Systems Architecture - Introduction

Types of Disk Systems: DASD
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Types of Disk Systems: DASD Mainframe Disk Introduced by IBM in 1956. The ‘oldest’ of the techniques for accessing disks from a host computer. Disks are accessed directly by a single host, historically a mainframe system. DASD – Direct Access Storage Device (Originally introduced by IBM in 1956) is the ‘oldest’ of the techniques for accessing disks from a host computer. Disks are directly accessed from the host (historically a mainframe system) and tightly coupled to the host environment. A hard drive in a personal computer is an example of a DASD system. Typically one can view the DASD as a one-to-one relationship between a server/computer and its disk drive. All access to the data on the disk has to be routed through the server/computer. Prior to the advent of networking technologies, such routing involved submission of a job request to the operators. Whereas the server/computer had direct access to data, the individual did not. In addition to the inconvenience of locating and loading the correct reels/cartridges of tape, DASD disk packs had to be swapped in and out for specific job runs. Despite their slowness, they did offer a faster alternative than tapes. If a disk in the pack failed, all data was lost or at the very least was suspect. Storage Systems Architecture - Introduction

Types of Disk Systems: JBOD
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Types of Disk Systems: JBOD Multiple physical disks in an external cabinet. Array connects to a single server only. Provides higher storage capacity with increased number of drives. Data not protected by JBOD Host Disk JBOD is an acronym for “just a bunch of disks”. The drives in a JBOD array can be independently addressed and accessed by the Server. Array Storage Systems Architecture - Introduction

Types of Disk Systems: Disk Arrays
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Types of Disk Systems: Disk Arrays Array controllers for optimized I/O operations and RAID (Redundant Array of Independent Disks) calculations. Higher speed interconnects between drives than JBODs. Multiple host I/O channels. Can be partitioned to allow each host to access its own set of drives. Host A Host B Host C Disk Array Controller Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 Disk arrays extend the concept of JBODs by improving performance and reliability. They have multiple host I/O ports. This enables connecting multiple hosts to the same disk array. Array management software allows the partitioning or segregation of array resources, so that a disk or group of disks can be allocated to each of the hosts. Typically they have controllers that can perform RAID (Redundant Array of Independent Disks) calculations. Host A Host B Host C Storage Systems Architecture - Introduction

Types of Disk Systems: “Intelligent” Disk Arrays
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Types of Disk Systems: “Intelligent” Disk Arrays Highly optimized for I/O processing. Cache for improving I/O performance. Operating environments provide: Intelligence for managing Cache, Array resource allocation (Logical Unit), Host access to Array resources, Connectivity for heterogeneous Hosts Host A Host B Host C Disk Array Controller Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 Intelligent Disk Arrays have an operating environment. This can be viewed as an “operating system” for the array. They also have large amounts of Cache. Sophisticated algorithms manage Cache to optimize the read/write requests from the Hosts. Large capacity drives can be partitioned or “sliced” into smaller units. These smaller units in turn can be presented to Hosts as individual disk drives. Array management software can also enable multiple hosts to access the array via the same I/O channel. The operating environment ensures that each host can only access the disk resources allocated to it. Storage Systems Architecture - Introduction

Lesson: Summary Topics covered in this lesson included: Tape Optical Disks DASD JBOD Disk Arrays Intelligent Disk Arrays In this lesson, we reviewed the different data storage media options of: Tapes Inexpensive solution (compared to disk) Often used for backup and recovery Optical - Mostly used by individuals Disk DASD – the oldest and ‘most’ traditional disk system JBOD – a collection of disks Arrays – an organized collection of disks Intelligent Arrays – a sophisticated, optimized collection of disks Storage Systems Architecture - Introduction

Lesson: Storage Environment
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Lesson: Storage Environment Upon completion of this lesson, you will be able to: Describe Direct Attached Storage (DAS) features. Describe Storage Area Network (SAN) features. Describe Network Attached Storage (NAS) features. There are different types of Storage Environments: DAS – Direct Attached Storage Networked Storage: Storage Area Network – SAN Network Attached Storage – NAS Storage Systems Architecture - Introduction

Direct Attached Storage – DAS
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Direct Attached Storage – DAS Server A Application A Client 1 Disks for Server A SCSI Local Area Network Disks for Server B Client 2 Server B Application B Disks for Server C In a Direct Attached Storage (DAS) environment, servers connect directly to the disk array typically via a SCSI interface. The same connectivity port on the Disk array cannot be shared between multiple servers. Clients connect to the Servers through the Local Area Network The distance between the Server and the Disk array is governed by the SCSI limitations. With the advent of Storage Area Networks and Fibre Channel interface, this method of Disk array access is becoming less prevalent. Client 3 Server C Application C Storage Systems Architecture - Introduction

Network Attached Storage – NAS
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Network Attached Storage – NAS Server A File System A Linux Client 1 NAS Device A File System A Disks for File System A Local Area Network Internal/External connectivity to disks or arrays Client 2 NAS Device B File System B Disks for File System B In a Network Attached Storage (NAS) environment, NAS Devices access the disks in an array via direct connection or through external connectivity. The NAS heads are optimized for file serving. They are setup to export/share file systems. Servers called NAS clients access these file systems over the Local Area Network (LAN) to run applications. The clients connect to these servers also over the LAN. Client 3 Windows Server B File System B Storage Systems Architecture - Introduction

Storage Area Network – SAN
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Storage Area Network – SAN Server A Application A Client 1 Disks for Server A Data Block Fibre Channel Local Area Network SAN FC Switch Disks for Server B Client 2 Server B Application B Disks for Server C In a Storage Area Network (SAN) environment, servers access the disk array through a dedicated network designated as SAN in the slide. SAN consists of Fibre Channel switches that provide connectivity between the servers and the disk array. In this model, multiple servers can access the same Fibre Channel port on the disk array. The distance between the server and the disk array can also be greater than that permitted in a direct attached SCSI environment. Clients communicate with the servers over the Local Area Network (LAN). Client 3 Disk Array Server C Application C Storage Systems Architecture - Introduction

Lesson: Summary Topics covered in this lesson included: Direct Attached Storage (DAS) features. Network Attached Storage (NAS) features. Storage Area Network (SAN) features. Differences: Connectivity In this lesson we looked at the different models for connecting storage devices including: Direct Attached Storage (DAS) – a single computer connection Network Attached Storage (NAS) – for multiple (possibly different OS) hosts and file system data Storage Area Networks (SAN) – high speed channel, with multiple hosts, and an intelligent storage controller. Storage Systems Architecture - Introduction

Module Summary Key points covered in this module: The three types of data storage media. The three storage environments. This module described The three common data storage media types include: Tapes Optical disks Hard disks The four common hard disk systems include: DASD JBOD Array Intelligent Arrays The three models used to connect disks to computers include: DAS NAS SAN Storage Systems Architecture - Introduction

 Check Your Knowledge What are the three most common storage media? What are the three types of disk-based solutions? What are the advantages of a disk-based storage solution? What are the three storage environments? Storage Systems Architecture - Introduction

Data Center Infrastructure
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Center Infrastructure Module 1.3 Computing Center  Data Center

Data Center Infrastructure
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Data Center Infrastructure Upon completion of this module, you will be able to: List the five core elements of a Data Center infrastructure. Describe the role of each element in supporting business activities. Describe the requirements of storage systems for optimally supporting business activities. Describe the challenges and activities in managing the storage systems of a data center. So far, we’ve looked at The importance of data and information to the business (competitive advantage). The proliferation of data that needs to be stored efficiently. The storage alternatives (tape, optical and disk). Disk solutions (DASD, JBOD) and Interconnected disk systems (DAS, NAS, SAN). Now, we will discuss the elements of the Data Center and the challenges of managing a complex storage systems environment. Storage Systems Architecture - Introduction

The Core Elements Applications Databases – Database Management System (DBMS) and the physical and logical storage of data Servers/Operating Systems Networks (between clients and servers or between servers and storage) Storage Arrays The five core elements include: Applications – specialized and dedicated software to manipulate data typically stored in databases. Databases – more commonly, Database Management Systems (DBMS), provide a structured way of storing data in logically organized tables with an interrelation between them. They optimize the storage and retrieval of data. Servers/Operating Systems – provide the computing platform required to run the applications and databases. Networks – provide the data communication paths between clients and servers or between servers and storage. Storage Arrays – this is where data and information lives. Storage Systems Architecture - Introduction

An Example: order entry system
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. An Example: order entry system Storage Array Server Client Storage Area Network Local Area Network Application User Interface Database Consider an order processing system consisting of: Application for order entry. Database Management System (DBMS) to store customer and product information. Server/Operating System on which the Application and Database programs are run. Networks that provide Connectivity between Clients and the Application/Database Server Connectivity between the Server and the Storage system. Storage Array. This example identifies the 5 core elements of a data center and how they may relate to an actual business activity. Storage Systems Architecture - Introduction

An Example ..Closer Look Storage Array Server Client Storage Area Network Local Area Network Application User Interface A customer order is entered via the Application User Interface on a client. A customer order is entered via the Application User Interface, typically from a Client machine on the order processing personnel’s desk. An Application accesses the Database to update the relevant information – Customer name/address/payment method, products ordered, quantity ordered etc. Storage Systems Architecture - Introduction

An Example ..Closer Look Storage Array Server Client Storage Area Network Local Area Network A customer order is entered via the Application User Interface on a client The client accesses the Server over a Local Area Network. A customer order is entered via the Application User Interface, typically from a Client machine on the order processing personnel’s desk. The client accesses the Server over a Local Area Network. Storage Systems Architecture - Introduction

An Example ..Closer Look Storage Array Server Client Storage Area Network Local Area Network O/S and DBMS A DBMS uses the operating system on the server to read and write this data to the physical location on a disk. A DBMS uses the Operating System to read and write this data to the physical location on a disk. A Network provides the communication link between the Client and the server, and transports the read/write commands and data between the Server and the Storage Array. A Storage Array receives the read/write commands and data from the Server and performs the necessary operations to store the data on physical disks. Storage Systems Architecture - Introduction

An Example ..Closer Look Storage Array Server Client Storage Area Network Local Area Network A DBMS uses the operating system on the server to read and write this data to the physical location on disk. A Network provides the communication link between the server and the storage array, and transports the read/write commands and data between the server and the storage array. A DBMS uses the Operating System to read and write this data to the physical location on disk. A Network provides the communication link between the Client and the server, and transports the read/write commands and data between the Server and the Storage Array. A Storage Array receives the read/write commands and data from the Server and performs the necessary operations to store the data on physical disks. Storage Systems Architecture - Introduction

An Example ..Closer Look Storage Array Server Client Storage Area Network Local Area Network Database A DBMS uses the operating system on the server to read and write this data to the physical location on disk. A Network provides the communication link between the client and the server, and transports the read/write commands and data between the server and the storage array. A storage array receives the read/write commands and data from the server and performs the necessary operations to store the data on the physical disks. A DBMS uses the Operating System to read and write this data to the physical location on disk. A Network provides the communication link between the Client and the server, and transports the read/write commands and data between the Server and the Storage Array. A Storage Array receives the read/write commands and data from the Server and performs the necessary operations to store the data on the physical disks. Storage Systems Architecture - Introduction

An Example.. Optimal Order Processing
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. An Example.. Optimal Order Processing The Application should be optimized for fast interaction with the DBMS. The tables in the Database should be constructed with care so that the number of read/write operations can be minimized. The Server should have sufficient CPU and memory resources to satisfy Application and DBMS needs. The Networks should provide fast communication between Client and Server, as well as Server and Storage Array. The Storage Array should service the read/write requests from the Server for optimal performance. If any one of the five elements is not available, the order entry process cannot be completed. For example, if the data is not available due to a disk failure, the order cannot be completed. The speed with which the order entry process can be completed depends on optimizing each of the five elements. Storage Systems Architecture - Introduction

An Example.. A Final Look at Data Access
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. An Example.. A Final Look at Data Access When the DBMS receives a request from the Application: It first searches the Server memory. If data is found there, the operation takes, perhaps, a millisecond. If not, it then uses the Operating System to request the data from the Storage Array. Dedicated high speed networks transport this request to the Storage Array. Intelligent Storage Arrays can deliver the requested data within a few milliseconds. They are also typically configured to protect data in the event of drive failures. Storage Systems Architecture - Introduction

Key Requirements of (Intelligent) Storage Systems
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Key Requirements of (Intelligent) Storage Systems Availability Data Integrity Security Capacity Scalability Performance Manageability Downtime per year 99.%=3.7days 99.9%=9hours 99.99%=53minutes 99.999%=5minutes I/O chain checks Authorized users Flexible to configure and monitor the storage system. Physically relocate or logically reassign resources to supporting different critical business needs. (DBMS) Meeting user expectations for timeliness and response to I/O requests. More server, one storage array While the requirements listed here are applicable to all elements of the Data Center Infrastructure, our focus is on Storage Systems. This course explores how Intelligent Storage Arrays meet these critical requirements. The various techniques and technology solutions to ensure these requirements are met will be extensively examined later in the class. Availability – ensure that data is accessible at all times when needed. As seen earlier, loss of access to data can have significant financial impact on businesses. Security – prevent unauthorized access to data. Mechanisms to allow servers to access only their allocated resources on Storage Arrays. Capacity – ability to add storage capacity “on-demand”, without interruption to the business. If a Database runs out of space on physical storage, it comes to a halt, thus impacting the business. Scalability – The Storage solution should be able to grow with the business. As the business grows, more Servers will be deployed, new applications/databases will be developed. Note: Continued on next page… Smoothly increase or decrease resources (apps, DB, server, storage) as needed (business grow). Applicable to all elements of the Data Center Infrastructure. They are qualities that must exist for successful use of data. Storage Systems Architecture - Introduction

Some Constraints to Meeting the Requirements
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Some Constraints to Meeting the Requirements Constraints include: Cost : the budget Physical Environment: the site Maintenance and Support: human resource Compliance – Regulatory & Legal: the business rule Hardware and Software infrastructure Interoperability and Compatibility The requirements are ‘tempered’ by the reality of business. These constraints put pressure on achieving the technology requirements. Storage Systems Architecture - Introduction

Management Activities
Copyright © 2006 EMC Corporation. Do not Copy - All Rights Reserved. Management Activities Data Center management activities include: Provisioning / Capacity Planning / Resource Planning Monitoring Reporting These activities are relevant to all elements of a Data Center Infrastructure. Our focus is on Storage systems and the Storage environment. Managing a modern, complex Storage environment involves many tasks. Key management activities include: Provisioning/Capacity/Resource Planning Monitoring Reporting These activities are interdependent. For example one has to monitor the utilization of storage space of a database. When the utilization reaches a critical value, more capacity has to be added or provisioned. Reports on utilization will help in understanding the business growth and anticipate future capacity requirements. The objective is to be predictive and proactive rather than reactive. Storage Systems Architecture - Introduction

Monitoring Performance Security Data Protection Utilization Attempts and types of intrusions Data transfers or transactions per minute Hardware errors that are detected and corrected Numbers of users and resource use (CPU, Memory, Storage) Network traffic Continuous monitoring is critical to ensure uninterrupted business activities. Performance – monitoring the performance of the array will help in identifying bottlenecks in the I/O chain. It gives clues for better data layout to improve performance. Security – ensure that unauthorized access of devices is not taking place. Proper security measures will leave an audit trail of any changes to the configuration and will ensure that only authorized users are performing the configuration changes. Data Protection – ensure that the data is continually protected. Monitor drive failures or other component failures. Utilization – if any component in the I/O chain reaches a saturation point, application response times will slow down. Adding new applications or servers when the existing components are already saturated will slow everybody down. Storage Systems Architecture - Introduction

Reporting Utilization Performance Reports help in trend analysis. For example, periodic reporting on disk space utilization enables predicting storage capacity requirements in the future. Many organizations use reporting as a chargeback system to recover cost of providing IT infrastructure services to their internal customers. In turn, the users may be held accountable for the resources they consume. Storage Systems Architecture - Introduction

Provisioning: provide the hardware, software and resources needed to run the Data Center Buy hardware Buy software Installing hardware and software Training resources Performance tuning the interrelated system With the data available from Monitoring and Reporting activities, data center managers can reserve required resources to meet anticipated growth. These also help in justifying budgetary levels for ongoing data center operations. Storage Systems Architecture - Introduction

Capacity Planning Understanding the business model – helps estimate the growth and support needs for the business. Understanding the business will help anticipate the data needs and growth in data capacity requirements. Understanding the data life cycle for the business – helps identify the various stages of data in the business, requirements for migrating data to archived backup, and anticipate or plan for the increasing capacity needs. Understanding changes in storage technology – ability to introduce new and more efficient storage methods to meet future capacity needs and manage costs. Storage Systems Architecture - Introduction

Resource Planning Understanding the procedures and tasks in the data center. Changes in policy, procedures, or business needs. Availability of qualified candidates. Ability to train data center resources. Sufficient budget to supply staff 24 X 7. Storage Systems Architecture - Introduction

Module Summary Key points covered in this module: The five core elements of a Data Center Infrastructure. The role of each element in supporting business activity was explained with an example of an order entry process. The importance of an Intelligent Storage Array. Key requirements of storage systems to support business activities as well as some of the constraints. Management activities in a data center operation with focus on storage systems. This module described: The five core elements of a Data Center Infrastructure including: Applications Databases Operating Systems Networks Storage The role of each element in supporting business activity was explained with an example of an order entry process. The importance of an Intelligent Storage Array was explained in the context of High-speed servicing of I/O requests from the Server Protecting data in the event of disk failures Seven key requirements of storage systems to support business activities as well as some of the constraints. Management activities in a data center operation with focus on storage systems: Provisioning/Capacity Planning/Resource Planning Monitoring Reporting Storage Systems Architecture - Introduction

 Check Your Knowledge What are the five core technology elements of the Data Center Infrastructure? What are the seven requirements of storage technology? What are the common management activities in a Data Center? Storage Systems Architecture - Introduction

Who is the industry leader?
Major companies (IBM, HP, Sun, Microsoft, Hitachi, EMC, Network appliance, even Cisco) are competing for storage market! Storage Systems Architecture - Introduction

Meeting Today’s Data Storage Needs

Similar presentations

Presentation on theme: "Meeting Today’s Data Storage Needs"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Meeting Today’s Data Storage Needs

Similar presentations

Presentation on theme: "Meeting Today’s Data Storage Needs"— Presentation transcript:

Similar presentations

About project

Feedback