backcup in standalone and restore to k8s,there are some error

[hxlsky]

i bakcup milvusdb in standalone and restore to k8s,it raise error:

how can i do?

[yhmo]

"Object name contains unsupported characters" is an error returned by MinIO copy() interface. Probably the path contains illegal characters.

Set log level to "debug" in the backup.yaml

log:
  level: debug

Try restore again, and send the full log of milvus-back for me.

[hxlsky]

i replace the minio from "minio/minio:latest" to "minio/minio:RELEASE.2023-03-20T20-16-18Z",the restore can success.

is the minio/minio:lastest bug?

[yhmo]

I think it is not a bug, maybe a design change of minio. I guess the error is caused by the double slash "//" in object path. minio 2023 accepts the double-slash but 2024 doesn't accept.

Milvus official deployment already specified the versions of dependencies, which are tested by milvus QA team. Change the dependency to un-tested version might encounter imcompatible problems.

[hxlsky]

how can i known the "Milvus official deployment already specified the versions of dependencies"?

how can i check the object path contain "//",but all my collection name does not contain "//"

[yhmo]

When you install a milvus standalone, the doc tells where to download the docker-compose.yml
wget https://github.com/milvus-io/milvus/releases/download/v2.5.0-beta/milvus-standalone-docker-compose.yml -O docker-compose.yml

The docker-compose.yml uses minio RELEASE.2023-03-20T20-16-18Z which is already tested by milvus qa team and works perfectly with milvus and milvus-backup.

  minio:
    container_name: milvus-minio
    image: minio/minio:RELEASE.2023-03-20T20-16-18Z

I guess the milvus-backup internally might construct a path with double-slash and pass to minio. But double-slash path is accepted by minio RELEASE.2023-03-20T20-16-18Z but not accepted by some other version of minio.