1
0
mirror of https://github.com/minio/docs.git synced 2025-07-11 06:02:00 +03:00
Files
docs/source/includes/container/installation.rst
Ravind Kumar 31bd45f20f DOCS-1084: Fix deployment menus for Windows, macos, containers, Add s… (#1108)
…cript for xfs settings to Linux"

Closes #1084 

Accomplishing a few things here:

1. General tidy-up of the installation pages so Windows/Container/MacOS
only display the appropriate deployment topos
2. Better admonitions/guidance on when to use what distribution
3. Added a section on Storage + XFS Settings to resolve an ongoing
customer request


---------

Co-authored-by: Daryl White <53910321+djwfyi@users.noreply.github.com>
Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
2024-01-23 14:12:11 -05:00

4.3 KiB

Install and Deploy MinIO

minio

Table of Contents

MinIO is a software-defined high performance distributed object storage server. You can run MinIO on consumer or enterprise-grade hardware and a variety of operating systems and architectures.

MinIO supports three deployment topologies:

Single-Node Single-Drive (SNSD or "Standalone")

A single MinIO server with a single storage volume or folder. |SNSD| deployment provides failover protections. Drive-level reliability and failover depends on the underlying storage volume.

|SNSD| deployments are best suited for evaluation and initial development of applications using MinIO for object storage.

|SNSD| deployments implement a zero-parity erasure coding backend and include support for the following erasure-coding dependent features:

  • Versioning <minio-bucket-versioning>
  • Object Locking / Retention <minio-object-retention>
Single-Node Multi-Drive (SNMD or "Standalone Multi-Drive")

A single MinIO server with four or more storage volumes. |SNMD| deployments provide drive-level reliability and failover only.

Multi-Node Multi-Drive (MNMD or "Distributed")

Multiple MinIO servers with at least four drives across all servers. The distributed |MNMD| topology supports production-grade object storage with drive and node-level availability and resiliency.

Note

This documentation provides instructions for |SNSD| and |SNMD| for supporting local development and evaluation of MinIO on a single host machine only. For |MNMD| deployments, use the MinIO Kubernetes Operator to deploy and manage MinIO tenants in a containerized and orchestrated environment <minio/kubernetes/upstream/operations/installation.html>.

Site Replication

Site replication <minio-site-replication-overview> links multiple MinIO deployments together and keeps the buckets, objects, and Identity and Access Management (IAM) settings in sync across all connected sites.

Important

MinIO does not recommend using |platform| hosts for site replication outside of early development, evaluation, or general experimentation. For production, use Kubernetes <minio/kubernetes/upstream/operations/install-deploy-manage/multi-site-replication.html> for an orchestrated container environment.

What Does Not Replicate?

Not everything replicates across sites.

Platform Support

MinIO provides container images at the following repositories:

RELEASE.2022-12-02T19-19-22Z

These images include the MinIO Client <minio-client> command line tool built in for container-level debugging. However, to regularly interact with a container MinIO install, install the MinIO Client <mc-install> on your computer and define an alias <mc alias set> to the container instead.

Use of MinIO images from any other repository, host, or organization is at your own risk.

The Single-Node Single-Drive <minio-snsd> and Single-Node Multi-Drive <minio-snmd> tutorials provide instructions for the Docker and Podman <> container managers.

/operations/install-deploy-manage/deploy-minio-single-node-single-drive /operations/install-deploy-manage/deploy-minio-single-node-multi-drive