Storage Considerations for VMware Cloud Foundation with FlashArray

This post was originally published on Pure Storage

If you’re currently using VMware Cloud Foundation or have been considering what to do differently with your vSphere environment to maximize your investment, storage has undoubtedly come up as a factor. In this post, I want to clarify the storage options and use cases to help you make a more informed decision.

Principal and Supplemental Storage Explained

Before diving into how FlashArray™ can simplify VMware Cloud Foundation (VCF) storage configurations and options, I would like to level set on terms that VMware has implemented when discussing storage and VCF:

Principal storage: When creating a workload domain or a new cluster in an existing workload domain, all ESXi hosts require access and configuration to at least one shared storage type. This initial storage type is referred to as principal storage and is selected during the creation process of either the workload domain or the new cluster. Supplemental storage: Storage that is added to the workload domain or cluster after it has been implemented is referred to as supplemental storage.

Going even further, with each storage classification, there are supported and unsupported storage protocols that can be used for management domains and workload domains. To avoid an eye chart, below

Read the rest of this post, which was originally published on Pure Storage.

Previous Post

Cloud Attackers Exploit Max-Critical Aviatrix RCE Flaw

Next Post

How to Get Better Data Insights with AI-Driven SQL