Backup to MinIO installed on Docker, error occurred

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: br 备份至 docker安装的MinIO,出错

| username: TiDBer_2i1SqvUB

[TiDB Usage Environment] Production Environment / Testing / PoC
Testing Environment
[TiDB Version]
V6.5.2
[Reproduction Path] What operations were performed when the issue occurred
Used BR to back up cluster data to MinIO
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration]
[Attachments: Screenshots / Logs / Monitoring]



The error is “failed to get region of bucket…”
Has anyone encountered a similar issue?

| username: xfworld | Original post link

Is it possible that the bucket wasn’t created?

| username: TiDBer_2i1SqvUB | Original post link

Created

| username: xfworld | Original post link

400 means access failure, check the authorization and other related aspects.

| username: TiDBer_2i1SqvUB | Original post link

It still doesn’t seem to work. I’m using administrator privileges.

| username: 像风一样的男子 | Original post link

Add the parameter --region in the command.

| username: xfworld | Original post link

Is the command written incorrectly?
Refer to:

./br backup db --pd "pd_ip:pd_port" --storage "s3://access_key:secret_key@endpoint/bucket_name" --ratelimit 60 --log-file backup.log

Here, “pd_ip:pd_port” is the address of your PD server, “access_key” and “secret_key” are the access key and secret key of your MinIO account, “endpoint” is the endpoint of your MinIO server, and “bucket_name” is the name of the bucket you created for backup.

The “–ratelimit” option specifies the maximum transfer rate in MB/s, and the “–log-file” option specifies the path to the log file.

| username: TiDBer_2i1SqvUB | Original post link

It prompts that there is no such parameter.

| username: TiDBer_2i1SqvUB | Original post link

Is this accessed via IAM?

| username: dba-kit | Original post link

Try this format, you need to actively set access-key=${access-key}&secret-access-key=${secret-access-key}, using @ method does not work.

| username: xfworld | Original post link

The MinIO documentation is indeed lacking, which is a bit frustrating :upside_down_face: :upside_down_face: :upside_down_face: :upside_down_face: :upside_down_face:

| username: TiDBer_2i1SqvUB | Original post link

It still doesn’t seem to work, boss.

| username: TiDBer_2i1SqvUB | Original post link

Yes, it’s a bit confusing.

| username: dba-kit | Original post link

I suspect it’s an issue with MinIO. Did you execute this command?

| username: TiDBer_2i1SqvUB | Original post link

No, I only downloaded the server, not the client.

| username: TiDBer_2i1SqvUB | Original post link

There’s no need to use Docker; just install it natively on Linux. It’s very strange, I don’t know why.

| username: dba-kit | Original post link

What is your docker run command? Did you forget to expose some ports?

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.