What’s New in VMware vSphere 5.0 – Storage€¦ · What’s New in VMware vSphere 5.0 – Storage Introduction VMware vSphere™ 5.0 (“vSphere”) brings many new capabilities

What’s New in VMware vSphere™ 5.0 – StorageT E C H N I C A L M A R K E T I N G D O C U M E N TAT I O N v 1 . 0 / U p D AT E D M Ay 2 0 1 1

What’s New in VMware vSphere 5.0 – Storage

T E C H N I C A L W H I T E p A p E R / 2

Table of Contents

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

vSphere VMFS-5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

vSphere Storage DRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Datastore Clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

Placement Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Affinity Rules and Maintenance Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6

vSphere Storage APIs – Storage Awareness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Profile-Driven Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

Virtual Machine Compliance Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Fibre Channel over Ethernet Software Initiator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

iSCSI Initiator Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

vSphere Storage I/O Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

vSphere Storage APIs – Array Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

vSphere Thin Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

Hardware Acceleration for NAS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

T10 Compliancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

vSphere Storage vMotion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15



IntroductionVMware vSphere™ 5.0 (“vSphere”) brings many new capabilities to extend the benefits of vSphere 4.1. These new features and enhancements to core capabilities in vSphere provide more performance optimization and easier provisioning, monitoring and troubleshooting. This paper focuses on the storage-specific features and enhancements that are available in vSphere 5.0 and provides an overview of how they optimize storage utilization, ease monitoring, and increase operational efficiency. Wherever possible, we will also provide use cases and requirements that might apply to these new functions.

The topics to be covered in this paper are:

•vSphere®VMFS-5

•vSphere®StorageDistributedResourceScheduler(StorageDRS)

•vSphere®StorageAPIs-StorageAwareness

•Profile-DrivenStorage

•FibreChanneloverEthernet

•vSphere®StorageI/OControl(StorageI/OControl)

•vSphere®StorageAPIs–ArrayIntegration

•vSphere®StoragevMotion®(StoragevMotion)

This will provide a technical overview of new capabilities and enhancements as well as links to additional information about each of these new storage features.

vSphere VMFS-5vSphere5.0introducesanewversionofvSphereVMFS(VMFS),VMFS-5,whichcontainsmanyimportantarchitecturalchangesthatenablegreaterscalabilityandperformancewhilereducingcomplexity.Althoughnumerous fundamental changes have been made, the following enhancements are significant from operational and architectural aspects:

•64TBdevicesupport

•Unifiedblocksize

•Improvedsubblockmechanism

vSphere5.0facilitatesanondisruptiveupgradefromVMFS-3toVMFS-5,ensuringconsistencyacrossvirtualinfrastructures.Theunifiedblocksize,1MB,enableseasierdeploymentsandreducedcomplexityfromanarchitectural and operational aspect while maintaining the scalability and the flexibility that were previously foundonlywithlargeblocksizes.ItshouldbenotedthatvolumesthatareupgradedfromVMFS-3toVMFS-5will retain their original block size, because modifying the block size would require a reformat of the volume. To enable greater scalability and reduce storage overhead associated with small files, various enhancements have beenmadetoVMFS-5.Theseenhancementsincludeoptimizedsubblocksizesandtheallocationoftheseblocks.Theyhaveresultedinsupportforlargevolumes(64TBonasingleextent)andhighervirtualmachinedensitywhilereducingtheoverheadassociatedwithsmallfiles.VMFS-5iscapableofallocating30.000subblocksof8KBforfilessuchaslogfilesandvirtualmachinemetadata(.vmxfiles).Forfileswithasizesmallerthan1KB,“smallfileblocks”areused.ThefollowingtabledepictsthemostsignificantarchitecturalchangesforVMFS-5incomparisontoVMFS-3.



Feature VMFS-3 VMFS-5

Supportforlargersingle-extentVMFSvolumesupto64TB No Yes

Supportforpass-throughRDMslargerthan2TB No Yes

Subblock for space efficiency Yes(64KB,maximum of approx.3K)

Yes(8KBmaximum of approx.30K)

Small-file support No Yes(1KB)

Unifiedblocksize No Yes

Table 1. VMFS-5 to VMFS-3 Comparison

vSphere Storage DrSVirtual machine provisioning has always imposed operational challenges. Monitoring datastore capacity and I/Oloadhasproventobeverydifficultandasaresultisoftenneglected.Duringtheprovisioningprocessofvirtual machines and virtual disks, datastores are often randomly selected, leading to hot spots and over- or underutilizeddatastores.StorageDRSisanewfeatureintroducedinvSphere5.0.ItprovidessmartvirtualmachineplacementandloadbalancingmechanismsbasedonI/Oandspacecapacity.StorageDRSwillhelpdecrease operational effort associated with the provisioning of virtual machines and the monitoring of the storage environment.

Datastore ClustersWithvSphere5.0,anewVMwarevCenter™objectcalledadatastoreclusterisintroduced.DatastoreclustersformthebasisofStorageDRS.Adatastoreclusterisacollectionofdatastoresaggregatedintoasingleunitofconsumptionfromanadministrator’sperspective.Whenadatastoreclusteriscreated,StorageDRScanmanagethestorageresourcescomparablytohowStorageDRSmanagescomputeresourcesinacluster.Aswith a cluster of hosts, a datastore cluster is used to aggregate storage resources, enabling smart and rapid placement of new virtual machines and virtual disk drives as well as load balancing of existing workloads. Figure1depictsadatastoreclusterof12TBformedbyfour3TBdatastores.

VM

VM VM VM VMVM

VMVM VM

Datastore Cluster12TB

3TB 3TB 3TB 3TBDatastores

Figure 1. Datastore Cluster



Placement RecommendationsStorageDRSprovidesinitialplacementandongoingbalancingrecommendations,helpingvSphereadministratorsmakeplacementdecisionsbasedonspaceandI/Ocapacity.Duringtheprovisioningofavirtualmachine, a datastore cluster can be selected as the target destination for this virtual machine or virtual disk, afterwhicharecommendationforinitialplacementismadebasedonspaceandI/Ocapacity.Initialplacementinamanualprovisioningprocesshasproventobeverycomplexinmostenvironments.Asaresult,crucialprovisioningfactorssuchascurrentspaceutilizationandI/Oloadareoftenignored.StorageDRSensuresthatinitial placement recommendations are made in accordance with space constraints and with respect to the goalsofspaceandI/Oloadbalancing.ThesegoalsaimtominimizetheriskofstorageI/Obottlenecksandtheperformanceimpactonvirtualmachines.Figure2depictsthesedefinablethresholds.

Figure 2. Defining Thresholds for Storage DRS

Ongoingbalancingrecommendationsaremadewhenoneormoredatastoresinadatastoreclusterexceedtheuser-configurablespaceutilizationorI/Olatencythresholds.Thesethresholdsaretypicallydefinedduringtheconfigurationofthedatastorecluster.StorageDRSappliesthedatastoreutilizationreportingmechanismofVMwarevCenterServer,tomakerecommendationswhenevertheconfiguredutilizedspacethresholdisexceeded.I/Oloadisevaluatedbydefaultevery8hours.WhentheconfiguredmaximumspaceutilizationortheI/Olatencythreshold(15msbydefault)isexceeded,StorageDRSwillcalculateallpossiblemoves,tobalance the load accordingly while considering the cost and the benefit of the migration.



VM VM VM VMVM

VMVM VM

VM

500GB 500GB 500GB 500GB

Datastore Cluster (Pod)

ApplyBalancing

Recommendations 2TB

Datastores

Figure 3. Defining Thresholds for Storage DRS

Affinity Rules and Maintenance ModeStorageDRSaffinityrulesenablecontroloverwhichvirtualdisksshouldorshouldnotbeplacedonthesamedatastorewithinadatastorecluster.Bydefault,avirtualmachine’svirtualdisksarekepttogetheronthesamedatastore.StorageDRSoffersthreetypesofaffinityrules:

•VMDKAnti-Affinity Virtual disks of a virtual machine with multiple virtual disks are placed on different datastores.

•VMDKAffinity Virtual disks are kept together on the same datastore.

•VMAnti-Affinity Two specified virtual machines, including associated disks, are placed on different datastores.

Inaddition,StorageDRSoffersDatastoreMaintenanceMode,whichautomaticallyevacuatesallvirtualmachinesand virtual disk drives from the selected datastore to the remaining datastores in the datastore cluster.

Datastore Cluster Datastore Cluster Datastore Cluster

VMDK A�nity VMDK Anti-A�nity VM Anti-A�nity

VMVM

VM

VM

VMVM

VMVM

VM

VM

Figure 4. Affinity Rules

StorageDRSworkswithbothVMFS-andNFS-baseddatastores.ButmixingVMFSandNFSdatastoresinasingle datastore cluster is currently not supported. More details about this feature, and implementation tips and design considerations, are described in the documentation: Resource Management Guide, chapter 11.



vSphere Storage aPIs – Storage awarenessvSphere®StorageAPIs-StorageAwarenessisanewsetofAPIsthatwillenableVMwarevCenterServertodetectthecapabilitiesofthestoragearrayLUNs/datastores,makingitmucheasiertoselecttheappropriatediskforvirtualmachineplacementorthecreationofdatastoreclusters.vSphereStorageAPIs–StorageAwarenesscanalso provide help in facilitating, for example, the troubleshooting process or conversations between vSphere and storageadministrators.Storagecapabilities,suchasRAIDlevel,thinorthickprovisioned,replicationstateandmuchmore,cannowbemadevisiblewithinVMwarevCenterServereithervia“system-definedcapabilities,”whichareper-datastoredescriptors,orviaattributesthatareexposedviaStorageViewsandSMSAPI.vSphereStorageAPIs–StorageAwarenessaimstoeliminatetheneedformaintainingmassivespreadsheetsdetailingthestoragecapabilitiesofeachLUNthatareneededtoguaranteethecorrectSLAtovirtualmachines.

Profile-Driven StorageManagingdatastoresandmatchingtheSLArequirementsofvirtualmachineswiththeappropriatedatastorecanbechallengingandcumbersometasks.vSphere5.0introducesProfile-DrivenStorage,whichwillenablerapidandintelligentplacementofvirtualmachinesbasedonSLA,availability,performanceorotherrequirements and provided storage capabilities.

UsingProfile-DrivenStorage,variousstoragecharacteristics,typicallydefinedasatier,canberequestedinavirtual machine storage profile. These profiles are used during provisioning, cloning and Storage vMotion to ensure that only those datastores or datastore clusters that are compliant with the virtual machine storage profile are made available. The virtual machine storage profile can also help select a similar type of datastores whencreatingaStorageDRSdatastorecluster.Profile-DrivenStoragewillreducetheamountofmanualadministrationrequiredforvirtualmachineplacementwhileimprovingvirtualmachineSLAstoragecompliance.

APPOS

NotCompliantCompliant

Gold

Virtual Machine Storage ProfileAssociated with Virtual Machine

Virtual Machine Storage ProfileDescribing Storage

Requirements

Storage CapabilitiesSurfaced by vSphere Storage

APIs–Storage Awareness or User Defined

Figure 5. Virtual Machine Storage Profile



Profile-DrivenStoragedeliversthesebenefitsbytakingadvantageofthefollowing:

•FullintegrationwithvSphereStorageAPIs–StorageAwareness,enablingusageofstoragecharacterizationsupplied by storage vendors.

•SupportforNFS,iSCSIandFibreChannel(FC)storage,andallstoragearraysontheHCL.

•EnablingthevSphereadministratortotagstoragebasedoncustomer-orbusiness-specificdescriptions.

•Usingstoragecharacterizationsand/oradministrator-defineddescriptionstocreatevirtualmachineplacementrules in the form of storage profiles.

•Providinganeasymeanstocheckavirtualmachine’scompliancewiththeserules.Thisensuresthatthevirtualmachine is not deployed or migrated to an incorrect type of storage without the administrator’s being informed about it.

Virtual Machine Compliance StatusAsmentioned,virtualmachinestorageprofilesenableyoutocheckcomplianceofallvirtualmachinesandtheassociatedvirtualdisksinasinglepaneofglass(Figure6).Buttheyalsoenableyoutoseethisonaper–virtualmachine basis, ensuring that even “virtual machine administrators” who don’t necessarily have access to all the differentlayerscanvalidatecomplianceonthevirtualmachinesummary’stab(Figure7).

Figure 6. Virtual Machine Storage Profiles Single Pane of Glass for Compliance

Figure 7. Per–Virtual Machine Profile Compliance

Asaresult,managingstoragetiers,provisioning,migrating,cloningvirtualmachinesandcorrectvirtualmachineplacementinvSpheredeploymentshavebecomemoreefficientanduserfriendly.Profile-DrivenStorage removes the need for maintaining complex and tedious spreadsheets and validating compliance manually during every migration or creation of a virtual machine or virtual disk.



Fibre Channel over ethernet Software InitiatorvSphere4.0introducedsupportforhardwareFibreChanneloverEthernet(FCoE)adaptors.vSphere5.0willtaketheadoptionofFCoEtoanewlevelbyintroducingasoftwareFCoEadaptor.ThesoftwareFCoEadaptorwillrequireanetworkadaptorthatcansupportpartialFCoEoffloadcapabilitiesbeforeitcanbeenabled(Figure8).

Figure 8. Adding a Software FCoE Adaptor

AfterthesoftwareFCoEadaptorhasbeenenabled,anewadaptoriscreated.Afterthecreationoftheadapter,devicesthatarepresentedtothisparticularadapterwillberecognized(Figure9)byvSphere,enablingthecreationofanewdatastore.ThesoftwareFCoEadapterwillenableyoutouseFCoEcapabilitieswithouttheneedtoresorttospecificFCoEhardwareadapters,creatingamoreagileandflexibleinfrastructure.

Figure 9. FCoE Adaptor

T E C H N I C A L W H I T E p A p E R / 1 0


iSCSI Initiator enhancementsWithvSphere4.0,anewiSCSIinitiatorwasreleasedthatwasmoreefficientandcapableofdrivingmoreIOPSthaneverbefore.TheentireiSCSIsoftwareinitiatorstackwasrewrittenandoptimizedforperformance.vSphere4.0enabledmultipleVMkernelnetworkadaptorstoconnecttotheiSCSIarray.Configurationwaspossible only through the command line and was considered to be a difficult task. vSphere 5.0 introduces the abilitytofullyconfigureiSCSIthroughthevSphereclient,asdepictedinFigure10.

Figure 10. iSCSI Initiator



vSphere Storage I/O ControlvSphereStorageI/OControlwasinitiallyintroducedinvSphere4.1toprovideI/OprioritizationofvirtualmachinesrunningonaclusterofVMware®ESX®serversthathadaccesstoashared,iSCSIorFC,storagepool.ItextendedthefamiliarconstructsofsharesandlimitsthatexistedforCPUandmemory,toaddressstorageutilizationthroughadynamicallocationofI/OqueueslotsacrossaclusterofVMwareESXservers.

vSphere5.0extendsStorageI/OControltoprovideclusterwideI/OsharesandlimitsforNFSdatastores.Thismeans that no single virtual machine should be able to create a bottleneck in any environment regardless of the typeofsharedstorageused.StorageI/OControlautomaticallythrottlesavirtualmachinethatisconsumingadisparateamountofI/Obandwidthwhentheconfiguredlatencythresholdhasbeenexceeded.ThisenablesothervirtualmachinesusingthesamedatastoretoreceivetheirfairshareofI/O.StorageDRSandStorageI/OControlaretheperfectpartnersforpreventingdeprecationofservice-levelagreementswhileprovidinglong-termandshort-termI/Odistributionfairness.

vSphere Storage aPIs – array IntegrationvSphereStorageAPIs–ArrayIntegration(VAAI)werefirstintroducedwithvSphere4.1,enablingoffloadcapabilities support for three primitives:

1. Full copy, enabling the storage array to make full copies of data within the array

2. Block zeroing, enabling the array to zero out large numbers of blocks

3. Hardware-assisted locking, providing an alternative mechanism to protect VMFS metadata

WithvSphere5.0,supportfortheVAAIprimitiveshasbeenenhancedandadditionalprimitiveshavebeenintroduced:

•vSphere®ThinProvisioning(ThinProvisioning),enablingthereclamationofunusedspaceandmonitoringofspaceusageforthin-provisionedLUNs

•HardwareaccelerationforNAS

•SCSIstandardizationbyT10compliancyforfullcopy,blockzeroingandhardware-assistedlocking

vSphere Thin ProvisioningvSphere5.0introducesmultipleVAAIenhancementsforenvironmentsusingarray-basedthin-provisioningcapabilities.Historically,thetwomajorchallengesofthin-provisionedLUNshavebeenthereclamationof deadspaceandthechallengessurroundingthemonitoringofspaceusage.VAAIThinProvisioningintroducesthe following:

•DeadSpaceReclamationinformsthearrayaboutthedatastorespacethatisfreedwhenfilesaredeletedorremoved from the datastore by Storage vMotion. The array can then reclaim the freed blocks of space.

•Out-of-SpaceConditionsmonitorsthespaceusageonthin-provisionedLUNstopreventrunningoutofphysicalspace.Anew,advancedwarninghasbeenaddedtovSphere5.0forathin-provisionedout-of-spacecondition.

DeadSpaceReclamationofferstheabilitytoreclaimblocksofathin-provisionedLUNonthearraywhenavirtualdiskisdeletedormigratedtoadifferentdatastoreby,forexample,StorageDRS(Figure10).Historically,when virtual machines were migrated from a datastore, the blocks used by the virtual machine prior to the migration were still being reported as “in use” by the array. This meant that usage statistics from the storage array might have been misleading and expensive disk space possibly might have been wasted. With this new VAAIprimitive,thestoragedevicewillbeinformedthattheblocksarenolongerused,resultinginbetterreporting of disk space consumption and allowing for the reclamation of these unused blocks.



VMware ESX

VM VM VMVM

Storage vMotion2

VMFS-A

ObsoleteVirtual Machine’s File Data Blocks

VMFS-B

Figure 11. Reclamation of Dead Space

An“out-of-spacecondition”isthenightmareofeverystorageandvirtualizationadministratorinarray-basedthin-provisioned environments. “Storage oversubscription” in thin-provisioned environments can lead to catastrophic scenarios when an out-of-space condition is encountered. vSphere 5.0 mitigates these problems andsimplifiesstoragemanagementthroughtheadditionofadvancedwarnings(Figure12)anderrorswhenthresholdsarereachedforthin-provisioneddatastores.Enhancementsincludemechanismsthattemporarilypause a virtual machine when disk space is exhausted, enabling the allocation of additional space to the datastore, or the migration of an existing virtual machine, without resulting in the failure of the virtual machine.

Figure 12. Out-of-Space Condition



Hardware Acceleration for NASHardwareAccelerationforNASwillenablefasterprovisioningandtheuseofthickvirtualdisksthroughtwonewlyintroducedVAAIprimitives:

•FullFileClone–SimilartoFullCopy.EnablesvirtualdiskstobeclonedbytheNASdevice

•ReserveSpace–EnablescreationofthickvirtualdiskfilesonNAS

FullFileCloneenablesfastprovisioningofvirtualmachinesonNASdevices,similartotheexperience “FullCopy”providedforiSCSI/FCarrays.

PriortovSphere5.0,avirtualdiskwascreatedasathin-provisioneddisk,notevenenablingthecreationofathickdisk.StartingwithvSphere5.0,VAAINASextensionsenableNASvendorstoreservespaceforanentirevirtualdisk(Figure13).ThisenablesthecreationofthickdisksonNFSdatastores.

Figure 13. Creation of Thick Disks



NASVAAIplug-insarenotshippedwithvSphere5.0.Theyaredevelopedanddistributedbystoragevendorsbut are signed by the VMware certification program to guarantee quality.

T10 CompliancyvSphere 4.1 introduced T10 compliancy for block zeroing, enabling vendors to utilize the T10 standards with the default,shippedplug-in.vSphere5.0introducesenhancedsupportforT10,enablingtheusageofVAAIprimitives without the need to install a plug-in, as well as enabling support for many additional storage devices.

vSphere Storage vMotionvSphere®StoragevMotion®(StoragevMotion)enableslivemigrationforrunningvirtualmachinediskfilesfromone storage location to another with no downtime or service disruption. With vSphere 5.0, multiple enhancements have been introduced to increase efficiency of the Storage vMotion process, to improve overall performance, and for enhanced supportability. Storage vMotion in vSphere 5.0 now also supports the migration of virtual machines with a vSphere snapshot and the migration of linked clones.

The enhancements to Storage vMotion include a new and more efficient migration process through the use of a new feature called Mirror Mode. Mirror Mode enables a single-pass block copy of the source disk to the destination diskbymirroringI/Osofcopiedblocks.NotonlyhastheefficiencyofStoragevMotionincreased,butalsothemigration time predictability, making it easier to plan migrations and reducing the elapsed time per migration.

Themirrordriverisenabledonaper–virtualmachinebasisandresideswithintheVMkernel.Whentheguest OSofthevirtualmachinethatisundergoingtheprocessusingStoragevMotioninitiatesawritetoanalreadycopiedblock,themirrordriver(Figure14)willsynchronouslymirrorthiswriteandwaitforbothacknowledgementsbeforecommunicatingthistotheguestOS.

Guest OS

2

VMM/Guest

Datamover VMkernelMirror Driver

Source Destination

Userworld

Figure 14. Data Flow with Storage vMotion Mirror Mode


ConclusionvSphere5.0addsmanynewstoragefeaturestoanalreadyrichsetofcapabilitiessupportedinvSphere4.1.Itreduces complexity while providing greater scalability. Virtual machine provisioning historically has imposed operational challenges. Monitoring and manually balancing workloads, or provisioning virtual machines based onI/Ocapacityandspaceutilization,hasproventobeverydifficultandhasoftenbeenneglected,leadingtohotspotsandover-orunderutilizeddatastores.StorageDRSisanewfeatureintroducedinvSphere5.0thatprovidessmartvirtualmachineplacementandloadbalancingmechanismsbasedonI/Oandspacecapacity.The result is a decrease in the operational effort associated with the provisioning of virtual machines and monitoring of the storage environment.

About the AuthorDuncanEppingisprincipalarchitectintheTechnicalMarketinggroupatVMwareandisfocusedonstorageandVMwareESXi.Previously,heworkedatOracleandwithseveralconsultancycompanies,wherehehadmorethan 10 years of experience in the design and development of infrastructures and deployment best practices. HewasamongthefirstVMwarecertifieddesignexperts(VCDX007).Heistheco-authorofmanybooks,including VMware vSphere 4.1 HA and DRS Technical Deepdive, the VMware vSphere 4.0 Quick Start Guide, Foundation for Cloud Computing with VMware vSphere 4 and his most recent publication, Foundation for Cloud Computing with VMware vCloud Director.

vMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www .vmware .comCopyright © 2011 VMware, Inc . All rights reserved . This product is protected by U .S . and international copyright and intellectual property laws . VMware products are covered by one or more patents listed at http://www .vmware .com/go/patents . VMware is a registered trademark or trademark of VMware, Inc . in the United States and/or other jurisdictions . All other marks and names mentioned herein may be trademarks of their respective companies . Item No: VMW-WP-5-0-STORAGE-USLET-101

Documents

What’s New in VMware vSphere 5.0 – Storage€¦ · What’s New in VMware vSphere 5.0 – Storage Introduction VMware vSphere™ 5.0 (“vSphere”) brings many new capabilities