forked from TrueCloudLab/frostfs-s3-gw
72 lines
3.6 KiB
Markdown
72 lines
3.6 KiB
Markdown
# Shared Backend MinIO Quickstart Guide [](https://slack.min.io) [](https://hub.docker.com/r/minio/minio/)
|
|
|
|
MinIO shared mode lets you use single [NAS](https://en.wikipedia.org/wiki/Network-attached_storage) (like NFS, GlusterFS, and other
|
|
distributed filesystems) as the storage backend for multiple MinIO servers. Synchronization among MinIO servers is taken care by design.
|
|
Read more about the MinIO shared mode design [here](https://github.com/minio/minio/blob/master/docs/shared-backend/DESIGN.md).
|
|
|
|
MinIO shared mode is developed to solve several real world use cases, without any special configuration changes. Some of these are
|
|
|
|
- You have already invested in NAS and would like to use MinIO to add S3 compatibility to your storage tier.
|
|
- You need to use NAS with an S3 interface due to your application architecture requirements.
|
|
- You expect huge traffic and need a load balanced S3 compatible server, serving files from a single NAS backend.
|
|
|
|
With a proxy running in front of multiple, shared mode MinIO servers, it is very easy to create a Highly Available, load balanced, AWS S3 compatible storage system.
|
|
|
|
# Get started
|
|
|
|
If you're aware of stand-alone MinIO set up, the installation and running remains the same.
|
|
|
|
## 1. Prerequisites
|
|
|
|
Install MinIO - [MinIO Quickstart Guide](https://docs.min.io/docs/minio-quickstart-guide).
|
|
|
|
## 2. Run MinIO on Shared Backend
|
|
|
|
To run MinIO shared backend instances, you need to start multiple MinIO servers pointing to the same backend storage. We'll see examples on how to do this in the following sections.
|
|
|
|
*Note*
|
|
|
|
- All the nodes running shared MinIO need to have same access key and secret key. To achieve this, we export access key and secret key as environment variables on all the nodes before executing MinIO server command.
|
|
- The drive paths below are for demonstration purposes only, you need to replace these with the actual drive paths/folders.
|
|
|
|
#### MinIO shared mode on Ubuntu 16.04 LTS.
|
|
|
|
You'll need the path to the shared volume, e.g. `/path/to/nfs-volume`. Then run the following commands on all the nodes you'd like to launch MinIO.
|
|
|
|
```sh
|
|
export MINIO_ACCESS_KEY=<ACCESS_KEY>
|
|
export MINIO_SECRET_KEY=<SECRET_KEY>
|
|
minio gateway nas /path/to/nfs-volume
|
|
```
|
|
|
|
#### MinIO shared mode on Windows 2012 Server
|
|
|
|
You'll need the path to the shared volume, e.g. `\\remote-server\smb`. Then run the following commands on all the nodes you'd like to launch MinIO.
|
|
|
|
```cmd
|
|
set MINIO_ACCESS_KEY=my-username
|
|
set MINIO_SECRET_KEY=my-password
|
|
minio.exe gateway nas \\remote-server\smb\export
|
|
```
|
|
|
|
*Windows Tip*
|
|
|
|
If a remote volume, e.g. `\\remote-server\smb` is mounted as a drive, e.g. `M:\`. You can use [`net use`](https://technet.microsoft.com/en-us/library/bb490717.aspx) command to map the drive to a folder.
|
|
|
|
```cmd
|
|
set MINIO_ACCESS_KEY=my-username
|
|
set MINIO_SECRET_KEY=my-password
|
|
net use m: \\remote-server\smb\export /P:Yes
|
|
minio.exe gateway nas M:\export
|
|
```
|
|
|
|
## 3. Test your setup
|
|
|
|
To test this setup, access the MinIO server via browser or [`mc`](https://docs.min.io/docs/minio-client-quickstart-guide). You’ll see the uploaded files are accessible from the all the MinIO shared backend endpoints.
|
|
|
|
## Explore Further
|
|
- [Use `mc` with MinIO Server](https://docs.min.io/docs/minio-client-quickstart-guide)
|
|
- [Use `aws-cli` with MinIO Server](https://docs.min.io/docs/aws-cli-with-minio)
|
|
- [Use `s3cmd` with MinIO Server](https://docs.min.io/docs/s3cmd-with-minio)
|
|
- [Use `minio-go` SDK with MinIO Server](https://docs.min.io/docs/golang-client-quickstart-guide)
|
|
- [The MinIO documentation website](https://docs.min.io)
|