mirror of
https://github.com/minio/docs.git
synced 2025-04-21 08:05:59 +03:00
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
65 lines
2.1 KiB
ReStructuredText
65 lines
2.1 KiB
ReStructuredText
.. _minio-snmd:
|
|
|
|
=====================================
|
|
Deploy MinIO: Single-Node Multi-Drive
|
|
=====================================
|
|
|
|
.. default-domain:: minio
|
|
|
|
.. contents:: Table of Contents
|
|
:local:
|
|
:depth: 2
|
|
|
|
The procedures on this page cover deploying MinIO in a Single-Node Multi-Drive (SNMD) configuration.
|
|
|SNMD| deployments provide drive-level reliability and failover/recovery with performance and scaling limitations imposed by the single node.
|
|
|
|
.. cond:: linux or macos or windows
|
|
|
|
For production environments, MinIO strongly recommends deploying with the :ref:`Multi-Node Multi-Drive (Distributed) <minio-mnmd>` topology for enterprise-grade performance, availability, and scalability.
|
|
|
|
.. cond:: container
|
|
|
|
For production environments, MinIO strongly recommends using the MinIO Kubernetes Operator to deploy Multi-Node Multi-Drive (MNMD) or "Distributed" Tenants.
|
|
|
|
Prerequisites
|
|
-------------
|
|
|
|
.. _deploy-minio-standalone-multidrive:
|
|
|
|
Local JBOD Storage with Sequential Mounts
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
.. |deployment| replace:: deployment
|
|
|
|
.. include:: /includes/common-installation.rst
|
|
:start-after: start-local-jbod-single-node-desc
|
|
:end-before: end-local-jbod-single-node-desc
|
|
|
|
.. admonition:: Network File System Volumes Break Consistency Guarantees
|
|
:class: note
|
|
|
|
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.
|
|
|
|
.. cond:: linux
|
|
|
|
.. include:: /includes/linux/steps-deploy-minio-single-node-multi-drive.rst
|
|
|
|
.. cond:: macos
|
|
|
|
.. include:: /includes/macos/steps-deploy-minio-single-node-multi-drive.rst
|
|
|
|
.. cond:: container
|
|
|
|
.. include:: /includes/container/steps-deploy-minio-single-node-multi-drive.rst |