Virtualization Changes Storage
Download as PPTX, PDF0 likes726 views
Virtualization changes storage in three key ways: 1) I/O is concentrated on fewer ports and randomized across physical disks. 2) Storage utilization is low due to abstraction overhead. 3) Options include shared storage on SAN/NAS, raw device mapping, or NFS with pros and cons for each. Effective virtualized storage requires balancing these changes.
Virtualization Changes Storage
- 1. How Does Virtualization Change Storage?May 18, 2009Stephen Foskett, Director of Consulting, Nirvanix
- 2. AbstractThe virtualization of servers destroys everything that storage folks thought they knew about I/O and throws in a new layer of abstraction to bootCreating storage for virtualization is not the same as storage for most other apps, and storage virtual servers on a SAN or NAS is not the same as using internal diskThis session will walk through what virtualization changes about storage, the various storage options, pros and cons, and what the future looks like with FCoE, UCS, 10 GbE, and VMware vStorage APIs2
- 3. Server Virtualization RecoilThe server virtualization revolution has challenged storage in many ways:
- 5. Impact on storage capacity utilization
- 6. Architecture decisions to be made: DAS, SAN, NAS
- 7. Trouble for traditional backup, replication, reporting
- 8. Biggest issue: Converged technology leads to converged management organizationsPillars of Virtual Machine Performance4ProcessorI/O (disk/net)MemoryVirtual machine performance demands a balanced base of processing, I/O subsystem, and memory performance, capability, and capacity
- 9. Virtualization As An I/O EngineServer virtualization is the single greatest I/O driver in the modern data centerCPU power and memory capacity are easy to ramp up, I/O is notUnbalanced systems will not perform well5
- 10. I/O Is ConcentratedThen…Each server had its own storage and LAN portsI/O utilization was lowNow…6All I/O is concentrated on just a few portsLANSANLANSAN
- 11. I/O is RandomizedThen…Now…Sequential I/O is mixed together randomlyDisk is virtualized and re-combined7I/O was mainly sequentialRequests were grouped physically on diskStorage could read ahead and cache data
- 12. I/O is AcceleratedThen…Now…Combined I/OPackets arrive quicklyQuicker protocols: 10 GbE, 8 Gb FC8Channels were under-utilized with little contention for resourcesSpeeds were low: 1 GbE, IDE/ATAIn the same amount of time…1 GbE handles 1 packet from 1 host...4 Gb FC handles 4 packets from 4 hosts...8 Gb FC handles 8 packets from 5 hosts...10 GbE handles 10 packets from all 6 hosts...
- 13. Converged Data Center I/ONow…All I/O is concentrated on just a few portsSoon…9I/O is converged on 10GbE and extended into server hardwareLANSANLANSAN
- 14. Server Virtualization and Storage Utilization
- 15. Wasted SpaceEach level of abstraction adds overheadOverall utilization is low!11Raw array capacityUsable array capacityLUNs presented to hostConfigured datastoreServer 1 virtual diskServer 2 virtual diskServer 3 virtual diskServer 1 used capacityServer 3 used capacityServer 3 used capacity
- 16. Thin ProvisioningThin provisioning allocates storage as-neededExample: 500 GB request for new project, but only 2 GB of initial data is written – array only allocates 2 GB and expands as data is writtenWhat’s not to love?Oops – we provisioned a petabyte and ran out of storageChunk sizes and formatting conflictsCan it thin unprovision?Can it replicate to and from thin provisioned volumes?VMware adding thin provisioning to vSphere 4 (standard at all license levels!)Some storage arrays do thin (3PAR, HDS, NetApp)12
- 17. Server Virtualization Demands SAN and NASServer virtualization has transformed the data center and storage requirements86% have implemented some server virtualization (ESG 2008)VMware is the #1 driver of SAN adoption today!60% of virtual server storage is on SAN or NAS (ESG 2008)Server virtualization has enabled and demanded centralization and sharing of storage on arrays like never before!
- 18. VMware Storage Options:Shared StorageShared storage - the common/ workstation approachStores VMDK image in VMFS datastoresDAS or FC/iSCSI SANHyper-V VHD is similarWhy?Traditional, familiar, common (~90%)Prime features (Storage VMotion, etc)Multipathing, load balancing, failover*But…Overhead of two storage stacks (5-8%)Harder to leverage storage featuresOften shares storage LUN and queueDifficult storage managementVMHostGuestOSVMFSVMDKDAS or SANStorage
- 19. VMware Storage Options:Shared Storage on NFSShared storage on NFS – skip VMFS and use NASNTFS is the datastoreWow!Simple – no SANMultiple queuesFlexible (on-the-fly changes)Simple snap and replicate*Enables full VmotionUse fixed LACP for trunkingBut…Less familiar (3.0+)CPU load questionsDefault limited to 8 NFS datastoresWill multi-VMDK snaps be consistent?VMHostGuestOSNFSStorageVMDK
- 20. VMware Storage Options:Raw Device Mapping (RDM)Raw device mapping (RDM) - guest VM’s access storage directly over iSCSI or FCVM’s can even boot from raw devicesHyper-V pass-through LUN is similarGreat!Per-server queues for performanceEasier measurementThe only method for clusteringBut…Tricky VMotion and DRSNo storage VMotionMore management overheadLimited to 256 LUNs per data centerVMHostGuestOSI/OMapping FileSAN Storage
- 21. Which VMware Storage Method Performs Best?Mixed Random I/OCPU Cost Per I/OVMFS,RDM (p), or RDM (v)Source: “Performance Characterization of VMFS and RDM Using a SAN”, VMware Inc., 2008
- 22. Which Storage Protocol Performs Best?Throughput by I/O SizeCPU Cost Per I/OFibre Channel,NFS,iSCSI (sw),iSCSI (TOE)Source: “Comparison of Storage Protocol Performance”, VMware Inc., 2008And iSCSI is even better in vSphere 4!
- 24. Which Storage Protocol is For You?FC, iSCSI, NFS all work wellMost production VM data is on FCEither/or? - 50% use a combination (ESG 2008)Leverage what you have and are familiar withFor IP storageUse TOE cards/iSCSI HBAsUse a separate network or VLANIs your switch backplane fast?No VM Cluster support with iSCSI*For FC storage4 Gb FC is awesome for VM’sGet NPIV (if you can)FCoE is the futureConverged storage and networks adapters (CNAs)Cisco UCS
- 25. Storage in VMware vSphere 4Thin provisioning is standard for all levelsDynamic expansion of VMFS volumesAny-to-any Storage VmotionHigh performance I/OParavirtualized SCSIEnhanced iSCSI stackJumbo framesData Protection APIs (A)Pluggable Storage multipathing (E+)21
- 26. The Organizational ChallengeHow will server, storage, and networking teams deal with integration?Each discipline has its own best practicesEach has its own prejudicesThey can be forced together, but will it work?22
- 27. Who Is Nirvanix23The Premier “Cloud Storage” Service Provider for the Enterprise Backed by Intel Capital, Mission Ventures, Valhalla Partners, Windward Ventures and European Founders Fund2007 “Storage Products of the Year”2008 “Top Startups to Watch”2008 “Product of the Year”Over 500 customers including leading Fortune 10, Media & Entertainment and Web 2.0 companies
- 28. 24Thank YouNirvanixWe manage your storage, so you can manage your businesswww.nirvanix.comtwitter.com/nirvanixStephen Foskettsfoskett@nirvanix.comEnterprise Storage Strategies Blog: bit.ly/ESSBlogPersonal Blog: blog.fosketts.netEnterprise IT Content: gestaltit.com
Editor's Notes
- #15: Up to 256 FC or iSCSI LUNsESX multipathingLoad balancingFailoverFailover between FC and iSCSI*Beware of block sizes greater than 256 KB!If you want virtual disks greater than 256 GB, you must use a VMFS block size larger than 1 MBAlign your virtual disk starting offset to your array (by booting the VM and using diskpart, Windows PE, or UNIX fdisk)*
- #16: Link Aggregate Control Protocol (LACP) for trunking/EtherChannel - Use “fixed” path policy, not LRUUp to 8 (or 32) NFS mount pointsTurn off access time updatesThin provisioning? Turn on AutoSize and watch out