360 likes | 598 Views
Section 2 : Storage Networking Technologies and Virtualization. Storage Virtualization. Chapter 10. Chapter Objectives. Upon completion of this chapter, you will be able to: Identify different virtualization technologies Describe block-level virtualization technologies
E N D
Section 2 : Storage Networking Technologies and Virtualization Storage Virtualization Chapter 10
Chapter Objectives Upon completion of this chapter, you will be able to: • Identify different virtualization technologies • Describe block-level virtualization technologies • Describe file-level virtualization technologies • Discuss virtual provisioning
Lesson –Virtualization Overview Upon completion of this lesson, you will be able to: • Identify and discuss virtualization technologies
What is Virtualization • Virtualization is a technique of abstracting physical resources into logical view • Increases utilization and capability of IT resource • Simplifies resource management by pooling and sharing resources • Significantly reduce downtime • Planned and unplanned • Improved performance of IT resources
Virtualization Comes in Many Forms Each application sees its own logical memory, independent of physical memory Virtual Memory Each application sees its own logical network, independent of physical network Virtual Networks Each application sees its own logical server, independent of physical servers Virtual Servers Each application sees its own logical storage, independent of physical storage Virtual Storage 6
Each application sees its own logical memory, independent of physical memory Virtual Memory Memory Virtualization Physical memory App App App Benefits of Virtual Memory • Remove physical-memory limits • Run multiple applications at once Swap space 7
Network Virtualization Each application sees its own logical network, independent of physical network Virtual Networks VLAN A VLAN B VLAN C Benefits of Virtual Networks • Common network links with access-control properties of separate links • Manage logical networks instead of physical networks • Virtual SANs provide similar benefits for storage-area networks Switch Switch VLAN trunk 8
Before Server Virtualization: After Server Virtualization: Operating system Operating system App App App App App App Operating system Virtualization layer Application • Single operating system image per machine • Software and hardware tightly coupled • Running multiple applications on same machine often creates conflict • Underutilized resources • Virtual Machines (VMs) break dependencies between operating system and hardware • Manage operating system and application as single unit by encapsulating them into VMs • Strong fault and security isolation • Hardware-independent Server Virtualization
Storage Virtualization Servers • Process of presenting a logical view of physical storage resources to hosts • Logical storage appears and behaves as physical storage directly connected to host • Examples of storage virtualization are: • Host-based volume management • LUN creation • Tape virtualization • Benefits of storage virtualization: • Increased storage utilization • Adding or deleting storage without affecting application’s availability • Non-disruptive data migration Virtualization Layer Heterogeneous Physical Storage
Lesson Summary Key topics covered in this lesson: • Various forms of virtualization • Memory, network, server and storage virtualization Additional Task Research on Virtual LAN & Virtual SAN
Lesson – Storage Virtualization Implementation Upon completion of this lesson, you will be able to: • Discuss SNIA virtualization taxonomy • Describe Block-Level Virtualization technologies and implementation • Describe File Level Virtualization technologies and implementation
Storage Virtualization What is created Tape, Tape Drive, File System, Block Disk Other Device Tape Library File/record Virtualization Virtualization Virtualization Virtualization Virtualization Where it is done Host Based Network Storage Device/Storage Virtualization Based Virtualization Subsystem Virtualization How it is implemented In-band Out-of-band Virtualization Virtualization SNIA Storage Virtualization Taxonomy
Storage Virtualization Requires a Multi-Level Approach Path management Server Volume management Replication Storage Path redirection Network Load balancing - ISL trucking Access control - Zoning Volume management - LUNs Access control Storage Replication RAID
Servers Servers Virtualization Virtualization Appliance Appliance Storage Network Storage Network Storage Storage Arrays Arrays Out-of-Band In-Band (a) (b) Storage Virtualization Configuration
Storage Virtualization Configuration • Out-of-band implementation • Virtualized environment configuration is stored external to the data path • Virtualization appliance is hardware-based and optimized for fibre channel • Enables data to be processed at network speed • More scalable • In-band implementation • Virtualization function is placed in the data path • Virtualization appliance is software-based and runs on general-purpose servers • During processing, data storing and forwarding through the appliance results in additional latency • Less scalable – only suitable for static environment with predictable workloads
Storage Virtualization Challenges • Scalability • Without virtualization, each storage array is managed independently to meet application requirements in terms of capacity and IOPS • With virtualization, the environment as a whole must be analyzed • Functionality • Virtualized environment must provide same or better functionality • Must continue to leverage existing functionality on arrays • Manageability • Virtualization device breaks end-to-end view of storage infrastructure • Must integrate with existing management tools • Support • Interoperability in multivendor environment
Servers Virtualization Applied at SAN Level Heterogeneous Storage Arrays Block-Level Storage Virtualization • Ties together multiple independent storage arrays • Presented to host as a single storage device • Hosts are directed to virtualized volumes on the virtualization device • Mapping is done to redirect I/O on this virtual storage device to underlying physical arrays • Deployed in a SAN environment • Non-disruptive data mobility and data migration • Enable significant cost and resource optimization
Before File-Level Virtualization After File-Level Virtualization Clients Clients Clients Clients IP IP Network Network Virtualization Appliance File File File File Server Server Server Storage Server Storage Array Array NAS Devices/Platforms NAS Devices/Platforms • Break dependencies between end-user access and data location • Storage utilization is optimized • Nondisruptive migrations • Every NAS device is an independent entity, physically and logically • Underutilized storage resources • Downtime caused by data migrations File-Level Virtualization
Lesson: Summary Key points covered in this lesson: • Storage virtualization challenges • Storage virtualization configuration • Types of storage virtualization Additional Task Research on Global File Virtualization
Lesson: Virtual Provisioning Upon completion of this lesson, you will be able to: • Explain Virtual Provisioning • Describe and explain Thin vs. Traditional LUNs • Explain the benefits of Virtual Provisioning • Explain how to create, monitor, and manage Thin LUNs
Host Reported Capacity Allocated Allocated Allocated What is Virtual Provisioning • Capacity-on-demand from a shared storage pool • Logical units presented to hosts have more capacity than physically allocated (thin provisioning) • Physical storage is allocated only when the host requires it • Provisioning decisions not bound by currently available storage • Above and beyond “Thin Provisioning” • Includes management tools that make it easier to configure, use, monitor and manage Thin Pools and Thin LUNs Shared Storage Pool Storage perceived by the application is larger than physically allocated storage
Traditional Provisioning Traditional Provisioning vs. Virtual Provisioning 1650 GB Or 1.65 TB Available Capacity 350 GB Actual Data LUN 1 LUN 3 LUN 2 Storage System Virtual Provisioning
Virtual Provisioning – Benefits • Reduce administrative costs • Simplifies storage provisioning • Over-provisioning can eliminate challenges of expansion • Reduces time required to repeatedly add storage capacity • Reduce storage costs • Increased space efficiency for primary storage and replicas • “Storage on demand” from shared storage pool • Deploy assets as needed • Reduce levels of unused physical storage • Avoid pre-allocating physical storage to applications • Reduce operating costs • Fewer disks consume less power, cooling and floor space • Reduce downtime • Less disruptive to applications
“Test & Dev Pool 2” Additional Disk Drives Virtual Provisioning – Thin Pool Expansion • Adding drives to the pool non-disruptively increases available shared capacity for all Thin LUNs in pool • Drives can be added to a Thin Pool while pool is being used in production • Allocated capacity is reclaimed by the pool when Thin LUNs are deleted
Use RAID Groups and traditional LUNs When microseconds of performance matters For the best and most predictable performance For precise data placement You are not as concerned about space efficiency Use Virtual Provisioning with Thin Pools and Thin LUNs When the best space efficiency is needed For minimal host impact When energy and capital savings are paramount For applications where space consumption is difficult to forecast Traditional vs. Thin LUNs
Lesson Summary Key points covered in this module: • Virtual Provisioning • Thin vs. Traditional LUNs • Benefits of Virtual Provisioning
Chapter Summary Key points covered in this chapter: • Virtualization technologies and forms • SNIA storage virtualization taxonomy • Storage virtualization configuration • Storage virtualization challenges • Types of storage virtualization • Virtual provisioning overview
Challenges with Traditional Storage Approach • Not designed to scale in the multi-petabyte • Addition of new arrays for capacity enhancement • Cost and management overhead • Increased time to market • Can address transactional and distributed computing • But fell short for Internet Era requirements • Designed for Operation Within IT’s Walls
Cloud Storage Infrastructure: The Big Picture • To deal with Internet Era data growth • A massively scalable infrastructure is required • One that offers global data distribution, self-healing, self-management, and multi-tenancy features • A Cloud approach to storage • A cost effective approach to handling Internet Era data growth • Focusing on five key infrastructure requirements • Infinite Scale • No Boundaries • Operationally Efficient • Self-Management • Self-Healing
Use of Cloud Computing Resources • “Cloud computing” takes hold as 69% of all Internet users have either stored data online or used a web-based software application Source: “Use of Cloud Computing Applications and Services”, Pew Internet & American Life Project, 9/12/2008
Defining Cloud Computing “Cloud Computing is an emerging IT development, deployment and delivery model, enabling real-time delivery of products, services and solutions over the Internet (i.e. enabling cloud services)” • Services include • Software-as-a-Service (SaaS) • Storage-as-a-Service (Staas) • Computing-as-a-Service (CaaS) • Platform-as-a-Service (PaaS) / Infrastructure-as-a-Service (IaaS) • Examples: • Amazon: Elastic Compute Cloud (EC2), Simple Storage Services (S3) • Storage Cloud – Dropbox, Google Drive, SugarSync, Skydrive, Box.net, SpiderOak, iDrive, Ubuntu One, etc… • Google Apps • Salesforce.com – provide CRM (customer relationship management) product
In cloud execution Offsite, provided by third-party Accessed via Internet Not bound to corporate/private network Minimal/no IT skills to “implement” Users need not have expertise Provisioning Self-requesting Pricing Fine-grained & usage-based pricing capability Similar to other utilities such as electricity and water User Interface Simple, not tied to any specific device/platform System Interface Web based standard framework Shared resources Shared asset approach Cloud Services:
Cloud Applications • Enterprise Solutions • Transactional data or high performance file sharing applications • Example: Amazon EC2 • Cloud storage infrastructure • Example: EMC Atmos • End-user Solutions • Rich Internet applications and online service providers • Examples: Social media sites, Online photo sharing • Online data backup • Example: iDrive Additional Task Research on Cloud Storage & EMC Atmos
#1 IT company For more information visit http://education.EMC.com