![]() Do note, that you can change the Storage Policy (For instance, changing the RAID from RAID 1 to RAID 5), while you undergo this migration. Once a mesh relationship has been established, a simple Storage vMotion is all that is required to migrate a Virtual Machine's storage to a remote vSAN cluster datastores. This allows for an easy understanding of what type of storage may be available to multiple vSAN clusters connected by HCI Mesh. When defining a storage policy, an administrator will be able to define the types of data services they are interested in (such as Deduplication and Compression, or Data-at-rest Encryption), and the storage policy wizard will filter out the available datastores that meet that criteria – assuming there are multiple remote datastores already mounted at the time of VM provisioning and policy selection. One of the most interesting capabilities, as it relates to HCI Mesh, is the integration with storage policies. Most importantly, HCI Mesh compute clusters do not need any vSAN licensing. HCI Mesh compute clusters use native vSAN protocols for maximum efficiency and affords the customer the ability to easily meet a broad variety of use cases. HCI Mesh compute clusters can consume storage resources provided by a remote vSAN cluster, in the same way, that multiple vSphere clusters can connect to a traditional storage array. In vSAN 7 U2, traditional vSphere clusters can mount a remote vSAN datastore. ![]() Storage is still managed and maintained as a cluster resource.ĭeploy VMware vSAN HCI Mesh Compute Cluster ![]() The vSAN performance service can allow for end to end monitoring of IO.Ĥ. There is no need to manage islands of storage within LUNs or NFS exports, and no need for datastore clustering or VAAI to try to work around issues that would come from adding another layer of abstraction.ĥ. Lower compute and IO overhead is preserved by using the native vSAN RDT protocol end to end.ģ. SPBM management is preserved end to end.Ģ. While vSAN can export iSCSI or NFS, the native vSAN protocol was chosing to export storage to another cluster for a number of reasons:ġ. While vMotion enables “Shared nothing migration” between clusters, this still forced storage and compute to move together between clusters. Historically, when these scaling events happen it could cause an existing clusters to run out of storage or compute and potentially strand the lower demanded resource.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |