VMwareVirtualSANTechnicalWalkthrough/MediumDiveRawlinsonRivera,VCDXSeniorArchitect|Storage&AvailabilityVirtualSANTechnicalWalkthrough1SDSandVirtualSANOverview2UseCases3HardwareRequirements4TechnicalCharacteristicsandArchitecture5ConfigurationWalkthrough6VirtualMachineProvisioningOperations7Resiliency

and

Failed

Scenarios8Interoperability9DesignandSizing10Troubleshooting22011-20132008-20102005-2007vSphere4.xThinProvisioningStorageI/OcontrolBootfromSANVAAILinkedmode2014+VI3.xVMFSSnapshotsStoragevMotionNAS&iSCSIsupportvSphere5.xStorageDRSProfile-drivenStorageVASASphereStorageAppliancevSphereDataProtectionvSphereReplicationvSphereFlashReadVMwareStorageInnovations3Software-definedStorageHypervisor-ConvergedOpportunitiesWhythevirtualizationplatformcanplayacriticalroletosolvestorageproblems?InherentknowledgeofapplicationGlobalviewofinfrastructureHardwareagnosticHypervisor-ConvergedstoragesolutionsabstracttheplumbingtooptimizestorageforapplicationsvSphereSAN&NASAllFlashBLOBDASServerSideFlash4VirtualSAN5vSANVSANSAN/NASVVOLVMwareSoftware-definedStorage6Bringingcompute’soperationalmodeltostorageAbstractionandpoolingInfrastructureintegrationNewstoragetiersVMcentricdataservicesThird-partyservicesintegrationCommonpolicy-basedautomationandorchestrationLUNLUNLUNLUNLUNLUNSAN/NASPoolVirtualDataPlanex86Servers

Hypervisor-convergedStoragepoolObjectStoragePoolCloudObjectStorageVirtualDataServicesDataProtectionMobilityPerformancePolicy-drivenControlPlaneVirtualSANVMwareVirtualSANSoftware-definedstoragesoftwaresolution.AggregateslocallyattachedstoragefromeachESXihostinacluster.Flashoptimizedstoragesolution.VM-Centricdataoperationsandpolicydrivenmanagementprincipals.ResilientdesignbasedonaDistributedRAIDarchitectureNosinglepointsoffailuresFullyintegratedwithvSphere.7vSphere+VirtualSANHarddisksHarddisksSSDSSDHarddisksSSD…VirtualSANSharedDatastoreHypervisor-Convergedstorageplatform8DataProtectionDisasterRecoveryvSphereCloudOpsandAutomationSnapshotsLinkedclonesSiteRecoveryManagervCenterOperationsManagervCloudAutomationCenterVirtualDesktopVDPAdvancedvSphereReplicationStoragePolicy-BasedManagementVMwareHorizonViewvMotionvSphereHADRSStoragevMotionIaaSDeeplyIntegratedwithVMwareStackBringingthebenefitofVMware’sproductstomakeStorageEasyVirtualSANisNOTaVirtualStorageAppliance9VirtualSANisfullyintegratedwithvSphere(ESXi&vCenter)DriversembeddedinESXi5.5containtheVirtualSANsmartsKernelmodules:ProvidetheshortestpathforI/ORemoveunnecessarymanagementoverheadswhendealingwithanapplianceDonotconsumeresourcesunnecessarilyVirtualSAN–EmbeddedintovSphereVirtualSAN–NotaVSA+VSAVMwareVirtualSANHybrid

storagesolutionMagneticdisks(HDD)Flashbaseddisks(SSD)StoragescaleoutarchitecturebuiltintothehypervisorDynamiccapacityandperformancescalabilityObjectbasedstoragearchitectureInteroperablewithvSphereandenterprisefeatures:vMotion,DRS,vSphereHA10vSphere+VirtualSANHarddisksHarddisksSSDSSDHarddisksSSD…VirtualSANSharedDatastoreRadicallySimpleHypervisor-ConvergedStorageSoftware11InstallsintwoclicksManagedfromvSphereClientPolicy-basedmanagementSelf-tuningandelasticDeepintegrationwithVMwarestackRadicallySimpleEmbeddedinvSpherekernelFlash-acceleratedUpto915KIOPsfrom16nodesclusterMatchestheVDIdensityofallflasharrayBestprice/performanceHighPerformanceLowerTCOEliminateslargeupfrontinvestments(CAPEX)Grow-as-you-go(OPEX)FlexiblechoiceofindustrystandardhardwareDoesnotrequirespecializedskillsVirtualSANKeyBenefitsStoragePolicy-BasedManagementVSANSharedDatastoreSimplifiesandAutomatesStorageManagement12PerVMstorageservicelevelsfromasingleself-tuningdatastoreCapacityPerformanceAvailabilityPerVMStoragePoliciesPoliciessetbasedonapplicationneedsvSphere+VSANSLAsSoftwareautomatescontrolofservicelevelsNomoreLUNs!NooverprovisioningLessresources,lesstimeEasytochangeToday5.Consumefrompre-allocatedbin4.Selectappropriatebin3.Exposepre-allocatedbins2.Pre-allocatestaticbins1.Pre-definestorageconfigurations1.Definestoragepolicy2.ApplypolicyatVMcreationVSANVSANSharedDatastoreResourceanddataserviceareautomaticallyprovisionedandmaintainedOverprovisioning(bettersafethansorry!)Wastedresources,wastedtimeFrequentDataMigrationsVirtualSANPutsTheAppInChargeSimplerandautomatedstoragemanagementthroughapplicationcentricapproach13VMwareVirtualSANUseCases15ManagementClustersUseCasesBackupandDRTargetDMZ/IsolatedTier2/Tier3

Test/Dev/Staging

PrivatecloudVirtualDesktopROBOVDISiteASiteBvSphereVSANVMwareVirtualSANHardwareRequirementsHardwareRequirements17AnyServerontheVMwareCompatibilityGuideSSD,HDD,andStorageControllersmustbelistedontheVMwareCompatibilityGuideforVSAN http:///resources/compatibility/search.php?deviceCategory=vsanMinimum3ESXi5.5Hosts,MaximumHosts“I’lltellyoulater……”1Gb/10GbNICSAS/SATAControllers(RAIDControllersmustworkin“pass-through”orRAID0”modeSAS/SATA/PCIe

SSDSAS/NL-SAS/SATAHDDAtleast1ofeach4GBto8GBUSB,SDCards,SATADOMFlashBasedDevicesInVirtualSANALLreadandwriteoperationsalwaysgodirectlytotheFlashtier.FlashbaseddevicesservetwopurposesinVirtualSANNon-volatileWriteBuffer(30%)WritesareacknowledgedwhentheyenterpreparestageonSSD.ReduceslatencyforwritesReadCache(70%)CachehitsreducesreadlatencyCachemiss–retrievedatafromHDDChoiceofhardwareisthe#1performancedifferentiatorbetweenVirtualSANconfigurations.18FlashBasedDevicesVMwareSSDPerformanceClassesClassA:2,500-5,000writespersecondClassB:5,000-10,000writespersecondClassC:10,000-20,000writespersecondClassD:20,000-30,000writespersecondClassE:30,000+writespersecondExamplesIntelDCS3700SSD~36000writespersecond->ClassEToshibaSASSSDMK2001GRZB~16000writespersecond->ClassCWorkloadDefinitionQueueDepth:16orlessTransferLength:4KBOperations:writePattern:100%randomLatency:lessthan5msEndurance10DriveWritesperDay(DWPD),andRandomwriteenduranceupto3.5PBon8KBtransfersizeperNANDmodule,or2.5PBon4KBtransfersizeperNANDmodule19MagneticDisks(HDD)SAS/NL-SAS/SATAHDDssupported7200RPMforcapacity10000RPMforperformance15000RPMforadditionalperformanceNLSASwillprovidehigherHDDcontrollerqueuedepthatsamedriverotationalspeedandsimilarpricepointNLSASrecommendedifchoosingbetweenSATAandNLSASDifferentiateperformancebetweenclusterswithSSDselection,andSSD:HDDratio.Ruleofthumbguidelineis10%ofanticipatedcapacityusage20StorageControllersSAS/SATAStorageControllersPass-throughor“RAID0”modesupportedPerformanceusingRAID0modeiscontrollerdependentCheckwithyourvendorforSSDperformancebehindaRAID-controllerStorageControllerQueueDepthmattersHigherstoragecontrollerqueuedepthwillincreaseperformanceValidatenumberofdrivessupportedforeachcontroller21StorageControllers–RAID0ModeConfigurealldisksinRAID0modeFlashbaseddevices(SSD)Magneticdisks(HDD)DisablethestoragecontrollercacheAllowsbetterperformanceascacheiscontrolledbyVirtualSANDisksDevicecachesupportFlashbaseddevicesleveragewritethroughcaching

ESXimaynotbeabletodifferentiateflashbaseddevicesfrommagneticdevices.UseESXCLItomanuallyflagthedevicesasSSD22Network1Gb/10Gbsupported10GbsharedwithNIOCforQoSwillsupportmostenvironmentsIf1GBthenrecommenddedicatedlinksforVirtualSANJumboFrameswillprovidenominalperformanceincreaseEnableforgreenfielddeploymentsVirtualSANsupportsbothVSS&VDSNIOCrequiresVDSNexus1000v–Shouldworkbuthasn'tbeenfullytested

Networkbandwidthperformancehasmoreimpactonhostevacuation,rebuildtimesthanonworkloadperformance23FirewallsVirtualSANVendorProvider(VSANVP)Inboundandoutbound-TCP8080ClusterMonitoring,Membership,andMonitoringServices(CMMDS)InboundandoutboundUDP12345-23451ReliableDatagramTransport(RDT)InboundandoutboundTCP223324VMwareCompatibilityGuide25Multi-levelcellSSD(orbetter)orPCIeSSDSAS/NL-SASHDDSelectSATAHDDsAnyServeronvSphereHardwareCompatibilityList*Note:Foradditionaldetails,pleaserefertoVirtualSANVMwareCompatibilityGuidePage6Gbenterprise-gradeHBA/RAIDController12BuildyourownVSANReadyNode…with10differentoptionsbetweenmultiple3rdpartyvendorsavailableatGAPreconfiguredserverreadytouseVSAN……usingtheVSANCompatibilityGuide*Chooseindividualcomponents…TwoWaystoBuildaVirtualSANNodeRadicallySimpleHypervisor-ConvergedStorageVMwareVirtualSANTechnicalCharacteristicsandArchitectureTechnicalCharacteristicsVirtualSANisaclusterlevelfeaturesimilarto:vSphereDRSvSphereHAVirtualSANDeployed,configuredandmanagefromvCenterthroughthevSphereWebClient(ONLY!).RadicallysimpleConfigureVMkernelinterfaceforVirtualSANEnableVirtualSANbyclickingTurnOn28VirtualSANImplementationRequirementsVirtualSANrequires:Minimumof3hostsinaclusterconfigurationAll3hostMUST!!!contributestoragevSphere5.5U1orlaterLocallyattacheddisksMagneticdisks(HDD)Flash-baseddevices(SSD)Networkconnectivity1GBEthernet10GBEthernet(preferred)29esxi-01localstoragelocalstoragelocalstoragevSphere5.5U1Clusteresxi-02esxi-03clusterHDDHDDHDDStoragePolicy-basedManagementSPBMisastoragepolicyframeworkbuiltintovSpherethatenablesvirtualmachinepolicydrivenprovisioning.VirtualSANleveragesthisnewframeworkinconjunctionwithVASAAPI’stoexposestoragecharacteristicstovCenter:

StoragecapabilitiesUnderlyingstoragesurfacesuptovCenterandwhatitiscapableofoffering.VirtualmachinestoragerequirementsRequirementscanonlybeusedagainstavailablecapabilities.VMStoragePoliciesConstructthatstoresvirtualmachine’sstorageprovisioningrequirementsbasedonstoragecapabilities.30StoragePolicyWizardSPBMVSANobjectVSANobjectmanagervirtualdiskVSANobjectsmaybe(1)mirroredacrosshosts&(2)stripedacrossdisks/hoststomeetVMstorageprofilepoliciesDatastoreProfileVirtualSANSPBMObjectProvisioningMechanismVirtualSANConstructsandArtifactsNewVirtualSANconstructs,artifactsandterminologies:

DiskGroups.VSANDatastore.Objects.Components.VirtualSANNetwork.32VirtualSANDiskGroupsVirtualSANusestheconceptofdiskgroups

topooltogetherflashdevicesandmagneticdisksassinglemanagementconstructs.Diskgroupsarecomposedofatleast1flashdeviceand1magneticdisk.Flashdevicesareuseforperformance(Readcache+Writebuffer).Magneticdisksareusedforstoragecapacity.Diskgroupscannotbecreatedwithoutaflashdevice.33diskgroupdiskgroupdiskgroupdiskgroupEachhost:5diskgroupsmax.Eachdiskgroup:1SSD+1to7HDDsdiskgroupHDDHDDHDDHDDHDDVirtualSANDatastoreVirtualSANisanobjectstoresolutionthatispresentedtovSphereasafilesystem.TheobjectstoremountstheVMFSvolumesfromallhostsinaclusterandpresentsthemasasingleshareddatastore.OnlymembersoftheclustercanaccesstheVirtualSANdatastoreNotallhostsneedtocontributestorage,butitsrecommended.34diskgroupdiskgroupdiskgroupdiskgroupEachhost:5diskgroupsmax.Eachdiskgroup:1SSD+1to7HDDsdiskgroupVSANnetworkVSANnetworkVSANnetworkVSANnetworkVSANnetworkvsanDatastoreHDDHDDHDDHDDHDDVirtualSANObjectsVirtualSANmanagesdataintheformofflexibledatacontainerscalledobjects.virtualmachinefilesarereferredtoasobjects.Virtualmachinesfilesarereferredtoasobjects.Therearefourdifferenttypesofvirtualmachineobjects:VMHomeVMswapVMDKSnapshotsVirtualmachineobjectsaresplitintomultiplecomponentsbasedonperformanceandavailability

requirementsdefinedinVMStorageprofile.35diskgroupdiskgroupdiskgroupdiskgroupEachhost:5diskgroupsmax.Eachdiskgroup:1SSD+1to7HDDsdiskgroupVSANnetworkVSANnetworkVSANnetworkVSANnetworkVSANnetworkvsanDatastoreHDDHDDHDDHDDHDDVirtualSANComponentsVirtualSANcomponentsarechunksofobjectsdistributesacrossmultiplehostsinaclusterinordertotoleratesimultaneousfailuresandmeetperformancerequirements.VirtualSANutilizesaDistributedRAIDarchitecturetodistributedataacrossthecluster.Componentsaredistributedwiththeuseoftwomaintechniques:

Striping(RAID0)Mirroring(RAID1)Numberofcomponentreplicasandcopiescreatedisbasedontheobjectpolicydefinition.36diskgroupdiskgroupdiskgroupdiskgroupdiskgroupVSANnetworkVSANnetworkVSANnetworkVSANnetworkVSANnetworkvsanDatastorereplica-1replica-2RAID1HDDHDDHDDHDDHDDObjectandComponentsLayout37VSANnetworkVSANnetworkVSANnetworkVSANnetworkVSANnetworkVirtualSANStorageObjectsR1R0R0R0AvailabilitydefinedasnumberofcopiesLowlevelstorageobjectswouldresideondifferenthostsVMFSVMFSVMFSrolo2.vmdkTheVMHomedirectoryobjectisformattedwithVMFStoallowaVM’sconfigurationfilestobestoredonit.PerformancemayincludeastripewidthVMFSrolo1.vmdkrolo.vmx,.log,etc/vmfs/volumes/vsanDatastore/rolo/rolo.vmdkdiskgroupHDDdiskgroupHDDdiskgroupHDDdiskgroupHDDdiskgroupHDDVirtualSANNetworkNewVirtualSANtrafficVMkernelinterface.DedicatedforVirtualSANintra-clustercommunicationanddatareplication.SupportsbothStandardandDistributesvSwitchesLeverageNIOCforQoSinsharedscenariosNICteaming–usedforavailabilityandnotforbandwidthaggregation.Layer2Multicastmustbeenabledonphysicalswitches.MucheasiertomanageandimplementthanLayer3Multicast38ManagementVirtualMachinesvMotionVirtualSANDistributedSwitch20shares30shares50shares100sharesuplink1uplink2vmk1vmk2vmk0VirtualSANNetworkNICteamedandloadbalancingalgorithms:

RoutebasedonPortIDactive/passivewithexplicitfailover

RoutebasedonIPHashactive/activewithLACP

portchannel

RoutebasedonPhysicalNICloadactive/activewithLACPportchannelManagementVirtualMachinesvMotionVirtualSANDistributedSwitch100shares150shares250shares500sharesuplink1uplink2vmk1vmk2vmk0MultichassislinkaggregationcapableswitchesVirtualSANScalableArchitecture40ScaleupandScaleoutarchitecture–granularandlinearlystorage,performanceandcomputescalingcapabilitiesPermagneticdisks–forcapacityPerflashbaseddevice–forperformancePerdiskgroup–forperformanceandcapacityPernode–forcomputecapacitydiskgroupdiskgroupdiskgroupVSANnetworkVSANnetworkVSANnetworkvsanDatastoreHDDdiskgroupHDDHDDHDDdiskgroupVSANnetworkHDDscaleupscaleoutVMwareVirtualSANConfigurationWalkthroughConfiguringVMwareVirtualSANRadicallySimpleconfigurationprocedure42SetupVirtualSANNetworkEnableVirtualSANontheClusterSelectManualorAutomatic

IfManual,creatediskgroupsConfigureNetwork43ConfigurethenewdedicatedVirtualSANnetworkvSphereWebClientnetworktemplateconfigurationfeature.EnableVirtualSANOneclickaway!!!VirtualSANconfiguredinAutomaticmode,allemptylocaldisksareclaimedbyVirtualSANforthecreationofthedistributedvsanDatastore.VirtualSANconfiguredinManualmode,theadministratormustmanuallyselectdiskstoaddthethedistributedvsanDatastorebycreatingDiskGroups.44DiskManagementEachhostintheclustercreatesasingleormultiplediskgroupswhichcontainacombinationofHDDs,andSSDs.

45VirtualSANDatastoreAsingleVirtualSANDatastoreiscreatedandmounted,usingstoragefromallmultiplehostsanddiskgroupsinthecluster.VirtualSANDatastoreisautomaticallypresentedtoallhostsinthecluster.VirtualSANDatastoreenforcesthin-provisioningstorageallocationbydefault.46VMStoragePoliciesVMStoragePoliciesareaccessiblefromvSphereWebClientHomescreen.47VirtualSANCapabilitiesVirtualSANcurrentlysurfacesfiveuniquestoragecapabilitiestovCenter.48NumberofFailurestoTolerateNumberoffailurestotolerateDefinesthenumberofhosts,diskornetworkfailuresastorageobjectcantolerate.For“n”failurestolerated,“n+1”copiesoftheobjectarecreatedand“2n+1”hostcontributingstoragearerequired.49vsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04~50%ofI/O~50%ofI/OVirtualSANPolicy:“Numberoffailurestotolerate=1”raid-1NumberofDiskStripesPerObjectNumberofdiskstripesperobjectThenumberofHDDsacrosswhicheachreplicaofastorageobjectisdistributed.Highervaluesmayresultinbetterperformance.50vsannetworkstripe-2bwitnessesxi-01esxi-02esxi-03esxi-04stripe-1bstripe-1astripe-2araid-0raid-0VSANPolicy:“Numberoffailurestotolerate=1”+“StripeWidth=2”raid-1VirtualSANStorageCapabilitiesForceprovisioningifyes,theobjectwillbeprovisionedevenisthepolicyspecifiedinthestoragepolicyisnotsatisfiablewiththeresourcescurrentlyavailable.Flashreadcachereservation(%)Flashcapacityreservedasreadcacheforthestorageobject.Specifiedasapercentageoflogicalsizeoftheobject.Objectspacereservation(%)Percentageofthelogicalsizeofthestorageobjectthatwillbereserved(thickprovisioned)uponVMprovisioning.Therestofthestorageobjectisthinprovisioned.

51VirtualSANI/Oflow–WriteAcknowledgementvsannetworkvmdkvmdkesxi-01esxi-02esxi-03esxi-04VSANmirrorswriteIOstoallactivemirrors,theseareacknowledgedwhentheyhittheflashbuffer!witnessDestagingtoHDDisdoneindependentlybetweenhosts.raid-1VirtualSANI/Oflow–1MBincrementstripingvsannetworkwitnessesxi-01esxi-02esxi-03esxi-04stripe-1bstripe-1a1MB(1)raid-0raid-0VSANisthinprovisionedbydefault,stripesgrowinincrementsof1MBraid-11MB(3)1MB(5)1MB(2)1MB(4)(x)indicatesstripesegment.ComponentsandObjectsVisualizationVisualizationofmappingandlayoutofallobjectsandcomponentsvSphereWebClientRVC54StorageCapabilitiesRecommendedPractices55StorageCapabilityUseCaseValueNumberoffailurestotolerate(RAID1–Mirror)RedundancyDefault1Max3Numberofdiskstripesperobject(RAID0–Stripe)PerformanceDefault1Max12ObjectspacereservationThickProvisioningDefault0Max100%FlashreadcachereservationPerformanceDefault0Max100%ForceprovisioningOverridepolicyDisabledVMStoragePoliciesRecommendationsNumberofDiskStripesperobjectShouldbeleftat1,unlesstheIOPSrequirementsoftheVMisnotbeingmetbytheflashlayer.

FlashReadCacheReservationShouldbeleftat0,unlessthereisaspecificperformancerequirementtobemetbyaVM.

ProportionalCapacityShouldbeleftat0,unlessthickprovisioningofvirtualmachinesisrequired.

ForceProvisioningShouldbeleftdisabled,unlesstheVMneedstobeprovisioned,evenifnotincompliance.56VMwareVirtualSANVirtualMachineProvisioningOperationsVirtualMachineProvisioningOperationsAllVMprovisioningoperationincludeaccesstoVMStoragePolicies58VirtualMachineProvisioningOperationsIftheVSANDatastoreunderstandsthecapabilitiesintheVMStoragePolicy,itwillbedisplayedasamatchingresource.59VirtualMachineProvisioningOperationsIftheVSANDatastorecansatisfytheVMStoragePolicy,theVMSummarytabwilldisplaytheVMascompliant.Ifnot,duetofailures,ortheforceprovisioningcapability,theVMwillbeshownasnon-compliant.60VirtualMachinePolicyManagementModifyVMperformance,capacity,andavailabilityrequirementswithoutdowntime.61VMwareVirtualSANResiliency&FailureScenariosUnderstandingFailureEventsVirtualSANrecognizedtwodifferenttypesofhardwaredeviceeventsinordertodefinethetypeoffailedscenario:AbsentDegraded

Absent

eventsareresponsibletotriggerthe60minutesrecoveryoperations.VirtualSANwillwait60minutesbeforestartingtheobjectandcomponentrecoveryoperations60minutesisthedefaultsettingforallabsenteventsConfigurablevalueviahostsadvancedsettings63UnderstandingFailureEventsDegradedeventsareresponsibletotriggertheimmediaterecoveryoperations.TriggerstheimmediaterecoveryoperationofobjectsandcomponentsNotconfigurableAnyofthefollowingdetectedI/Oerrorsarealwaysdeemeddegraded:MagneticdiskfailuresFlashbaseddevicesfailuresStoragecontrollerfailuresAnyofthefollowingdetectedI/Oerrorsarealwaysdeemedabsent:NetworkfailuresNetworkInterfaceCards(NICs)Hostfailures64FailurehandlingphilosophyTraditionalSANsPhysicaldriveneedstobereplacedtogetbacktofullredundancyHot-sparedisksaresetasidetotakeroleoffaileddisksimmediatelyInbothcases:1:1replacementofdiskVirtualSANEntireclusterisa“hot-spare”,wealwayswanttogetbacktofullredundancyWhenadiskfails,manysmallcomponents(stripesormirrorsofobjects)failNewcopiesofthesecomponentscanbespreadaroundtheclusterforbalancingReplacementofthephysicaldiskjustaddsbackresourcesManagingFailureScenarios

Throughpolicies,VM’sonVirtualSANcantoleratemultiplefailuresDiskFailure–degradedeventSSDFailure–degradedeventControllerFailure–degradedeventNetworkFailure–absenteventServerFailure–absenteventVM’scontinuetorunParallelrebuildsminimizeperformancepainSSDFail–immediatelyHDDFail–immediatelyControllerFail–immediatelyNetworkFail–60minutesHostFail–60minutes66VirtualSANAccessRulesComponentsAccessRulesAtleast1mirrorcopyintactAllstripesmustbeintactGreaterthan50%ofcomponentsmustbeavailableIncludingwitnesses1MirrorCopyAllstripesavailable>50%componentsandwitnessesPoweronOperationLogicisimplementedperobjectMagneticDiskFailure–InstantmirrorcopyDegraded-Allimpactedcomponentsonthefaileddiskwillbeinstantaneouslycreatedontootherdisk,diskgroups,orhosts.vsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04XvmdknewmirrorcopyInstant!Diskfailure,instantmirrorcopyofimpactedcomponentraid-1FlashBasedDeviceFailure–InstantmirrorcopyDegraded-Allimpactedcomponentsonthefaileddiskwillbeinstantaneouslycreatedontootherdisk,diskgroups,orhosts.Greaterimpactontheclusteroverallstoragecapacityvsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04XvmdknewmirrorcopyInstant!Diskfailure,instantmirrorcopyofimpactedcomponentraid-1HostFailure–60MinuteDelayAbsent–willwaitthedefaulttimesettingof60minutesbeforestartingthecopyofobjectsandcomponentsontootherdisk,diskgroups,orhosts.Greaterimpactontheclusteroverallcomputeandstoragecapacity.vsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04vmdknewmirrorcopy60minutewaitHostfailure,60minuteswaitcopyofimpactedcomponentraid-1XNetworkFailure–60MinuteDelayAbsent–willwaitthedefaulttimesettingof60minutesbeforestartingthecopyofobjectsandcomponentsontootherdisk,diskgroups,orhosts.NICfailures,physicalnetworkfailurescanleadtonetworkpartitions.Multiplehostscouldbeimpactedinthecluster.vsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04vmdknewmirrorcopy60minutewaitNetworkfailure,60minuteswaitcopyofimpactedcomponentraid-1XVirtualSAN1hostisolated–HArestartvsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04isolated!HArestartraid-1vSphereHArestartsVMVirtualSAN2hostsisolated–HArestartvsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04isolated!isolated!HArestartraid-1vSphereHArestartsVMonESXi-02/ESXi-03,theyown>50%ofcomponents!VirtualSANpartition–WithHArestartvsannetworkvmdkvmdkwitnessesxi-01esxi-02esxi-03esxi-04Partition1Partition2HArestartvSphereHArestartsVMinPartition2,itowns>50%ofcomponents!raid-1MaintenanceMode–planneddowntime3Maintenancemodeoptions:

EnsureaccessibilityFulldatamigration

NodatamigrationVMwareVirtualSANInteroperabilityTechnologiesandProductsTechnologyInteroperabilityVirtualSANisfullyintegratedwithmanyofVMware’sstorageandvSphereavailabilityenterprisefeatures.77SupportedNotapplicableFutureVirtualMachineSnapshotsStorageIOControl(SIOC)62TBVMDKsvSphereHAStorageDRSvCOPSvSphereDRSDistributedPowerManagement(DPM)vMotionHorizonViewVirtualSANandHorizonView:Handlepeakperformancesuchasboot,login,read/writestormsSeamlessgranularscalingwithouthugeupfrontinvestmentsSupporthighVDIdensitySupporthighendvirtualdesktopGPUrequirementsVirtualSANiscompatiblewiththefollowingHorizonViewversions:HorizonView5.3(SPBMmanuallyimplemented)Policiesmaintainedacrossoperationssuchasrefresh/refresh–noneedtore-associatevSphere+VirtualSANHarddisksHarddisksSSDSSDHarddisksSSD…FullClonePoliciesFTT=1forpersistentFTT=0fornon-persistentProvisioning100%reservedLinked