Does the Milvus standalone Docker image include MinIO? How to configure backup?

[0000005]

Hi team,

I'm currently using the standalone Milvus Docker image (installed via plain docker run on Linux, not using docker-compose).

Now, I want to enable data backup, so I looked into the milvus-backup component. According to the documentation, it requires access to Milvus's MinIO service for query data.

However, after inspecting the Milvus standalone Docker container, I couldn't find any trace of MinIO running inside it — no open ports, no running processes, and no configuration referring to MinIO.

My questions are:

1. Does the standalone Docker image of Milvus include MinIO by default?
2. If not, what is the recommended way to enable or connect MinIO when running Milvus in standalone mode (via docker run)?
3. Is there an official guide or best practice for setting up backup in this scenario?

Any help or clarification would be greatly appreciated!

Thanks in advance!

[yhmo]

Standalone deployment:

• docker https://milvus.io/docs/install_standalone-docker.md
• docker-compose https://milvus.io/docs/install_standalone-docker-compose.md

docker standalone is a one-container deployment, etcd is embeded in the milvus container, it uses local storage to store data instead of minio. If you open the standalone_embed.sh by text editor,you will see this command:

    sudo docker run -d \
        --name milvus-standalone \
        --security-opt seccomp:unconfined \
        -e ETCD_USE_EMBED=true \
        -e ETCD_DATA_DIR=/var/lib/milvus/etcd \
        -e ETCD_CONFIG_PATH=/milvus/configs/embedEtcd.yaml \
        -e COMMON_STORAGETYPE=local \
        -v $(pwd)/volumes/milvus:/var/lib/milvus \
        -v $(pwd)/embedEtcd.yaml:/milvus/configs/embedEtcd.yaml \
        -v $(pwd)/user.yaml:/milvus/configs/user.yaml \
        -p 19530:19530 \
        -p 9091:9091 \
        -p 2379:2379 \
        --health-cmd="curl -f http://localhost:9091/healthz" \
        --health-interval=30s \
        --health-start-period=90s \
        --health-timeout=20s \
        --health-retries=3 \
        milvusdb/milvus:v2.5.5 \
        milvus run standalone  1> **/dev/null

docker-compose standalone is a three-container deployment, milvus container, etcd container, minio container

In the config file of milvus-backup, the StorageType:

storageType: "minio" # support storage type: local, minio, s3, aws, gcp, ali(aliyun), azure, tc(tencent)

https://github.com/zilliztech/milvus-backup/blob/b1f4d20656937092b202308b65198aef59858087/configs/backup.yaml#L34

Technically "local storage" is supported, but seldom tested.

In milvus local storage mode, all data files are stored under this path in the container:

milvus/configs/milvus.yaml

Line 91 in c15c550

path: /var/lib/milvus/data/

localStorage:
  # Local path to where vector data are stored during a search or a query to avoid repetitve access to MinIO or S3 service.
  # Caution: Changing this parameter after using Milvus for a period of time will affect your access to old data.
  # It is recommended to change this parameter before starting Milvus for the first time.
  path: /var/lib/milvus/data/

In the standalone_embed.sh, the internal path /var/lib/milvus/data/ is mapped to outside ./volumes/milvus

-v $(pwd)/volumes/milvus:/var/lib/milvus \

So, I suppose the milvus-backup can work with local storage with these configurations:

minio:
  storageType: "local"
  ......(other configurations no change)
  rootPath: "[path to volumes]/volumes/milvus" # Milvus storage root path in MinIO/S3, make it the same as your milvus instance

  backupStorageType: "local"
  ......(other configurations no change)
  backupRootPath: "[path to volumes]/volumes/backup"
  ......

[0000005]

thank you for your reply