1
0
mirror of https://github.com/minio/docs.git synced 2025-04-24 06:05:11 +03:00
docs/source/includes/common/installation.rst
Ravind Kumar c783e10594 DOCS-492: Container Platform Docs
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.
2022-07-18 17:46:59 -04:00

5.1 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. deployment provides failover protections. Drive-level reliability and failover depends on the underlying storage volume.

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

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. 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 topology supports production-grade object storage with drive and node-level availability and resiliency.

For tutorials on deploying or expanding a distributed MinIO deployment, see:

  • deploy-minio-distributed
  • expand-minio-distributed

The following table compares the key functional differences between MinIO deployments:

Single-Node Single-Drive Single-Node Multi-Drive Multi-Node Multi-Drive
Site-to-Site Replication Client-Side via mc mirror Server-Side Replication <minio-bucket-replication> Server-Side Replication <minio-bucket-replication>
Versioning No Object Versioning <minio-bucket-versioning> Object Versioning <minio-bucket-versioning>
Retention No Write-Once Read-Many Locking <minio-bucket-locking> Write-Once Read-Many Locking <minio-bucket-locking>
High Availability / Redundancy Drive Level Only (RAID and similar) Drive Level only with Erasure Coding <minio-erasure-coding> Drive and Server-Level with Erasure Coding <minio-erasure-coding>
Scaling No Server Pool Expansion <expand-minio-distributed> Server Pool Expansion <expand-minio-distributed>.

Site Replication

Site replication expands the features of bucket replication to include IAM, security tokens, service accounts, and bucket features the same across all sites.

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

What Does Not Replicate?

Not everything replicates across sites.

Platform Support

MinIO provides builds of the MinIO server (minio) and the MinIO CLI (Command Line Interface) (mc) for the following platforms.

linux

  • Red Hat Enterprise Linux 8.5+ (including all binary-compatible RHEL alternatives)
  • Ubuntu 18.04+

MinIO provides builds for the following architectures:

  • AMD64
  • ARM64
  • PowerPC 64 LE
  • S390X

macos

MinIO recommends non-EOL macOS versions (10.14+).

windows

MinIO recommends non-EOL Windows versions (Windows 10, Windows Server 2016+). Support for running distributed MinIO deployments <deploy-minio-distributed> is experimental on Windows OS.

For unlisted platforms or architectures, please reach out to MinIO at hello@min.io for additional support and guidance. You can build MinIO from source <minio/#install-from-source> and cross-compile for your platform and architecture combo. MinIO generally does not recommend source-based installations in production environments.

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