What's New In VMware Virtual SAN (VSAN) - WordPress
What’s New in VMware Virtual SAN (VSAN)T e c h n i c a l W HI T E P A P E Rv 0 . 1 c /A U G U S T 2 0 1 3
What’s New in VMware Virtual SAN (VSAN)Table of Contents1. Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Software-Defined Datacenter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.2 Software-Defined Storage. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.3 What is VSAN? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52. Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1 vSphere Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1.1 vCenter Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.1.2 vSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2 Storage Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2.1 Disk Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2.2 Hard Disk Drives. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.2.3 Solid-State Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52.3 Network Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3.1 Network Interface Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3.2 Supported Virtual Switch Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62.3.3 VMkernel Network. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63. Install and Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1 Creating a Virtual SAN Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.1 Manually Add Disks to Disk Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.2 Automatic Creation of Disk Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.1.3 Virtual SAN Cluster Creation Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2 The Virtual SAN Datastore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.2.1 VSAN Datastore Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73.3 Defining Virtual Machine Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74. Architecture Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.1 Distributed RAID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.2 Witnesses and Replicas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.3 The Role of Solid-State Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.3.1 Purpose of Read Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84.3.2 Purpose of Write Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8T ECHNICAL W HI T E P A P E R / 2
What’s New in VMware Virtual SAN (VSAN)5. Storage Policy Based Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1 Virtual SAN Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.1 Number of Failures to Tolerate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95.1.2 Number of Disk Stripes per Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1.3 Flash Read Cache Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1.4 Object Space Reservation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105.1.5 Force Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.2 Witness Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3 VM Storage Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3.1 Enabling VM Storage Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3.2 Creating VM Storage Policies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115.3.3 Assigning a VM Storage Policy During Virtual Machine Provisioning. . . . . . . 125.3.4 Virtual Machine Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125.3.5 Matching Resource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135.3.6 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Acknowledgments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14About the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14T ECHNICAL W HI T E P A P E R / 3
What’s New in VMware Virtual SAN (VSAN)1. Introduction1.1 Software-Defined DatacenterThe annual VMware user conference, VMworld, introduced the vision of VMware for the software-defineddatacenter (SDDC) in 2012. The SDDC is the architecture for the cloud by VMware in which all pillars of thedatacenter, including compute, storage, networks and associated services, are virtualized. In this white paper, welook at one aspect of the SDDC of VMware, the storage pillar. We specifically discuss how a new product calledVirtual SAN (VSAN) fits into this vision.1.2 Software-Defined StorageThe plan of VMware for software-defined storage is to focus on a set of VMware initiatives around local storage,shared storage and storage/data services. In essence, we want to make VMware vSphere a platform forstorage services.Software-defined storage is designed to provide storage services and service-level agreement automationthrough a software layer on the hosts that integrates with and abstracts the underlying hardware.Historically, storage was something that was configured and deployed at the beginning of a project and was notchanged during its life cycle. If there was a requirement to change some aspects or features of the LUN orvolume being leveraged by virtual machines, the original LUN or volume was deleted in many cases and a newvolume with the required features was created. This was a very intrusive and time-consuming operation thatmight have taken weeks to coordinate. With software-defined storage, virtual machine storage requirementscan be dynamically instantiated. There is no need to repurpose LUNs or volumes. Virtual machine workloadsmight change over time, and the underlying storage can be adapted to the workload at any time.A key factor for software-defined storage is Storage Policy Based Management (SPBM). This is featured in thevSphere 5.5 release. SPBM can be considered the next generation of VMware vSphere Storage Profile features.vSphere Storage Profile was first introduced with vSphere 5.0. In vSphere 5.5, an enhanced feature calledVM Storage Policies is introduced.SPBM is a critical component for VMware in implementing software-defined storage. Using SPBM andVMware vSphere APIs, the underlying storage technology surfaces an abstracted pool of storage space withvarious capabilities that is presented to vSphere administrators for virtual machine provisioning. The capabilitiescan relate to performance, availability or storage services such as VMware vSphere Thin Provisioning. A vSphereadministrator can then create a VM Storage Policy using a subset of the capabilities required by the applicationrunning in the virtual machine. At deployment time, the vSphere administrator selects the VM Storage Policyappropriate for the needs of that virtual machine. SPBM will push the requirements down to the storage layer.Datastores that provide the capabilities placed in the VM Storage Policy are made available for selection. Thismeans that the virtual machine is always instantiated on the appropriate underlying storage based on therequirements placed in the VM Storage Policy. If the virtual machine’s workload changes over time, it issimply a matter of applying a policy to the virtual machine with new, updated requirements that reflect thenew workload.This document thoroughly examines VSAN, which provides storage services by utilizing local disks on vSphere hosts.T ECHNICAL W HI T E P A P E R / 4
What’s New in VMware Virtual SAN (VSAN)1.3 What is VSAN?VSAN is a new storage solution from VMware that is fully integrated with vSphere. It automatically aggregatesserver disks in a cluster to create shared storage that can be rapidly provisioned from VMware vCenter duringVM creation. It is an object-based storage system and a platform for VM Storage Policies designed to simplifyvirtual machine storage placement decisions for vSphere administrators. It is fully integrated with core vSpherefeatures such as VMware vSphere High Availability (vSphere HA), VMware vSphere Distributed Resource Scheduler (vSphere DRS) and VMware vSphere vMotion . Its goal is to provide both high availability and scale-out storagefunctionality. It can also be considered in the context of quality of service (QoS) because VM Storage Policies canbe created that define the level of performance and availability required on a per–virtual machine basis.2. RequirementsThe following section details the hardware and software requirements that must be met to create a VSAN cluster.2.1 vSphere Requirements2.1.1 vCenter ServerVSAN requires at a minimum that the VMware vCenter Server version is 5.5. Both the Microsoft Windowsversion of vCenter Server and the VMware vCenter Server Appliance can manage VSAN. VSAN is configuredand monitored via the VMware vSphere Web Client and this also requires version 5.5.2.1.2 vSphereVSAN requires at least three vSphere hosts (in which each host has local storage) to form a supportedVSAN cluster. This enables the cluster to meet the minimum availability requirement of at least one host, disk,or network failure tolerated. The vSphere hosts requires at a minimum vSphere version 5.5.2.2 Storage Requirements2.2.1 Disk ControllersEach vSphere host participating in the VSAN cluster requires a disk controller. This can be a SAS/SATA host busadapter (HBA) or a RAID controller. However, the RAID controller must function in what is commonly referred toas pass-through mode or HBA mode. In other words, it must be able to pass up the underlying hard disk drives(HDDs) and solid-state drives (SSDs) as individual disk drives without a layer of RAID sitting on top. This isnecessary because VSAN will manage any RAID configuration when policy attributes such as availability andperformance for virtual machines are defined. The VSAN Hardware Compatibility List (HCL) will call out thecontrollers that have passed the testing phase.Each vSphere host in the cluster that contributes its local storage to VSAN must have at least one HDD and atleast one SSD.2.2.2 Hard Disk DrivesEach vSphere host must have at least one HDD when participating in the VSAN cluster. HDDs make up thestorage capacity of the VSAN datastore. Additional HDDs increase capacity but might also improve virtualmachine performance. This is because virtual machine storage objects might be striped across multiple spindles.This is covered in far greater detail when VM Storage Policies are discussed later in this paper.2.2.3 Solid-State DisksEach vSphere host must have at least one SSD when participating in the VSAN cluster. The SSD provides both awrite buffer and a read cache. The more SSD capacity the host has, the greater the performance, because moreI/O can be cached.NOTE: The SSDs do not contribute to the overall size of the distributed VSAN datastore.T ECHNICAL W HI T E P A P E R / 5
What’s New in VMware Virtual SAN (VSAN)2.3 Network Requirements2.3.1 Network Interface CardsEach vSphere host must have at least one network interface card (NIC). The NIC must be 1Gb capable. However,as a best practice, VMware is recommending 10Gb NICs. For redundancy, a team of NICs can be configured on aper-host basis. VMware considers this a best practice but does not deem it necessary when building a fullyfunctional VSAN cluster.2.3.2 Supported Virtual Switch TypesVSAN is supported on both the VMware vSphere Distributed Switch (VDS) and the vSphere Standard Switch(VSS). No other virtual switch types are supported in the initial release.2.3.3 VMkernel NetworkOn each vSphere host, a VMkernel port for VSAN communication must be created. The VMkernel port is labeledVirtual SAN. This port is used for intercluster node communication and also for reads and writes when one of thevSphere hosts in the cluster owns a particular virtual machine, but the actual data blocks making up the virtualmachine files are located on a different vSphere host in the cluster. In this case, I/O must traverse the networkconfigured between the hosts in the cluster.3. Install and ConfigureThis chapter includes a detailed description of the install and configure process, along with any initialpreparation that might be required before deployment of a VSAN cluster.3.1 Creating a Virtual SAN ClusterThe creation of a VSAN cluster requires many of the same steps a vSphere administrator might take to set up aDRS or vSphere HA cluster. A cluster object is created in the vCenter server inventory, and one can either chooseto enable the VSAN cluster functionality and then add in the hosts to the cluster or add the hosts first and thenenable VSAN. When you enable the VSAN functionality, a single option is displayed asking the administrator tochoose a manual or automatic cluster. This gives the vSphere administrator an option: They can assign VSAN todiscover all the local disks on the hosts and automatically add the disks to the VSAN datastore or theadministrator can opt to manually select the disks to add to the cluster.3.1.1 Manually Add Disks to Disk GroupsIf this option is selected, the VSAN cluster is still formed. However, the VSAN datastore is 0 bytes in size initially.The administrator must manually create disk groups on a per-host basis and add at least one HDD and at mostone SSD disk to each of the disk groups. Each disk group can only contain a single SSD, so there might bemultiple disk groups, each containing an SSD and any number of HDDs. After each disk group is created on aper-host basis, the size of the VSAN datastore will grow according to the amount of HDD that is added.NOTE: The SSDs function as read caches and write buffers and are not included in the capacity of theVSAN datastore.3.1.2 Automatic Creation of Disk GroupsIf an automatic method is chosen to create the VSAN cluster, VSAN will automatically discover local HDDs andSSDs on each host and build disk groups on every host in the cluster. All hosts with valid storage have a diskgroup containing their local HDDs and SSDs. Finally, after this is completed, the VSAN datastore is createdand its size reflects the capacity of all the HDDs across all the hosts in the cluster, except for somemetadata overhead.Hosts that do not have valid storage or no storage can still access the VSAN datastore. This is a veryadvantageous feature of VSAN, because a VSAN cluster can now also be scaled on compute requirements,not just on storage requirements.T ECHNICAL W HI T E P A P E R / 6
What’s New in VMware Virtual SAN (VSAN)3.1.3 Virtual SAN Cluster Creation ExampleAfter the host, storage and networking requirements are met, the creation of the VSAN cluster can commence.As mentioned, the configuration is very much the same as the creation of a vSphere HA or DRS cluster, and it isuser interface (UI) driven. To create a VSAN cluster, create a cluster object in the vCenter inventory, add thevSphere hosts to the cluster object that you intend to have participate in the VSAN, and enable VSAN on the cluster.Figure 1. Create a New VSAN Cluster3.2 The Virtual SAN Datastore3.2.1 VSAN Datastore PropertiesThe size of a VSAN datastore is governed by the number of HDDs per vSphere host and the number of vSpherehosts in the cluster. There is also some metadata overhead to consider. For example, if a host has 6 x 2TB HDDsand there are eight hosts in the cluster, the raw capacity would be 6 x 2TB x 8 96TB of raw capacity.The number of supported disks per host and the number of hosts in the cluster govern the maximum size of aVSAN datastore.After the VSAN datastore is formed, a number of datastore capabilities are surfaced up into vCenter Server.These include stripe width, component failures to tolerate, force provisioning and proportional capacity. Thestorage layer is surfacing what it can support in terms of performance, availability and provisioning. Thesecapabilities will be discussed in greater detail later in this paper, but for now it’s important to know that they canbe used to create a virtual machine policy that defines the storage requirements of a virtual machine. Further,they enable a vSphere administrator to now specify other capabilities that must be provided by the underlyingstorage, including performance, availability and data services, during the virtual machine provisioning process.All of this enables the administrator to select the correct storage for that virtual machine.3.3 Defining Virtual Machine RequirementsOn creation of the VSAN cluster, a vsanDatastore is also created. The vsanDatastore has a set of capabilities thatit surfaces up to vCenter.When a vSphere administrator sets out to design a virtual machine, the application that runs in that virtualmachine will have a set of requirements, including storage requirements.The vSphere administrator uses a VM Storage Policy to specify the application’s storage requirements. TheVM Storage Policy contains storage requirements in the form of a set of the storage capabilities.The VM Storage Policy indicates which of these storage capabilities the virtual machine must have to meet theapplication’s storage requirements.In effect, then, storage provides capabilities and virtual machines consume them via requirements placed in theVM Storage Policy.T ECHNICAL W HI T E P A P E R / 7
What’s New in VMware Virtual SAN (VSAN)4. Architecture Details4.1 Distributed RAIDIn traditional storage environments, redundant array of independent disks (RAID) refers to disk redundancyinside the storage chassis to withstand the failure of one or more disk drives. A VSAN cluster uses the conceptof distributed RAID, whereby an environment can now contend with the failure of a vSphere host—orcomponents within that host such as a disk drive or network interface—and continue to provide completefunctionality for all virtual machines. Availability is now defined on a per–virtual machine basis through the useof VM Storage Policies, with which vSphere administrators can define how many host, network or disk failures avirtual machine can tolerate in a VSAN cluster. If an administrator sets a zero capability in the VM Storage Policy,a host or disk failure can impact the availability of a virtual machine.Using VM Storage Policies along with VSAN distributed RAID architecture—whereby copies of the virtualmachine and its contents can reside on multiple nodes in the cluster—it is not necessary to migrate data on afailing node to other nodes in the cluster in the event of a failure.4.2 Witnesses and ReplicasReplicas are copies of the virtual machine storage objects that are instantiated when an availability capability isspecified for the virtual machine. The availability capability dictates how many replicas are created. It enablesvirtual machines to continue running with a full complement of objects when there are host, network or diskfailures in the cluster.Witnesses are part of every storage object. They are components that do not contain data, only metadata. Theirpurpose is to serve as tiebreakers when availability decisions are made in the VSAN cluster. A witness consumesabout 2MB of space for metadata on the VSAN datastore.NOTE: For an object to be accessible in VSAN, more than 50 percent of its components must be accessible.4.3 The Role of Solid-State DisksSolid-state disks (SSDs) have two purposes in Virtual SAN. These are to provide a read cache and a write buffer.This dramatically improves the performance of virtual machines. In some respects, VSAN can be compared to anumber of “hybrid” storage solutions in the market, which also use a combination of SSD and HDD storage toboost the performance of the I/O and which have the ability to scale out based on low-cost HDD storage.4.3.1 Purpose of Read CacheThe read cache keeps a cache of commonly accessed disk blocks. This reduces the I/O read latency in the eventof a cache hit. The actual block that is read by the application running in the virtual machine might not be on thesame vSphere host on which the virtual machine is running. To handle this situation, VSAN distributes adirectory of cached blocks between vSphere hosts in the VSAN cluster. This enables a vSphere host todetermine if another host has data cached that is not in local cache. If this is the case, the vSphere host canretrieve cached blocks from another host over the interconnect. If the block is not in cache on any VSAN host, itis retrieved directly from the HDD.4.3.2 Purpose of Write CacheThe write cache behaves as a nonvolatile write buffer. The fact that we can use SSD storage for writes alsoreduces the latency for write operations.Because the writes go to SSD storage, we must of course ensure that there is a copy of the data elsewhere in theVSAN cluster. All virtual machines deployed to VSAN have an availability policy setting ensuring that at least oneadditional copy of the virtual machine data is available. This includes the write cache contents.T ECHNICAL W HI T E P A P E R / 8
What’s New in VMware Virtual SAN (VSAN)After a write is initiated by the application running inside of the guest operating system (OS), the write is sentin parallel to both the local write cache on the owning host and also to the write cache on the remote host(s).The write must be committed to the SSD on both hosts before it is acknowledged.This means that in the event of a host failure, we also have a copy of the data on another SSD in the VSANcluster so that no data loss will occur. The virtual machine will access the replicated copy of the data on anotherVSAN host via the VSAN interconnect.5. Storage Policy Based ManagementIn the introduction, it was mentioned that Storage Policy Based Management (SPBM) now plays a major role inthe policies and automation for the software-defined storage vision of VMware. Using VM Storage Policies,administrators can specify a set of required storage capabilities for a virtual machine, or more specifically a setof requirements for the application running in the virtual machine. This set of required storage capabilities ispushed down to the storage layer, which then checks where the storage objects for that virtual machine can beinstantiated to match this set of requirements. For instance, are there enough stripe widths available in thecluster if this virtual machine requires it? Or are there enough hosts in the cluster to provide the number offailures to tolerate? If the VSAN datastore understands the capabilities placed in the VM Storage Policy, it is saidto be a matching resource and is highlighted as such in the provisioning wizard. Subsequently, when the virtualmachine is deployed, if the requirements in the VM Storage Policy attached to the virtual machine can be met bythe VSAN datastore, the datastore is said to be compliant from a storage perspective in its own summarywindow. If the VSAN datastore is overcommitted or cannot meet the capability requirements, it might still beshown as a matching resource in the deployment wizard, but the provisioning task might fail.SPBM now provides an automated, policy-driven mechanism for selecting an appropriate datastore for virtualmachines, based on the required storage capabilities placed in the VM Storage Policies.5.1 Virtual SAN CapabilitiesThis section examines the required storage capabilities that can be placed in a VM Storage Policy. Thesecapabilities, which are surfaced by the VSAN datastore when the cluster is configured successfully, highlightthe availability, performance and sizing requirements that can then be required of the storage on a per–virtualmachine basis.If you do not correctly state the requirements—in other words, if you put a capability in the storage level thatcannot be detected by the VSAN datastore—the VSAN datastore no longer appears as a matching resourceduring provisioning.5.1.1 Number of Failures to TolerateThis property requires the storage object to tolerate at least NumberOfFailuresToTolerate of concurrent host,network or disk failures in the cluster and still ensure availability of the object.If this property is populated, it specifies that configurations must contain at least NumberOfFailuresToTolerate 1replicas and might also contain an additional number of witness objects to ensure that the object’s data is available(to maintain quorum in cases of split-brain), even in the presence of as many as NumberOfFailuresToTolerateconcurrent host failures. Therefore, to tolerate n failures, at least (n 1) copies of the object must exist and atleast (2n 1) hosts are required.NOTE: Any disk failure on a single host is treated as a “failure” for this metric. Therefore, the object cannotpersist if there is a disk failure on host A and another disk failure on host B when you haveNumberOfFailuresToTolerate set to 1.T ECHNICAL W HI T E P A P E R / 9
What’s New in VMware Virtual SAN (VSAN)5.1.2 Number of Disk Stripes per ObjectThis defines the number of physical disks across which each replica of a storage object is distributed. A valuehigher than 1 might result in better performance if read caching is not effective, but it will also result in a greateruse of system resources.To understand the impact of Disk Stripes, we examine it first in the context of write operations and then in thecontext of read operations. Because all writes go to the SSD write buffer, the value of
The plan of VMware for software-defined storage is to focus on a set of VMware initiatives around local storage, shared storage and storage/data services. In essence, we want to make VMware vSphere a platform for storage services. Software-defined storage is designed to provide storage services and service-level agreement automation
2.7 VMware vCenter Support Assistant 22 2.8 VMware Continuent 23 2.9 VMware Hyper-Converged Infrastructure Kits 23 2.10 VMware Site Recovery Manager 23 2.11 VMware NSX 24 2.12 VMware NSX Advanced Load Balancer 28 2.13 VMware SD-WAN by VeloCloud 29 2.14 VMware Edge Network Intelligence 30 2.15 VMware NSX Firewall 30
the VMware Hybrid Cloud Native VMware management tools extend on-prem services across VMware Hybrid Cloud vRealize adapters allow "first class citizen" status for VMware Cloud on AWS Leverage same in-house VMware tools and processes across VMware Hybrid Cloud Support the cloud agility strategy of the organisation without disruption
8. Install VMware Fusion by launching the “Install VMware Fusion.pkg”. 9. Register VMware Fusion when prompted and configure preferences as necessary. 10. Quit VMware Fusion. Create a VMware Fusion Virtual Machine package with Composer 1. Launch VMware Fusion from /Applications. 2. Cre
VMware, Inc. 9 About ThisBook The Guest Operating System Installation Guide provides users of VMware ESX Server, VMware GSX Server, VMware Server, VMware ACE, VMware Workstation, and VMware Fusion information about installing guest operating systems in
VMware View 18 VMware Mirage 21 VMware Workspace 24 Summary 25 Chapter 2 VMware View Architecture 27 Introduction 27 Approaching the Design and Architecture 27 Phase I: Requirements Gathering and Assessment 28 Phase II: Analysis 29 Phase III: Calculate 30 Phase IV: Design 32 VMware View Server Architecture 33 VMware View Connection Server 34
VMware also welcomes your suggestions for improving our other VMware API and SDK documentation. Send your feedback to: docfeedback@vmware.com. . , and can assist development of applications for VMware vSphere and vCloud. The user interface retains . In the VMware Developer Center, find the introduction page for VMware Workbench IS. At the .
Fundamentals Associate VMware Data Center Virtualization Associate VMware Cloud Management and Automation Associate VMware Security. Design Expert Certification (VCDX) Certification . VMware Data Center Virtualization: Core Technical Skills VCTA-DCV VMware vSphere: Install, Configure, Manage vSphere Professional VMware Advanced
VMware ESX Server uses a virtual disk file format different from the format used by VMware products that run on a host operating system—such as VMware GSX Server, VMware Server, VMware Player, VMware Workstation, and VMware Fusion. As a result, when you move a virtual machine from a system
