0cd491c328
Updates `mc` reference docs for several releases of the MinIO Client.
- Adds missing flags to `mc admin trace`
- Updates `disk` -> `drive` throughout the docs, but not in all cases.
- Adds `--airgap flag` to `mc support profile` and `mc support perf`
commands.
- Updates the flags for `mc ilm add` command
- Adds `mc license unregister` command.
Closes #571
Closes #614
Closes #627
Closes #633
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. deployments provide drive-level reliability and failover/recovery with performance and scaling limitations imposed by the single node.
linux or macos or windows
For production environments, MinIO strongly recommends deploying with
the Multi-Node Multi-Drive (Distributed) <minio-mnmd>
topology for enterprise-grade performance, availability, and
scalability.
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 drive 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