c783e10594
This commit also generally cleans up the Installation docs and uses /includes/<platform>/steps-*.rst as a pattern for storing platform-specific tutorials within a single root URL. Finally, due to API rate limits, this commit adds some Makefile magic to allow skipping of sync'ing dependencies. Pass `make BUILD_DEPENDENCIES=FALSE <platform>` to skip building any deps and use what is already in the branch.
2.1 KiB
Deploy MinIO: Single-Node Multi-Drive
minio
Table of Contents
The procedures on this page cover deploying MinIO in a Single-Node
Multi-Drive (SNMD) configuration. This topology provides increased
drive-level reliability and failover protection as compared to Single-Node Single-Drive (SNSD) deployments <minio-snsd>.
linux or macos or windows
For production environments, MinIO strongly recommends deploying with
the Multi-Node Multi-Drive (Distributed) <minio-mnmd>
topology.
container
For production environments, MinIO strongly recommends using the MinIO Kubernetes Operator to deploy Multi-Node Multi-Drive (MNMD) or "Distributed" Tenants.
Prerequisites
Local JBOD Storage with Sequential Mounts
Network File System Volumes Break Consistency Guarantees
MinIO's strict read-after-write and list-after-write consistency model requires local disk filesystems.
MinIO cannot provide consistency guarantees if the underlying storage volumes are NFS or a similar network-attached storage volume.
For deployments that require using network-attached storage, use NFSv4 for best results.
Deploy Single-Node Multi-Drive MinIO
The following procedure deploys MinIO consisting of a single MinIO server and a multiple drives or storage volumes.
linux
macos
container