Complete Your Software Defined Storage Strategy with MinIO Object Storage and VMware vSAN

MinIO can run on almost all hardware profiles. Our recommended partners are listed here.

We recommend the following:

• CPUs/Node: 2 Xeon Gold CPUs with 8 cores per CPU
• NIC/Node: 25GbE for High Density
• Memory/Node: 128GB
• Drives/Node: Minimum 8 HDD (16TiB/drive)
• Minimum No of Nodes per Cluster: 4
• HW OEM Options: Please refer to the HW OEMs listed here for High Density - https://min.io/product/reference-hardware

MinIO integrated with vSphere leverages the Data Persistency Platform to create multiple instances of MinIO to allow for isolated multiple tenants to be on boarded on the same vSphere install. Each tenant lives in their own namespace and the VI admin can carve resources, set quotas and assign them to each tenant.

MinIO’s encryption functionality is implemented at the object layer and is designed for high-performance I/O. Objects are independently encrypted each with their own keys. Applications can choose to supply these encryption keys from the client side, or via an external Key Management Service. You do not need vSAN encryption when MinIO’s encryption is turned on.

Running MinIO as a guest cluster is not recommended but it is possible. MinIO will need storage on the nodes exposed either through vSphere CSI driver or from VM local storage using Direct CSI driver.

Apps connect to an S3 endpoint which is provided in the MinIO instance plugin UI with virtual hosted style requests. MinIO is strictly consistent and has no bucket limitation. Multiple MinIO clusters can be deployed on the same bare metal or Kubernetes platform to achieve multi-tenancy as well if more separation is required.

MinIO’s server-side replication feature supports both active-passive and active-active configurations to keep two data-centers in sync continuously. Objects are replicated immediately as long as there is sufficient bandwidth.

MinIO provides continuous data protection capability with built-in object versioning, immutability and server-side replication. You can roll back objects to any point in time without ever performing snapshots. Remote site is continuously kept in sync including the object version history. Since MinIO itself is a popular backup target, it is important to eliminate the need for yet-another backup storage tier.

Object Storage is typically backed up to another cluster in a geographically distant location. Cost will depend on the needs of the backup, i.e. does it need to be active-active replication backup or is it purely archival. In either case the cost is directly related to the amount of hardware needed for the backup. So, if all data does not need to be backed up, less hardware can be used on the DR site. If MinIO is being backed up to a cloud provider such as AWS S3, then the cost is specific to the provider.

Best practices related to replication and backups tend to be application and customer specific, however please see the following resources.

https://github.com/minio/minio/blob/master/docs/bucket/replication/DESIGN.md and https://docs.min.io/minio/baremetal/replication/replication-overview.html for a detailed guide.

MinIO supports object expiry and transition via its ILM APIs. Objects are chosen for archival based on the object tags, expiry timeline and object name prefixes. API allows you to setup richer rules to selectively expire and transition the objects to a remote low-cost HDD based MinIO site.

MinIO supports disaster recovery planning through its server-side replication functionality. You can pair buckets with remote MinIO setups to keep them in sync continuously.

MinIO uses Erasure Coding to evenly distribute all objects across the available servers. Spare nodes are not necessary in this configuration.

The MinIO Subscription Network can be found here. VMware requires a license key for all ISVs on the vSAN Data Persistence platform. There is a 60 day trial period, during which the enterprise will be automatically onboarded to SUBNET.

VMware requires that all of the ISVs on the vSAN Data Persistence platform offer licensing terms and product support independently of VMware. Information on the MinIO Subscription Network can be found here.

MinIO is a highly-available distributed object storage system. It can tolerate multiple node and drive failures through its erasure-code and bitrot protection mechanism.

vSAN can offer usage consumption for the storage pools that host MinIO. Capacity for vSAN SNA and vSAN Direct is thick provisioned where the entire capacity needed is pre provisioned for MinIO. For further breakdown of the used capacity, MinIO Console provides a bucket level summary of used capacity.

MinIO is the world’s fastest object store. Benchmarks can be found here.

Example results of MinIO HDD Cluster Performance:

• Read throughput: 16.3GB/s
• Write throughput: 9.4GB/s

Please see the reference hardware page for various calculators. Please note that the calculators do not include VMware vSAN DPP related license costs.

We recommend a cluster built using NVMe based drives with 100GbE NIC.

Please refer to the below recommendation for NVMe cluster:

• CPUs/Node: 2 Xeon Gold CPUs with 8 cores per CPU
• NIC/Node: 100GbE
• Memory/Node: 128GB
• Drives/Node: Minimum 8 NVMe (7.6TiB+ / drive)
• Minimum No of Nodes per Cluster: 4
• HW OEM Options: Please refer to the HW OEMs listed here for Performance - https://min.io/product/reference-hardware

Note: For this recommendation, we need to take into account any Kubernetes Master Node configuration requirements, which are not addressed in the list above.

For large scale clusters, this is a function of primarily the drive used for MinIO Object Storage. NVMe SSD is more expensive than HDD clusters. But the cost of NVMe is coming down significantly. The $/GiB also depends on the Erasure Coding configuration used in the cluster.

Note: MinIO doesn’t have any NVMe related calculator published. But the NVMe costs at a high level can be accessed here.

Customers can use the erasure code calculator to calculate usable capacity for a variety of configurations.

MinIO is light on CPU and memory usage (recommended 16 CPU / 128GB RAM per server). Throughput is almost always bottlenecked on the network. Please refer to the link below for MinIO guidance on sizing.

https://core.vmware.com/resource/minio-object-storage-vmware-cloud-foundation-tanzu#sizing-guidelines

Generally, more pods and PVs lead to more parallelism that improves performance. The number is limited by physical resources.

MinIO looks at tenancy more from a resource management perspective (i.e. storage class or buckets). Most applications only require the endpoint and bucket to function. Multi-tenancy is useful to group similar applications, groups or users from resource management (i.e reporting) as well as operational management. There are no technical limitations restricting the sharing of many buckets in a large MinIO deployment.

This is dependent on the operational needs of a given organization. Many applications to a single instance will typically be used in scenarios where multiple groups from the same organization want to utilize a single cluster with resource access defined via IAM policies. This use case can be simpler operationally as there is only a single cluster to manage. Using unique instances for a given application is typically deployed for two use cases. The first, when you wish to have complete isolation of data, for example when providing MinIO services to end customers, you may wish to ensure that an incorrect policy application does not allow one customer to see another customer's data. The second is when you want to have different configurations for each unique cluster. One example would be to allow for different erasure code parity settings for non-critical data in one cluster, and higher redundancy for another cluster with business critical data.

Multi-user vs Multi-tenancy options available for customers to deploy MinIO in a variety of configurations without negatively impacting the performance of the system.

MinIO Policy-Based Access Control (PBAC) supports granular isolation of user access down to the bucket or bucket prefix. For applications that require exclusive access to object storage, you can deploy a MinIO tenant for supporting only those applications. For example:

• Applications write to the same bucket on a single tenant.
• Applications write to their own bucket on a single tenant.
• Applications write to their own MinIO Tenant.
• Storage and compute resources are exclusive to each tenant

For more information, see:

• MinIO Multi-User Guide
• MinIO Identity and Access Management
• Deploy a MinIO Tenant (VMware Cloud Foundation 4.2)

Data durability by most cloud storage vendors offers 11 nines of reliability. MinIO is designed from the ground up to be a drop-in replacement for AWS S3 service for various deployment methods and using similar commodity HW and features (i.e. EC and replication) MinIO can easily provide 11 9s of durability. Due its object-level granularity based on some calculations it is possible to even provide better durability but this would require very conservative erasure coding (EC) configurations which may be not practical or cost effective.

11 9s of durability (99.999999999) translates into about 12 objects lost per year per PiB. This can easily be prevented by using N/2 EC configuration and at a minimum of 2x site replication.

Basic calculations around erasure coding (EC) and its impact on durability can be found here.

MinIO can be deployed in multiple availability zones via replication. Multiple MinIO instances (or tenants) can be deployed against disparate Kubernetes / VMware clusters that are deployed in various zones or regions of the overall Global Data Center footprint. Any given MinIO tenant should reside in a single vSphere cluster. Multiple tenants can exist in a single cluster. Stretch clusters are not recommended. MinIO supports active-active replication between independent tenants, where objects written to one tenant are automatically synchronized to the remote. Documentation can be found here.

MinIO supports both sync and async replications across multiple sites. Choice will depend on each customer's latency and throughput availability across these data centers, availability zones (AZs) or sites in general.

The performance cost for synchronous replication will be directly related to available throughput and intersite network latency since the application will have to wait for the roundtrip to complete.

Durability cost for asynchronous will be similarly impacted by available throughput and network latency but since MinIO implements object-level granularity this minimizes the impact compared to other async approaches.

MinIO EC is configured at Tenant creation as part of the Tenant Size step. Select the Erasure Code Parity setting to use for the initial Zone. MinIO has an Erasure Code Calculator to assist in selecting an appropriate parity setting based on the desired Zone topology.

When expanding a tenant, the new Zone inherits its EC setting from the Tenant. MinIO requires that the new zone have a sufficient number of drives to support the Tenant EC. Specifically, the new zone must have at least 2x the number of drives to support the same EC configuration as the existing Zone’s EC in that particular tenant.

You can set up replication at any time after deploying the MinIO Tenant. MinIO server-side replication requires a MinIO service as the replication target. MinIO has documented procedures for One-Way Active-Passive and Two-Way Active-Active replication.

MinIO also provides the mc mirror tool for performing client-side content synchronization to any S3-compatible service.

The MinIO plugin tenant tab will indicate when an update is available. Customers can simply click on the UI to trigger the rolling instance upgrade. There is no service interruption.

MinIO scales seamlessly from TiB to PiB. To learn more about the details we suggest this documentation.

Customers can also modify the vCPU allocation for the tenant. Please refer to this documentation for additional information.

Customers can also add more vSAN direct drives to scale capacity for each ESXi server. ESXi servers may also be expanded to accommodate capacity requirements.

For single disk failures there is no performance impact. In general, the rebuild workload takes a lower priority if there is an active workload that is happening in parallel. This process is completely executed in the background with no active management requirement by the customers.

No. Rebalancing is not required with MinIO.

Please see the compatibility matrix below. The Operator upgrade must stay within the boundary of each row to keep all components in check. If user wants to upgrade MinIO Operator to the latest that cross different rows, need to upgrade the vDPp plugin as well, plugin upgrades are currently not handled from UI.